Plane Plunges 18,000 Feet After Cockpit Stabbing in Suspected Terror Attack

Airplane seen through terminal windows with empty gate seating — Photo: Dabarti CGI / Shutterstock

A hijack code lit up controllers’ screens, the jet plunged, and fighter jets scrambled—before the cockpit story shifted.

Story Snapshot

The flight briefly squawked code 7500, the hijack alert, then diverted to Tabuk, Saudi Arabia.
Israeli officials said it was not a hijacking and pointed to a cockpit altercation.
Flydubai said there was an in‑flight incident and everyone landed safely in Tabuk.
Israel launched a security response, including scrambling aircraft as a precaution.

What Actually Happened Onboard And In The Sky

Flight FZ1073 left Dubai for Tel Aviv and soon broadcast an emergency code. Tracking logs and reports show the jet then briefly switched to code 7500, the signal for unlawful interference, which controllers treat as a hijacking alert. The flight diverted to Tabuk, Saudi Arabia, and landed safely. Flydubai confirmed an incident in flight and a safe landing with all passengers accounted for. Israeli authorities treated the alert seriously and moved assets in response.

Initial media reports focused on the hijack signal and the rapid descent. That framing fit the high-risk procedures tied to code 7500. Aviation rules direct controllers to act fast on that code and assume the worst until they hear otherwise. After landing, Israeli officials and several outlets said the case did not appear to be a hijacking. They cited a fight between the two pilots as the likely trigger for the emergency codes. That account lowered the temperature but did not erase the earlier alarm.

Why A 7500 Squawk Triggers A Big Response

Code 7500 is not a casual mistake. The Federal Aviation Administration says controllers never assign it. Pilots set it only to signal unlawful interference, which can mean a hijacking or a forced diversion. Once that code appears, air traffic control moves to hijack procedures and security agencies stand up. That design is deliberate. It builds in a bias for caution because the cost of delay can be catastrophic. False alarms happen, but the system prefers a safe overreaction to a slow response.

That protocol explains why Israel scrambled aircraft and why public alerts spiked. The code alone justifies a major posture shift. Later facts can calm the picture, but they do not make the first response “hype.” They show the machinery worked as intended. American common sense backs that approach. When a cockpit sends the hijack signal, you act first, verify second. Lives come before optics.

Competing Accounts: Hijacking Or Cockpit Brawl?

Reports from Israeli media and officials converged on an internal fight between the pilots. Several outlets quoted the Prime Minister’s office or officials saying there was no hijacking, and that an onboard altercation drove the emergency alert. Flydubai acknowledged an onboard incident and a safe outcome, but detailed findings were not public in the sources cited here. Some early claims mentioned stabbing or blood, but those details were not consistent across reports and remain unverified in the materials reviewed.

Flight bound for Israel diverted to Saudi Arabia following cockpit altercation where one pilot reporting attacked the other with a knife. Reportedly, one pilot was Emirati, the other Omani.

If they cannot get along with each other, how can we expect them to live peacefully with…

— That Stacey Girl (@jerseyborn23) September 30, 2026

The split between the stark hijack signal and the calmer post-landing narrative leaves gaps. The public record does not show cockpit voice recordings, flight data, or sworn crew statements in full. That keeps key facts fuzzy, like who selected 7500, how the descent unfolded, and whether a weapon was present. Until investigators release formal reports, the strongest confirmed pieces remain the transponder history, the diversion to Tabuk, the Israeli response, and official statements ruling out a hijacking.

What To Watch Next: Proof, Not Hype

Three items will settle the debate. First, the cockpit voice recorder and flight data recorder, which would show the cockpit timeline and confirm control inputs. Second, formal incident reports from the airline and the regulator, which would classify the event and document injuries, if any. Third, security logs from Israel and Saudi Arabia, which would nail down the decision chain behind the scramble and the handling in Tabuk. These deliver facts, not spin.

One more lesson is durable now. Procedure beats rumor. The code 7500 exists to save lives, and it did its job by forcing a rapid, serious response. If later evidence shows a crew dispute, that will expose a different safety failure that also demands hard fixes. Clear cockpit discipline, strict vetting, and zero tolerance for unprofessional conduct are not abstract ideals. They are the thin line that keeps a bad minute from becoming a tragedy.