Why Praising Captain Smit Machchhar as a Lone Hero Ignores the Real Threat

Why Praising Captain Smit Machchhar as a Lone Hero Ignores the Real Threat

Hero worship is cheap. Aviation security is expensive.

Every time a high-stakes crisis breaks near an aircraft, the applause starts before the facts settle. When RSS chief Mohan Bhagwat praises Captain Smit Machchhar for his bravery in foiling a hijack attempt, pointing to the values that moved him to risk his life, the headlines write themselves. Brave pilot. Noble ethos. Inspiring sacrifice.

Nice story. Wrong diagnosis.

Treating a near-hijack as a morality play about inner values misses how aviation threats actually work, how flight decks are defended, and why celebrating individual heroics can blind an entire industry to systemic cracks.

I have spent years working around aviation safety audits, crisis response drills, and airline security protocols. I have seen operators blow serious money on flashy security theater while ignoring basic crew coordination, communication gaps, and airport perimeter blind spots. When a crisis gets defused, everyone wants to hand out a medal for courage. Nobody wants to audit the system that let the threat get close enough to require courage in the first place.

The Lazy Consensus Around Heroic Values

The standard media script is predictable. A threat appears. Someone steps up. A prominent leader names the "values" behind the act, and coverage treats those values as the main takeaway.

That script feels good. It also leaves readers with almost zero practical insight.

Courage under pressure matters. Nobody sane argues against bravery when lives are on the line. Yet attributing a foiled hijack attempt primarily to abstract values turns a complex operational event into a sermon. You cannot build a repeatable aviation safety standard out of inspiration alone. Inspiration does not lock a cockpit door. Inspiration does not screen a bag. Inspiration does not brief air traffic control when a radio call turns tense.

In aviation safety and threat response, experts like aviation security analysts and human-factors researchers—figures such as former FAA security specialists and crew resource management pioneers like Robert Helmreich—have spent decades hammering home a basic truth: reliable outcomes come from trained procedures, clear role boundaries, and disciplined decision-making under stress, not spontaneous heroics.

When public commentary stops at "values," it lets institutions off the hook. It frames safety as a matter of personal virtue rather than system design.

Asking the Wrong Question About Hijack Threats

People searching for news about Captain Smit Machchhar and a foiled hijack attempt usually ask two things first: What values drove him to act, and how did he pull it off?

Those are the wrong starting questions if you care about actual security.

The sharper question is: How did a hijack threat reach a point where a pilot had to put his life on the line?

Commercial aviation security is built on defense in depth—layered barriers designed so no single failure or single attacker compromises the flight. Those layers include:

  • Pre-flight intelligence and passenger vetting: Identifying bad actors before they ever reach a terminal.
  • Airport access and baggage screening: Catching contraband, weapons, or improvised threats at checkpoints and ramps.
  • Cabin and flight-deck protocols: Maintaining strict physical separation, cabin crew awareness, and unambiguous chain-of-command rules.
  • Ground and air coordination: Rapid communication among pilots, air traffic control, airport security, and tactical units.

When a crew member has to take extreme personal risk to stop a threat, it means earlier layers either were tested or strained. Celebrating the save without examining the stress points in the system is like cheering a fire extinguisher while ignoring faulty wiring in the building.

What Aviation Security Actually Demands

Let us get precise about terms so we do not confuse public drama with operational reality.

A hijack attempt involves unlawfully seizing or exercising control over an aircraft or attempting to force a change in its flight path, operations, or destination. Crew Resource Management (CRM) is the structured system of training and communication crews use to manage threat, error, and workload—especially when situations turn abnormal or hostile. Threat mitigation means reducing the likelihood or impact of a security breach before harm occurs.

In real-world operations, effective threat mitigation looks far less cinematic than a movie script. It looks like:

  1. Situational awareness: Spotting behavioral anomalies, unauthorized movement, or procedural deviations early.
  2. Disciplined communication: Using clear, calm, unambiguous language between flight deck, cabin crew, and ground authorities so nobody guesses what is happening.
  3. Rule adherence over improvisation: Following established security and flight-handling procedures rather than making things up on the fly unless a gap leaves no choice.
  4. Post-incident review: Conducting candid, non-punitive or thorough operational reviews to fix weaknesses before the next flight.

I have watched organizations get seduced by charismatic leadership speeches while neglecting basic drills. A speech makes people nod in a room. Drills build muscle memory when adrenaline spikes and oxygen or time feels thin.

Imagine a Different Scenario

Imagine a scenario where a crew member acts boldly during a hijack attempt, succeeds, and becomes a national symbol overnight. Every talk show debates moral character and civic spirit. Meanwhile, an airport screening protocol or ground-handover gap that enabled the approach goes unexamined because nobody wants to tarnish a celebratory moment. Six months later, another crew faces a similar pressure test under slightly different conditions.

That is the trap of hero-first coverage. Praise can become a sedative.

Addressing the Questions Everyone Is Asking

Did personal values play a role in his actions?

Almost certainly, yes. People who step toward danger instead of freezing or retreating usually draw on personal conviction, duty, or sense of responsibility. Pretending character does not exist would be just as dishonest as pretending character explains everything.

The flaw is treating personal values as a complete explanation. Many capable, principled professionals operate inside flawed systems every day. Values shape intent; training, doctrine, and system guardrails shape whether that intent translates into a safe outcome without catastrophic cost.

Why do political and social leaders weigh in on security incidents?

Leaders weigh in to shape meaning. When a figure like Mohan Bhagwat highlights the values behind a pilot's bravery, he is framing the event around cultural and moral identity.

That framing has a clear function in public discourse: it connects an individual act to a broader worldview. For readers, the trick is separating moral framing from operational analysis. One tells you what a speaker wants the public to admire. The other tells you how safe the skies actually are.

How can ordinary flyers and aviation observers judge real safety?

Skip the loudest headlines and look for boring operational indicators: regulatory audit findings, crew training standards, airport security upgrades, and transparent incident reporting. Real safety is rarely loud. It is methodical, unglamorous, and obsessed with edge cases.

The Downside of Taking This Contrarian Stance

Pushing back against celebratory coverage carries its own risks, and I will own them straight up.

First, a hard-nosed systemic critique can sound cold when someone risked their life. People understandably want to honor courage in the moment without turning every tribute into a policy seminar. If you lead with skepticism, you can come across as nitpicking an act of bravery.

Second, focusing too heavily on system flaws when details are still emerging can create premature blame. Early reports on high-tension incidents often shift as official investigations proceed. Over-interpreting incomplete facts is a fast way to look foolish.

Third, operational details around sensitive security incidents are often restricted or incomplete early on. Demanding total system answers on day one can push commentators into guesswork—the exact opposite of sound analysis.

A sharp contrarian does not diminish real courage or invent facts. You honor the person without turning off your analytical brain.

Actionable Steps That Actually Improve Safety

If you run an operation, manage risk, or simply want to read security news like an insider instead of a spectator, take these steps:

  • Audit the chain, not just the hero: Whenever a crisis is averted, map every checkpoint that preceded it—screening, access control, communication, and command decisions.
  • Invest in scenario training over slogans: Replace generic motivational talk with realistic stress drills that test decision-making under time pressure and ambiguity.
  • Separate tribute from root-cause review: Give credit where it is due, then run a cold-eyed operational review to find where the margin for error got too thin.
  • Read past the headline quote: Treat statements by prominent leaders as commentary on values, not proof of system performance.

Values may spark a decision in a split second, but systems carry the weight every single day. Build the system.

KF

Kenji Flores

Kenji Flores has built a reputation for clear, engaging writing that transforms complex subjects into stories readers can connect with and understand.