GNSS radio frequency interference (RFI) and spoofing have become a persistent, if less headline-grabbing, feature of the operational landscape for crews flying through conflict-adjacent airspace. The surge in reporting during 2023-2024 tracked closely with the intensification of jamming and spoofing activity linked to the wars in Ukraine and the Middle East, particularly around the eastern Mediterranean, the Baltic states, the Black Sea region, Cyprus, and areas near the Iran-Iraq border and the Persian Gulf. Organizations like OPSGROUP, EUROCONTROL, and the FAA issued repeated advisories and NOTAMs during that period documenting spikes in GPS position errors, false terrain warnings, ADS-B corruption, and in some cases aircraft clocks jumping decades into the future or past due to corrupted timing signals. The relative quiet in mainstream coverage since then likely reflects a combination of normalization—crews and dispatchers have adapted procedures—and the fact that ongoing regional conflicts have become a fixture of the news cycle rather than a novel story, not necessarily that the underlying interference has meaningfully diminished.
For working pilots, this is not an abstract IT problem but an operational hazard with direct implications for navigation, terrain awareness, and traffic separation. Spoofing is particularly insidious compared to simple jamming because affected avionics may report a false but plausible position with high confidence, rather than flagging an obvious loss of signal. This has led to documented cases of aircraft receiving spurious GPWS/TAWS terrain alerts in level cruise flight, RNAV approaches becoming unreliable, and ADS-B Out broadcasting incorrect positions that confuse ATC and TCAS logic in nearby traffic. Airlines operating through the Eastern Mediterranean, Iraq, Iran, and parts of the Baltic and Black Sea FIRs have adjusted procedures accordingly: briefing crews on expected RFI zones, emphasizing reversion to conventional and inertial navigation, cross-checking FMS position against raw VOR/DME or ILS data, and in some cases avoiding GPS-dependent approaches or specific airspace segments entirely. Many operators now include GNSS interference as a standard briefing item for international ops, similar to how volcanic ash or high-threat overflight risk is handled.
The trend connects to a broader shift in how the industry views satellite navigation resilience. For roughly two decades, aviation steadily migrated toward GPS/GNSS as the primary means of navigation, with performance-based navigation (PBN), RNP approaches, and ADS-B surveillance all built on the assumption of a trustworthy satellite signal. The interference wave of the past few years has forced a partial rethink, reviving interest in maintaining proficiency with conventional navaids, inertial reference systems, and multi-sensor position blending that can detect and reject spoofed inputs. Avionics manufacturers have also accelerated work on GNSS anti-spoofing algorithms and receiver autonomous integrity monitoring (RAIM) improvements, while regulators have discussed longer-term backstops like enhanced Loran (eLoran) as a non-satellite alternative for critical infrastructure, including aviation.
Whether ATPs remain concerned likely depends heavily on route structure. Pilots flying purely domestic U.S. or intra-continental routes may see little practical GNSS interference and could reasonably perceive the issue as having faded, while those flying international long-haul or business jet trips through the Middle East, Eastern Europe, or parts of Asia continue to encounter it routinely and treat it as a normal, briefed risk rather than an emergency. The lack of recent mainstream coverage says more about media fatigue with an ongoing conflict-driven phenomenon than about the interference itself disappearing; incident-reporting databases and NOTAM traffic from EUROCONTROL and regional FIRs continued to show elevated GNSS anomaly counts well into 2025. For crews and dispatchers, the practical takeaway is that GNSS RFI has shifted from an emerging anomaly to a known, manageable operational risk factor—one requiring continued vigilance, current NOTAM review, and maintained proficiency in non-GPS navigation techniques rather than an assumption that the problem has resolved itself.