“I Couldn’t Let Everybody Else Die”: The Flydubai Captain Who Exposed Aviation’s Cockpit Security Dilemma

The Flydubai cockpit attack raises a difficult question for airlines and aircraft manufacturers: can aviation protect the flight deck from external threats while still creating a safe way to respond when danger comes from inside?

Global (Tourism Reporter — Publisher’s Perspective) — On 30 September, Flydubai Flight FZ1073 departed Dubai for Tel Aviv carrying more than 170 people. While flying over Saudi Arabia, the Boeing 737 MAX 8 suddenly entered a steep descent, losing nearly 14,000 feet in less than 30 seconds. The aircraft transmitted the emergency code 7700 and subsequently squawked 7500, the international transponder code associated with unlawful interference.

What happened inside the cockpit remains under investigation. Israeli Prime Minister Benjamin Netanyahu said the co-pilot had stabbed Captain Smit Machchhar and was attempting to bring down the aircraft. Passengers described shouting from the front of the cabin, a sudden descent and scenes of panic before, remarkably, the cockpit door opened from the inside.

The man who opened it was Captain Smit Machchhar, an Indian national who had been seriously wounded in the attack. Speaking from his hospital bed during a video call with Indian Prime Minister Narendra Modi, Machchhar recalled the moment he realised the aircraft was plunging.

“This is the last push, Smit, do it. The door is right there,” he recalled telling himself.

He then made that final effort to reach and open the cockpit door.

“I was trying to save my own life, but I knew I could not let all those people die,” he said.

His action allowed passengers and crew to enter the flight deck and help subdue the attacker. Two other pilots who were travelling on the aircraft subsequently helped take control, and the flight was diverted safely to Tabuk, Saudi Arabia. All those on board survived.

Captain Machchhar’s actions have rightly been described as heroic. Netanyahu praised him for helping prevent what he called a catastrophic mid-air disaster, while Modi praised his courage and presence of mind.

That part of the story deserves to be told clearly.

But there is another question worth asking.

What happens when the person the cockpit door was designed to keep out is not the threat—and the danger is already inside?

That is the uncomfortable question Flydubai Flight FZ1073 leaves behind.

The issue is not to second-guess Captain Machchhar’s actions, nor to prejudge the motive or circumstances of the co-pilot while investigations are continuing. It is a more structural question about aviation security: how does an aircraft protect the integrity of a locked flight deck while still having a safe and reliable way to respond when the threat originates inside it?

A Door Built for the Threat From Outside

Reinforced cockpit doors became a defining feature of post-11 September aviation security for an entirely understandable reason: hijackers had breached flight decks from the cabin, and the industry’s response was to make unauthorised access extraordinarily difficult. The modern cockpit door is a hardened barrier designed to resist forced entry, with access controlled by the flight crew and emergency-entry procedures intended to provide a carefully controlled means of access when necessary.

On aircraft such as the Boeing 737, flight-deck access systems can include a keypad-based procedure through which authorised cabin crew can request entry. Depending on the aircraft configuration and operator’s procedures, the request can be accepted, rejected or, in certain emergency circumstances, progress through a timed sequence if there is no response from the flight deck. The principle is deliberate: make unauthorised entry extremely difficult while retaining a controlled emergency route into the cockpit.

It is an elegant security concept for the threat it was primarily designed to address: a hijacker, terrorist or other intruder attempting to force their way into the flight deck from the cabin.

But what happens when the threat is already inside?

That is where the Flydubai incident becomes particularly difficult.

If the preliminary account is ultimately confirmed, the danger aboard FZ1073 did not originate in the cabin. It originated inside the protected space itself. The person who needed help was also inside the cockpit, while the person allegedly creating the danger was already there.

And that creates a very different security problem.

The cockpit door is designed to prevent the wrong person from getting in. But in an incident like this, the question becomes whether the right people can get in quickly enough when the person inside the cockpit is no longer able—or willing—to let them in.

Captain Smit Machchhar appears to have answered that question himself, while wounded and under attack, by finding the strength to open the door.

That was an extraordinary act of courage.

But it also leaves aviation with a question worth examining:

Should a life-threatening emergency inside the cockpit depend on the person being attacked having enough strength to open the door?

That, I believe, is where the real cockpit-security dilemma begins.

Aviation Has Seen This Problem Before, in a Different Shape

This is not the first time a hardened cockpit door has produced an unintended failure mode. In March 2015, Germanwings Flight 9525 crashed into the French Alps, killing all 150 people aboard, after investigators concluded that the co-pilot had deliberately locked the captain out of the cockpit and continued the aircraft’s descent into the mountainside. The tragedy exposed, in a different form, the vulnerability created when one pilot inside a secured flight deck could prevent another authorised pilot from regaining access.

Aviation’s response to Germanwings was largely procedural rather than mechanical. Many airlines introduced or reinforced rules requiring two authorised people to be present on the flight deck at all times, so that no pilot would routinely be left alone behind a locked cockpit door. The measure was designed to address the specific circumstances exposed by Germanwings.

But it would not, on its own, address the scenario now raised by FZ1073, where the second person in the cockpit was reportedly the threat itself.

Aviation has therefore encountered at least two very different failure modes involving the same basic security architecture.

In one, the captain was locked out by a pilot inside the cockpit who, according to investigators, had deliberately taken control of the aircraft.

In the other, if the preliminary account of FZ1073 is ultimately confirmed, the captain was trapped inside the cockpit with a co-pilot who had allegedly attacked him.

The circumstances are different. The risks are different. And the appropriate safeguards may be different too.

But both incidents point towards the same uncomfortable question:

What happens when the security system designed to keep an unauthorised person out also prevents authorised people from reaching someone who urgently needs help inside?

That is the dilemma aviation may now need to examine more closely.

