A Boeing 737 MAX 8 operated by Flydubai departed Dubai bound for Tel Aviv with more than 150 passengers on board. Minutes into the flight, the situation deteriorated sharply: a steep loss of altitude, emergency transponder codes, and an eventual diversion to Saudi Arabia. Flight FZ1073 quickly became the focus of an international security alert. Beyond early claims of a terrorist attack, one question remains: what actually happened inside the cockpit?
The sequence of events on flight FZ1073
Tracking data shows the aircraft descended several thousand meters in a very short time. The crew then transmitted code 7700, signaling a general emergency, followed by code 7500, reserved for unlawful interference — a signal associated with hijacking scenarios.
Israel launched a precautionary military response, scrambling fighter jets. On board, passengers reported hearing screams and seeing blood. Multiple accounts describe a violent confrontation between the two pilots, with one of them wounded by a bladed weapon. Passengers reportedly intervened in the cockpit.
Both pilots were hospitalized after the landing at Tabuk, Saudi Arabia. All passengers were declared safe. Flydubai confirmed only that an “incident” occurred during the flight, without publicly detailing its nature.
Competing narratives and the limits of what is known
In the first hours, several accounts circulated almost simultaneously: hijacking, a suicide attempt, a terrorist attack, a struggle between pilots. Some Israeli media even raised the possibility that a pilot intended to crash the aircraft.
These scenarios are not equivalent, and none is yet established. Two Israeli officials described the event as a possible “terrorist attack” while noting that the investigation was ongoing. Contradictory versions also emerged regarding the circumstances and even the nationality of the pilots.
The established fact is an extremely violent incident that triggered an emergency. The motive remains a matter for the investigation.
Why 9/11 comparisons are premature
The analogy to the September 11, 2001 attacks carries heavy implications. 9/11 was a coordinated terrorist operation involving multiple hijacked aircraft used as weapons. In the case of flight FZ1073, nothing in the publicly available information so far establishes a comparable plan, organization, or demonstrated intent to use the aircraft as a weapon.
Some passenger accounts describe a situation that, from the cabin, felt like an imminent catastrophe. One passenger said she heard screams, saw blood, and believed the plane would crash.
That distinction matters: the fear passengers experienced is a fact; interpreting that fear as terrorism remains a hypothesis.
The cockpit as the investigation’s central grey area
The most puzzling element may not be the dramatic code 7500, but what happened in the seconds before it was activated.
- Who was actually controlling the aircraft?
- Why did the plane lose altitude so abruptly?
- Who triggered the different emergency codes?
- When did passengers enter the cockpit?
- Was one pilot attempting to seize control to divert or crash the plane, or did the situation stem from a confrontation whose consequences spiraled beyond the crew’s control?
Flight data can help reconstruct the timeline. Cockpit voice and flight recorders, along with air traffic control communications, will likely be decisive in distinguishing a deliberate act, a struggle, or a temporary loss of control.
A crisis that extends far beyond the aircraft
The case takes on added significance because the aircraft carried Israeli passengers and was heading to Tel Aviv. The alert unfolded in a region already under heavy security tensions. The plane ultimately landed at Tabuk, in Saudi Arabia — a country with which Israel still has no official diplomatic relations.
What began at several thousand meters altitude rapidly became a diplomatic and military problem: fighter jet interception, Israeli security consultations, the handling of Israeli nationals on Saudi territory, and an investigation involving multiple authorities.
That may be the real takeaway: in modern aviation, a few seconds of uncertainty in a cockpit can trigger consequences far beyond the aircraft itself.
What is established — and what is not
At this stage, several elements are confirmed: the aircraft suffered a serious incident, both pilots were injured, the plane experienced a steep descent, emergency codes were transmitted, and the aircraft landed at Tabuk with passengers safe.
However, the motive of those involved, the exact intent behind the confrontation, and the possible existence of a plan to turn the aircraft into a weapon are not publicly established.
That zone of uncertainty should be the focus of the investigation. In such a sensitive case, the most important question may not be “Was this a new 9/11?” It is rather: “How could a commercial airliner end up in a situation where, for several minutes, no one outside the cockpit knew who truly had control?”
The answer now lies with investigators, flight data, the aircraft’s recorders, and accounts gathered from the crew and passengers.
