https://www.spreaker.com/podcast/aviation-survivals--7307849
Each episode reconstructs one true aviation story from the ground up, told in full, with no host breaking in and no filler between the facts. You get the timeline minute by minute, the voices from the black box, the investigators piecing together what the plane crash actually looked like from the inside, and the survivors who walked away carrying a version of the event no official aviation report can fully capture.

Some episodes cover famous air disasters that reshaped aviation safety rules forever. Others dig into obscure aviation accidents that barely made the news but changed the lives of everyone aboard. You will hear about mechanical failures no one caught in time, weather that turned a routine flight into a fight for survival, and the small human errors that the aviation industry spends billions trying to prevent. The black box data, the wreckage analysis, and the radio transcripts all get pulled together into one continuous, unflinching account of what really happened in the skies.

If you want to understand how a plane crash actually happens, not the headline version but the real sequence of failures and choices behind every aviation tragedy, subscribe and follow the feed. New episodes drop weekly, each one a complete story from takeoff to the moment everything went wrong, and each one a reminder of how fragile aviation safety truly is.]]>enHistoryCopyright OBOMEDIA ENTERTAINMENThttps://d3wo5wojvuv7l.cloudfront.net/t_rss_itunes_square_1400/images.spreaker.com/original/fe495ac5383fc4a9d93c84ab7ed638c4.jpghttps://www.spreaker.com/podcast/aviation-survivals--7307849Mon, 31 Aug 2026 17:39:35 +0000OBOMEDIA ENTERTAINMENTOBOMEDIA ENTERTAINMENTcreators@obomedia.comAviation disasters leave behind a trail of evidence that most people never see: a scorched propeller blade, a cockpit recording cut short, a maintenance log with one signature missing. Aviation Survival Stories starts there, in the wreckage, and works...
Each episode reconstructs one true aviation story from the ground up, told in full, with no host breaking in and no filler between the facts. You get the timeline minute by minute, the voices from the black box, the investigators piecing together what the plane crash actually looked like from the inside, and the survivors who walked away carrying a version of the event no official aviation report can fully capture.

Some episodes cover famous air disasters that reshaped aviation safety rules forever. Others dig into obscure aviation accidents that barely made the news but changed the lives of everyone aboard. You will hear about mechanical failures no one caught in time, weather that turned a routine flight into a fight for survival, and the small human errors that the aviation industry spends billions trying to prevent. The black box data, the wreckage analysis, and the radio transcripts all get pulled together into one continuous, unflinching account of what really happened in the skies.

If you want to understand how a plane crash actually happens, not the headline version but the real sequence of failures and choices behind every aviation tragedy, subscribe and follow the feed. New episodes drop weekly, each one a complete story from takeoff to the moment everything went wrong, and each one a reminder of how fragile aviation safety truly is.]]>falsebf410af4-7107-5e33-8333-cf5beebd2b5depisodichttps://www.spreaker.com/episode/the-radar-scale-maxed-out-and-they-had-five-minutes-to-live--74771468
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.]]>https://api.spreaker.com/episode/74771468Mon, 31 Aug 2026 17:39:35 +0000OBOMEDIA ENTERTAINMENTA 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...
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.]]>942falsefullhttps://www.spreaker.com/episode/the-empty-flight-recorder-box-that-erased-whether-they-made-it-in-time--74771467
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.]]>https://api.spreaker.com/episode/74771467Mon, 31 Aug 2026 17:39:31 +0000OBOMEDIA ENTERTAINMENTA 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...
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.]]>937falsefullhttps://www.spreaker.com/episode/the-blizzard-that-grounded-search-helicopters-and-cost-four-days-to-reach-them--74771465
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.]]>https://api.spreaker.com/episode/74771465Mon, 31 Aug 2026 17:39:27 +0000OBOMEDIA ENTERTAINMENTA 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...
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.]]>855falsefullhttps://www.spreaker.com/episode/the-three-handed-altimeter-misread-cost-them-ten-thousand-feet-and-nine-lives--74771464
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.]]>https://api.spreaker.com/episode/74771464Mon, 31 Aug 2026 17:39:23 +0000OBOMEDIA ENTERTAINMENTA 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 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.]]>841falsefullhttps://www.spreaker.com/episode/the-failed-right-engine-turbine-blades-bled-thrust-and-left-them-two-miles-short--74771462
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.]]>https://api.spreaker.com/episode/74771462Mon, 31 Aug 2026 17:39:19 +0000OBOMEDIA ENTERTAINMENTA 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 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.]]>889falsefullhttps://www.spreaker.com/episode/the-dark-landing-gear-light-that-hid-how-fast-fuel-leaked--74771460
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.]]>https://api.spreaker.com/episode/74771460Mon, 31 Aug 2026 17:39:15 +0000OBOMEDIA ENTERTAINMENTA 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...
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.]]>1187falsefullhttps://www.spreaker.com/episode/the-one-missed-seat-that-cost-them-one-mile-from-the-runway--74771459
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.]]>https://api.spreaker.com/episode/74771459Mon, 31 Aug 2026 17:39:10 +0000OBOMEDIA ENTERTAINMENTA 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...
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.]]>839falsefullhttps://www.spreaker.com/episode/the-wing-frost-that-formed-on-the-ramp-did-they-deice-in-time--74771458
The wing frost that formed on the ramp - did they deice in time?

In this episode, we follow the events and decisions on the night a 23‑year‑old DC‑9‑15RC prepared to depart Cleveland in falling snow. The episode traces the pilots’ backgrounds, the aircraft’s design sensitivity to contamination, and the organizational gaps that set the stage - could a ramp check or a different briefing have changed everything?

Date: February 17, 1991
Aircraft: DC-9-15RC (series 10 variant)
Location: Cleveland Hopkins International Airport
Person: Captain David Reay; First Officer Richard Duney Jr.
Operator: Ryan International Airlines (carrying U.S. Mail)

- Engines were running on the ramp with anti-ice switches for the engines turned on eight minutes before takeoff while nobody walked out to visually inspect the wings.
- The DC-9-15RC lacks leading-edge slats present on other DC-9 variants, making it highly sensitive to even thin layers of frost or ice.
- Both pilots had most of their DC-9 experience in series 30/50 aircraft that include leading-edge devices, not the frost‑sensitive series 10 they were flying that night.
- Ryan International had acquired the aircraft fleet without being informed of three prior accidents tied to ice contamination on the same airframe family.
- Weather at Cleveland was below freezing with light snow, one‑mile visibility, and an active low‑level wind shear advisory during the crew’s short ground stop.

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.]]>https://api.spreaker.com/episode/74771458Mon, 31 Aug 2026 17:39:07 +0000OBOMEDIA ENTERTAINMENTA frost‑sensitive DC‑9 sits engines‑running on a snowy Cleveland ramp as two pilots prepare to take off - did they deice in time? The wing frost that formed on the ramp - did they deice in time? In this episode, we follow the events and...
The wing frost that formed on the ramp - did they deice in time?

In this episode, we follow the events and decisions on the night a 23‑year‑old DC‑9‑15RC prepared to depart Cleveland in falling snow. The episode traces the pilots’ backgrounds, the aircraft’s design sensitivity to contamination, and the organizational gaps that set the stage - could a ramp check or a different briefing have changed everything?

Date: February 17, 1991
Aircraft: DC-9-15RC (series 10 variant)
Location: Cleveland Hopkins International Airport
Person: Captain David Reay; First Officer Richard Duney Jr.
Operator: Ryan International Airlines (carrying U.S. Mail)

- Engines were running on the ramp with anti-ice switches for the engines turned on eight minutes before takeoff while nobody walked out to visually inspect the wings.
- The DC-9-15RC lacks leading-edge slats present on other DC-9 variants, making it highly sensitive to even thin layers of frost or ice.
- Both pilots had most of their DC-9 experience in series 30/50 aircraft that include leading-edge devices, not the frost‑sensitive series 10 they were flying that night.
- Ryan International had acquired the aircraft fleet without being informed of three prior accidents tied to ice contamination on the same airframe family.
- Weather at Cleveland was below freezing with light snow, one‑mile visibility, and an active low‑level wind shear advisory during the crew’s short ground stop.

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.]]>935falsefullhttps://www.spreaker.com/episode/the-flagpole-sheared-the-wing-and-left-them-four-thousand-feet-short--74771457
The flagpole sheared the wing and left them four thousand feet short

In this episode, we follow the flight, crew, and neighborhood moments leading up to the March 7, 1950 impact that left an airliner short of the runway. We trace decisions, weather, and airport conditions to ask how a rested crew on a functioning aircraft came to be low and off course - and what the airport owes the homes below.

Date: March 7, 1950
Flight: Northwest Orient Flight 307
Aircraft: Martin 202, registration N93050
Location: Minneapolis, Runway 35 approach
Crew: Captain Donald B. Jones; First Officer William Tracy McGinn; flight attendant Mary Kennedy

- The flight departed a multi-leg route that day and, after a hydraulic seal replacement delay in Detroit, had its schedule compressed into a late-evening approach.
- Minneapolis approach reported a 900-foot ceiling, visibility 0.5-0.75 miles, north winds gusting to 40 mph, and two recent airport electrical failures with instructions to assume a third if radio contact was lost.
- A Northwest Orient 377 had used maximum power on Runway 35 just before Flight 307’s approach; investigators examined whether disturbed air or wake turbulence affected the Martin 202.
- Captain Jones had 7,619 total flight hours, nearly 1,000 in the 202; First Officer McGinn held an ATP with 2,432 hours and 585 in type; both pilots had rested nearly 22 hours before departure.
- At 9:02 PM a 70-foot flagpole at Fort Snelling’s north entrance was sheared by the aircraft’s left wing, and the plane tumbled toward a Minneapolis neighborhood four thousand feet short of the runway.

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.]]>https://api.spreaker.com/episode/74771457Mon, 31 Aug 2026 17:39:03 +0000OBOMEDIA ENTERTAINMENTA flagpole shears a wing at night over Minneapolis as Northwest Orient Flight 307 struggles toward Runway 35 - did they make it in time? The flagpole sheared the wing and left them four thousand feet short In this episode, we follow the flight,...
The flagpole sheared the wing and left them four thousand feet short

In this episode, we follow the flight, crew, and neighborhood moments leading up to the March 7, 1950 impact that left an airliner short of the runway. We trace decisions, weather, and airport conditions to ask how a rested crew on a functioning aircraft came to be low and off course - and what the airport owes the homes below.

Date: March 7, 1950
Flight: Northwest Orient Flight 307
Aircraft: Martin 202, registration N93050
Location: Minneapolis, Runway 35 approach
Crew: Captain Donald B. Jones; First Officer William Tracy McGinn; flight attendant Mary Kennedy

- The flight departed a multi-leg route that day and, after a hydraulic seal replacement delay in Detroit, had its schedule compressed into a late-evening approach.
- Minneapolis approach reported a 900-foot ceiling, visibility 0.5-0.75 miles, north winds gusting to 40 mph, and two recent airport electrical failures with instructions to assume a third if radio contact was lost.
- A Northwest Orient 377 had used maximum power on Runway 35 just before Flight 307’s approach; investigators examined whether disturbed air or wake turbulence affected the Martin 202.
- Captain Jones had 7,619 total flight hours, nearly 1,000 in the 202; First Officer McGinn held an ATP with 2,432 hours and 585 in type; both pilots had rested nearly 22 hours before departure.
- At 9:02 PM a 70-foot flagpole at Fort Snelling’s north entrance was sheared by the aircraft’s left wing, and the plane tumbled toward a Minneapolis neighborhood four thousand feet short of the runway.

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.]]>1284falsefullhttps://www.spreaker.com/episode/the-strobe-beacon-lit-off-course-would-they-reach-the-runway--74771456
The strobe beacon lit off-course - would they reach the runway?

In this episode, we follow the final minutes of Linjeflyg Flight 267 as the crew descends into heavy fog toward Ängelholm-Helsingborg, guided by a light that should not have been there. What decisions, procedures, and infrastructure mismatches set the aircraft on a dangerous path, and how did a single unauthorized beacon alter the approach?

Event: Linjeflyg Flight 267
Date: November 20, 1964
Aircraft: Convair CV-340, registration SE-CCK
Location: Ängelholm-Helsingborg Airport (F 10 Ängelholm)
Condition: Cloud base approximately 60 meters; visibility 1.5-2 km

