Flydubai FZ1073: What We Know About the Pilot Stabbing, 14,000-Foot Plunge and Alleged Crash Attempt

Last reviewed: September 30, 2026

A Flydubai passenger flight from Dubai to Tel Aviv made an emergency landing in Tabuk, Saudi Arabia, on September 30 after a violent incident in the cockpit. Public flight-tracking data show an extreme descent. Flydubai confirms an altercation on the flight deck; Israeli officials say the co-pilot stabbed the captain and apparently tried to crash the aircraft.

Passengers and crew intervened. Flydubai says on-duty airline personnel traveling aboard the aircraft secured it, diverted it to Tabuk and landed it safely. Passengers later continued to Tel Aviv on a replacement flight.

The broad sequence is now strongly supported by airline and aviation-authority statements, flight-tracking data, passenger accounts and reporting by major news organizations. The attacker’s intent and motive, the cause of the aircraft damage, and the exact sequence of events remain under investigation.

The short answer

Flydubai flight FZ1073 was operating from Dubai International Airport to Ben Gurion Airport near Tel Aviv aboard a Boeing 737 MAX 8. Aviation incident reporting identified the aircraft as registration A6-FKF. AP reported that 174 people were on board. AeroInside incident summary About two and a half hours into the flight, the aircraft made a series of sharp altitude changes, including a reported loss of nearly 14,000 feet in less than 30 seconds.

The aircraft transmitted emergency transponder codes and requested an emergency landing at Tabuk. It landed safely at about 9:45 a.m. local time, according to the airport account. Both operating pilots were injured and taken to a hospital. Passengers later reached Tel Aviv aboard a replacement aircraft. AP reported that three passengers received treatment for minor injuries.

Flydubai has confirmed that an altercation occurred in the cockpit. Israeli officials say the co-pilot stabbed the captain and apparently attempted to crash the plane. Flydubai and the UAE General Civil Aviation Authority have said the reasons and motive remain under investigation. That distinction matters: the evidence supports a grave cockpit security incident, but the alleged attacker’s intent has not been established in a completed investigative finding.

What is confirmed, what is strongly supported, and what remains unresolved

A minute-by-minute reconstruction of FZ1073

Public flight data provide an unusually useful record of the aircraft’s external movements. They cannot reveal what happened inside the cockpit, and published reconstructions differ by a few minutes on some transponder events. Times below are approximate and in UTC unless stated otherwise.

India Today’s OSINT analysis of Flightradar24 data calculated a drop from 30,875 feet to 16,750 feet between 05:22:07 and 05:22:36 UTC: 14,125 feet in 29 seconds. Khaleej Times also published a Flightradar24-based timeline, placing the 7700 and 7500 changes at about 05:31 and 05:38 UTC. Reuters described the plunge as nearly 14,000 feet in less than 30 seconds. Al Jazeera’s public reconstruction places the emergency codes a few minutes earlier. These are different published reconstructions of public tracking data, so the exact values and times should remain attributed until investigators release authoritative records. India Today OSINT analysis · Khaleej Times timeline · Reuters reconstruction · Al Jazeera timeline

The published flight path also shows the aircraft briefly entering Jordanian airspace before turning back toward Saudi Arabia. The important sequencing point is that the sharp descent appears to have begun before the emergency transponder sequence became visible in public tracking data. That does not show who caused the descent or why. It does show that the aircraft was already undergoing a dramatic flight event before the codes appeared in those public reconstructions. Al Jazeera timeline

The Tabuk airport account, reported by the Saudi Gazette, says controllers received the emergency request at 8:44 a.m. local time and that the aircraft landed at 9:45 a.m. It also says both operating pilots were taken to hospital and that passengers departed aboard a replacement aircraft at 5:40 p.m. local time. AP and Reuters subsequently reported that passengers arrived at Ben Gurion Airport later that day. Tabuk airport account via the Saudi Gazette · AP report on the passengers’ return

What happened inside the cockpit?

