UAE Prosecutors Say Flydubai Co-Pilot Planned to Crash FZ1073
UAE prosecutors say the co-pilot of flydubai FZ1073 planned to seize the aircraft and crash it into Ben Gurion Airport. The alleged plot passed ordinary hiring checks and was stopped through layered cockpit and crew responses; a separate Saudi safety investigation remains open.
UAE prosecutors said on October 9 that the co-pilot of flydubai flight FZ1073 had planned to seize the aircraft and crash it into the passenger terminal at Ben Gurion Airport. The announcement transforms the story from an unexplained cockpit emergency into a documented aviation insider-threat case, while leaving the separate technical safety investigation unfinished.
The 30-second summary
- What changed? The UAE Attorney-General disclosed findings from the criminal investigation, including an alleged confession, witness accounts, medical evidence and a review of the co-pilot’s recruitment.
- Why does it matter? The case tests how airlines screen trusted crew members and how layered cockpit procedures respond when the threat comes from someone already authorised to fly.
- What remains open? Prosecutors are still checking for accomplices, while Saudi investigators have not issued aviation-safety findings or recommendations.
Key fact: Prosecutors said the co-pilot passed the professional and security requirements used when flydubai hired him. That finding does not prove the checks were defective, but it exposes the limits of screening based on licences, records and known warning signs.
What UAE prosecutors now say happened
The Emirates News Agency statement attributes the findings to Attorney-General Hamad Saif Al Shamsi. It says the 29-year-old Omani co-pilot attacked the captain with an emergency axe on September 30 after using two earlier Tel Aviv flights to study the route and airport. A second flydubai pilot travelling aboard noticed unusual cockpit-door movement, entered with an access code and helped crew members and passengers restrain the suspect.
Two reserve pilots then took control and diverted the Boeing 737 MAX to Tabuk, Saudi Arabia. This sequence aligns with the 7700 and 7500 transponder alerts NewTqnia examined immediately after the incident. Those codes conveyed a general emergency and unlawful interference before investigators had established the alleged motive.
Why ordinary vetting did not reveal the alleged plan
Prosecutors said the co-pilot held a valid licence, supplied a good-conduct certificate and completed the required hiring checks. None identified extremist views or an intention to attack. Associated Press reporting says flydubai also found no warning in its professional or security screening.
This makes the security lesson narrower than calling for a single new sensor or database. Background checks can find documented history, but they cannot reliably infer concealed intent. The successful response instead came from several independent layers: a locked cockpit, access procedures, another qualified crew, standardised transponder codes, air-traffic coordination and an available diversion airport.
What the announcement does not settle
The account is a prosecution finding in an ongoing criminal investigation, not a final court judgment or an air-accident report. Prosecutors said the suspect confessed in the presence of his lawyer, but they are still testing his claim that he acted alone. Reuters reports that Saudi Arabia is conducting a separate safety investigation under international aviation rules. It has not published conclusions about cockpit procedures, recruitment, equipment or regulatory changes.
What editors and regulators should watch next
The next technically consequential document will be any Saudi preliminary or final safety report. It could determine whether the event produces recommendations on crew vetting, cockpit access, carriage of emergency equipment, reserve-pilot procedures or information sharing between airlines and governments. Until then, the strongest conclusion is that the layered response prevented the alleged plan, but the case has not yet established which preventive layer, if any, must be redesigned.
Verified topics and entities
Sources and citations4 sources
External references used to support the reporting in this article.
- UAE Attorney-General announces updates on investigation into flydubai flight FZ1073
- UAE says Omani flydubai co-pilot planned suicide attack on Tel Aviv flight
- FlyDubai co-pilot intended to crash plane into Tel Aviv airport, UAE prosecutor says
- Saudi Arabia launches air safety probe into flydubai incident
Published by
NewTqnia Technology Policy Desk
An institutional editorial team within NewTqnia