- The crew was following standard approach beacons (LJ outer, J inner) whose positions at F 10 were displaced far from civilian norms.
- A strobe beacon, 2,250 meters from threshold and 110 meters right of centerline, pulsed in the fog but was not on any approach chart the pilots carried.
- The tower switched the strobe on and told the crew it was on the runway centerline and about 2.5 km from threshold - a positional mismatch the pilots relied upon.
- The Convair had changed owners and been rebuilt multiple times in the decade before the flight, operating a routine domestic evening run with 43 people aboard.
- Civilian operations at the airport occurred on military terms, leaving navigational aids and procedures out of sync with civilian approach expectations.

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.]]>https://api.spreaker.com/episode/74771456Mon, 31 Aug 2026 17:38:59 +0000OBOMEDIA ENTERTAINMENTA pulsing strobe appears in the fog by the runway as a Convair descends - did they make it to the runway in time? The strobe beacon lit off-course - would they reach the runway? In this episode, we follow the final minutes of Linjeflyg Flight...
The strobe beacon lit off-course - would they reach the runway?

In this episode, we follow the final minutes of Linjeflyg Flight 267 as the crew descends into heavy fog toward Ängelholm-Helsingborg, guided by a light that should not have been there. What decisions, procedures, and infrastructure mismatches set the aircraft on a dangerous path, and how did a single unauthorized beacon alter the approach?

Event: Linjeflyg Flight 267
Date: November 20, 1964
Aircraft: Convair CV-340, registration SE-CCK
Location: Ängelholm-Helsingborg Airport (F 10 Ängelholm)
Condition: Cloud base approximately 60 meters; visibility 1.5-2 km

- The crew was following standard approach beacons (LJ outer, J inner) whose positions at F 10 were displaced far from civilian norms.
- A strobe beacon, 2,250 meters from threshold and 110 meters right of centerline, pulsed in the fog but was not on any approach chart the pilots carried.
- The tower switched the strobe on and told the crew it was on the runway centerline and about 2.5 km from threshold - a positional mismatch the pilots relied upon.
- The Convair had changed owners and been rebuilt multiple times in the decade before the flight, operating a routine domestic evening run with 43 people aboard.
- Civilian operations at the airport occurred on military terms, leaving navigational aids and procedures out of sync with civilian approach expectations.

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.]]>905falsefullhttps://www.spreaker.com/episode/the-cracked-solder-joint-flashed-amber-did-they-fix-it-in-time--74771455
The cracked solder joint flashed amber - did they fix it in time?

In this episode, we follow a routine flight that departed Surabaya and vanished from radar forty-three minutes later, tracking the chain of warnings, maintenance choices, and human lives on board. What decisions were made in the cockpit and on the ground as the same fault recurred again and again?

Event: AirAsia Flight 8501
Date: December 28, 2014
Aircraft: Airbus A320-216, registration PK-AXC
Location: Java Sea, en route M635
Passengers and crew: 162 (155 passengers, 7 crew)

- The same amber rudder travel limiter warning had activated 23 times in the prior 12 months and been reset each time.
- A fingertip-sized cracked soldered connection inside the rudder limiter unit was present but never repaired.
- The flight departed Juanda Airport at 05:35, climbed to FL320, and vanished from radar at 06:18, 43 minutes after takeoff.
- Captain Iriyanto had over 20,500 flight hours; First Officer Rémi Plesel had 2,247 hours and was two years into a second career.
- No distress call was transmitted; air traffic control first learned something was wrong when the aircraft disappeared from radar.

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.]]>https://api.spreaker.com/episode/74771455Mon, 31 Aug 2026 17:38:55 +0000OBOMEDIA ENTERTAINMENTA cracked solder joint tripped an amber rudder limiter warning on an Airbus over the Java Sea - did they fix it in time? The cracked solder joint flashed amber - did they fix it in time? In this episode, we follow a routine flight that departed...
The cracked solder joint flashed amber - did they fix it in time?

In this episode, we follow a routine flight that departed Surabaya and vanished from radar forty-three minutes later, tracking the chain of warnings, maintenance choices, and human lives on board. What decisions were made in the cockpit and on the ground as the same fault recurred again and again?

Event: AirAsia Flight 8501
Date: December 28, 2014
Aircraft: Airbus A320-216, registration PK-AXC
Location: Java Sea, en route M635
Passengers and crew: 162 (155 passengers, 7 crew)

- The same amber rudder travel limiter warning had activated 23 times in the prior 12 months and been reset each time.
- A fingertip-sized cracked soldered connection inside the rudder limiter unit was present but never repaired.
- The flight departed Juanda Airport at 05:35, climbed to FL320, and vanished from radar at 06:18, 43 minutes after takeoff.
- Captain Iriyanto had over 20,500 flight hours; First Officer Rémi Plesel had 2,247 hours and was two years into a second career.
- No distress call was transmitted; air traffic control first learned something was wrong when the aircraft disappeared from radar.

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.]]>950falsefullhttps://www.spreaker.com/episode/the-fuel-gauge-warned-of-ditching-did-they-make-it-in-time--74771454
The fuel gauge warned of ditching - did they make it in time?

In this episode, we follow the last hours of OB-1303, a Boeing 727 ferry flight carrying sixteen people from Keflavík toward Gander that vanished after a single distress transmission. We lay out the timeline, the odd route deviation, and the sparse clues that forced searchers to ask one grim question: where do you search when nothing is left to find?

Date: September 11, 1990
Aircraft: Boeing 727 (registration OB-1303)
People aboard: 16 (six crew, ten others)
Last reported altitude: 10,000 feet
Last known position: ~250 miles southeast of St. John’s

- Departed Keflavík at 13:16 local after a routine refueling of ~20 metric tons for a multi-leg ferry flight back to Lima.
- Flight plan called for routes through London/Milan, Keflavík, Gander, Miami, and finally Lima; this leg was Keflavík to Gander.
- By 14:50 the aircraft left Icelandic control and was estimated to need ~3h38m to reach Gander; it never arrived.
- At ~15:20 two commercial flights relayed a transmission reporting fuel critically low and imminent ditching, then the frequency went silent.
- Searchers found no wreckage, no debris field, and no life rafts within the area implied by the faint satellite pulse detected after the last transmission.

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.]]>https://api.spreaker.com/episode/74771454Mon, 31 Aug 2026 17:38:51 +0000OBOMEDIA ENTERTAINMENTA ferry flight over the North Atlantic reports fuel critical and imminent ditching - did they make it in time? The fuel gauge warned of ditching - did they make it in time? In this episode, we follow the last hours of OB-1303, a Boeing 727 ferry...
The fuel gauge warned of ditching - did they make it in time?

In this episode, we follow the last hours of OB-1303, a Boeing 727 ferry flight carrying sixteen people from Keflavík toward Gander that vanished after a single distress transmission. We lay out the timeline, the odd route deviation, and the sparse clues that forced searchers to ask one grim question: where do you search when nothing is left to find?

Date: September 11, 1990
Aircraft: Boeing 727 (registration OB-1303)
People aboard: 16 (six crew, ten others)
Last reported altitude: 10,000 feet
Last known position: ~250 miles southeast of St. John’s

- Departed Keflavík at 13:16 local after a routine refueling of ~20 metric tons for a multi-leg ferry flight back to Lima.
- Flight plan called for routes through London/Milan, Keflavík, Gander, Miami, and finally Lima; this leg was Keflavík to Gander.
- By 14:50 the aircraft left Icelandic control and was estimated to need ~3h38m to reach Gander; it never arrived.
- At ~15:20 two commercial flights relayed a transmission reporting fuel critically low and imminent ditching, then the frequency went silent.
- Searchers found no wreckage, no debris field, and no life rafts within the area implied by the faint satellite pulse detected after the last transmission.

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.]]>972falsefullhttps://www.spreaker.com/episode/the-unlit-runway-fooled-them-did-they-stop-in-time--74771453
The unlit runway fooled them - did they stop in time?

In this episode, we follow the morning of August 27, 2006, at Blue Grass Airport as a fifty-seat regional jet prepares to depart in pre-dawn darkness. We trace the crew’s actions, the airport environment, and the cockpit audio that captured the thirty-seven seconds when pilots noticed something odd but did not abort - what happened in that window?

Date: August 27, 2006
Location: Blue Grass Airport, Lexington, Kentucky
Aircraft: Bombardier CRJ-100 ER, serial number 7472
Flight: Comair Flight 5191 (Delta Connection)
Runways: Runway 22 - 7003 ft lit; Runway 26 - 3501 ft unlit

- Captain Jeffrey Clay (35) had 4,710 total hours, 3,082 on type, and was responsible for taxiing that morning.
- First Officer James Polehinke (44) had 6,564 total hours, 3,564 on type, and was the pilot flying for takeoff.
- The tower was staffed by a single FAA controller handling both tower and ground duties despite prior guidance recommending two.
- Both runways shared a common threshold area and looked nearly identical in the pre-dawn dark; Runway 22 required an extra taxi turn, Runway 26 was a straighter alignment from the ramp.
- The cockpit voice recorder captured 27 minutes of routine conversation, then 37 seconds in which one pilot remarked, "That is weird with no lights," and no abort was initiated.

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.]]>https://api.spreaker.com/episode/74771453Mon, 31 Aug 2026 17:38:47 +0000OBOMEDIA ENTERTAINMENTA regional jet lines up on an unlit runway that is 243 feet too short for takeoff - did the pilots recognize the danger in time? (aviation) The unlit runway fooled them - did they stop in time? In this episode, we follow the morning of August...
The unlit runway fooled them - did they stop in time?

In this episode, we follow the morning of August 27, 2006, at Blue Grass Airport as a fifty-seat regional jet prepares to depart in pre-dawn darkness. We trace the crew’s actions, the airport environment, and the cockpit audio that captured the thirty-seven seconds when pilots noticed something odd but did not abort - what happened in that window?

Date: August 27, 2006
Location: Blue Grass Airport, Lexington, Kentucky
Aircraft: Bombardier CRJ-100 ER, serial number 7472
Flight: Comair Flight 5191 (Delta Connection)
Runways: Runway 22 - 7003 ft lit; Runway 26 - 3501 ft unlit

- Captain Jeffrey Clay (35) had 4,710 total hours, 3,082 on type, and was responsible for taxiing that morning.
- First Officer James Polehinke (44) had 6,564 total hours, 3,564 on type, and was the pilot flying for takeoff.
- The tower was staffed by a single FAA controller handling both tower and ground duties despite prior guidance recommending two.
- Both runways shared a common threshold area and looked nearly identical in the pre-dawn dark; Runway 22 required an extra taxi turn, Runway 26 was a straighter alignment from the ramp.
- The cockpit voice recorder captured 27 minutes of routine conversation, then 37 seconds in which one pilot remarked, "That is weird with no lights," and no abort was initiated.

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.]]>870falsefullhttps://www.spreaker.com/episode/the-c-46-climbed-into-darkness-and-missed-the-qingdao-approach-in-fog--74771451
The C‑46 climbed into darkness and missed the Qingdao approach in fog

In this episode, we follow the flight that left Longhua Airport at 5:10 AM on January 5, 1947, and never reached its destination. The episode lays out who was aboard, the weather warnings received, and the decisions made en route - what happened during the approach to Qingdao?

Date: January 5, 1947
Aircraft: Curtiss C-46
Location: Langya Mountain, approach to Qingdao
People: 42 aboard (including opera performer Li Shifang, student Wan Hanguang, Captain Charles H. Sharkey)
Warning: Dense fog reported by US Navy at Cangkou, Qingdao

- Captain Charles H. Sharkey read the Navy weather warning from Cangkou and chose to depart Longhua at 5:10 AM.
- The flight climbed out of Shanghai into dense coastal fog and set a northeast course to Qingdao, a planned two-hour thirty-five-minute trip.
- At 7:45 AM the C-46 crossed the Qingdao coastline and began its descent through overcast toward the approach corridor.
- Langya Mountain, an unassuming ridge roughly 800 meters high at the edge of Qingdao’s approach, lay hidden in the fog along the descent path.
- The passenger list included students, performers, officials, missionaries, and a man who boarded under a false name, each with distinct reasons for travelling that morning.

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.]]>https://api.spreaker.com/episode/74771451Mon, 31 Aug 2026 17:38:43 +0000OBOMEDIA ENTERTAINMENTA Curtiss C-46 climbs into dense fog off Shanghai bound for Qingdao - did they make the approach in time? The C‑46 climbed into darkness and missed the Qingdao approach in fog In this episode, we follow the flight that left Longhua Airport at...
The C‑46 climbed into darkness and missed the Qingdao approach in fog

In this episode, we follow the flight that left Longhua Airport at 5:10 AM on January 5, 1947, and never reached its destination. The episode lays out who was aboard, the weather warnings received, and the decisions made en route - what happened during the approach to Qingdao?

