A violent cockpit altercation turned a routine Dubai–Tel Aviv flight into a regional security emergency, sending the jet sharply downward, triggering the international hijack code and leaving Israeli passengers in a Saudi airport.
TABUK, Saudi Arabia — The Flydubai FZ1073 pilots fight diverted a Dubai–Tel Aviv flight to northwestern Saudi Arabia on Wednesday after the aircraft transmitted first a general emergency code and then the international signal for unlawful interference. Israeli fighter jets scrambled as officials initially treated the flight as a possible hijacking. The Boeing 737 landed safely at Tabuk Airport, and Flydubai said all passengers were safe and accounted for.
The core facts are extraordinary without embellishment. Flight FZ1073 departed Dubai for Ben Gurion Airport carrying between 150 and 180 passengers, many of them Israeli, according to reports reviewed by Signal Post News. Flight-tracking data showed the aircraft turn away from Israel, descend rapidly and transmit codes 7700, then 7500, then 7700 again before landing in Tabuk. An Israeli official told Reuters that the emergency signals followed a physical altercation between the pilots. Israel's prime minister's office said the incident was not believed to be a hijacking.
What happened inside the cockpit remains less certain. Passengers described screams, blood and a knife in accounts carried by Israeli television and international outlets, but Flydubai and government authorities had not publicly confirmed those details when this report was published. The distinction is critical: officials have confirmed an internal personnel incident and a safe diversion; the most alarming claims about stabbing, motive and an attempt to crash the aircraft remain unverified.
Why this matters: the threat no cockpit door can stop
Modern airline security is designed primarily to keep an attacker out of the flight deck. FZ1073 raises the inverse problem: what happens when the threat begins among the people already authorized to control the aircraft? A reinforced cockpit door can protect pilots from an intrusion, but it can also delay intervention when a crisis develops inside. That does not mean the security model has failed; it means crew selection, medical oversight, two-person coordination and rapid communication are as important as the barrier itself.
The episode also shows how quickly an ambiguous cockpit event becomes an international military problem. A passenger flight heading toward Israel broadcast the one four-digit code guaranteed to be read as a potential hijacking. It did so over a region where air defense decisions are made in minutes and where the diversion airport sat in a country that has no diplomatic relations with Israel. Controllers, militaries and political leaders had to act before they knew whether the aircraft had been seized.
The immediate success was that the jet landed and no passenger was reported injured. The institutional test comes next: whether investigators can establish who selected each emergency code, what disabled normal communications, who retained control during the descent and whether cockpit procedures contained or intensified the danger.
Squawk 7500 hijack code explained: why four digits scramble fighter jets
Aircraft transponders identify a flight to air-traffic control and can also broadcast standardized emergency codes. Code 7700 means a general emergency. Code 7500 signals unlawful interference, the category that includes hijacking. It is not a verdict about what happened; it is a high-priority warning designed to let a crew communicate danger even when speaking openly over radio may be impossible.
On FZ1073, Flightradar24 data cited by Reuters showed a sequence of 7700, 7500 and then 7700 again. Investigators will need to determine who selected the codes and why. Reuters reported that it was not immediately clear whether either pilot deliberately transmitted the unlawful-interference signal. A brief 7500 transmission could reflect a purposeful alert, confusion during the struggle or another sequence that only cockpit and avionics records can resolve.
That ambiguity explains why jets scramble for a 7500 squawk. The code tells authorities to prepare for the most dangerous plausible interpretation, not to wait for courtroom-level proof. Fighter aircraft can identify and monitor the airliner, establish visual contact, protect nearby airspace and be ready to respond if the jet turns toward a sensitive target. Scrambling fighters is therefore evidence that the alert was taken seriously, not proof that a hijacking occurred.
Israel's response: jets scrambled as Netanyahu convened his security chiefs
Israeli Prime Minister Benjamin Netanyahu and Defense Minister Israel Katz held a security consultation as the alert unfolded. Israel's military said Chief of Staff Eyal Zamir conducted a situational assessment with the air force commander and other senior officials. An Israeli military spokesperson told CNN that fighter jets were scrambled after the emergency signal.
The response matched the uncertainty. Reports said officials temporarily struggled to establish contact with the cockpit, while the aircraft deviated from its path and descended over northwestern Saudi Arabia. Until the plane was safely on the ground, decision-makers could not assume that the 7500 code was accidental or that the crew had restored control.
After landing, Netanyahu's office said the situation was “under control” and that measures were being taken to return Israeli passengers safely. That statement narrowed the event from a possible attack against Israel to a complicated aviation, law-enforcement and diplomatic incident.
What passengers say happened — and what remains unconfirmed
The most vivid accounts came from passengers and relatives, not from official investigative findings. An unnamed passenger told Israel's Channel 12, in an account carried by The Sun, that people heard screams, saw blood after the cockpit opened and believed a pilot had been stabbed with a pocketknife. A passenger identified as Noam said travelers understood that one pilot was seriously wounded and that the plane began to dive. The outlet also reported that passengers and crew helped restrain an attacker.
Reuters separately quoted Yasmin Abu Kasis, whose daughter Miriam was aboard. Abu Kasis said her daughter told her that she heard screaming and that a man took a knife, put a pilot on the floor and that there was blood. These are material eyewitness or secondhand accounts, but they do not establish who held a knife, who was injured, whether the object was a pocketknife or what caused the confrontation.
Claims that a pilot tried to seize or crash the aircraft are more serious still and remain unconfirmed. Neither Flydubai nor the Israeli, Saudi or Emirati authorities had publicly endorsed that version. Signal Post News is not treating nationality claims, an alleged suicide motive or the reported stabbing sequence as established fact. Cockpit voice recordings, medical evidence and interviews with both pilots and cabin crew should carry more weight than descriptions formed during a frightening, fast-moving emergency.
FZ1073 Tabuk emergency landing: the descent in numbers
CNN's review of flight-tracking data found that the aircraft descended 17,400 feet, from about 34,000 feet to around 16,600 feet, in just over two minutes at approximately 1:20 a.m. Eastern time. It transmitted an emergency signal at 1:32 a.m. and landed shortly before 3 a.m. ET. The Times reported that the plane had crossed into Jordanian airspace before turning back toward Saudi Arabia and flying at about 15,000 feet.
A rapid descent can be a deliberate response to several emergencies, including depressurization, smoke or a need to get the aircraft lower quickly. Flight-tracking data alone cannot show who was controlling the jet, why the maneuver began or whether passengers experienced the entire altitude change as a dive. What the numbers do establish is that the emergency involved a major and abrupt change from normal cruise flight.
The aircraft's changing track and transponder codes widened the response. A Dubai to Tel Aviv flight emergency already crosses multiple air-traffic jurisdictions; turning over Jordan and landing in Saudi Arabia brought additional authorities into the chain. Investigators will need synchronized radar, radio and aircraft records to reconstruct the sequence minute by minute.
Israelis stranded in Saudi Arabia: a diplomatic first
The landing placed a large group of Israelis in Saudi Arabia at once, under emergency conditions, despite the absence of formal diplomatic relations. CNN described it as a rare mass arrival. Saudi Arabia opened its airspace to Israel-bound flights and Israeli airlines in 2022, but overflight access is not the same thing as consular relations or routine entry.
This was not the first Israel-linked Flydubai diversion to the kingdom: Reuters noted that a Dubai–Tel Aviv flight made a medical-emergency landing in Riyadh in September 2025. FZ1073 was different in scale and security context. Instead of one passenger needing care, an entire planeload needed protection, processing and onward transport while two governments without diplomatic ties coordinated indirectly.
The arrangement also tests the practical side of regional normalization. Riyadh says it will not establish diplomatic relations with Israel without an independent Palestinian state. Yet aviation geography creates situations in which Saudi and Israeli authorities must still cooperate through airlines, controllers and intermediaries. The safe landing shows functional channels exist even when formal politics remain frozen.
Pilots fight in cockpit mid-air: the questions for Flydubai and regulators
Flydubai said only that FZ1073 “experienced an incident while en route,” landed safely in Tabuk and that all passengers were safe and accounted for. It said its teams were working with the relevant authorities and promised further updates as verified details became available. That restraint is appropriate during an investigation, but the airline will face demanding questions.
First is command: who was pilot flying, who was pilot monitoring and who controlled the aircraft during the rapid descent? Second is access: how did cabin crew or passengers become involved, if the passenger accounts are accurate, and was the cockpit door opened under established emergency procedures? Third is signaling: who selected 7700 and 7500, and did either code accurately reflect what the selector believed was occurring?
Regulators will also examine duty history, medical fitness, training and any prior conflict between the pilots. Those are normal investigative avenues, not evidence that a particular cause has already been found. The cockpit voice recorder and flight-data recorder should help distinguish between an argument, an assault, an incapacitation and any alleged attempt to interfere with control of the aircraft.
The episode will inevitably revive debate over the “two-person cockpit” principle and the ability of a crew member outside the flight deck to gain emergency access. The wrong lesson would be to redesign security around an unverified narrative. The right sequence is evidence first, then procedural change targeted at the failure investigators actually identify.
What happens next: investigation, jurisdiction, and repatriation
The immediate priority is repatriation. Flydubai was expected to arrange another aircraft to take the passengers onward to Israel. Saudi authorities had responsibility for the plane and people on the ground, while the United Arab Emirates, as the airline's home jurisdiction, and aviation investigators connected to the aircraft and its operator were likely to have central roles in determining the cause. The exact lead and participating authorities had not yet been publicly detailed.
The evidence list is clear even if jurisdiction is not: cockpit voice and flight-data recordings, transponder selections, radio calls, crew schedules, medical examinations, airport security records and passenger video. Investigators must separate three questions that were fused during the emergency — whether there was a physical fight, whether a weapon was used and whether anyone intended to seize or crash the plane.
For passengers, the decisive fact is that the Tabuk airport emergency landing ended safely. For Flydubai and regulators, that outcome cannot be allowed to obscure how close an internal crew crisis may have come to overwhelming the systems built to contain aviation threats. The next credible update should come from evidence, not the most sensational version circulating while the aircraft was still in the air.
Sources
- CNN — “Violent incident” between pilots sparks diversion of Israel-bound flight to Saudi Arabia
- Reuters via Devdiscourse — Israel-bound flight diverted to Saudi Arabia after brawl between pilots
- The Times — Hijack alert on flight to Israel “triggered by fighting pilots”
- The Sun — Passenger accounts and reported cockpit violence
Source note: The diversion, emergency-code sequence, cockpit altercation and safe landing are supported by official statements and multiple reports. Claims involving a knife, stabbing or intent to crash remain unconfirmed and are attributed above to the passengers and outlets that reported them.