When a flight risk assessment relies on a single source, it inherits that source's blind spots. In airspace planning, the default single source is the NOTAM — the Notice to Air Missions issued by state authorities. FlySafe analysis shows that between 1 January and 12 August 2026, formal notices corroborated fewer than half of the airspace disruptions that were independently confirmed by other signals. For dispatchers and route planners, that gap is the practical meaning of flight risk: the disruptions a NOTAM-only review never sees.
FlySafe Research operates a consensus engine that requires at least two independent signals before an event is counted as confirmed. Across the study window, that engine recorded 603 confirmed airspace-disruption events across 71 flight information regions (FIRs), totalling 4,992 airspace-days (FlySafe airspace-risk collectors, as of 2026-08-12). Undetermined-cause detections were excluded. The finding below rests on that confirmed set.
The Signal Gap: What NOTAM-Only Review Misses
Among FIRs with three or more confirmed events, FlySafe's own ADS-B flight-traffic collection corroborated roughly 76% of events, while formal NOTAM records corroborated roughly 45%. In other words, a review built only on published notices would miss the majority of confirmed disruptions in the regions where disruptions cluster most.
This is not a claim that NOTAMs are inaccurate. It is a coverage observation. A NOTAM is a deliberate administrative act: a state authority decides a restriction warrants a notice, drafts it, and publishes it into the aeronautical information cycle. Observed flight behaviour — aircraft rerouting, thinning traffic density, altitude shifts visible in ADS-B Out returns — appears whether or not a notice is filed, and often earlier. When the two signals disagree, the disagreement itself is information about flight risk.
The practical implication is straightforward. Airlines have rerouted around volumes where the observable traffic pattern changed before, or without, a corresponding formal notice. A planning process that waits for the NOTAM inherits a lag and a coverage hole at the same time.
The Most-Disrupted FIRs in 2026
The corroboration split is visible directly in the ranking of most-disrupted FIRs by airspace-days. The columns below report how often each event was independently corroborated by flight-traffic and by NOTAM.
| FIR | Events | Airspace-days | Flight-traffic corroboration | NOTAM corroboration |
|---|---|---|---|---|
| Damascus (OSTT) | 63 | 691.0 | 30% | 68% |
| RPHI | 42 | 496.0 | 0% | 95% |
| UHMM | 33 | 411.0 | 0% | 97% |
| SEFG | 27 | 405.0 | 0% | 100% |
| SKED | 26 | 390.0 | 100% | 100% |
| SPIM | 24 | 356.0 | 100% | 100% |
Source: FlySafe airspace-risk collectors, confirmed events only, as of 2026-08-12.
The table shows that the signal gap is not uniform. In SKED and SPIM, both signals agree completely — flight-traffic and NOTAM corroborate every event. In RPHI, UHMM and SEFG, the confirmed events are carried almost entirely by NOTAM records with no flight-traffic corroboration, which is consistent with restrictions in low-density airspace where little observable traffic exists to reroute. Damascus (OSTT) sits between: the largest single contributor by airspace-days, with flight-traffic corroboration in 30% of events and NOTAM corroboration in 68%. No single signal captures the full picture in that FIR, which is precisely why a two-signal consensus is used. FlySafe reports these as disruption metrics only and does not attribute a cause to any individual FIR here.
Year-to-Date Totals and the Monthly Trend
Set against the 603-event, 4,992-airspace-day total across 71 FIRs, the six FIRs above account for a substantial share of the year's confirmed airspace-days. The concentration matters for route planning: a small number of regions drive most of the disruption burden.
The monthly confirmed-event trend across the window:
| Month | Confirmed events |
|---|---|
| January | 5 |
| February | 16 |
| March | 1 |
| April | 21 |
| May | 72 |
| June | 143 |
| July | 325 |
| August (to 12th) | 20 |
The count rose sharply through the second quarter and peaked in July. The August figure covers only the first twelve days and should not be read as a monthly total. FlySafe reports the trend as a count of confirmed events and does not forecast forward from it.
On the operational categories, the confirmed airspace-days break down as follows, using neutral operational classifications only: volcanic ash 58% (2,876 days, 267 events), conflict-zone restrictions 31% (1,562 days, 213 events), seismic activity 6% (304 days, 45 events), tropical cyclones 3% (153 days, 32 events), and other regulatory restrictions 2% (97 days, 46 events). These are operational categories, not attributions of cause to any specific region.
Recovery and Duration
Every confirmed disruption in the window has ended: 603 of 603 are resolved, with 309 of those ending in the last 30 days. The average confirmed disruption ran approximately 8.3 airspace-days. That average is a useful planning anchor — most confirmed disruptions are measured in days, not hours or weeks — but it is a mean across a wide distribution and should not be applied to any single active event. FlySafe does not currently publish per-FIR duration distributions in this bulletin; where that granularity is needed, it is not available here.
Regulatory Context
The NOTAM-versus-observation gap intersects several regulatory frameworks that route planners already work within.
- ICAO Annex 15 — Aeronautical Information Services defines the NOTAM system and the AIRAC cycle through which states publish airspace changes. The corroboration gap is, in part, a gap between what Annex 15 obliges states to publish and what independent observation detects. Reference: ICAO Annexes overview.
- ICAO Annex 11 — Air Traffic Services governs the provision of ATS within FIRs and the delegation of airspace responsibility, which is why the FIR is the natural unit for disruption accounting.
- EU Regulation 965/2012 — Air Operations places the operational-control and risk-assessment obligation on the operator, meaning the operator — not only the state issuing a NOTAM — is responsible for identifying airspace risk on a route.
- EASA Conflict Zone Information Bulletins (CZIB) are advisory instruments. Under FlySafe terminology, a CZIB issued without a supporting state-level airspace restriction is "advisory only" and does not by itself close or restrict airspace; the underlying regulatory status still rests on the relevant state's NOTAM or AIP. See EASA Conflict Zones.
- 14 CFR §91.703 requires US operators outside US airspace to comply with the rules of the state having jurisdiction and with applicable ICAO provisions — a reminder that NOTAM coverage varies by jurisdiction, and the operator carries the compliance burden across all of them.
None of these frameworks guarantees that every real disruption produces a timely NOTAM. That is the structural reason a second, observation-based signal changes the flight risk picture.
Key Takeaway
The meaning of the NOTAM blind spot is measurable. In the FIRs where disruptions concentrate, flight-traffic corroborated about 76% of confirmed events while NOTAMs corroborated about 45%. A route-risk process anchored only to formal notices misses the majority of confirmed disruptions in exactly the regions where the burden is highest. The corollary is not that NOTAMs should be ignored — in several FIRs they are the only signal available — but that no single source is sufficient. Two independent signals, reconciled, give a fuller and earlier read.
Airspace status: as of 2026-08-12, all 603 confirmed disruptions in the window have resolved; the operational picture is a record of what occurred, not a live restriction list.
Recommendation: treat NOTAM-only route reviews as a floor, not a complete risk assessment. Pair published notices with independent traffic observation, and weight the two accordingly when they disagree.
For the FIR-level rankings behind this bulletin, see 2026's most-disrupted FIRs ranked and the companion analysis on why NOTAMs miss most airspace disruptions.
Methodology & Provenance
FlySafe's consensus engine requires at least two independent signals per event before it is counted as confirmed, and requires an attributed cause; undetermined-cause detections are excluded. Inputs are public NOTAM, EASA and FAA TFR advisories, volcanic-ash and seismic advisories, plus FlySafe's own ADS-B flight-traffic collection, which is the primary corroborating signal. Corroboration percentages report how often each signal type independently supported an event, so a single event can be corroborated by more than one signal. All figures are drawn from confirmed events only, window 2026-01-01 to 2026-08-12, and are current as of 2026-08-12. Where the data does not cover a dimension — per-FIR duration distributions, carrier-level rerouting, specific NOTAM identifiers, or cost figures — that is stated rather than estimated.
Analysis based on publicly available data only. FlySafe Research is an aviation risk intelligence service and is not an operational authority; nothing here constitutes an airspace restriction, a NOTAM, ATC instruction, or authorization to plan or conduct a flight. Operators remain responsible for consulting official NOTAMs, AIP entries, and the relevant state CAA before any operation.
- In the highest-disruption FIRs, NOTAM records corroborated roughly 45% of confirmed airspace disruptions, while ADS-B flight-traffic data corroborated roughly 76% — meaning a NOTAM-only planning process misses the majority of events in the regions where disruptions cluster most.
- Observable flight behaviour — rerouting, traffic thinning, altitude shifts in ADS-B returns — appears whether or not a formal notice is filed, and often before one is issued, so NOTAM-only review inherits both a coverage gap and a timing lag.
- The signal gap is not uniform across regions: some FIRs (e.g. SKED, SPIM) show 100% corroboration from both sources, while others show near-zero flight-traffic corroboration despite near-complete NOTAM coverage, and vice versa — making the mix of signals region-dependent rather than a single global correction factor.
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.