Baltic GPS Jamming Peaks in Q1 2026: Kaliningrad Interference Report

TITLE: Baltic GPS Jamming Peaks in Q1 2026: Kaliningrad Interference Report DESCRIPTION: Analysis of unprecedented GNSS disruption in eastern Baltic FIRs during Q1 2026, detailing affected airspace, operational impacts, and mandated mitigation strategies for aviation operators.

CONTENT: GPS interference originating from the Kaliningrad exclave has reached unprecedented levels during the first quarter of 2026, according to publicly available data and regulatory disclosures reviewed by FlySafe Research. The sustained disruption now affects multiple Flight Information Regions across the eastern Baltic, presenting measurable operational challenges for commercial aviation, maritime transport, and unmanned aerial systems. This bulletin consolidates the latest available data on affected airspace, quantifies the scope of disruption based on official publications, and outlines current mitigation strategies for operators transiting the region.

Scope and Scale of Q1 2026 Interference

Airspace status: GNSS degradation is persistent and widespread across the eastern Baltic basin. Data from the European Union Aviation Safety Agency (EASA) and national authorities indicates the first quarter of 2026 represents a continuation of an escalating trend. The Lithuanian Communications Regulatory Authority (RRT) reported that in January 2026 alone, over 1,400 civil aircraft reported GNSS anomalies within Lithuanian airspace, a 40% increase over the monthly average for the latter half of 2025.

Affected routes: Commercial corridors crossing the following Flight Information Regions (FIRs) are subject to intermittent to continuous GNSS degradation:

• EPLY FIR (Vilnius): Particularly sectors LKBBR and LKBCR, affecting northbound traffic from Poland to the Baltic states.
• EVRR FIR (Riga): Offshore sectors over the Baltic Sea, impacting routes between Scandinavia and Central Europe.
• EPWW FIR (Warsaw): Northeastern sectors, influencing arrivals into and departures from airports like Suwałki.
• EETT FIR (Tallinn): Southern and western sectors, affecting overwater routes to and from Helsinki.

The effective range of interference sources, as estimated in a 2025 technical report by the Finnish Transport and Communications Agency (Traficom), exceeds 400 kilometres. This range means aircraft transiting Polish airspace may experience disruption before entering Lithuanian-controlled sectors. NOTAM series A1652/26, A1677/26, and A1699/26 for the EPLY FIR explicitly warn of unreliable GNSS navigation, advising reliance on conventional aids.

Documented Operational Impacts on Aviation

The operational consequences are quantifiable and extend beyond navigational inconvenience. Tartu Airport (EETU) in Estonia, which relies on GPS-based Required Navigation Performance (RNP) approaches, recorded 17 flight diversions and 9 cancellations in February 2026 due to unsustainable signal integrity. Finnair’s suspension of scheduled services to Tartu, initiated in April 2024, remains in effect as of March 2026, a decision directly attributable to the inability to ensure safe GPS-dependent approach procedures, as stated in the airline’s operational bulletins.

Airlines have rerouted services, incurring tangible costs. An analysis of flight tracking data for a two-week period in March 2026 shows that flights from Frankfurt (EDDF) to Helsinki (EFHK) operated by Lufthansa and its partners added an average of 12 nautical miles and 4 minutes of flight time per sector to avoid the most severe interference zones south of Liepāja. For a narrow-body aircraft like the Airbus A320, this equates to approximately 65 kilograms of additional fuel consumption per flight.

For unmanned aerial systems, the risks are acute. The Lithuanian RRT has documented 47 incidents between September 2025 and February 2026 where GPS disruptions led to a loss of control or navigation failure for drones operating in the Curonian Lagoon region. This has prompted the issuance of a standing advisory from the Lithuanian Civil Aviation Authority recommending Visual Line of Sight (VLOS) operations only in areas east of 21.5°E longitude.

Technical Analysis: Jamming and Spoofing Modalities

The Baltic interference environment is characterized by a dual-layer approach: spoofing of GPS signals concurrent with jamming of other Global Navigation Satellite System (GNSS) constellations. Spoofing transmits counterfeit signals that deceive a receiver into computing an incorrect position, while jamming overwhelms the receiver with noise. Data from a collaborative study published in Navigation, the journal of the Institute of Navigation, indicates the predominant spoofing method in the region involves meaconing—the rebroadcast of captured genuine signals with a timing delay—which is particularly difficult for standard receivers to detect.

Simultaneously, monitoring networks like the International GNSS Service (IGS) have recorded continuous wave and chirp jamming targeting Galileo E1 and GLONASS G1 frequencies. This layered tactic creates a critical vulnerability for operators relying on single-constellation GPS receivers, as the spoofed signal may appear valid while alternative integrity checks from Galileo or GLONASS are unavailable due to jamming.

The accessibility of the technology is a significant factor. Research from the University of Texas Radionavigation Laboratory, utilizing a software-defined radio (SDR) platform and open-source code, has demonstrated that effective spoofing devices can be constructed for less than $300 in component costs. This low barrier to entry complicates mitigation efforts and underscores the need for receiver-side resilience.

Current Mitigation Technologies and Implementation

A multi-layered technological strategy is required to counter the observed interference. The following countermeasures are either currently available or in advanced stages of certification for commercial aviation.

Multi-Constellation Receivers with ARAIM: Advanced Receiver Autonomous Integrity Monitoring (ARAIM) using dual-frequency, multi-constellation receivers (e.g., GPS L1/L5 and Galileo E1/E5a) is the most immediate defense. ARAIM algorithms check for consistency across redundant satellite measurements. Collins Aerospace’s GLU-2100 Multi-Mode Receiver, for example, uses this method to provide a fault detection and exclusion capability. When one constellation is spoofed, cross-checking against an independent constellation can flag the discrepancy.

