Flydubai Tel Aviv Flight Diverts to Saudi Arabia After Hijack Alert Tied to Cockpit Fight

A Flydubai aircraft operating from Dubai to Tel Aviv diverted to Tabuk Airport in Saudi Arabia on Wednesday, September 30, 2026, after transmitting emergency signals that briefly raised fears of a hijacking.
The aircraft had departed Dubai International Airport in the United Arab Emirates early Wednesday morning bound for Ben-Gurion Airport. About two hours into the journey, it signalled a general emergency code, according to Flightradar24, then minutes later switched to the code used to report a hijacking, also according to Flightradar24 BBC. It changed course over Saudi Arabia after the emergency signal and landed instead at Tabuk. The hijacking code was later changed back to the general emergency signal, according to Flightradar24.
Those codes are transponder settings, basically preset alarm buttons pilots use to tell air traffic control what kind of trouble they face. Everyone on board was reported safe New York Post. Initial reports differed on numbers. The BBC reported around 150 people, most of whom are Israeli, while Ynet reported 174 passengers Indian Express.
Local media citing Israeli defence officials reported the signal was thought to have been issued following an altercation between the pilot and co-pilot BBC. That altercation was a physical fight. Sources described it as a "violent incident" CNN.
The response in Israel was immediate. The Israeli air force dispatched fighter jets. Prime Minister Benjamin Netanyahu held urgent consultations. The prime minister's office said the incident was not believed to have been a hijacking. All on board were reported safe. The aircraft remained on the ground in Tabuk after the diversion.
Looking at what this means for aviation security and crisis response, the sequence explains the scale of the reaction. A general emergency followed by a hijacking alert leaves air defences and political leaders little room for delay. Interception, high-level meetings and planning for a hostile case follow automatically, even if the cockpit cause later proves internal.
In my view, the questions for investigators and operators now are narrow and practical. What happened between the two pilots, and how did it affect command of the aircraft while the codes were changing. Why Tabuk became the chosen airfield, and how crew, passengers, aircraft and security were handled on the ground. For diplomats, an Israel-bound flight with mostly Israeli passengers landing unscheduled in Saudi airspace creates a coordination task that is sensitive by definition, regardless of cause.
The broader context here is discipline around emergency signalling. Transponder codes are blunt tools. They alert every relevant listener at once. When set off during an internal dispute rather than an outside threat, they still trigger the full outside system. That mismatch, between cockpit-level disorder and system-level alarm, is what turned a Dubai to Tel Aviv service into a regional incident.


