Flydubai FZ1073 Cockpit Attack: What Official Investigations Have Confirmed

A serious security incident aboard flydubai flight FZ1073 on September 30, 2026, resulted in an emergency diversion to Tabuk, Saudi Arabia. In the days following the event, official statements from authorities in the United Arab Emirates and Saudi Arabia have provided a clearer picture of what happened inside the flight deck.
According to the latest statement from the UAE Attorney-General, the investigation has found that the co-pilot attempted to carry out what authorities described as a terrorist act, attacking the captain with a crash axe and attempting to take control of the aircraft. The investigation, however, remains ongoing. Authorities are still examining the full circumstances, motives and possible connections behind the incident.

What Happened to Flydubai Flight FZ1073?

Flydubai flight FZ1073 was operating from Dubai International Airport (DXB) to Ben Gurion International Airport (TLV) on September 30 when a security incident occurred in the flight deck. The UAE General Civil Aviation Authority (GCAA) initially confirmed that the incident had been brought under control but required the aircraft to divert and make an emergency landing at Tabuk Airport in Saudi Arabia. Crew members were injured and received medical treatment following the landing.
Flydubai subsequently confirmed that an altercation had occurred inside the flight deck.
Importantly, the airline stated that on-duty flydubai crew members who were travelling aboard the flight secured the aircraft, diverted it and landed safely in Tabuk. All passengers and crew were accounted for. This distinction is important because some early reports contained conflicting descriptions of exactly who regained control of the aircraft.

Official statements differ on the exact number of people aboard FZ1073. Flydubai stated that all 172 passengers and crew on board were safe, while Saudi Arabia’s Ministry of Interior reported that the aircraft was carrying 174 passengers and eight crew members. As of October 5, 2026, this discrepancy between the two official accounts has not been publicly clarified.

Flydubai FZ1073 Cockpit Attack: What Official Investigations Have Confirmed — Aircraft involved in the incident
source

Flight Data Shows the Severity of the Event

Flight-tracking data also illustrates the seriousness of the incident. According to Flightradar24 data cited by Reuters, FZ1073 lost approximately 16,625 feet of altitude in just over 30 seconds during the event. The aircraft also transmitted emergency transponder codes, including 7700 for a general emergency and 7500, the internationally recognized code for unlawful interference. These data provide additional operational context to the security incident, although the precise sequence of events remains subject to the official investigation.

Saudi Authorities Confirm an Attack on the Captain

Saudi Arabia’s Ministry of Interior later released further details through the Saudi Press Agency. According to the Saudi statement, preliminary investigations conducted by Saudi authorities, with the participation of a UAE security team, found that the co-pilot had assaulted the captain, resulting in injuries to both pilots. Saudi authorities said the aircraft landed safely at Prince Sultan bin Abdulaziz International Airport in Tabuk. Passengers received assistance following the emergency landing and were subsequently able to continue their journey aboard a replacement flydubai aircraft. The captain and co-pilot were hospitalized before later leaving Saudi Arabia for the UAE after receiving medical clearance.

UAE Investigation Identifies an Attempted Terrorist Act

The most significant official development came on October 3. UAE Attorney-General Counsellor Dr. Hamad Saif Al Shamsi announced that the investigation had found that the co-pilot attempted to carry out a terrorist act. According to the Attorney-General, the co-pilot began executing his plan during the flight, attacked the captain inside the flight deck using a crash axe, and attempted to take control of the aircraft’s flight controls. This official finding also clarifies an important detail that was uncertain in some of the earliest media reports: UAE investigators identified the weapon as a crash axe, rather than simply describing it as a knife or other sharp object. Authorities have not yet announced the complete findings of the investigation. The UAE Attorney-General said investigators are continuing to examine the circumstances and motives surrounding the incident, any possible connections, and physical and digital evidence. Final results will be released after the necessary investigative procedures have been completed.

Captain and Crew Praised for Their Response

