Drooid Logo
Back to story perspectives

Full Breakdown

Flydubai Flight FZ1073’s Mid-Air Crisis: Cockpit Fight, Emergency Signals and a Safe Landing in Saudi Arabia

By Drooid · · How we work

Core Event

On September 30, 2026, Flydubai flight FZ1073, a Boeing 737 MAX 8 bound for Ben Gurion Airport, transmitted squawk 7700 and, minutes later, the unlawful-interference code 7500 after a violent altercation between the two pilots. The aircraft descended rapidly, turned back over Jordanian airspace and landed safely at Tabuk Airport in north-western Saudi Arabia. All 174 passengers—including 27 children—and crew were reported safe and accounted for.

Background & Context

Flydubai operates daily Dubai-Tel Aviv services, a route opened after the UAE-Israel normalization in 2020. The September 2026 incident occurred amid heightened regional security concerns linked to the Gaza conflict and upcoming Israeli elections.

Timeline

Timeline
Time (UTC)Event
03:05Flight departs Dubai (20 min behind schedule).
~05:21Squawk 7700 (general emergency) transmitted.
~05:28Squawk 7500 (unlawful interference) transmitted.
05:21-05:22Drop of roughly 14,000 ft in less than a minute, followed by a low-altitude turn back toward Saudi airspace.
05:30-05:45Israeli Air Force scrambles two fighter jets; senior IDF officials convene an urgent assessment.
07:00 (local)Aircraft lands at Tabuk; Saudi security surrounds the plane.
07:20-07:45Israeli leaders hold a security consultation; Police Commissioner Danny Levy says “We are preparing for every scenario.”
08:00-09:00Flydubai confirms an “incident” and announces a replacement aircraft for passengers.

Data & Statistics

  • Passengers: 174 (including 27 children).
  • Altitude loss: ~14,000 ft (from ~34,000 ft to ~20,000 ft) within 30 seconds, descent rate ~30,976 ft/min.
  • Emergency codes: 7700 followed by 7500.
  • Flight time before diversion: about 90 minutes.

Official Statements & Responses

  • Police Commissioner Danny Levy: “We are preparing for every scenario.”
  • Israeli Defence Minister Israel Katz participated in the emergency meeting; IDF Chief of Staff Lt. Gen. Eyal Zamir led the assessment.

On-the-Ground Reports

Passengers described chaotic scenes. “We felt that this was it; we were about to crash. I was already screaming ‘Shema Yisrael’…” — Miriam, Israeli passenger.

Tzvika Manes, a passenger, said he and two others entered the cockpit after his wife heard the commotion: “He called for help, and two other men and I entered the cockpit and subdued the attacker. I'm covered in blood. It was insane.”

Conflicting Reports & Gaps

  • Pilot nationalities – Israeli officials identified the attacker as an Omani national and the defending captain as Indian; earlier media reports mentioned Russian and Ukrainian pilots.
  • Motivation – Treated as a possible terrorist attack, though the airline and Saudi authorities have not confirmed a motive.
  • Cause of the emergency signals – An anonymous official said the codes were triggered after the pilots “got into a physical altercation,” but it is unclear who activated them.

Why It Matters

The incident highlights cockpit security vulnerabilities on routine commercial flights and shows how emergency transponder codes prompt immediate military responses. It also illustrates the coordination required when an aircraft diverts to a country without formal diplomatic ties to Israel.

What’s Next

Flydubai will transport passengers from Tabuk to Tel Aviv on a replacement aircraft. Israeli and Saudi authorities are conducting joint investigations, including analysis of the cockpit voice and flight-data recorders, to determine the sequence of events and any criminal liability. No further actions have been publicly disclosed.