Flydubai Flight FZ1073: Dramatic Flight-Data Timeline Revealed After Cockpit Incident
Flydubai Flight Diverted to Tabuk After Emergency During Dubai–Tel Aviv Journey
Dubai/Tabuk: Flydubai Flight FZ1073, operating from Dubai to Tel Aviv on September 30, 2026, was reportedly diverted to Tabuk, Saudi Arabia, following an emergency involving the aircraft.
According to the flight-tracking data cited in preliminary reports, the Boeing 737-8 MAX departed Dubai at approximately 03:05 UTC and climbed to around 34,000 feet. At approximately 05:21 UTC, the aircraft reportedly experienced significant altitude changes, including a descent followed by a climb and another descent.
By approximately 05:33 UTC, the aircraft was reportedly flying at around 15,000 feet. Further fluctuations in altitude and ground speed were also indicated in the tracking data.
Emergency Transponder Codes Reported
At 05:28:48 UTC, the aircraft reportedly transmitted transponder code 7700, which is internationally used to indicate a general emergency.
At approximately 05:35 UTC, the transponder code reportedly changed to 7500, which indicates unlawful interference, before later returning to 7700. The meaning and circumstances of these transmissions require confirmation through official records and investigative findings.
The aircraft subsequently changed course, reportedly entering Jordanian airspace briefly before turning back toward Saudi Arabia and proceeding toward Tabuk. At approximately 05:44 UTC, an emergency landing was reportedly requested.
Aircraft Lands Safely in Tabuk
The aircraft reportedly landed safely at Prince Sultan bin Abdulaziz International Airport in Tabuk, Saudi Arabia. Flight-tracking records showed a final signal at approximately 06:58 UTC; this timestamp should not be treated as the confirmed landing time.
Investigation Into Reported Cockpit Incident
According to the statement attributed to the UAE Attorney-General, investigators established that the co-pilot allegedly attacked the captain with a crash axe and attempted to take control of the aircraft.
Authorities are continuing to investigate the circumstances, alleged motive and other aspects of the incident. The General Civil Aviation Authority (GCAA) is also examining operational and security-related matters.
Final conclusions will depend on the examination of flight recorders, cockpit evidence, air traffic control communications and other investigative material. The reported sequence of events and allegations should be treated as preliminary until confirmed through official findings.