Middle East Airspace Closures, June 2026: How FlySafe Flagged Each FIR Ahead of the NOTAMs

When conflict closes airspace, the difference between a safe reroute and a scramble is timing — and granularity. Knowing "the Middle East is risky" helps no one dispatch a flight. Knowing which FIR is going dark, in what order, and how fast is the whole job. Here is how FlySafe handled the 6-7 June 2026 Middle East closures, end to end.

What happened

As the Iran-Israel-Lebanon-Gulf confrontation escalated — cross-border strikes, missile and drone activity over the Gulf and Levant — a cluster of FIRs closed or emptied within roughly 48 hours.

How FlySafe saw it

FlySafe scores every FIR's live overflight count against its own recent baseline, then corroborates before escalating. The wave moved from the periphery inward — and we tracked it one FIR at a time, with a sequence and a clock (see the timeline above): periphery first on 5 June, Syria on 6 June, the Iranian interior and Gulf approaches on 7 June, and the heavily GPS-jammed Tehran FIR reading last on 8 June.

Knowing "the Middle East is risky" helps no one dispatch a flight. Knowing which FIR is going dark, in what order, and how fast — that is the job.

Why it was not a false alarm

A traffic drop on its own can be a quiet hour or a data gap. FlySafe escalates a closure only when independent signals agree — live traffic, conflict news classified to the specific FIR, and prediction-market closure odds. On 6-7 June all three lined up, which is exactly what separates a real shutdown from noise.

Elevated before it closed

Across the affected FIRs, FlySafe's risk level was already standing High before the closures consolidated — a heads-up window, not a same-minute alarm. You can watch the live picture on the GPS-interference regional map.

The one place we were slower — and what we are doing about it

Our weakest read was the most heavily GPS-jammed airspace, the Tehran FIR, where spoofed and degraded positions make live traffic harder to trust — so our detection there lagged the rest of the region by about a day. We do not paper over that. A dedicated GPS-integrity feed — reading real ADS-B navigation-integrity rather than an inference — is now built and accumulating, specifically to close that gap.

What this is — and is not

This is real-time detection and short-horizon early warning built on live operational data, corroborated across sources. It is not a geopolitical forecast, and we do not claim to predict the politics. The value is speed and per-FIR precision: which airspace is going dark, in what order, a step ahead of the official notices. See how the scoring works in our methodology.