Pricing Search Start free trial
FlySafe Sentinel MONITORING VERIFIED CHECKED 15 Nov 2026 05:17 UTC PUBLISHED 25 Aug 2026 11 SOURCES

Aggregated from EASA Conflict Zone Information Bulletins, FAA SFARs, national NOTAM publications, and airline operational disclosures. Status can change within hours. Operators must verify through official channels before filing.

Middle East Airspace
Live status & airspace monitoring

The Middle East and Persian Gulf region continues to operate under elevated airspace disruption pressure across 2026. Following the February 2026 coordinated closure of twelve Flight Information Regions, rolling restrictions, precautionary closures, and GPS interference advisories have persisted across the region. This briefing summarises current FIR-level status and active regulatory bulletins.

Middle East airspace status today

As of 18 November 2026, EASA lists 8 active Conflict Zone Information Bulletins (CZIBs) for this region: Iran (until 31 January 2027); Iraq (until 31 January 2027); Jordan (until 31 January 2027); Lebanon (until 31 January 2027); Persian Gulf and Gulf of Oman (until 31 January 2027); Saudi Arabia (until 31 January 2027); Syria (until 30 April 2027); Yemen – Sana’a Flight Information Region (until 30 April 2027).

A CZIB is a safety recommendation to operators, not a closure. Closures are published as NOTAMs by national authorities, so read the current NOTAM for the FIR. FlySafe publishes FIR-level status, not advice on individual flights. See closed airspace today and the EASA CZIB list.

Current status
RESTRICTED — Tehran FIR (OIIX) traffic ~45% below baseline since 2026-08-22; OMA

Executive summary

Since the previous review, Emirates FIR (OMAE) has returned to normal traffic levels (91 aircraft vs a 7-day baseline of 84.3) per FlySafe Sentinel traffic anomaly detection, retrieved 2026-08-25T05:00:16Z, reversing the effective closure reported in the prior briefing, while Tehran FIR (OIIX) remains restricted at approximately 45% below baseline (7 vs 12.8 aircraft) with a full-closure signal detected 2026-08-22. Tel Aviv FIR (LLLL), Bahrain FIR (OBBB) and Amman FIR (OJAC) continue at normal traffic levels, and Kuwait FIR (OKAC), Baghdad FIR (ORBB) and Sanaa FIR (OYSC) show negligible or no monitored overflight traffic against near-zero baselines. The single signal to watch in the next review window is publication of a formal NOTAM for OIIX to confirm the legal basis of the restriction; live NOTAM data not currently accessible; status pending verification through next review.

FIR-by-FIR status

ICAO Status Last change Source Retrieved
OIIX Restricted — traffic approximately 45% below baseline (7 vs 12.8 aircraft); full-closure signal detected 2026-08-22 FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
OMAE Advisory — normal traffic (91 vs 84.3 baseline); mid-August anomaly resolved 2026-08-19 FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
LLLL Advisory — normal traffic (24 vs 21.4 baseline) No sustained anomaly FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
OBBB Normal operations (49 vs 41.5 baseline) No sustained anomaly FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
OJAC Normal operations (24 vs 21.2 baseline) No sustained anomaly FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
OKAC NO RECENT DATA — negligible monitored traffic (baseline 0.4); live NOTAM access would unblock — FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
ORBB NO RECENT DATA — no monitored overflight traffic (baseline 0.1); live NOTAM access would unblock — FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z
OYSC NO RECENT DATA — no traffic baseline available; live NOTAM access would unblock — FlySafe Sentinel traffic anomaly detection 2026-08-25T05:00:16Z

Regulatory context

