Between 1 January and 10 August 2026, FlySafe's airspace-risk collectors confirmed 578 airspace-disruption events across 69 flight information regions (FIRs), amounting to 4,791 airspace-days of degraded or restricted operations. Readers searching for the status of Jordan airspace will find a notable absence in this dataset: Jordan's FIR does not appear among the most-disrupted regions of 2026, even as the neighbouring Damascus FIR (OSTT) tops the year-to-date table with 661 airspace-days. This bulletin synthesizes the year-to-date totals, the monthly trend, the most-affected FIRs, the cause-category mix, and a persistent detection gap in NOTAM-only monitoring. All figures are drawn from FlySafe collector data as of 2026-08-10.
2026 Year-to-Date: The Headline Numbers
The confirmed-event dataset covers only disruptions corroborated by at least two independent signals with an attributed cause; detections with undetermined causes are excluded. On that conservative basis (FlySafe collectors, as of 2026-08-10):
| Metric | Value |
|---|---|
| Confirmed disruption events | 578 |
| FIRs affected | 69 |
| Total airspace-days | 4,791 |
| Average disruption duration | ~8.3 airspace-days |
| Events now ended | 578 of 578 |
| Events ended in the last 30 days | 297 |
Two figures deserve emphasis. First, every confirmed 2026 disruption tracked in the dataset has ended — there are no open confirmed events as of the data date. Second, 297 of those closures occurred in the last 30 days alone, reflecting the sharp mid-summer concentration of events described below.
The Monthly Trend: A Steep Mid-Year Climb
Confirmed events were rare in the first quarter and surged through early summer (FlySafe collectors, as of 2026-08-10):
| Month (2026) | Confirmed events |
|---|---|
| January | 5 |
| February | 16 |
| March | 1 |
| April | 21 |
| May | 72 |
| June | 143 |
| July | 303 |
| August (through 10th) | 17 |
July alone accounted for 303 events — more than half the year-to-date total. The August figure covers only ten days and is not comparable to full months. The dataset attributes causes per event but does not support conclusions about why the aggregate curve steepened; no forecast is offered here.
Most Disrupted FIRs by Airspace-Days
Six FIRs dominate the year-to-date ranking (FlySafe collectors, as of 2026-08-10):
| FIR | Events | Airspace-days | Flight-traffic corroboration | NOTAM corroboration |
|---|---|---|---|---|
| Damascus FIR (OSTT) | 61 | 661.0 | 31% | 67% |
| RPHI | 41 | 495.0 | 0% | 95% |
| UHMM | 31 | 394.0 | 0% | 97% |
| SEFG | 25 | 375.0 | 0% | 100% |
| SKED | 24 | 360.0 | 100% | 100% |
| SPIM | 22 | 326.0 | 100% | 100% |
The corroboration columns show how differently disruptions surface in different regions. In SKED and SPIM, every confirmed event was visible both in NOTAM publications and in observed flight-traffic behaviour. In RPHI, UHMM, and SEFG, NOTAMs captured nearly all events, but flight-traffic signatures were absent — consistent with restrictions in volumes carrying little through-traffic. Damascus FIR shows the inverse weakness: a third of its events left no NOTAM trace in the corroboration data. A fuller ranking is available in FlySafe's companion piece, 2026's most-disrupted FIRs ranked by NOTAM data.
What Drove the Disruptions: Cause-Category Mix
By airspace-days, natural phenomena — not security-related restrictions — account for the majority of 2026's confirmed disruption burden (FlySafe collectors, as of 2026-08-10):
| Cause category | Share of airspace-days | Airspace-days | Events |
|---|---|---|---|
| Volcanic ash | 57% | 2,741 | 252 |
| Conflict-zone restrictions | 31% | 1,505 | 207 |
| Seismic activity | 6% | 300 | 43 |
| Tropical cyclones | 3% | 148 | 30 |
| Other regulatory restrictions | 2% | 97 | 46 |
Most-affected FIRs per category, by ICAO designator:
- Volcanic ash: RPHI (495.0 airspace-days), UHMM (388.0), SEFG (375.0)
- Conflict-zone restrictions: Damascus FIR / OSTT (661.0), UUWV (326.0), Tehran FIR / OIIX (301.0)
- Seismic activity: MMFR (223.0), MMID (25.0), RJDG (21.0)
- Tropical cyclones: ZSHA (91.0), KZAK (22.0), MMID (10.0)
- Other regulatory restrictions: KZJX (10.0), KZMP (10.0), KZLC (10.0)
Volcanic ash is the single largest driver at 57% of all airspace-days — more than half the global burden — concentrated in three FIRs. Conflict-zone restrictions, while second by volume, produced the single most-disrupted FIR of the year (OSTT). MMID appears in two categories (seismic and cyclone), the only FIR in the dataset affected by two distinct natural-hazard classes among the per-category leaders.
The dataset does not include cost estimates, carrier-level impact figures, or individual NOTAM identifiers; those are not currently available in this bulletin's source data.
Jordan Airspace and the Regional Picture
Search interest in Jordan airspace status is understandable given its geography: the Amman FIR sits directly adjacent to the Damascus FIR (OSTT), 2026's most-disrupted region at 61 events and 661 airspace-days. Traffic avoiding a restricted volume typically transits adjacent FIRs, which raises legitimate planning questions for operators in the corridor.
The honest answer from the data: Jordan's FIR does not rank among the most-disrupted FIRs in FlySafe's 2026 confirmed-event dataset, in any cause category. No confirmed-event figures for Jordan airspace are reported in the current data window, and this bulletin does not infer an operational status beyond that. Operators planning through the region should consult current NOTAMs and applicable EASA Conflict Zone Information Bulletins for the relevant FIRs rather than rely on aggregate rankings. For a comparable regional breakdown elsewhere in the Middle East, see FlySafe's analysis of which FIRs lost the most days in the UAE region in 2026.
The Signal Gap: Why NOTAM-Only Monitoring Misses Disruptions
Among FIRs with at least three confirmed events, flight-traffic observation corroborated roughly 77% of events, while NOTAM publications corroborated only about 45% (FlySafe collectors, as of 2026-08-10). A monitoring posture that relies on NOTAMs alone would therefore miss the majority of confirmed disruptions — either because a formal notice was never published, or because it lagged the operational reality visible in traffic behaviour.
The Damascus FIR illustrates the gap concretely: 67% NOTAM corroboration means one event in three surfaced only through independent signals. Conversely, the 0% flight-traffic corroboration in RPHI, UHMM, and SEFG shows the reverse blind spot — traffic-only monitoring would miss restrictions in low-traffic volumes that NOTAMs capture well. Neither signal is sufficient alone; the case for multi-signal consensus is examined in depth in why NOTAMs miss most airspace disruptions in 2026.
Regulatory Context
Several frameworks govern how the disruptions in this dataset are declared, published, and acted upon:
- ICAO Annex 11 — Air Traffic Services defines the FIR structure itself and the responsibility of states to provide air traffic services within their designated regions — the unit of measurement used throughout this bulletin.
- ICAO Annex 15 — Aeronautical Information Services establishes the NOTAM system as the formal channel for temporary airspace changes. The signal-gap findings above are, in effect, a measurement of how completely that channel reflects operational reality.
- EASA Conflict Zone Information Bulletins (CZIB) provide advisory-level risk information for airspace affected by security situations. A CZIB is advisory only unless adopted by a state authority via NOTAM or AIP entry — a distinction relevant to the conflict-zone-restriction category, which accounts for 31% of 2026 airspace-days.
- EU Regulation 965/2012 — Air Operations obliges EU operators to assess route risks as part of their management systems, which in practice requires exactly the kind of multi-source disruption awareness the signal-gap data argues for.
- FAA Advisory Circular 91-70B addresses oceanic and international operations planning, relevant to carriers routing around disrupted volumes on long-haul segments.
Methodology & Provenance
- Source: FlySafe airspace-risk collectors; data window 2026-01-01 through 2026-08-10.
- Confirmation standard: an event is confirmed only when at least two independent signals corroborate it and a cause can be attributed. Detections with undetermined causes are excluded from all figures in this bulletin.
- Signals: public NOTAM publications, EASA advisories, FAA temporary flight restrictions, volcanic-ash and seismic advisories, and FlySafe's own ADS-B flight-traffic collection, which serves as the primary corroborating signal.
- Unit: an airspace-day is one FIR affected for one day.
- Known limitations: no cost data, no carrier-level figures, no individual NOTAM references in this aggregate view; August 2026 is a partial month.
Key Takeaway
The 2026 year-to-date picture is one of concentration on every axis: 578 confirmed events and 4,791 airspace-days across 69 FIRs, with more than half of all events occurring in July alone, 57% of the disruption burden attributable to volcanic ash in just a handful of FIRs, and a single region — Damascus FIR — carrying 661 airspace-days. Meanwhile, the monitoring gap is structural, not incidental: NOTAMs corroborated fewer than half of confirmed events in multi-event FIRs. For operators, the practical implication is that no single data channel — NOTAM, advisory, or traffic observation — provides a complete disruption picture on its own.
FlySafe's consensus engine exists to close that gap, cross-checking public aeronautical publications against independent flight-traffic observation before any event is confirmed. FlySafe analysis is based exclusively on publicly available data. FlySafe is not an operational authority; nothing in this bulletin substitutes for official NOTAMs, AIP entries, or state-issued guidance, which remain the sole authoritative sources for flight planning.
- Jordan's FIR does not appear among the most-disrupted regions of 2026, even as its neighbour Damascus FIR (OSTT) leads the year-to-date table with 661 airspace-days across 61 confirmed events.
- NOTAM-only monitoring produces systematically incomplete coverage: in three of the six most-disrupted FIRs (RPHI, UHMM, SEFG), flight-traffic corroboration was zero despite near-total NOTAM capture, meaning real-world impact was not reflected in official publications alone.
- Disruptions were heavily concentrated in mid-year: July 2026 alone accounted for 303 of 578 confirmed events — more than half the year-to-date total — against just 5 events in January.
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.