EASA CZIB 2026-03 — Middle East & Persian Gulf
Issued: 28 Feb 2026 · Revisions: R1–R4 (March) · Source: EASA.europa.eu · Airways Magazine · AirMed&Rescue
On 28 February 2026, EASA issued Conflict Zone Information Bulletin CZIB 2026-03 covering Middle East and Persian Gulf airspace, with initial validity until 2 March. The bulletin was extended through four formal revisions over the following weeks: R1 (2 → 6 March), R2 (6 → 11 March), R3 (11 → 18 March), and R4 (18 → 27 March). The R4 revision (18 March 2026) was based on an assessment by the Integrated EU Aviation Security Risk Assessment Group (IRAG) and reflected observed conflict dynamics including shifts in military-activity geographic distribution. Affected airspace under R4: Bahrain, Iran, Iraq, Israel, Jordan, Kuwait, Lebanon, Oman, Qatar, UAE, and Saudi Arabia's Jeddah FIR.
Revision timeline
| Revision | Issue date | Extended validity |
|---|---|---|
| Initial (2026-03) | 28 Feb 2026 | Through 2 March 2026 |
| R1 | 2 March 2026 | Extended through 6 March |
| R2 | 6 March 2026 | Extended through 11 March |
| R3 | 11 March 2026 | Extended through 18 March |
| R4 | 18 March 2026 | Extended through 27 March (continues thereafter) |
Source: EASA newsroom + official CZIB PDF publications (cited in Sources below).
What R4 changed (18 March 2026)
The Revision 4 issued on 18 March 2026 was the most substantive update in the cycle. Key elements per EASA's published bulletin:
- →IRAG assessment basis. The revision is based on an assessment by the Integrated EU Aviation Security Risk Assessment Group (IRAG) and reflects "observed conflict dynamics," including shifts in level and geographic distribution of military activities.
- →Saudi Arabia and Oman recommendations revised. R4 specifically updated EASA recommendations concerning these two states' airspace.
- →"Avoid all altitudes" guidance. EASA advised operators to avoid all altitudes and flight levels within the affected airspace.
Affected airspace under R4
The full geographic scope of EASA's "avoid all altitudes" advice as of 18 March 2026 Revision 4:
FIR codes added for cross-reference; not all states have a single FIR. Some airspace dimensions (altitudes, sectors) may have specific carve-outs per the bulletin text.
What CZIBs do and don't do
- →CZIBs are advisory, not mandatory. EASA Conflict Zone Information Bulletins provide formal risk-based guidance to EU operators. They do not legally compel rerouting; operator decisions remain the carrier's responsibility under their AOC framework.
- →National AOC implications. EU member-state civil aviation authorities incorporate CZIBs into their own oversight. EU-licensed operators effectively comply.
- →Non-EU carriers reference CZIBs too. CZIBs are publicly available and widely consulted; major non-EU carriers often align routing with active CZIBs as best-practice.
- →Periodic revision is normal. CZIBs are designed to be revised as conditions evolve. Most active CZIBs see multiple revisions through their lifecycle.
Comparison with FAA SFAR
EASA CZIB is the European counterpart to the US FAA's Special Federal Aviation Regulations (SFAR). Differences in scope and force:
| Dimension | EASA CZIB | FAA SFAR |
|---|---|---|
| Force | Advisory | Regulatory (binding for US-registered) |
| Scope | EU operators primarily | US-registered carriers |
| Issuance pace | Reactive (days/weeks) | Slower (rulemaking process) |
| Revision pattern | Frequent (R1-R4 over weeks) | Less frequent, more durable |
Sources
- EASA — official CZIB 2026-03 publications and revisions R1, R2, R3, R4 on easa.europa.eu
- EASA Newsroom — "EASA extends duration of CZIB for Middle East and Persian Gulf" + subsequent extension announcements
- Airways Magazine — "EASA Revises Middle East/Persian Gulf Conflict-Zone Bulletin"
- AirMed & Rescue — "EASA extends Middle East conflict zone bulletin amid ongoing aviation risks"
Related
For airlines, OTAs, insurance underwriters
FlySafe integrates EASA CZIB status (active/revised/lifted) into airspace risk scoring. Real-time tracking of all active CZIBs across covered FIRs via API.
Request sandbox API key →