Date: January 5, 1947
Aircraft: Curtiss C-46
Location: Langya Mountain, approach to Qingdao
People: 42 aboard (including opera performer Li Shifang, student Wan Hanguang, Captain Charles H. Sharkey)
Warning: Dense fog reported by US Navy at Cangkou, Qingdao

- Captain Charles H. Sharkey read the Navy weather warning from Cangkou and chose to depart Longhua at 5:10 AM.
- The flight climbed out of Shanghai into dense coastal fog and set a northeast course to Qingdao, a planned two-hour thirty-five-minute trip.
- At 7:45 AM the C-46 crossed the Qingdao coastline and began its descent through overcast toward the approach corridor.
- Langya Mountain, an unassuming ridge roughly 800 meters high at the edge of Qingdao’s approach, lay hidden in the fog along the descent path.
- The passenger list included students, performers, officials, missionaries, and a man who boarded under a false name, each with distinct reasons for travelling that morning.

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.]]>918falsefullhttps://www.spreaker.com/episode/the-captain-s-relentless-insults-froze-the-co-pilot-and-lost-them-minutes--74771439
The captain's relentless insults froze the co‑pilot and lost them minutes

In this episode, we follow the two-hour flight of Airblue 202 from Karachi to Islamabad and the cockpit dynamics that unfolded before impact. The episode covers the flight's technical status, the pilots' backgrounds, the approach procedure and weather challenges, and asks how interpersonal breakdowns shaped the minutes that mattered.

Date: 28 July 2010
Aircraft: Airbus A321, registration AP‑BJB
Route: Karachi (Jinnah) to Islamabad (Benazir Bhutto)
People: 152 aboard (146 passengers, 6 crew)
Visibility: 3.5 kilometers

- Captain Pervez‑Iqbal Chaudhry, age 61, with 25,497 total flight hours and 1,060 on the A320 family, assumed an authoritative cockpit role.
- First Officer Muntajib‑ud‑Din Ahmed, age 34, former Pakistan Air Force squadron leader, had 1,837 total hours and 286 on the A320 family.
- For about 60 minutes Chaudhry subjected Ahmed to sustained harsh and dismissive criticism recorded on the cockpit voice recorder.
- Islamabad's circling approach to runway 12 required a minimum safe altitude of 2,500 feet and a protected zone extending 8 km where the Margalla Hills are charted.
- In the 30 minutes before Airblue 202 arrived, other flights diverted or executed multiple go‑arounds, signaling challenging conditions for the approach.

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.]]>https://api.spreaker.com/episode/74771439Mon, 31 Aug 2026 17:38:39 +0000OBOMEDIA ENTERTAINMENTA captain's insults silence his co‑pilot during an Islamabad approach as a charted hill fills the windscreen - did they make it in time? The captain's relentless insults froze the co‑pilot and lost them minutes In this episode, we follow the...
The captain's relentless insults froze the co‑pilot and lost them minutes

In this episode, we follow the two-hour flight of Airblue 202 from Karachi to Islamabad and the cockpit dynamics that unfolded before impact. The episode covers the flight's technical status, the pilots' backgrounds, the approach procedure and weather challenges, and asks how interpersonal breakdowns shaped the minutes that mattered.

Date: 28 July 2010
Aircraft: Airbus A321, registration AP‑BJB
Route: Karachi (Jinnah) to Islamabad (Benazir Bhutto)
People: 152 aboard (146 passengers, 6 crew)
Visibility: 3.5 kilometers

- Captain Pervez‑Iqbal Chaudhry, age 61, with 25,497 total flight hours and 1,060 on the A320 family, assumed an authoritative cockpit role.
- First Officer Muntajib‑ud‑Din Ahmed, age 34, former Pakistan Air Force squadron leader, had 1,837 total hours and 286 on the A320 family.
- For about 60 minutes Chaudhry subjected Ahmed to sustained harsh and dismissive criticism recorded on the cockpit voice recorder.
- Islamabad's circling approach to runway 12 required a minimum safe altitude of 2,500 feet and a protected zone extending 8 km where the Margalla Hills are charted.
- In the 30 minutes before Airblue 202 arrived, other flights diverted or executed multiple go‑arounds, signaling challenging conditions for the approach.

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.]]>983falsefullhttps://www.spreaker.com/episode/the-off-duty-pilot-grabbed-the-controls-as-the-wind-shifted-did-they-lift--74771438
The off‑duty pilot grabbed the controls as the wind shifted - did they lift?

In this episode, we present the documented account of Aeromexico Connect Flight 2431's takeoff at Durango, the cockpit configuration that day, and the sequence of events captured on the flight and voice recorders. Listeners are led through the decisions, the shifting weather, and the crew roles that set the stage for what happened next.

Aircraft: Embraer 190, registration XA‑GAL
Date: July 31, 2018
Location: Durango International Airport
People: Captain Carlos Galván Meyran; First Officer Daniel Dardon Chávez; José Ramón Vázquez (listed passenger)
Event: Left wing struck runway during takeoff roll

- The plane had climbed to about thirty feet-roughly the height of a two‑story house-before falling back toward the ground.
- José Ramón Vázquez sat in the co‑pilot's right seat with his hands on the controls though he was listed as a passenger and not certified on the Embraer 190.
- First Officer Daniel Dardon Chávez, though holding an ATP and type hours, was in the observer's jump seat rather than the right seat during the takeoff.
- The flight was already eighteen minutes late after maintenance found a fuel leak in engine one, which was deemed within acceptable limits before departure.
- Tower wind reports three minutes old showed 090 degrees at 20 knots; the flight data recorder captured a rapid wind shift during the takeoff roll.

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.]]>https://api.spreaker.com/episode/74771438Mon, 31 Aug 2026 17:38:35 +0000OBOMEDIA ENTERTAINMENTAn off‑duty pilot with simulator hours-listed as a passenger-takes the controls during takeoff at Durango as the wind shifts; did they lift? The off‑duty pilot grabbed the controls as the wind shifted - did they lift? In this episode, we present...
The off‑duty pilot grabbed the controls as the wind shifted - did they lift?

In this episode, we present the documented account of Aeromexico Connect Flight 2431's takeoff at Durango, the cockpit configuration that day, and the sequence of events captured on the flight and voice recorders. Listeners are led through the decisions, the shifting weather, and the crew roles that set the stage for what happened next.

Aircraft: Embraer 190, registration XA‑GAL
Date: July 31, 2018
Location: Durango International Airport
People: Captain Carlos Galván Meyran; First Officer Daniel Dardon Chávez; José Ramón Vázquez (listed passenger)
Event: Left wing struck runway during takeoff roll

- The plane had climbed to about thirty feet-roughly the height of a two‑story house-before falling back toward the ground.
- José Ramón Vázquez sat in the co‑pilot's right seat with his hands on the controls though he was listed as a passenger and not certified on the Embraer 190.
- First Officer Daniel Dardon Chávez, though holding an ATP and type hours, was in the observer's jump seat rather than the right seat during the takeoff.
- The flight was already eighteen minutes late after maintenance found a fuel leak in engine one, which was deemed within acceptable limits before departure.
- Tower wind reports three minutes old showed 090 degrees at 20 knots; the flight data recorder captured a rapid wind shift during the takeoff roll.

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.]]>1027falsefullhttps://www.spreaker.com/episode/the-rear-pressure-bulkhead-detonated-and-stole-the-crew-s-last-twelve-minutes--74771437
The rear pressure bulkhead detonated and stole the crew's last twelve minutes

In this episode, we follow Japan Airlines Flight 123 from boarding at Gate 18 through its short domestic climb and the ordinary people aboard. The story traces a seven-year-old structural repair, the aircraft's thousands of pressurization cycles, and the moment the rear pressure bulkhead catastrophically fails-what decisions and inspections led here?

Aircraft: Boeing 747SR JA8119
Event: Failure of rear pressure bulkhead
Date: August 12, 1985
Flight: Japan Airlines Flight 123
Cycles: 12,318 pressurization cycles

- A repair team made a single structural substitution in 1978 that engineers predicted would fail after about 11,000 cycles.
- The aircraft continued flying 1,318 cycles beyond that estimate, accumulating 18,800 pressurization cycles over eleven years.
- At 18:24, twelve minutes after takeoff from Haneda on a short hop to Osaka, the rear pressure bulkhead detonated.
- The explosion severed all four hydraulic lines, destroyed the vertical stabilizer, and ripped away the rudder within seconds.
- The cockpit crew-Captain Masami Takahama, First Officer Yutaka Sasaki, and Flight Engineer Hiroshi Fukuda-faced a situation no training had prepared them for.

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.]]>https://api.spreaker.com/episode/74771437Mon, 31 Aug 2026 17:38:31 +0000OBOMEDIA ENTERTAINMENTA routine flight from Haneda becomes a race when a repaired bulkhead may blow apart the plane-did they make it in time? The rear pressure bulkhead detonated and stole the crew's last twelve minutes In this episode, we follow Japan Airlines...
The rear pressure bulkhead detonated and stole the crew's last twelve minutes

In this episode, we follow Japan Airlines Flight 123 from boarding at Gate 18 through its short domestic climb and the ordinary people aboard. The story traces a seven-year-old structural repair, the aircraft's thousands of pressurization cycles, and the moment the rear pressure bulkhead catastrophically fails-what decisions and inspections led here?

Aircraft: Boeing 747SR JA8119
Event: Failure of rear pressure bulkhead
Date: August 12, 1985
Flight: Japan Airlines Flight 123
Cycles: 12,318 pressurization cycles

- A repair team made a single structural substitution in 1978 that engineers predicted would fail after about 11,000 cycles.
- The aircraft continued flying 1,318 cycles beyond that estimate, accumulating 18,800 pressurization cycles over eleven years.
- At 18:24, twelve minutes after takeoff from Haneda on a short hop to Osaka, the rear pressure bulkhead detonated.
- The explosion severed all four hydraulic lines, destroyed the vertical stabilizer, and ripped away the rudder within seconds.
- The cockpit crew-Captain Masami Takahama, First Officer Yutaka Sasaki, and Flight Engineer Hiroshi Fukuda-faced a situation no training had prepared them for.

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.]]>1306falsefullhttps://www.spreaker.com/episode/the-travel-rule-that-kept-his-assistants-home-and-who-made-the-flight--74771436
The travel rule that kept his assistants home - and who made the flight?

In this episode, we follow the choices and routines that set a team’s travel plan for a December road trip and the single decision that placed one man on a doomed charter flight. We trace the policy, the season, and the moments that led to that night - and ask what the travel rule meant for who traveled.

Person: Bobby Watson
Date: December 13, 1977
Location: small airport in Indiana
Event: charter flight took off and did not return
Topic: college basketball travel policy

- Watson had survived two Vietnam tours with the 101st Airborne and received five Purple Hearts.
- He built a coaching career from assistant at Xavier to head coach at Evansville after a 61-8 record at Ferrum.
- As Evansville’s first Division I season progressed, Watson insisted on flying in a day early to practice on the opponent’s court.
- On December 13, 1977, a commercial charter with 29 people on board departed from a small Indiana airport.
- Watson’s assistant coaches were absent on scouting assignments, following the travel plan that dictated who would be on the flight.

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.]]>https://api.spreaker.com/episode/74771436Mon, 31 Aug 2026 17:38:26 +0000OBOMEDIA ENTERTAINMENTA head coach boards a charter from a small Indiana airport because his travel rule forces practice on the opponent’s court - did they make it in time? The travel rule that kept his assistants home - and who made the flight? In this episode, we...
The travel rule that kept his assistants home - and who made the flight?

In this episode, we follow the choices and routines that set a team’s travel plan for a December road trip and the single decision that placed one man on a doomed charter flight. We trace the policy, the season, and the moments that led to that night - and ask what the travel rule meant for who traveled.

Person: Bobby Watson
Date: December 13, 1977
Location: small airport in Indiana
Event: charter flight took off and did not return
Topic: college basketball travel policy

- Watson had survived two Vietnam tours with the 101st Airborne and received five Purple Hearts.
- He built a coaching career from assistant at Xavier to head coach at Evansville after a 61-8 record at Ferrum.
- As Evansville’s first Division I season progressed, Watson insisted on flying in a day early to practice on the opponent’s court.
- On December 13, 1977, a commercial charter with 29 people on board departed from a small Indiana airport.
- Watson’s assistant coaches were absent on scouting assignments, following the travel plan that dictated who would be on the flight.

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.]]>847falsefullhttps://www.spreaker.com/episode/the-de-icer-flowed-at-18-fouled-the-engines-and-cost-them-minutes--74771433
The de-icer flowed at 18% - fouled the engines and cost them minutes

