エピソード

  • The chart that showed forty‑five feet forced the plane to hit the wires

    The chart that showed forty‑five feet forced the plane to hit the wires
    2026/09/01
    A decorated KLM captain lines up a visual approach to Prestwick with charts showing 45 feet obstruction - did he make it in time?

    The chart that showed forty‑five feet forced the plane to hit the wires

    In this episode, we follow the Nijmegen's night approach to Prestwick and the chain of choices, weather reports, and flawed wartime charts that framed the crew's decisions. It lays out the margins they had - delays, wind estimates, runway options - and asks whether those margins were enough.

    Person: Koene Dirk Parmentier
    Event: KLM flight PH‑TEN (Constellation Nijmegen) approach to Prestwick
    Date: October 20, 1948
    Location: Five miles northeast of Prestwick
    Cargo: Diamonds and watches valued at £31,000

    - Captain Parmentier, KLM’s most decorated pilot, had written the airline’s low‑visibility landing rules and knew runway two‑six was off‑limits in low cloud.
    - The Nijmegen departed Schiphol 1 hour 11 minutes late after extra cargo for Iceland was added, reducing operational margins.
    - Meteorological forecast predicted probable clearing, but actual cloud base that night sat between 300 and 600 feet, low enough to obscure a visual approach.
    - Runway 32 offered ground‑controlled radar approach but Parmentier judged crosswinds near KLM limits, so he elected runway 26 with no radar guidance.
    - The cockpit chart used wartime American military data and showed the highest terrain in the approach corridor as 250 feet, with a critical spot marked 45 feet.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    14 分
  • The radar scale maxed out - and they had five minutes to live

    The radar scale maxed out - and they had five minutes to live
    2026/08/31
    A NOAA Hurricane Hunter plane dives toward the ocean into Hurricane Hugo with the radar scale maxed out and only five minutes to read what’s inside.

    The radar scale maxed out - and they had five minutes to live

    In this episode, we follow a NOAA WP-3D Orion crew and scientists as they prepare to descend into Hurricane Hugo’s eyewall with critical radar data arriving just minutes before impact. The episode traces the decisions, equipment failures, and roles aboard Kermit that set the team on a collision course and asks whether those five minutes were enough to keep them safe.

    Date: September 15, 1989
    Aircraft: Lockheed WP-3D Orion (NOAA 42, Kermit), registration N42RF
    Event: Hurricane reconnaissance flight into Hurricane Hugo (Category Three assessment)
    People aboard: 16 (mix of flight crew, systems engineers, radar and Doppler scientists, dropsonde scientist, air-sea scientist, observer, reporter)
    Critical issue: Belly-mounted radar failed, repaired en route, leaving a five-minute window to interpret maxed-out radar returns

    - Flight Director Jeff Masters had only five minutes to analyze the radar data before descent into the eyewall began.
    - The belly radar, essential for near-surface structure, failed after takeoff and was repaired twenty minutes later, consuming the preflight analysis window.
    - Mission plan called for eyewall entry at 1,500 feet to study the near-surface environment under the Hurricane Energetics experiment.
    - Radar Technician Neil Rain and scientists Peter Dodge and Bob Burpee were responsible for interpreting radar and Doppler returns under extreme time pressure.
    - The radar scale was hitting its upper measurement limit at multiple points around the eyewall, a phenomenon not previously documented in a hurricane.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    16 分
  • The empty flight‑recorder box that erased whether they made it in time

    The empty flight‑recorder box that erased whether they made it in time
    2026/08/31
    A United flight over Lake Michigan suddenly dives and the flight recorder is missing-did the crew realize what was happening?

    The empty flight‑recorder box that erased whether they made it in time

    In this episode we lay out the sequence of events on United Airlines Flight 389 from departure to impact and the puzzling gaps that investigators faced. We follow the crew, the aircraft, and the missing pieces that leave one central question: what did they think was happening in those final seconds?

    Date: August 16, 1965
    Flight: United Airlines Flight 389
    Aircraft: Boeing 727, registration N7036U
    Crew: Captain Melville W. Towle; First Officer Roger M. Whitezell; Second Officer Maurice L. Femmer
    Location: Lake Michigan, near North Avenue Beach

    - At 21:21 the sky lit orange, a roar followed three seconds later, and the aircraft hit the lake at roughly 200 knots.
    - The Boeing 727 had its first flight on May 18, 1965, was delivered June 3, 1965, and had only 138 cycles with no reported mechanical faults.
    - Captain Towle had 17,142 total hours and had passed a proficiency check in July; the two co‑pilots were current on the 727 with hundreds of hours on type.
    - Chicago Center cleared the flight to 6,000 feet; the crew acknowledged with “Roger” while the aircraft was estimated between 1,000 and 2,500 feet.
    - The flight data recorder casing was recovered intact from about 250 feet of water, but the magnetic tape that would show the final instrument readings was missing.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    16 分
  • The blizzard that grounded search helicopters-and cost four days to reach them

    The blizzard that grounded search helicopters-and cost four days to reach them
    2026/08/31
    A Boeing 737 vanishes in a February blizzard east of Kabul as helicopters turn back-did rescuers reach the wreckage in time?

    The blizzard that grounded search helicopters-and cost four days to reach them

    In this episode, we narrate the disappearance of Kam Air Flight 904 and the immediate search efforts hampered by the worst snowstorm in five years. We describe the flight, the conditions that stopped helicopters, and the delay that left families waiting-what decisions and barriers defined those four days?

    Event: Kam Air Flight 904 crash on February 3, 2005
    Aircraft: Boeing 737-200, registration EX-037
    Passengers and crew: 105 onboard (97 passengers, 8 crew)
    Operator arrangement: Aircraft operated by Phoenix Aviation, contracted by Kam Air
    Location: Mountains east of Kabul, Afghanistan

    - Military helicopters were dispatched to search shortly after contact was lost but turned back due to the blizzard.
    - Ground search teams and Afghan National Army commandos were organized but could not penetrate the terrain in whiteout conditions.
    - The wreckage lay on a ridge at about eleven thousand feet, amid two roofless stone observation posts from the 1980s.
    - The flight data recorder contained no valid data and the cockpit voice recorder was never found, leaving cockpit decisions unknown.
    - Four days passed before investigators and rescue teams could reach the crash site because the storm prevented access.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    14 分
  • The three‑handed altimeter misread cost them ten thousand feet and nine lives

    The three‑handed altimeter misread cost them ten thousand feet and nine lives
    2026/08/31
    A test flight crew trusts a three‑handed altimeter as dense fog hides the ground - did their instrument misread cost them ten thousand feet?

    The three‑handed altimeter misread cost them ten thousand feet and nine lives

    In this episode, we follow the December 24, 1958 airworthiness test of a Bristol Britannia that descended into Dorset under dense fog. The episode traces the flight, the crew, the instrument at the center of the inquiry, and the unanswered procedural questions that kept investigators focused on systems rather than people.

    Date: December 24, 1958
    Aircraft: Bristol Britannia G‑AOVD
    Event: Airworthiness test flight
    Location: Burley Road, Dorset
    Weather: Dense fog

    - Departure from London Heathrow at 10:10 for a routine airworthiness test to Hurn Airport with five crew and seven non‑revenue passengers aboard
    - The three‑handed altimeter displayed altitude via three differently sized hands that required mental assembly and were known to be misread in prior accidents
    - As the Britannia descended, dense fog removed visual cues that would have allowed a last‑second correction by the crew
    - Ground impact left a path of sheared telephone poles and dragged cables mapping the aircraft’s final seconds
    - Investigators concentrated on instruments and procedures, noting the altimeter design had already contributed to earlier crashes

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    14 分
  • The failed right-engine turbine blades bled thrust and left them two miles short

    The failed right-engine turbine blades bled thrust and left them two miles short
    2026/08/31
    A right-engine turbine bled thrust after takeoff from Honolulu, leaving two pilots racing back to the runway. Did they make it in time?

    The failed right-engine turbine blades bled thrust and left them two miles short

    In this episode, we follow the nine minutes between takeoff and impact as two experienced pilots confront a sudden loss of right-engine power on a forty‑five‑year‑old Boeing 737‑200 over Māmala Bay. The episode lays out the aircraft, the crew, the early diagnostics and the cockpit decisions that defined their last chance to reach the runway.

    Date: July 2, 2021
    Aircraft: Boeing 737‑200 (N810TA)
    Event: Controlled flight into water two miles short of runway
    Crew: Captain Henry Okai (15,781 hrs), First Officer Gregory Ryan (5,272 hrs)
    Engine: Pratt & Whitney JT8D‑9A right‑engine turbine blade failures

    - Nine seconds after rotation the cockpit recorder captured a thud and immediate vibrations as the right engine began losing thrust.
    - The right high‑pressure turbine blades showed oxidation, corrosion and stress fractures that caused progressive blade failure, not a sudden explosion.
    - Both pilots correctly identified degraded right‑engine performance, then reduced power on both engines and leveled off at about 2,100 feet to assess.
    - The flight was an eleven‑minute overnight cargo hop from Honolulu to Maui on an aging 1976 freighter operated by Transair/Rhoades Aviation.
    - Maintenance records included two prior FAA Service Difficulty reports for the left engine in 2018 and 2019, entries that appear not to have been communicated to the crew before departure.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    15 分
  • The dark landing-gear light that hid how fast fuel leaked

    The dark landing-gear light that hid how fast fuel leaked
    2026/08/31
    A dark landing-gear light strands a fully fueled DC‑8 over Portland as crew debate fuel levels - did they make it back before the tanks ran dry?

    The dark landing-gear light that hid how fast fuel leaked

    In this episode, we follow United Airlines Flight 173’s final hour: a landing-gear indicator that never lit, a crew running checklists, and a holding pattern that turned routine into crisis. The episode lays out what happened in the cockpit and asks whether the crew’s decisions and communications saved the flight in time.

    Date: December 28, 1978
    Flight: United Airlines Flight 173
    Aircraft: McDonnell Douglas DC-8-61, N8082U
    Fuel on board: 46,700 pounds
    Location: Southeast Portland holding pattern, 6 miles short of runway

    - Captain Malburn “Buddy” McBroom: 52 years old, 27 years at United, ~27,600 flight hours, ~5,500 on DC-8.
    - First Officer Roderick Beebe: 35 years old, 13 years at United, ~5,200 flight hours.
    - Flight Engineer Forrest Mendenhall monitored gauges as fuel numbers moved and noted ambiguous fuel-quantity readings.
    - A corroded cylinder caused the right main gear to free-fall and damage a microswitch, leaving the right main gear indicator light dark.
    - The crew held in a slow circle at 5,000 feet with gear and flaps down, increasing fuel burn while communications about fuel remained tentative rather than direct.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    20 分
  • The one missed seat that cost them one mile from the runway

    The one missed seat that cost them one mile from the runway
    2026/08/31
    A captain with far too few jet hours pilots a Boeing 737 toward Cuenca in fog, one mile short of Mariscal Lamar - did they make it in time?

    The one missed seat that cost them one mile from the runway

    In this episode, we follow the flight, the crew, and the institutional decisions that shaped a routine fifty-minute trip to Cuenca. The episode traces training requirements, cultural rules at TAME, and the hour-by-hour choices that moved the jet toward the mountain - could one missed seat change everything?

    Date: July 11, 1983
    Aircraft: Boeing 737-200 Adv, registration HC-BIG, Ciudad de Loja
    Airline: TAME (Transportes Aéreos Militares Ecuatorianos)
    Person: Captain Jorge Leonardo Peña Terán - ~30 hours on type (required 100)
    Event: Flight 173 disappeared one mile short of Mariscal Lamar Airport

    - TAME was a military airline whose culture placed retired generals in command roles rather than subordinate seats.
    - Boeing's purchase agreement required six weeks in Seattle, one month with a Boeing instructor, one month with a Boeing-approved co-pilot, and 100 hours before left-seat command.
    - Terán completed three weeks in a Brazil simulator and logged roughly thirty hours on the 737 after joining TAME about ten months earlier.
    - The morning of July 11, 1983, the Ciudad de Loja departed Quito with 111 passengers and 8 crew for a 50-minute flight to Cuenca in marginal weather on approach.
    - One passenger, Governor Juan Cordero Íñiguez, overslept and missed the flight - a single missed seat that highlights how narrowly fate and procedure intersected.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
    続きを読む 一部表示
    14 分