The broad outline is increasingly well corroborated, even though not every detail has been independently established. Reuters interviewed passenger Almog Italie, who described the aircraft dropping, stabilizing, then dropping again as passengers moved toward the front of the cabin. Reuters also reported verifying video recorded aboard the plane after the confrontation. The footage showed two bloodied men on the floor; people filming identified one as the attacked pilot and the other as the attacker, who appeared to wear first-officer insignia.

Doron Spielman, a spokesperson for the Israeli prime minister’s office, told Reuters that the wounded captain managed to release the cockpit door before passengers entered and subdued the other pilot. That detail currently rests on an Israeli official’s account of what passengers reported, not on a released cockpit recording or a completed investigation.

Flydubai’s public statement confirms the narrower operational point: an altercation occurred on the flight deck, and on-duty Flydubai personnel traveling aboard the plane secured the aircraft, diverted it and landed it in Tabuk. Reuters passenger reconstruction · Flydubai statement reported by Emirates 24|7

Did passengers actually save the airplane?

The evidence strongly suggests passengers played a critical role in entering the cockpit and helping restrain the alleged attacker. Passengers have described participating directly, and Israeli officials have credited passenger intervention.

It would go too far, though, to say that passengers themselves flew FZ1073 to Saudi Arabia. Flydubai says on-duty airline crew traveling aboard ultimately secured, diverted and landed the aircraft. Passengers and news reports have described additional qualified Flydubai pilots aboard who took control after the confrontation.

That distinction preserves both parts of the account: passengers appear to have intervened during the cockpit struggle, while Flydubai credits airline personnel aboard with securing and landing the aircraft. Airlines do sometimes transport pilots as passengers while they travel between assignments; the presence of additional pilots appears to have provided a backup flight crew in an extraordinary emergency.

Did the co-pilot actually try to crash the plane?

This is the central unresolved factual question.

Netanyahu said the co-pilot stabbed the captain and apparently attempted to crash the aircraft. Israel’s defense minister described the event as an attempted jihadist terrorist attack and said preliminary Israeli information indicated an intention to kill everyone aboard.

Those are Israeli government assessments, not yet the findings of the aviation investigation. Flydubai says the reasons and motives remain unknown and subject to formal investigation. The UAE GCAA describes the event as a security incident, says its investigation is examining operational and security aspects, and has urged the public not to pre-empt its findings. UAE GCAA statement via Emirates News Agency

That does not mean Israel’s assessment is unsupported. The combination of a reported stabbing in the cockpit, an extreme descent, a 7500 unlawful-interference code, passenger intervention and accounts that the alleged attacker interfered with aircraft controls is substantial evidence of an event far more serious than an ordinary fight between colleagues.

But the formal investigation must answer questions that political statements and passenger video cannot resolve on their own: what control inputs were made and by whom; whether systems were deliberately disconnected or altered; whether the descent was intentional; and what communications or planning preceded the attack. Until then, “alleged attempt to crash the aircraft” is the strongest description that reflects both the evidence and what remains unknown.

Was this a hijacking?

Not necessarily in the conventional sense, even though the aircraft reportedly transmitted code 7500.

The FAA describes 7500 as the code associated with unlawful interference. Its guidance connects the code to an aircraft being hijacked or forced toward another destination. Code 7700, by comparison, is the general emergency code. FAA guidance on unlawful interference

FZ1073 reportedly transmitted 7700, changed to 7500, and later returned to 7700. If confirmed by authoritative flight records, that sequence is powerful evidence that someone with access to the aircraft’s transponder communicated an unlawful-interference emergency. It does not, by itself, establish who selected each code, what that person knew at the time, or the attacker’s ultimate objective.

A pilot attacking another pilot in an effort to seize control of an aircraft would plainly constitute unlawful interference, even if the objective were to crash the plane rather than redirect it. Whether investigators or authorities formally classify the event as a hijacking will depend on the evidence and the definition they apply.

The aircraft appears to have suffered serious rudder damage

Photographs taken after the aircraft landed show substantial damage to the Boeing 737 MAX 8’s rudder, the movable flight-control surface mounted on its vertical tail. AP reported that most of the rudder had been torn away and that aviation experts were surprised the aircraft remained controllable after the descent and damage.

