Flydubai Flight to Tel Aviv Diverts to Saudi Arabia After Cockpit Altercation Between Pilots

What triggered the descent

The most detailed public account of what happened inside the cockpit comes from Israeli officials rather than from flydubai or Saudi aviation authorities, who have so far confirmed only that an "incident" occurred and that the aircraft diverted safely. Israeli Prime Minister Benjamin Netanyahu said publicly that "one of the pilots stabbed the other and apparently attempted to crash the plane with everyone on it," a characterization also reported by CNN and the Washington Post. Israeli Defense Minister Yisrael Katz went further, saying the individual responsible "had a single objective: to crash the plane, killing everyone on board" — a claim that, as of publication, has not been independently verified by aviation investigators or corroborated with technical evidence from the flight data recorder.

Passenger accounts relayed to CBS News describe a struggle inside the cockpit, with one passenger, Miryam Shira Ohayon, saying that "the co-pilot tried to murder the pilot and basically carry out a suicide attack on the plane." According to that and other passenger accounts, off-duty crew members and at least one other person on board intervened, gained access to the cockpit, and helped subdue the individual responsible for the stabbing, allowing another crew member to stabilize the aircraft's flight path.

flydubai's own public statement has been narrower in scope. The airline said the aircraft "experienced an incident while en route" and confirmed it "has landed safely in Tabuk, and all passengers are safe and accounted for," adding that "the safety and well-being of our passengers and crew remain our highest priority." The airline has not confirmed the specific nature of the cockpit altercation, the number of people involved, or whether the descent was a deliberate control input rather than a response to the physical struggle for control of the aircraft.

Injuries and the aftermath in Tabuk

Multiple outlets reported that both pilots were wounded, with the pilot who was reportedly attacked sustaining stab wounds. Saudi authorities said two crew members were hospitalized with injuries described as unspecified in severity. No passenger injuries have been reported by any outlet reviewed for this article. Of the 174 people on board, Israeli media reported that 166 were Israeli nationals, a detail relevant to why Israeli officials — rather than UAE or Saudi authorities — were the first to speak publicly and in detail about the incident's cause.

The individual identified by Israeli officials as responsible for the stabbing was reportedly taken into custody by Saudi authorities upon landing and is being questioned. NewsFellow is not naming or identifying that individual, consistent with standard practice while facts remain under investigation and no charges have been formally confirmed through a judicial process. Reports describing the person's nationality or possible motive — including suggestions of a "terror" motive or an "Iranian connection" floated by Israeli officials — remain unconfirmed by independent investigators and are not corroborated by evidence made public as of this writing.

Why the descent was so extreme

Aviation-focused outlets covering the incident noted that a descent of the magnitude reported — several thousand feet in a matter of minutes — is consistent with either a deliberate nose-down input at the controls or a violent struggle over the yoke and control column, rather than a mechanical malfunction. One report indicated the aircraft may have experienced aerodynamic stress on its rudder as a result of the abrupt maneuvering, though this detail has not been confirmed by flydubai, Boeing, or Saudi civil aviation authorities and should be treated as preliminary until an official investigation, if one is opened, is completed.

Because the flight crossed into Saudi airspace before diverting, the incident places Saudi General Authority of Civil Aviation and, potentially, Saudi security services in the position of leading any formal investigation, even though the flight originated in the UAE and was destined for Israel — two countries with which Saudi Arabia does not maintain full diplomatic relations. That geopolitical backdrop has fueled some of the speculation around motive, but as with other unconfirmed details in this story, NewsFellow is treating claims about intent, coordination, or organizational backing as unverified pending any formal statement from Saudi, UAE, or international aviation-safety authorities.

A rare route now under fresh scrutiny

Flydubai's Dubai-Tel Aviv service is one of only a handful of scheduled air links between the Gulf and Israel, launched in the wake of the 2020 Abraham Accords that normalized diplomatic relations between the UAE and Israel. The route has operated on and off since, occasionally suspended during periods of regional tension, including brief halts tied to wider conflict in the Middle East over the past two years. Because so few carriers fly the corridor directly — El Al and Israir on the Israeli side, flydubai as the primary Gulf operator — any disruption to the route draws outsized attention from both governments and from the roughly triangular diplomatic relationship between the UAE, Israel, and Saudi Arabia, the last of which has not normalized ties with Israel but permits certain overflights.