The lesson may not be that the cockpit door is wrong. Quite the opposite: the security principle behind a hardened flight deck remains fundamental.

The harder question is whether that principle needs another layer—one designed not for intrusion from outside, but for the extremely rare circumstance in which the emergency originates inside the protected space itself.

The Question Worth Asking Is Not “Unlocked or Locked”

It would be easy, and wrong, to frame the response to FZ1073 as a binary choice: should cockpits be harder to enter, or easier?

That framing risks solving one failure mode by reopening another.

A cockpit door designed to allow rapid access in every emergency could also weaken the very security principle that led to reinforced flight-deck doors after 11 September 2001. The industry does not need a simpler door. It needs a better answer to a more specific question:

Can aviation create a secure third pathway—something between “locked” and “open”—for the rare but potentially catastrophic situation in which the danger originates inside the flight deck and the pilot who would normally control access is either incapacitated, under attack or the source of the threat?

That is a much harder engineering and procedural problem than simply choosing between a stronger door and an easier one.

And it may not have a single, universal solution.

Perhaps the answer lies in a combination of measures: better ways of detecting when a flight-deck emergency is developing; stronger coordination between the cockpit and cabin crew; additional safeguards for situations in which a pilot becomes incapacitated; or an independently governed emergency-access mechanism that does not rely entirely on the cooperation of the person inside the cockpit.

But there is an obvious complication.

Any mechanism capable of overriding the cockpit-security system must itself be protected against misuse.

That is the central engineering challenge. Aviation cannot create an emergency pathway that becomes a new vulnerability for the very threats the cockpit door was designed to prevent.

Which means any potential solution would have to be exceptionally carefully designed, tested and regulated.

The important point is not that aviation should immediately adopt one particular technology or mechanism. It is that the FZ1073 incident raises a legitimate question about whether the industry’s existing security architecture has sufficiently considered this particular failure mode.

That question deserves examination by regulators, aircraft manufacturers, airlines, pilots, cabin crew and aviation-security specialists.

Because the objective should not be to make the cockpit easier to enter.

It should be to make the aircraft more resilient when the person who needs help is already inside the cockpit.

Resisting the “Another 9/11” Framing

Some of the language surrounding FZ1073 has reached for the biggest possible comparison. Indian Prime Minister Narendra Modi described Captain Machchhar’s actions as helping prevent what he called “another 9/11-like attack”, while Israeli officials have used similarly grave framing.

The impulse is understandable. The stakes were unquestionably serious: the aircraft entered a steep descent, and the events inside the cockpit created the potential for a catastrophic outcome.

But building the story primarily around “another 9/11” risks collapsing a genuinely different security problem into a familiar one—and, in doing so, encouraging solutions designed for the wrong threat.

The 9/11 hijackings involved an external breach of the flight deck. The FZ1073 incident, according to the preliminary accounts, involved a threat originating inside the cockpit.

Those are fundamentally different security scenarios.

And that distinction matters.

The post-9/11 cockpit-security model was built around a straightforward principle: keep unauthorised people out of the flight deck.

Germanwings later exposed another vulnerability: what happens when an authorised person inside the flight deck becomes the threat.

FZ1073 appears to raise yet another variation: what happens when an authorised person inside the flight deck becomes the victim?

Treating all three scenarios as essentially the same problem risks overlooking the specific question this latest incident presents.

The more precise framing is this:

One reinforced door has spent 25 years helping protect aircraft from threats outside the cockpit. FZ1073 raises the question of what happens when the threat is already inside.

Those are not the same emergency.

And they may not require the same security response.

The goal, therefore, should not be to weaken the cockpit door or to undermine the security architecture created after 9/11. It should be to ask whether that architecture can be complemented by another layer—one capable of responding to the rare circumstance in which the person who needs help is already behind the locked door.

That is the harder question. And perhaps it is the one aviation should now be asking.

What Aviation Has Actually Spent Twenty-Five Years Building, and What Comes Next

Since 2001, the industry has spent a quarter of a century making the cockpit harder to enter. That was a logical response to the threat exposed by the 9/11 attacks, and reinforced flight-deck security has remained a fundamental part of modern aviation security.

FZ1073 does not undermine that achievement. It raises a different question—one that the post-9/11 architecture was never primarily designed to answer:

What happens when the person inside the hardened door can no longer be trusted to protect the people outside it, while the person who needs protecting is also, improbably, on the wrong side of the same lock?

Captain Machchhar’s final push to reach that door, seriously wounded and under attack, with the aircraft in a steep descent, should be remembered as an extraordinary act of individual courage.

But it should not become the industry’s answer to the problem.

A safety architecture that ultimately depends on a severely wounded pilot finding the strength to reach the door is not the kind of redundancy aviation normally strives for. It is a story about one person’s determination in an extraordinary emergency—and, fortunately, one that ended with everyone aboard surviving.

The next pilot in a similar situation might be unconscious before reaching the door.

The crew outside might know that something has gone catastrophically wrong on the flight deck and still have no safe way to intervene.

That is the vulnerability worth examining.

Aviation cannot engineer away every threat that a determined or compromised individual might pose from inside a cockpit. Nor should one extraordinary incident automatically dictate a new technology or procedure.

But aviation can examine the scenarios it has now been confronted with and ask whether its security architecture is sufficiently resilient when the threat comes from within the protected space.

That is where the conversation should go next.

Not: Should the cockpit door be locked or unlocked?

Not: Was the existing system a failure?

But something more useful:

Can aviation design a system in which a pilot’s survival—and the survival of everyone behind that cockpit door—does not depend entirely on the pilot being physically capable of opening it?

The question FZ1073 leaves behind is not whether Captain Machchhar was brave.

It is whether aviation should ever have to depend on such extraordinary courage again.