Is It Safe to Fly Over the Persian Gulf? EASA's Gulf Bulletin CZIB-2026-07R3 Explained: Bahrain, Kuwait, Doha, Emirates and Muscat FIRs

Of the six Middle East bulletins on EASA's conflict-zone list, the one covering the Persian Gulf and the Gulf of Oman is the strangest to read as a passenger. It tells European airlines not to fly over the waters of the Gulf at any altitude, and in the same breath says that flights into and out of airports in the same airspace may continue. Dubai, Doha, Abu Dhabi, Bahrain, Kuwait and Muscat are all inside the bulletin's area, and all of them are busy. So what exactly is being warned against, and is it safe to fly over the Persian Gulf?

This post goes through CZIB-2026-07R3 line by line: which flight information regions it covers, what the risk description actually says, why the recommendation draws a line between water and land and between overflights and arrivals, what changed in the latest revision, and what to look for on your own flight's route. It is the dedicated explainer for the Gulf bulletin, alongside the ones on the [Iraq](/blog/is-it-safe-to-fly-over-iraq-easa-iraq-airspace-bulletin-czib-2026-05-r2-baghdad-fir), [Lebanon](/blog/is-it-safe-to-fly-over-lebanon-easa-lebanon-bulletin-czib-2026-06-r2-beirut-fir), [Saudi Arabia](/blog/easa-saudi-arabia-airspace-bulletin-czib-2026-09-jeddah-fir) and [Jordan](/blog/easa-jordan-airspace-bulletin-czib-2026-08-r3-extended-16-november-what-changed) bulletins.

What CZIB-2026-07R3 covers

The bulletin applies to all altitudes and flight levels in five flight information regions: Bahrain (OBBB), Kuwait (OKAC), Doha (OTDF), Emirates (OMAE) and Muscat (OOMM). Between them those FIRs contain the whole of the Persian Gulf south of the Iranian coast plus the Gulf of Oman, and the airspace over Bahrain, Kuwait, Qatar, the United Arab Emirates and Oman themselves. If you are hazy on what an FIR is, the [flight information region explainer](/blog/what-is-a-flight-information-region-fir-explained) covers it; the short version is that it is the block of airspace one air traffic control authority is responsible for, and it usually extends well out over the sea.

