Pricing Search Start free trial
// Airspace Post UPDATED 4 months ago 7 min read

NOTAMs Confirm Just 29% of 2026 Airspace Disruptions

NOTAMs confirm only 29% of airspace disruptions—but flight-traffic data reveals much more. See why for your route planning.

← All data stories

By: FlySafe Editorial

Written for Dispatchers Insurance
NOTAMs Confirm Just 29% of 2026 Airspace Disruptions

Across the first six-and-a-half months of 2026, FlySafe airspace-risk collectors recorded 272 confirmed airspace-disruption events spanning 59 flight information regions (FIRs), totalling 1,512 airspace-days. Within that set, a single detection metric stands out for anyone building a route plan: formal NOTAM notices corroborated only about 29% of confirmed disruptions, while independently collected flight-traffic data corroborated roughly 73%. For an operator whose airspace picture depends on NOTAM review alone, the practical meaning of "flight risk" is that the majority of confirmed disruptions never appear in the one feed most flight-planning workflows treat as authoritative.

This bulletin reports the detection signal-gap first, then supports it with the FIR ranking and the year-to-date totals. FlySafe analysis shows the gap is not uniform — it is wide in some regions and narrow in others — and that distribution is what determines where NOTAM-only planning is safest and where it is weakest.

The Detection Signal-Gap

FlySafe confirms an event only when at least two independent signals agree and an operational cause is attributable; undetermined-cause detections are excluded. The primary corroborating signal is FlySafe's own ADS-B flight-traffic collection, which observes whether aircraft actually avoid, thin out over, or reroute around a volume of airspace.

Across FIRs with three or more confirmed events, flight-traffic data corroborated approximately 73% of events, whereas NOTAM references corroborated approximately 29%. The difference is the blind spot: a NOTAM-only review would miss the majority of confirmed disruptions, because observed traffic behaviour changed before, without, or independently of a published notice.

This is consistent with how the two data types differ in nature. A NOTAM is an administrative act — it exists when a state authority originates and publishes it. Observed traffic is a behavioural fact — it exists when aircraft move differently, regardless of whether paperwork accompanies the change. The two do not always align in time or in coverage, and the 2026 data quantifies how far apart they can sit.

The route-planning implication is direct. A dispatcher validating a route against NOTAMs alone is working from a feed that, in aggregate this year, reflected fewer than one in three confirmed disruptions. That does not make NOTAMs unreliable where they exist; it makes NOTAM-only coverage incomplete as a picture of where airspace is actually being avoided.

Where the Gap Is Widest — and Narrowest

The most disrupted FIRs by airspace-days show that NOTAM corroboration varies sharply by region. The table below ranks the six FIRs carrying the most airspace-days year-to-date, with the share of events corroborated by flight-traffic versus by NOTAM.

FIR Events Airspace-days Traffic corrob. NOTAM corrob.
Tehran (OIIX) 41 273.0 80% 46%
Damascus (OSTT) 33 241.0 58% 39%
RPHI 14 183.0 0% 86%
MMFR 13 180.0 100% 92%
Tel Aviv (LLLL) 28 131.0 89% 39%
UUWV 14 108.0 93% 50%

Two patterns emerge. In several high-airspace-day FIRs — Tehran (OIIX), Damascus (OSTT), and Tel Aviv (LLLL) — NOTAM corroboration sits below 50% while flight-traffic corroboration runs from 58% to 89%. In those regions, observed traffic behaviour is the stronger signal, and NOTAM-only review would understate the disruption footprint.

By contrast, RPHI and MMFR show high NOTAM corroboration (86% and 92%). RPHI is notable for 0% flight-traffic corroboration against 86% NOTAM corroboration — a profile in which the formal notice carried the signal and observed avoidance did not, the inverse of the wider trend. MMFR is corroborated by both signals at high rates (100% traffic, 92% NOTAM), the closest alignment in the top six.

The takeaway is that the blind spot is regional, not universal. NOTAM coverage was strong in some volumes and weak in others during 2026. A planner cannot assume uniform NOTAM completeness across all FIRs, and cannot assume flight-traffic will always fill the gap — RPHI shows the reverse can occur.

Year-to-Date Totals and Trend

The year-to-date baseline, as of 13 July 2026: 272 confirmed events, 1,512 airspace-days, 59 FIRs. The monthly confirmed-event trend rose through the period — January 5, February 16, March 1, April 21, May 72, June 137 — before a partial July count of 20 through the 13th. June carried the highest confirmed-event count in the window.

By airspace-days, the cause-category mix uses neutral operational categories only: conflict-zone restrictions 54% (815 days, 147 events), volcanic ash 25% (375 days, 47 events), seismic activity 14% (213 days, 27 events), other regulatory restrictions 6% (97 days, 46 events), and tropical cyclones 1% (12 days, 5 events). These categories describe the operational nature of the disruption, not any political or geographic reason for it.

