Between 1 January and 24 August 2026, FlySafe airspace-risk collectors logged 746 confirmed airspace-disruption events across 74 FIRs, totalling 6,407 airspace-days. Of the events occurring in FIRs with a meaningful sample, formal notices corroborated roughly 47%, while independent flight-traffic observation corroborated roughly 73%. That difference is the operational core of this bulletin: a planner relying on formal notices alone would have missed the majority of confirmed disruptions during this window. This FlySafe analysis sets out where the gap is widest and what it means for route review.
The Signal Gap: What NOTAM-Only Review Misses
FlySafe classifies an event as confirmed only when at least two independent signals agree and a cause is attributed; undetermined-cause detections are excluded. Within that confirmed set, two corroborating channels can be compared directly: the formal notice channel (public NOTAM and equivalent advisories) and the flight-traffic channel (FlySafe ADS-B observation of how aircraft actually behaved).
Across FIRs with three or more confirmed events, flight-traffic corroborated about 73% of events; formal notices corroborated about 47%. The practical reading is straightforward. A review process that treats the absence of a NOTAM as the absence of a problem inherits a blind spot covering a large share of real, multi-signal-confirmed disruptions. Aircraft were already routing around a volume that the formal-notice record did not fully reflect.
The term "flight risk meaning," in this operational sense, is precise: the risk that matters to a dispatcher is not whether a notice exists on paper, but whether the airspace is actually usable as filed. Observed traffic behaviour measures the second question directly.
This does not imply that formal notices are unreliable — they remain the legal instrument of record. It means that notice coverage and real-world disruption are not the same dataset, and the difference is measurable.
The Numbers Behind the Gap: Most-Disrupted FIRs
The FIR-level ranking makes the divergence concrete. Corroboration rates differ sharply between the two channels depending on the FIR.
| FIR | Events | Airspace-days | Flight-traffic corrob. | NOTAM corrob. |
|---|---|---|---|---|
| Damascus (OSTT) | 75 | 850.0 | 25% | 73% |
| SEFG | 39 | 585.0 | 0% | 100% |
| SKED | 38 | 570.0 | 100% | 100% |
| SPIM | 36 | 533.0 | 100% | 100% |
| RPHI | 47 | 519.0 | 0% | 96% |
| UUWV | 42 | 516.0 | 98% | 83% |
Source: FlySafe airspace-risk collectors, as of 2026-08-24.
Two patterns stand out. Where both channels read 100% (SKED, SPIM), the record is internally consistent and a notice-based review would not miss the event. But UUWV shows the inverse of the aggregate concern — flight-traffic corroborated 98% of events against 83% by notice — a case where behaviour led the paper record. Conversely, SEFG and RPHI show near-total notice coverage with little or no independent flight-traffic corroboration, which is the expected signature of a full closed volume: when a FIR is genuinely closed by NOTAM, there is little residual civil traffic left to observe.
The point of the two-channel method is not to declare one channel correct. It is that neither channel alone reconstructs the full picture, and the FIRs where they disagree are exactly the ones that warrant a second look before a flight plan is filed.
Year-to-Date Trend and Recovery
The confirmed-event count was not evenly distributed across the window. Monthly confirmed events ran: January 5, February 16, March 1, April 21, May 72, June 143, July 350, August 138 (partial month, through 24 August). The concentration in the mid-year period is the reason a single quarterly review would have understated activity for much of the first half.
On the operational categories — reported here as neutral operational classifications only — the airspace-day totals break down as: volcanic ash 57% (3,669 days, 343 events), conflict-zone restrictions 33% (2,138 days, 263 events), seismic activity 5% (316 days, 51 events), tropical cyclones 3% (187 days, 43 events), and other regulatory restrictions 2% (97 days, 46 events). No political or geographic cause is attributed here; these are operational categories only.
Recovery data provides context on duration. All 746 confirmed disruptions have ended, 348 of them within the last 30 days, and the average confirmed disruption ran approximately 8.6 airspace-days. That average is a planning figure, not a forecast: it describes how long confirmed events in this window persisted, not how long any future event will last.
For a fuller FIR-by-FIR breakdown, see the companion analyses on the hardest-hit FIRs by airspace-days and the 2026 most-disrupted FIRs ranked from NOTAM data.
What This Means for Route Planning
Airspace status: confirmed disruptions in this window spanned 74 FIRs; all have since ended, but the corroboration gap persists as a review-process issue rather than a live-airspace one.
Recommendation: treat the formal-notice record as necessary but not sufficient. Where a flight plan crosses a FIR that has appeared in confirmed-disruption data, cross-check the notice record against observed traffic behaviour before assuming the volume is clear. The two-channel divergence in FIRs such as OSTT (25% flight-traffic vs 73% notice corroboration) is precisely where a notice-only check is weakest.
Specific carrier reroutings, cost figures, and individual NOTAM identifiers are not covered in this dataset and are not asserted here. Where a claim of that type would be useful, the honest position is that the data does not currently support it.
Regulatory Context
The frameworks below govern how airspace status is promulgated and how operators are expected to act on it. They are cited where they genuinely apply to the corroboration question.
- ICAO Annex 15 — Aeronautical Information Services establishes the NOTAM as the formal instrument for notifying temporary changes to airspace and facilities. The corroboration gap discussed here does not contradict Annex 15; it reflects the practical latency and coverage limits inherent in any notice system.
- ICAO Annex 11 — Air Traffic Services frames the FIR as the unit of airspace within which ATS is provided, which is why FIR-level metrics are the correct granularity for this analysis.
- EU Regulation 965/2012 — Air Operations places responsibility on operators to assess route feasibility, including the integration of available information beyond the minimum notice set — a duty that a two-channel review directly supports.
- EASA Conflict Zone Information Bulletins (CZIB) are, by ICAO/EASA terminology, advisory only unless a state CAA adopts the underlying restriction via NOTAM or AIP. A CZIB is not itself a closure, and should not be read as one.
- FAA Advisory Circular 91-70B — Oceanic and International Operations and 14 CFR Part 91 set the general operating expectations for international route review under US rules.
Nothing in this bulletin substitutes for the official NOTAM, AIP, or CZIB record of the relevant state authority.
Methodology and Provenance
FlySafe's consensus engine requires at least two independent signals per event and an attributed cause before an event is marked confirmed; undetermined-cause detections are excluded from every figure above. FlySafe's own ADS-B flight-traffic collection is the primary corroborating signal. Inputs are public NOTAM, EASA, FAA TFR, volcanic-ash, and seismic advisories, combined with FlySafe ADS-B observation.
All figures are as of 2026-08-24 and describe the window 2026-01-01 to 2026-08-24. Corroboration percentages for the signal-gap comparison are computed over FIRs with three or more confirmed events. Airspace-days count the summed duration of confirmed disruptions per FIR.
Disclaimer: Analysis based on publicly available data only. FlySafe is a risk-intelligence service and is not an operational authority. It does not issue, amend, or supersede NOTAMs, AIP entries, or CZIBs. Flight-planning and dispatch decisions must rely on the official notices and clearances of the relevant civil aviation authority and air navigation service provider.
Key Takeaway
In the 2026 year-to-date window, formal notices corroborated roughly 47% of confirmed airspace disruptions while independent flight-traffic observation corroborated roughly 73% — across 746 confirmed events and 6,407 airspace-days in 74 FIRs. The NOTAM blind spot is not a failure of the notice system; it is a coverage boundary that a second, independent signal can close. For route review, that means the meaningful question is not only whether a notice exists, but whether the airspace is behaving as if it is usable.
For continued FIR-level monitoring and the two-channel corroboration view, FlySafe publishes ongoing bulletins including which FIRs lost the most days in 2026.
- A NOTAM-only review process misses the majority of confirmed airspace disruptions: formal notices corroborated only 47% of events, while flight-traffic observation corroborated 73%.
- The absence of a NOTAM does not mean the airspace is usable; observed aircraft behavior is a more reliable indicator of actual usability than the paper record.
- Corroboration rates vary sharply by FIR: some regions show perfect agreement between both channels (SKED, SPIM), while others show flight-traffic leading the notice record (UUWV) or notices leading traffic (SEFG, RPHI).
- Route planning should incorporate flight-traffic observation data as a complement to formal notices, because relying on either channel alone creates a measurable blind spot.
Powered by B1KEY
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.