In this episode, we lay out the hour before Air Florida Flight 90 ever moved and follow the chain of ground decisions, equipment faults, and cold-weather inexperience that set the flight on its course. The narrative asks how de-icing, taxi choices, and crew background combined to create a crisis the moment the plane left the ground.

Date: January 13, 1982
Location: Washington National Airport
Aircraft: Boeing 737
Flight: Air Florida Flight 90
Passengers aboard: 79

- Two de-icing workers used one truck; the glycol concentration delivered was 18% instead of the required 30% and the nozzle was non-standard.
- Pitot covers, static port covers, and engine inlet covers were not installed before the aircraft was signed off and cleared to taxi.
- The crew backed away from the gate using reverse thrust in continuous freezing precipitation, a maneuver cautioned against in icing conditions.
- The 737 waited in the taxi queue directly behind a DC-9 with engines running for 49 minutes while freezing precipitation continued.
- Captain Larry Wheaton and First Officer Roger Pettit had logged only ten combined winter takeoffs on the 737, despite substantial total flight hours.

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.]]>https://api.spreaker.com/episode/74771433Mon, 31 Aug 2026 17:38:23 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 at a snowy Seattle gate with de-icer flowing-minutes tick toward a doomed takeoff: did they make it in time? The de-icer flowed at 18% - fouled the engines and cost them minutes In this episode, we lay out the hour before Air...
The de-icer flowed at 18% - fouled the engines and cost them minutes

In this episode, we lay out the hour before Air Florida Flight 90 ever moved and follow the chain of ground decisions, equipment faults, and cold-weather inexperience that set the flight on its course. The narrative asks how de-icing, taxi choices, and crew background combined to create a crisis the moment the plane left the ground.

Date: January 13, 1982
Location: Washington National Airport
Aircraft: Boeing 737
Flight: Air Florida Flight 90
Passengers aboard: 79

- Two de-icing workers used one truck; the glycol concentration delivered was 18% instead of the required 30% and the nozzle was non-standard.
- Pitot covers, static port covers, and engine inlet covers were not installed before the aircraft was signed off and cleared to taxi.
- The crew backed away from the gate using reverse thrust in continuous freezing precipitation, a maneuver cautioned against in icing conditions.
- The 737 waited in the taxi queue directly behind a DC-9 with engines running for 49 minutes while freezing precipitation continued.
- Captain Larry Wheaton and First Officer Roger Pettit had logged only ten combined winter takeoffs on the 737, despite substantial total flight hours.

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.]]>1302falsefullhttps://www.spreaker.com/episode/the-jackscrew-s-last-threads-stripped-as-fuel-ran-low-did-they-land--74771432
The jackscrew's last threads stripped as fuel ran low-did they land?

In this episode, we follow the timeline from takeoff through the crew’s first warning of a stuck horizontal stabilizer and the unfolding mechanical failure that instruments could not detect. The story traces the flight crew, the maintenance history, and the tiny component whose wear set the crisis in motion-could the pilots regain control before fuel constraints sealed their fate?

Date: January 31, 2000
Flight: Alaska Airlines Flight 261
Aircraft: MD-83, tail N963AS
People on board: 88
Duration from first warning to impact: less than 32 minutes

- Departure at 13:37 PST from Puerto Vallarta with clear weather and an unremarkable climb.
- Crew: Captain Ted Thompson (17,750+ flight hours, 4,000+ on MD-80) and First Officer William Tansky (8,060 hours on MD-80).
- Maintenance logs showed the acme nut had been checked and lubricated, though investigators later found no effective lubrication remained.
- At 15:49 PST the captain reported the horizontal stabilizer was stuck; checklists existed but could not explain why it stopped moving.
- Recovery from the ocean revealed a 22-inch hardened steel jackscrew with metal filaments-the last remnants of the acme nut’s threads.

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.]]>https://api.spreaker.com/episode/74771432Mon, 31 Aug 2026 17:38:19 +0000OBOMEDIA ENTERTAINMENTA worn jackscrew in an MD-83 stripped almost all its threads midflight above the Pacific as fuel ran low-did they land in time? The jackscrew's last threads stripped as fuel ran low-did they land? In this episode, we follow the timeline from...
The jackscrew's last threads stripped as fuel ran low-did they land?

In this episode, we follow the timeline from takeoff through the crew’s first warning of a stuck horizontal stabilizer and the unfolding mechanical failure that instruments could not detect. The story traces the flight crew, the maintenance history, and the tiny component whose wear set the crisis in motion-could the pilots regain control before fuel constraints sealed their fate?

Date: January 31, 2000
Flight: Alaska Airlines Flight 261
Aircraft: MD-83, tail N963AS
People on board: 88
Duration from first warning to impact: less than 32 minutes

- Departure at 13:37 PST from Puerto Vallarta with clear weather and an unremarkable climb.
- Crew: Captain Ted Thompson (17,750+ flight hours, 4,000+ on MD-80) and First Officer William Tansky (8,060 hours on MD-80).
- Maintenance logs showed the acme nut had been checked and lubricated, though investigators later found no effective lubrication remained.
- At 15:49 PST the captain reported the horizontal stabilizer was stuck; checklists existed but could not explain why it stopped moving.
- Recovery from the ocean revealed a 22-inch hardened steel jackscrew with metal filaments-the last remnants of the acme nut’s threads.

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.]]>986falsefullhttps://www.spreaker.com/episode/the-cessna-climbed-past-its-ceiling-and-burned-its-fuel-clock-dry--74771430
The Cessna climbed past its ceiling and burned its fuel-clock dry

In this episode, you’ll hear the known facts of a routine recruiting flight that became a baffling disappearance. We trace Bo Rein’s career and the flight’s odd timeline to ask what could have happened inside a cockpit that went radio‑silent.

Person: Bo Rein
Date: January 10, 1980
Location: departed Shreveport bound for Baton Rouge, intercepted over North Carolina, continued out over the Atlantic
Aircraft: Cessna 441 twin‑turboprop, certified ceiling ~35,000 ft, climbed to 41,600 ft
Status: no wreckage recovered, no bodies found

- Bo Rein, 34, had been LSU head coach for fewer than two months and was on a routine recruiting trip.
- Pilot Louis Benscotter prepared and departed on a flight of roughly forty minutes; a storm prompted a turn east to avoid weather.
- Air traffic control tracked the deviation and maintained contact until they lost the flight’s last transmission.
- The aircraft climbed steadily past its certified ceiling and leveled at 41,600 feet, continuing due east without descending or turning.
- Air National Guard fighters intercepted the plane about 1,000 miles off course and reported no one visible at the controls.

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.]]>https://api.spreaker.com/episode/74771430Mon, 31 Aug 2026 17:38:15 +0000OBOMEDIA ENTERTAINMENTA twin‑engine Cessna climbs beyond its ceiling with a college football coach aboard - did they make it in time? The Cessna climbed past its ceiling and burned its fuel-clock dry In this episode, you’ll hear the known facts of a routine...
The Cessna climbed past its ceiling and burned its fuel-clock dry

In this episode, you’ll hear the known facts of a routine recruiting flight that became a baffling disappearance. We trace Bo Rein’s career and the flight’s odd timeline to ask what could have happened inside a cockpit that went radio‑silent.

Person: Bo Rein
Date: January 10, 1980
Location: departed Shreveport bound for Baton Rouge, intercepted over North Carolina, continued out over the Atlantic
Aircraft: Cessna 441 twin‑turboprop, certified ceiling ~35,000 ft, climbed to 41,600 ft
Status: no wreckage recovered, no bodies found

- Bo Rein, 34, had been LSU head coach for fewer than two months and was on a routine recruiting trip.
- Pilot Louis Benscotter prepared and departed on a flight of roughly forty minutes; a storm prompted a turn east to avoid weather.
- Air traffic control tracked the deviation and maintained contact until they lost the flight’s last transmission.
- The aircraft climbed steadily past its certified ceiling and leveled at 41,600 feet, continuing due east without descending or turning.
- Air National Guard fighters intercepted the plane about 1,000 miles off course and reported no one visible at the controls.

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.]]>886falsefullhttps://www.spreaker.com/episode/the-mode-c-transponder-missing-the-piper-and-the-playground-that-waited--74771428
The Mode C transponder missing the Piper - and the playground that waited

In this episode, we present the documented record of the midair collision over southern California on August 31, 1986, and the chain of events that put two very different flights on a collision course. What decisions, rules, and equipment gaps converged above Cerritos and left a playground waiting below?

Date: August 31, 1986
Event: Midair collision above Cerritos, California
Aircraft: Piper PA‑28‑181 Archer (N4891F) and Aeromexico DC‑9 (XA‑JED)
People: 82 occupants on Aeromexico and Piper passengers/crew; 15 fatalities on the ground
System detail: Piper lacked a Mode C transponder and had not received TCA clearance

- William Kramer, age 53, piloted the Piper with 231 total flight hours on a planned Torrance-to-Big Bear scenic flight.
- The Piper lifted at ~11:40 AM and climbed toward the Los Angeles Terminal Control Area without an authorization required by that airspace.
- In 1986 small aircraft like the Piper were not legally required to carry Mode C altitude-reporting transponders.
- Aeromexico Flight 498 (DC‑9 XA‑JED) was on a standard, radio‑tracked final approach to LAX with an experienced crew in clear daylight.
- The Piper appeared as a radar blip with no automatic altitude data while controllers and the DC‑9 crew had no warning before the collision.

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.]]>https://api.spreaker.com/episode/74771428Mon, 31 Aug 2026 17:38:11 +0000OBOMEDIA ENTERTAINMENTA private Piper without a Mode C transponder climbs toward LA airspace while an Aeromexico DC-9 descends-did anyone see the altitude in time? The Mode C transponder missing the Piper - and the playground that waited In this episode, we present...
The Mode C transponder missing the Piper - and the playground that waited

In this episode, we present the documented record of the midair collision over southern California on August 31, 1986, and the chain of events that put two very different flights on a collision course. What decisions, rules, and equipment gaps converged above Cerritos and left a playground waiting below?

Date: August 31, 1986
Event: Midair collision above Cerritos, California
Aircraft: Piper PA‑28‑181 Archer (N4891F) and Aeromexico DC‑9 (XA‑JED)
People: 82 occupants on Aeromexico and Piper passengers/crew; 15 fatalities on the ground
System detail: Piper lacked a Mode C transponder and had not received TCA clearance

- William Kramer, age 53, piloted the Piper with 231 total flight hours on a planned Torrance-to-Big Bear scenic flight.
- The Piper lifted at ~11:40 AM and climbed toward the Los Angeles Terminal Control Area without an authorization required by that airspace.
- In 1986 small aircraft like the Piper were not legally required to carry Mode C altitude-reporting transponders.
- Aeromexico Flight 498 (DC‑9 XA‑JED) was on a standard, radio‑tracked final approach to LAX with an experienced crew in clear daylight.
- The Piper appeared as a radar blip with no automatic altitude data while controllers and the DC‑9 crew had no warning before the collision.

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.]]>911falsefullhttps://www.spreaker.com/episode/the-helicopter-that-climbed-for-a-gear-check-collided-before-they-could-land--74771427
The helicopter that climbed for a gear check collided before they could land

In this episode, we lay out the sequence of decisions and moments that put a Bell 412 and a Piper Aerostar into the same patch of Pennsylvania sky. We follow the pilots' choices, the aircraft movements, and the immediate aftermath that left questions about judgment and risk.

Date: April 4, 1991
Location: Lower Merion Township, Pennsylvania
Aircraft: Piper Aerostar; Bell 412 helicopter
Person: U.S. Senator H. John Heinz III
Event: Midair collision over Merion Elementary School

- At 11:52 a.m., the Piper Aerostar experienced landing gear uncertainty while airborne.
- Sun Company's Bell 412 helicopter was dispatched to visually inspect the Aerostar's landing gear.
- The two aircraft closed to the same altitude and location within seconds of each other.
- Both aircraft collided midair and crashed; wreckage fell onto Merion Elementary School.
- The NTSB attributed the accident to poor judgment by the pilots, with no sabotage or single mechanical failure identified.

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.]]>https://api.spreaker.com/episode/74771427Mon, 31 Aug 2026 17:38:06 +0000OBOMEDIA ENTERTAINMENTA helicopter climbs close to check a Piper Aerostar's balky landing gear over a schoolyard - did they make it in time? The helicopter that climbed for a gear check collided before they could land In this episode, we lay out the sequence of...
The helicopter that climbed for a gear check collided before they could land

