Search queries such as "why is Caribbean airspace closed" spike every time flights reroute unexpectedly — yet the actual drivers of airspace disruption in 2026 look very different from what most travelers assume. According to FlySafe's airspace-risk collectors, 534 confirmed airspace-disruption events were recorded across 68 flight information regions (FIRs) between 1 January and 7 August 2026, amounting to 4,443 airspace-days of disruption. The single largest cause was not any security situation: it was volcanic ash, responsible for 57% of all airspace-days lost. This bulletin breaks down the full 2026 picture by disruption category, identifies the most-affected FIRs in each, and explains why NOTAM-only monitoring captures less than half of confirmed events. All figures are FlySafe data as of 2026-08-07.
The 2026 Disruption Mix: Five Operational Categories
Measured in airspace-days (one FIR disrupted for one day = one airspace-day), the confirmed 2026 events break down as follows:
| Category | Share of airspace-days | Airspace-days | Events |
|---|---|---|---|
| Volcanic ash | 57% | 2,523 | 226 |
| Conflict-zone restrictions | 31% | 1,390 | 195 |
| Seismic activity | 7% | 300 | 43 |
| Tropical cyclones | 3% | 133 | 24 |
| Other regulatory restrictions | 2% | 97 | 46 |
Two features of this distribution stand out. First, natural hazards — volcanic ash, seismic activity, and tropical cyclones combined — account for 67% of all airspace-days lost, roughly double the share attributable to conflict-zone restrictions. Second, the average confirmed disruption ran approximately 8.3 airspace-days, and all 534 confirmed disruptions in the dataset have ended, 274 of them within the last 30 days. Airspace disruption in 2026 has been frequent but, on average, short-lived.
The monthly trend shows a pronounced mid-year concentration: 5 confirmed events in January, 16 in February, 1 in March, 21 in April, 72 in May, 143 in June, and 266 in July, with 10 recorded in the first week of August. July alone accounted for roughly half of all confirmed events year-to-date.
Volcanic Ash: The Dominant Category by a Wide Margin
Volcanic ash contamination produced 2,523 airspace-days of disruption across 226 events — more than the other four categories combined. The most-affected FIRs:
- RPHI — 486 airspace-days
- UHMM — 355 airspace-days
- SEFG — 330 airspace-days
Ash-related disruptions are characteristically well documented in official channels: NOTAM corroboration reached 95% of events in RPHI, 96% in UHMM, and 100% in SEFG. Notably, flight-traffic corroboration in those three FIRs was 0% — consistent with ash events affecting airspace volumes where ADS-B traffic density is low, so the regulatory record (NOTAMs and volcanic-ash advisories) carries the detection burden. A ranked view of the year's most-affected regions is available in FlySafe's 2026 most-disrupted FIRs analysis.
Conflict-Zone Restrictions: Fewer Days, Denser Impact
Conflict-zone restrictions — the neutral ICAO-aligned category covering airspace subject to security-related operational limitations — produced 1,390 airspace-days across 195 events. The most-affected FIRs:
- Damascus FIR (OSTT) — 616 airspace-days, the single most-disrupted FIR of 2026 by this measure (58 events)
- Tehran FIR (OIIX) — 286 airspace-days
- UUWV — 283 airspace-days
Corroboration patterns here differ sharply from the ash category. In OSTT, NOTAMs corroborated 66% of events while flight-traffic data corroborated 33% — meaning a third of confirmed events left a visible footprint in actual traffic behavior. Airlines have rerouted around affected volumes in these regions; the dataset records the disruptions themselves, not carrier-specific routing decisions, and no per-carrier data is currently available. Terminology matters in this category: a FIR under conflict-zone restriction is not necessarily "closed" — full closure applies only where the responsible civil aviation authority has prohibited all civil operations by NOTAM or AIP entry. Where EASA publishes a Conflict Zone Information Bulletin without a supporting state-level restriction, the correct status is advisory only.
Caribbean, Jordan, UAE, and Qatar Airspace: What the Data Does and Does Not Show
High-volume search questions — why is Caribbean airspace closed, is Qatar airspace closed, is UAE airspace closed, what is the status of Jordan airspace — generally cannot be answered from headlines, and this dataset does not support blanket answers either. The FlySafe confirmed-event dataset covers 68 FIRs globally; it does not currently break out a Caribbean regional aggregate, and no confirmed 2026 events for Jordanian, Emirati, or Qatari FIRs appear in the top-ranked figures above. Where a specific FIR is not listed, no confirmed disruption data is currently available for it in this window — which is not the same as a guarantee of unrestricted operations.
The operationally correct answer to any "is X airspace closed" question is always the current NOTAM record for that FIR, checked at the time of flight planning. Regional closures are frequently partial (specific routes or altitude bands, i.e. restricted rather than closed), time-limited, or carrier-specific — distinctions that a yes/no headline cannot carry. The seismic and tropical-cyclone categories illustrate how routine such disruptions are: seismic activity produced 300 airspace-days in 2026 (led by MMFR at 223 days), and tropical cyclones produced 133 airspace-days (led by ZSHA at 86 days) — all of which ended, with normal operations resumed.
Why NOTAM-Only Monitoring Misses Most Confirmed Disruptions
Across FIRs with at least three confirmed events, flight-traffic data corroborated approximately 77% of events, while NOTAMs corroborated approximately 42%. A review process built solely on NOTAM feeds would therefore miss the majority of confirmed disruptions — a gap examined in detail in FlySafe's analysis of why NOTAMs miss most airspace disruptions in 2026.
The pattern is category-dependent. Volcanic-ash events are NOTAM-rich and traffic-poor; several other disruption profiles are the reverse. In SKED and WIIF, both corroboration channels reached 100% — 21 and 26 events respectively — showing that where traffic density and regulatory publication overlap, detection confidence is highest. The practical conclusion for operators: single-source monitoring, whatever the source, systematically under-detects.
Regulatory Context
Several frameworks govern how the disruptions in this dataset are published and managed:
- ICAO Annex 11 (Air Traffic Services) assigns responsibility for airspace organization and ATS provision within each FIR to the relevant state authority.
- ICAO Annex 15 (Aeronautical Information Services) and ICAO Doc 4444 (PANS-ATM) define how airspace status changes must be promulgated — the NOTAM system that corroborated 42% of confirmed events flows from these provisions. Details of the framework are maintained by ICAO.
- EASA Conflict Zone Information Bulletins (CZIBs) provide advisory risk information for the conflict-zone restriction category; current bulletins are published on the EASA CZIB page.
- EU Regulation 965/2012 (Air Operations) requires EU operators to assess route risks — including the categories above — within their management systems, consistent with ICAO Annex 19 (Safety Management).
- 14 CFR Part 91 and the FAA Aeronautical Information Manual govern US operator obligations regarding restricted and disrupted airspace; current US NOTAMs are searchable via the FAA NOTAM system.
Methodology & Provenance
- Source: FlySafe airspace-risk collectors; observation window 2026-01-01 through 2026-08-07.
- Confirmation standard: the FlySafe consensus engine requires at least two independent signals per event plus an attributed cause; detections with undetermined cause are excluded from all figures above.
- Inputs: public NOTAM feeds, EASA publications, 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.
- Metric: airspace-days (one FIR disrupted for one day). Cost figures, per-carrier routing data, and individual NOTAM references are not currently available in this dataset.
- Data as of: 2026-08-07.
FlySafe is not an operational authority. This bulletin is analytical, based exclusively on publicly available and independently verifiable data, and does not replace official NOTAMs, AIP entries, or state CAA guidance. Operational decisions must be based on current official sources.
Key Takeaway
The answer to "what is closing airspace in 2026" is, by airspace-days, primarily volcanic ash (57%), followed by conflict-zone restrictions (31%), with seismic activity, tropical cyclones, and other regulatory restrictions making up the remainder of the 4,443 airspace-days recorded across 534 confirmed events and 68 FIRs. Every confirmed disruption in the window has ended, averaging roughly 8.3 airspace-days each — but detection depends heavily on combining regulatory feeds with live traffic data, since neither source alone captures the full picture. FlySafe analysis shows that multi-signal confirmation is the difference between monitoring airspace and merely reading about it; the running year-to-date ledger is tracked in FlySafe's airspace-day loss reporting.
- Volcanic ash is the single largest driver of airspace disruption in 2026, accounting for 57% of all airspace-days lost — more than all other categories combined, and roughly double the share from conflict-zone restrictions (31%). Natural hazards overall (ash, seismic, cyclones) account for 67% of airspace-days, which inverts the common traveler assumption about what closes airspace.
- NOTAM-only monitoring captures less than half of confirmed disruption events: the article explicitly frames this as a structural gap, with flight-traffic corroboration serving as a necessary second detection layer.
- The top ash-affected FIRs (RPHI, UHMM, SEFG) show 0% flight-traffic corroboration despite 95–100% NOTAM corroboration, revealing that ADS-B-based detection is effectively blind to ash events in low-traffic-density airspace — the regulatory record carries the entire detection burden there.
- Disruptions are heavily concentrated mid-year: July alone produced 266 of 534 confirmed events year-to-date (~50%), suggesting a strong seasonal or geographic signal rather than a uniform baseline risk throughout the year.
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.