> ## Content Index
> Fetch the complete content index at: https://beirutwire.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Everything We Know About the Flydubai Flight Attack
- URL: https://beirutwire.com/everything-we-know-about-the-flydubai-flight-attack/
- Published: 2026-10-02T05:54:50.000Z
- Updated: 2026-10-02T05:54:50.000Z
- Description: Flydubai flight FZ1073 was carrying 174 passengers from Dubai to Tel Aviv when its co-pilot attacked the captain and the aircraft plunged thousands of feet before passengers and additional pilots regained control. The plane eventually landed safely in Tabuk, Saudi Arabia.
- Author: Beirut Wire
- Tags: Politics

A Flydubai flight from Dubai to Tel Aviv came close to disaster on September 30 after the co-pilot attacked the captain inside the cockpit, sending the aircraft into a steep descent before passengers and additional pilots managed to regain control.

Two days later, investigators are still trying to establish the most important unanswered question: why it happened.

Here is everything confirmed so far.

Flydubai flight FZ1073 departed Dubai International Airport on the morning of September 30 bound for Ben Gurion Airport in Israel.

The Boeing 737 MAX 8 was carrying 174 passengers and eight crew members, according to Saudi Arabia’s Interior Ministry.

At some point during the flight, a violent confrontation erupted inside the cockpit.

Saudi Arabia’s preliminary investigation has confirmed that the co-pilot assaulted the captain, leaving both men injured. Flydubai initially described what happened more cautiously as an “altercation” in the flight deck.

Accounts from passengers and Israeli officials provide a much more dramatic picture.

According to Israeli Prime Minister Benjamin Netanyahu and multiple passengers aboard the aircraft, the co-pilot stabbed Captain Smit Machchhar, an Indian national, and then apparently attempted to force the aircraft into a crash.

Flight-tracking data shows just how severe the situation became.

The aircraft suddenly lost thousands of feet of altitude during the incident. Different tracking analyses have measured the drop differently depending on the time interval examined, but data reviewed by major news organizations showed the plane falling roughly 14,000 to 17,000 feet during the most violent part of the descent.

The aircraft also transmitted emergency signals.

Flight data showed the crew using the general emergency transponder code 7700 before transmitting 7500, the internationally recognized code indicating unlawful interference with an aircraft.

That immediately raised fears of a hijacking.

Israeli officials said the country’s air force detected that the aircraft had deviated from its expected flight path and was descending rapidly. When attempts to contact the plane initially failed and the unlawful-interference alert appeared, Israel briefly prepared for the possibility of an attack involving the aircraft.

Inside the cockpit, however, the captain was still fighting back.

Despite being injured, Machchhar reportedly managed to unlock or open the cockpit door, allowing people outside to intervene.

Passengers then helped overpower and restrain the co-pilot.

Two additional Flydubai pilots who happened to be travelling aboard the flight were able to enter the cockpit, regain control of the aircraft and ultimately divert it to Saudi Arabia.

The plane landed safely at Prince Sultan bin Abdulaziz International Airport in Tabuk at approximately 9:45 a.m. local time.

All 174 passengers survived.

Saudi authorities said the passengers were later placed aboard a replacement Flydubai aircraft and continued their journey at around 5:40 p.m. The remaining crew returned separately to Dubai.

The captain and co-pilot remained behind.

Both were taken to hospital in Saudi Arabia because of their injuries.

On the morning of October 1, after doctors cleared them to travel, both men were transferred to Abu Dhabi accompanied by an Emirati security team.

The investigation has now shifted primarily to the United Arab Emirates.

The UAE attorney general has ordered a formal investigation into the circumstances surrounding the attack, including whether it involved terrorism, advance planning or instructions from another person or organization.

That distinction is important because Israeli officials have already publicly characterized the incident as terrorism.

Israeli Defense Minister Israel Katz described it as an attempted jihadist attack.

Netanyahu has gone further, saying Israeli authorities believe the co-pilot had undergone “radical Islamist indoctrination” and was suicidal. Israeli security officials have also said they are examining whether the incident was intended to become a mass-casualty attack similar in concept to the September 11 attacks.

But those claims have not yet been established by the official UAE investigation.

Flydubai has specifically urged against premature conclusions about the attacker’s motive, saying the reasons behind the incident remain subject to investigation.

The suspected attacker has widely been identified by Israeli officials and international reporting as an Omani national.

Omani officials have confirmed to CBS News that the man was born in Oman and holds Omani citizenship, although Saudi Arabia’s official statement focused on the circumstances of the attack rather than identifying him publicly.

His nationality has raised another question.

Netanyahu has said arrangements surrounding flights to Israel normally restrict pilots from countries that do not have diplomatic relations with Israel from operating those routes.

Oman does not have formal diplomatic relations with Israel.

Investigators are therefore also examining how the co-pilot was assigned to the Tel Aviv flight and whether existing airline or security procedures were followed.

The attack is consequently becoming a much broader aviation-security case.

Modern cockpit doors were heavily reinforced after the September 11 attacks specifically to prevent passengers or hijackers from entering the flight deck.

But the Flydubai incident demonstrates the opposite problem: what happens if the security threat is already inside the cockpit.

Aviation specialists say the case is likely to intensify scrutiny of pilot vetting, psychological monitoring, crew procedures and protocols for dealing with a hostile pilot while an aircraft is airborne.

It has also become politically sensitive because of the route involved.

Flydubai has operated direct services between the UAE and Israel since the countries normalized relations under the Abraham Accords in 2020.

The route became one of the most visible examples of the new relationship, carrying large numbers of Israeli travellers to Dubai.

An apparent deliberate attempt to destroy an Israel-bound aircraft therefore immediately raised questions about whether the attack was motivated specifically by its destination.

For now, investigators have not publicly established that link.

There is also no publicly verified evidence that Iran or any other government or armed organization directed the attack.

U.S. President Donald Trump has warned that Iran would face severe consequences if evidence emerged linking Tehran to the incident, but the warning was conditional and no such connection has been established.

The most firmly established sequence remains much simpler.

A co-pilot attacked the captain.

The aircraft entered a dangerous descent.

The injured captain managed to help open the cockpit to intervention.

Passengers restrained the attacker.

Additional pilots regained control.

And 174 passengers ultimately landed safely in Saudi Arabia.

What investigators must now determine is whether this was the act of one individual, a planned terrorist attack, or something involving a wider network.

Until the UAE investigation answers that question, the motive behind one of the most extraordinary aviation incidents in the region in years remains unresolved.