That backdrop matters because it shapes who is speaking publicly about the incident and why. Israeli officials, including the prime minister and defense minister, have been unusually quick and direct in characterizing the event as an attempted attack rather than waiting for a joint or Saudi-led technical investigation to conclude. Aviation-safety specialists interviewed by various outlets have cautioned that political statements made within hours of an in-flight emergency — however serious — typically run ahead of the forensic work needed to establish intent, sequence of events, and responsibility. Cockpit voice recorder and flight data recorder analysis, along with interviews of surviving crew and passengers conducted by trained investigators, normally take days to weeks even in comparatively straightforward incidents.

Industry context: cockpit security since 2015

Commercial aviation's approach to in-flight cockpit security was reshaped after the 2015 Germanwings Flight 9525 disaster, in which a first officer locked the captain out of the cockpit and deliberately crashed the aircraft into the French Alps, killing all 150 people on board. That event led many regulators and airlines to mandate that at least two authorized crew members remain in the cockpit at all times, a rule some carriers have since relaxed as fatigue-management research evolved. It is not yet publicly known whether flydubai's two-person cockpit policy was in effect and, if so, how a struggle between the two pilots was able to escalate to the point of a knife attack and an attempted takeover of the flight controls. Boeing has not commented publicly on the 737 MAX 8's cockpit-access systems in relation to this specific event, and flydubai has not addressed the question of crew-access protocol in its statements so far.

The involvement of off-duty personnel or passengers in regaining control, as described in multiple passenger accounts, would be unusual even by the standards of past cockpit-security incidents, most of which have involved either a single rogue crew member acting alone with no resistance (as in the Germanwings case) or attempts by an outside hijacker to breach a locked cockpit door from the cabin. If confirmed, an account in which the flight was brought under control by people other than on-duty flight crew would raise distinct questions for accident investigators about how quickly and by what means that intervention occurred at cruising altitude on a twin-engine narrowbody jet.

What happens next

Passengers were deplaned safely in Tabuk, and flydubai has not yet detailed how it will get the 174 people who were on FZ1073 to their original destination or return them to Dubai. Airlines involved in incidents that trigger a 7500 squawk typically face a multi-agency review — in this case potentially involving Saudi aviation authorities, the UAE's General Civil Aviation Authority, and Boeing, given the aircraft type involved. flydubai has not said whether the aircraft, registration A6-FKF, remains grounded in Tabuk pending inspection or has since been cleared to reposition.

For flydubai, a Dubai-government-owned carrier that operates one of the busiest 737 MAX fleets in the Middle East and has previously flown routes into Tel Aviv as one of the few Gulf carriers to maintain such service, the incident is likely to draw scrutiny of cockpit security procedures industry-wide, particularly around two-person cockpit protocols and rest-crew access. It is also likely to reignite scrutiny of route security on the small number of direct Gulf-Israel air links that have operated intermittently since the normalization agreements between Israel and several Gulf states.

As of publication, no aviation regulator — Saudi, Emirati, Israeli, or international — has issued a formal incident report, and the account of what happened in the cockpit rests primarily on statements from Israeli political leaders and passenger accounts relayed to media, rather than on a completed technical investigation. NewsFellow will continue to treat unconfirmed details, including the attacker's identity, nationality, and alleged motive, as unverified until independent confirmation is available.

Sources

• Pilot on Tel Aviv-bound flight tried to crash plane after cockpit stabbing, Netanyahu says — The Washington Post
• Dubai to Israel flight makes emergency landing, passenger says "co-pilot tried to murder the pilot" and crash jet — CBS News
• Israel: Flydubai pilot tried to hijack Tel Aviv flight, all passengers safe — The Jerusalem Post
• Flight to Tel Aviv diverted to Saudi Arabia after pilot 'stabbed the other': Netanyahu — ABC News