On recovery: all 272 confirmed disruptions in the window have ended, 128 of them within the last 30 days, and the average confirmed disruption ran approximately 5.6 airspace-days. Airspace disruption in this dataset is therefore predominantly transient rather than permanent — a factor that matters when weighing whether a temporarily avoided route is likely to reopen within a planning horizon.

This same finding — that NOTAMs miss the majority of confirmed disruptions — is examined in further detail in FlySafe's analysis of how NOTAMs missed most aviation airspace disruptions in 2026.

What This Means for Route Planning

For dispatchers and flight-planning teams, the operational reading is straightforward.

Recommendation: Treat NOTAM review as necessary but not sufficient. Where a NOTAM exists, it remains the regulatory instrument that defines whether airspace is closed, restricted, or a prohibited area, and it must be complied with. Where a NOTAM does not exist, the absence of a notice is not evidence that airspace is undisrupted — in 2026, most confirmed disruptions were not reflected in NOTAM feeds.

Pairing NOTAM review with an independent behavioural signal — observed flight-traffic — narrows the blind spot. A volume that aircraft are demonstrably avoiding warrants scrutiny even without a published notice, and a published notice warrants compliance even where traffic has not yet visibly thinned.

Because 272 of 272 disruptions in the window have ended, planners should also treat disruption status as time-sensitive: a route avoided last week may be usable now, and vice versa. No cost figures, specific NOTAM identifiers, or carrier-level rerouting data are included here, as those are not present in the underlying dataset.

Regulatory Context

The NOTAM system's coverage limits sit within a defined regulatory framework. Under ICAO Annex 15 — Aeronautical Information Services, states are responsible for originating and disseminating NOTAMs for their FIRs; a NOTAM's existence depends on that origination step, which is one structural reason observed disruptions can precede or bypass formal notices. ICAO Annex 11 — Air Traffic Services governs how air traffic services and airspace restrictions are administered within each FIR.

At the advisory level, EASA Conflict Zone Information Bulletins (CZIB) provide guidance to European operators on specific airspace, but a CZIB is advisory only unless the relevant state CAA gives it force through a NOTAM or AIP entry. Under EU Regulation 965/2012 — Air Operations, EU/EEA operators carry responsibility for assessing airspace risk as part of operational control, which extends the planning obligation beyond simple NOTAM compliance. For US operators, 14 CFR Part 91 — including §91.703 for operations outside US airspace — establishes the general operating rules that apply when transiting foreign FIRs.

None of these frameworks guarantees that every disruption a planner needs to know about will appear as a NOTAM. That is precisely the gap the corroboration data measures.

Methodology and Provenance

All figures are from FlySafe airspace-risk collectors for the window 1 January 2026 to 13 July 2026, and reflect confirmed events only — those with at least two independent signals and an attributed operational cause; undetermined-cause detections are excluded. The FlySafe consensus engine requires two or more independent signals per event, with FlySafe's own ADS-B flight-traffic collection serving as the primary corroborating signal. Inputs include public NOTAM, EASA, FAA TFR, volcanic-ash, and seismic advisories, combined with FlySafe ADS-B data. All data is as of 13 July 2026.

Analysis is based on publicly available data only. FlySafe Research is an aviation risk intelligence service and is not an operational authority. This bulletin is not a NOTAM, does not carry regulatory force, and does not replace official aeronautical information. Operators must consult the relevant state AIS, current NOTAMs, and their own operational control processes before flight.

Key takeaway: In 2026 to date, flight-traffic data corroborated roughly 73% of confirmed airspace disruptions against roughly 29% for NOTAMs — meaning NOTAM-only review missed the majority. The gap is regional: wide in Tehran, Damascus, and Tel Aviv FIRs, narrow in MMFR. Against a baseline of 272 confirmed events and 1,512 airspace-days across 59 FIRs, pairing NOTAM review with an independent behavioural signal is what closes the blind spot.

For continuously updated FIR-level disruption tracking that combines public advisories with independent flight-traffic corroboration, see FlySafe Research.

✦SqueezeAI
  1. Flight-traffic data corroborated roughly 73% of confirmed 2026 airspace disruptions, versus only 29% for NOTAMs — meaning a NOTAM-only workflow misses the majority of events where aircraft actually altered their behavior around a given airspace volume.
  2. The gap is structural, not incidental: NOTAMs are an administrative record that exists only when a state authority publishes one, while traffic corroboration is a behavioral observation that exists whenever aircraft deviate, independently of any published notice.
  3. NOTAM corroboration rate varies sharply by region — Tehran FIR (OIIX) reached 46% versus the 29% fleet average — so the practical risk of NOTAM-only planning is unevenly distributed across the route network.

Powered by B1KEY

FlySafe

Live tools behind the analysis.

The signals FlySafe writes about are also published live — continuously verified by the Sentinel pipeline.

Information is accurate as of the publication date. FlySafe uses exclusively publicly available data.