Skip to content

Week 2026 / 42 · 2026-10-12 – 2026-10-18

Week 42 (12–18 October 2026): Integrity-drop measurements (consistent with GNSS degradation)

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

Affected aircraft-hour share

%3.7

▼ 0.1 pp vs previous week

Affected aircraft-hours

6,469

/ 174,561 aircraft-hours

Events

247

247 medium/high sufficiency

Position anomalies

79

high/medium-sufficiency events

Day by day

Each day's affected aircraft-hour share (%). Peak day in dark colour.

  • 3.6
    Mon
  • 3.8
    Tue
  • 3.5
    Wed
  • 4
    Thu
  • 4.1
    Fri
  • 3.4
    Sat
  • 3.6
    Sun

Last 12 weeks

Weekly share; this report is the highlighted point. Weeks without data are left blank.

%3%4.1

Highest FIRs

Regions with enough sample during the week, by affected aircraft share.

  • Ankara%9.6
  • Damascus%9.1
  • Bucharest%8.1
  • Sofia%4.9
  • Istanbul%3.6
  • Amman%3
  • Budapest%2.7
  • Nicosia%2.4

Cell map of the peak day · 2026-10-16

Each polygon is an H3 cell; “no data” does not mean calm.

  • Insufficient data
  • Low
  • Medium
  • High

Largest event of the week

Istanbul

143

2026-10-12, 01–10 UTC, 10 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.

  • 17
    Mon
  • 8
    Tue
  • 3
    Wed
  • 34
    Thu
  • 6
    Fri
  • 4
    Sat
  • 7
    Sun

Findings this week

  1. In the regional scope (Türkiye and neighbours), 3.71% (6,469) of 174,561 aircraft-hours over seven days showed degraded navigation integrity; the daily rate ranged from 3.43% to 4.06%. The peak day was 16 October (4.06%), followed by 15 October (3.97%). These data do not identify the cause of any rise or fall.
  2. Share of aircraft affected by region (weekly, FIRs with sufficient observation volume): Ankara 9.6%, Damascus 9.1%, Bucharest 8.1%, Sofia 4.9%, Istanbul 3.6%.
  3. The integrity-drop event affecting the most aircraft this week was on 12 October in the Istanbul FIR: 143 unique aircraft, 10 hours (01–10 UTC), 25 cells (event = connected medium/high-level cell-hours). The days of the week were produced with two algorithm versions (1.5.0, 1.6.0); the event rule is identical in both, so events are comparable; only the position-anomaly confidence tiers were computed differently in the two versions.
  4. Position anomalies (spoofing, rule-based, focus region): 79 high/medium-confidence events this week (73 high, 6 medium); busiest day 15 October (34). There are also 28 low-confidence events and 365 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 20 October 2026 and rests on the published data of that day: regional scope (Türkiye and neighbours), algorithm 1.5.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.

Open on the map

This report is based on observed ADS-B data and is not an operational navigation source. See the methodology page for the general framework.