kimo
Case file // regional-airspace-monitoring
Regional aviation-safety team · Europe
Defense IntelligenceCivil aviation safety · Public sector

A regional aviation-safety team mapped GNSS interference from open ADS-B data.

A regional aviation-safety team learned about GNSS interference from pilot reports, often days after the fact. By scoring the navigation-accuracy fields that aircraft already broadcast in ADS-B, Kimo now maps degraded areas hour by hour, and a safety notice goes out within about six hours of the first degraded reports.

from first degraded reports to a safety noticedown from about 3 days
6 h
position reports scored per day
2.4M
of flagged cells corroborated by crew reports
84%
raw aircraft tracks stored outside the team
0
[01]Challenge

Interference reports that arrived days after the fact

The team supports civil aviation safety for a European region with several busy airports and a long stretch of coastline. Its job is to spot hazards early, inform airlines and air navigation service providers, and feed the regional safety picture. EASA has reported a notable increase in GNSS jamming and spoofing since February 2022, particularly around conflict zones and other sensitive areas, and the region had started to see it too (see references).

The evidence arrived slowly and unevenly. Crews filed reports after landing, some airlines shared them quickly and others did not, and the team had no consistent way to tell whether three reports on Tuesday were a single faulty receiver or a whole sector of degraded positioning. Building a picture for one event took about three days of analyst time.

The data to do better already existed. Aircraft equipped with ADS-B broadcast their position along with quality indicators: the navigation accuracy category (NACp) estimates position uncertainty, and the navigation integrity category (NIC) gives a containment radius. When either drops to zero, the position uncertainty is far higher than typical GNSS performance, which suggests significant interference (see references). The team had its own ground receivers and access to an open, crowdsourced ADS-B network, but no way to turn millions of messages into a map someone could act on.

> We stopped waiting for crew reports to tell us something was wrong. The aircraft were already telling us; we just were not listening at scale.
Head of Safety Analysis
Regional aviation-safety team · Europe
[02]Solution

How the aviation-safety team set up Kimo

Kimo Bridge was installed next to the team’s receiver archive, a Postgres database fed by its ground stations. Kimo queries the archive through the bridge and receives only aggregates, so raw tracks never leave the team’s servers. Open ADS-B data and a base map of sectors and airports were connected alongside it.

The model aggregates position reports into a fixed grid and, for each cell and hour, computes the share of distinct aircraft reporting degraded NIC or NACp. A cell is flagged only when several aircraft from different operators are affected at the same time, which filters out single-avionics faults. Each flag shows the evidence: aircraft count, the distribution of accuracy values, altitude bands and the trend over the previous 24 hours.

The output is deliberately civil and descriptive. Analysts see where positioning was degraded, when and for how many aircraft; they do not attempt to locate or characterize emitters, which is a matter for the competent authorities. A templated safety notice is drafted from each confirmed event and reviewed by a duty analyst before it goes to airlines and service providers.

  1. Week 101/03
    Bridge and feeds

    Kimo Bridge beside the receiver archive; open ADS-B data and sector maps connected.

  2. Week 302/03
    Integrity model

    Hourly grid of degraded NIC/NACp shares, with multi-aircraft corroboration rules.

  3. Week 403/03
    First published map

    Confirmed events drafted into safety notices and shared with operators.

Operational picture

Aviation-safety team: Regional GNSS integrity

A recreation with fictional data. Hover the chart for values.

KIMO//DI
Regional aviation-safety team · Europe · Regional GNSS integrity
Aircraft observed (24h)
4,318
Cells flagged
7
+3
Notices drafted
2
Raw tracks exported
0
Aircraft reporting degraded NIC/NACp
Share of aircraft per sector, daily (simulated)
Sector North
Sector Coast
Sector South
Flagged cells · last 24h (simulated)
CellAircraftDegradedAltitude bandStatus
C-146218%FL250–FL390Notice drafted
C-154811%FL180–FL350Review
N-03376%Below FL100Watch
S-21292%AllNormal
> ask kimo: cells where >5% of aircraft reported degraded NIC today
Mock dashboard for Regional aviation-safety team · Europe (fictional data): Regional GNSS integrity
Outcome
from first degraded reports to a safety notice
6 h
position reports scored per day
2.4M
of flagged cells corroborated by crew reports
84%
raw aircraft tracks stored outside the team
0
[03]Results

6 h from interference to published notice.

The time from the first degraded reports to a reviewed safety notice fell from about three days to roughly six hours. In the first quarter, 84% of the cells the model flagged were later corroborated by at least one crew report, and several events were identified before any crew report arrived.

The hourly maps also changed the conversation with airlines. Instead of anecdotes, the team now shares a weekly summary of affected sectors, altitude bands and durations, which operators use to brief crews. All aircraft data shown on this page is simulated, and all figures are illustrative.

Regional aviation-safety team · Europe: before and after Kimo
MetricBefore KimoWith Kimo
Picture of one event≈ 3 analyst-days≈ 6 hours
EvidenceCrew reports onlyEvery ADS-B equipped aircraft
Single-receiver false alarmsHard to rule outFiltered by corroboration
Raw tracks leaving the teamn/aNone (Bridge)
> The corroboration rule is what made the maps credible. One aircraft is an anecdote; twelve aircraft from five operators is an event.
Duty Analyst
Regional aviation-safety team · Europe

References

The customer story is anonymized and illustrative. The industry facts it mentions come from these public sources.

  1. Global navigation satellite system outages and alterations · EASANotes a notable increase in GNSS jamming and spoofing since February 2022 and links SIB 2022-02.
  2. Locating GNSS Interference Sources using ADS-B with Non-linear Least Squares (Liu et al.) · NAVIGATION, Journal of the Institute of Navigation, 2025Defines NACp and NIC; a value of 0 for either suggests significant interference.
[04]Stack

From 5 sources to one answer.

Sources
  • ADS-B Air Traffic
  • OpenSky Network
  • Kimo Bridge
  • PostgreSQL
  • OpenStreetMap
Kimo models
  • ADS-B integrity grid
  • Event corroboration
  • Safety notices
Semantic layer · one definition per metric
Dashboards
  • Regional GNSS integrity
  • Event review
  • Weekly operator summary
Next step // Briefing

Request a sovereign deployment briefing.

Walk through on-premise and air-gapped deployment, accreditation support and the simulated operations picture.