What began as a routine flight from Dubai to Tel Aviv turned into a full-blown international security emergency in a matter of minutes. A violent struggle inside the cockpit, a steep and sudden loss of altitude, emergency codes linked to hijackings, and finally an unscheduled landing in Saudi Arabia — this is the sequence that pushed Flydubai flight FZ1073 into the global spotlight. Yet beyond the early accusations of a terrorist attack, one question refuses to go away: what actually happened behind that cockpit door?
From routine departure to mid-air emergency
On Wednesday, the Flydubai Boeing 737 MAX 8 left Dubai bound for Tel Aviv with more than 150 passengers on board. At some point during the flight, the situation deteriorated abruptly.
Available tracking data reveals an extremely rapid descent: several thousand metres lost in a very short window. The aircraft then transmitted code 7700, signalling a general emergency, before squawking 7500 — the code used when a crew reports unlawful interference on board, including situations that could amount to a hijacking.
For authorities and for passengers on the ground, uncertainty was at its peak.
Israel launched a military response, scrambling fighter jets as a precaution. On board, several passengers described hearing screams and seeing blood. According to multiple witness accounts, a violent confrontation apparently erupted between the two pilots, with one of them wounded by a bladed weapon. Passengers are said to have intervened in the cockpit afterwards.
Both pilots were hospitalised after the landing at Tabuk, in Saudi Arabia. All passengers were reported safe and sound. Flydubai, for its part, confined itself to confirming that an "incident" had occurred during the flight, without publicly specifying its nature.
The detail that rewrites the story
This is where the real journalistic stakes lie.
In the first hours, several narratives circulated almost simultaneously: hijacking, a suicide attempt, a terrorist attack, a fight 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 above all, they are not yet established.
Two Israeli officials described the event as a possible "terrorist attack", while making clear that the investigation was ongoing. Contradictory versions have also emerged 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 itself remains a matter for the investigation.
Why the 9/11 comparison is premature
The analogy with the attacks of 11 September 2001 carries particularly heavy 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 public information available so far establishes the existence of a comparable plan, organisation or demonstrated intent to use the aircraft as a weapon.
Some witness accounts nonetheless describe a situation that, seen from the cabin, could have felt like an imminent catastrophe. One passenger said she heard screams, saw blood and believed the plane was going to crash.
That distinction matters: the fear experienced by passengers is a fact; the terrorist interpretation of that fear remains a hypothesis.
The cockpit as the investigation’s new grey area
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 flying the aircraft?
- Why did the plane suddenly lose altitude?
- Who triggered the various emergency codes?
- At what point did passengers enter the cockpit?
- And above all: was one of the pilots genuinely trying to seize 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 prove decisive in distinguishing a deliberate action, a struggle, or a momentary loss of control.
A crisis that goes far beyond the aircraft
The case takes on a particular dimension because the aircraft was carrying Israeli passengers and heading to Tel Aviv.
The alert occurred in a region already under heavy security tensions. The plane ultimately had to land at Tabuk, in Saudi Arabia — a country with which Israel still has no official diplomatic relations.
So an incident several thousand metres up quickly became a diplomatic and military problem: fighter jets scrambled, Israeli security consultations, Israeli nationals handled on Saudi territory, and an investigation involving multiple authorities.
Perhaps that is the real lesson here.
In modern aviation, a few seconds of uncertainty inside a cockpit can trigger consequences that reach far beyond the aircraft itself.
What we know — and what we don’t yet
At this stage, several elements are established: the aircraft suffered a serious incident, both pilots were injured, the plane underwent a steep descent, emergency codes were transmitted, and the aircraft eventually landed at Tabuk with its passengers safe.
However, the motive of those involved, the exact intention behind the confrontation, and the possible existence of a plan to turn the aircraft into a weapon have not been publicly established.
It is precisely this zone of uncertainty that should be at the heart of the journalistic investigation.
For in a case this sensitive, the most important question may not be: "Was this a new 9/11?"
It is rather: "How could an airliner end up in a situation where, for several minutes, nobody outside the cockpit knew who was really in control?"
The answer now lies with investigators, flight data, the aircraft’s recorders, and the testimonies gathered from the crew and passengers.
