Kegworth: The Wrong Engine

On the evening of 8 January 1989, British Midland Flight 092 fell out of the sky onto the M1 motorway near Kegworth, Leicestershire. Forty-seven people died. The crew had shut down the wrong engine. In this episode, Capt. Amit Singh FRAeS examines the cognitive mechanism that made a skilled, experienced flight crew certain of the wrong answer — and stay certain until it was too late. Premature cognitive closure, satisficing, and the authority gradient that silenced everyone who knew the truth.

On February 23, 2026, a Redbird Airways Beechcraft King Air C-90A operating as an air ambulance from Ranchi to New Delhi crashed in Jharkhand, tragically claiming the lives of all seven people on board, including two pilots, medical personnel, and a patient. Minutes after takeoff, the aircraft encountered a severe thunderstorm and suffered a catastrophic in-flight structural breakup, scattering its engines, tail, and fuselage across a kilometer of forested terrain.In this episode, we dive into the official Aircraft Accident Investigation Bureau (AAIB) preliminary report and independent safety analyses to understand how this tragedy unfolded. We explore:The Weather Trap: How escalating cumulonimbus (CB) clouds and a violent gust front forced the crew into progressive, reactive heading changes—relying on visual avoidance rather than radar—which ultimately led them directly into the core of the storm.The Radar Mystery: Why the aircraft's 1987-vintage magnetron-based weather radar may have provided a false sense of security. We discuss the dangers of radar attenuation, where moderate rain hides severe weather behind it, and the limitations of manual tilt management.The Wreckage Evidence: What the widely scattered distribution of the heavy engines and the violently separated empennage tells us about the extreme aerodynamic overstress the aircraft endured before hitting the ground.Human Factors: The critical role of crew experience—the 25-year-old Captain was flying with a First Officer who had zero Pilot-in-Command hours on this aircraft type—and the dangerous impact of "mission-completion bias" that often pressures air ambulance crews to accept severe risks.Join us as we unpack the final 12 minutes of flight VT-AJV, the forensic wreckage analysis, and the urgent safety recommendations needed to protect future flights from the deadly forces of convective weather

In this episode, we dive into IndiGo’s recent decision to appoint Willie Walsh—former CEO of British Airways and IAG—as its new Chief Executive. While the market reacted with a euphoric 9% jump in share prices, veteran airline captain Amit Singh argues that this hiring pattern demands deeper scrutiny.Why does India export its finest managerial minds to lead global giants like Google, Microsoft, and the World Bank, yet consistently import Western executives to run its own airlines? We explore the deep-seated psychological mechanisms driving these boardroom decisions, including "colonial mentality," the need for "legitimacy signalling" to foreign investors, and "superstitious learning".Finally, we analyze what this means for IndiGo's future. While Walsh—famously nicknamed "Slasher Walsh" for his aggressive cost-cutting at Aer Lingus—might be the right leader to stabilize operations in the short term, is he equipped to handle IndiGo's long-haul ambitions, unique technological challenges, and the complex dynamics of the Indian workforce? Join us as we examine the unfinished business of decolonizing India's corporate imagination.

Have you ever wondered why a ground vehicle at LaGuardia Airport drove right past illuminated red Runway Entrance Lights (REL)? The system didn't fail, but the driver's perception was severely compromised.In this video, we dive into the fascinating world of aviation safety, human factors, and visual physiology to explain why the color red might actually be a safety hazard at night.Due to a physiological phenomenon known as the "Purkinje Shift," our eyes use different cells in the dark, causing our sensitivity to shift away from red and toward shorter wavelengths like blue and green. This makes red objects appear significantly darker or even disappear entirely at night. At an airport, this night vision shift combines with a "sea of blue" from taxiway edge lights and wet reflective surfaces, physiologically disadvantaging the most critical "STOP" signals.This visibility issue isn't limited to aviation. It is the exact same scientific reason why many fire departments and the FAA have transitioned from traditional red fire engines to highly visible lime-yellow emergency vehicles, which have been proven to reduce visibility-related accidents.We also explore the cognitive traps that lead to runway incursions:Foveal Tunneling: How the intense task load of navigating an airport narrows a driver's attention, causing them to miss low-profile, in-pavement peripheral lights.Auditory Masking: How loud vehicle engines and sirens mask critical ATC communications.The Temporal Reinforcement Trap: How predictive runway light systems extinguish shortly after a vehicle crosses, creating a false feedback loop that validates the driver's error.Finally, we discuss how the actual shape and color of signs can save lives. While standard runway holding signs are red with sharp edges, experts argue that changing them to yellow with rounded edges would allow the human brain to process the warnings significantly faster.Watch to understand how the mismatch between system design and human perception causes runway incursions, and what actionable mitigations can prevent the next major accident!#AviationSafety #HumanFactors #RunwayIncursion #PurkinjeShift #Aviation #LaGuardia

