Flydubai Flight FZ1073: Timeline of In-Flight Emergency That Led to Saudi Divert and Israeli Hijack Allegation

A Flydubai passenger jet traveling from Dubai to Tel Aviv was forced to divert to Saudi Arabia on Wednesday after a violent incident in the cockpit triggered a cascade of emergency signals, according to flight tracking data and official statements. The event quickly became entangled in Israeli domestic politics, with Prime Minister Benjamin Netanyahu alleging that one pilot attacked the other and attempted to bring down the aircraft—a claim that has not been independently verified.

The flight, designated FZ1073, departed Dubai at 03:05 GMT on September 30 and initially climbed to a cruising altitude of 34,000 feet, according to data from the flight tracking service Flightradar24. For roughly two hours, the journey appeared routine. That changed abruptly at approximately 05:21 GMT, when the aircraft entered a series of extreme maneuvers: a deep descent, a sharp climb, and then a second steep plunge. By 05:33 GMT, the plane had dropped to roughly 15,000 feet, less than half its original cruising altitude, as it flew near the border between Saudi Arabia and Jordan.

The first public indication of trouble came at 05:28 GMT, when the aircraft began broadcasting transponder code 7700—the internationally recognized signal for a general emergency. Seven minutes later, the code shifted to 7500, which indicates unlawful interference, a category that includes hijacking. At that point, the plane turned west, briefly entered Jordanian airspace, and then reversed course back toward Saudi Arabia. The sequence of codes suggested a rapidly evolving situation in which the crew was communicating different levels of distress to air traffic controllers.

At 05:44 GMT, controllers in the Saudi city of Tabuk received a distress call from FZ1073 requesting an emergency landing. Saudi authorities later placed the time at 08:44 local time. As the aircraft approached Tabuk, its transponder switched back to 7700, signaling a general emergency once more. The plane landed safely at Prince Sultan bin Abdulaziz International Airport at 06:45 GMT, according to Saudi media reports. Flightradar24 received the aircraft's final tracking signal at 06:58 GMT, confirming it was on the ground at Tabuk.

Flydubai, the Dubai-based carrier, issued a brief statement describing the event as an "incident" and confirming that the flight had been diverted to Tabuk, where it landed safely. The airline said all passengers were safe and accounted for. The United Arab Emirates government has not publicly commented on the circumstances surrounding the incident, leaving a gap that competing narratives have rushed to fill.

Later on September 30, Netanyahu released a video message alleging that the co-pilot had stabbed the pilot and apparently attempted to crash the plane. He said passengers and a crew member entered the cockpit and restrained the co-pilot. An Israeli official identified the detained co-pilot as an Omani national, though that nationality claim has not been independently confirmed. Israel's Ministry of Transport announced that a joint investigation would be conducted with the defense establishment, underscoring the seriousness with which Israeli authorities are treating the episode.

The incident did not occur in a vacuum. On September 29, just one day before the flight, Netanyahu said Israel had indications that its "enemies" might attempt attacks ahead of the country's October 27 election. He did not specify the nature of the threat. That night, at about 20:30 GMT, opposition leader Yair Lapid received a security briefing from Netanyahu. Afterward, Lapid publicly stated there was "no reason to put the public in a panic," arguing that security threats should be handled professionally rather than used as election messaging.

Lapid's office moved swiftly to distance the briefing from the flight emergency. In a post on X, the opposition leader said: "Let me make this clear. Nothing even resembling this morning's plane incident appeared in the security briefing with the prime minister last night. Nothing similar, nothing reminiscent of it, not even a hint." He accused government-aligned voices of attempting to exploit the incident for political gain, a charge that reflects the charged atmosphere in Israel as the election approaches.

The factual record remains incomplete. There has been no independent confirmation of a hijacking attempt, and the precise sequence of events inside the cockpit—who did what, when, and why—has not been verified by neutral parties. Saudi authorities have not issued a detailed account of the investigation. Flydubai has declined to elaborate beyond its initial statement. The Omani nationality of the arrested individual, reported by an Israeli official, remains unverified. These gaps are significant because the most dramatic allegation—that a pilot tried to crash an Israel-bound jet—came from a political leader facing an election, not from an independent investigative body.

The transponder data, however, does corroborate that something highly abnormal occurred. The combination of rapid altitude changes, the 7700 general emergency code, the 7500 unlawful interference code, and a distress call requesting an emergency landing paints a picture of a cockpit in crisis. The fact that the aircraft briefly entered Jordanian airspace before turning back to Saudi Arabia suggests the crew was still attempting to control the plane's trajectory during the emergency. That the plane landed safely and all passengers were accounted for is a testament to the efforts of those who ultimately regained control.

Later that afternoon, a Flydubai rescue flight carrying passengers from FZ1073 arrived at Ben Gurion Airport near Tel Aviv at 15:34 GMT, according to footage from international news agencies. The return of the passengers closed one chapter of the ordeal, but the larger questions—about what happened in the cockpit, about the motivations involved, and about the political uses to which the incident has been put—remain unresolved. With Israel's election less than a month away, the FZ1073 emergency is likely to remain a subject of intense scrutiny, claim, and counterclaim, even as investigators on the ground piece together the facts.