Data Services for the Digital Earth
TerraNexus GNSS-Independent Navigation DemonstratorMulti-resolution TerraNexus DGGS corridor through GPS-jammed airspace · FRA → DXB |
What you're looking at → click any section below to expand the full context for this demonstration.
In April 2026, CNN reported that GPS jamming incidents have driven thousands of aircraft to issue false “terrain pull-up” warnings, abort approaches, and divert mid-flight. The vulnerability is structural: every commercial flight on Earth depends on a satellite signal that can be drowned out by a transmitter the size of a backpack.
Jamming is no longer rare or remote
Eastern Europe, the Black Sea, the eastern Mediterranean, parts of the Gulf and the Baltic now record continuous, large-scale GPS interference affecting civilian airspace.
Spoofing is more dangerous than jamming
A spoofed GPS receiver doesn't just lose its position — it confidently reports a false one. Several recent incidents involved aircraft believing they were hundreds of kilometres from their actual location.
SBAS, WAAS and SouthPAN inherit the same vulnerability
Augmentation systems improve accuracy — they do not replace the underlying signal. If GNSS is denied, augmentation goes with it.
The fallback is unaided inertial dead-reckoning
Inertial systems drift over time and have no map. Without an external reference, a four-hour flight can accumulate kilometres of position error.
The aviation industry has invested heavily in GNSS augmentation. The problem is that every existing layer either depends on the GNSS signal itself, or has no spatial map to keep an aircraft aligned to its planned route.
SBAS / WAAS / SouthPAN
- Improves GPS accuracy when signal is clean
- Mature, deployed, regulated
- Built directly on GNSS — jamming kills it too
- No defence against spoofing
Inertial Navigation Alone
- Self-contained, signal-independent
- Reliable for short intervals
- Drifts kilometres per hour without correction
- No external map to verify against
TerraNexus + Inertial
- Pre-flight route is sealed as a 4D corridor
- Inertial position is continuously matched to corridor
- Operates entirely without external signals
- Edge-deployable for in-flight rerouting
Before takeoff, the entire flight plan — latitude, longitude, altitude, and time — is encoded into a TerraNexus zoneSet: a compressed, integrity-checked sequence of 4D Discrete Global Grid System (DGGS) zones that defines exactly where the aircraft is supposed to be at every moment of the flight. No internet connection. No GPS. The corridor is loaded onto the aircraft and that's it.
1. Flight Plan
Filed route + schedule comes in from existing flight planning systems. No new operational workflow required.
2. Encode Corridor
TerraNexus compresses the 4D route into a zoneSet of ~200KB — integrity-sealed, signed, opaque to the outside world.
3. Loaded Onboard
TerraNexus Edge Deployment + INS. The aircraft carries a sealed, signed copy of its own corridor — entirely offline, no external dependencies.
4. In-Flight Match
INS provides motion. The corridor provides the map. The aircraft never asks “where am I?” in absolute terms — it asks “am I still inside the corridor?”, and that is a local check.
5. Continuous INS Re-Fix
Each TerraNexus zone has a known, immutable, deterministic 4D reference position derivable from its zone ID — zone reference coordinates that cannot drift, cannot be spoofed, and require no satellite signal to compute. When the aircraft is positively inside a zone, the INS uses that zone's centre as a positional re-fix — zeroing accumulated drift against ground truth on every confirmed cell entry. The INS does not coast through GPS denial; it is actively recalibrated by the corridor itself, with no external signal required.
This is the structural difference between TerraNexus and any other GNSS-fallback architecture. SBAS, ARAIM, and DME/DME augmentation all depend on receiving an external signal that is, in the limit, jammable. Pure-INS dead reckoning has no external reference at all and accumulates error at 0.6–2 nm/h. TerraNexus carries its own positional ground truth on the aircraft — sealed, signed, offline — and uses it to actively correct the INS rather than passively monitor it.
The corridor cubes are not lat/lon tiles — they are real DGGS zones from a live TerraNexus instance. The DGGS zones are axis-aligned in ECEF (Earth-Centered Earth-Fixed) coordinates; their visible orientation shifts as the route arcs around the planet because TerraNexus operates in 3D Cartesian space, not on a projected surface.
Adaptive resolution
Terminal phases use Level 7 (~11.7 km wide DGGS zones) for runway/SID/STAR precision. Climb-out and descent use Level 6 (~35 km wide DGGS zones). Cruise uses Level 5 (~105 km wide DGGS zones). The corridor literally narrows where precision is needed and broadens through the steady cruise.
Why this matters
Surface (2D) DGGS systems (e.g. H3, S2) can only define a flight path in 2D, leading to complex representations of flight path corridors involving a mix of DGGS zones + altitude + time that still require GNSS positioning information to operate. TerraNexus is a true 4D DGGS system, enabling the entire flightpath corridor to be defined by a simple zoneSet that can include multiple resolutions: higher-resolution zones where precision navigation is required (e.g. takeoff and landing), and lower-resolution zones elsewhere (e.g. at cruising altitude).
Shadow flight path (orange)
Shows the same flight without TerraNexus. The deviating track is illustrative of pilot manual corrections in response to inaccurate (or false) GNSS readings and INS drift during periods of degraded or denied GNSS signal. Lateral deviations are rendered at true physical scale: peak displacement of ~80 nm during severe events sits in the middle of the documented 60–225 nm spoofing-driven displayed-position errors reported by OPSGROUP, Aviation Week, and Honeywell (see Sources & References). The qualitative pattern (drift, manual fix, overshoot, multiple recoveries) is well-documented in those references; specific numeric parameters of the correction profile are tuned for demo timescale, not forensic accuracy of any single incident.
Four jamming events, one corridor
The flight transits four real-world interference patterns in sequence: Eastern European Corridor (moderate), Black Sea Region (severe), Iraq/Northern Gulf (severe), Persian Gulf Approach (moderate). DGGS Track stays LOCKED throughout.
Modern inertial navigation systems do not navigate from inertial sensors alone — they fuse IMU data with external aiding fixes through an Extended Kalman Filter, which estimates and corrects accumulating drift in real time. In conventional systems the aiding fix comes from GNSS. TerraNexus replaces that aiding fix with the DGGS enabled corridor itself.
Each zone is an immutable position reference
A TerraNexus DGGS zone has a single, mathematically defined centroid in ECEF space. Once a zoneSet is signed and loaded onboard, that centroid cannot change — it is not transmitted, not derived from an external signal, not subject to spoofing. It exists as bytes on the aircraft's edge instance.
Zone transitions act as aiding fixes
As the aircraft transits each DGGS zone, the IMU's estimated position is reconciled against the zone's known centroid. The Kalman filter consumes this as an aiding observation — functionally identical to a GNSS pseudorange update, but with a position reference that does not depend on a satellite signal of any kind.
Drift is bounded, not accumulated
Because aiding fixes arrive continuously throughout the flight (every L5 cell transition during cruise, every L6 in climb/descent, every L7 in terminal), the INS error never exceeds approximately one zone edge length before being corrected. A 5-hour flight that would otherwise accumulate ~5 nm of unaided drift stays inside the corridor envelope from takeoff to landing.
Watch this happen live
The INS Aiding row in the telemetry panel reads “CORRIDOR” throughout the flight and flashes “◉ ZONE FIX” at every cell transition. The Zone Fixes counter increments each time TerraNexus provides a new position aiding event. The INS Drift Rate stays bounded near the IRS noise floor (0.02–0.06 nm/h) regardless of jamming severity, because the corridor keeps correcting it.
Why this is fundamentally different from existing fallbacks: SBAS, WAAS, and SouthPAN improve the GNSS signal; if GNSS is denied, they fail with it. INS-only dead reckoning has no aiding source at all and accumulates drift unbounded. TerraNexus provides an independent aiding source — one that exists entirely on the aircraft, was sealed before takeoff, and cannot be jammed, spoofed, or intercepted because it doesn't transmit anything.
Every quantitative claim in this demo, and every qualitative behaviour shown in the shadow flight path, is grounded in published industry sources from regulators, safety organisations, and avionics manufacturers. Where a specific numeric parameter (e.g. the exact pilot-overcorrection percentage) is illustrative rather than directly sourced, this is stated explicitly.
GNSS jamming & spoofing — scale and severity
- EASA Safety Information Bulletin 2022-02R3 — GNSS Outages and Alterations Leading to Communication / Navigation / Surveillance Degradation (published July 2024). Identifies Black Sea, Eastern Mediterranean, Middle East, Baltic Sea, and Arctic as primary affected regions; warns of pilots reacting to false TAWS pull-up warnings. easa.europa.eu
- IATA Safety Risk Assessment — GNSS Interference, v5 (2025). Documents 220% increase in GPS signal-loss events between 2021 and 2024; identifies hotspots and trend lines. ic.iata.org
- OPSGROUP GPS Spoofing WorkGroup Final Report (Sept 2024, 128 pages, 950 contributors). Establishes ~1,500 flights per day spoofed in summer 2024 versus 300 in Q1/Q2 of 2024 (a 500% increase); 8 overall safety concerns and 33 specific concerns raised. ops.group
- EASA & IATA joint workshops on GNSS interference (Cologne, Jan 2024 and May 2025). Multi-stakeholder industry response with formal recommendations to ICAO. easa.europa.eu
- Aireon — Observations of trends in GPS anomalies affecting aviation (May 2025 white paper). Independent ADS-B-based analysis of GPS anomaly patterns globally. aireon.com
Inertial Reference System drift — the basis for the shadow path
- SKYbrary — Inertial Reference System (IRS). Confirms modern strap-down LRG INS drift rate of ~0.6 nm/h; older stabilised platforms 2 nm/h. Reviewed by Eurocontrol/Skybrary editorial board. skybrary.aero
- Honeywell Aerospace — GPS Spoofing & Jamming Solutions (manufacturer guidance). Confirms typical Pure-IRS drift rates of 1–2 nm/h; describes how Hybrid IRS becomes contaminated by spoofed GPS data over time. aerospace.honeywell.com
- IVAO Documentation Library — Inertial Navigation Systems. Independent confirmation of 0.6 nm/h modern / 2 nm/h legacy drift figures, plus discussion of Schuler loop and transport-wander corrections. wiki.ivao.aero
INS aiding via external position fixes — the Kalman filter basis for TerraNexus auto-recalibration
- VectorNav — INS (Inertial Navigation System) Solutions (manufacturer documentation). Describes the standard INS architecture: an IMU fused with one or more aiding sources through an Extended Kalman Filter, which "uses external corrections to bind that drift" and produce a continuous navigation estimate. The principle is GNSS-agnostic — aiding fixes can come from any source that provides a verified position. vectornav.com
- SBG Systems — Tight Coupling (manufacturer documentation). Detailed treatment of GNSS/INS Kalman filter integration. Confirms that "with a single pseudorange measurement, the Kalman Filter can still derive an error correction vector that effectively restrains the INS drift." Establishes that drift bounding from a single position observation is well-understood engineering practice. sbg-systems.com
- Salychev et al. — A Novel Approach for Kalman Filter Tuning for Direct and Indirect Inertial Navigation System / Global Navigation Satellite System Integration (PMC peer-reviewed, 2024). Academic treatment of open-loop and closed-loop error feedback architectures in INS/GNSS integration. The "closed-loop" architecture — where corrections are fed back into the INS state at each iteration — is the standard pattern TerraNexus's zone-fix aiding would use. pmc.ncbi.nlm.nih.gov
Pilot response to GPS spoofing — documented incident behaviour
- OPSGROUP — Flights misled over position, navigation failure follows (26 Sept 2023). First public incident report: aircraft on airway UM688 over Iraq with position shown 60 nm east of true location; crews forced to request ATC vectors when all onboard navigation systems failed. ops.group
- OPSGROUP — GPS Spoofing Update: Map, Scenarios and Guidance (Nov 2023). Documents three distinct spoofing scenarios with verbatim crew reports: Gulfstream G650 from Tel Aviv with EPU jumping to 99 nm, FMS believing aircraft was 225 nm south of true position; Bombardier Global Express spoofed to show position over Beirut. ops.group
- Aviation Week — The Serious Threat Of GPS Spoofing: An Analysis (Oct 2023). Industry analysis confirming spoofed FMS displays of aircraft "more than 60 nm off-track" with subsequent IRS contamination. aviationweek.com
- NBAA / Honeywell — Pilot, OEM Share Best Practices to Fight GPS Spoofing Attacks (March 2025). Honeywell's senior director of commercial navigation systems and an MP Air senior captain document position jumps of 50 to several hundred miles, with the “insidious” smaller incremental shifts being the most dangerous because they are easy to miss. nbaa.org
- GPS World — GNSS spoofing threatens airline safety (Oct 2024). Documents United Airlines New Delhi–New York flight (August 2024) whose GPS was spoofed for the entire flight, ending with the GPS reporting termination in the Atlantic Ocean while the aircraft actually landed at Newark. Includes FAA Chief Scientist Ken Alexander on workload risk: “If we lose an airplane because of workload issues...compounded with an emergency, that is going to be a horrendous event.” gpsworld.com
- Air Traffic Technology International — GPS Spoofing and Jamming: Can we keep aviation on track? (March 2025). Documents Boeing 777 captain's account of an aircraft forced to rely on INS alone over the North Atlantic following GPS interference, ultimately landing short of US destination to refuel. airtraffictechnologyinternational.com
Honest disclosure — what's illustrative vs sourced
Directly sourced from references
• Geographic locations of jamming hotspots (refs 1, 2, 12–13)
• INS drift rates of 0.6–2 nm/h (refs 6, 7, 8)
• INS aiding via Kalman filter from external position fixes (refs 9, 10, 11)
• Pilots resorting to ATC vectors during nav failures (refs 12, 13, 17)
• Position jumps of 50–200+ nm during spoofing (refs 13, 14, 15)
• ~1,500 flights/day spoofed (refs 2, 3)
• Hybrid IRS contamination by spoofed GPS (refs 7, 14)
Illustrative for visual demonstration
• The shadow's deviating track is illustrative of pilot manual corrections in response to inaccurate or false GNSS readings combined with INS drift during periods of degraded or denied GNSS signal — the qualitative pattern (drift, manual fix, overshoot, repeated recoveries) is well-documented in the cited references; specific numeric parameters of the simulation are not.
• Lateral deviations are rendered at true physical scale, in nautical miles. The simulation's drift parameters are tuned to produce peak deviations in the 60–90 nm range — in the middle of documented spoofing magnitudes (refs 10, 11, 12). No visual multiplier is applied.
• Specific 35% overshoot percentage on the shadow's manual correction. Documented incidents establish that pilots make manual corrections after GPS recovery, but the precise overshoot fraction is a design choice for demo readability, not a value attributable to a specific source.
• The 25-second correction profile and smoothstep ease curve. Illustrative timing chosen to fit the 5-minute compressed simulation.
• Specific drift random-walk variance and bias direction selection per zone. Illustrative; chosen to produce a visibly varied track with realistic per-zone severity gradient (severe > moderate).
The shadow path's purpose is to convey, qualitatively, the difference between a flight relying on continuous DGGS reference (smooth track) and one relying on intermittent GPS recovery with manual pilot correction (ragged track). Numeric parameters are tuned for readability at demo timescales, not for forensic accuracy of any specific real-world incident.
Dubai sits downstream of every interference hotspot in the demo. Every long-haul connection through DXB is, by geography, a transit through GPS-contested airspace. The result: measurable diversions, delayed approaches, and loss-of-position incidents that have direct cost to operators with both the means and the motivation to fund a structural fix.
Concentrated stakeholders
Emirates, Etihad, FlyDubai, GCAA, Mubadala, ADQ, and EDGE Group are all within a single procurement ecosystem. A single successful pilot can scale through the connected fleet rapidly.
Sovereign positioning capability
For UAE Defence and aviation regulators, GNSS-independent navigation is also a sovereignty story: a navigation reference that does not depend on US-controlled satellite infrastructure or its augmentation systems.
Defensible commercial argument
The cost of a single diversion (fuel, slot loss, passenger compensation, crew duty extension) is six figures. A fleet-wide TerraNexus deployment pays back in single-digit weeks given current incident rates.
Beyond aviation
Same lattice, same corridor primitive, addresses GNSS-denied operations in maritime, autonomous logistics, drone corridors, and critical infrastructure monitoring. Aviation is the wedge — not the ceiling.