Flydubai Flight FZ1073: A Timeline of the Dubai-Tel Aviv Emergency and Its Political Fallout
A Flydubai passenger jet traveling from Dubai to Tel Aviv was forced to make an emergency landing in Saudi Arabia on Wednesday after a dramatic mid-air incident that Israeli Prime
A Flydubai passenger jet traveling from Dubai to Tel Aviv was forced to make an emergency landing in Saudi Arabia on Wednesday after a dramatic mid-air incident that Israeli Prime Minister Benjamin Netanyahu later characterized as an attempted hijacking and crash. The aircraft, operating as flight FZ1073, diverted to Tabuk after transmitting emergency signals, according to flight tracking data and official statements. The episode has ignited a fierce political dispute in Israel, arriving less than a month before a scheduled national election.
The sequence of events began a day before the flight, when Netanyahu publicly warned that Israel's "enemies" might attempt attacks in the period leading up to the October 27 vote. He did not elaborate on the specific nature of the threat, leaving the public and political establishment uncertain about what intelligence had prompted the caution.
Later that same evening, at approximately 20:30 GMT on September 29, opposition leader Yair Lapid received a security briefing from the prime minister. After the meeting concluded, Lapid publicly stated there was "no reason to put the public in a panic," arguing that security threats ought to be managed professionally rather than deployed as election messaging. His remarks set an early tone of skepticism that would intensify the following day.
At 03:05 GMT on September 30, Flydubai flight FZ1073 departed Dubai International Airport bound for Tel Aviv, climbing to a cruising altitude of 34,000 feet, according to data from the flight tracking service Flightradar24. For roughly the first two hours, the flight appeared routine, with no indication of the crisis that would soon unfold over the deserts of the Arabian Peninsula.
The situation deteriorated sharply beginning around 05:21 GMT, when Flightradar24 data recorded the aircraft entering a deep descent. This was followed almost immediately by a sharp climb and then a second steep descent. By approximately 05:33 GMT, the jet had dropped to roughly 15,000 feet, a dramatic loss of altitude that suggested the crew was struggling for control of the aircraft.
At 05:28 GMT, while flying near the border between Saudi Arabia and Jordan, the plane began transmitting the emergency transponder code 7700, the internationally recognized signal for a general emergency. This code alerts air traffic controllers across the region that an aircraft is in distress and requires immediate priority handling.
Minutes later, at 05:35 GMT, the transponder switched to code 7500, which specifically denotes unlawful interference — the standard aviation signal for a hijacking or security threat. Following this change, the aircraft turned west, briefly entered Jordanian airspace, and then reversed course back toward Saudi Arabia, a puzzling trajectory that reflected the chaotic situation on board.
At 05:44 GMT, air traffic controllers in Tabuk, Saudi Arabia, received a distress call from FZ1073 requesting an emergency landing. Saudi authorities recorded the time as 08:44 local time. As the aircraft approached Tabuk, its transponder reverted to code 7700, indicating a general emergency rather than unlawful interference, though the reason for the change remains unclear.
At 06:45 GMT, the plane landed safely at Prince Sultan bin Abdulaziz International Airport in Tabuk, according to local media reports. Flightradar24 received the aircraft's final tracking signal at 06:58 GMT, confirming the jet was on the ground. Flydubai issued a brief statement acknowledging that the flight had experienced an "incident" and was diverted to Tabuk, where it landed safely, adding that all passengers were safe and accounted for. The airline did not elaborate on the nature of the incident, and the United Arab Emirates has not publicly commented on the circumstances surrounding the event.
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 stated that passengers and a crew member entered the cockpit and restrained the co-pilot, preventing a potential catastrophe. The exact time when Netanyahu recorded or released the video was not immediately clear, nor has there been independent confirmation of a hijacking attempt.
According to Netanyahu and an Israeli official, the co-pilot was identified as an Omani national and was arrested after the plane landed. Israel's Ministry of Transport announced that a joint investigation would be conducted with the defense establishment. However, the nationality of the arrested individual has not been independently verified, and Omani authorities have not issued any public statement on the matter.
The political repercussions were immediate. Lapid forcefully rejected any attempt to connect the Flydubai incident to the security briefing he had received from Netanyahu the previous night. "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," Lapid wrote on the social media platform X. He accused government-aligned voices of exploiting the incident for political purposes, deepening the already charged atmosphere ahead of the election.
Later that afternoon, footage from international news agencies showed a Flydubai rescue flight carrying passengers from FZ1073 arriving at Ben Gurion Airport near Tel Aviv at 15:34 GMT. The passengers, who had endured hours of uncertainty in Saudi Arabia, were finally returned to Israel, though many likely faced debriefings from security officials about what they had witnessed in the cockpit.
The incident raises significant questions about aviation security in the region. The route from Dubai to Tel Aviv crosses sensitive airspace, and the fact that a flight crew member allegedly turned violent mid-flight has prompted concerns about screening and psychological evaluation protocols for airline personnel. The rapid sequence of transponder code changes — from general emergency to unlawful interference and back — also suggests that the situation on board evolved rapidly and may have been resolved by the time the aircraft approached Tabuk.
For Saudi Arabia, the emergency landing represented a moment of regional cooperation, as Saudi air traffic controllers facilitated the safe arrival of an Israel-bound flight at a time of complex diplomatic relations. The kingdom has not issued an official statement about the incident, but its role in accepting the diverted aircraft underscored the practical coordination that exists among regional aviation authorities even amid political tensions.
As Israel's election campaign enters its final weeks, the Flydubai incident is likely to remain a flashpoint. Netanyahu's allegations, if substantiated, would represent a serious security breach, while Lapid's insistence that the threat was not flagged in advance suggests a competing narrative about the government's handling of intelligence. With a joint investigation underway and international aviation authorities expected to review the incident, the full account of what happened aboard FZ1073 may take weeks to emerge — but its political consequences are already being felt.
Comments (0)