Flydubai flight FZ1073: how a cockpit struggle triggered an international security crisis
A Boeing 737 MAX 8 flying from Dubai to Tel Aviv with more than 150 passengers on board suddenly plunged into chaos. Within minutes, flight FZ1073 became the centre of an international security crisis. But behind the first accusations of a terrorist attack, one question remains: what actually happened inside the cockpit?
The minutes that changed everything
On Wednesday, the Flydubai aircraft had left Dubai bound for Tel Aviv when the situation deteriorated rapidly. Flight tracking data shows an extremely fast descent—several thousand metres lost in a very short time. The plane then transmitted code 7700, signalling a general emergency, before emitting code 7500, used when a crew reports an unlawful interference on board, including situations that could correspond to a hijacking.
For authorities and passengers 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 testimonies, a violent confrontation apparently pitted the two pilots against each other, with one of them wounded by a knife. Passengers then reportedly intervened in the cockpit.
Both pilots were hospitalised after landing at Tabuk, in Saudi Arabia. All passengers were declared safe. Flydubai limited itself to confirming that an “incident” had occurred during the flight, without publicly specifying its nature.
The detail that changes the whole story
This is where the real journalistic issue lies.
In the first 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 wanted to crash the plane.
But these scenarios are not equivalent and, crucially, they are not yet established.
Two Israeli officials described the event as a possible “terrorist attack”, while specifying that the investigation was ongoing. Contradictory versions also exist 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 for investigation.
Why the 9/11 comparison is premature
The analogy with the September 11, 2001 attacks is particularly heavy with consequences.
9/11 was a coordinated terrorist operation involving multiple hijacked planes used as weapons. In the case of Flydubai flight FZ1073, nothing in the publicly available information at this hour allows us to establish the existence of a comparable plan, an organisation, or a demonstrated intention to use the aircraft as a weapon.
However, some testimonies describe a situation that, from the cabin, could have felt like an imminent catastrophe. A passenger 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 spectacular code 7500, but what happened seconds before it was activated.
Who was actually in control of the aircraft?
Why did the plane suddenly lose altitude?
Who triggered the various emergency codes?
When did passengers enter the cockpit?
And above all: was one of the pilots really trying to take control of the aircraft to hijack 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 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 plane was carrying Israeli passengers and heading to Tel Aviv.
The alert occurred in a region already under strong security tensions. The aircraft eventually had to land at Tabuk, in 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 cause 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 plane suffered a serious incident, both pilots were injured, the aircraft experienced a brutal descent, emergency codes were emitted, and the plane ultimately landed at Tabuk with its passengers safe.
On the other hand, the motive of the protagonist(s), 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 it 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 testimonies gathered from the crew and passengers.