Responding to suspected GNSS interference in the field

Recognize a positioning problem before naming its cause

GNSS receivers can be affected by interference from natural or human made sources. Intentional jamming is one possible cause of degraded reception, but similar field symptoms can arise from obstruction, equipment faults, power problems or configuration errors. Begin by identifying what changed and whether the positioning evidence remains suitable for the task. A controller warning or a lost solution is a reason to investigate, not proof that a particular person or device is responsible.

The immediate priority is to stop relying on an unverified position where that reliance could affect the work. Follow the site's normal safety and operational procedures. For a survey crew, this may mean pausing coordinate collection and protecting the current setup while checks are performed. Do not continue storing points merely because an approximate position remains visible or because the correction connection still appears active.

Continue learning The ionosphere and GNSS: why conditions can change

Preserve a factual event record

Record the time, location, equipment configuration, observed symptoms and operational impact. Include the time convention, because an event log without a clear time system is difficult to compare with service records. Save relevant receiver diagnostics and raw observations where supported. Photographs of the normal setup can be useful, but avoid approaching unfamiliar equipment or interrupting other site activities in an attempt to identify a source.

Separate observation from interpretation. Statements such as tracking lost across several constellations or repeated control checks failed are more useful than an unsupported claim that a jammer was present. Keep the original files unchanged and note any later configuration changes. A reliable timeline allows the equipment supplier, service operator or appropriate authority to assess the event without relying on an increasingly embellished account passed between crews.

Continue learning Diagnosing interference symptoms in GNSS correction radios

Check ordinary equipment dependencies first

Inspect power continuity, antenna connections where applicable, cable condition and receiver events. Confirm that the equipment is using the intended configuration and that no recent change explains the behavior. If the issue is limited to one receiver, compare with a known suitable unit under controlled conditions where practical. Do not assume that two devices using the same shared antenna, power supply or software configuration provide fully independent evidence.

Review the correction path separately from satellite reception. A cellular outage, expired service access or wrong mountpoint can prevent an RTK solution without indicating radio interference at GNSS frequencies. Conversely, a healthy NTRIP connection does not establish that satellite observations are sound. Keeping these dependencies separate avoids wasting time on the wrong system and produces a clearer report for anyone assisting with diagnosis.

Continue learning Managing GNSS field operations during changing solar activity

Compare local and wider behavior

Determine whether the problem occurs at one obstructed point, across the site or among separate crews. A change that follows a particular physical location suggests different hypotheses from a simultaneous event observed across independent open sites. Use authorized routine movements and existing project checks; do not undertake a search for a suspected transmitter or interfere with other equipment. Technical source identification belongs with appropriately equipped and authorized specialists.

Consult official service status information and relevant space weather context. Record what was available at the time rather than rewriting the event history after an explanation appears plausible. A broad status notice can support the investigation without proving the cause of every local symptom. Similarly, the absence of a notice does not establish that the crew's problem was imaginary or that collection can safely resume without verification.

Continue learning Cross-checking suspicious GNSS positions without jumping to conclusions

Use an approved alternative workflow

If the GNSS evidence is unsuitable, follow the project's contingency method. This may involve another survey technique, a different work area or a pause until independent verification is possible. Confirm that alternative control is valid. Switching instruments does not solve a coordinate framework problem if the new method starts from the same unverified GNSS points that triggered concern.

Keep provisional and accepted observations clearly separated. Mark the affected time span and point identifiers for office review. Do not delete them immediately, because they may be valuable for diagnosis, but prevent them from entering an issued coordinate list by accident. The crew and office should agree on status labels and handover responsibilities so an operational pause does not turn into an ambiguous mixture of trusted and untrusted data.

Continue learning The ionosphere and GNSS: why conditions can change

Escalate through the appropriate channels

Notify the project lead and the equipment or service support contact as appropriate. Provide the factual event record, diagnostics and checks already performed. If suspected interference requires reporting, use the relevant local authority or official reporting process for the jurisdiction. Do not apply another country's legal rules automatically, and do not accuse a nearby operator based only on a coincidence in time or proximity.

Never test the theory by operating a jammer or other interfering device. Such a test can disrupt other users and is unnecessary for a survey crew's quality decision. The practical question is whether the positioning workflow has adequate evidence for the task. Preserve that evidence and let authorized specialists investigate the radio environment if source identification is required.

Continue learning Diagnosing interference symptoms in GNSS correction radios

Resume only after suitable verification

When reception appears normal, perform the project's checks before restarting production. Confirm configuration, solution behavior, independent control and any required repeat occupations. A recovered satellite count or a green solution icon is useful but incomplete evidence. Record the time at which normal collection resumed and identify whether points from the affected period need recollection or a restricted status.

If a receiver or configuration was changed during the event, verify that the new setup uses the correct coordinate framework, antenna information and correction source. An emergency equipment swap can introduce a second problem even after the original reception issue disappears. Retain both configurations and the transition time so office analysts can interpret the dataset without guessing which equipment produced each group of points.

Continue learning Managing GNSS field operations during changing solar activity

Identify the last verified observation

During the event review, locate the latest successful independent check and the first evidence of degradation. These times help define an initial investigation window without claiming that every point between them is either valid or invalid. Use logs and project criteria to refine the affected span. This is more defensible than assuming the event began exactly when an operator first noticed a warning, and it gives the office a practical starting point for targeted remeasurement and acceptance review.

Continue learning Cross-checking suspicious GNSS positions without jumping to conclusions

Close the event with a defensible conclusion

The final record should summarize symptoms, checks, actions, accepted observations and unresolved questions. Use cautious causal language where the source was not established. Suspected interference is a meaningful conclusion when supported by evidence; confirmed intentional jamming requires stronger evidence than a survey crew normally collects. The report should make that distinction without minimizing the operational impact.

A well handled event protects both survey quality and the credibility of the organization. It avoids unsupported accusations, preserves useful technical evidence and provides a clear path back to verified collection. The same disciplined response is valuable whether the eventual cause is interference, a failed cable, an obstructed site or a service problem that initially looked much more unusual.

Continue learning The ionosphere and GNSS: why conditions can change