A routine flight that turned into an international crisis
A Boeing 737 MAX 8 operated by Flydubai left Dubai bound for Tel Aviv with more than 150 passengers on board. Within minutes, flight FZ1073 became the centre of an international security emergency: a violent incident in the cockpit, a steep loss of altitude, an emergency code linked to hijackings, and an eventual emergency landing in Saudi Arabia. Beyond the initial claims of a terrorist attack, one question remains: what actually happened inside the cockpit?
The sequence of events
Tracking data shows an extremely rapid descent — several thousand metres lost in a very short time. The aircraft then transmitted code 7700, signalling a general emergency, before sending code 7500, used when a crew reports unlawful interference on board, including situations that could correspond to a hijacking.
For authorities and people on the ground, uncertainty was at its peak.
Israel launched a military response, sending fighter jets as a precaution. On board, several passengers reported hearing screams and seeing blood. According to multiple accounts, a violent confrontation apparently took place between the two pilots, one of whom was wounded with a bladed weapon. Passengers then reportedly intervened in the cockpit.
Both pilots were hospitalised after landing in Tabuk, Saudi Arabia. All passengers were declared safe and sound. Flydubai limited itself to confirming that an “incident” had occurred during the flight, without publicly specifying its nature.
The detail that changes everything
In the early hours, several narratives circulated almost simultaneously: hijacking, suicide attempt, terrorist attack, struggle between pilots. Some Israeli media even raised the possibility that a pilot had tried to crash the plane.
But these scenarios are not equivalent and, more importantly, they are not yet established.
Reuters reported that two Israeli officials described the event as a possible “terrorist attack”, while noting that the investigation was ongoing. The agency also pointed to contradictory versions regarding the circumstances and even the nationality of the pilots.
In other words: the established fact is that of an extremely violent incident that triggered an emergency situation. The motive remains a matter of investigation.
Why the 9/11 comparison is premature
The analogy with the September 11, 2001 attacks is particularly fraught with consequences.
9/11 was a coordinated terrorist operation involving multiple hijacked aircraft used as weapons. In the case of Flydubai flight FZ1073, nothing in the publicly available information at this hour establishes the existence of a comparable plan, organisation or demonstrated intent to use the aircraft as a weapon.
Some accounts do describe a situation that, from inside the cabin, could have felt like an imminent catastrophe. A passenger quoted by i24NEWS said she heard screams, saw blood and believed the plane was going to crash.
This distinction is essential: the fear experienced by passengers is a fact; the terrorist interpretation of that fear remains a hypothesis.
The cockpit: a new grey area in the investigation
The most intriguing element of this case may ultimately not be the dramatic code 7500, but what happened in the seconds before it was activated.
Who was actually in control of the aircraft?
Why did the plane abruptly lose altitude?
Who triggered the different emergency codes?
At what point did passengers enter the cockpit?
And above all: was one of the pilots genuinely trying to take control of the aircraft to divert it or crash it, or did the situation result from a confrontation whose consequences spiralled beyond the crew’s control?
Flight data may help reconstruct the timeline. The flight recorders and air traffic control communications will likely be decisive in distinguishing between a deliberate action, a struggle, or a momentary loss of control.
A crisis that extends far beyond the aircraft
The case takes on a particular dimension because the aircraft was carrying Israeli passengers and was heading to Tel Aviv.
The alert occurred in a region already under severe security tensions. The plane ultimately had to land in Tabuk, Saudi Arabia — a country with which Israel still has no official diplomatic relations.
Thus, an incident at several thousand metres altitude quickly turned into a diplomatic and military problem: fighter jet intervention, Israeli security consultations, handling of Israeli nationals on Saudi territory, and an investigation involving multiple authorities.
This may be the real lesson of the affair.
In modern aviation, a few seconds of uncertainty in a cockpit can trigger consequences that go far beyond the aircraft itself.
What we know — and what we don’t yet know
At this stage, several elements are established: the aircraft suffered a serious incident, both pilots were injured, the plane experienced a brutal descent, emergency codes were emitted, and the aircraft eventually landed in Tabuk with its passengers safe.
However, the motive of the protagonist or protagonists, the exact intention behind the confrontation, and the possible existence of a plan to turn the aircraft into a weapon are not publicly established.
It is precisely this zone of uncertainty that should be at the heart of the journalistic investigation.
For in such a sensitive case, the most important question may not be: “Was this a new 9/11?”
It is rather: “How could an airliner find itself in a situation where, for a few minutes, no one outside the cockpit knew who was actually in control?”
The answer now lies in the hands of investigators, flight data, the aircraft’s recorders and the testimonies gathered from crew and passengers.
