GNSS Observatory

Independent, reproducible monitoring of GNSS interference affecting civil aviation.

Satellite navigation signals reach an aircraft receiver extremely weak — roughly the power of a car headlight seen from twenty thousand kilometres away. They are correspondingly easy to disrupt.

Episodes of degraded satellite navigation affecting commercial aviation over parts of Europe have been reported publicly by airlines, aviation authorities and the trade press. Individual accounts exist. What does not is a continuous, independent, reproducible record of where and when aircraft reported degraded navigation integrity — one built to survive being challenged, and held by someone with no stake in the answer.

GNSS Observatory is being built to be that record.

How it works

Aircraft broadcast their position continuously over ADS-B, derived from onboard GNSS receivers. Those broadcasts also carry navigation integrity fields — the receiver's own assessment of how far its reported position can be trusted.

When reception degrades, that self-assessment falls, and the aircraft broadcasts the degradation to anyone listening. The effect publishes its own evidence. We read those public broadcasts and look for populations of aircraft whose navigation integrity falls together, in the same airspace, at the same time — then record the result in a form that can be re-derived and audited later.

What is being built

Public map

A free, openly accessible view of where aircraft have reported degraded navigation integrity.

Open to anyone

Incident documentation

Detailed records of individual episodes — airspace, time bounds, the underlying evidence, and the exact software version that produced them.

Airlines · insurers · legal · regulators

Data access

A programmatic interface and monitoring notifications, for organisations that need this inside their own systems.

Operations · routing · analytics platforms

Status

A feasibility audit against a full day of real archive data in August 2026 established that the integrity fields the primary method depends on are present at usable density: a median interval of 17 seconds between integrity reports per aircraft, with the relevant field populated on every sample. On an ordinary day, about 5% of reports carry no integrity value — the background rate any real finding has to rise above.

That establishes the data can support the method. It says nothing yet about how well the method works. No findings are published on this site, and none will be until they have been evaluated both against independently documented events and against control airspace where none were reported.

Get in touch

If this would be useful to you, get in touch — and tell us what you would use it for, and what it would replace. That second question is the one that shapes what gets built first.

Most directly relevant to those carrying the consequences: aviation and specialty insurers, underwriters and claims teams, operators assessing route risk, accident and incident investigators, and air navigation service providers. Also to journalists covering the subject.

[email protected]

Method and principles

These are design rules rather than aspirations. They exist because the failure modes are worse than the missed detections — and because they are what allows a finding to survive being challenged.

Coverage

Region
Baltic — 53.5°N to 66.0°N, 9.0°E to 30.0°E
Resolution
15-minute windows over a hexagonal spatial grid
Cadence
Daily batch processing of published archives. Nothing is real-time
Expansion
Further regions only after the method is validated in this one

Data and licensing

Source
Publicly released daily archives of aircraft transponder broadcasts, from the adsb.lol community project
Licence
Used under the upstream project's published terms (ODbL 1.0 and CC0), with attribution
Collection
No radio equipment is operated. Only archives already published by others are processed