On October 2, the UAE GCAA publicly praised Captain Machchhar Smit, the crew and passengers who helped bring the situation under control. The GCAA said their rapid intervention helped contain the incident and prevent potentially more serious consequences. The authority also confirmed that Captain Smit had returned safely to the UAE, was in good condition and was receiving medical treatment. Flydubai CEO Ghaith Al Ghaith similarly thanked the captain, the pilots who secured and safely landed the aircraft, the cabin crew and passengers who assisted during the emergency.

Flights to Israel Temporarily Suspended

Following the FZ1073 incident, flydubai announced that flights to and from Israel would be temporarily suspended while authorities continued their investigation. The airline said the measure was being taken in coordination with the relevant authorities and would allow investigators to establish the facts surrounding the incident. The suspension should therefore be understood as part of the immediate operational response to the investigation rather than, based on the information currently available, evidence of a wider security problem across the flydubai network.

Why Does the UAE Have Jurisdiction?

Although the incident occurred outside UAE territory and the aircraft landed in Saudi Arabia, UAE authorities are leading a major part of the investigation. The UAE Ministry of Foreign Affairs explained that the country’s judicial authorities have jurisdiction because the aircraft is registered in the UAE and operates under the UAE flag. According to the ministry, UAE law consequently applies to crimes committed aboard the aircraft even when they occur outside UAE territory. The investigation is being conducted by a specialised Public Prosecution team in coordination with the GCAA and other relevant authorities.

The Wider Aviation Security Question: Insider Threat

The FZ1073 incident also highlights a particularly difficult aviation-security problem: insider threat. Modern aviation security is heavily designed to prevent unauthorized individuals from gaining access to aircraft, restricted airport areas and flight decks. An incident involving an authorized crew member presents a fundamentally different security challenge. This is not a new concern for international aviation regulators.

ICAO has specifically strengthened international aviation-security standards addressing insider threats. Amendment 17 to ICAO Annex 17 — Security introduced revised provisions covering areas including background checks, vulnerability assessments, training, access control and staff screening. ICAO’s broader Annex 17 framework is designed to protect international civil aviation against acts of unlawful interference and is continuously reviewed as security threats evolve. However, it would be premature to conclude that a particular security or vetting failure caused the FZ1073 incident. The UAE authorities have explicitly stated that the investigation includes both operational and security aspects, and its final findings have not yet been published.

What Is Confirmed — and What Is Still Unknown?

As of October 5, 2026, several important facts have been officially established. Flydubai FZ1073 experienced a serious flight-deck security incident while travelling from Dubai to Tel Aviv. The co-pilot attacked the captain, and the UAE Attorney-General says the attack involved a crash axe and an attempt to take control of the aircraft. Flydubai crew members travelling aboard the flight intervened, secured the aircraft and safely diverted it to Tabuk. The captain and co-pilot sustained injuries, while the passengers were ultimately able to continue their journey. UAE investigators have formally characterized the co-pilot’s actions as an attempted terrorist act.

What remains unknown is equally important.

Authorities have not yet publicly established the complete motive, disclosed all possible connections related to the incident or released the final results of the technical, physical and digital evidence examinations. For this reason, claims circulating about the alleged perpetrator’s background, previous employment, ideology or possible organizational affiliations should be treated cautiously unless and until they are confirmed by the authorities conducting the investigation.

Conclusion

The flydubai FZ1073 incident is an unusual and serious aviation-security event because the alleged threat originated inside the flight deck rather than from an unauthorized passenger attempting to enter it. The successful intervention of other crew members, combined with the subsequent emergency diversion to Tabuk, prevented the situation from developing further. At the same time, the incident is likely to attract wider attention within the aviation-security community because it raises questions about insider threats, personnel security, crew vetting and the resilience of procedures designed to protect aircraft when a threat comes from an individual who already has authorized access. Those broader lessons, however, should not be determined before investigators complete their work. For now, the most reliable account remains the one emerging from the official investigation: the UAE Attorney-General says the co-pilot attacked the captain with a crash axe and attempted to take control of the aircraft as part of an attempted terrorist act, while the investigation into the motive, connections and complete circumstances remains ongoing.

This article reflects information officially available as of October 5, 2026, and may be updated as UAE and other relevant authorities release further findings.