It was first issued on 14 July 2026, has been revised three times, and in its current form is valid until 16 November 2026 unless EASA reviews it earlier. Like every CZIB it is addressed to EASA operators (airlines regulated under EU air operations rules) and to third-country operators flying to, from and within the EU under an EASA authorisation. It is advice to airlines, not an airspace closure, a distinction the post on [how EASA's Middle East bulletins work](/blog/easa-conflict-zone-bulletins-middle-east-explained) goes into.

What the risk description actually says

The description is unusually specific about where the danger is. It starts from the conflict between the United States and Iran and says the regional situation remains volatile. It then names three mechanisms. First, Iranian efforts to maintain control over the Strait of Hormuz, recurrent attacks on commercial vessels and the related US military actions create high risk over the waters of Bahrain, Kuwait, Qatar and the UAE, and over the Gulf of Oman west of longitude 58°E. Second, the presence of major US military facilities in the Gulf states increases the likelihood that those states could be directly exposed to Iranian missile and drone attacks, with the surrounding maritime airspace affected by overflights, interceptions and falling debris. Third, the heightened readiness of national and US air-defence systems raises the risk of misidentification, unintended engagement and collateral effects on civil aircraft.

Two further sentences explain why EASA treats this as a different kind of risk from a conventional closure. Military activity, it says, may occur with little or no warning in confined airspace, which shrinks the time available for tactical rerouting. And although the regional authorities have closed or restricted airspace at various stages of the conflict, the unpredictability and speed of military activity may challenge the timely implementation of such measures. In plain terms: the authorities might not be able to close the airspace fast enough, so airlines should not wait for them to.

The bulletin's own conclusion is that unpredictable military developments, combined with the possible use of missiles, drones, combat aircraft and air-defence systems, create a high risk to civil flights at all altitudes over the waters within the concerned airspace.

Water versus land, and overflights versus arrivals

The recommendations are where the bulletin splits the Gulf in two. For the waters of the Persian Gulf inside the Bahrain, Kuwait, Doha and Emirates FIRs, operators are told not to operate at any altitude, except to the extent necessary for arrivals at or departures from aerodromes within those FIRs. For the Gulf of Oman inside the Muscat FIR, the no-operate advice applies west of longitude 58°E at all altitudes, with no arrivals exception stated. Over the land territory of the five states, the advice is softer: exercise caution and take the potential risks into account.

The reasoning is in the description. The threat is concentrated over the water, around the Strait of Hormuz and the shipping lanes, where missiles, drones, interceptions and debris are most likely. The bulletin says explicitly that while risks over the waters remain high, operations necessary for arrivals and departures may be conducted with sufficient mitigation, provided they rest on an up-to-date risk assessment and continuous monitoring. Residual risks remain over land, which is why caution rather than avoidance is recommended there.

That is why your flight to Dubai still operates. An approach into Dubai or Doha crosses Gulf waters for minutes, with the airline's risk assessment behind it and the option of short-notice instructions from the state. What the bulletin targets is the long transit over the Gulf by flights that are not stopping there, which is a very different exposure.

• Over the waters of the Gulf (Bahrain, Kuwait, Doha, Emirates FIRs): do not operate, except as necessary for arrivals and departures.
• Over the Gulf of Oman west of 58°E (Muscat FIR): do not operate, at all altitudes and flight levels.
• Over the land territory of the five states: exercise caution and take the risks into account.
• Everywhere in the five FIRs: keep an up-to-date risk assessment and a high level of contingency planning, and be ready for short-notice instructions from the state authorities.
• Monitor aeronautical publications for the region and the European information-sharing platform on conflict zones, and follow national authority guidance.

What changed in R3

Not much, and that is itself the news. The R3 revision of 30 September 2026 did one thing: it extended the bulletin's validity to 16 November 2026. EASA's revision note states that no changes to the content or the recommendations were made. The Gulf bulletin therefore now shares its expiry date with the Iran, Iraq, Lebanon, Saudi Arabia and, since 14 October, Jordan bulletins, which means the whole Middle East set comes up for review on the same day.

An extension without a change in wording is a signal in its own right. When EASA judged the Jordan situation to have improved it said so in the text and softened the language. For the Gulf it extended the same high-risk description unchanged, which reads as an assessment that the maritime threat around Hormuz has not eased enough to revise.

So, is it safe to fly over the Persian Gulf?

For a passenger the honest answer has three parts. If you are flying to or from a Gulf airport on a European or EASA-authorised airline, your flight is operating inside the bulletin's explicit exception, with the airline required to have a current risk assessment and contingency plan. If you are transiting the Gulf on a European carrier, the airline is being told not to route over the water, so expect routings that hug the coast or avoid the Gulf, with the extra minutes that implies. If you are flying a Gulf carrier, or a carrier regulated somewhere else, the EASA bulletin does not bind it, and its own regulator's assessment and its own routing decisions apply.

The 58°E line in the Gulf of Oman is worth knowing for flights between the Gulf and India or South-East Asia. Longitude 58°E runs roughly north to south through the eastern part of Oman; airspace east of that line is outside the no-operate advice, which is why routes between Muscat or the UAE and the Indian subcontinent can turn south-east over Omani territory and then out over the Arabian Sea rather than running along the Iranian coast.

None of this makes an individual flight unsafe. It means that the airlines who follow EASA's advice are planning around a known risk, and the way to reassure yourself is to look at what your own flight actually does rather than at the headline.

How to check your own route

Open a flight tracker and look at the previous day's flight with your flight number. For a flight into Dubai, Doha, Abu Dhabi, Bahrain, Kuwait or Muscat, note where it crosses the coast and how long it spends over water; a descent that stays over land until the final approach is the mitigated pattern. For a transit flight, see whether the track runs over the Gulf or around it. The post on [reading a flight map for a healthy route](/blog/how-to-read-a-flight-map-healthy-route) explains what a reroute looks like on a map, and the [Europe to India routes](/blog/europe-to-india-routes-without-iranian-airspace) and [southern corridor](/blog/southern-corridor-egypt-saudi-arabia-flight-routes) posts show the alternatives airlines are using.

If a layover in the Gulf is itself the worry, the [safer alternatives to a Dubai layover](/blog/safer-alternatives-to-a-dubai-layover) post weighs the options honestly, including the point that the hubs are inside the exception precisely because the risk there is judged manageable with mitigation.

What to watch before 16 November

Six EASA Middle East bulletins now expire on the same day. The possibilities for the Gulf one are an extension unchanged (the pattern so far), an extension with softened wording (the Jordan pattern), a narrowing of the area (for example dropping the land-caution element or moving the 58°E line), or a lapse. Watch the revision-date column on EASA's conflict-zone list in the days before the 16th, and read the revision description before the headline: it is the one place EASA says in plain words what changed and why. We will cover the review here when it happens.