The damage is visible; its timing and cause are not established. The aircraft underwent an extraordinary descent and reportedly reached unusually high speeds, making aerodynamic loads one obvious line of investigation. Investigators will need to establish when the damage occurred, what loads the aircraft experienced, and whether other structural or control-system damage occurred.

It would be premature to say the attacker ripped the rudder off by diving the aircraft. The defensible account is that FZ1073 landed with substantial visible rudder damage after an extreme in-flight event, while investigators have not publicly established the damage’s precise cause. AP report

Where did the weapon come from?

There is not yet a satisfactory public answer to how a weapon was available in the cockpit.

Passengers have described a stabbing or knife attack, and video and images reported by news organizations show severe injuries. But no authoritative source reviewed for this article has publicly identified the weapon, established its size or origin, or explained how it became available aboard the aircraft.

That distinction matters. Saying that a pilot “smuggled a knife through airport security” assumes facts investigators have not established. Commercial pilots undergo security screening, but an aircraft also contains tools, catering items and emergency equipment. The presence of a sharp object aboard does not by itself establish how it entered the aircraft or who brought it there.

The question of how the weapon became available is among the issues raised in reporting about the incident. Until authorities identify it and reconstruct its provenance, the weapon’s origin remains unknown.

Why did the plane land in Saudi Arabia?

Once the aircraft was under control, the immediate priority was to get it on the ground safely. Tabuk was the airport where it made its emergency landing. The aircraft had undergone an extreme flight event, both operating pilots were injured, and the extent of aircraft damage would not necessarily have been known in the air.

The diversion created a diplomatic point of interest because Saudi Arabia and Israel do not maintain formal diplomatic relations. But an aviation emergency does not wait for diplomatic normalization. Saudi airport authorities activated emergency procedures, received the aircraft, arranged medical care for the injured pilots and assisted passengers in the terminal. Passengers later departed for Israel aboard a replacement aircraft.

How many people were aboard?

Early reports gave varying estimates, including approximately 150, 170, 174 or 180 people. AP later reported that the flight was carrying 174 people. That is the clearest figure in the sources cited here, although Flydubai’s public statement reviewed for this article did not provide an official passenger-manifest total.

The distinction between “people aboard” and “passengers” also matters: a total aboard can include the operating crew and other airline personnel traveling on the flight. Unless Flydubai releases a manifest figure, 174 should be attributed to AP rather than presented as an airline-confirmed passenger count.

Who were the pilots?

Some outlets have identified the injured captain as Smit Machchhar, an Indian pilot, and Israeli officials have reportedly identified the alleged attacker as an Omani co-pilot. These identifications are widely reported, but Flydubai’s public statements cited here do not name either pilot or confirm their nationalities.

In the first hours after the incident, inaccurate claims also circulated describing the pilots as Russian and Ukrainian. Khaleej Times reported that the Russian Consulate General in Dubai called the claim that a Russian pilot was aboard unfounded. That early confusion is a reason to distinguish widely reported identities from details confirmed by the airline or investigators. Khaleej Times report

The central questions are not the pilots’ nationalities. They are what the investigation establishes about the attack, the motive, the airline’s security procedures, and how control of the aircraft was regained. Names and nationalities should be updated if authorities confirm them, and clearly attributed in the meantime.

What investigators should be able to determine

This is an unusually evidence-rich aviation investigation. The aircraft survived. The injured captain survived. The alleged attacker survived, according to current reporting. Passengers and reserve crew witnessed parts of the event. Video was recorded aboard the aircraft, and flight-tracking data captured its external movements. Investigators should also have access to the Boeing’s cockpit-voice recorder, flight-data recorder and aircraft systems.

Those records could help establish:

• when the violence began and what the pilots said to one another;
• who moved the flight controls during each descent and whether the changes were deliberate;
• whether the autopilot or other systems were disconnected or altered;
• what caused the rudder damage and when it occurred;
• who selected the 7700 and 7500 transponder codes;
• how the cockpit door was opened and who entered;
• what weapon was used and how it became available aboard the aircraft; and
• whether evidence points to planning, ideology, personal conflict, suicide intent or another motive.