In this episode, we lay out the sequence of decisions and moments that put a Bell 412 and a Piper Aerostar into the same patch of Pennsylvania sky. We follow the pilots' choices, the aircraft movements, and the immediate aftermath that left questions about judgment and risk.

Date: April 4, 1991
Location: Lower Merion Township, Pennsylvania
Aircraft: Piper Aerostar; Bell 412 helicopter
Person: U.S. Senator H. John Heinz III
Event: Midair collision over Merion Elementary School

- At 11:52 a.m., the Piper Aerostar experienced landing gear uncertainty while airborne.
- Sun Company's Bell 412 helicopter was dispatched to visually inspect the Aerostar's landing gear.
- The two aircraft closed to the same altitude and location within seconds of each other.
- Both aircraft collided midair and crashed; wreckage fell onto Merion Elementary School.
- The NTSB attributed the accident to poor judgment by the pilots, with no sabotage or single mechanical failure identified.

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.]]>846falsefullhttps://www.spreaker.com/episode/the-microburst-struck-the-approach-did-they-make-it--74771426
The microburst struck the approach - did they make it?

In this episode, we follow Flight 191’s final minutes as a veteran crew, functioning instruments, and a working radar face a thunderstorm phenomenon that no 1985 cockpit could detect. The episode traces what the pilots knew, what radios reported, and the gaps in information that became decisive.

Flight: Delta Flight 191
Date: August 2, 1985
Aircraft: Lockheed L-1011 TriStar
Location: Dallas/Fort Worth International Airport approach
People: Captain Edward Connors Jr.; First Officer Rudolph Price; Flight Engineer Nicholas Nassick

- At 17:43:45 the captain said, "I'd rather not go through it. I'd rather go around it one way or the other," captured by the cockpit voice recorder.
- Three minutes before impact the captain transmitted a calm, almost cheerful radio call while the aircraft was in rain.
- A Learjet 25 landed three miles ahead on the same approach, reported heavy rain and no severe hazards before Flight 191 followed.
- Instruments and airborne radar in 1985 showed thunderstorm cells and rain but could not detect the descending column of air known as a microburst.
- The aircraft struck a plowed farm field 6,336 feet north of the runway while traveling over 200 mph, during a storm that intensified in the minutes between the two landings.

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.]]>https://api.spreaker.com/episode/74771426Mon, 31 Aug 2026 17:38:03 +0000OBOMEDIA ENTERTAINMENTA seasoned TriStar on final approach into a storm at Dallas/Fort Worth encounters an invisible explosive downdraft - did they make it in time? The microburst struck the approach - did they make it? In this episode, we follow Flight 191’s final...
The microburst struck the approach - did they make it?

In this episode, we follow Flight 191’s final minutes as a veteran crew, functioning instruments, and a working radar face a thunderstorm phenomenon that no 1985 cockpit could detect. The episode traces what the pilots knew, what radios reported, and the gaps in information that became decisive.

Flight: Delta Flight 191
Date: August 2, 1985
Aircraft: Lockheed L-1011 TriStar
Location: Dallas/Fort Worth International Airport approach
People: Captain Edward Connors Jr.; First Officer Rudolph Price; Flight Engineer Nicholas Nassick

- At 17:43:45 the captain said, "I'd rather not go through it. I'd rather go around it one way or the other," captured by the cockpit voice recorder.
- Three minutes before impact the captain transmitted a calm, almost cheerful radio call while the aircraft was in rain.
- A Learjet 25 landed three miles ahead on the same approach, reported heavy rain and no severe hazards before Flight 191 followed.
- Instruments and airborne radar in 1985 showed thunderstorm cells and rain but could not detect the descending column of air known as a microburst.
- The aircraft struck a plowed farm field 6,336 feet north of the runway while traveling over 200 mph, during a storm that intensified in the minutes between the two landings.

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.]]>1333falsefullhttps://www.spreaker.com/episode/the-forklift-shifted-and-cracked-the-pylon-did-they-make-it-off-the-runway--74771424
The forklift shifted and cracked the pylon - did they make it off the runway?

In this episode, we follow the chain of routine choices and procedures that put a McDonnell Douglas DC‑10 back into service with an undetected structural crack. From a shortcut in a Tulsa maintenance hangar to the cockpit moments before takeoff, the episode asks what happens when inspections and experience collide with an invisible flaw.

Date: May 25, 1979
Aircraft: McDonnell Douglas DC‑10, registration N110AA
Location: O'Hare International Airport, runway 32R
Event: Engine/pylon removal and reinstallation preceded by combined lift using a forklift
Crew: Captain Walter H. Lux; First Officer James Dillard; Flight Engineer Alfred Udovich

- Maintenance in Tulsa removed the left engine and pylon together with a forklift instead of following McDonnell Douglas's separate‑removal procedure.
- A McDonnell Douglas representative warned that the combined removal carried "an element of risk" before the work proceeded.
- During the lift the forklift shifted and the pylon aft bulkhead flange absorbed an unintended stress, creating a microscopic crack.
- The damaged pylon was reinstalled, the aircraft passed standard checks, and N110AA flew scheduled routes for fifty‑seven days with the crack undetected.
- At 15:03:22 on May 25, 1979, Flight 191 advanced throttles and climbed to 325 feet before the last cockpit voice recorder entry.

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.]]>https://api.spreaker.com/episode/74771424Mon, 31 Aug 2026 17:37:59 +0000OBOMEDIA ENTERTAINMENTA DC‑10 with a hidden maintenance crack taxis at O'Hare for takeoff with 273 souls aboard - did they make it off the runway? The forklift shifted and cracked the pylon - did they make it off the runway? In this episode, we follow the chain of...
The forklift shifted and cracked the pylon - did they make it off the runway?

In this episode, we follow the chain of routine choices and procedures that put a McDonnell Douglas DC‑10 back into service with an undetected structural crack. From a shortcut in a Tulsa maintenance hangar to the cockpit moments before takeoff, the episode asks what happens when inspections and experience collide with an invisible flaw.

Date: May 25, 1979
Aircraft: McDonnell Douglas DC‑10, registration N110AA
Location: O'Hare International Airport, runway 32R
Event: Engine/pylon removal and reinstallation preceded by combined lift using a forklift
Crew: Captain Walter H. Lux; First Officer James Dillard; Flight Engineer Alfred Udovich

- Maintenance in Tulsa removed the left engine and pylon together with a forklift instead of following McDonnell Douglas's separate‑removal procedure.
- A McDonnell Douglas representative warned that the combined removal carried "an element of risk" before the work proceeded.
- During the lift the forklift shifted and the pylon aft bulkhead flange absorbed an unintended stress, creating a microscopic crack.
- The damaged pylon was reinstalled, the aircraft passed standard checks, and N110AA flew scheduled routes for fifty‑seven days with the crack undetected.
- At 15:03:22 on May 25, 1979, Flight 191 advanced throttles and climbed to 325 feet before the last cockpit voice recorder entry.

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.]]>1223falsefullhttps://www.spreaker.com/episode/the-flaps-command-that-started-the-go-around-did-they-make-it--74771423
The flaps command that started the go‑around - did they make it?

In this episode, we follow the final minutes of United Airlines Flight 585 and the crew's actions during a routine-to-ruin approach into Colorado Springs on March 3, 1991. The episode traces the flight path, cockpit sounds, weather and mechanical clues, asking what unfolded in those eight seconds and why the data that mattered was missing.

Date: March 3, 1991
Flight: United Airlines Flight 585
Aircraft: Boeing 737-291, N999UA
Location: Widefield Park / Colorado Springs Municipal Airport
People: Captain Harold Green; First Officer Patricia Eidson

- The approach was routine until 62 seconds after the last ATC call, when the aircraft rolled sharply to the right.
- Captain Green called for 15 degrees of flaps and advanced throttles-an immediate go‑around command recorded on the cockpit voice recorder.
- Weather that morning included northwest gusts up to 40 knots, active wind shear alerts, and nearby reports of large airspeed swings.
- The flight data recorder lacked a single critical parameter that investigators later identified as central to the puzzle.
- The same warning had occurred on the same aircraft days earlier but was not recognized, and the airplane remained in service.

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.]]>https://api.spreaker.com/episode/74771423Mon, 31 Aug 2026 17:37:55 +0000OBOMEDIA ENTERTAINMENTA United crew battles a turbulent approach as a Boeing 737 rolls hard - did their go‑around command reach the flaps in time? The flaps command that started the go‑around - did they make it? In this episode, we follow the final minutes of United...
The flaps command that started the go‑around - did they make it?

In this episode, we follow the final minutes of United Airlines Flight 585 and the crew's actions during a routine-to-ruin approach into Colorado Springs on March 3, 1991. The episode traces the flight path, cockpit sounds, weather and mechanical clues, asking what unfolded in those eight seconds and why the data that mattered was missing.

Date: March 3, 1991
Flight: United Airlines Flight 585
Aircraft: Boeing 737-291, N999UA
Location: Widefield Park / Colorado Springs Municipal Airport
People: Captain Harold Green; First Officer Patricia Eidson

- The approach was routine until 62 seconds after the last ATC call, when the aircraft rolled sharply to the right.
- Captain Green called for 15 degrees of flaps and advanced throttles-an immediate go‑around command recorded on the cockpit voice recorder.
- Weather that morning included northwest gusts up to 40 knots, active wind shear alerts, and nearby reports of large airspeed swings.
- The flight data recorder lacked a single critical parameter that investigators later identified as central to the puzzle.
- The same warning had occurred on the same aircraft days earlier but was not recognized, and the airplane remained in service.

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.]]>993falsefullhttps://www.spreaker.com/episode/the-cloud-top-upslope-erased-a-thousand-feet-did-they-get-out--74771420
The cloud‑top upslope erased a thousand feet - did they get out?

In this episode, we follow two airliners descending into layered cloud over Carmel, New York, and the split‑second visual illusion that erased a thousand feet of separation. The episode traces the crews, the aircraft, and the moments of decision that preceded a midair collision - what choices were made as the sky turned against them?

Date: December 4, 1965
Location: Carmel, New York
Event: Midair collision above cloud layer
Aircraft 1: Lockheed L-1049C Super Constellation, N6218C
Aircraft 2: Boeing 707-131B, N748TW

- Eastern Air Lines Flight 853 departed Boston for Newark with 49 passengers and a crew led by Captain Charles J. White.
- TWA Flight 42 flew from San Francisco toward New York with 51 passengers and Captain Thomas Carroll at the controls.
- Both aircraft were descending through a cloud layer between 10,000 and 11,000 feet, giving the legal 1,000‑foot separation on paper.
- As Eastern broke through the cloud, a rising cloud‑top created an optical illusion that made the Boeing appear level with the Constellation.
- A shouted warning from First Officer Roger Holt occurred the instant the illusion formed, triggering the crews’ split‑second reactions.

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.]]>https://api.spreaker.com/episode/74771420Mon, 31 Aug 2026 17:37:52 +0000OBOMEDIA ENTERTAINMENTA thousand feet of mandated separation vanishes when a rising cloud-top makes a Boeing look level with a Constellation - did they make it out in time? The cloud‑top upslope erased a thousand feet - did they get out? In this episode, we follow...
The cloud‑top upslope erased a thousand feet - did they get out?

In this episode, we follow two airliners descending into layered cloud over Carmel, New York, and the split‑second visual illusion that erased a thousand feet of separation. The episode traces the crews, the aircraft, and the moments of decision that preceded a midair collision - what choices were made as the sky turned against them?

Date: December 4, 1965
Location: Carmel, New York
Event: Midair collision above cloud layer
Aircraft 1: Lockheed L-1049C Super Constellation, N6218C
Aircraft 2: Boeing 707-131B, N748TW

- Eastern Air Lines Flight 853 departed Boston for Newark with 49 passengers and a crew led by Captain Charles J. White.
- TWA Flight 42 flew from San Francisco toward New York with 51 passengers and Captain Thomas Carroll at the controls.
- Both aircraft were descending through a cloud layer between 10,000 and 11,000 feet, giving the legal 1,000‑foot separation on paper.
- As Eastern broke through the cloud, a rising cloud‑top created an optical illusion that made the Boeing appear level with the Constellation.
- A shouted warning from First Officer Roger Holt occurred the instant the illusion formed, triggering the crews’ split‑second reactions.

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.]]>1323falsefullhttps://www.spreaker.com/episode/the-thirty-five-thousand-foot-altitude-put-them-on-a-collision-clock--74771419
The thirty‑five‑thousand‑foot altitude put them on a collision clock

