Baltic GNSS: harm without an incident
Satellite navigation interference around the Baltic became persistent enough that Finnair suspended an entire route for a month, after two flights turned back mid-approach. Estonian controllers logged more than 600 pilot reports in April 2024 alone. The jammers, one of them said, run essentially all the time.
An RAF aircraft carrying the UK Defence Secretary was affected near Kaliningrad. There is no single incident here to investigate, which is precisely what makes it difficult.
↓ Download one-page brief (PDF)13 March 2024 - a ministerial aircraft
An RAF Falcon 900LX carrying the UK Defence Secretary is affected near Kaliningrad on an official trip to Poland, with interference reported on both legs of the journey and the aircraft using other means to determine its position.
25 and 26 April - two aborted approaches
Two Finnair flights from Helsinki abandon their approach to Tartu and return to Helsinki. Tartu lies around 40 km from the Russian border and its approach procedures depend on a satellite signal.
29 April - a route suspended
Finnair suspends daily flights to Tartu until 31 May so that an alternative approach not requiring a satellite signal can be installed. Finnair is the only airline operating international flights there.
The scale becomes visible
Estonian air navigation services report more than 600 pilot reports in April alone, with jammers operating essentially continuously. Tens of thousands of civilian flights are reported as affected over the preceding months.
2 June - service resumes
Flights resume once an alternative navigation method for the landing approach is in place. Estonia raises the issue with the EU and NATO; its foreign minister warns that the interference is dangerous enough that it will eventually cause a crash.
Nothing discrete to investigate
There is no crater, no vessel to board, no arrest to make. The harm is a degraded environment rather than an event, so the apparatus of investigation and prosecution has nothing to grip.
The threshold is never crossed
Flights divert, approaches are abandoned, routes are suspended. Nobody is hurt, so nothing compels the response that a single crash would.
The effect ignores the line
A transmitter inside one state degrades navigation across several others, so no single jurisdiction owns either the cause or the consequence.
This is the purest example of the pattern the rest of this library circles. Real harm, continuously delivered, with nothing to investigate and nobody to charge. The Warsaw-Lublin IED was calibrated to stay below the casualty threshold; this never approaches a threshold at all, because there is no moment at which it happens.
Attribution is asserted by the affected states and not formally resolved
Estonia, Finland and Germany have pointed to Russia and to specific areas, and Estonia's foreign minister said proof existed without making it public. Russia did not comment at the time. On the open record this is an attribution made by governments rather than one established by an independent process, and it should be reported as such.
The vulnerability is dependence, and it is nearly universal
Satellite positioning and timing underpin aviation approaches, maritime navigation, telecommunications synchronisation, financial timestamping and the electricity grid. Most organisations have no idea how many of their dependencies terminate at a satellite signal.
Redundancy is what actually resolved it
The route reopened when a ground-based approach procedure was installed at Tartu. The interference did not stop. The only control that worked was not needing the signal, and that is available to anyone willing to engineer it in advance.
Continuous degradation is harder to answer than a discrete attack
A single act produces evidence, a victim and an investigation. This produces a worse aggregate outcome and none of those things, which is why it has continued for years while individual incidents elsewhere have triggered NATO consultations.
Nothing here creates any pressure to stop
The interference has run for years, imposed real cost, and produced no consequence for whoever is responsible. There is no incident to investigate, no casualty to prosecute and no border to point at. It is almost certain that satellite navigation interference continues across these regions, and unlikely that it ends through attribution rather than through users engineering their way out of the dependency.
More than 600 pilot reports in a single month from one small country's air navigation service, and jammers described as operating essentially continuously. There is no incident here to report, which is exactly why it works.
- Find your satellite dependencies before you need to. Timing and positioning sit underneath far more systems than most registers record - synchronisation, logging, scheduling and access control among them.
- Engineer the fallback in advance. Tartu reopened because a ground-based approach was installed. Every dependency on a satellite signal should have an answer that does not involve one.
- Treat degradation as an operating condition, not an incident. Interference is persistent in these regions. Procedures, training and route planning should assume it rather than react to it.
- Report it even when nothing happens. The 600 reports in a month are what made the scale visible. Individually each was a nuisance; collectively they were the evidence.
- Extend the thinking to shipping and logistics. Maritime navigation is affected in the same areas, and supply chains crossing the Baltic, Black Sea and eastern Mediterranean carry the same exposure.
- Do not wait for attribution to be settled. It has not been resolved in several years of degradation, and resilience measures that wait for it will not be taken.
- https://therecord.media/baltic-countries-blame-russia-gps-jamming-airline-flights
- https://www.cbc.ca/1.7213538
- https://www.aerotime.aero/articles/finnair-suspends-flights-tartu-gps-jamming
- https://www.thenationalnews.com/news/europe/2024/04/30/finnair-suspends-flights-to-estonian-city-due-to-russian-gps-jamming/
Compiled from open-source reporting for professional security discussion. Attribution to Russia is made by the affected states and has not been established by any independent process; Russia did not comment on the accusations at the time. This is a protective-security lessons-learned assessment, not an operational account.