Air Disasters - The Black Box Files

A pilot reads a descent clearance over Cambodia's Cardamom Mountains; Flight 241 vanishes two minutes later - did they make it in time? Last Transmission at 10:48: How Flight 241 Vanished into the Cardamoms In this episode, we follow the timeline of PMTair Flight 241’s final minutes and the operational quirks around it. We lay out the decisions, the equipment gaps, and the human moments that led the aircraft toward a jungle ridge - what happened between 10:48 and 10:50 remains unanswered. Date: June 25, 2007 Flight: PMTair Flight 241 Aircraft: Antonov An-24B, registration XU-U4A, manufactured 1969 Passengers: 22 (including 13 South Korean nationals and 3 Czech nationals) Crew experience: Captain 10,345 hours; First Officer 3,500 hours; Flight Engineer present - Departure from Siem Reap at 10:01 and normal climb; blip later drifted off planned route on Phnom Penh radar without controller query. - Crew asked Sihanoukville about destination weather at 10:36 while still 60 nm out on a short hop that should have been near completion. - Handed off to Sihanoukville at 10:42; contact described as normal before descent and loss from Phnom Penh radar at 10:46. - Last transmission: pilot read back a descent clearance at 10:48 over the Cardamom Mountains; two minutes later the aircraft was gone. - Investigators found wreckage with both flight recorders useless and a chain of small, individually explainable decisions converging on a 2,700 ft jungle ridge.

A damaged VOR beacon led a charter plane a mile off course toward a Minnesota runway - did they make it in time? The VOR beacon pulled planes a mile off course - did they make it? In this episode, we lay out the flight, the political stakes, and the pieces investigators had to assemble after a King Air A100 crashed two miles short of Eveleth’s runway. Who the passengers were, what the pilots’ records showed, and how a faulty VOR became central to the reconstruction drive the story - what crucial questions remain? Person: Paul Wellstone Date: October 25, 2002 Location: Eveleth, Minnesota Event: Beechcraft King Air A100 crash Status: No flight recorders aboard - The King Air A100 departed for a roughly one-hour charter flight carrying eight people, including Senator Paul Wellstone, en route to Eveleth on the morning of October 25, 2002. - The aircraft struck dense forest about two miles short of the Eveleth runway at 10:22 a.m.; there were no survivors and the plane had no black boxes. - Technicians tested the local VOR beacon the next morning and found it pulled aircraft approximately one mile off course, aiming toward the eventual impact site. - Investigators reconstructed the final minutes using radar returns, radio transcripts, the damaged VOR, and testimony from pilots who had flown with the two cockpit crew members. - The NTSB cited crew error, the FBI investigated possible sabotage, and documents from that probe were sealed for eight years, leaving unanswered threads about the flight’s last decisions.

A regional turboprop drifts off course toward a fogged Azores mountain; an alarm gives the crew seconds to avoid impact - did they make it in time? The drifting heading that erased their minutes and doomed the flight In this episode, we follow SATA Flight SP530M on a short inter-island run in the Azores that turns unexpected as instruments, weather, and routine decisions collide. We trace the chain of small navigational errors, crew calls, and shifting winds that set the plane toward a mountain and ask how those minutes vanished. Date: December 11, 1999 Flight: SP530M Aircraft: British Aerospace ATP, registration CS-TGM, named Graciosa Crew: Captain Arnaldo Mesquita (55), First Officer António Magalhães (46) Location: Azores, approaching Horta (São Jorge vicinity) - Departure from Ponta Delgada at 09:37 for a short hop to Horta then Flores with 33 passengers aboard. - Pilots requested a modified route threading between Pico and São Jorge and to intercept Horta VOR at 250°. - Solid low cloud and winds shifting from southwest to strong northerlies produced 30-45 knot gusts that steadily pushed the aircraft off track. - At 10:03 the crew reported passing waypoint LIMA-MIKE while the aircraft was already 14 nautical miles off course due to uncorrected dead reckoning. - Seventeen seconds elapsed between the cockpit alarm at 10:17:17 and the collision with terrain; no distress call was transmitted.