In this episode, we lay out the sequence of a midair disaster: two military transports, their missions and crews, and the safety systems that should have kept them apart. As the story unfolds, one question hangs over every decision and omission: could the documented failures alone have set a collision in motion?

Date: 13 September 1997
Location: South Atlantic, 65 nautical miles off Namibia
Aircraft: C-141B Starlifter (REACH 4201); Tupolev Tu-154M (GAF 74)
Persons on board: 33 (combined)
Independent witness: bright flash recorded by a U.S. military satellite

- A U.S. C-141B on a humanitarian return leg departed Windhoek at 14:11 UTC bound for Ascension Island, cruising filed at 35,000 ft with nine aboard.
- A German Air Force Tu-154M flew from Cologne via Niamey to Windhoek en route to Cape Town, filed to cruise at 35,000 ft with 24 aboard including marines and spouses.
- The semicircular rule assigned 35,000 ft to northbound traffic; GAF 74 was southbound yet occupied that same even altitude, creating a head-on intercept.
- Neither aircraft had airborne collision avoidance systems installed despite recommendations and procurement lists noting the technology for years.
- The only independent confirmation of the impact was a satellite-detected flash; no radar tracked either plane at the collision moment and no controller warned the crews.

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.]]>https://api.spreaker.com/episode/74771419Mon, 31 Aug 2026 17:37:47 +0000OBOMEDIA ENTERTAINMENTA humanitarian C-141 and a German Tu-154 converged at 35,000 ft over the South Atlantic with no traffic warnings-did anyone make it in time? The thirty‑five‑thousand‑foot altitude put them on a collision clock In this episode, we lay out the...
The thirty‑five‑thousand‑foot altitude put them on a collision clock

In this episode, we lay out the sequence of a midair disaster: two military transports, their missions and crews, and the safety systems that should have kept them apart. As the story unfolds, one question hangs over every decision and omission: could the documented failures alone have set a collision in motion?

Date: 13 September 1997
Location: South Atlantic, 65 nautical miles off Namibia
Aircraft: C-141B Starlifter (REACH 4201); Tupolev Tu-154M (GAF 74)
Persons on board: 33 (combined)
Independent witness: bright flash recorded by a U.S. military satellite

- A U.S. C-141B on a humanitarian return leg departed Windhoek at 14:11 UTC bound for Ascension Island, cruising filed at 35,000 ft with nine aboard.
- A German Air Force Tu-154M flew from Cologne via Niamey to Windhoek en route to Cape Town, filed to cruise at 35,000 ft with 24 aboard including marines and spouses.
- The semicircular rule assigned 35,000 ft to northbound traffic; GAF 74 was southbound yet occupied that same even altitude, creating a head-on intercept.
- Neither aircraft had airborne collision avoidance systems installed despite recommendations and procurement lists noting the technology for years.
- The only independent confirmation of the impact was a satellite-detected flash; no radar tracked either plane at the collision moment and no controller warned the crews.

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.]]>962falsefullhttps://www.spreaker.com/episode/the-ninety-degree-shaft-step-in-engine-two-fractured-before-they-reached-runway--74771415
The ninety‑degree shaft step in engine two fractured before they reached runway

In this episode we lay out the timeline and the hardware that preceded the March 14, 1980 crash of LOT Polish Airlines Flight 007, tracking the aircraft, its passengers, and the maintenance decisions that kept it flying despite known engine anomalies. What sequence of inspections, repairs, and cost-driven choices led to the fractured shaft in engine two?

Date: March 14, 1980
Aircraft: Ilyushin Il-62 (SP-LAA, Mikołaj Kopernik)
Flight: LOT Polish Airlines Flight 007
People aboard: 87
Engine model: NK-8 turbofan

- The aircraft clipped a tree and crashed into a frozen moat 950 meters from the runway threshold at 11:14:35, with wreckage 100 meters from the nearest apartment block.
- Engine number two had been rotated through three airframes, repaired in the Soviet Union and Poland, and accumulated 700 hours of marginal vibration on SP-LAA before the accident.
- Engine one showed a deformed turbine blade cleared as within tolerance the day before; engine three had 8,200 hours since overhaul versus a 5,000-hour manufacturer limit.
- LOT routinely stretched overhaul intervals and refueled in Poland to save hard currency, practices that increased engine wear and were known within the airline.
- Investigators later identified a ninety-degree step at a diameter change point inside engine two’s shaft as a geometric stress concentrator associated with the fracture.

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.]]>https://api.spreaker.com/episode/74771415Mon, 31 Aug 2026 17:37:43 +0000OBOMEDIA ENTERTAINMENTA Transatlantic Il‑62 is seconds from the runway with landing gear down when a hidden engine defect fractures-did they make it in time? The ninety‑degree shaft step in engine two fractured before they reached runway In this episode we lay out...
The ninety‑degree shaft step in engine two fractured before they reached runway

In this episode we lay out the timeline and the hardware that preceded the March 14, 1980 crash of LOT Polish Airlines Flight 007, tracking the aircraft, its passengers, and the maintenance decisions that kept it flying despite known engine anomalies. What sequence of inspections, repairs, and cost-driven choices led to the fractured shaft in engine two?

Date: March 14, 1980
Aircraft: Ilyushin Il-62 (SP-LAA, Mikołaj Kopernik)
Flight: LOT Polish Airlines Flight 007
People aboard: 87
Engine model: NK-8 turbofan

- The aircraft clipped a tree and crashed into a frozen moat 950 meters from the runway threshold at 11:14:35, with wreckage 100 meters from the nearest apartment block.
- Engine number two had been rotated through three airframes, repaired in the Soviet Union and Poland, and accumulated 700 hours of marginal vibration on SP-LAA before the accident.
- Engine one showed a deformed turbine blade cleared as within tolerance the day before; engine three had 8,200 hours since overhaul versus a 5,000-hour manufacturer limit.
- LOT routinely stretched overhaul intervals and refueled in Poland to save hard currency, practices that increased engine wear and were known within the airline.
- Investigators later identified a ninety-degree step at a diameter change point inside engine two’s shaft as a geometric stress concentrator associated with the fracture.

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.]]>847falsefullhttps://www.spreaker.com/episode/the-weather-bulletin-that-never-reached-them-did-they-climb-out-in-time--74771412
The weather bulletin that never reached them: did they climb out in time?

In this episode, we follow the minutes before and after Pan Am Flight 759's departure from New Orleans on July 9, 1982, focusing on what the crew knew, what they were not told, and the procedural gap that may have mattered. The episode asks whether a missing weather alert changed everything.

Date: July 9, 1982
Flight: Pan Am Flight 759 (Clipper Defiance, N4737)
Aircraft: Boeing 727
Crew experience: ~37,000 combined flight hours
Location: New Orleans International Airport (Runway 10)

- The flight departed New Orleans at 16:07:57 with First Officer Donald G. Pierce flying and Captain Kenneth L. McCullers monitoring.
- The crew’s weather briefing was two hours old; the airport broadcast a wind shear alert during the takeoff roll.
- Airport protocol required hourly weather recordings but had no procedure to actively notify crews when a new recording superseded their briefing.
- The cockpit voice recorder captured only 64 seconds from liftoff to impact, containing voices, engines, and no evidence the crew heard the local alert.
- Investigators found no single catastrophic failure on paper; they identified a procedural gap in how updated weather information was communicated.

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.]]>https://api.spreaker.com/episode/74771412Mon, 31 Aug 2026 17:37:38 +0000OBOMEDIA ENTERTAINMENTA seasoned Pan Am crew climbs out of New Orleans into gusty skies unaware a wind shear bulletin never reached them - did they make it in time? The weather bulletin that never reached them: did they climb out in time? In this episode, we follow...
The weather bulletin that never reached them: did they climb out in time?

In this episode, we follow the minutes before and after Pan Am Flight 759's departure from New Orleans on July 9, 1982, focusing on what the crew knew, what they were not told, and the procedural gap that may have mattered. The episode asks whether a missing weather alert changed everything.

Date: July 9, 1982
Flight: Pan Am Flight 759 (Clipper Defiance, N4737)
Aircraft: Boeing 727
Crew experience: ~37,000 combined flight hours
Location: New Orleans International Airport (Runway 10)

- The flight departed New Orleans at 16:07:57 with First Officer Donald G. Pierce flying and Captain Kenneth L. McCullers monitoring.
- The crew’s weather briefing was two hours old; the airport broadcast a wind shear alert during the takeoff roll.
- Airport protocol required hourly weather recordings but had no procedure to actively notify crews when a new recording superseded their briefing.
- The cockpit voice recorder captured only 64 seconds from liftoff to impact, containing voices, engines, and no evidence the crew heard the local alert.
- Investigators found no single catastrophic failure on paper; they identified a procedural gap in how updated weather information was communicated.

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.]]>888falsefullhttps://www.spreaker.com/episode/the-two-percent-ice-ridge-broke-the-atr-s-lift-did-they-make-it--74771411
The two-percent ice ridge broke the ATR's lift - did they make it?

In this episode, we follow the last fifteen critical seconds before a commuter ATR lost control over Newton County, Indiana, on October 31, 1994. The narrative traces crew actions, the aircraft’s deice system, and the unnoticed two-percent ice ridge that changed everything-did they catch it in time?

Date: October 31, 1994
Location: Newton County, Indiana
Aircraft: ATR registered N401AM
Flight: American Eagle Flight 4184
People on board: 68

- The crew activated the Level Three deice system and set prop RPM to 86% during descent as standard cold-weather procedure.
- Deice boots covered only 5-7% of the wing chord while a hard ice ridge was forming at about 9% chord-two percent beyond the boots’ reach.
- The flight entered a holding pattern at LUCIT from 15:18, expecting further clearance and orbiting in icing conditions for over thirty minutes.
- At 15:33 the captain reported the airplane “wallowing” and the first officer extended flaps to 15° to regain lift; the airplane initially steadied.
- Between 15:48 and 15:54 crew notes record ice accumulation and routine checks; the critical loss of control occurred within the next fifteen seconds.

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.]]>https://api.spreaker.com/episode/74771411Mon, 31 Aug 2026 17:37:35 +0000OBOMEDIA ENTERTAINMENTAn ATR on approach to Indiana accumulates unexpected ice-can the crew regain control before the stall takes them? The two-percent ice ridge broke the ATR's lift - did they make it? In this episode, we follow the last fifteen critical seconds...
The two-percent ice ridge broke the ATR's lift - did they make it?

In this episode, we follow the last fifteen critical seconds before a commuter ATR lost control over Newton County, Indiana, on October 31, 1994. The narrative traces crew actions, the aircraft’s deice system, and the unnoticed two-percent ice ridge that changed everything-did they catch it in time?

Date: October 31, 1994
Location: Newton County, Indiana
Aircraft: ATR registered N401AM
Flight: American Eagle Flight 4184
People on board: 68

- The crew activated the Level Three deice system and set prop RPM to 86% during descent as standard cold-weather procedure.
- Deice boots covered only 5-7% of the wing chord while a hard ice ridge was forming at about 9% chord-two percent beyond the boots’ reach.
- The flight entered a holding pattern at LUCIT from 15:18, expecting further clearance and orbiting in icing conditions for over thirty minutes.
- At 15:33 the captain reported the airplane “wallowing” and the first officer extended flaps to 15° to regain lift; the airplane initially steadied.
- Between 15:48 and 15:54 crew notes record ice accumulation and routine checks; the critical loss of control occurred within the next fifteen seconds.

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.]]>1350falsefullhttps://www.spreaker.com/episode/when-sky-turned-silent-the-dual-engine-disaster-over-georgia--74771409
When Sky Turned Silent: The Dual-Engine Disaster Over Georgia

In this episode, we lay out the sequence that led a Southern Airways DC-9 from routine flight to catastrophe over Paulding County, Georgia. We track the decisions, the instruments, and the gaps in procedures that set the crew on a course into the storm and ask whether different information or actions could have changed what happened.

Date: April 4, 1977
Aircraft: Douglas DC-9-31
Person: Captain William W. McKenzie; First Officer Lyman W. Keele Jr.
Location: Paulding County, Georgia
Event: Dual engine flameout after penetrating convective weather

