fz1073-investigation

Open-Data Timeline & Telemetry Analysis: Flydubai Flight FZ1073 Incident

Disclaimer: This document serves as an independent, non-partisan open-data registry for the Flydubai Flight FZ1073 incident. It synthesizes verified ADS-B transponder telemetry, flight dynamics profiles, passenger testimonies, and multi-agency regulatory statements into a Single Source of Truth for safety analysts and investigators.


1. Flight Metadata & Security Profile

Attribute Verified Value / Detail Primary Data Source
Flight Number / Callsign FZ1073 / FDB1073 Mode S / Flightradar24 Logs
Aircraft Type & Reg Boeing 737 MAX 8 (A6-FKF) UAE GCAA Aircraft Registry
Date & Scheduled Time Sep 30, 2026 — 06:45 GST (02:45 UTC) Flight Schedule (DXB)
Route & Diversion DXB $\rightarrow$ TLV (Diverted to TUU / OETB, Tabuk) ATC Transponder / Ground Track
Commanding Captain Capt. Smit Machchhar (Injured, Operational Hero) Airline & Diplomatic Briefings
Perpetrator / First Officer Hamam / Majid al-Hammami (Omani, Age 29) UAE AG / GACA Inquiry
Declared Intent Suicide Ramming (Targeting Ben Gurion Airport) Interrogation Confession Logs
Weapon Used Flight Deck Emergency Crash Axe UAE Public Prosecution
Intervening Flight Crew Two Off-Duty/Reserve Flydubai Pilots + Passengers Joint GACA / IAF Reports

2. Technical Telemetry & Flight Dynamics

Telemetry Parameter Recorded Metric / Parameter Aviation Context & Verification Status
Cruising Altitude ~34,000 ft (FL340) Nominal pressure altitude prior to event onset
Altitude Delta ($\Delta h$) ~14,000–19,000 ft drop High-rate uncommanded descent profile
Descent Duration ~30 seconds ADS-B Pitch/Altitude telemetry log
Peak Descent Rate Exceeding -14,000 ft/min Transonic dive profile recorded by Flightradar24
Transponder Squawk Sequence 7700 (05:32 UTC) $\rightarrow$ 7500 (05:39 UTC) Mode S Emergency & Unlawful Interference Signals
Level-Off & Stabilization ~15,000 ft (FL150) Manual yoke recovery & pitch stabilization
Structural Impact Observed Upper rudder structural separation Inspection post-touchdown at Tabuk (TUU)

3. Event Sequence Chronology

UTC Time Marker Phase / Action Key Actors Involved Location / Operational Status
03:05 UTC Departure: Flight departs Dubai International Airport. Flight Crew Nominal climb to FL340
05:21 UTC Assault Onset: First officer attacks Captain; forces yoke down. First Officer, Captain Machchar Flight Deck (Locked)
05:22 UTC Uncommanded Dive: Aircraft drops >14,000 ft in ~30 seconds. Avionics / Controls High-speed descent initiated
05:23 UTC Door Release: Captain engages emergency door release. Captain Machchar Flight Deck Mechanism
05:24 UTC Cabin Intervention: Passengers & off-duty pilots breach cockpit. Yaniv Hayun, Crew & Passengers Flight Deck / Forward Cabin
05:32 UTC Emergency Signal: Mode S Transponder broadcasts Squawk 7700. Deadheading Pilots / Avionics International Airspace
05:33 UTC Flight Level Stabilized: Yoke pulled back; altitude levels at FL150. Deadheading Pilots & Passengers Pitch recovery achieved
05:39 UTC Hijack Signal: Transponder updated to Squawk 7500. Avionics / Crew Regional ATC Notification
06:45 UTC Emergency Landing: Safe touchdown executed at Tabuk (TUU). Off-Duty Pilots & Saudi ATC Tabuk Airport (OETB / TUU)

4. Single Source of Truth (SSOT) Verification Matrix

This matrix categorizes incident parameters into strict verification tiers:

Data Metric / Claim Status Primary Source Analytical / Forensic Notes
Attacker Identity & Weapon 🟢 Verified UAE Attorney General / GACA Hamam al-Hammami (Omani FO); crash axe used in cockpit assault.
Target & Motive Confession 🟢 Verified UAE / Saudi Custody Interrogations Stated intent to ram Ben Gurion Airport terminal; acted as lone-wolf.
Upper Rudder Separation 🟢 Verified Tabuk Airport (TUU) Ground Inspection Aerodynamic overload exceeding $V_{DF}/M_{DF}$ limits during -14,000+ ft/min dive pull-up.
In-Flight Control Recovery 🟢 Verified Flight Crew & Passenger Statements Wounded Captain unlocked door; two deadheading Flydubai pilots & passengers stabilized pitch.
Pre-Employment Vetting Failure 🟢 Verified Wall Street Journal / WSJ & UAE Audit Oman previously flagged FO for extremism; Flydubai conducted basic criminal check without checking Omani records.
Israeli Air Defense Scramble 🟢 Verified Israeli MoD / IDF Statements IAF fighters scrambled for kinetic intercept if border was crossed before Tabuk diversion.
CVR / FDR Laboratory Readout 🟡 In Progress Joint UAE/Saudi Forensic Team Flight Data & Cockpit Voice Recorders currently under spectral audio analysis.

5. Regional & Global Media Framing Analysis

The media coverage of the Flight FZ1073 incident diverged significantly across different regions during the initial 48-hour breaking news cycle, reflecting distinct editorial standards, domestic political contexts, and geopolitical sensitivities:

1. Western Mainstream Media (Initial Minimization & Evolution)

2. Israeli Media & Political Narrative

3. Gulf & Regional State Media (UAE, Saudi Arabia, Oman)

4. Indian Media (Focus on Captain’s Heroism)


Media Framing vs. Verified Telemetry Comparison

Media Phase / Angle Initial Framing Narrative Verified Data Reality OSINT Impact
Breaking News Phase “Cockpit argument / fight between crew” Squawk 7500 transmitted; $V_z > -14,000\text{ ft/min}$ drop Obscured the severity of the flight control emergency
Middle Phase “Unexplained diversion to Tabuk” Emergency landing granted at TUU due to upper rudder failure Highlighted regional air traffic control coordination
Final Verified Status “Foiled hijack / suicide-ramming attempt” Crash axe attack, wounded captain, physical rudder separation Re-aligned media narrative with physical telemetry

6. Systemic Vetting & Security Audit Findings

Investigations conducted by the UAE Public Prosecution, Saudi GACA, and diplomatic leaks highlight three critical security vulnerabilities:

  1. Omani Regulatory Disconnect: The perpetrator was flagged and grounded by Omani civil aviation due to extremist activity on social media prior to 2026. However, no international alert or registry entry was issued.
  2. Airline Hiring Protocol Flaw: Flydubai executed standard criminal background checks during recruitment in February 2026 but failed to request employment history verification from Omani aviation authorities.
  3. Crew Manifest Vetting Gaps: Despite receiving the flight crew list, regulatory authorities failed to flag a pilot holding citizenship of a state without diplomatic relations with the destination state, revealing an oversight in API/PNR crew screening procedures.

7. References & Primary Sources

Telemetry & Flight Tracking Data

Official Regulatory & Government Statements

Verified Witness Accounts & Investigative Reporting