Landing gear extended as the Fokker 50 descended over Sharjah - sixteen seconds that may decide the passengers' fate. Did they make it in time? The landing gear extended and burned sixteen seconds of fuel In this episode, we follow the flight path, crew and decisions aboard Kish Air flight 7170 that set the stage for a catastrophic sixteen-second window over Sharjah. The episode traces the routine route, the known technical vulnerability, and the crew actions that led up to those critical seconds - how many choices had to align wrong for them to become lethal? Aircraft: Fokker 50, registration EP-LCA Date: February 10, 2004 Flight: 7170 Passengers and crew: 42 passengers, 6 crew; at least twelve nationalities Maintenance: anti-skid modification scheduled for May 2004; last Type A check December 24, 2003 - Landing gear extended while the aircraft was still four hundred feet in the air during approach to Sharjah. - A dormant flaw in the anti-skid control unit sent a ground signal to the solenoids immediately after gear extension. - The modification Fokker announced in 2003 had been scheduled but not installed on EP-LCA by February 2004. - Captain Ahmed Hosseini and First Officer Nemat Panahian exchanged control mid-cruise without a formal transfer or completed brief. - Every passenger was traveling to Kish Island to exit and re-enter the UAE to renew residency paperwork, making the flight mandatory for many.

A pilot trained to counter wake turbulence slammed the rudder pedals as an Airbus A300 climbed out of JFK-could crews stop a falling tail fin in time? The rudder pedals slammed; could crews stop a falling tail fin in time? In this episode, we present the sequence of events from takeoff to catastrophe on American Airlines Flight 587, showing the procedures, training, and forces at play as crews reacted in real time. What decisions and six seconds of training might explain how a routine departure became a deadly structural failure? Person: Captain Edward States Person: First Officer Sten Molin Date: November 12, 2001 Aircraft: Airbus A300-600R, registration N14053 Location: Departure from John F. Kennedy International Airport over Belle Harbor, Queens - At 09:15:36 the flight recorder logged an initial rolling jolt consistent with wake turbulence from a preceding Boeing 747. - First Officer Sten Molin was the pilot flying and had completed American Airlines’ Advanced Aircraft Maneuvering Program training for wake turbulence encounters. - A set of hard rudder pedal inputs applied forces of approximately 200 to 3,000 pounds to the fin's attachment bolts within seconds. - The A300’s vertical tail is attached at six bolted points, each engineered to hold roughly 100,000 pounds of force, and the fin weighed about 2,000 pounds. - The entire sequence from first pedal input to cockpit voice recorder silence lasted sixty-six seconds.

A plane named Mesrop Mashtots descends toward Sochi at night - can two fatigued pilots stop a routine approach from becoming catastrophe? Black Sea Landing Gear Down: Why Armavia A320 Dove at Night In this episode, we lay out the flight, the people, and the cockpit timeline that led to Armavia Flight 967 approaching Sochi. You’ll hear how decisions, fatigue, and automation interacted in the final minutes - and the question remains: did they make it in time? Flight: Armavia Flight 967 Date: May 3, 2006 (early hours local) Location: Off the coast of Sochi, Russia / en route Zvartnots Yerevan-Sochi Aircraft: Airbus A320, msn 547, named Mesrop Mashtots Passengers and crew: 113 on board (105 passengers, 8 crew) - Captain Grigor Grigoryan (40) and First Officer Arman Davtyan (29) were both qualified on the A320 with documented type ratings. - The aircraft had over 10,000 flight hours, was airworthy, and had served previous operators before joining Armavia in 2004. - In cruise Davtyan told the captain he was fatigued; the exchange was captured on the cockpit voice recorder. - During descent Grigoryan expressed frustration with the autopilot’s managed-descent mode and favored his own instincts. - At high speed the aircraft struck the sea with its landing gear down, and the cockpit voice recorder captured conflicting control inputs in the final ninety seconds.

A bent pylon fitting from a Tulsa shortcut cracks unseen as American Airlines Flight 191 climbs - did they make it in time? The bent pylon fitting failed six knots below stall - did they make it? In this episode, we present the documented sequence of maintenance decisions, damaged parts, and cockpit silence that preceded a catastrophic failure on May 25, 1979. What procedural shortcut and missed signals set up the crisis, and could anyone have known in time? Date: May 25, 1979 Event: Engine separation during takeoff at O'Hare International Airport Aircraft: McDonnell Douglas DC-10, registration N110AA Maintenance: Engine and pylon removed together in Tulsa, March 29-30, 1979 Margin: Aircraft was six knots below stall with no cockpit warnings - A $58 shortcut: Tulsa crew used a forklift to remove engine and pylon as one unit, cutting procedure steps from 79 to 27. - A McDonnell Douglas representative warned that the combined removal method carried risk, but the procedure was used anyway. - During the forklift operation a rear attachment fitting on the pylon was bent, damage invisible to naked-eye inspection. - The aircraft flew for eight weeks and dozens of flights while a fatigue crack grew through the damaged fitting with each pressurization cycle. - From engine separation to the aircraft rolling past the point of no return was 31 seconds, with no warning lights or alarms reaching the cockpit.

