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

NOTAM Aviation Data: 2026's Most-Disrupted FIRs Ranked

373 confirmed aviation disruptions in 2026's 61 most-disrupted FIRs. Learn why NOTAM data alone misses critical operational realities.

← All data stories

By: FlySafe Editorial

Written for Dispatchers Risk Managers
NOTAM Aviation Data: 2026's Most-Disrupted FIRs Ranked

Between 1 January and 24 July 2026, FlySafe airspace-risk collectors recorded 373 confirmed airspace-disruption events across 61 Flight Information Regions (FIRs), together accounting for 2,672 airspace-days of lost or constrained operation. That year-to-date total is the reference figure for everything that follows. The dataset counts only confirmed events — each backed by at least two independent signals and an attributed operational cause — while detections with an undetermined cause are excluded. For flight-planning teams that rely on NOTAM (Notice to Air Missions) feeds as their primary picture of airspace availability, the ranking below carries a second, quieter finding: NOTAM aviation notices alone did not surface the majority of these confirmed disruptions.

This bulletin reports disruption metrics only. It does not assign political or geographic reasons to any FIR, and it does not publish a live open or closed status for individual airspace. Analysis is based on publicly available data only.

The Year So Far: 2,672 Airspace-Days Across 61 FIRs

The 373 confirmed events resolve into an average confirmed disruption of roughly 7.2 airspace-days. All 373 have since ended, and 213 of them closed within the most recent 30-day period, which indicates a high turnover of short-to-medium duration events rather than a small number of prolonged full closures.

Concentration matters more than the headline count. A relatively small group of FIRs absorbed a disproportionate share of the 2,672 airspace-days. The table below ranks the most-disrupted FIRs by airspace-days for the window, alongside the share of each FIR's events that were independently corroborated by flight-traffic observation and by published NOTAMs.

Most-Disrupted FIRs by Airspace-Days (2026 YTD)

Rank FIR Events Airspace-days Flight-traffic corroboration NOTAM corroboration
1 Damascus FIR (OSTT) 44 406.0 43% 55%
2 RPHI 24 332.0 0% 92%
3 Tehran FIR (OIIX) 42 274.0 79% 48%
4 MMFR 15 223.0 100% 100%
5 UHMM 16 185.0 0% 94%
6 WIIF 12 176.0 100% 100%

Source: FlySafe airspace-risk collectors, confirmed events only, as of 24 July 2026.

Two patterns stand out. First, event count and airspace-days do not track one another cleanly: Damascus FIR (OSTT) led on both events (44) and airspace-days (406.0), but RPHI reached the second-highest airspace-day total (332.0) from far fewer events (24), implying longer average durations per event. Second, the corroboration columns diverge sharply. RPHI and UHMM show 0% flight-traffic corroboration but very high NOTAM corroboration (92% and 94%), whereas MMFR and WIIF were corroborated by both signals in 100% of events. That divergence is the substantive detection finding, examined below.

The Monthly Trend: A Steep Second-Quarter Rise

Confirmed events were not distributed evenly across the year. The monthly count moved as follows:

The first quarter was quiet, with March recording a single confirmed event. Volume then climbed steeply from April into a June peak of 143 confirmed events. July's figure of 115 covers only the first 24 days of the month and is therefore a partial count; it should not be read as a month-over-month decline until the full month is closed. The bulletin does not forecast future months and does not speculate on the drivers of the second-quarter rise.

The Detection Signal-Gap: Why NOTAM-Only Review Misses Disruptions

Across FIRs with at least three confirmed events, flight-traffic observation corroborated roughly 75% of events, while NOTAMs corroborated roughly 42%. In practice, a review process that depends on NOTAMs alone would have missed the majority of confirmed disruptions in this dataset.

The mechanism is visible in the ranking table. Some FIRs — RPHI and UHMM — were captured almost entirely through NOTAMs, with no flight-traffic corroboration recorded. Others — Tehran FIR (OIIX) at 79% flight-traffic and 48% NOTAM — were seen more clearly through observed traffic than through published notices. The two signals are complementary, not redundant: neither source, used in isolation, produced a complete picture of where airspace-days were being lost. FlySafe has examined this gap in more detail in a companion analysis of how NOTAMs miss most aviation airspace disruptions in 2026.

