Mariama Hamani
What really happened when flydubai flight FZ1073 lost control?
A Boeing 737 MAX 8 traveling from Dubai to Tel Aviv, a violent struggle inside the cockpit, a steep loss of altitude, emergency codes linked to hijacking, and an emergency landing in Saudi Arabia. Within minutes, flight FZ1073 became the center of an international security crisis. But behind early claims of a terrorist attack, one crucial question remains: what really unfolded inside the cockpit?
On that Wednesday, the flydubai jet had departed Dubai bound for Tel Aviv with more than 150 passengers on board. Mid-flight, the situation suddenly spiraled out of control.
The moment the flight turned into an emergency
Available tracking data reveals an extremely rapid descent: several thousand meters lost in a very short time. The aircraft then transmitted code 7700, signaling a general emergency, before squawking 7500 — the code used when a crew reports unlawful interference on board, including situations that could indicate a hijacking.
For authorities and people on the ground, uncertainty was at its peak.
Israel triggered a military response, scrambling fighter jets as a precaution. On board, several passengers described hearing screams and seeing blood. According to multiple accounts, a violent confrontation erupted between the two pilots, one of whom was wounded by a knife. Passengers reportedly then intervened in the cockpit.
Both pilots were hospitalized after landing in Tabuk, 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 everything
This is where the real journalistic stakes lie.
In the first hours, several narratives circulated almost simultaneously: hijacking, suicide attempt, terrorist attack, pilot struggle. Some Israeli media even raised the possibility that a pilot intended to crash the plane.
But these scenarios are not equivalent and, more importantly, none has been established.
Two Israeli officials described the event as a possible “terrorist attack,” while stressing that the investigation was ongoing. There were also contradictory versions regarding the circumstances and even the nationality of the pilots.
In other words: the established fact is an extremely violent incident that triggered an emergency. The motive itself remains a matter for the 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 public information available so far establishes the existence of a comparable plan, organization, or demonstrated intent to use the aircraft as a weapon.
Some accounts describe a situation that, from the cabin, could have felt like an imminent disaster. A passenger quoted by i24NEWS said she heard screams, saw blood, and believed the plane was going to crash.
That distinction is essential: the fear experienced by passengers is a fact; the terrorist interpretation of that fear remains a hypothesis.
The cockpit: the investigation’s new gray area
The most intriguing element of this case may ultimately not be the dramatic code 7500, but what happened seconds before it was activated.
- Who was actually controlling the aircraft?
- Why did the plane suddenly lose altitude?
- Who triggered the different emergency codes?
- When did passengers enter the cockpit?
- And above all: was one of the pilots genuinely trying to seize control of the aircraft to hijack it or crash it, or was the situation the result of a confrontation whose consequences spiraled 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 temporary loss of control.
A crisis that goes far beyond the aircraft
The case takes on a special dimension because the plane was carrying Israeli passengers and heading to Tel Aviv.
The alert occurred in a region already under heavy security tensions. The aircraft 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 meters altitude quickly became a diplomatic and military problem: fighter jet interception, Israeli security consultations, handling of Israeli nationals on Saudi soil, 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 far exceed the aircraft itself.
What we know — and what we still don’t
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 in Tabuk with all passengers safe.
However, the motive of the individual or individuals involved, 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 end up 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.