This is why the distinction between what happened and why it happened matters. We already know a great deal about the aircraft’s movements and have multiple accounts of violence and intervention. We know far less about intent, motive and the precise sequence of cockpit actions.

What happens next?

The UAE GCAA says investigators are examining operational and security issues in coordination with relevant authorities. Saudi authorities are also investigating the emergency landing and injuries. Israeli officials have announced a security review; Reuters reported plans to increase checks involving pilots operating flights into Israel.

The inquiries may also examine the security arrangements and crew-related provisions governing flights between the UAE and Israel. Reuters reported that Israel planned tighter checks on pilots flying into the country and a joint review with its defense establishment. Those questions should be framed as matters for the review, not as proof that any rule was broken. Reuters report on Israel’s planned pilot checks

If investigators establish that a credentialed airline pilot deliberately attacked another pilot in an effort to destroy a passenger aircraft, the case will raise difficult questions about insider threats, pilot vetting, cockpit procedures, crew screening, and safeguards when a threat comes from someone authorized to enter the flight deck. Those conclusions depend on the investigation’s findings, which have not yet been released.

Bottom line

A violent cockpit incident occurred on Flydubai flight FZ1073. The aircraft underwent an extreme descent, transmitted emergency codes, diverted to Tabuk and landed safely. Both operating pilots were injured. Passengers and crew intervened, and Flydubai says on-duty airline personnel aboard the aircraft secured and landed it. The aircraft showed substantial rudder damage, and passengers later reached Tel Aviv on a replacement flight.

Israeli officials say the co-pilot stabbed the captain and intended to crash the aircraft. That assessment is supported by serious evidence and passenger accounts, but the exact control inputs, the attacker’s motive and the cause of the aircraft damage have not been established in a completed investigation. Flydubai and the UAE GCAA say the inquiry is ongoing.

For now, the strongest evidence supports a narrower but still extraordinary conclusion: FZ1073 survived a violent act of unlawful interference in its cockpit that came frighteningly close to becoming an aviation catastrophe. Whether it was a deliberate crash attempt, a terrorist attack, or something else is a question for investigators with access to physical, digital and eyewitness evidence.

References and further reading

Primary and authoritative aviation sources

• UAE General Civil Aviation Authority statement on the FZ1073 security incident, via Emirates News Agency — Confirms the event was treated as a security incident and that operational and security investigations are continuing.
• Prince Sultan bin Abdulaziz International Airport account, via the Saudi Gazette — Gives the emergency-call and landing times, reports both pilots were hospitalized and says passengers departed aboard a replacement aircraft.
• FAA guidance on unlawful interference and transponder code 7500 — Explains the code’s use in unlawful-interference emergencies.

Flight data and aviation reconstruction

• Khaleej Times flight-data reconstruction — Publishes a Flightradar24-based timeline and reports the Russian consulate’s denial that a Russian pilot was aboard.
• India Today OSINT analysis — Gives the specific 14,125-foot loss over 29 seconds derived from Flightradar24 data.
• Al Jazeera’s FZ1073 timeline — Provides a public flight-data timeline, including a different set of approximate emergency-code times.
• Reuters reconstruction of the descent and cockpit struggle — Includes passenger accounts and the reported descent.\n- AeroInside incident summary — Identifies the aircraft registration as A6-FKF.

Independent reporting and witness evidence

• Associated Press: “Pilot stabs fellow pilot on flight to Israel before passengers intervene” — Reports the 174-person figure, passenger return to Israel, minor passenger injuries, the reported arrest and visible rudder damage.
• Reuters report on Israel’s planned pilot checks — Reports on Israel’s intended security response and a joint review with its defense establishment.
• Reuters report on passengers reaching Israel and the investigation — Reports on passenger and crew intervention, the replacement flight and the unresolved motive.
• Financial Times passenger reconstruction — Detailed reconstruction based on passenger accounts; the article may require a subscription.
• Flydubai statement reported by Emirates 24|7 — Reports the airline’s account of the flight-deck altercation, crew response and warning against speculation.

This article reflects reporting and official statements available on September 30, 2026. It concerns an active investigation and should be updated when Flydubai, the UAE GCAA, Saudi authorities or other investigators release new findings.