- Preflight briefing noted embedded thunderstorms and possible tornadic activity, but no updated dispatch weather was sent before the afternoon departure.
- The DC-9’s cockpit weather radar was functioning normally and displayed an attenuated return that read as an apparent “corridor” through the squall line.
- Air traffic control cleared Flight 242 toward the Rome, Georgia VOR, directing the aircraft toward the area of peak convective intensity.
- The crew descended from 17,000 to 14,000 feet, steering into the radar-indicated gap that the instruments suggested was safe.
- Hail shattered the windshield and was ingested into both Pratt & Whitney tail-mounted engines, causing simultaneous compressor failure and flameout.

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.]]>https://api.spreaker.com/episode/74771409Mon, 31 Aug 2026 17:37:31 +0000OBOMEDIA ENTERTAINMENTA seasoned DC-9 crew flies toward a radar corridor over Georgia and, trusting the storm radar, suddenly lose both engines - did they make it in time? When Sky Turned Silent: The Dual-Engine Disaster Over Georgia In this episode, we lay out the...
When Sky Turned Silent: The Dual-Engine Disaster Over Georgia

In this episode, we lay out the sequence that led a Southern Airways DC-9 from routine flight to catastrophe over Paulding County, Georgia. We track the decisions, the instruments, and the gaps in procedures that set the crew on a course into the storm and ask whether different information or actions could have changed what happened.

Date: April 4, 1977
Aircraft: Douglas DC-9-31
Person: Captain William W. McKenzie; First Officer Lyman W. Keele Jr.
Location: Paulding County, Georgia
Event: Dual engine flameout after penetrating convective weather

- Preflight briefing noted embedded thunderstorms and possible tornadic activity, but no updated dispatch weather was sent before the afternoon departure.
- The DC-9’s cockpit weather radar was functioning normally and displayed an attenuated return that read as an apparent “corridor” through the squall line.
- Air traffic control cleared Flight 242 toward the Rome, Georgia VOR, directing the aircraft toward the area of peak convective intensity.
- The crew descended from 17,000 to 14,000 feet, steering into the radar-indicated gap that the instruments suggested was safe.
- Hail shattered the windshield and was ingested into both Pratt & Whitney tail-mounted engines, causing simultaneous compressor failure and flameout.

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.]]>919falsefullhttps://www.spreaker.com/episode/the-refusal-of-ils-at-22-28-doomed-their-descent-on-mount-somma--74771408
The refusal of ILS at 22:28 doomed their descent on Mount Somma

In this episode, we follow Alitalia Flight 45's final minutes: the crew's routine night approach, the weather briefing they received, and the decision to decline instrument guidance. How did familiarity and confidence shape the choices made before the aircraft struck the mountain?

Aircraft: Vickers Viscount I-LAKE
Date: March 28, 1964
Person: Captain Pasquale Umana
Location: Mount Somma / Naples approach
Passengers aboard: 45

- Flight delayed in Rome for a maintenance check and weather, then pushed back at 22:10 toward Naples.
- Crew received a weather bulletin describing cloud layers, six kilometres visibility, and southerly winds before departure.
- At 22:28 Naples approach read the same weather and offered the ILS approach to runway 24.
- Captain Umana replied in Italian that they would not use the ILS because "we can see it."
- Two minutes after declining instrument guidance, the aircraft struck Mount Somma at 610 metres above sea level.

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.]]>https://api.spreaker.com/episode/74771408Mon, 31 Aug 2026 17:37:27 +0000OBOMEDIA ENTERTAINMENTA veteran captain refuses the ILS as his Viscount descends toward Naples at night; can visual confidence beat the unseen ridge of Mount Somma? The refusal of ILS at 22:28 doomed their descent on Mount Somma In this episode, we follow Alitalia...
The refusal of ILS at 22:28 doomed their descent on Mount Somma

In this episode, we follow Alitalia Flight 45's final minutes: the crew's routine night approach, the weather briefing they received, and the decision to decline instrument guidance. How did familiarity and confidence shape the choices made before the aircraft struck the mountain?

Aircraft: Vickers Viscount I-LAKE
Date: March 28, 1964
Person: Captain Pasquale Umana
Location: Mount Somma / Naples approach
Passengers aboard: 45

- Flight delayed in Rome for a maintenance check and weather, then pushed back at 22:10 toward Naples.
- Crew received a weather bulletin describing cloud layers, six kilometres visibility, and southerly winds before departure.
- At 22:28 Naples approach read the same weather and offered the ILS approach to runway 24.
- Captain Umana replied in Italian that they would not use the ILS because "we can see it."
- Two minutes after declining instrument guidance, the aircraft struck Mount Somma at 610 metres above sea level.

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.]]>1029falsefullhttps://www.spreaker.com/episode/they-had-eight-seconds-why-the-737-s-rudder-turned-against-its-pilots--74771406
They Had Eight Seconds: Why the 737's Rudder Turned Against Its Pilots

In this episode, we follow the final twenty minutes of United Flight 585 from departure to a violent eight-second crash and the baffling gap left by investigators. What happened during that approach, and why did a routine landing turn into an uncontrollable roll?

Date: March 3, 1991
Flight: United Airlines Flight 585
Aircraft: Boeing 737-291, N999UA, s/n 22742
Crew: Captain Harold Green (9,902 UA hours; 1,732 on 737), First Officer Patricia Eidson (3,903 total hours; 1,077 on 737)
Condition: Low-level wind shear advisory; prior uncommanded rolls reported six and two days earlier

- Departed Denver Stapleton at 09:23 MST on a short leg to Colorado Springs scheduled for 09:46.
- Cockpit voice recorder captured crew noting wind shear and joking “Sounds adventurous” before final approach.
- FDR showed normal accelerations and 155 kt airspeed; standard 20° bank to align with runway at 09:42.
- At 09:43:33 the aircraft rolled right at ~5°/sec, nose dropped and control inputs could not stop the rapid roll.
- NTSB investigators spent two years yet initially stated they could not determine a probable cause.

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.]]>https://api.spreaker.com/episode/74771406Mon, 31 Aug 2026 17:37:23 +0000OBOMEDIA ENTERTAINMENTA United Airlines 737 on final approach to Colorado Springs suddenly rolls hard right and crashes in eight seconds - did the rudder betray its pilots? They Had Eight Seconds: Why the 737's Rudder Turned Against Its Pilots In this episode, we...
They Had Eight Seconds: Why the 737's Rudder Turned Against Its Pilots

In this episode, we follow the final twenty minutes of United Flight 585 from departure to a violent eight-second crash and the baffling gap left by investigators. What happened during that approach, and why did a routine landing turn into an uncontrollable roll?

Date: March 3, 1991
Flight: United Airlines Flight 585
Aircraft: Boeing 737-291, N999UA, s/n 22742
Crew: Captain Harold Green (9,902 UA hours; 1,732 on 737), First Officer Patricia Eidson (3,903 total hours; 1,077 on 737)
Condition: Low-level wind shear advisory; prior uncommanded rolls reported six and two days earlier

- Departed Denver Stapleton at 09:23 MST on a short leg to Colorado Springs scheduled for 09:46.
- Cockpit voice recorder captured crew noting wind shear and joking “Sounds adventurous” before final approach.
- FDR showed normal accelerations and 155 kt airspeed; standard 20° bank to align with runway at 09:42.
- At 09:43:33 the aircraft rolled right at ~5°/sec, nose dropped and control inputs could not stop the rapid roll.
- NTSB investigators spent two years yet initially stated they could not determine a probable cause.

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.]]>897falsefullhttps://www.spreaker.com/episode/the-twenty-one-degree-turn-that-outpaced-their-descent-time--74771403
The twenty‑one‑degree turn that outpaced their descent time

In this episode, we follow the final sixteen silent minutes of Merpati Nusantara Airlines Flight 5601 and the decisions that led a two‑year‑old CN‑235 to stray from its intended heading. We trace the crew’s request to switch to visual flight rules, their routing through convective cells, and the moment the recorded heading diverged by twenty‑one degrees-what could that deviation mean for those on board?

Aircraft: CASA/IPTN CN-235-10, registration N.13
Date: October 18, 1992
Flight: Merpati Nusantara Airlines Flight 5601
Persons: Captain Fierda Basaria Panggabean (PF), First Officer Adnan S. Paago (FO)
Location: West Java approach to Husein Sastranegara International Airport

- Departed Semarang at 13:05 for a routine regional flight expected to arrive Bandung ~14:30.
- Aircraft was two years old with >2,000 flight hours and maintenance logs indicating airworthiness.
- At 13:35 the crew reported at 12,500 ft and ready for approach; ATC advised holding altitude due to convective activity.
- At 13:40 the crew requested and received a change from IFR to VFR, then began threading between cumulonimbus cells toward Tasikmalaya and Garut.
- Last transmission at 13:42 reported descent to 8,500 ft; the subsequent 16 minutes were silent while the recorded heading differed by 21 degrees from the planned track.

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.]]>https://api.spreaker.com/episode/74771403Mon, 31 Aug 2026 17:37:18 +0000OBOMEDIA ENTERTAINMENTA routine regional flight over West Java turns twenty-one degrees off course into worsening weather-did the crew see the mountain in time? The twenty‑one‑degree turn that outpaced their descent time In this episode, we follow the final sixteen...
The twenty‑one‑degree turn that outpaced their descent time

In this episode, we follow the final sixteen silent minutes of Merpati Nusantara Airlines Flight 5601 and the decisions that led a two‑year‑old CN‑235 to stray from its intended heading. We trace the crew’s request to switch to visual flight rules, their routing through convective cells, and the moment the recorded heading diverged by twenty‑one degrees-what could that deviation mean for those on board?

Aircraft: CASA/IPTN CN-235-10, registration N.13
Date: October 18, 1992
Flight: Merpati Nusantara Airlines Flight 5601
Persons: Captain Fierda Basaria Panggabean (PF), First Officer Adnan S. Paago (FO)
Location: West Java approach to Husein Sastranegara International Airport

- Departed Semarang at 13:05 for a routine regional flight expected to arrive Bandung ~14:30.
- Aircraft was two years old with >2,000 flight hours and maintenance logs indicating airworthiness.
- At 13:35 the crew reported at 12,500 ft and ready for approach; ATC advised holding altitude due to convective activity.
- At 13:40 the crew requested and received a change from IFR to VFR, then began threading between cumulonimbus cells toward Tasikmalaya and Garut.
- Last transmission at 13:42 reported descent to 8,500 ft; the subsequent 16 minutes were silent while the recorded heading differed by 21 degrees from the planned track.

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.]]>729falsefullhttps://www.spreaker.com/episode/the-ils-course-correction-that-drew-them-below-the-runway-just-before-midnight--74771401
The ILS course correction that drew them below the runway just before midnight

In this episode, we follow Flight 1808’s final approach to Auburn-Lewiston Municipal Airport and the chain of routine decisions that converged on a single eight-second descent. The story traces the flight path, weather, and cockpit conditions that left no audio or flight-data record - and asks how such a routine correction could go so wrong.

Person: Samantha Smith
Aircraft: Beechcraft Model 99
Event: Flight 1808 approach to Auburn-Lewiston Municipal Airport
Date: August 25, 1985
Location: Four thousand and seven feet from treeline to runway end

- Flight 1808 carried eight people after a cancelled earlier flight folded passengers onto the northbound leg.
- A flag stop at Auburn was added, and one booked passenger failed to board, leaving an empty seat.
- Weather at Auburn just before 22:00: ceiling 300 ft, visibility 1 mile, light drizzle, altimeter 30.24 inHg.
- Radar showed the aircraft drifting east of the ILS course for Runway 4; Portland ATC issued a heading correction to 340°.
- The aircraft had no cockpit voice recorder or flight data recorder, forcing investigators to rely on radar, transponder returns, and wreckage.

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.]]>https://api.spreaker.com/episode/74771401Mon, 31 Aug 2026 17:37:15 +0000OBOMEDIA ENTERTAINMENTA turboprop drifts off the ILS on a foggy Maine night; can the crew correct course and make the runway before they sink into the trees? The ILS course correction that drew them below the runway just before midnight In this episode, we follow...
The ILS course correction that drew them below the runway just before midnight

In this episode, we follow Flight 1808’s final approach to Auburn-Lewiston Municipal Airport and the chain of routine decisions that converged on a single eight-second descent. The story traces the flight path, weather, and cockpit conditions that left no audio or flight-data record - and asks how such a routine correction could go so wrong.

Person: Samantha Smith
Aircraft: Beechcraft Model 99
Event: Flight 1808 approach to Auburn-Lewiston Municipal Airport
Date: August 25, 1985
Location: Four thousand and seven feet from treeline to runway end

