Travel/Public Service · NEWS EXPLAINER
Flydubai FZ1073 lands safely in Tabuk after onboard incident; passengers accounted for
Flydubai says flight FZ1073 diverted from its Dubai–Tel Aviv route and landed safely in Tabuk, Saudi Arabia, on September 30. All passengers were accounted for; the precise cause and conflicting reports about the cockpit incident remained under investigation.

Flydubai flight FZ1073, scheduled from Dubai to Tel Aviv, diverted to Tabuk in northwestern Saudi Arabia on September 30 after emergency signals and an onboard incident. The airline said the aircraft landed safely and all passengers were safe and accounted for.
As of 12:12 UTC on September 30, the outcome was clearer than the cause. Reuters and AP reported conflicting accounts about a cockpit confrontation, while the airline and Saudi authorities had not publicly established a final cause, motive or identity of any attacker.
The confirmed result: a safe landing in Tabuk
Flydubai confirmed that FZ1073 was operating from Dubai International Airport to Ben Gurion International Airport when it experienced an incident en route. The aircraft diverted to Prince Sultan bin Abdulaziz International Airport in Tabuk and landed safely.
The carrier’s statement says all passengers were safe and accounted for. Reuters separately reported that Tabuk airport said the captain and co-pilot sustained injuries and were taken to a hospital. No passenger fatality was reported in the sources reviewed.
What the emergency signals show — and what they do not
Flightradar24 data cited by Reuters and AeroTime showed the aircraft first transmitting code 7700, the general-emergency code, then briefly 7500, used for unlawful interference, before returning to 7700. Its flight history lists the September 30 service as diverted to Tabuk.
Those signals document that the flight crew or aircraft system declared an emergency; they do not by themselves identify who selected the code or prove a hijacking, terror motive or suicide attempt. Reuters said it was not immediately clear who transmitted the signals.

Reports of a cockpit fight remain part of an investigation
Reuters and AP reported accounts from Israeli officials and media describing a physical confrontation between the pilots. Reuters also recorded conflicting claims about a stabbing, motive and the pilots’ nationalities, and said it could not verify an image said to be from inside the aircraft.
For that reason, this article treats the fight, the identity of an aggressor and any alleged terror or self-harm motive as reported allegations rather than established facts. Flydubai’s public statement described only an incident and said further information would follow when confirmed.
How travelers can check the next flight status
Travelers should use Flydubai’s official flight-status page and search by flight number FZ1073 and travel date. The page is the operational source for later departures and arrivals; the September 30 safe landing does not guarantee that the next scheduled rotation will operate unchanged.
If a booking is affected, use the airline’s Manage booking or Contact us routes linked from the same official site. As of this review, the sources did not publish a final investigation report or a complete onward-travel timetable for the passengers, so later carrier and airport updates should control.