EASA Revises Its Saudi Arabia Airspace Bulletin (CZIB-2026-09-R1, 9 October 2026): Riyadh Airport Attacks, a Second Avoid Area, and What Changed

Nine days after it issued a new Conflict Zone Information Bulletin for the airspace of Saudi Arabia, EASA has revised it. CZIB-2026-09-R1 was published on 9 October 2026 with a one-line revision note: the description was updated and the recommendations revised to reflect the change in the risk area. That understates what is new. The revised text names Riyadh's airport as a recent target, says attacks have shifted towards aviation infrastructure, and replaces the single avoid area of the original bulletin with two.

We covered the [original 30 September bulletin](/blog/easa-saudi-arabia-airspace-bulletin-czib-2026-09-jeddah-fir) in detail. This post is only about what changed in R1 and what it means if you are flying to, from or over Saudi Arabia in the coming weeks. As always, the factual content comes from the bulletin text on EASA's public conflict-zone page; where we interpret, we say so.

The headline changes in R1

• Riyadh and its airport are named. New text says that within the broader escalation of late September and early October, repeated missile and drone attacks targeted the Riyadh area, including its airport. The original bulletin mentioned Riyadh only as one of several areas that had been struck.
• Attacks on aviation infrastructure, and risk on the ground. R1 says attacks during this period showed a greater focus on aviation infrastructure than previously, increasing risks to aircraft on the ground and during take-off and landing in the affected areas. That is a new category of risk in this bulletin; the original was about overflight.
• Medina joins the list. The areas where deep strikes have been demonstrated now read Riyadh, Tabuk, Medina and Yanbu. Medina was not in the 30 September text.
• A second avoid area. The do-not-operate recommendation now defines two areas by waypoint lines rather than one. Details below.
• Validity unchanged. R1 is still valid until 16 November 2026 unless reviewed earlier, and still applies to the whole Jeddah FIR (OEJD) at all altitudes. Revisions inside a validity period are normal; our [guide to EASA's Middle East bulletins](/blog/easa-conflict-zone-bulletins-middle-east-explained) explains the R-numbering.

How the do-not-operate area changed

The 30 September bulletin told EU operators not to operate within the part of the Jeddah FIR enclosed by the FIR boundary and a line through the waypoints RIBOK, BOSUT, ISLAM, DEKLO, OBSAM and SILPA. Reading it alongside the bulletin's own description of where exposure was greatest, we took that to be the southern and south-western strip nearest Yemen.

R1 keeps that idea but redraws it. The first line is now RIBOK, BOSUT, MIGDA, RAGNO, MIXUG, DEKLO, OBSAM and SILPA: the same start and end points, with the middle of the line routed through different waypoints. The second, entirely new line runs ULBAM, TOTEB, DURMA, LAKSO and SOLAT. Each line, together with the FIR boundary, encloses an area in which EASA operators should not fly at any altitude.

EASA does not publish a map with the bulletin, so we cannot tell you precisely where the second polygon sits, and we will not guess at coordinates. What we can say is what the text implies. The new paragraphs are about the Riyadh area and about aviation infrastructure being targeted; the only structural change to the recommendations is the addition of a second avoid area. Our reading, which is an interpretation, is that the revision formalises an avoid area beyond the southern border strip in response to the central-region attacks. Dispatchers and airline security teams plot the exact shapes from the published points; passengers should take from it that the hard no-go zone is no longer a single southern block.

For the rest of the FIR the instruction is unchanged: exercise caution and take potential risks into account, keep an up-to-date risk assessment and a high level of contingency planning, be prepared for short-notice instructions from the Saudi authorities, and monitor aeronautical publications from Saudi Arabia, its neighbours and the operator's own state.

Why the aviation-infrastructure line matters more than it looks

Most conflict-zone bulletins are about the sky: the risk that an airliner at cruising altitude is misidentified by air defences, or is in the path of a missile, an interceptor or falling debris. All of that remains in R1, in the same words as before. What is new is a sentence about aircraft on the ground and during take-off and landing in the affected areas.

That shifts the question an airline has to answer. Avoiding a polygon at altitude is a routing problem; most of the kingdom's east-west traffic can be moved north or south of a shape on a map. Risk during take-off and landing at a named airport is a destination problem. An operator cannot route around its own arrival. In practice this is the kind of language that pushes airlines to review not just overflights but schedules, night operations and ground time at the airports concerned, and to lean harder on the Saudi authorities' own tactical measures, which the bulletin again credits, including Emergency Security Control of Air Traffic.

None of this means flights to Riyadh are stopping. The bulletin does not close anything, does not name any airline, and applies only to EASA operators and the third-country operators EASA authorises for EU flights. It is a risk assessment and a set of instructions for the operators it covers.

What it means if you are flying

If your flight starts or ends in Riyadh, Jeddah, Medina, Tabuk or Yanbu with a European airline, expect the airline to be following this bulletin and to have a plan for it. That can mean schedule changes at short notice, longer taxi or holding times while military activity is deconflicted, or in some cases cancellations. Our post on [refund and rebooking rights when airspace closes](/blog/flight-cancelled-airspace-closure-refund-rebooking-rights) explains what you are owed in each case.

If your flight merely crosses Saudi airspace, the change is mostly invisible to you. The main east-west corridors in the north of the kingdom are outside the areas described, and the [southern corridor over Egypt and Saudi Arabia](/blog/southern-corridor-egypt-saudi-arabia-flight-routes) that many Europe-to-Asia flights use to avoid Iran remains in use, with the caution-and-planning requirement attached. Airlines from outside the EU follow their own regulators, whose guidance may be stricter or looser.

If you want to see for yourself, a route map or a live flight-tracking site will show whether your airline's recent flights to the same destination are still operating and whether they have changed track. Our explainer on [reading a flight map for a healthy route](/blog/how-to-read-a-flight-map-healthy-route) shows what to look for; a sudden detour or an unusual holding pattern is more informative than any headline.

Where this sits among the other bulletins

The Saudi revision is the latest in a dense run of changes. On 30 September EASA revised its Iran, Iraq, Lebanon and Persian Gulf bulletins to run to 16 November 2026 and Jordan's to 16 October; on 1 October the [Syria bulletin](/blog/easa-syria-airspace-bulletin-czib-2017-03r20-damascus-fir-explained) was revised to 30 November. With Saudi Arabia now on R1 nine days after issue, the pattern is of an agency updating frequently rather than waiting for scheduled review dates, which is itself a signal about how fast the picture is moving.

For travellers the practical conclusion is the same one we keep returning to: the airline, not the news, decides your route, and the airline is reading these bulletins. Check your flight status the day before and the morning of travel, keep the airline's app notifications on, and treat a schedule change as the system working rather than failing. We will update this post if EASA revises the bulletin again before 16 November.