Saudi Probe Finds Flydubai Co-Pilot Assaulted Captain Before Emergency Landing in Tabuk
Saudi Arabian authorities have released the first official findings from their investigation into a midair disruption aboard a Flydubai passenger jet this week, concluding that the
Saudi Arabian authorities have released the first official findings from their investigation into a midair disruption aboard a Flydubai passenger jet this week, concluding that the aircraft's co-pilot physically assaulted the captain while the plane was in flight. The disclosure, issued by the kingdom's Interior Ministry on Thursday, marks the first public comment by Riyadh on an incident that forced an Emirates-bound flight traveling from Dubai to Tel Aviv to divert to northwestern Saudi Arabia.
According to the ministry, a preliminary inquiry determined that "the pilot was assaulted by his co-pilot, resulting in various injuries to both." The initial investigation was carried out by Saudi officials with the participation of a security delegation from the United Arab Emirates, underscoring the cross-border nature of an event that unfolded aboard a UAE-registered carrier flying between two other countries.
The flight, designated FZ1073, was en route from Dubai to Israel on Wednesday when what Flydubai described as "an altercation occurred in the flight deck." The carrier said crew members were able to secure the aircraft and divert it safely, a sequence of events that aviation specialists say reflects trained cockpit protocols for handling disruptions at altitude.
Saudi authorities said the plane was cleared for an emergency landing and touched down safely at 9:45am local time, or 06:45 GMT, at Prince Sultan bin Abdulaziz International Airport in Tabuk. Onboard were 174 passengers and eight crew members. The ministry added that "all necessary care was provided" to those aboard after arrival.
The timeline released by Riyadh indicates that passengers were not stranded for long. At approximately 5:40pm that same day, all travelers resumed their journey aboard a replacement Flydubai aircraft. The remaining crew members, excluding the captain and co-pilot, were flown back to Dubai on a separate flight, according to the ministry's account.
Both pilots were transported to a hospital in Tabuk for treatment based on an assessment of their condition. Once their health improved and they received medical clearance, the captain and co-pilot departed Saudi Arabia for Abu Dhabi on Thursday morning, traveling alongside the Emirati security team. The ministry framed the handling of the case as consistent with Saudi Arabia's "international and humanitarian obligations," pointing to the readiness of its aviation and security systems to respond to exceptional situations.
Separately, Saudi Arabia's National Transport Safety Center confirmed that its own investigation team had commenced work on the incident. The center said it was coordinating with relevant authorities to establish the circumstances surrounding the event and to collect evidence, a process that typically involves interviews, cockpit voice recordings, and maintenance records in cases involving commercial aircraft.
The UAE has opened a parallel criminal probe. Attorney General Hamad Saif Al Shamsi launched an investigation into the cockpit confrontation, with Emirati state news agency WAM reporting that investigators will examine the circumstances and motives behind the incident. A central question, according to WAM, is whether the episode was connected to any "terrorist activity or intent," or whether it involved prior planning or direction — language that signals authorities are not ruling out either a spontaneous breakdown or a premeditated act.
At the center of the case is Captain Smit Machchhar, an Indian national who was seriously injured during the struggle. Although the investigation remains ongoing, his conduct in apparently preventing a midair catastrophe has drawn praise from world leaders and from those who know him personally. The Indian Embassy in Riyadh said Machchhar was taken to a hospital in Tabuk in stable condition on Wednesday, and India's Ministry of External Affairs confirmed on Thursday that he had been transferred to Abu Dhabi for continued treatment. India's ambassador to the UAE visited the captain, and his family was briefed on his recovery.
Indian Prime Minister Narendra Modi publicly hailed Machchhar as a hero. In a post on X, Modi wrote that "in the face of the gravest danger and despite being seriously injured, he showed immense courage and an unwavering resolve to protect the lives of others," adding that his valor helped save hundreds of lives and avert a great tragedy.
The incident has also revived broader questions about cockpit security and the safeguards in place when a flight crew member becomes violent. The episode stands out because the threat allegedly originated inside the flight deck itself — a compartment designed to be sealed off from the cabin precisely to prevent outside interference. The case has prompted commentary from aviation safety analysts about crew resource management, psychological screening, and the procedures flight attendants follow when a disturbance occurs behind the locked cockpit door.
For passengers, the practical outcome was a disrupted journey that ended with a safe landing and an eventual continuation to their destination. For regulators in three countries — the UAE as the state of the carrier, Saudi Arabia as the state of landing, and Israel as the intended destination — the event has created overlapping jurisdictions and a shared interest in determining exactly what transpired at cruising altitude.
Flydubai, for its part, has confirmed only that an altercation took place and that its crew responded to secure the aircraft. The airline has not commented publicly on the identities or conditions of the two pilots beyond what has been released by government authorities. As the Saudi and Emirati investigations proceed, the coming weeks are likely to bring further details on the sequence of events, the nature of the injuries, and whether any charges will follow — questions that will shape how one of the most unusual inflight security episodes in recent memory is ultimately understood.
Comments (0)