Skip to content

GNSS integrity from ADS-B

See where GPS-integrity drops are observed, and which aircraft it affects.

We measure GPS-integrity drops in the ADS-B messages aircraft broadcast, map them on hexagonal cells and show the aircraft behind every cell. Where there is no data, that is not «no interference».

  • Free, no sign-up
  • Source: adsb.lol (ODbL)
  • Our own method

Indicative · based on ADS-B integrity (NIC) data

Reading data window…

Latest measured day

2026-10-20
  • Insufficient data · 43
  • Low · 158
  • Medium · 29
  • High · 51

Cell levels. Türkiye and neighbours (static export region).

35
medium/high-level events
4.1%
of aircraft-hours affected
23,145
aircraft-hours observed

Decorative animation: the signals and names on the globe are randomly generated, not measurements. Real data is in the cards below.

Built on openly licensed data and open standards

  • adsb.lol (ODbL)
  • Uber H3
  • EUROCONTROL FIR
  • OurAirports
  • OpenFreeMap
  • MapLibre GL

01 — 2026-10-20

The latest data, at a glance

Every chart below comes from the newest published day. Nothing on this page is sample data. Coverage depends on where receivers are: an unseen region does not mean «no problem», and a change does not tell its cause.

Share of aircraft-hours affected

Last 30 days, daily. Affected aircraft-hours / observed aircraft-hours; Türkiye and neighbours.

0%2.5%5%4.1%09-2110-0510-202026-09-21 · 3.07% · 23,8992026-09-22 · 2.74% · 24,8862026-09-23 · 3.51% · 25,7542026-09-24 · 3.17% · 25,7832026-09-25 · 2.88% · 25,9152026-09-26 · 3.16% · 26,9602026-09-27 · 3.37% · 27,0062026-09-28 · 2.6% · 25,5512026-09-29 · 2.86% · 24,9432026-09-30 · 3.38% · 25,4212026-10-01 · 2.87% · 25,5842026-10-02 · 3.1% · 25,6572026-10-03 · 3.43% · 26,3502026-10-04 · 3.05% · 26,1112026-10-05 · 3.05% · 24,4852026-10-06 · 3.76% · 23,8472026-10-07 · 4.35% · 24,6712026-10-08 · 3.44% · 25,0332026-10-09 · 3.42% · 25,0832026-10-10 · 4.38% · 26,0902026-10-11 · 3.95% · 25,9312026-10-12 · 3.64% · 24,2502026-10-13 · 3.8% · 23,7072026-10-14 · 3.49% · 24,4692026-10-15 · 3.97% · 25,5152026-10-16 · 4.06% · 24,4692026-10-17 · 3.43% · 25,8532026-10-18 · 3.57% · 26,2982026-10-19 · 3.06% · 24,3772026-10-20 · 4.07% · 23,145
Days before 4 Oct 2026 may include unfiltered records from faulty devices.

Largest events of the day

On the latest measured day, by aircraft affected; medium and high level events.

Week comparison

difference −0.2 points · small difference

  • Last 7 days3.7%
  • previous 7 days3.9%

An observed change; it does not say why, or whether coverage changed.

Affected share by hour

Latest measured day, UTC hour. Each bar is the share of aircraft affected in that hour.

0%12%00:00 UTC · 9.7% · 44/45401:00 UTC · 8.7% · 39/44802:00 UTC · 10.2% · 51/49903:00 UTC · 6.6% · 42/63904:00 UTC · 3.4% · 27/79805:00 UTC · 4% · 38/95506:00 UTC · 3.5% · 34/97207:00 UTC · 2.6% · 27/103808:00 UTC · 2.8% · 34/120209:00 UTC · 3.7% · 47/126210:00 UTC · 2.4% · 31/130611:00 UTC · 2.2% · 29/131812:00 UTC · 3.9% · 53/134713:00 UTC · 3.3% · 45/136114:00 UTC · 3.7% · 50/133515:00 UTC · 3.9% · 50/127416:00 UTC · 5.4% · 64/118817:00 UTC · 5.5% · 57/103518:00 UTC · 3.2% · 33/102419:00 UTC · 2.1% · 20/97020:00 UTC · 3.2% · 27/83721:00 UTC · 3.8% · 27/70922:00 UTC · 4.7% · 29/61223:00 UTC · 8% · 45/56200061218

Route example: LTFM → LTAC

Cell levels along the shortest (great-circle) line; latest measured day.

Level
High
km
381
Measurable share of the line
100%

Data status and coverage →

Regions, last 7 days

Share of affected aircraft per region. Open a region for its daily trend, recent events and yearly history.

All regions →

Four tools, one measurement

01 — Map

See integrity drops cell by cell

The share of aircraft with a low NIC is aggregated hour by hour on H3 cells. Insufficient data and coverage gaps never look “clean”; they are marked separately.

Open the map →

02 — Explainability

The aircraft behind every colour

Click a cell: affected aircraft, lowest NIC, the hourly trend and observation sufficiency. A red cell is a measurement, not a claim.

How we calculate →

03 — Events

Integrity drops and positioning anomalies, one event schema

Drops in adjacent cells become events: a permanent page and RSS. An event does not say what caused it (jamming, spoofing or a fault).

See events →

04 — Route

Assess a route with two airports

Cell levels along the line, the measurable share and the last 30 days of history. Background information, not a flight-planning tool.

Try a route →

The same three steps under every tool

The map, events and reports all derive from the same hourly summaries. Every page reads the same published daily data.

01

Collect

Daily position messages from the open adsb.lol archive are processed; each carries the aircraft's GPS integrity (NIC).

02

Resolve

Messages are aggregated hourly on H3 cells, faulty avionics are dropped and cells are assessed statistically against a background rate.

03

Retain

Daily summaries are archived by date; past days are read the same way.

Daily
archive processing
Separate
insufficient data and coverage gaps
Labelled
observation sufficiency, in every cell

How is the level decided?

The level is computed from NIC only; NACp is a second signal. Colours match the map.

  • Insufficient data

    Very few aircraft in the cell. It does not mean “clean”.

  • Low

    Small affected share, or not significant against the background.

  • Medium

    Significantly above the background, moderate share.

  • High

    Significantly above the background, large share.

Start with your own region

Open your airport, route or FIR; the first measurement is one click away.

Your part of the sky, first.