Skip to content

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

All events

Unknown region

Integrity drop2026-10-15 19:00Z – 20:00Z · 2 h

Scale
Small
Observation sufficiency
Medium
Aircraft affected
7

Low navigation integrity (NIC) in adjacent cells. It does not say what caused it.

Opens the event's day; you choose departure and arrival.

Evidence

Strongest moment (UTC)
19:00 · cell 852c934ffffffffOpen the strongest moment on the map
Aircraft affected that hour
4 / 21 aircraft
Scale basis
7 affected aircraft → Small event
Observation-sufficiency basis
33 aircraft observed, 7 affected.
Aircraft observed in hot hours
33 aircraft (21% affected)
Technical details
Hot cell-hours
5(hour, cell) pairs that make up the event
Cells
3
Data source
adsb.lol (ODbL)
Algorithm version
1.6.0

Hour by hour: before, event, after

Hourly view of the event day: the event hours plus a few hours before and after. Values are the hourly share of affected aircraft across the whole published region network, not of the event's own cells; do not read them as the event's size or cause.

16:00Z Before: 2.8%17:00Z Before: 2.8%18:00Z Before: 4.2%19:00Z Event: 2.9%20:00Z Event: 2.8%21:00Z After: 3.3%22:00Z After: 4.7%23:00Z After: 7.7%16182123▮ Event
Hour (UTC) · 2026-10-15highest 7.7%

Before → Event → After. ○ no data: no aircraft were observed that hour; this does not mean zero interference.

Hourly values (whole region network)
Hour (UTC)PhaseAircraft observedAircraft affectedShare
16:00Before1264352.8%
17:00Before1203342.8%
18:00Before1150484.2%
19:00Event1083312.9%
20:00Event940262.8%
21:00After857283.3%
22:00After687324.7%
23:00After594467.7%

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

What we do not know about this event

  • Cause: jamming, spoofing or a fault in the aircraft's avionics cannot be told apart from this data alone.
  • Coverage: the data comes from a single source (adsb.lol); aircraft where there are no receivers are not seen.
  • Share: the affected-aircraft count is not a share of all aircraft in the region; it covers only aircraft observed in the event's hot cell-hours.
  • Reality: this is an indicator; the event has not been verified by an independent source.
Method and limits
What is this event?
An event is a region of low navigation integrity (NIC) seen in adjacent cells over consecutive hours. It does not say what caused it (jamming, spoofing or a fault).
What does “aircraft affected” mean?
The number of distinct aircraft that reported low NIC in the event's hot cell-hours. It is not a count of all aircraft in the region. Observed aircraft are only those seen in the event's hot cell-hours, not all aircraft in the region. The share should therefore not be read as “the share of aircraft in the area”.
What does observation sufficiency say?
Observation sufficiency comes from the number of aircraft observed and the uncertainty interval of the affected share; it shows how solid the data is. It does not say what caused the event or whether it is real. A reasonable sample. “High” needs more aircraft and a narrow interval.

Indicative · based on ADS-B integrity (NIC) data · Contains information from adsb.lol contributors (ODbL 1.0) · Manzlytics GNSS