- Flight 1808 carried eight people after a cancelled earlier flight folded passengers onto the northbound leg.
- A flag stop at Auburn was added, and one booked passenger failed to board, leaving an empty seat.
- Weather at Auburn just before 22:00: ceiling 300 ft, visibility 1 mile, light drizzle, altimeter 30.24 inHg.
- Radar showed the aircraft drifting east of the ILS course for Runway 4; Portland ATC issued a heading correction to 340°.
- The aircraft had no cockpit voice recorder or flight data recorder, forcing investigators to rely on radar, transponder returns, and wreckage.

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.]]>861falsefullhttps://www.spreaker.com/episode/concrete-death-how-muan-s-barrier-turned-a-bird-strike-fatal--74771400
Concrete Death: How Muan's Barrier Turned a Bird Strike Fatal

In this episode, we lay out the sequence of decisions, warnings and equipment failures that met Flight 2216 on final approach to Muan International Airport. We trace the crew, the airport’s ignored safety notes, and the minutes that followed the bird strike to ask what went wrong and why.

Date: December 29, 2024
Flight: Jeju Air Flight 2216
Aircraft: Boeing 737-800 (registration HL8088)
Location: Muan International Airport, South Jeolla Province, South Korea
Casualties aboard: 181 people (2 survivors)

- Seven months before the crash the airport manual warned the barrier was too close to the runway and no relocation occurred.
- Muan had the highest bird-strike rate among Korea’s regional airports and regulations required four bird-deterrence staff; only one was on duty that morning.
- Deterrent systems (sound cannons, lasers, warning lights) were not operating because runway extension work delayed their deployment.
- ATC issued a bird-strike warning at 08:57; investigators later identified 17 Baikal teal specimens recovered from the engines.
- Cockpit and flight data recorders cut out at 08:58:50, and the crew declared a mayday six seconds later, starting a four-minute, seven-second sequence until the aircraft stopped.

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.]]>https://api.spreaker.com/episode/74771400Mon, 31 Aug 2026 17:37:11 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 approaches Muan International amid known bird strike risk and a concrete barrier too close to the runway - did they make it in time? Concrete Death: How Muan's Barrier Turned a Bird Strike Fatal In this episode, we lay out the...
Concrete Death: How Muan's Barrier Turned a Bird Strike Fatal

In this episode, we lay out the sequence of decisions, warnings and equipment failures that met Flight 2216 on final approach to Muan International Airport. We trace the crew, the airport’s ignored safety notes, and the minutes that followed the bird strike to ask what went wrong and why.

Date: December 29, 2024
Flight: Jeju Air Flight 2216
Aircraft: Boeing 737-800 (registration HL8088)
Location: Muan International Airport, South Jeolla Province, South Korea
Casualties aboard: 181 people (2 survivors)

- Seven months before the crash the airport manual warned the barrier was too close to the runway and no relocation occurred.
- Muan had the highest bird-strike rate among Korea’s regional airports and regulations required four bird-deterrence staff; only one was on duty that morning.
- Deterrent systems (sound cannons, lasers, warning lights) were not operating because runway extension work delayed their deployment.
- ATC issued a bird-strike warning at 08:57; investigators later identified 17 Baikal teal specimens recovered from the engines.
- Cockpit and flight data recorders cut out at 08:58:50, and the crew declared a mayday six seconds later, starting a four-minute, seven-second sequence until the aircraft stopped.

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.]]>831falsefullhttps://www.spreaker.com/episode/the-broken-flight-recorder-cost-them-the-final-seconds-to-save-45-lives--74771399
The broken flight recorder cost them the final seconds to save 45 lives

In this episode, we follow the routine Chicago-to-Omaha leg that became a catastrophic approach to Midway, and the painstaking reconstruction after the primary flight data source failed. How did a broken recorder, an ARTS-III radar fifty-five miles away, and a nonprecision localizer approach combine to shape the last ninety seconds?

Date: December 8, 1972
Flight: United Airlines Lines Flight 553
Aircraft: Boeing 737, registration N9031U, “City of Lincoln”
Location: West Seventieth Place, Chicago (approach to Midway Airport)
Passengers: 55 boarded; 45 killed

- Crew experience: Captain Wendell Lewis Whitehouse (≈18,000 hours, ~2,400 on 737), First Officer Walter O. Coble (≈10,600 hours), Second Officer Barry J. Elder (≈2,700 hours).
- Known mechanical failure: flight data recorder suffered a mechanical failure before departure from Washington; crew aware, Chicago approach control was not.
- Radar backup: ARTS-III radar at O’Hare logged transponder returns for the flight and provided time-stamped data fifty-five miles away.
- Approach profile: nonprecision localizer to runway 31L at Midway requiring manual descent discipline with runway visual only below ~500-600 feet in overcast conditions.
- Investigative evidence: transponder returns were matched to Boeing performance tables and cockpit voice recordings to rebuild the final eight minutes without the flight data recorder.

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.]]>https://api.spreaker.com/episode/74771399Mon, 31 Aug 2026 17:37:07 +0000OBOMEDIA ENTERTAINMENTA United Airlines Boeing 737 approaches Midway with a failed flight recorder and 45 lives at stake - did they make it in time? The broken flight recorder cost them the final seconds to save 45 lives In this episode, we follow the routine...
The broken flight recorder cost them the final seconds to save 45 lives

In this episode, we follow the routine Chicago-to-Omaha leg that became a catastrophic approach to Midway, and the painstaking reconstruction after the primary flight data source failed. How did a broken recorder, an ARTS-III radar fifty-five miles away, and a nonprecision localizer approach combine to shape the last ninety seconds?

Date: December 8, 1972
Flight: United Airlines Lines Flight 553
Aircraft: Boeing 737, registration N9031U, “City of Lincoln”
Location: West Seventieth Place, Chicago (approach to Midway Airport)
Passengers: 55 boarded; 45 killed

- Crew experience: Captain Wendell Lewis Whitehouse (≈18,000 hours, ~2,400 on 737), First Officer Walter O. Coble (≈10,600 hours), Second Officer Barry J. Elder (≈2,700 hours).
- Known mechanical failure: flight data recorder suffered a mechanical failure before departure from Washington; crew aware, Chicago approach control was not.
- Radar backup: ARTS-III radar at O’Hare logged transponder returns for the flight and provided time-stamped data fifty-five miles away.
- Approach profile: nonprecision localizer to runway 31L at Midway requiring manual descent discipline with runway visual only below ~500-600 feet in overcast conditions.
- Investigative evidence: transponder returns were matched to Boeing performance tables and cockpit voice recordings to rebuild the final eight minutes without the flight data recorder.

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.]]>1006falsefullhttps://www.spreaker.com/episode/the-taws-switch-silenced-the-cockpit-and-cost-them-the-runway-time--74771396
The TAWS switch silenced the cockpit and cost them the runway-time

In this episode, we follow Tara Air Flight 197’s fifteen-minute climb from Pokhara toward Jomsom through the narrow Kali Gandaki gorge. The podcast covers the flight’s equipment, crew makeup, weather and procedural context to ask whether key decisions and a silenced Terrain Awareness and Warning System sealed the aircraft’s fate.

Date: May 29, 2022
Flight: Tara Air Flight 197
Aircraft: DHC-6 Twin Otter, registration 9N-AET
Passengers on board: 22 (19 passengers, 3 crew)
Route: Pokhara to Jomsom, Kali Gandaki gorge

- The aircraft took off at 09:55 for a scheduled 20-minute hop through a VFR-only corridor known for sudden cloud and turbulence.
- The cockpit carried functional safety systems including TAWS, FDR, CVR, TCAS, AHRS and weather radar - but TAWS was inhibited.
- The captain, aged 62, flew with a junior copilot who had only his second sector flight and was assigned no operational role.
- Competing operators had already turned back and Jomsom had opened at 09:09 amid cloudy, rainy conditions reported around the critical Tatopani and Lete passes.
- The flight’s entire final fifteen minutes and cockpit exchanges were captured on the CVR and FDR, prompting investigators to probe how an experienced crew flew into the gorge with warnings turned off.

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.]]>https://api.spreaker.com/episode/74771396Mon, 31 Aug 2026 17:37:03 +0000OBOMEDIA ENTERTAINMENTA captain hesitates at Pokhara with TAWS inhibited and clouds closing on the Kali Gandaki gorge - did they make it to Jomsom in time? The TAWS switch silenced the cockpit and cost them the runway-time In this episode, we follow Tara Air Flight...
The TAWS switch silenced the cockpit and cost them the runway-time

In this episode, we follow Tara Air Flight 197’s fifteen-minute climb from Pokhara toward Jomsom through the narrow Kali Gandaki gorge. The podcast covers the flight’s equipment, crew makeup, weather and procedural context to ask whether key decisions and a silenced Terrain Awareness and Warning System sealed the aircraft’s fate.

Date: May 29, 2022
Flight: Tara Air Flight 197
Aircraft: DHC-6 Twin Otter, registration 9N-AET
Passengers on board: 22 (19 passengers, 3 crew)
Route: Pokhara to Jomsom, Kali Gandaki gorge

- The aircraft took off at 09:55 for a scheduled 20-minute hop through a VFR-only corridor known for sudden cloud and turbulence.
- The cockpit carried functional safety systems including TAWS, FDR, CVR, TCAS, AHRS and weather radar - but TAWS was inhibited.
- The captain, aged 62, flew with a junior copilot who had only his second sector flight and was assigned no operational role.
- Competing operators had already turned back and Jomsom had opened at 09:09 amid cloudy, rainy conditions reported around the critical Tatopani and Lete passes.
- The flight’s entire final fifteen minutes and cockpit exchanges were captured on the CVR and FDR, prompting investigators to probe how an experienced crew flew into the gorge with warnings turned off.

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.]]>924falsefullhttps://www.spreaker.com/episode/the-throttle-coupling-slipped-the-left-engine-surged-did-they-stop-in-time--74771395
The throttle coupling slipped, the left engine surged - did they stop in time?

In this episode, we follow the final minute after an Airbus A310 touches down at Irkutsk and a single unchecked component suddenly moves. The episode traces how maintenance choices, crew background, and cockpit actions aligned in a race against runway length and time.

Aircraft: Airbus A310-300, registration F-OGYP
Date: July 9, 2006
Location: Irkutsk, runway 30
People: Captain Sergey G. Shibanov; First Officer Vladimir G. Chernykh; 203 aboard
Issue: Left engine throttle coupling never inspected; required 400 g to move (standard ~1200 g)

- The aircraft was nineteen years old and had no recorded inspections of the left throttle coupling across its entire service history.
- Three days earlier the right thrust reverser failed; parts were swapped and the left reverser was deferred per the minimum equipment list.
- S7 Airlines did not provide specific crew training or a briefing about operating with the thrust reverser deferred.
- Captain Shibanov had 10,611 flight hours with 1,056 on the A310; First Officer Chernykh had 9,771 hours but only 158 on the A310 after recent conversion from four-person cockpits.
- Seconds after touchdown at 132 knots, a palm brushed the left throttle lever and the worn coupling let the engine surge to 60% thrust while the aircraft was committed to stopping on the runway.

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.]]>https://api.spreaker.com/episode/74771395Mon, 31 Aug 2026 17:36:59 +0000OBOMEDIA ENTERTAINMENTA landing at Irkutsk goes from routine to critical when a worn throttle coupling lets the left engine surge - did they stop in time? The throttle coupling slipped, the left engine surged - did they stop in time? In this episode, we follow the...
The throttle coupling slipped, the left engine surged - did they stop in time?

In this episode, we follow the final minute after an Airbus A310 touches down at Irkutsk and a single unchecked component suddenly moves. The episode traces how maintenance choices, crew background, and cockpit actions aligned in a race against runway length and time.

Aircraft: Airbus A310-300, registration F-OGYP
Date: July 9, 2006
Location: Irkutsk, runway 30
People: Captain Sergey G. Shibanov; First Officer Vladimir G. Chernykh; 203 aboard
Issue: Left engine throttle coupling never inspected; required 400 g to move (standard ~1200 g)

- The aircraft was nineteen years old and had no recorded inspections of the left throttle coupling across its entire service history.
- Three days earlier the right thrust reverser failed; parts were swapped and the left reverser was deferred per the minimum equipment list.
- S7 Airlines did not provide specific crew training or a briefing about operating with the thrust reverser deferred.
- Captain Shibanov had 10,611 flight hours with 1,056 on the A310; First Officer Chernykh had 9,771 hours but only 158 on the A310 after recent conversion from four-person cockpits.
- Seconds after touchdown at 132 knots, a palm brushed the left throttle lever and the worn coupling let the engine surge to 60% thrust while the aircraft was committed to stopping on the runway.

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.]]>899falsefull