FlySafe was not operational during this event. This analysis reconstructs publicly available signals — to demonstrate how predictive airspace intelligence could have provided advance warning.
Ukraine PS752 Incident
January 8, 2020 — Shot Down Over Tehran
Six years after MH17, it happened again. Ukraine International Airlines Flight 752 — a Boeing 737-800 with 176 people — was lost by two Iranian Tor-M1 missiles at 8,000 feet, six minutes after takeoff from Tehran Imam Khomeini Airport. Iran had launched regional military systems at US bases in Iraq hours earlier. The airspace was open. No NOTAM was issued. No warning was given. 176 people died because the lesson of MH17 — close airspace during military operations — was not applied.
What Happened
On January 8, 2020, Ukraine International Airlines Flight PS752 — a Boeing 737-800 registered UR-PSR — departed Tehran Imam Khomeini International Airport (IKA) at 06:12 local time, bound for Kyiv Boryspil. Six minutes after takeoff, climbing through 8,000 feet, the aircraft was struck by two Tor-M1 surface-to-air missiles fired by the military forces. All 176 people on board lost their lives: 167 passengers and 9 crew members. The wreckage came down near Parand, west of Tehran.
The context was unambiguous and documented: just two hours before PS752 took off, Iran had launched Operation Martyr a January 2020 event — a regional military system strike against two US military bases in Iraq (Al Asad and Erbil), in direct retaliation for the killing of military General Qasem a January 2020 event on January 3. military air defense units were on elevated alert, expecting a US retaliatory strike. An operator misidentified PS752, a scheduled commercial departure on a known IFR track, as an incoming regional military systems. No NOTAM was issued. IKA remained open. No airlines were warned.
- AircraftBoeing 737-800 (UR-PSR)
- OperatorUkraine International Airlines
- RouteIKA → KBP (Tehran → Kyiv)
- Departure06:12 local, Jan 8 2020
- Brought down06:18 local — 6 min airborne
- Altitude~8,000 ft, climbing
- Fatalities176 of 176
- Hours beforeIran ballistic strike on US bases
- OperationMartyr a January 2020 event (~04:00 local)
- TargetsAl Asad AB + Erbil, Iraq
- military postureHigh alert, US retaliation expected
- Weapon usedTor-M1 (SA-15) SAM system
- NOTAM issuedNone
- IKA closureAirport remained open
Authorities initially denied responsibility, attributing the crash to mechanical failure. Ukrainian investigators, Western intelligence agencies, and flight data analysis pointed immediately to a missile strike. On January 11 — three days after the event — Military authorities publicly acknowledged that the military had brought down PS752 "unintentionally." The admission came only after Ukrainian, Canadian, and US officials presented conclusive evidence including video of the missile launch.
Warning Signs
The signals preceding PS752's destruction were not subtle. They were publicly documented, geopolitically unambiguous, and operationally concrete. The FAA had already acted on them. The failure was not a lack of data — it was a lack of systematic integration and propagation of that data to all operators flying the affected airspace.
Iran's regional military system strike against US military installations in Iraq concluded approximately 02:00 hours before PS752's wheels left IKA's runway. military air defense units were in active engagement posture. An active inter-state military exchange was ongoing in the same regional threat environment as the departure airport.
The FAA issued NOTAM KICZ A0005/20 prohibiting US-certificated carriers from operating in Iranian, Iraqi, Gulf of Oman, and Gulf of Persia FIRs. This prohibition reflected a US government assessment of unacceptable risk to civil aviation from military escalation. Non-US regulators had not issued equivalent prohibitions, creating a critical asymmetry in operator risk awareness.
Tor-M1 (NATO: SA-15 Gauntlet) short-range SAM systems were actively deployed in the vicinity of Tehran to defend against anticipated US counterstrikes. These systems operate with engagement envelopes reaching 6–12 km altitude — covering the entire initial climb-out corridor of any departure from IKA. Their presence and activation state were not communicated to civil aviation.
The US killing of a senior figure at Baghdad Airport on January 3 had already generated a five-day escalation window of explicit Iranian threats of retaliation. Open-source intelligence, diplomatic channels, and government travel advisories had been flagging Iran-US conflict risk continuously. The specific threat to aviation near military forces installations was a foreseeable downstream risk.
Despite an active military alert status, Iranian civil aviation authorities did not implement any temporary restriction, NOTAM, or holding measure at IKA. Qatar Airways, Emirates, and Turkish Airlines all had aircraft on the ground at IKA at the time. The absence of civil-military coordination is structurally identical to the failure mode identified after MH17 over eastern Ukraine in July 2014.
Iranian airspace had remained open during previous periods of heightened Iran-US tension, including tanker seizures and drone incidents in 2019. The pattern of non-closure during elevated military readiness was a known structural characteristic of the Tehran FIR, not an isolated anomaly.
Timeline
A January 2020 incident at Baghdad International Airport in which a senior military figure was reportedly killed. Iran declares a period of national mourning and vows "severe retaliation." Regional threat level for US-Iran tensions assessed as highest in decades. FAA begins drafting airspace restriction measures for Iranian and Iraqi FIRs.
Five-day escalation window. Open Iranian state media explicitly signals forthcoming retaliatory strike. US military assets in Iraq and the Gulf region placed on heightened alert. FAA NOTAM KICZ A0005/20 issued, prohibiting US-certificated operators from Tehran FIR (OIIX), Baghdad FIR (ORBB), Gulf of Oman FIR (OOMM), and Gulf of Persia FIR. Non-US regulators do not issue equivalent restrictions; European, Canadian, Middle Eastern, and Ukrainian carriers continue normal operations into IKA.
Iran launches Operation Martyr a January 2020 event: regional military systems strike Al Asad Air Base in western Iraq. No US fatalities. military publicly claims responsibility within hours. military air defense forces across Iran placed on maximum alert, anticipating US counterstrike.
Second wave of Iranian regional military systems strikes Erbil air base in northern Iraq. military air defense posture remains at maximum alert. Tehran FIR remains open. IKA operates normal commercial schedule. No NOTAM, no ground stop, no coordination with civil aviation. Qatar Airways, Emirates, and Turkish Airlines aircraft are on the ground at IKA.
Ukraine International Airlines Flight PS752 departs IKA Runway 29R. Boeing 737-800 UR-PSR, operating scheduled passenger service to Kyiv Boryspil. 167 passengers and 9 crew on board. Aircraft transponder active, squawking on assigned code. IFR clearance issued and acknowledged. Aircraft climbing normally on standard departure track.
military Tor-M1 SAM operator locks onto PS752. The aircraft is climbing through approximately 8,000 feet, six minutes after takeoff, on a northwest heading. The operator, under extreme alert conditions and without communication with civilian ATC, misidentifies the Boeing 737 as an incoming regional military systems. Two Tor-M1 missiles are fired in rapid succession.
Both missiles impact PS752. Wreckage falls near Parand. All 176 on board lose their lives. Victims include 82 Iranian nationals, 57 Canadians, 11 Ukrainians, 10 Swedish, 4 Afghan, 3 German, and 3 British citizens. IKA continues to operate; other aircraft depart and arrive without incident in subsequent hours.
Iran Civil Aviation Organization attributes crash to "technical failure." Iranian authorities begin removing wreckage and restrict access to the crash site. Ukrainian, Canadian, and US investigators present preliminary evidence of missile strike — including radar data, infrared satellite tracking of two heat signatures, and recovered warhead fragments matching Tor-M1 specifications. Iran continues to deny missile involvement.
The military publicly admits that the military "unintentionally" brought down PS752, citing human error under high-alert conditions. Officials described the admission as a result of internal military investigation. Multiple military air defense personnel are arrested. International calls for full accountability, transparency, and access to black boxes intensify.
Canadian Transportation Safety Board and Ukrainian NBAAI lead international investigation. Iran delays and restricts access to flight recorders. ICAO issues strengthened conflict zone safety recommendations. The Atlantic Council and multiple aviation safety bodies publish analyses concluding that the lessons of MH17 (2014) had not been implemented — airspace again left open during active military operations without notification to civil aviation.
Aviation Impact
All 176 people on board lost their lives: 167 passengers and 9 crew. Victims represented at least 7 nationalities. The largest single-incident aviation loss of Canadian nationals since Swissair 111 in 1998: 57 Canadians lost, many holding dual Iranian-Canadian citizenship.
Iran's regional military system attack on US bases concluded approximately two hours before PS752 departed IKA. military air defense units remained at maximum engagement alert throughout. The airport operated a normal commercial schedule during an active inter-state military exchange.
Despite an active regional military system strike on a neighboring country, maximum military air defense alert, and Tor-M1 SAM systems in engagement posture around Tehran, not a single NOTAM was issued restricting or alerting civil aviation in the Tehran FIR (OIIX) at the time of the loss event.
From January 8 to January 11, Iranian authorities publicly attributed the crash to mechanical failure. The three-day period of denial complicated evidence preservation, restricted crash site access, and delayed the international safety response — a pattern first observed after the KAL 007 loss event in 1983.
US-certificated carriers: banned from Tehran FIR (OIIX), Baghdad FIR (ORBB), Gulf of Oman FIR (OOMM), and Gulf of Persia FIR by FAA NOTAM KICZ A0005/20 — issued days before the loss event, citing military escalation risk.
Non-US carriers received no equivalent guidance from their national regulators. UIA (Ukraine), Qatar Airways, Emirates, and Turkish Airlines all had aircraft operating at or through IKA on the night of January 8. The information asymmetry between US and non-US operators was direct and fatal.
The PS752 disaster triggered ICAO to accelerate work on conflict zone risk information sharing, reinforcing the framework established after MH17 but still not fully implemented. The Atlantic Council's post-incident analysis concluded directly: "The lessons of MH17 have not been learned." Six years after a commercial aircraft was lost by a SAM over an active conflict zone, the structural failure — open airspace during military engagement, no civil-military coordination, no NOTAM — repeated itself with identical consequences.
Takeaway
PS752 is not a case where hindsight reveals hidden signals. Every material risk factor was active, documented, and publicly known before PS752 pushed back from the gate. The FAA had already acted. The failure was systemic: risk intelligence existed but was not translated into universal operator guidance, and civil aviation authorities at IKA did not implement the one intervention that may have prevented the loss event — a temporary ground stop.
This is precisely the operational gap that systematic airspace risk monitoring addresses. The question is not whether the signals were detectable. They were. The question is whether they were aggregated, weighted, and communicated with sufficient urgency to reach every operator with an aircraft at IKA on the morning of January 8, 2020.
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.
A retrospective analysis suggests FlySafe's indices may have indicated Tehran FIR (OIIX) at CRITICAL risk level from January 3, 2020 onward — immediately upon the January 2020 targeted incident — and escalated to DO NOT FLY status upon detection of the Operation Martyr a January 2020 event regional missile activity at approximately 01:20 UTC on January 8, a full 82 minutes before PS752 departed IKA.
- → Geopolitical trigger (Jan 3): a January 2020 event targeted incident classified as Level 4 escalation event — active state-level conflict risk between Iran and the US. Tehran FIR elevated to HIGH. Operator advisory issued automatically to all carriers with scheduled IKA operations.
- → Regulatory signal (Jan 3–7): FAA prohibition of US carriers from OIIX/ORBB/OOMM treated as a material safety signal — not a jurisdictional boundary. When a Tier-1 safety regulator prohibits its carriers from an airspace, FlySafe surfaces that action to all operators regardless of flag state.
- → Active strike detection (Jan 8, ~01:20 UTC): regional military systems launch events in Iraqi FIR correlated with military origin. Automatic escalation of Tehran FIR to CRITICAL. Real-time push alert to all operators with imminent IKA departures: "Active military exchange detected in adjacent airspace. military air defense expected at maximum alert posture. Recommend immediate ground stop at IKA pending airspace assessment."
- → SAM threat envelope mapping: Known Tor-M1 deployment areas around Tehran overlaid on IKA departure corridors. Departure track for Runway 29R exits IKA directly through documented SAM engagement envelope. This route flagged as high-risk until military stand-down confirmed.
The NOTAM system is reactive by design — it documents decisions made by airspace managers. PS752 demonstrates what happens when airspace managers fail to act. FlySafe is designed to close that gap: to synthesize open-source military intelligence, regulatory actions, and geopolitical escalation signals into a continuous risk picture that operators can act on regardless of whether the relevant authority has issued a NOTAM. The absence of a NOTAM is not evidence of safety. It is sometimes evidence of a failure that has not yet happened.
Sources
- — Atlantic Council — Iran Plane Tragedy Proves Lessons of MH17 Have Not Been Learned (January 2020)
- — Canadian Transportation Safety Board — Aviation Investigation Report A20F0007: Final Report on PS752
- — Iran Civil Aviation Organization — Accident Investigation Final Report: Ukraine International Airlines Flight 752
- — BBC News — PS752: Iran admits shooting down Ukrainian plane "unintentionally" (January 11, 2020)
- — The New York Times — Iran Shot Down Ukrainian Airliner, Officials Say — timeline and investigation coverage (January 2020)
- — ICAO — Conflict Zone Safety: Recommendations and Guidelines for Information Sharing (post-PS752 review, 2020)
- — FAA NOTAM KICZ A0005/20 — Prohibition of US civil aviation operations in Tehran FIR (OIIX), Baghdad FIR (ORBB), Gulf of Oman FIR (OOMM), Gulf of Persia FIR
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.