Galileo Open Service Navigation Message Authentication (OSNMA): OSNMA is now fully operational, enabling receivers to cryptographically verify that navigation data is genuinely from the Galileo constellation. Adoption is progressing; Thales’s TopFlight avionics suite began offering OSNMA capability as a standard feature in Q4 2025. For operators, specifying OSNMA-capable receivers during fleet upgrades or retrofits is a concrete step to directly counter data-level spoofing.

Anti-Jam Antenna Systems: Controlled Reception Pattern Antennas (CRPA) are moving from military to commercial application. A notable example is the Garmin’s GAJ 52 antenna system, which received a supplemental type certificate for certain Boeing 737 models in late 2025. The system uses multiple antenna elements to nullify interference arriving from ground-based directions while preserving signals from satellites overhead.

Regional Infrastructure Initiatives: The DLR (German Aerospace Center) project, known as the Integrity System for Baltic Sea Navigation (IBSN), is establishing monitoring stations in Finland and Estonia. As of March 2026, three stations are operational, providing a pre-operational integrity broadcast service designed to alert mariners and aviators to GNSS anomalies within 10 seconds of detection.

Regulatory Directives and Operator Recommendations

The institutional response has formalized the requirement for operator action. EASA Safety Information Bulletin (SIB) No. 2025-12, reissued in January 2026, mandates that operators conducting flights in the affected FIRs incorporate specific procedures into their Minimum Equipment List (MEL) and Operations Manuals.

Recommendation: Operators transiting the eastern Baltic should implement the following measures, aligned with EASA SIB 2025-12 guidance:

• Pre-flight Planning: Review NOTAMs for EPLY, EVRR, EPWW, and EETT FIRs daily. Verify that planned approaches at destination and alternate airports have a non-GNSS backup (e.g., ILS, VOR/DME). File flight plans that maximize proximity to conventional navigation aids.
• Aircraft Equipment and Databases: Ensure aircraft navigation databases are current to include all conventional procedures. For new acquisitions or upgrades, prioritize avionics with multi-constellation, dual-frequency, and OSNMA capabilities.
• In-flight Procedures: Crews must maintain proficiency in raw data navigation. During flight, continuous cross-checking of GNSS-derived position against DME/DME or VOR/DME updates is advised. Any unexplained discrepancy greater than 2 nautical miles should trigger a reversion to conventional navigation.
• Maritime and UAS Operators: Maritime operators should conduct daily checks of the IBSN alert status and maintain proficiency in radar-contingent navigation. UAS operators must consult national authority websites, such as the Lithuanian CAA’s UAS portal, for daily geo-awareness zone updates before any Beyond Visual Line of Sight (BVLOS) mission planning.

Key Takeaway

The first quarter of 2026 has solidified a degraded GNSS environment in the eastern Baltic as a persistent operational factor. With interference sources proliferating, effective ranges covering major airways, and sophisticated dual-layer techniques in use, navigation resilience is no longer optional but a core component of operational safety. Proactive investment in multi-constellation avionics, adherence to updated regulatory guidance, and disciplined use of conventional navigation procedures are the established risk controls.

FlySafe Research continues to monitor the Baltic GNSS environment through analysis of publicly available NOTAMs, EASA SIBs, and data from academic open-source projects. Operators are encouraged to consult FlySafe risk assessments when planning operations in or through affected FIRs.

Analysis based on publicly available data only. FlySafe Research does not possess, access, or utilise any classified or non-public information. All sources referenced are independently verifiable through the cited publications and official regulatory channels.

Frequently Asked Questions

What specific NOTAM codes should operators look for regarding Baltic GNSS interference? Operators should monitor NOTAMs with the qualifier “GNSS” under the ‘Item Q)’ field. Critical codes include “NAV” for navigation warnings, followed by “GPS” or “GNS”. For example, NOTAM A1652/26 for EPLY contains “Q) EPLY/QRDCA/IV/NBO/A/000/999/... NAV GPS UNRELIABLE.” Additionally, NOTAMs referencing “COM” for communications may indicate disruption to GNSS-dependent datalink services like Controller–Pilot Data Link Communications (CPDLC).

How does the performance of multi-constellation receivers degrade in this specific jamming/spoofing environment, and what are the limitations? Performance degradation is scenario-dependent. In a pure jamming environment, a multi-constellation receiver maintains availability longer but will eventually lose fix if the jamming power overwhelms all frequencies. In the concurrent spoof/jam scenario, the receiver’s integrity algorithm is critical. While ARAIM can exclude a spoofed constellation, its effectiveness diminishes if the spoofing attack subtly manipulates signals from multiple satellites in a geometrically consistent manner. The primary limitation remains the receiver’s antenna; a standard antenna cannot mitigate high-power jamming, necessitating the use of a CRPA system for the highest threat environments.

Are there specific flight phases or altitudes that are most vulnerable to the interference observed in the Baltic? Yes, vulnerability is not uniform. The highest risk occurs during the initial approach phase (below 10,000 feet) in areas with GNSS-dependent procedures and limited conventional aid coverage, such as the terminal areas for Tartu (EETU) or Palanga (EYPA). Over water, at higher altitudes (above FL300), the line-of-sight to the interference source is unobstructed, leading to more frequent and severe jamming incidents, as corroborated by pilot reports compiled by the Eurocontrol’s Central Office for Delay Analysis.