In this episode, we expose a serious safety violation at Air India involving the operation of an Airbus A320 (VT-TQN) without a valid Airworthiness Review Certificate (ARC). Based on leaked internal investigation reports, we break down how an aircraft flew eight revenue flights carrying passengers while illegally undocumented.In this episode:• The Incident: How VT-TQN operated a test flight and 8 passenger flights in November 2025 despite its safety certificate expiring days earlier.• The Failure: Why the Engineering team incorrectly informed Flight Ops that the "ARC is valid" and how pilots failed to perform mandatory document checks.• The Root Cause: A "Swiss Cheese" failure of communication between the ARC Cell, Continuing Airworthiness Manager (CAM), and Engineering Planning.• The Fallout: The internal scramble to fix "systemic failures" and the disciplinary actions recommended against staff.#AirIndia #AviationSafety #Whistleblower #AviationNews #AirbusA320

Why do preliminary aviation reports sometimes distinguish between milestones occurring "as per EAFR" and specific statistics like "maximum recorded airspeed"? In this episode, we analyze the technical nuance behind these terms, using the example of a 180 KIAS peak to illustrate the difference between procedural events (like V1 or Vr) and peak values captured in a data trace. We also dive into the architecture of the 787's Enhanced Airborne Flight Recorder (EAFR) and the Recorder Independent Power Supply (RIPS), explaining how a recorder can continue operating even if specific inputs—like air data from the ADR—stop updating or become invalid

In this episode, we deconstruct the preliminary acoustic evidence surrounding the infamous cockpit exchange: “Why did you cut off?” — “I didn’t do it.”.While media reports suggest the CVR audio needed to be "cleaned up" to identify these voices, this necessity for heavy post-processing reveals a critical forensic clue. It suggests investigators were forced to rely on the Cockpit Area Microphone (CAM) rather than the typically clear individual headset channels.Key Analysis Points:• The Acoustic Deduction: Heavy background noise and the need for "cleanup" points to a recording dominated by the Area Mic (CAM).• The Electrical Implication: A CAM-only recording signature is consistent with the aircraft operating on backup power or in an abnormal electrical configuration, such as the deployment of the Ram Air Turbine (RAT). Technical schematics of the Recorder Independent Power Supply (RIPS) confirm that in the event of usual power failure, the RIPS sends battery power specifically to the Flight Deck Area Mic and the Forward Flight Recorder.• The Timeline Conflict: The simplistic timeline suggests a Flight Control System (FCS) cutoff led to power loss and subsequent RAT deployment. However, if the audio recording of the voices already exhibits the "heavy noise" signature of backup power, the aircraft may have been in the RAT/backup configuration before the verbal exchange occurred.This evidence challenges the linear sequence of events and raises physics-based questions about the latency between control inputs and hydraulic pressure changes.Sources:• Acoustic Evidence and the RAT Deployment Timeline• Acoustic_Forensics_Timeline_Revision• Flight Recorder System Schematics (RIPS/EAFR)

