Indicative · based on ADS-B integrity (NIC) data
Budapest FIR (LHCC)
Integrity drop2026-10-16 14:00Z – 15:00Z · 2 h
- Scale
- Small
- Observation sufficiency
- Medium
- Aircraft affected
- 5
- In this FIR, last 30 days
- 47th of 47 events
Low navigation integrity (NIC) in adjacent cells. It does not say what caused it.
This is not a risk percentage or an observation-sufficiency value; it is only a size ranking. How is it calculated?
Opens the event's day; you choose departure and arrival.
Evidence
- Strongest moment (UTC)
- 15:00 · cell 851e0a43fffffffOpen the strongest moment on the map
- Aircraft affected that hour
- 2 / 8 aircraft
- Scale basis
- 5 affected aircraft → Small event
- Observation-sufficiency basis
- 26 aircraft observed, 5 affected.
- Aircraft observed in hot hours
- 26 aircraft (19% affected)
- FIR
- Budapest FIR (LHCC)
Technical details
- Hot cell-hours
- 4(hour, cell) pairs that make up the event
- Cells
- 4
- 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.
Before → Event → After. ○ no data: no aircraft were observed that hour; this does not mean zero interference.
| Hour (UTC) | Phase | Aircraft observed | Aircraft affected | Share |
|---|---|---|---|---|
| 11:00 | Before | 1407 | 48 | 3.4% |
| 12:00 | Before | 1351 | 43 | 3.2% |
| 13:00 | Before | 1360 | 42 | 3.1% |
| 14:00 | Event | 1307 | 59 | 4.5% |
| 15:00 | Event | 1298 | 49 | 3.8% |
| 16:00 | After | 1241 | 54 | 4.4% |
| 17:00 | After | 1160 | 34 | 2.9% |
| 18:00 | After | 1119 | 22 | 2% |
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.
Among this FIR's events in the last 30 days
This event is the 47th largest of the 47 events recorded in Budapest FIR (LHCC) over the last 30 days, ranked by affected aircraft (5 aircraft).
How is it calculated?
This is not a risk percentage and not an observation-sufficiency value. It is only a size ranking; size means affected aircraft. The 47 events are sorted by affected aircraft from largest to smallest, and this event is at rank 47. Events of equal size count as ahead of this one; low-level events are left out of the comparison.
An event crossing midnight is stored as two records. The count 47 can therefore be higher than the real number of events, and a split event can look smaller than it was; the rank can shift accordingly.
FIR-wide daily share (secondary context; not the event ranking)
Daily share of aircraft affected (affected / observed) for Budapest FIR (LHCC), over the whole FIR. A large but local event in a wide FIR may barely move this share, so it is not used to judge the event's size.
highest 3.5%
Gap: no data for the FIR that day (not zero). Marker: too few aircraft observed that day; no ratio computed.
| Day | Share | Aircraft observed | Events |
|---|---|---|---|
| 2026-09-21 | 1.9% | 17230 | 0 |
| 2026-09-22 | 1.7% | 18033 | 1 |
| 2026-09-23 | 2.3% | 18049 | 3 |
| 2026-09-24 | 2.4% | 18456 | 3 |
| 2026-09-25 | 1.9% | 18952 | 4 |
| 2026-09-26 | 2.6% | 19110 | 1 |
| 2026-09-27 | 1.7% | 18989 | 1 |
| 2026-09-28 | 1.5% | 17976 | 0 |
| 2026-09-29 | 2% | 17661 | 1 |
| 2026-09-30 | 1.9% | 17380 | 1 |
| 2026-10-01 | 1.4% | 18179 | 1 |
| 2026-10-02 | 2.1% | 18022 | 3 |
| 2026-10-03 | 2% | 18602 | 1 |
| 2026-10-04 | 1.7% | 18084 | 0 |
| 2026-10-05 | 2.4% | 17474 | 4 |
| 2026-10-06 | 2.2% | 16947 | 1 |
| 2026-10-07 | 1.9% | 16815 | 2 |
| 2026-10-08 | 2% | 17706 | 1 |
| 2026-10-09 | 1.5% | 18138 | 1 |
| 2026-10-10 | 1.7% | 18846 | 3 |
| 2026-10-11 | 2% | 18695 | 3 |
| 2026-10-12 | 2.2% | 17841 | 5 |
| 2026-10-13 | 2.5% | 17036 | 1 |
| 2026-10-14 | 2.8% | 16922 | 0 |
| 2026-10-15 | 2.2% | 18302 | 1 |
| 2026-10-16 | 3.5% | 18066 | 7 |
| 2026-10-17 | 2.7% | 19183 | 4 |
| 2026-10-18 | 3.3% | 18332 | 3 |
| 2026-10-19 | 1.7% | 16851 | 3 |
| 2026-10-20 | 3% | 16891 | 5 |
Secondary: 64 integrity drop event records in this FIR over the last 30 days. An event crossing midnight counts as two records, so the count is not an exact measure.
Data note: on some earlier days unfiltered records from faulty devices may be included, so shares on those days may be slightly high.
Longer history in this region
Integrity drop events with medium or high observation sufficiency for Budapest FIR (LHCC), year by year (from the days in the archive).
| Year | Events | Days with events | Observation level |
|---|---|---|---|
| 2023 | 11 | 9 / 318 | %43 · Moderate |
| 2024 | 224 | 127 / 366 | %65 · Moderate |
| 2025 | 457 | 250 / 361 | %82 · Strong |
| 2026 | 331 | 183 / 283 | %86 · Strong |
The observation level is that year's observed aircraft-hours as a share of today's level. As the adsb.lol receiver network grew, observation grew; event counts in low-level years cannot be compared with today's. An event is one cluster of adjacent cell-hours: several unconnected clusters on the same day count as separate events and midnight splits an event in two, so the event count is not a number of separate incidents. This is not a trend or risk claim.
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