Week 2026 / 43 · 2026-10-19 – 2026-10-25
Week 43 (19–25 October 2026): Integrity-drop measurements (consistent with GNSS degradation)
Indicative · based on ADS-B integrity (NIC) data
Affected aircraft-hour share
%3.8
▲ 0.1 pp vs previous week
Affected aircraft-hours
6,630
/ 173,485 aircraft-hours
Events
240
240 medium/high sufficiency
Position anomalies
39
high/medium-sufficiency events
Day by day
Each day's affected aircraft-hour share (%). Peak day in dark colour.
- 3.1Mon
- 4.1Tue
- 3.8Wed
- 4.3Thu
- 4.2Fri
- 3.3Sat
- 4.1Sun
Last 12 weeks
Weekly share; this report is the highlighted point. Weeks without data are left blank.
%3%3.8
Highest FIRs
Regions with enough sample during the week, by affected aircraft share.
- Ankara%9.4
- Damascus%8.7
- Bucharest%7.4
- Sofia%4.8
- Istanbul%3.4
- Amman%2.7
- Budapest%2.5
- Nicosia%2.3
Cell map of the peak day · 2026-10-22
Each polygon is an H3 cell; “no data” does not mean calm.
- Insufficient data
- Low
- Medium
- High
Largest event of the week
Istanbul
160
2026-10-24, 01–05 UTC, 5 hours in total. The number of unique affected aircraft is shown above.
Position anomalies (spoofing) · day by day
High- and medium-sufficiency events (rule-based, focus region only); high in dark colour.
- 0Mon
- 3Tue
- 5Wed
- 5Thu
- 11Fri
- 6Sat
- 9Sun
Findings this week
- In the regional scope (Türkiye and neighbours), 3.82% (6,630) of 173,485 aircraft-hours over seven days showed degraded navigation integrity; the daily rate ranged from 3.06% to 4.25%. The peak day was 22 October (4.25%), followed by 23 October (4.16%). These data do not identify the cause of any rise or fall.
- Share of aircraft affected by region (weekly, FIRs with sufficient observation volume): Ankara 9.4%, Damascus 8.7%, Bucharest 7.4%, Sofia 4.8%, Istanbul 3.4%.
- The integrity-drop event affecting the most aircraft this week was on 24 October in the Istanbul FIR: 160 unique aircraft, 5 hours (01–05 UTC), 37 cells (event = connected medium/high-level cell-hours). The days of the week were produced with several algorithm versions (1.10.0, 1.6.0); the level and event rules are identical across them, so events are comparable; only the position-anomaly confidence tiers and the exclusion of faulty-avionics aircraft were computed differently between versions, so small count differences between days are possible.
- Position anomalies (spoofing, rule-based, focus region): 39 high/medium-confidence events this week (30 high, 9 medium); busiest day 23 October (11). There are also 21 low-confidence events and 308 jumps overlapping with low integrity; jumps coinciding with integrity loss are not counted in this headline figure; the cause is not stated. Indicator only: it states no cause.
Data period, version and scope
This report was published on 26 October 2026 and rests on the published data of that day: regional scope (Türkiye and neighbours), algorithm 1.10.0, 1.6.0 (a single affected-aircraft definition is used: a notable share of reports showing low integrity; faulty-transmitter filter applied). Earlier weekly reports may have been prepared with a different scope or algorithm version; reports must not be compared directly. The data come from a single source (adsb.lol); areas without receivers are invisible and “no data” does not mean “calm”. It is an indicator only: it states no cause and makes no definitive detection claim.
This report is based on observed ADS-B data and is not an operational navigation source. See the methodology page for the general framework.