On July 9, 2024, a LATAM Boeing 777-300ER dragged its tail along the runway at Milan Malpensa for over 700 meters. How does a modern cockpit with an Instructor Captain and a Relief Captain fail to notice that their takeoff speeds are dangerously low?In this episode, we break down the preliminary report and apply a "cognitive view" to understand how a "100-tonne class" error slipped through the safety net.Key Topics Covered:✈️ The Incident: Reviewing the takeoff of flight LA8073. The aircraft rotated at 149 knots, despite needing speeds calculated for a 328-tonne takeoff weight. The result was a 6cm deep furrow in the runway and a fuel-dumping emergency return.Math The "Plausibility" Math: We look at the simple math that suggests the crew likely used performance data for a weight around 223 tonnes—roughly 100 tonnes lighter than their actual weight.🧠 The Cognitive Traps: Why do good crews make gross errors?• Echo-Checking: Replacing independent verification with "Do we match?".• Learned Carelessness: How daily repetition reduces mental effort.• The "Commitment Tunnel": Why pilots lock up and try to "make it fly" even when the data feels wrong.🛡️ The Solution - "Do They Belong?": Moving beyond checking for matching numbers to checking for sense. We discuss the "2-breath gross-error trap" and how to empower the jump-seat pilot to speak up.Sources: Based on "Cognitive Traps and Performance Errors in the Milan Tail Strike" by Amit Singh (Safety Matters Foundation).

In this podcast, we analyse the critical gap between written Standard Operating Procedures (SOP) and the tactile reality of cockpit practice, using the AI132 fuel control switch incident as a key case study.1. The "Mess Hall" Problem We begin with an analogy from A Few Good Men: just because the procedure to get to the mess hall isn’t in the book, it doesn’t mean the Marines don’t eat. Similarly, in aviation, you can do the job safely every day even when the manual doesn’t describe every micro-step. SOP provides the documented minimum for compliance, but "practice" is the unwritten discipline—the tactile method of moving a switch or the habit of verifying detents—that actually prevents accidents,.2. The AI132 Case Study: A Safety-Critical Mismatch In the AI132 narrative, a mismatch emerged between the pilot’s report of "slight vertical pressure" causing a switch to unlatch, and a technical explanation focusing on incorrect force vectors,. We discuss why resolving this mismatch is vital to avoid "premature closure"—a human factors trap where the system decides what happened (pilot error) before proving the mechanism.3. The Questions We Must Ask If the issue was simply "incorrect handling," why did it occur only on the left switch and not the right?. We explore potential engineering factors that a robust investigation must consider:• Hardware asymmetry: Differences in micro-wear or detent spring fatigue between left and right switches,.• Ergonomics: Why humans are unreliable sensors of force vectors.• Repeatability: Why the failure wasn't seen on every start.4. The Real Lesson for Pilots and Safety Managers Issuing a "strict SOP compliance" order is an immediate barrier, but the mature safety response is to reinforce control-handling discipline—like the "hands off unless required" rule and deliberate latch verification,.Key Takeaway: SOP is necessary but never sufficient for every tactile nuance. True safety culture improves when we ask, "What made this easy to do?" rather than just "Who did what?".Chapters: 0:00 - The "Mess Hall" Problem: SOP vs. Practice 1:45 - What is "Practice" in the Cockpit? 3:10 - The AI132 Mismatch: Vertical Pressure vs. Force Vector 5:30 - The Unanswered Questions: Why Left Only? 7:20 - Avoiding Premature Closure in Investigations 9:00 - Cockpit Takeaways: Hands Off & Verify#AviationSafety #AI132 #HumanFactors #PilotTraining #AviationMaintenance #SafetyCulture #SOP

On September 30, 2001, a King Air C-90 carrying former Aviation Minister from the sky, killing all eight onboard. The official report blamed heavy rains and pilot error—a "convenient story" for a high-profile disaster. But 25 years later, a new forensic analysis suggests the investigation was filled with comforting lies rather than hard truths.In this episode, we explore the dangerous intersection of VIP pressure and aviation safety, asking the questions the original investigators ignored:• The Weather Deception: Why did the report claim "heavy thunderstorms" when satellite archives show zero rain and clear skies at cruising altitude?• The Impossible Wind: Did investigators falsify wind direction data to explain away burn marks on the fuselage?• Silent Evidence: The pilot’s trachea contained soot—proof he was breathing during a fire—yet the report ruled out an in-flight blaze.Join us as we uncover how "vested interests" can shape the narrative when the influential can't defend themselves.