EASA Extends Its Jordan Airspace Bulletin to 16 November: What Changed in CZIB-2026-08-R3 and What It Means for Flights Over Amman
For two months the Jordan bulletin on EASA's conflict-zone list carried a different expiry date from its neighbours. Iran, Iraq, Lebanon, the Persian Gulf and Saudi Arabia all ran to 16 November 2026; Jordan's CZIB-2026-08 ran only to 16 October. That made it the first Middle East bulletin due to lapse since the summer, and the one to watch for a signal about where the region's aviation risk was heading. On 14 October 2026, two days before the deadline, EASA published revision 3 (CZIB-2026-08-R3), extended the bulletin to 16 November and rewrote the risk description.
This post explains what the new revision says, how it differs from the version it replaced, why EASA extended rather than withdrew it, and what it means in practice if you have a flight that crosses the Amman Flight Information Region in the next month. As always, the bulletin is an advisory to EU air operators, not a closure; the practical effect depends on what your airline does with it.
What CZIB-2026-08-R3 actually says
The bulletin covers the Amman FIR (OJAC) at all altitudes and flight levels, which is the whole of Jordanian airspace from the ground up. It applies to EASA operators (airlines regulated under EU air-operations rules) and to third-country operators flying to, from or within the EU under an EASA authorisation. The revision date is 14 October 2026 and the new validity is 16 November 2026, 'unless reviewed earlier'. The revision note is short: the validity was extended, and 'the content and recommendations have been revised to reflect the change in the risk level'.
The description is the part that changed. It still frames the risk as a consequence of the conflict between the United States and Iran, and still describes the regional situation as volatile, with 'significant fluctuations in the level of kinetic military activity affecting Jordanian airspace' and a history of calm periods followed by renewed attacks with little or no warning. But it then states something the earlier revisions did not: there has been no reported kinetic military activity affecting Jordanian airspace since 9 September 2026, which EASA says 'indicates an improvement in the security situation', while adding that the potential for renewed escalation means operators should keep contingency arrangements in place.
The threat picture itself is described in the past tense: during previous escalations, Iranian missile attacks and, to a lesser extent, drone attacks against assets in Jordan, together with the activation of air-defence systems, raised the risk of misidentification of civil aircraft, missile overflights, interception activity and falling debris. EASA's point is that the underlying factors behind that risk 'remain present' even though the activity has stopped, so the risk could rise again quickly if military operations resume.
What changed between R2 and R3
Three things, in order of importance for a passenger.
- The expiry moved from 16 October to 16 November 2026, bringing Jordan into line with the Iran, Iraq, Lebanon, Persian Gulf and Saudi Arabia bulletins, which all now expire on the same day. That alignment matters: it suggests EASA intends to review the whole Middle East set together in mid-November rather than country by country.
- The risk language softened. The earlier revisions described active and recurring threats; R3 records more than five weeks without reported kinetic activity and calls that an improvement. This is the first Middle East bulletin in the current cycle to say so explicitly.
- The recommendations did not change in kind. Operators are still told to take the potential risks into account, keep an up-to-date risk assessment and a high level of contingency planning, be ready for short-notice instructions from state authorities, and monitor aeronautical publications and the European conflict-zone information-sharing platform. There is no new 'do not operate' wording and there was none before.
Why extend a bulletin whose risk has fallen?
Because a Conflict Zone Information Bulletin is not a verdict that something bad is happening; it is a statement that a region carries a risk airlines must actively assess. EASA's own description of the process is that a bulletin is issued for airspace that the Integrated EU Aviation Security Risk Assessment Group has identified as high risk, or where there is a need to make information public. Withdrawing the Jordan bulletin after five quiet weeks would have told airlines the risk assessment was over. Extending it with revised wording tells them the risk is lower but the situation that produced it is unresolved, which is a more accurate message and the one that keeps contingency plans in place.
There is also a practical point in the bulletin that is easy to miss. During the earlier escalations, Jordan's own authorities did not publish conflict-related airspace restrictions, route closures or operational advisories. In other words, the warning that something had changed came from the events themselves, not from a NOTAM. EASA's recommendation that operators 'be prepared to comply with tactical deconfliction in the event of renewed kinetic activity' is a polite way of saying that if the attacks resume, crews may get instructions in the air rather than at the planning stage. That is why the bulletin stays active even in a calm month.
Is it safe to fly over Jordan right now?
The honest answer is the same as it was for Iraq and Lebanon when we covered their bulletins: EASA rates the airspace as carrying a risk that EU operators must assess and plan for, and leaves the decision to the operator. In practice, the bulletin itself notes that Jordan's authorities issued no conflict-related airspace restrictions or route closures during the earlier escalations, so the airspace stayed formally open; it sits on the corridor between the Mediterranean and the Gulf and is one of the routes airlines use when they avoid Iran. Whether a given airline overflew it during those periods was that airline's own decision, made with its own mitigations. What has changed in R3 is the direction of travel: the first official statement that the situation has improved.
If you want to know what your specific airline does, the bulletin does not tell you. Your airline's route decision is what matters, and the way to check it is to look at the actual routing of your flight number on recent days on a flight-tracking site, or to read the airline's travel-advisory page. Our guide to [checking whether a flight avoids conflict zones](/blog/how-to-check-if-your-flight-avoids-conflict-zones) walks through this, and the [Middle East alternative-routes post](/blog/alternative-flight-routes-avoiding-middle-east-airspace) explains the corridors airlines use when they do route around the region. Jordan is often part of the solution to avoiding Iranian airspace rather than part of the problem.
How Jordan fits the rest of the Middle East list in mid-October
As of 15 October 2026 EASA's active Middle East bulletins are: Saudi Arabia (CZIB-2026-09-R1, revised 9 October), Jordan (CZIB-2026-08-R3, revised 14 October), the Persian Gulf and Gulf of Oman (CZIB-2026-07R3), Lebanon (CZIB-2026-06-R2), Iraq (CZIB-2026-05-R2) and Iran (CZIB-2026-04-R2), every one valid to 16 November 2026, plus Syria (CZIB-2017-03R20, revised 1 October, valid to 30 November) and Yemen (to 30 April 2027). Jordan was the only one whose expiry was out of step; it no longer is. The six bulletins now share a review date, and 16 November is the next date to watch for the whole region.
The Jordan revision is also the only one of the six to describe an improvement. The Iran, Iraq and Lebanon bulletins were extended on 30 September without that language. If a similar sentence appears in the Iraq or Lebanon bulletins at the November review, that would be a strong signal that the region's assessment is moving in one direction; if Jordan's wording is tightened again, the opposite. The bulletin itself says EASA will keep monitoring 'with a view to assess whether there is an increase or decrease of the risk', so expect the next change to be in that wording rather than in a dramatic closure or withdrawal.
What this means for your flight
- Flights to and from Amman (Queen Alia International) and Aqaba are not restricted by the bulletin; it asks operators to assess the risk, and whether a particular airline flies is that airline's call.
- Flights that overfly Jordan between Europe and the Gulf, India or East Africa also continue. If your airline reroutes, it is more likely to be because of Iranian or Iraqi airspace than Jordanian.
- Flight times and prices are not directly affected by this revision. It changes the paperwork behind a decision airlines already made, not the decision.
- The real risk to a passenger from a bulletin like this is disruption, not danger: a sudden change in the region can mean rerouting, a technical stop or a cancellation. Our post on what happens when airspace closes mid-flight and the one on your refund and rebooking rights when a flight is cancelled for an airspace closure cover what to do if that happens.
- If you are nervous, read the airline's own advisory, look at the flown routes on a tracker, and remember that a bulletin that has just been softened is the opposite of a warning that things are getting worse.
Where to check the bulletin yourself
The list of active and withdrawn bulletins is on EASA's Conflict Zones Advisories page; each entry links to the full text with its revision history, and the page has a CSV, JSON and RSS feed if you want to be told when a bulletin changes. Our explainer on [how EASA's Middle East bulletins work](/blog/easa-conflict-zone-bulletins-middle-east-explained) covers how to read one, the earlier [Jordan advisory post](/blog/easa-jordan-airspace-advisory-what-travelers-should-know) covers the original bulletin, and the [post on NOTAMs](/blog/what-is-a-notam-how-to-read-airspace-closure-notices) covers the operational notices that sit alongside them. SafeRoutes tracks the EASA list daily; when the November review lands, we will cover what changed, as we did for Jordan today.