Skip to content

Week 2026 / 38 · 2026-09-14 – 2026-09-20

Week 38 (14–20 September 2026): Integrity-drop measurements (consistent with GNSS degradation)

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

Affected aircraft-hour share

%3.1

▼ 0.3 pp vs previous week

Affected aircraft-hours

5,778

/ 187,746 aircraft-hours

Events

245

245 medium/high sufficiency

Position anomalies

100

high/medium-sufficiency events

Day by day

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

  • 2.9
    Mon
  • 3
    Tue
  • 2.7
    Wed
  • 2.7
    Thu
  • 2.9
    Fri
  • 3.4
    Sat
  • 4
    Sun

Last 12 weeks

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

%3.1%4.1

Highest FIRs

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

  • Damascus%8.1
  • Bucharest%6.5
  • Ankara%6.2
  • Sofia%4.1
  • Istanbul%3
  • Nicosia%2.4
  • Amman%2.3
  • Budapest%2.2

Cell map of the peak day · 2026-09-20

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

  • Insufficient data
  • Low
  • Medium
  • High

Largest event of the week

Istanbul

252

2026-09-20, 06–23 UTC, 18 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.

  • 8
    Mon
  • 13
    Tue
  • 20
    Wed
  • 11
    Thu
  • 11
    Fri
  • 12
    Sat
  • 25
    Sun

Findings this week

  1. In the regional scope (Türkiye and neighbours), 3.08% (5,778) of 187,746 aircraft-hours over seven days showed degraded navigation integrity; the daily rate ranged from 2.68% to 3.98%. The peak day was 20 September (3.98%), followed by 19 September (3.37%). 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): Damascus 8.1%, Bucharest 6.5%, Ankara 6.2%, Sofia 4.1%, Istanbul 3.0%.
  3. The integrity-drop event affecting the most aircraft this week was on 20 September in the Istanbul FIR: 252 unique aircraft, 18 hours (06–23 UTC), 37 cells (event = connected medium/high-level cell-hours). All days of the week were produced with the same algorithm version (1.5.0), so the events are comparable with one another.
  4. Position anomalies (spoofing, rule-based, focus region): 100 high/medium-confidence events this week (100 high, 0 medium); busiest day 20 September (25). There are also 10 low-confidence events and 404 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 15 October 2026 and rests on the published data of that day: regional scope (Türkiye and neighbours), algorithm 1.5.0 (a single affected-aircraft definition is used: a notable share of reports showing low integrity; faulty-transmitter filter applied). This report was prepared retrospectively on 15 October 2026, after the week ended: the figures show the current reprocessed series, not necessarily what would have been published at the time. 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.