The Flydubai FZ1073 incident on 30 September 2026 became one of the most serious aviation security incidents of the year after a routine Dubai-to-Tel Aviv flight was disrupted by a violent confrontation inside the cockpit.

According to UAE authorities, the co-pilot attacked the captain with a cockpit crash axe and attempted to take control of the aircraft. The aircraft subsequently experienced a dramatic loss of altitude before passengers, crew members and additional pilots helped regain control. It was eventually diverted to Tabuk, Saudi Arabia, where it landed safely. The UAE Attorney-General has classified the incident as an attempted terrorist act, while the wider investigation into motive, planning and possible connections remains ongoing.

Flydubai FZ1073 Incident at a Glance

Flight FZ1073 was operated by Flydubai from Dubai International Airport (DXB) to Ben Gurion International Airport (TLV).

The aircraft was a Boeing 737-8 MAX, registration A6-FKF. It departed Dubai at approximately 03:05 UTC and initially climbed normally towards cruising altitude.

During the flight, however, the aircraft experienced a series of extreme altitude changes. Flight-tracking data showed a loss of more than 16,000 feet during the most severe phase of the incident.

The aircraft eventually diverted to Prince Sultan bin Abdulaziz International Airport in Tabuk, Saudi Arabia.

Flydubai FZ1073 Incident: Detailed Specifications

The aircraft and flight information is supported by flydubai and aviation-tracking data, while the UAE Attorney-General has confirmed the alleged cockpit attack and attempted takeover.

How the Incident Unfolded

The flight departed Dubai normally and climbed to approximately 34,000 feet.

The situation changed when an altercation developed inside the cockpit. According to the UAE Attorney-General, the co-pilot attacked Captain Machchhar with a crash axe and attempted to take control of the aircraft.

Around the same period, flight-tracking data recorded an extraordinary descent. The aircraft dropped more than 16,000 feet during the most severe phase before recovering and subsequently changing course.

For passengers, the sudden altitude changes would have created a frightening and potentially dangerous situation. However, flight-tracking data alone cannot establish exactly who was controlling the aircraft at each moment; investigators must rely on cockpit recordings, flight-data records, witness testimony and other evidence to reconstruct the sequence.

Emergency Signals and Loss of Control

The aircraft’s transponder activity provided important indications of the developing emergency.

FZ1073 transmitted 7700, the internationally recognised code for a general emergency. Tracking information also showed 7500, the code associated with unlawful interference.

The aircraft subsequently returned to 7700 before diverting towards Saudi Arabia.

These signals helped air-traffic authorities recognise that the aircraft was experiencing a serious emergency.

Captain Smit’s Role

Captain Machchhar Smit, an Indian national, was injured during the cockpit confrontation.

Despite his injuries, the captain was able to facilitate access to the cockpit. This gave passengers and other crew members an opportunity to intervene.

The UAE General Civil Aviation Authority later praised Captain Machchhar, the crew and passengers for their response. The captain was subsequently returned to the UAE for medical treatment.

His actions became a crucial part of the chain of events that allowed the aircraft to be recovered.

Passengers and Additional Pilots Help Regain Control

Once access to the cockpit was possible, passengers and crew members helped restrain the alleged attacker.

The presence of additional flydubai pilots travelling as passengers was also significant. After the confrontation was contained, qualified pilots were able to enter the cockpit and assist with flying the aircraft.

They diverted the aircraft towards Tabuk, where Saudi emergency services had prepared for its arrival.

A medical professional travelling on the aircraft also helped treat the injured captain.

The incident therefore involved a coordinated response from the captain, cabin crew, passengers and additional pilots rather than a single individual restoring control.

Emergency Landing in Saudi Arabia

With the aircraft stabilised, the crew diverted to Prince Sultan bin Abdulaziz International Airport in Tabuk.

The Boeing 737 MAX 8 landed safely, and passengers and crew were accounted for. Saudi authorities provided emergency assistance, while the injured pilots received medical treatment.

Flydubai subsequently arranged replacement aircraft so passengers could continue their journey to Israel.

UAE Declares It an Attempted Terrorist Act

The official description of the incident evolved as investigators gathered evidence.

Initially, UAE aviation authorities referred to the event as a security incident and said an investigation was underway.

The UAE Attorney-General later announced that investigators had determined that the co-pilot attacked the captain with a crash axe and attempted to take control of the aircraft.

The UAE subsequently characterised the incident as an attempted terrorist act.

This is currently the most significant official finding. However, the investigation into the suspect’s broader motivation and possible connections remains incomplete.

Who Was the Suspected Co-Pilot?

Media reports have identified the suspected co-pilot as an Omani national, with reports naming him as Hamam or Hammam al-Hammami.

Investigators are examining his previous aviation training, education, employment history and international connections.

Reports have linked him to aviation-related training in several countries, including Australia, while other reports have examined previous applications to airlines.

These details are relevant to the investigation, but a person’s education, travel or employment history does not by itself establish involvement in terrorism or an attack.

Was the Attack Planned?

One of the most serious developments came after the initial investigation.

Reuters reported on 5 October that Israeli officials familiar with the investigation said the suspect allegedly planned the attack before joining flydubai. Sources also reportedly told Reuters that investigators believed Ben Gurion Airport was the intended target.

