What forced Flydubai’s safe diversion? Crash-attempt allegations remain unproven

What happened in the cockpit of Flydubai flight FZ1073—and do the accounts now emerging establish that someone tried to crash it? The answer is not yet clear. The Dubai–Tel Aviv flight diverted to Tabuk, Saudi Arabia, on September 30, 2026, and landed safely. Flydubai said all passengers were safe and accounted for. But the explanation has moved from reports of a fight between pilots to allegations of stabbing and an attempt to seize control, without a verified investigative finding establishing those actions or their intent. ^{2 8 24}

That distinction is the center of this story, not a qualification to tack onto its end. A safe landing is confirmed. A deliberate crash attempt is not. The airline’s passenger-accounting update answers an immediate question about the people on the flight; it does not explain what forced the aircraft off its scheduled route.

FZ1073 was traveling from Dubai International Airport to Ben Gurion International Airport when it diverted. Its passengers reached Saudi Arabia rather than their destination in Israel. No replacement flight, onward departure time, accommodation arrangement or confirmation that they subsequently reached Tel Aviv has been established. ^{2 24}

Flightradar24 reports a sequence of three transponder settings: 7700, the general-emergency code; 7500, the unlawful-interference code; and then 7700 again. Those signals communicated an emergency and possible unlawful interference. They do not independently establish a hijacking, identify who selected the codes or explain why the settings changed. ⁶

Israel scrambled jets after the emergency initially raised hijacking concerns, according to CBS/AP reporting summarized in the contemporaneous account. The aircraft deployed, any interception or escort, and the military’s underlying assessment have not been established. Ahram subsequently reported that Prime Minister Benjamin Netanyahu’s office withdrew the initial hijacking characterization and said the diversion was not believed to be a hijacking. That was an early assessment, not a completed investigation. ^{1 14}

The first explanation circulating publicly was a physical altercation between the pilots. NBC News attributed the apparent dispute to Israeli media; other reporting cited an Israeli official. Israel National News reported airline confirmation that the pilots had clashed, but a complete quoted airline statement establishing that explanation was not available. The directly reproduced airline description in Al Jazeera’s coverage was simply an “incident.” ^{3 7 12 13}

Later reporting alleged something substantially more serious. JNS said the co-pilot repeatedly stabbed the captain and sought to seize control before being subdued by crew and passengers. Its account of Israeli authorities treating the event as terrorism relied explicitly on journalist Amit Segal. Israel.com reported suspicion of a crash attempt, while DW described an investigation into a possible attempt to crash the aircraft. These reports establish that serious allegations and suspicions emerged—not that investigators proved them. ^{8 17 22}

The Jerusalem Post quoted an unnamed passenger saying: “From what I understand, the pilot tried to kill himself together with us.” The opening words matter. This is a passenger’s interpretation of events, not demonstrated knowledge of the pilot’s intent. It conveys the fear aboard the aircraft without resolving what happened in the cockpit. ⁵

Nor can the apparent change in the public account be treated as a verified official reversal. No direct statement from a named investigating authority explains whether the early no-hijacking assessment was revised. Article publication and update times cannot substitute for the times at which authorities reached their assessments. The later terrorism framing is not a final terrorism determination. ^{8 12 14 17}

Some of the most precise-looking details are among the least settled. On September 30, Globes reported 174 passengers; The Times of Israel reported 180. Neither count has been reconciled with an authoritative manifest or an airline-confirmed total. Both are described as passenger figures, so the difference cannot responsibly be explained by assuming one includes crew. The total crew count is also unknown. ^{4 18}

The same caution applies to claims of a sudden descent. Business Upturn described an apparent 14,300-foot plunge in 37 seconds, while Hindustan Times used 17,500 feet. A separate 17,400-foot claim also circulated. No verified timestamped altitude trace substantiates any of these descriptions. Selecting the most dramatic figure—or averaging them—would manufacture certainty. Even a verified descent would need context before it could demonstrate an intention to crash. ^{1 20 21}

The flight’s clock and geography are incomplete, too. GreekReporter gives a tracking-based departure time of 03:05 UTC, but that time was not independently reproduced in the available Flightradar24 account. Globes places receipt of the first emergency signal at about 09:08 “this morning,” without specifying a time zone. Neither exact code-change times nor a verified UTC landing time has been established. ^{4 6 11}

Globes places the aircraft over Jordan, and ABC describes a diversion from Jordanian airspace. Flightradar24 places the inflight incident above Saudi Arabia; The Times of Israel describes a U-turn near the Jordan–Saudi Arabia border and a brief unlawful-interference transmission over Saudi Arabia. These may describe different stages. Without timestamped positions tied to each event, they cannot identify the cockpit emergency’s precise location. ^{4 6 18 19}

GreekReporter identifies a Boeing 737 MAX 8, while The Times of Israel specifies a 737 MAX. A direct airline or authority identification and aircraft registration remain unestablished. A 737-800 photograph caption alongside JNS’s coverage is not evidence of the model operating FZ1073. ^{8 11 18}

The medical distinction deserves particular care. “Safe and accounted for” does not establish that nobody was injured, or confirm the captain’s or co-pilot’s condition. IntelliNews’s separate description of no reported casualties does not supply a complete injury account. Likewise, reports that someone was subdued do not establish an arrest; neither an arrest nor a confirmed absence of arrests has been established. ^{8 9 24}

Aviation Shop carried an update marked 08:10 UTC quoting a spokesperson’s wording that Flydubai was “working closely with the relevant authorities.” That is the outlet’s update time, not a verified release time for the airline’s statement. No direct public Saudi aviation-authority statement resolving the allegations has been established. ²³

For now, the responsible account ends where the evidence ends: an emergency flight reached the ground safely, passengers were accounted for, and a deeply troubling cockpit event remains unexplained. Their arrival in Tabuk is established. Their medical circumstances, the possible criminal conduct and completion of their journey still require answers.

CNN’s contemporaneous account ¹; Gulf News’s airline-attributed landing report ²; NBC News’s emergency coverage ³; Globes’s flight and passenger-count account ⁴.

The Jerusalem Post’s passenger accounts ⁵; Flightradar24’s tracking report ⁶; Global Banking & Finance Review’s pilot-altercation coverage ⁷; JNS’s alleged stabbing and terrorism account ⁸.

IntelliNews’s diversion report ⁹; The Indian Express’s live coverage ¹⁰; GreekReporter’s aircraft and departure account ¹¹; Israel National News’s cockpit-clash and subsequent allegations coverage ¹².

Al Jazeera’s airline-attributed incident report ¹³; Ahram Online’s Netanyahu-office assessment ¹⁴; Associated Press coverage carried by WSLS ¹⁵; Middle East Online’s early pilot-fight explanation ¹⁶.

Israel.com’s suspected crash-attempt report ¹⁷; The Times of Israel’s flight summary ¹⁸; ABC News Australia’s diversion coverage ¹⁹; Business Upturn’s descent claim ²⁰.

Hindustan Times’s descent account ²¹; DW’s possible crash-attempt investigation report ²²; Aviation Shop’s passenger-safety update ²³; The Arabian Stories’ airline-attributed landing and passenger-accounting report ²⁴.