FlySafe was not operational during this event. This analysis reconstructs publicly available signals — to demonstrate how predictive airspace intelligence could have provided advance warning.
Jordan–Iraq–Iran Cascade Closure
April 13-14, 2024 — Domino FIR Shutdown
When Iran launched Operation True Promise on April 13, 2024, the 170+ drones didn't fly directly to Israel. They transited Iraqi airspace (ORBB), then Jordanian airspace (OJAC), before entering Israeli airspace (LLLL). The flight time for slow-moving Shahed-136 drones: approximately 4-5 hours across 1,600km. This meant three sovereign FIRs had to close sequentially as the drone swarm progressed westward. Iraq closed ORBB first. Jordan closed OJAC 30 minutes later. Israel closed LLLL approximately 60 minutes before impact. Lebanon closed OLBA preemptively. The cascade pattern was unprecedented — weapons transiting commercial air corridors in real-time.
What Happened
On the night of April 13–14, 2024, Iran launched Operation True Promise — its first direct large-scale military strike against Israeli territory. The attack employed a deliberately layered, sequenced weapons package: more than 170 Shahed-136 and Shahed-238 loitering munitions departed from launch sites near Ilam and Kermanshah in western Iran, followed by approximately 30 Paveh land-attack regional military systems and over 120 regional military systems of the Emad and Ghadr families. The combination was designed to overwhelm layered air defences through timing convergence, but it also created an unprecedented aviation crisis across four sovereign flight information regions simultaneously.
The drones, flying at approximately 185 km/h, required a transit of 4–5 hours to cover the roughly 1,600 km between their launch sites and Israeli airspace. That slow transit was the mechanism that turned a single military event into a cascading, rolling airspace shutdown across the Middle East. As each swarm element crossed from one FIR into the next — ORBB (Baghdad FIR, Iraq), then OJAC (Amman FIR, Jordan), then toward LLLL (Tel Aviv FIR, Israel) — each state sequentially closed its sovereign airspace, propagating a domino effect that ultimately blacked out the central Middle East corridor for commercial aviation for more than six hours.
- 170+ Shahed-136/238 loitering munitions — ~185 km/h, ~1,600 km range transit
- 30+ Paveh regional military systems — subsonic, terrain-following, faster than drones
- 120+ Emad/Ghadr regional military systems — medium-range, 8–12 min flight time
- ORBB — Baghdad FIR (Iraq): first closure, drone entry point
- OJAC — Amman FIR (Jordan): closed ~30 min after ORBB, active interception
- LLLL — Tel Aviv FIR (Israel): pre-impact closure ~60 min before strike
- OLBA — Beirut FIR (Lebanon): preemptive closure, conflict spillover risk
Early Signals
The April 13 attack did not emerge without precursor signals. In the weeks prior, a compounding sequence of geopolitical escalation events produced a threat environment that informed analysts and multi-source intelligence channels had flagged as high probability for Iranian kinetic response. Any airspace risk system monitoring the full signal stack — not just active NOTAMs — may have registered an actionable alert window of 24–72 hours before the first drone crossed into ORBB.
An Israeli cross-border aerial action struck the Iranian consular annex in Damascus on April 1, claiming the lives of two military generals including Brigadier General Mohammad Reza Zahedi. Iran publicly pledged a direct retaliatory strike — an explicit, named threat against Israeli territory, not a proxy response. This signal alone elevated LLLL, OJAC, and ORBB threat posture to critical.
Open-source intelligence and satellite imagery in the 48–72 hours before the attack indicated unusual logistics and fuel movements near western military forces Aerospace Force sites — the same provinces from which Shahed-136 drone launches ultimately originated. Regional aviation authorities received informal diplomatic warnings through back-channel contacts.
The USS Arleigh Burke–class destroyers USS Carney and USS The Sullivans repositioned into the Eastern Mediterranean in the days prior to April 13, a movement visible to maritime tracking services. US Central Command publicly stated forces were being pre-positioned for a potential Iranian strike. This sovereign military repositioning was a direct, observable precursor to imminent airspace disruption.
Israeli authorities issued civilian guidance in the hours before the attack commenced. Ben Gurion Airport (LLBG) operations staff had already begun contingency planning for airspace closure. Several carriers operating into Tel Aviv rerouted or delayed afternoon and evening departures before the formal NOTAM closure was issued — a behavioral signal detectable in ADS-B traffic pattern analysis.
Iraq's Baghdad FIR had already been flagged in the 2023 IATA safety assessment as a medium-risk transit airspace due to proximity to Iranian launch corridors and persistent conflict activity in northern Iraq. The baseline risk was well-documented — what April 13 demonstrated is that ORBB functions as the geographic entry point for any Iranian westward strike package, making its closure a leading indicator of downstream FIR disruptions.
Timeline
Israeli cross-border aerial action destroys Iranian consular annex in Damascus, killing two military generals. Iran's supreme leader and military publicly vow direct retaliation against Israeli territory — the clearest pre-event threat signal of the sequence. LLLL, OJAC, ORBB FIR threat postures should have been elevated immediately by any systematic risk model.
US military repositions Arleigh Burke–class destroyers into Eastern Mediterranean. White House and Pentagon brief congressional leaders that an Iranian attack is imminent. Multiple major carriers — including Lufthansa, Air France, and others — begin voluntarily suspending or rerouting Tel Aviv services ahead of any formal NOTAM closure.
Launch confirmed. Shahed-136/238 drones depart from Ilam and Kermanshah provinces, western Iran. Simultaneously, Paveh regional military systems launch. At 185 km/h, the drone swarm faces a 4–5 hour transit before reaching Israeli airspace. regional military systems launches will begin later, timed for near-simultaneous impact convergence.
ORBB (Baghdad FIR) closes as drone swarm enters Iraqi airspace. Iraqi authorities issue NOTAMs restricting the FIR to emergency traffic. Commercial flights transiting Iraq — including overflights between Europe/Gulf and South/Southeast Asia — immediately face rerouting. Flights divert around ORBB to the south over Saudi Arabia (OEJD, OERK sectors) or are held at origin airports.
OJAC (Amman FIR, Jordan) closes approximately 30 minutes after ORBB as the drone swarm crosses the Iraq–Jordan border. Jordan's Royal Air Force deploys F-16s and actively intercepts Shahed-136 drones over Jordanian territory — one of only a handful of historical instances of a third-party state engaging Iranian operational events in its own airspace. OLBA (Beirut FIR, Lebanon) issues preemptive closure simultaneously, citing conflict spillover risk.
LLLL (Tel Aviv FIR, Israel) formally closes approximately 60 minutes before projected drone impact, as the swarm approaches from Jordanian airspace. Ben Gurion Airport (LLBG) suspends all arrivals and departures. Simultaneously, Iran launches its regional military system salvo — Emad and Ghadr MRBMs with ~8–12 minute flight times — calibrated to arrive concurrently with drones. US Navy destroyers in the Eastern Mediterranean engage regional military systems mid-flight. Israel's Arrow-3, David's Sling, and Iron Dome systems engage the remaining threats.
All four FIRs simultaneously closed or severely restricted: ORBB, OJAC, LLLL, OLBA. The Eastern Mediterranean is effectively severed from Middle East transit. Airlines with flights airborne divert to Cairo (HECA/HEAT), Larnaca (LCLK), and Turkish airports (LTBA, LTFM, LTAC). Flightradar24 records a near-complete absence of commercial ADS-B tracks across the four-FIR zone. The rolling blackout creates cascading crew rest, slot, and positioning violations across European and Gulf carriers.
ORBB and OJAC begin issuing conditional reopening NOTAMs as the active threat phase concludes. LLLL reopens later in the morning following military assessment of Israeli airspace. Full commercial operations do not resume to Tel Aviv for several days pending security review. Carriers reassess scheduling for the following 72-hour window given unresolved escalation risk.
Aviation Impact
The April 13–14 cascade produced a multi-FIR blackout of a scale not seen in the Middle East since the 2022 Russia–Ukraine airspace closure. The defining characteristic of this event — what differentiates it from a single-FIR emergency — was the sequential, predictable propagation of closures driven by drone transit speed. Each FIR closed in a cascade that was geometrically determined by weapon velocity. That predictability, had it been modeled in advance, offered airlines a rerouting window of 30–60 minutes per FIR transition.
ORBB, OJAC, LLLL, and OLBA were all closed or restricted simultaneously during the peak disruption window of approximately 22:30–03:00 UTC — the largest coordinated airspace blackout in the Middle East since the 2022 Russian airspace closure. The four FIRs together cover a critical corridor linking Europe, the Gulf, and South Asia.
The Shahed-136/238 swarm of more than 170 drones physically transited ORBB and OJAC en route to LLLL — making each of those FIRs active munitions corridors during their respective closure windows. Jordanian F-16s intercepted a significant portion of the swarm within OJAC airspace itself, creating a live air-to-air combat environment within a commercial FIR.
From the first ORBB closure at approximately 20:30 UTC to the beginning of OJAC and ORBB reopening at roughly 04:00–06:00 UTC, the multi-FIR blackout persisted for approximately 6 hours — long enough to affect a full day of European–Gulf morning bank flights, generating widespread crew-out-of-position and slot cancellation effects into April 14 and 15.
Cairo International (HECA/HEAT), Larnaca International (LCLK), and Istanbul (LTFM/LTBA) absorbed the bulk of diversions from airlines unable to transit the affected FIRs. Larnaca in particular — already a regional alternate hub due to its position in the Eastern Mediterranean — saw significant overnight congestion. Carriers including Emirates, Lufthansa, Air France, and British Airways were among those rerouting or diverting services.
What made the April 13–14 event analytically distinctive — and operationally dangerous — was not the individual FIR closures themselves, but their sequential, velocity-driven propagation. The Shahed-136 drone's 185 km/h cruise speed meant that once ORBB closed, the window until OJAC closure was mathematically derivable: approximately 30 minutes at the observed swarm entry geometry. Once OJAC closed, LLLL closure was similarly projectable at approximately 60 additional minutes.
Airlines that were monitoring only the ORBB NOTAM at the moment of its issue had, in theory, a 30-minute rerouting window before OJAC closed — and a 90-minute window before LLLL closed. In practice, most carriers did not have real-time multi-FIR cascade modeling available to their dispatch teams, leading to a reactive rather than predictive rerouting posture. Flights that could have been proactively rerouted around OJAC were instead held at origin or diverted mid-flight at higher cost and disruption.
Takeaway
The Jordan–Iraq–Iran cascade of April 13–14, 2024 is the defining case study for what aviation risk analysts call a velocity-propagated FIR cascade — a class of disruption event where the physical speed of an airborne threat directly determines the sequence and timing of downstream airspace closures. It is categorically different from a simultaneous multi-FIR closure (such as a regional war outbreak) or a single-FIR incident. The drone swarm's slow transit speed was not an operational weakness for the attacker — it was irrelevant to their objectives. But for commercial aviation, that same slow speed created a predictable, modelable cascade that could have been used to generate proactive rerouting guidance with 30–90 minute lead times per FIR, had the right analytical infrastructure been in place.
The event also exposed the inadequacy of relying solely on NOTAM issuance as the primary trigger for rerouting decisions. NOTAMs for ORBB, OJAC, and LLLL were all issued reactively — only after drones had already entered, or were imminently entering, each FIR. A dispatch team waiting for NOTAMs was, by definition, operating with zero lead time on each closure. The geopolitical signal environment — Iran's explicit public retaliation pledge on April 1, US naval repositioning on April 11–12, Israeli civilian alerts on April 13 — collectively provided a 12-day warning window at varying confidence levels that something was coming. None of those signals are captured in NOTAM systems.
The broader lesson is structural: Middle East FIR risk cannot be assessed by monitoring each FIR in isolation. ORBB, OJAC, LLLL, and OLBA form a geographic cascade chain for any Iranian westward strike package. An event affecting one has calculable downstream probability implications for the others, particularly when the threat vector is a slow-transiting drone swarm. Risk systems must model inter-FIR dependencies, not just individual FIR status.
This retrospective analysis examines signals present in public data before the event. It is provided for educational context only and does not claim predictive capability for future events.
FlySafe's multi-source threat model may have reflected elevated ORBB, OJAC, and LLLL to HIGH RISK status on April 1, 2024 — the day of the Damascus consulate strike — based on Iran's explicit, named retaliation threat against Israeli territory. A geopolitical escalation trigger of that specificity and public nature constitutes a Tier-1 threat signal for all FIRs in the projected strike corridor.
On April 11–12, the US naval repositioning and intelligence community warnings may have indicated an upgrade to CRITICAL status across ORBB, OJAC, and LLLL, with a 48–72 hour imminent-strike confidence flag. FlySafe's cascade propagation model — which maps FIR adjacency relationships against known Iranian drone transit corridors — may have pre-flagged OJAC as a secondary closure risk contingent on ORBB closure, and LLLL as tertiary.
When ORBB closure was confirmed at approximately 20:30 UTC on April 13, FlySafe's real-time cascade engine may have immediately issued a 28–32 minute projected closure window for OJAC and a 85–95 minute projected closure window for LLLL — derived from Shahed-136 cruise speed, swarm entry geometry, and FIR boundary distances — giving dispatchers an actionable rerouting lead time before each subsequent NOTAM was issued.
Named retaliation threats against specific states create actionable FIR risk 12+ days before kinetic action
Velocity-based modeling of drone transit speed enables projected closure timing for downstream FIRs
Proactive cascade modeling converts zero-lead-time reactive NOTAM response into actionable dispatch windows
Sources
- CNBC — Jordan, Israel Close Airspace Amid Drone Attack from Iran (April 14, 2024)
- New York Times — How Iran Launched Its Attack on Israel: A Visual Guide (April 14, 2024)
- Flightradar24 — Sequential Airspace Closures April 13–14, 2024: ORBB, OJAC, LLLL, OLBA Analysis
- Reuters — Iran Drone and Missile Attack Timeline: Operation True Promise (April 14, 2024)
- Aviation Week & Space Technology — Multi-FIR Cascade Analysis: Middle East Airspace Closures April 2024
This is a retrospective analysis of publicly documented events. FlySafe's prediction system was not operational during this event. All information is sourced from public records, aviation authority publications, airline statements, and open data.