For dispatch and flight-planning teams, the operational implication is procedural rather than alarming: cross-referencing published notices against observed traffic patterns closes a coverage gap that a single-source workflow leaves open. NOTAMs remain the authoritative regulatory instrument. The finding is that they are not, on their own, a complete surveillance layer.

Cause-Category Mix (Neutral Operational Categories)

The 2,672 airspace-days break down across neutral operational categories as follows:

Volcanic ash accounted for the largest share of lost airspace-days despite a smaller event count than the conflict-zone category, again reflecting longer average durations. Conflict-zone restrictions produced the highest number of individual events (161) at a lower airspace-day-per-event ratio. These are operational classifications only; the bulletin does not attribute any cause beyond the neutral category and does not name a political or geographic reason.

"Is This Airspace Closed?" — Reading Status Correctly

Public search interest around airspace availability tends to cluster on specific regions, with recurring questions such as why is Caribbean airspace closed, whether UAE airspace is closed, whether Qatar airspace is closed, and whether Canada airspace is closed. Two points apply to all such questions.

First, none of those regions appear among the most-disrupted FIRs by airspace-days in the current window, and this bulletin does not publish a live open or closed readout for any individual FIR. A specific status must be confirmed from that FIR's current NOTAMs and AIP, not inferred from a ranking or from search-trend interest.

Second, the terminology carries precise meaning that general reporting often blurs:

A "Caribbean airspace closed" or "UAE airspace closed" query, in operational terms, is answerable only against the current published status of the specific FIR involved. The correct source is always the primary NOTAM or AIP entry, read at the time of flight.

Regulatory Context

Several frameworks govern how these disruptions are notified and how operators must respond. They are cited here as the relevant regulatory scaffolding, not as specific article text.

Primary regulatory texts are maintained by the responsible authorities, including ICAO and the FAA. Where this bulletin and those sources differ, the primary source governs.

Key Takeaway

For 2026 to date, airspace disruption has been concentrated: a small set of FIRs — led by Damascus FIR (OSTT) at 406.0 airspace-days — accounted for a large share of the 2,672 airspace-days lost across 61 FIRs. Volume rose sharply through the second quarter to a June peak. The most actionable finding for planning teams is the detection signal-gap: with flight-traffic corroborating roughly 75% of events against NOTAMs' roughly 42%, a NOTAM-only workflow leaves real disruptions unseen. Combining published notices with observed traffic is the practical correction.

Methodology & Provenance

FlySafe's consensus engine requires at least two independent signals per event before it is confirmed, plus an attributed operational cause; undetermined-cause detections are excluded. 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. The measurement window is 1 January 2026 to 24 July 2026. All figures in this bulletin are as of 24 July 2026 and reflect confirmed events only. July's monthly figure is a partial count through 24 July.

Disclaimer

FlySafe is not an operational authority. Nothing in this bulletin constitutes an airspace clearance, a flight-planning authorization, or a substitute for official NOTAMs, AIP entries, or state civil aviation authority guidance. Operators, dispatchers, and flight crews must consult primary sources before flight. Analysis is based on publicly available, independently verifiable data only. For FIR-level monitoring that pairs published notices with observed flight-traffic corroboration, FlySafe maintains continuous airspace-risk surveillance across the regions covered above.

✦SqueezeAI
  1. NOTAM feeds alone did not surface the majority of the 373 confirmed disruptions: for high-traffic FIRs like Tehran (OIIX), NOTAM corroboration reached only 48%, meaning teams relying solely on NOTAMs would miss roughly half of confirmed events in that airspace.
  2. Event count and airspace-days diverge significantly: RPHI reached 332 airspace-days from only 24 events versus Damascus FIR's 406 days from 44 events, meaning duration per event — not frequency — is the dominant risk metric for some FIRs.
  3. The corroboration signal split reveals two distinct detection profiles: RPHI and UHMM show 0% flight-traffic corroboration alongside 92–94% NOTAM corroboration, while MMFR and WIIF are confirmed by both signals 100% of the time — indicating that no single signal type reliably covers all FIRs.

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.