EASA Conflict Zone Information Bulletins (CZIBs) carry the force of a safety advisory, not a regulatory mandate, per the EASA CZIB framework; no specific in-force CZIB ID for these FIRs was captured in this review. For EU-registered operators, EU Regulation 965/2012 (ORO.GEN.110) requires the operator to conduct and document a conflict-zone risk assessment before overflight. US-registered operators remain subject to 14 CFR §91.703, which requires compliance with ICAO Annex 2 and the regulations of the state whose airspace is used when operating outside the United States. Carrier scope is therefore jurisdiction-specific: EASA advisories bind no operator by force of law, while operator-state risk-assessment duties apply to EU carriers under 965/2012 and to US carriers under §91.703. Live NOTAM data not currently accessible; status pending verification through next review. AIP entries for this FIR not currently captured; refer to state authority directly.

Source lineage

  1. FlySafe Sentinel traffic anomaly detection (FIR traffic snapshot) retrieved 2026-08-25T05:00:16Z
  2. FlySafe Sentinel FIR closure detection (proxy-traffic signals) retrieved 2026-08-25T05:00:56Z
  3. FlySafe FIR registry (FIR metadata) retrieved 2026-08-25T05:00:57Z
  4. EASA Conflict Zone Information Bulletin portal retrieved 2026-08-25T05:00:57Z
  5. AIRAC current cycle 2608 retrieved 2026-08-25T05:00:58Z

Update Log

  • 2026-08-25 Status verified. Source lineage refreshed.
  • 2026-05-26 Status verified. Source lineage refreshed.
  • 2026-05-22 Status verified. Source lineage refreshed.
  • 2026-05-19 Status verified. Source lineage refreshed.
  • 2026-05-09 Migrated to FlySafe Sentinel continuous monitoring.
  • 2026-04-21 Briefing initialised. FIR status table updated. Three EASA CZIBs remain active across OIIX, ORBB, OSDI. UAE precautionary closure count updated to four for March 2026.

    Middle East Airspace — Frequently Asked Questions

    Common search queries answered with current status, FIR codes, and source citations.

    Is Middle East airspace open currently?
    Status differs by FIR. As of 18 November 2026, EASA lists active Conflict Zone Information Bulletins for Iran (until 31 January 2027); Iraq (until 31 January 2027); Jordan (until 31 January 2027); Lebanon (until 31 January 2027); Persian Gulf and Gulf of Oman (until 31 January 2027); Saudi Arabia (until 31 January 2027); Syria (until 30 April 2027); Yemen – Sana’a Flight Information Region (until 30 April 2027). A CZIB is a safety recommendation to operators, not a closure. Closures are published as NOTAMs by national authorities and can last only hours, so read the current NOTAM for the FIR.
    Is it safe to fly to Dubai currently?
    FlySafe does not provide travel advice or rate individual flights. The EASA bulletin in force for the area: Persian Gulf and Gulf of Oman (until 31 January 2027). UAE airspace had four precautionary closures of 1–6 hours each during March 2026. Check your airline and official channels before travel.
    Which Middle East areas have active EASA CZIBs currently?
    As of 18 November 2026, 8 bulletins are active for the region: Iran (until 31 January 2027); Iraq (until 31 January 2027); Jordan (until 31 January 2027); Lebanon (until 31 January 2027); Persian Gulf and Gulf of Oman (until 31 January 2027); Saudi Arabia (until 31 January 2027); Syria (until 30 April 2027); Yemen – Sana’a Flight Information Region (until 30 April 2027). The full bulletin texts are published on the EASA website.
    Are commercial flights affected in the Persian Gulf?
    An EASA bulletin is active: Persian Gulf and Gulf of Oman (until 31 January 2027). Effects differ by FIR and can change with limited notice. FlySafe publishes FIR-level status, not statements about individual carriers.
    When was the Middle East airspace status last verified?
    The EASA bulletin list on this page was refreshed on 18 November 2026. The Last Verified badge at the top of the page shows the most recent automated source check of the rest of the briefing.
    Share this

    FlySafe provides automated computation of numerical indices from publicly available data. Indices are raw computational output and do not represent opinions, assessments, recommendations, or advice of any kind. They do not replace official NOTAMs, SIGMETs, AIPs, or communications from aviation authorities. Operators must independently verify current airspace status through official channels. See Terms of Service for full details.