The Spoofed Position, GPS Interference Over the Middle East and Baltic, and the ADS-B Integrity Problem Nobody Built a Fix For Yet
GPS spoofing in the Middle East and Baltic regions is silently feeding false position data into ADS-B transponders, with no onboard alert to warn pilots or controllers.
GPS spoofing is corrupting ADS-B position data at operational scale in specific regions of the world, and the aviation system has no built-in mechanism to catch it. When a spoofing device replaces legitimate satellite signals with fabricated ones, an aircraft’s transponder broadcasts false position data with full confidence - to other aircraft, to ATC, and to oceanic surveillance systems. The underlying problem is architectural: ADS-B was designed to trust GPS, and that trust is now being deliberately exploited.
How GPS Spoofing Corrupts ADS-B Position Data
ADS-B Out - required in Class A, B, and C airspace in the United States since January 2020 - works by taking a GPS-derived position and broadcasting it every second to ground stations and nearby aircraft. The logic is straightforward: GPS computes location, ADS-B transmits it, and everyone downstream builds a traffic picture from those transmissions.
There is no independent verification step between the GPS output and the ADS-B broadcast. No cross-check against primary radar. No cryptographic signature that would allow a ground station or another aircraft to confirm the position data originated from real satellites rather than a ground-based transmitter.
When a spoofing device floods the GNSS frequencies with fabricated but internally coherent signals, the aircraft’s GPS receiver sees what looks like a healthy constellation. The timing relationships are coherent. The signal geometry passes inspection. The receiver computes a confident position fix and passes it downstream - to the FMS, to TCAS, and to the ADS-B transponder broadcasting that position to every receiver in range.
Why Spoofing Is More Dangerous Than Jamming
Jamming and spoofing are related but fundamentally different threats. A jammer floods GNSS frequencies with noise, causing a no-fix condition. Receiver Autonomous Integrity Monitoring (RAIM) alerts fire. The system knows it’s broken, tells the crew, and crews fall back to DME crosshairs, inertial reference, or ATC vectors. Jamming is an honest failure.
Spoofing doesn’t block the signal. It replaces it. A well-executed spoof feeds the receiver a fake but coherent constellation - RAIM may not fire at all, because RAIM was designed to detect inconsistencies in satellite geometry, not a sophisticated fake that mimics one. The position quietly migrates to somewhere wrong, and the system presents it with full confidence.
The crew has no flag. The FMS has no flag. The ADS-B transponder broadcasts the false location to everyone.
What Pilots and Controllers Are Experiencing in Affected Airspace
The International Civil Aviation Organization (ICAO) and the Federal Aviation Administration (FAA) began issuing substantive safety advisories on GPS interference around 2022. Those advisories have been updated repeatedly. The highest-risk areas are airspace over northern Iraq, Iran, eastern Turkey, and the Eastern Mediterranean. The Baltic region is a separate but related problem, with interference traceable to activity near the Russian border affecting airspace over Finland, Estonia, Latvia, and Poland.
Pilots report their Flight Management Systems acquiring a new position mid-cruise that places the aircraft on the surface of an airport - sometimes Baghdad International - while actually cruising at Flight Level 380. Sometimes the displayed position is inside restricted airspace the crew never cleared into. FMS disagreement alerts populate. TCAS attempts to reconcile what it sees with what should be there.
The aircraft itself is completely normal. The avionics are functioning exactly as designed. The inputs are corrupt.
The Inertial Reference System as Ground Truth
The Inertial Reference System (IRS) is the critical cross-check. Unlike GPS, the IRS measures position by tracking acceleration mathematically - it has no dependency on radio signals of any kind. In a spoofing scenario, the IRS and GPS will disagree.
On a segment of normal duration, IRS position is far more trustworthy than a GPS showing full confidence. The IRS does drift over very long flights, but on a two-hour or three-hour segment, a discrepancy of dozens or hundreds of miles between IRS and GPS is a clear signal that the GPS picture is wrong. On aircraft with glass cockpits and inertial reference capability, most FMSes display both sources simultaneously - periodically comparing them in high-risk regions is sound airmanship.
If the GPS position starts behaving unexpectedly, trust the IRS first. Then DME crosshairs if available. Then terrain and visual references if in visual conditions.
The Controller’s Perspective: When ADS-B and Radar Disagree
An experienced en-route controller with good sector situational awareness may notice that a primary radar return - which depends on transponder interrogation but not on GPS - places an aircraft at a different location than the ADS-B tag. In regions with primary radar coverage, controllers have learned to treat this discrepancy as a spoof indicator and use the radar return as ground truth. Some operators have established specific protocols for this scenario.
The problem is coverage. Over oceanic routes, there is no primary radar. The surveillance picture is built entirely from ADS-B data. Aireon’s space-based ADS-B system, which places receivers on the Iridium satellite constellation and extended tracking to oceanic routes that previously had none, was a genuine advancement in global surveillance. But if an aircraft’s GPS has been spoofed before it crosses into oceanic airspace, the false position is what Aireon receives - and what oceanic controllers see.
TCAS and the Uncharacterized Edge Cases
TCAS version 2 uses ADS-B as one of its traffic inputs, with resolution advisory logic based on time to closest approach derived from surveillance data. In most practical spoofing scenarios - where an aircraft appears to jump to a ground location - a resolution advisory probably doesn’t fire, because TCAS doesn’t perceive a collision threat from something it classifies as static.
But the broader traffic picture degrades. Spoofed aircraft appearing in wrong locations affect the deconfliction logic for nearby traffic. The edge cases here are not fully characterized, and that lack of characterization is itself a documented concern for safety researchers.
What Pilots Should Do Before and During Flight in Affected Regions
Before departure: Check current NOTAMs specifically for GNSS anomalies in the affected regions. The FAA publishes a list of geographic areas with documented GPS interference risk. The OPSGROUP aviation safety organization has been cataloguing spoofing incidents in significant detail; their briefings are worth consulting for operators flying the Middle East or Baltic regions.
In flight: Cross-check IRS position against GPS position periodically. Any disagreement larger than a few miles in a spoofing-prone environment warrants investigation. Do not assume full GPS confidence means accurate GPS position.
If position behaves unexpectedly: Treat it as a GPS integrity event. Use IRS, DME, and charts as primary references. Declare the situation to ATC so controllers can apply primary radar as ground truth if available.
For general aviation pilots, the current hot zones are geographically concentrated in politically active regions. North American and Western European airspace is not facing the same intensity of spoofing activity as the Eastern Mediterranean. But the vulnerability is structural - it exists in every ADS-B system tied to GPS, everywhere, and the exposure level varies while the underlying architecture does not.
The Fixes in Development - and Why They Take Time
The near-term fix with the most traction is multi-constellation cross-checking. Modern GNSS receivers that simultaneously track GPS (United States), GLONASS (Russia), Galileo (Europe), and BeiDou (China) are substantially harder to spoof coherently. Fabricating four independent satellite systems simultaneously - each with its own frequencies, timing, and orbital geometry - raises the cost and complexity of a spoofing operation dramatically. Aviation receivers with true multi-constellation capability offer meaningfully better integrity.
The longer-term fix is cryptographic authentication. The European Galileo system has already implemented a feature called Open Service Navigation Message Authentication (OSNMA), which allows receivers to verify that signals genuinely originated from satellites rather than a ground transmitter. The American GPS system has committed to similar authentication features in future satellite blocks. This is the architectural solution - but constellation upgrade cycles measure in decades, and receiver hardware across the global aviation fleet would need to follow.
There is also active research into fusing ADS-B position data with independent verification at the ground station level - correlating ADS-B reports against primary radar, multilateration data, and signal timing cross-checks to flag aircraft whose broadcasts appear inconsistent with what other systems observe. This is architecturally complex and requires changes to ground infrastructure, but it directly addresses the root problem: the current system has no mechanism to catch a corrupted input.
The Architecture Problem That Predates the Threat
ADS-B does exactly what it was designed to do. It takes a GPS position and broadcasts it accurately. The design assumption baked in from the beginning was that GPS is a reliable input - and when the ADS-B mandate was developed and implemented, operational-scale spoofing in certificated airspace was a theoretical concern documented in academic papers, not a practical threat.
That environment no longer exists. The assumption is no longer universally true.
A transponder fed false GPS data isn’t malfunctioning. It’s functioning correctly with corrupted data. That’s a harder engineering problem than a system that simply fails - and it’s the problem the aviation industry is now actively working to solve.
Key Takeaways
- GPS spoofing replaces legitimate satellite signals with fabricated ones; RAIM may not alert, and ADS-B broadcasts the false position to ATC and other aircraft with no warning
- The highest-risk regions as of current FAA and ICAO advisories are northern Iraq, Iran, eastern Turkey, the Eastern Mediterranean, and the Baltic region near the Russian border
- The Inertial Reference System (IRS) is the reliable cross-check - a multi-mile disagreement between IRS and GPS in a spoofing-prone region means the GPS picture is wrong
- True multi-constellation GNSS receivers (GPS + GLONASS + Galileo + BeiDou) are significantly harder to spoof than single-constellation receivers
- Cryptographic signal authentication - already implemented in Galileo’s OSNMA - is the long-term architectural fix, but full aviation fleet adoption will take years
Radio Hangar. Aviation talk, built by pilots. Listen live | More articles