What to do when RTK NTRIP connection drops in the field
When RTK correction drops, the key is to diagnose and record the problem before trusting the measurement.
Field takeaways
- Stop critical measurements when fixed solution is lost.
- Check correction age, internet, satellites, PDOP and multipath.
- Re-check a known control point after corrections return.
- Do not use float or standalone results for precision stake-out.
- MapLab Survey helps keep notes and records with the job.
First, stop measuring
The expensive mistake is not the dropout but carrying on as if nothing happened. The moment the solution falls from fixed to float, stop and mark the last reliable point.
Quick diagnosis
Check mobile data coverage, the NTRIP session and the link to the receiver. If the operator network is the problem, no setting on the phone will fix it.
Plan B
A local base or a PPK workflow lets you continue without the network. If neither is available, do the work that does not need precision and keep the critical points for later.
After it returns
Do not just accept the fix. Re-measure the last reliable point and confirm it agrees within tolerance.
Try these steps on your own phone.
MapLab Survey handles RTK/GNSS point capture, drawing, area and volume calculations and coordinate conversion, then exports to DXF, KML/KMZ, GeoJSON, Shapefile, GeoPackage, NCZ or CSV. Capture, calculation and export work offline. Live NTRIP corrections and online basemaps need a connection.
Frequently asked questions
Can I measure after fixed is lost?
Not for critical precision work.
Why does NTRIP drop?
Internet, credentials, mountpoint, service or site conditions.
Can float be used?
Not for precision delivery.
What after reconnecting?
Check a known control point.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: RTK GNSS field accuracy · GPS measurement error · Field survey checklist · MapLab Survey