If ultimately confirmed, such evidence would indicate that the incident was not simply a spontaneous cockpit confrontation but a premeditated operation.

However, these claims remain part of the ongoing investigation. They should not be presented as final judicial findings until authorities release supporting evidence and conclusions.

Questions About Radicalisation and International Connections

Investigators are also examining allegations concerning the suspect’s ideological background and possible radicalisation.

Israeli officials have made claims about Islamist radicalisation and suicidal intent, while authorities in Australia and New Zealand have examined aspects of the suspect’s previous connections to those countries.

These investigations do not establish that any university, country or organisation was connected to the attack.

The key issue for investigators is whether the suspect had previously demonstrated behaviour or connections that should have raised security concerns before he became a commercial pilot.

Was Iran Involved?

There is currently no established public evidence that Iran was involved in the incident.

The fact that the aircraft was travelling to Israel and the incident has been classified as terrorism-related has generated speculation about possible regional connections.

However, speculation should not be confused with evidence. The UAE investigation is still examining whether anyone assisted, directed or encouraged the suspect.

Why the Incident Raises Aviation Security Concerns

The FZ1073 case is particularly significant because the alleged threat came from inside the cockpit.

Commercial aviation security is designed largely around preventing unauthorised individuals from accessing aircraft and restricted areas. A threat involving an authorised crew member presents a different challenge.

Investigators are therefore likely to examine:

• Pilot recruitment procedures
• Background and security checks
• Aviation licensing
• Psychological assessment
• Previous employment records
• Crew assignment procedures
• Cockpit-access protocols
• Emergency response procedures
• Information sharing between aviation authorities

The case could ultimately lead airlines and regulators to reconsider how potential insider threats are identified.

Why Israel Is Reviewing Pilot Security

The aircraft’s destination adds another layer to the investigation.

FZ1073 was bound for Ben Gurion Airport, one of the world’s most security-sensitive aviation destinations.

The reported nationality of the suspected co-pilot and the fact that Oman and Israel do not have diplomatic relations have prompted questions about crew screening and assignment procedures for flights into Israel.

Israeli authorities have indicated that aviation-security procedures concerning foreign airline crews are being reviewed.

The precise circumstances surrounding the pilot’s assignment to FZ1073 remain part of the investigation.

What Investigators Need to Establish

Several major questions remain unanswered.

The exact cockpit sequence

Investigators need to determine precisely what happened between the two pilots and who was controlling the aircraft during each stage of the descent.

The motive

They must establish why the alleged attack occurred and whether it was driven by ideology, personal circumstances, political objectives or another motive.

Advance planning

Investigators must determine whether the attack was planned in advance and, if so, when the planning began.

Possible accomplices

Authorities need to establish whether the suspect acted alone or received assistance, instructions or financial or logistical support.

Pilot screening

The investigation will examine whether relevant warning signs existed before the suspect was employed as a commercial pilot.

International connections

Authorities in several countries are examining aspects of the suspect’s background to determine whether any of those connections are relevant to the incident.

A Narrowly Avoided Disaster

The FZ1073 incident is remarkable because several separate events combined to prevent a potentially catastrophic outcome.

The captain, despite being injured, helped make cockpit access possible.

Passengers and crew members intervened against the alleged attacker.

Additional qualified pilots were available in the cabin.

Saudi authorities prepared for the emergency landing.

And the aircraft itself remained capable of being flown to a safe airport.

Any one of those factors being absent could have made the emergency significantly more difficult to manage.

Flydubai’s Response

Flydubai confirmed that the incident occurred during FZ1073’s journey from Dubai to Tel Aviv and that the aircraft diverted to Tabuk.

The airline later confirmed that passengers and crew were safe and thanked the captain, pilots, cabin crew, passengers and Saudi authorities for their assistance.

Flydubai has also stressed that the circumstances and motives surrounding the incident remain matters for the official investigation.

Flydubai FZ1073 Incident Timeline

Exact timings of individual cockpit events remain subject to the official investigation.

What Is Confirmed vs What Is Still Alleged?

This distinction is important because the investigation is still developing.

Conclusion

The Flydubai FZ1073 incident was a dramatic mid-air emergency that could have ended very differently.

A flight travelling normally from Dubai to Tel Aviv suddenly became a cockpit security crisis. The UAE says the co-pilot attacked the captain with a crash axe and attempted to take control. The aircraft subsequently experienced an extreme descent before passengers, crew members and additional pilots helped stabilise the situation.

The aircraft was diverted to Tabuk, Saudi Arabia, and landed safely.

The incident is now being investigated not only as an aviation emergency but as an alleged attempted terrorist act. Authorities are examining the suspect’s background, possible advance planning, motive, international connections and the effectiveness of pilot screening and aviation-security procedures.

For the passengers aboard FZ1073, the most important fact is simple: the aircraft landed safely and everyone was accounted for.

For the aviation industry, however, the incident raises a much larger question: how can airlines identify and prevent an insider threat when the alleged attacker is already authorised to sit in the cockpit?

The answer will depend on the findings of the UAE-led investigation and could influence aviation-security procedures well beyond flydubai.

Information current to 6 October 2026. Allegations concerning motive, planning, radicalisation and international connections should be treated as unproven until confirmed by competent investigative or judicial authorities.