When GNSS disappears, what happens next?
A practical response plan for maintaining navigation, timing and mission services through jamming, spoofing and loss of satellite reference.
GNSS resilience starts with defined system behaviour
Most GNSS-dependent systems perform well while the sky is clear and the received signal remains valid. The engineering challenge begins when the signal becomes unreliable. Jamming may remove reception. Spoofing may provide believable but incorrect position or time. Local interference can degrade performance without creating an obvious alarm.
GNSS-denied operations require more than a backup receiver. Teams need to decide how the system detects abnormal conditions, which functions must continue, how long accuracy must be maintained and what evidence operators need to make the next decision.
The useful starting point is the operational consequence. A navigation platform may need to preserve position and heading. A timing system may need to hold frequency within a defined limit. A substation or broadcast facility may need network synchronisation to continue while the GNSS reference remains isolated.
Turn a GNSS outage into testable requirements
“Keep operating” is too broad to verify. A resilient PNT specification should describe the event, the required response and the evidence that proves the system behaved correctly.
| Condition | Required system behaviour | Evidence to retain |
|---|---|---|
| Broadband jamming | Detect loss of usable GNSS, reject the reference and enter the defined holdover or alternate-navigation state. | RF event data, receiver state, reference change, timing or position error and operator alert. |
| Spoofing or manipulated timing | Identify inconsistent signal behaviour, prevent an untrusted source from steering the system and preserve service from accepted references. | Classification indicators, source comparison, rejection decision and downstream system response. |
| Partial degradation | Continue within agreed performance limits while increasing monitoring and preparing controlled isolation. | Signal quality trends, satellite data, oscillator state and deviation from the operational baseline. |
| Reference restoration | Return to the preferred reference without an uncontrolled step in time, position or network synchronisation. | Recovery timing, convergence behaviour, alarms cleared and post-event validation. |
An operational playbook for GNSS-denied environments
The following sequence connects design assumptions to repeatable testing and an operator response.
-
Map the dependency
Identify every service that consumes GNSS-derived position, time or frequency. Trace the reference through receivers, grandmasters, switches, applications and operational displays. This prevents a hidden dependency from becoming the first discovery during an outage.
- Record interfaces, protocols and client systems
- Define the consequence of incorrect data as well as missing data
-
Reproduce the failure safely
Laboratory simulation allows teams to expose receivers and complete systems to repeatable jamming, spoofing and timing-manipulation scenarios without radiating uncontrolled interference. GPSPATRON GP-Simulator 2 and GP-Jammer support controlled validation before field deployment.
- Test detection thresholds and rejection logic
- Measure how downstream services behave during each transition
-
Detect and classify the live event
Operational monitoring should distinguish interference from an ordinary receiver or antenna fault. Persistent and portable GPSPATRON sensors can observe RF conditions, timing behaviour and spoofing indicators, allowing alarms to carry useful context into the operations environment.
- Correlate RF evidence with receiver and timing state
- Send classified alerts to the systems operators already monitor
-
Sustain the required function
Continuity may come from oscillator holdover, an alternate timing reference, inertial sensing or multi-sensor fusion. The method depends on the mission. Meinberg holdover supports time and frequency continuity, while AEVEX assured PNT combines timing, inertial data and other sensors for navigation across air, land and maritime platforms.
- Specify the maximum drift or navigation error over time
- Define when the system must warn, isolate or stop a function
-
Recover with evidence
Recovery should be controlled and measurable. Store the interference record, reference changes, holdover performance and downstream response. That evidence supports engineering review, operational reporting and improvement of future test cases.
- Validate convergence before restoring normal dependence
- Update thresholds, procedures and test scenarios from the event
The technology layers must work as one system
No single product covers the complete failure path. The architecture connects validation, situational awareness, continuity and distribution.
GPSPATRON simulation
Create repeatable jamming and spoofing conditions to validate receiver logic, alarms and system behaviour before deployment.
Explore GPSPATRON testingGPSPATRON monitoring
Observe live GNSS and RF conditions so operations teams can investigate interference before it remains an unexplained system fault.
View GPSPATRON productsMeinberg resilient timing
Multi-source timing and holdover maintain an accepted timebase while GNSS is unavailable or deliberately isolated.
Explore Meinberg timingAEVEX PNT
Integrated timing, inertial sensing and multi-sensor fusion support navigation when GNSS becomes degraded or denied.
Explore AEVEX capabilityRelyum rugged networking
PTP-aware TSN with HSR or PRP redundancy carries trusted time and mission traffic through harsh environments without a single network path becoming the weak point.
Explore Relyum networkingiTkey system engineering
Bring alerts, timing state, alternate references and performance evidence into the wider operational system and response process.
Discuss integrationWhat continuity looks like in different operations
The required response changes with the function at risk. These examples show why a common “GNSS backup” specification rarely goes far enough.
Defence platform
The navigation solution detects inconsistent GNSS, reduces reliance on the affected measurements and continues from inertial and other accepted sensors. Operators receive the confidence state and expected error growth.
Energy substation
The timing system rejects the affected GNSS reference, enters specified holdover and continues distributing PTP across redundant network paths. The control centre receives alarms and retained event data.
Financial infrastructure
Timestamping remains within the agreed accuracy limit while alternate references and holdover support the primary and recovery sites. The event record preserves traceability for technical and compliance review.
Broadcast facility
The facility preserves PTP for media systems while the affected external reference remains isolated. Engineers can correlate the interference event with grandmaster state and downstream synchronisation performance.
Questions for the architecture workshop
A useful workshop should produce measurable requirements rather than a generic resilience objective.
- Which operational functions depend directly or indirectly on GNSS?
- Which interference and spoofing conditions must the system detect?
- How quickly must operators receive a classified alert?
- What accuracy must remain after 10 minutes, one hour or one day?
- Which alternate references or sensors can the system accept?
- What degraded behaviour remains safe and useful?
- How will trusted time and mission data cross a network failure?
- Which evidence must remain available after recovery?
Define the response before the signal disappears
Bring iTkey the operating environment, required continuity, interfaces and expected threats. We will map the dependency, testing, detection, holdover, navigation and networking layers into a resilient PNT architecture.
Technical basis: iTkey Land Forces 2026 PNT field notes. Product capabilities and performance depend on the selected configuration, interfaces, operating environment and integration design.
Ready to Discuss Your Requirements?
Our technical experts are ready to help you design and implement the perfect timing solution for your critical infrastructure needs.
- Precision EngineeringOur timing solutions deliver nanosecond-level accuracy for the most demanding applications.
- Security FirstMilitary-grade security features and compliance with classified network requirements.
- Expert SupportTechnical support from timing specialists with defence and infrastructure experience.
- Custom SolutionsTailored timing architectures designed for your specific operational requirements.
Open the published page to view and test the live form.
