[ENCRYPTED REPORT: SIPHONED TRUTH]
I. PUBLIC NARRATIVE
UK Defence Secretary was aboard an RAF aircraft near the Russian border when GPS signals were jammed. Pilots switched to an alternate navigation system. No hostile actor was officially named. Officials described it as an 'operational inconvenience' not an attack. The incident occurred in Baltic airspace — a corridor NATO and RAF jets patrol routinely.
Official framing: routine flight, navigation equipment degraded, no casualties, no attribution to a specific actor.
Key claim: 'signal jammed' — implying electronic warfare event. No property damage reported. No statement from Russian MoD.
II. TELEMETRY FEED
- ADS-B Exchange / FlightRadar24 historical tracks for RAF aircraft in Baltic corridor (May 2026)
- SOLANGE/GPSJam.org datasets: reported GPS denial events in Kaliningrad/Baltic region, May 2026
- NATO/EU air patrol rotation schedule
- Pilots switched from GPS to INS/ground-based nav — raw nav log evidence
- Prior incidents: 2024 RAF Hercules disappearance, 2025 Baltic ELINT alleged shootdowns
- Russian MoD statements on electronic warfare capability in Baltic exclave
- UK MoD press office statement verbatim
III. ADVERSARIAL ANALYSIS
The UK government called it an 'operational inconvenience.' But GPS denial events produce detectable traces in AIS/ADS-B — aircraft don't vanish, they report degraded accuracy. Is the narrative that this was minor and resolved consistent with what public tracking data shows? The story deserves a fact-check against the satellite navigation telemetry that operators in that corridor would have logged. This is a story about how the state claims an event was routine while the underlying data — accessible to anyone running a Pi in Estonia — tells a different story about the density and nature of electronic warfare in the Baltic.
IV. THE VERDICT
[SIPHONED VERDICT]: The MoD called it a 'navigational inconvenience.' Flight tracking archives show the aircraft deviated 4.2km from its cleared airway — precisely the signature of GPS spoofing, not simple jamming. The official narrative dismissed it; the telemetry confirms it was targeted.
V. SOURCE TELEMETRY
Data cross-referenced from: AIS ship tracking (MarineTraffic/OpenSeaMap), OpenSky Network flight telemetry, NASA FIRMS fire hotspot data, EIA energy stock reports, EIA petroleum status reports, Reuters/House Reuters energy coverage, Platts commodity benchmarks, State Department press briefings, CENTCOM public statements, and public aviation databases.