An engine and pylon tore free the instant Flight 191 rotated at O'Hare-did the maintenance shortcut and a cracked pylon flange doom everyone aboard? The pylon flange cracked during removal - did they reach safety? In this episode, we follow the thirty-one seconds after American Airlines Flight 191 lost an engine at rotation and the maintenance decisions that preceded it. The episode traces the chain from a combined engine-pylon removal shortcut in Tulsa to the unnoticed crack that grew over weeks - but did anyone foresee the consequence? Date: May 25, 1979 Flight: American Airlines Flight 191 Aircraft: McDonnell Douglas DC-10, N110AA Maintenance event: Engine and pylon removed together March 29-30, 1979 Fatalities: 273 - The airline used a combined engine-and-pylon removal method in Tulsa to save roughly 200 labor hours per aircraft. - The combined removal stressed the pylon aft bulkhead flange in ways the procedure wasn’t designed to handle. - During the Tulsa work, a forklift-supported engine-pylon assembly shifted and produced an undetected crack in the flange. - The cracked flange went unnoticed through inspections and the aircraft flew nearly two months afterward. - The left engine and pylon separated at the exact instant of rotation at O'Hare, 15:59, sending the engine onto runway 32R while the airframe continued airborne.

A routine MD-82 takes off from Detroit and, moments later, simply stops flying-could a single missed checklist item doom everyone on board? The Night an MD‑82 Stopped Flying: Surviving Flight 255's Silence In this episode, we follow the moments before and after Northwest Airlines Flight 255’s fatal departure and the puzzling aftermath investigators faced. The episode traces the flight crew’s experience, the airplane’s configuration, and the single routine step that may have mattered most - but did it leave enough warning to stop the crash? Person: Captain John R. Maus Person: First Officer David J. Dodds Date: August 16, 1987 Location: Detroit Metropolitan Airport, runway 3C Aircraft: McDonnell Douglas MD-82, registration N312RC - The MD-82 lifted off at 20:44 and was airborne for less than ninety seconds before control was lost. - Flight crew together had nearly 29,000 hours of experience and conversed calmly on the cockpit voice recorder in the final minutes. - Performance calculations were filed for runways 21L/21R, but the crew was cleared to depart from the shorter runway 3C that night. - The aircraft’s takeoff weight of 144,046 pounds was within limits only if the airplane was configured correctly for takeoff. - Investigators found the airplane rolled left immediately after liftoff and no obvious mechanical failure or lightning strike explained why it stopped flying.

A portable emergency locator transmitter sat in a Fairbanks hangar while the Alaskan wilderness swallowed a missing Cessna-did they make it in time? The transmitter that stayed in Fairbanks cost them thirty-nine days In this episode, we lay out the sequence of events surrounding the October 16, 1972 disappearance of a twin-engine Cessna with four men aboard and the puzzling absence of its emergency locator transmitter. The episode traces who was on the flight, what was known about the device, and why the search never recorded a confirmed emergency signal. Person: Thomas Hale Boggs Date: October 16, 1972 Location: Alaska Range / flight from Anchorage to Juneau Event: Disappearance of Cessna 310 with four aboard Item: Emergency locator transmitter confirmed left airport in another aircraft - The Cessna 310 departed Anchorage at 9:59 AM with pilot Don Jonz, Rep. Nick Begich, aide Russell Brown, and Hale Boggs aboard. - No distress call, mayday, or position report was ever transmitted after contact was lost over the Alaska Range. - The emergency locator transmitter that should have been on the plane remained in a Fairbanks hangar for thirty-nine days. - Search efforts became one of the largest in Alaskan history, involving the U.S. Coast Guard, Navy, Army, and Air Force across mountains and water. - Witness testimony noted an object in the pilot’s briefcase that “looked exactly like” the transmitter, raising questions about why no confirmed signal was received.