https://www.spreaker.com/podcast/aviation-survival-stories--7195689
This podcast goes beyond mere accident reports, bringing you gripping narratives of near-misses, harrowing aircraft incidents, and incredible tales of human resilience. We explore the critical decisions, the split-second actions, and the sheer will to survive that define these extraordinary events. From cockpit drama to passenger bravery, each episode uncovers the real stories behind aviation catastrophes.

New episodes arrive every single day, Monday through Sunday, at 4:00 AM, offering a consistent dose of compelling content. Each installment provides a meticulously researched account, reconstructing the events with vivid detail and exploring the lessons learned from each aviation disaster and miraculous escape.

This show is for anyone fascinated by flight safety, the mechanics of aircraft failures, and the extraordinary human spirit in extreme circumstances. If you're drawn to tales of survival against impossible odds and the intricate details of aviation accidents, you've found your next obsession.

Subscribe now to Aviation Survival Stories and prepare for takeoff.]]>enPersonal Journals© 2026 OBOMEDIA Creatorshttps://d3wo5wojvuv7l.cloudfront.net/t_rss_itunes_square_1400/images.spreaker.com/original/f66bb0bdfb2644b2f50f3e9209f901d4.jpghttps://www.spreaker.com/podcast/aviation-survival-stories--7195689Sun, 25 Oct 2026 08:02:19 +0000Creator at ObomediaCreator at Obomediacreators@obomedia.comBeyond the headlines and the black box recordings, what truly happens when disaster strikes at 30,000 feet? Aviation Survival Stories delves deep into the human element of airborne emergencies. This podcast goes beyond mere accident reports, bringing...
This podcast goes beyond mere accident reports, bringing you gripping narratives of near-misses, harrowing aircraft incidents, and incredible tales of human resilience. We explore the critical decisions, the split-second actions, and the sheer will to survive that define these extraordinary events. From cockpit drama to passenger bravery, each episode uncovers the real stories behind aviation catastrophes.

New episodes arrive every single day, Monday through Sunday, at 4:00 AM, offering a consistent dose of compelling content. Each installment provides a meticulously researched account, reconstructing the events with vivid detail and exploring the lessons learned from each aviation disaster and miraculous escape.

This show is for anyone fascinated by flight safety, the mechanics of aircraft failures, and the extraordinary human spirit in extreme circumstances. If you're drawn to tales of survival against impossible odds and the intricate details of aviation accidents, you've found your next obsession.

Subscribe now to Aviation Survival Stories and prepare for takeoff.]]>false6b550982-705f-52dd-91ee-77e57eb16551episodichttps://www.spreaker.com/episode/a-keyboardist-filmed-himself-describing-a-plane-crash-dream-hours-before-dying-in-one--73097369
Fear of sudden catastrophe: a musician told a hairdresser twice that he dreamed the plane would crash hours before a Learjet vanished from radar north of São Paulo, killing nine people - so how did an airworthy jet with no mechanical failures end up flying straight into terrain? Discover the sequence of cockpit decisions, a missed approach turned deadly, and the one left unanswered question: why did the crew turn toward Serra da Cantareira when every chart said turn away?

In this episode, we follow the final hours of Mamonas Assassinas and the flight that ended them, tracing the crew’s duty time, the aircraft’s condition, the approach into Guarulhos, and the critical decisions made in the cockpit that night to ask whether a different choice could have saved nine lives.

Person: Júlio César Barbosa (Júlio Rasec)
Event: Learjet PT-LSD accident on March 2, 1996
Location: north of São Paulo, Serra da Cantareira
Aircraft: Learjet 25 Delta, registration PT-LSD, built 1978, 6,123 flight hours
Operator: Madrid Táxi Aéreo Ltda (no safety team; insurance lapsed)

- The band’s debut album sold three million copies.
- Nine people were aboard the Learjet when it vanished from radar.
- The crew had been on duty for roughly thirty-six hours before takeoff.
- PT-LSD lifted off Brasília at 21:58 on March 2, 1996; São Paulo was about ninety minutes away.
- The published missed-approach procedure required a right turn; the pilot deliberately turned left toward terrain roughly 3,300 feet high.

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/73097369Mon, 26 Oct 2026 08:00:02 +0000Creator at ObomediaA keyboardist filmed himself describing a plane-crash dream hours before dying in one Fear of sudden catastrophe: a musician told a hairdresser twice that he dreamed the plane would crash hours before a Learjet vanished from radar north of São...
Fear of sudden catastrophe: a musician told a hairdresser twice that he dreamed the plane would crash hours before a Learjet vanished from radar north of São Paulo, killing nine people - so how did an airworthy jet with no mechanical failures end up flying straight into terrain? Discover the sequence of cockpit decisions, a missed approach turned deadly, and the one left unanswered question: why did the crew turn toward Serra da Cantareira when every chart said turn away?

In this episode, we follow the final hours of Mamonas Assassinas and the flight that ended them, tracing the crew’s duty time, the aircraft’s condition, the approach into Guarulhos, and the critical decisions made in the cockpit that night to ask whether a different choice could have saved nine lives.

Person: Júlio César Barbosa (Júlio Rasec)
Event: Learjet PT-LSD accident on March 2, 1996
Location: north of São Paulo, Serra da Cantareira
Aircraft: Learjet 25 Delta, registration PT-LSD, built 1978, 6,123 flight hours
Operator: Madrid Táxi Aéreo Ltda (no safety team; insurance lapsed)

- The band’s debut album sold three million copies.
- Nine people were aboard the Learjet when it vanished from radar.
- The crew had been on duty for roughly thirty-six hours before takeoff.
- PT-LSD lifted off Brasília at 21:58 on March 2, 1996; São Paulo was about ninety minutes away.
- The published missed-approach procedure required a right turn; the pilot deliberately turned left toward terrain roughly 3,300 feet high.

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.]]>1136falsefullhttps://www.spreaker.com/episode/they-landed-on-their-bellies-why-98-people-didn-t-survive-pia-8303--73097368
The sound of aluminum grinding against concrete echoed for miles when an Airbus A320’s engines hit Runway 25L first - the airplane was intact and 99 people were alive for a brief, terrible moment. How did an aircraft with a valid airworthiness certificate, a captain with 17,252 hours, and a plane that had flown six times since returning to service end with 98 preventable deaths?

In this episode, we tell who was on Flight 8303, what happened during the final approach and immediate aftermath, and the systemic failures that made those engines touch concrete. Could the crash have been avoided if oversight and pilot qualification issues had been addressed months or years earlier?

Date: May 22, 2020
Aircraft: Airbus A320-214, registration AP-BLD
Passengers onboard: 99
Total fatalities: 98
Airframe hours: 47,124

- The aircraft touched down belly-first at 14:28 local time on Runway 25L at Karachi’s Jinnah International Airport.
- Ninety-seven passengers died within the hour and one more died ten days later, a total of 98 deaths.
- The airplane had returned to service on May 7, 2020, after roughly two months grounded for the COVID-19 pandemic and completed six flights before Flight 8303.
- Captain Sajjad Gul was 58 years old with 17,252 total flight hours; he was the pilot monitoring on this flight.
- Investigators later revealed 262 of Pakistan’s 860 licensed pilots held inauthentic credentials, and PIA suspended 150 of its 434 active pilots as the probe widened.

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/73097368Sun, 25 Oct 2026 08:00:02 +0000Creator at ObomediaThey Landed on Their Bellies: Why 98 People Didn't Survive PIA 8303 The sound of aluminum grinding against concrete echoed for miles when an Airbus A320’s engines hit Runway 25L first - the airplane was intact and 99 people were alive for a brief,...
The sound of aluminum grinding against concrete echoed for miles when an Airbus A320’s engines hit Runway 25L first - the airplane was intact and 99 people were alive for a brief, terrible moment. How did an aircraft with a valid airworthiness certificate, a captain with 17,252 hours, and a plane that had flown six times since returning to service end with 98 preventable deaths?

In this episode, we tell who was on Flight 8303, what happened during the final approach and immediate aftermath, and the systemic failures that made those engines touch concrete. Could the crash have been avoided if oversight and pilot qualification issues had been addressed months or years earlier?

Date: May 22, 2020
Aircraft: Airbus A320-214, registration AP-BLD
Passengers onboard: 99
Total fatalities: 98
Airframe hours: 47,124

- The aircraft touched down belly-first at 14:28 local time on Runway 25L at Karachi’s Jinnah International Airport.
- Ninety-seven passengers died within the hour and one more died ten days later, a total of 98 deaths.
- The airplane had returned to service on May 7, 2020, after roughly two months grounded for the COVID-19 pandemic and completed six flights before Flight 8303.
- Captain Sajjad Gul was 58 years old with 17,252 total flight hours; he was the pilot monitoring on this flight.
- Investigators later revealed 262 of Pakistan’s 860 licensed pilots held inauthentic credentials, and PIA suspended 150 of its 434 active pilots as the probe widened.

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.]]>1116falsefullhttps://www.spreaker.com/episode/on-propeller-blade-angle-experienced-crew-on-routine-check-system-supposed-to-prevent-reversal--73097364
A single measurement - a propeller blade at minus eight degrees - turned a routine proficiency check into a deadly mismatch of forces that rolled a DC-6 into the ground. Three engines were producing forward thrust, one was producing full reverse, and three men died in a field; how could a safety system designed to prevent reversals actually make recovery impossible?

In this episode, we describe the flight, the crew, the maintenance and the design detail that led to the accident, and we follow how that single blade angle revealed a hidden failure mode that no one in the cockpit could correct; how did a grounded reversal become irrevocable once the airplane lifted off?

Date: April 4, 1955
Aircraft: Douglas DC-6, registration N37512
Weight: approximately 61,000 pounds at takeoff
Crew experience: Captain Stanley C. Hoyt, 9,763 total flight hours, 549 hours in DC-6
Propeller settings: three at +34 degrees, one at -8 degrees

- Takeoff occurred at about 3 minutes before 4 PM from Long Island MacArthur Airport.
- Aircraft total airframe hours at the time: 22,068 hours.
- Last scheduled maintenance inspection completed 105 hours before the accident.
- Wind at the field: southwest about 20 knots with gusts near 30 knots.
- The reversal system used a weight-on-gear switch that cut electrical power the moment wheels left the runway, removing both the ability to reverse in flight and the ability to reset a blade already reversed.

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/73097364Sat, 24 Oct 2026 08:00:02 +0000Creator at Obomediaon propeller blade angle; experienced crew on routine check; system supposed to prevent reversal A single measurement - a propeller blade at minus eight degrees - turned a routine proficiency check into a deadly mismatch of forces that rolled a...
A single measurement - a propeller blade at minus eight degrees - turned a routine proficiency check into a deadly mismatch of forces that rolled a DC-6 into the ground. Three engines were producing forward thrust, one was producing full reverse, and three men died in a field; how could a safety system designed to prevent reversals actually make recovery impossible?

In this episode, we describe the flight, the crew, the maintenance and the design detail that led to the accident, and we follow how that single blade angle revealed a hidden failure mode that no one in the cockpit could correct; how did a grounded reversal become irrevocable once the airplane lifted off?

Date: April 4, 1955
Aircraft: Douglas DC-6, registration N37512
Weight: approximately 61,000 pounds at takeoff
Crew experience: Captain Stanley C. Hoyt, 9,763 total flight hours, 549 hours in DC-6
Propeller settings: three at +34 degrees, one at -8 degrees

- Takeoff occurred at about 3 minutes before 4 PM from Long Island MacArthur Airport.
- Aircraft total airframe hours at the time: 22,068 hours.
- Last scheduled maintenance inspection completed 105 hours before the accident.
- Wind at the field: southwest about 20 knots with gusts near 30 knots.
- The reversal system used a weight-on-gear switch that cut electrical power the moment wheels left the runway, removing both the ability to reverse in flight and the ability to reset a blade already reversed.

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.]]>998falsefullhttps://www.spreaker.com/episode/nine-seconds-to-impact-boy-pointed-wing-struck-monte-cinto--73097334
A chilling gap between two pictures of the same flight: investigators later found the left wing struck Monte Cinto and placed a plaque at the precise impact point amid 27 tons of wreckage and human remains after 27 years - so how did searchers spend the first hours looking at the sea instead of the mountain? What did the final nine seconds reveal about a crew, a controller, and a route no one there had flown before?

In this episode, we tell the sequence of events on the approach to Ajaccio Airport on 1 September 1981, how navigation and communication left a jet descending into Corsica’s highest massif, and why those last nine seconds mattered. Could different information in the cockpit or on the ground have changed what happened?

Event: Crash of Inex-Adria DC-9 YU-AJO
Date: 1 September 1981
People aboard: 180
Wreckage recovered: 27 tons
Time from GPWS to impact: 9 seconds

- The aircraft was a DC-9 operated by Inex-Adria Aviopromet registered YU-AJO with 683 flight hours.
- Investigators placed a plaque at the exact point where the left wing first made contact with the mountain.
- Human remains were still tangled in debris after 27 years on the slope.
- Ajaccio Airport had no radar; the controller’s picture of the aircraft’s position came solely from voice transmissions.
- The first officer had received his commercial pilot license 20 days before the flight and his young son was aboard and heard on the cockpit voice recording naming Monte Cinto.

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/73097334Fri, 23 Oct 2026 08:00:02 +0000Creator at ObomediaNine Seconds to Impact: Boy Pointed, Wing Struck Monte Cinto A chilling gap between two pictures of the same flight: investigators later found the left wing struck Monte Cinto and placed a plaque at the precise impact point amid 27 tons of wreckage...
A chilling gap between two pictures of the same flight: investigators later found the left wing struck Monte Cinto and placed a plaque at the precise impact point amid 27 tons of wreckage and human remains after 27 years - so how did searchers spend the first hours looking at the sea instead of the mountain? What did the final nine seconds reveal about a crew, a controller, and a route no one there had flown before?

In this episode, we tell the sequence of events on the approach to Ajaccio Airport on 1 September 1981, how navigation and communication left a jet descending into Corsica’s highest massif, and why those last nine seconds mattered. Could different information in the cockpit or on the ground have changed what happened?

Event: Crash of Inex-Adria DC-9 YU-AJO
Date: 1 September 1981
People aboard: 180
Wreckage recovered: 27 tons
Time from GPWS to impact: 9 seconds

- The aircraft was a DC-9 operated by Inex-Adria Aviopromet registered YU-AJO with 683 flight hours.
- Investigators placed a plaque at the exact point where the left wing first made contact with the mountain.
- Human remains were still tangled in debris after 27 years on the slope.
- Ajaccio Airport had no radar; the controller’s picture of the aircraft’s position came solely from voice transmissions.
- The first officer had received his commercial pilot license 20 days before the flight and his young son was aboard and heard on the cockpit voice recording naming Monte Cinto.

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.]]>995falsefullhttps://www.spreaker.com/episode/at-03-42-a-m-they-pushed-an-airworthy-plane-into-earth--73097245
Fear that skilled pilots can still be outpaced by human limits: a Boeing 757 flying as FlyDubai 981 struck the ground at nearly 500 mph despite being airworthy and fully functional, killing 62 people - so what chain of pressures turned a routine route into a fatal descent? Dive into the one night where fatigue, weather and decisions collided to erase margins of safety.

In this episode, we present the sequence of events from the March 18, 2016 flight from Dubai to Rostov-on-Don, the deteriorating weather, the prolonged holding pattern, and the approaches that preceded the crash, asking how exhaustion and procedural pressures combined to produce catastrophe.

Flight: FlyDubai 981
Date: March 18, 2016
Aircraft: Boeing 757-200
Fatalities: 62
Location: Rostov-on-Don

- The aircraft impacted terrain at nearly 500 miles per hour.
- The crew circled in a holding pattern for nearly two hours before landing attempts.
- Captain Aristos Sokratous was 45 years old and due to move to Ryanair; his wife was pregnant.
- First Officer Alejandro Gazenko was 35 and neither pilot had flown into Rostov-on-Don before that night.
- Aeroflot on a parallel frequency made three aborted approaches and diverted to Krasnodar.

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/73097245Thu, 22 Oct 2026 08:00:03 +0000Creator at ObomediaAt 03:42 a.m. They Pushed an Airworthy Plane Into Earth Fear that skilled pilots can still be outpaced by human limits: a Boeing 757 flying as FlyDubai 981 struck the ground at nearly 500 mph despite being airworthy and fully functional, killing 62...
Fear that skilled pilots can still be outpaced by human limits: a Boeing 757 flying as FlyDubai 981 struck the ground at nearly 500 mph despite being airworthy and fully functional, killing 62 people - so what chain of pressures turned a routine route into a fatal descent? Dive into the one night where fatigue, weather and decisions collided to erase margins of safety.

In this episode, we present the sequence of events from the March 18, 2016 flight from Dubai to Rostov-on-Don, the deteriorating weather, the prolonged holding pattern, and the approaches that preceded the crash, asking how exhaustion and procedural pressures combined to produce catastrophe.

Flight: FlyDubai 981
Date: March 18, 2016
Aircraft: Boeing 757-200
Fatalities: 62
Location: Rostov-on-Don

- The aircraft impacted terrain at nearly 500 miles per hour.
- The crew circled in a holding pattern for nearly two hours before landing attempts.
- Captain Aristos Sokratous was 45 years old and due to move to Ryanair; his wife was pregnant.
- First Officer Alejandro Gazenko was 35 and neither pilot had flown into Rostov-on-Don before that night.
- Aeroflot on a parallel frequency made three aborted approaches and diverted to Krasnodar.

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.]]>987falsefullhttps://www.spreaker.com/episode/the-wings-had-been-cleaned-subversion-if-wings-were-clean-why-28-dead--73097214
Cold, routine choices can hide lethal consequences: deicing fluid ran off in sheets, the plane waited in snow for 27 minutes, and 28 people died. How did a cleaned wing and a series of small procedural gaps combine into disaster?

In this episode, we walk through the sequence of events on Continental Airlines Flight 1713 and the operational context at Denver Stapleton on November 15, 1987, detailing crew experience, air traffic communications, and the timing that led to the unanswered question: why was no decision made to deice again?

Event: Continental Airlines Flight 1713
Date: November 15, 1987
Location: Denver Stapleton International Airport, Runway 35L
Aircraft: Douglas DC-9-14, registration N626TX
Fatalities: 28

- Deicing fluid was applied and ran off the aircraft surfaces; a technician signed off at 1:46 PM.
- The aircraft sat in the snow for 27 minutes between deicing completion and the accident.
- Flight 1713 reached the number-one position at Runway 35L at 2:05 PM.
- Captain Frank B. Zvonek Jr. had 166 hours on the DC-9 and had been upgraded to captain on the type less than three weeks before the crash.
- First Officer Lee E. Bruecher had 36 hours on the DC-9 and had not flown in the 24 days before November 15.

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/73097214Wed, 21 Oct 2026 08:00:02 +0000Creator at ObomediaThe wings had been cleaned. - subversion: if wings were clean, why 28 dead? Cold, routine choices can hide lethal consequences: deicing fluid ran off in sheets, the plane waited in snow for 27 minutes, and 28 people died. How did a cleaned wing and...
Cold, routine choices can hide lethal consequences: deicing fluid ran off in sheets, the plane waited in snow for 27 minutes, and 28 people died. How did a cleaned wing and a series of small procedural gaps combine into disaster?

In this episode, we walk through the sequence of events on Continental Airlines Flight 1713 and the operational context at Denver Stapleton on November 15, 1987, detailing crew experience, air traffic communications, and the timing that led to the unanswered question: why was no decision made to deice again?

Event: Continental Airlines Flight 1713
Date: November 15, 1987
Location: Denver Stapleton International Airport, Runway 35L
Aircraft: Douglas DC-9-14, registration N626TX
Fatalities: 28

- Deicing fluid was applied and ran off the aircraft surfaces; a technician signed off at 1:46 PM.
- The aircraft sat in the snow for 27 minutes between deicing completion and the accident.
- Flight 1713 reached the number-one position at Runway 35L at 2:05 PM.
- Captain Frank B. Zvonek Jr. had 166 hours on the DC-9 and had been upgraded to captain on the type less than three weeks before the crash.
- First Officer Lee E. Bruecher had 36 hours on the DC-9 and had not flown in the 24 days before November 15.

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.]]>899falsefullhttps://www.spreaker.com/episode/the-night-they-landed-anyway-how-18-died-in-aspen--73097192
Fear of crossing a clear legal line drove a professional crew to land where the rules forbade it: 18 people boarded a Gulfstream III on March 29, 2001, and none survived. The NTSB found the captain received a direct FAA warning that same day and that client pressure was a contributing factor-so why did they still descend below the legal minimum?

In this episode, we tell the story of the flight from Van Nuys to Aspen and the sequence of decisions, warnings, and pressures that led to a fatal illegal approach. You’ll hear how crew communication, a late departure, a client’s demands, and a federal warning intersected to produce a single deadly choice-what made them fly on?

Event: Avjet Flight, March 29, 2001
Aircraft: Gulfstream III
People: 18 on board
Captain: Robert Frisbie, 44 years old
First Officer: Peter Kowalczyk, 38 years old

- Departure time from Van Nuys: 16:52 (4:52 PM)
- Departure delay caused by client arrival: 41 minutes
- Sunset time at Aspen that evening: 19:52 MST (7:52 PM)
- Number of fatalities: 18 (no survivors)
- NTSB finding: first federal record naming charter client pressure as a contributing factor

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/73097192Tue, 20 Oct 2026 08:00:02 +0000Creator at ObomediaThe Night They Landed Anyway: How 18 Died in Aspen Fear of crossing a clear legal line drove a professional crew to land where the rules forbade it: 18 people boarded a Gulfstream III on March 29, 2001, and none survived. The NTSB found the captain...
Fear of crossing a clear legal line drove a professional crew to land where the rules forbade it: 18 people boarded a Gulfstream III on March 29, 2001, and none survived. The NTSB found the captain received a direct FAA warning that same day and that client pressure was a contributing factor-so why did they still descend below the legal minimum?

In this episode, we tell the story of the flight from Van Nuys to Aspen and the sequence of decisions, warnings, and pressures that led to a fatal illegal approach. You’ll hear how crew communication, a late departure, a client’s demands, and a federal warning intersected to produce a single deadly choice-what made them fly on?

Event: Avjet Flight, March 29, 2001
Aircraft: Gulfstream III
People: 18 on board
Captain: Robert Frisbie, 44 years old
First Officer: Peter Kowalczyk, 38 years old

- Departure time from Van Nuys: 16:52 (4:52 PM)
- Departure delay caused by client arrival: 41 minutes
- Sunset time at Aspen that evening: 19:52 MST (7:52 PM)
- Number of fatalities: 18 (no survivors)
- NTSB finding: first federal record naming charter client pressure as a contributing factor

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.]]>946falsefullhttps://www.spreaker.com/episode/last-words-cheerful-nine-minutes-later-thirteen-people-dead-inside-a-cloud-covered-mountain--73097180
A routine thirty-minute flight ended with thirteen dead after a cheerful radio sign-off at 11:11 on August 11, 2009 - the Twin Otter vanished into cloud over the Owen Stanley Range nine minutes later. How did two experienced pilots on a familiar route, flying an aircraft with 46,700 flight hours and no recorders, end up inside a mountain?

In this episode, we present the facts of Airlines PNG Flight 4684 and the conditions and paperwork that preceded the crash, tracing crew qualifications, aircraft equipment, and weather to ask the central question: could small regulatory and procedural gaps combine into a fatal chain?

Date: August 11, 2009
Event: Airlines PNG Flight 4684 crash
Aircraft: de Havilland Canada Twin Otter P2-MCB, built 1974, 46,700 total flight hours
Crew hours: Captain Moala 2,177 total hours (1,836 on type); First Officer Souka 2,150 total hours (1,940 on type)
Passengers: 13 people aboard (including 8 Australians, 1 Japanese tourist, 1 Papua New Guinean guide)

- Takeoff from Jacksons International Airport at 10:50 with estimated arrival at Kokoda 11:20.
- Radio exchange at 11:11: "Thank you very much, morning long you," followed by silence nine minutes later.
- Flight was filed as IFR though First Officer Souka did not hold an IFR rating.
- Kokoda Airstrip had no ground-based navigation aids; crew relied on onboard GPS for the approach.
- Aircraft carried no cockpit voice recorder or flight data recorder because regulations at the time did not require them.

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/73097180Mon, 19 Oct 2026 08:00:02 +0000Creator at ObomediaLast words cheerful - nine minutes later, thirteen people dead inside a cloud-covered mountain A routine thirty-minute flight ended with thirteen dead after a cheerful radio sign-off at 11:11 on August 11, 2009 - the Twin Otter vanished into cloud...
A routine thirty-minute flight ended with thirteen dead after a cheerful radio sign-off at 11:11 on August 11, 2009 - the Twin Otter vanished into cloud over the Owen Stanley Range nine minutes later. How did two experienced pilots on a familiar route, flying an aircraft with 46,700 flight hours and no recorders, end up inside a mountain?

In this episode, we present the facts of Airlines PNG Flight 4684 and the conditions and paperwork that preceded the crash, tracing crew qualifications, aircraft equipment, and weather to ask the central question: could small regulatory and procedural gaps combine into a fatal chain?

Date: August 11, 2009
Event: Airlines PNG Flight 4684 crash
Aircraft: de Havilland Canada Twin Otter P2-MCB, built 1974, 46,700 total flight hours
Crew hours: Captain Moala 2,177 total hours (1,836 on type); First Officer Souka 2,150 total hours (1,940 on type)
Passengers: 13 people aboard (including 8 Australians, 1 Japanese tourist, 1 Papua New Guinean guide)

- Takeoff from Jacksons International Airport at 10:50 with estimated arrival at Kokoda 11:20.
- Radio exchange at 11:11: "Thank you very much, morning long you," followed by silence nine minutes later.
- Flight was filed as IFR though First Officer Souka did not hold an IFR rating.
- Kokoda Airstrip had no ground-based navigation aids; crew relied on onboard GPS for the approach.
- Aircraft carried no cockpit voice recorder or flight data recorder because regulations at the time did not require them.

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.]]>1039falsefullhttps://www.spreaker.com/episode/engine-failure-was-survivable-the-captain-s-own-hands-brought-the-plane-down--73097172
A routine domestic flight became deadly two minutes after liftoff when a Boeing 737 climbed to less than 400 feet with its landing gear still down - a configuration that turned a contained engine failure into catastrophe. Why did the crew never retract the gear, and how did missed briefings and cockpit protocol failures leave the pilots without the shared commands that might have saved 102 lives?

In this episode, we tell what the flight carried, the conditions on the ground, and the cockpit actions recorded before and after takeoff, centering on the unanswered question of why the landing gear remained extended during climb.

Event: Crash of Air Algérie 6289
Date: March 6, 2003
Location: Tamanrasset to Ghardaïa (departure from Tamanrasset)
Aircraft: Boeing 737-200 (registration 7T-VEZ)
Survivors: 1 of 103 aboard

- Departure time: liftoff at 15:13 local, impact two minutes later.
- Occupants: 103 on board - 97 passengers and 6 crew.
- Fatalities: 102 people died; 1 survivor (28-year-old soldier Youcef Djillali).
- Aircraft weight at takeoff: 48,708 kilograms (within max 49,500 kg).
- Performance speeds computed: V1 144 knots, Vr 146 knots, V2 150 knots.

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/73097172Sun, 18 Oct 2026 08:00:03 +0000Creator at ObomediaEngine failure was survivable - the captain's own hands brought the plane down A routine domestic flight became deadly two minutes after liftoff when a Boeing 737 climbed to less than 400 feet with its landing gear still down - a configuration that...
A routine domestic flight became deadly two minutes after liftoff when a Boeing 737 climbed to less than 400 feet with its landing gear still down - a configuration that turned a contained engine failure into catastrophe. Why did the crew never retract the gear, and how did missed briefings and cockpit protocol failures leave the pilots without the shared commands that might have saved 102 lives?

In this episode, we tell what the flight carried, the conditions on the ground, and the cockpit actions recorded before and after takeoff, centering on the unanswered question of why the landing gear remained extended during climb.

Event: Crash of Air Algérie 6289
Date: March 6, 2003
Location: Tamanrasset to Ghardaïa (departure from Tamanrasset)
Aircraft: Boeing 737-200 (registration 7T-VEZ)
Survivors: 1 of 103 aboard

- Departure time: liftoff at 15:13 local, impact two minutes later.
- Occupants: 103 on board - 97 passengers and 6 crew.
- Fatalities: 102 people died; 1 survivor (28-year-old soldier Youcef Djillali).
- Aircraft weight at takeoff: 48,708 kilograms (within max 49,500 kg).
- Performance speeds computed: V1 144 knots, Vr 146 knots, V2 150 knots.

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.]]>1087falsefullhttps://www.spreaker.com/episode/the-night-two-planes-vanished-charkhi-dadri-s-fatal-misread-altitude--73097163
A single misread number and a radio operator without instruments turned a routine airway into the deadliest mid-air collision in history, killing all 349 people aboard both aircraft - how did two crews occupying the same sky at the same time fail to see each other? What one miscommunication changed every minute of the final six minutes above Haryana?

In this episode, we tell what happened on the evening of 12 November 1996, describing the flights, crews, and the airway system that depended entirely on pilots’ reports; we follow the Lahoti Commission’s central question about how a crew could descend through an altitude they reported holding and collide with an aircraft they had been warned was there.

Date: 12 November 1996
Event: Mid-air collision above Charkhi Dadri
Total fatalities: 349
Aircraft 1: Saudia Flight 763, Boeing 747, 312 people on board
Aircraft 2: Kazakhstan Airlines Flight 1907, Ilyushin Il-76, 37 people on board

- Time of sighting reported by US Air Force crew: 18:40 local
- Saudia Flight 763 departure time: 18:32 from Indira Gandhi International Airport
- Kazakhstan Flight 1907 reported altitude at 18:39: 15,000 feet (flight recorder showed 16,348 ft and still descending)
- Vertical separation assigned by controller V. K. Dutta: 1,000 feet (Kazakhstan at 15,000 ft, Saudia climbing to 14,000 ft)
- Number of Kazakhstan crew members listed: navigator aged 51, radio operator Egor Repp aged 41, flight engineer aged 50

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/73097163Sat, 17 Oct 2026 08:00:02 +0000Creator at ObomediaThe Night Two Planes Vanished: Charkhi Dadri's Fatal Misread Altitude A single misread number and a radio operator without instruments turned a routine airway into the deadliest mid-air collision in history, killing all 349 people aboard both...
A single misread number and a radio operator without instruments turned a routine airway into the deadliest mid-air collision in history, killing all 349 people aboard both aircraft - how did two crews occupying the same sky at the same time fail to see each other? What one miscommunication changed every minute of the final six minutes above Haryana?

In this episode, we tell what happened on the evening of 12 November 1996, describing the flights, crews, and the airway system that depended entirely on pilots’ reports; we follow the Lahoti Commission’s central question about how a crew could descend through an altitude they reported holding and collide with an aircraft they had been warned was there.

Date: 12 November 1996
Event: Mid-air collision above Charkhi Dadri
Total fatalities: 349
Aircraft 1: Saudia Flight 763, Boeing 747, 312 people on board
Aircraft 2: Kazakhstan Airlines Flight 1907, Ilyushin Il-76, 37 people on board

- Time of sighting reported by US Air Force crew: 18:40 local
- Saudia Flight 763 departure time: 18:32 from Indira Gandhi International Airport
- Kazakhstan Flight 1907 reported altitude at 18:39: 15,000 feet (flight recorder showed 16,348 ft and still descending)
- Vertical separation assigned by controller V. K. Dutta: 1,000 feet (Kazakhstan at 15,000 ft, Saudia climbing to 14,000 ft)
- Number of Kazakhstan crew members listed: navigator aged 51, radio operator Egor Repp aged 41, flight engineer aged 50

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.]]>1046falsefullhttps://www.spreaker.com/episode/when-a-tiny-engine-part-killed-a-senator-and-his-daughter--73097154
A single failed propeller control unit turned routine physics into a sudden catastrophe that killed 23 people on April 5, 1991. A former U.S. senator and his 35-year-old daughter were among the dead-how did one small component end a life that survived war, politics, and public disgrace?

In this episode, we tell the story of Flight 2311 and the people on board, tracing John Goodwin Tower’s path from the Pacific War to the Senate and the moments before the crash, while asking what the wreckage reveals about the end of his life and legacy.

Person: John Goodwin Tower
Person: Marian Tower
Event: Atlantic Southeast Airlines Flight 2311 crash
Date: April 5, 1991
Cause: Failed propeller control unit

- 23 lives lost when the propeller control unit failed
- John Tower born September 29, 1925, in Houston
- Tower served in the Pacific from June 1943 to March 1946 aboard an LCS
- Tower won his Senate runoff with 50.6% to 49.4%
- Marian Tower was 35 years old at the time of the crash

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/73097154Fri, 16 Oct 2026 08:00:02 +0000Creator at ObomediaWhen a Tiny Engine Part Killed a Senator and His Daughter A single failed propeller control unit turned routine physics into a sudden catastrophe that killed 23 people on April 5, 1991. A former U.S. senator and his 35-year-old daughter were among...
A single failed propeller control unit turned routine physics into a sudden catastrophe that killed 23 people on April 5, 1991. A former U.S. senator and his 35-year-old daughter were among the dead-how did one small component end a life that survived war, politics, and public disgrace?

In this episode, we tell the story of Flight 2311 and the people on board, tracing John Goodwin Tower’s path from the Pacific War to the Senate and the moments before the crash, while asking what the wreckage reveals about the end of his life and legacy.

Person: John Goodwin Tower
Person: Marian Tower
Event: Atlantic Southeast Airlines Flight 2311 crash
Date: April 5, 1991
Cause: Failed propeller control unit

- 23 lives lost when the propeller control unit failed
- John Tower born September 29, 1925, in Houston
- Tower served in the Pacific from June 1943 to March 1946 aboard an LCS
- Tower won his Senate runoff with 50.6% to 49.4%
- Marian Tower was 35 years old at the time of the crash

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.]]>1015falsefullhttps://www.spreaker.com/episode/the-playwright-who-never-saw-broadway-larry-shue-s-final-flight--73097141
Fear of a life just about to arrive - a playwright days from his Broadway debut boarded a routine Beech 99 commuter flight on September 23, 1985, and never reached home; what was lost were two soon-to-be-famous plays, a Disney screenplay, and twenty-seven years of private diaries - how did a common regional flight end an extraordinary career?

In this episode, we tell the story of Larry Shue’s final journey and the works he left behind, tracing his rise from Illinois Wesleyan to Milwaukee repertory success and the abrupt end on a flight to Virginia that halted his Broadway debut and a Disney project.

Person: Larry Howard Shue
Date: July 23, 1946 (birth); September 23, 1985 (death)
Event: Beech 99 commuter plane crash near Weyers Cave, Virginia
Works: The Nerd (premiered April 1981), The Foreigner (premiered January 13, 1983)
Archive: Twenty-seven years of diaries held at University of Wisconsin-Milwaukee

- The Beech 99 crashed near Weyers Cave, Virginia on September 23, 1985, killing all 14 aboard.
- Larry Shue was 39 years old at the time of the crash and days away from his Broadway debut.
- The Nerd premiered in April 1981 at the Milwaukee Repertory Theater; The Foreigner premiered January 13, 1983.
- The Foreigner won two Obie Awards in 1985 and both plays later ran in London's West End.
- Twenty-seven years of Shue’s diaries, letters, and drawings are archived at the University of Wisconsin-Milwaukee.

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/73097141Thu, 15 Oct 2026 08:00:02 +0000Creator at ObomediaThe Playwright Who Never Saw Broadway: Larry Shue's Final Flight Fear of a life just about to arrive - a playwright days from his Broadway debut boarded a routine Beech 99 commuter flight on September 23, 1985, and never reached home; what was lost...
Fear of a life just about to arrive - a playwright days from his Broadway debut boarded a routine Beech 99 commuter flight on September 23, 1985, and never reached home; what was lost were two soon-to-be-famous plays, a Disney screenplay, and twenty-seven years of private diaries - how did a common regional flight end an extraordinary career?

In this episode, we tell the story of Larry Shue’s final journey and the works he left behind, tracing his rise from Illinois Wesleyan to Milwaukee repertory success and the abrupt end on a flight to Virginia that halted his Broadway debut and a Disney project.

Person: Larry Howard Shue
Date: July 23, 1946 (birth); September 23, 1985 (death)
Event: Beech 99 commuter plane crash near Weyers Cave, Virginia
Works: The Nerd (premiered April 1981), The Foreigner (premiered January 13, 1983)
Archive: Twenty-seven years of diaries held at University of Wisconsin-Milwaukee

- The Beech 99 crashed near Weyers Cave, Virginia on September 23, 1985, killing all 14 aboard.
- Larry Shue was 39 years old at the time of the crash and days away from his Broadway debut.
- The Nerd premiered in April 1981 at the Milwaukee Repertory Theater; The Foreigner premiered January 13, 1983.
- The Foreigner won two Obie Awards in 1985 and both plays later ran in London's West End.
- Twenty-seven years of Shue’s diaries, letters, and drawings are archived at the University of Wisconsin-Milwaukee.

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.]]>928falsefullhttps://www.spreaker.com/episode/seat-cushion-and-silence-the-unsolved-crash-that-killed-otis-redding--73097125
A seat cushion floated in Lake Monona while a man who could not swim surfaced after a plane vanished beneath him-seven people were lost on December 10, 1967, including a twenty-six-year-old who had just recorded a song that would become number one. How did a surviving cushion, a surgeon's removed polyps, and a disputed final song become the last traces of Otis Redding's life?

In this episode, we follow the sequence of events that led from a Stax recording session and a larynx operation to a fatal afternoon near Truax Field, and we ask what the unanswered details of the crash leave behind. What does the silence around that seat cushion tell us about loss, talent and the music left unfinished?

Person: Otis Ray Redding Jr.
Date: December 10, 1967
Location: Lake Monona, four miles from Truax Field, Madison, Wisconsin
Event: Twin-engine Beechcraft H18 crash at 3:28 PM
Song: "(Sittin' On) The Dock of the Bay" recorded early December 1967

- A seat cushion was already floating in Lake Monona when Ben Cauley broke the surface after the crash.
- Seven people died when the Beechcraft H18 went down at 3:28 PM on December 10, 1967.
- Otis Redding was twenty-six years old when he died and had recorded his now-number-one song three days earlier.
- Redding was born September 9, 1941, and by 1967 earned more than $35,000 a week with annual income exceeding $1,000,000.
- In September 1967 a surgeon removed polyps from Redding's larynx; during recovery he wrote nearly thirty songs in two weeks.

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/73097125Wed, 14 Oct 2026 08:00:02 +0000Creator at ObomediaSeat Cushion and Silence: The Unsolved Crash That Killed Otis Redding A seat cushion floated in Lake Monona while a man who could not swim surfaced after a plane vanished beneath him-seven people were lost on December 10, 1967, including a...
A seat cushion floated in Lake Monona while a man who could not swim surfaced after a plane vanished beneath him-seven people were lost on December 10, 1967, including a twenty-six-year-old who had just recorded a song that would become number one. How did a surviving cushion, a surgeon's removed polyps, and a disputed final song become the last traces of Otis Redding's life?

In this episode, we follow the sequence of events that led from a Stax recording session and a larynx operation to a fatal afternoon near Truax Field, and we ask what the unanswered details of the crash leave behind. What does the silence around that seat cushion tell us about loss, talent and the music left unfinished?

Person: Otis Ray Redding Jr.
Date: December 10, 1967
Location: Lake Monona, four miles from Truax Field, Madison, Wisconsin
Event: Twin-engine Beechcraft H18 crash at 3:28 PM
Song: "(Sittin' On) The Dock of the Bay" recorded early December 1967

- A seat cushion was already floating in Lake Monona when Ben Cauley broke the surface after the crash.
- Seven people died when the Beechcraft H18 went down at 3:28 PM on December 10, 1967.
- Otis Redding was twenty-six years old when he died and had recorded his now-number-one song three days earlier.
- Redding was born September 9, 1941, and by 1967 earned more than $35,000 a week with annual income exceeding $1,000,000.
- In September 1967 a surgeon removed polyps from Redding's larynx; during recovery he wrote nearly thirty songs in two weeks.

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.]]>1079falsefullhttps://www.spreaker.com/episode/audie-murphy-s-last-flight-how-a-fog-bank-killed-a-legend--73097121
A decorated war hero who survived Sicily, Anzio, and a burning tank destroyer died not on a battlefield but when his Aero Commander six-eighty flew into a mountain in zero visibility; the pilot held no instrument rating and six people on board were killed - so how did a man who survived so much perish in a Virginia fog bank? What did the wreckage reveal, and what crucial questions remain about that final flight?

In this episode, we tell the life story of Audie Leon Murphy alongside the facts of the crash that ended his life and the gaps investigators could not fully close. We trace his rise from a fifth-grade school dropout in Kingston, Texas to the most decorated American soldier of World War II, and we return to the mountain ridge northwest of Roanoke to ask why the flight went on in conditions that required an instrument rating.

Date: May 28, 1971
Location: Fourteen nautical miles northwest of Roanoke, Virginia
Aircraft: Aero Commander 680 (twin-engine)
Passengers on board: Six
Victim: Audie Leon Murphy, born June 20, 1925

- Visibility at the crash site was reported as zero with clouds on the ridgeline and rain falling.
- The aircraft impacted roughly one thousand feet above sea level on a Blue Ridge ridgeline.
- The pilot did not hold an instrument flight rules (IFR) rating despite weather requiring one.
- Audie Murphy was forty-five years old at the time of the crash.
- Murphy enlisted June 30, 1942 (service record lists false birth year 1924) and returned from WWII in September 1945 with a fifty-percent disability rating.

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/73097121Tue, 13 Oct 2026 08:00:03 +0000Creator at ObomediaAudie Murphy's Last Flight: How a Fog Bank Killed a Legend A decorated war hero who survived Sicily, Anzio, and a burning tank destroyer died not on a battlefield but when his Aero Commander six-eighty flew into a mountain in zero visibility; the...
A decorated war hero who survived Sicily, Anzio, and a burning tank destroyer died not on a battlefield but when his Aero Commander six-eighty flew into a mountain in zero visibility; the pilot held no instrument rating and six people on board were killed - so how did a man who survived so much perish in a Virginia fog bank? What did the wreckage reveal, and what crucial questions remain about that final flight?

In this episode, we tell the life story of Audie Leon Murphy alongside the facts of the crash that ended his life and the gaps investigators could not fully close. We trace his rise from a fifth-grade school dropout in Kingston, Texas to the most decorated American soldier of World War II, and we return to the mountain ridge northwest of Roanoke to ask why the flight went on in conditions that required an instrument rating.

Date: May 28, 1971
Location: Fourteen nautical miles northwest of Roanoke, Virginia
Aircraft: Aero Commander 680 (twin-engine)
Passengers on board: Six
Victim: Audie Leon Murphy, born June 20, 1925

- Visibility at the crash site was reported as zero with clouds on the ridgeline and rain falling.
- The aircraft impacted roughly one thousand feet above sea level on a Blue Ridge ridgeline.
- The pilot did not hold an instrument flight rules (IFR) rating despite weather requiring one.
- Audie Murphy was forty-five years old at the time of the crash.
- Murphy enlisted June 30, 1942 (service record lists false birth year 1924) and returned from WWII in September 1945 with a fifty-percent disability rating.

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.]]>1081falsefullhttps://www.spreaker.com/episode/champagne-tony-s-last-landing-ran-out-of-fuel-short-of-runway--73097115
A celebrated golfer landed not on a green but in a water hazard when his twin‑engine Beechcraft Bonanza ran out of fuel less than a mile from Lansing Municipal Airport on July 24, 1966 - four people died and there was no mechanical failure. How did a routine 300‑mile hop end with engines quitting short of the runway?

In this episode, we tell the facts of that afternoon and trace Tony Lema’s journey from East Oakland caddie to twelve‑time Tour winner, ending with the fatal flight that followed a championship weekend. What decisions and oversights led to the aircraft exhausting its fuel so close to its destination?

Person: Anthony David Lema
Date: July 24, 1966
Location: Lansing Municipal Airport vicinity, Illinois
Event: Aircraft ran out of fuel and crashed in a water hazard
Passengers: Four people on board, all killed

- The plane crossed the Illinois state line with its tanks nearly dry and was less than a mile from Lansing Municipal Airport when the engines quit.
- The crash occurred in a water hazard short of the seventh green, less than half a mile from where the pilot intended to land.
- Tony Lema was born February 25, 1934, in East Oakland and lost his father in 1937 at age three.
- By summer 1966 Lema was thirty‑two years old with twelve official PGA Tour victories and had just flown from Akron, Ohio after the PGA Championship.
- The Beechcraft Bonanza was owned by Wylie Mullen and Dr. George Bard; Doris Mullen was pilot in command and Dr. Bard occupied the right seat as copilot.

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/73097115Mon, 12 Oct 2026 08:00:04 +0000Creator at ObomediaChampagne Tony's Last Landing: Ran Out of Fuel Short of Runway A celebrated golfer landed not on a green but in a water hazard when his twin‑engine Beechcraft Bonanza ran out of fuel less than a mile from Lansing Municipal Airport on July 24, 1966...
A celebrated golfer landed not on a green but in a water hazard when his twin‑engine Beechcraft Bonanza ran out of fuel less than a mile from Lansing Municipal Airport on July 24, 1966 - four people died and there was no mechanical failure. How did a routine 300‑mile hop end with engines quitting short of the runway?

In this episode, we tell the facts of that afternoon and trace Tony Lema’s journey from East Oakland caddie to twelve‑time Tour winner, ending with the fatal flight that followed a championship weekend. What decisions and oversights led to the aircraft exhausting its fuel so close to its destination?

Person: Anthony David Lema
Date: July 24, 1966
Location: Lansing Municipal Airport vicinity, Illinois
Event: Aircraft ran out of fuel and crashed in a water hazard
Passengers: Four people on board, all killed

- The plane crossed the Illinois state line with its tanks nearly dry and was less than a mile from Lansing Municipal Airport when the engines quit.
- The crash occurred in a water hazard short of the seventh green, less than half a mile from where the pilot intended to land.
- Tony Lema was born February 25, 1934, in East Oakland and lost his father in 1937 at age three.
- By summer 1966 Lema was thirty‑two years old with twelve official PGA Tour victories and had just flown from Akron, Ohio after the PGA Championship.
- The Beechcraft Bonanza was owned by Wylie Mullen and Dr. George Bard; Doris Mullen was pilot in command and Dr. Bard occupied the right seat as copilot.

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.]]>1054falsefullhttps://www.spreaker.com/episode/the-lecture-that-never-happened-the-mind-lost-on-flight-427--73097111
A respected neuroscientist who had traced a complete neural circuit was aboard a routine flight that became a thirty-second descent into death; all 132 people died when the Boeing 737 struck the ground at about 300 mph. What exactly did Walter Heiligenberg carry in his head - and what was lost when the lecture he planned to give was silenced forever?

In this episode, we tell who Walter Heiligenberg was and what his work on weakly electric fish had achieved, the circumstances of USAir Flight 427’s final approach, and the immediate facts the NTSB found at the crash site; could the loss of one lecture erase a decisive step toward closing the gap between sensory input and motor output in vertebrate neuroscience?

Person: Walter Heiligenberg
Date: September 8, 1994
Event: USAir Flight 427 crash on final approach to Pittsburgh International Airport
Location: near Hopewell Township, Pennsylvania
Fatalities: 132

- Heiligenberg was 56 years old when he boarded USAir Flight 427.
- The Boeing 737 entered an uncontrolled roll and struck the ground in less than 30 seconds.
- The aircraft impacted at approximately 300 miles per hour.
- The crash killed all 132 people aboard; there were no survivors.
- Heiligenberg had mapped the neural circuitry behind the Jamming Avoidance Response in Eigenmannia, a weakly electric fish.

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/73097111Sun, 11 Oct 2026 08:00:03 +0000Creator at ObomediaThe Lecture That Never Happened: The Mind Lost on Flight 427 A respected neuroscientist who had traced a complete neural circuit was aboard a routine flight that became a thirty-second descent into death; all 132 people died when the Boeing 737...
A respected neuroscientist who had traced a complete neural circuit was aboard a routine flight that became a thirty-second descent into death; all 132 people died when the Boeing 737 struck the ground at about 300 mph. What exactly did Walter Heiligenberg carry in his head - and what was lost when the lecture he planned to give was silenced forever?

In this episode, we tell who Walter Heiligenberg was and what his work on weakly electric fish had achieved, the circumstances of USAir Flight 427’s final approach, and the immediate facts the NTSB found at the crash site; could the loss of one lecture erase a decisive step toward closing the gap between sensory input and motor output in vertebrate neuroscience?

Person: Walter Heiligenberg
Date: September 8, 1994
Event: USAir Flight 427 crash on final approach to Pittsburgh International Airport
Location: near Hopewell Township, Pennsylvania
Fatalities: 132

- Heiligenberg was 56 years old when he boarded USAir Flight 427.
- The Boeing 737 entered an uncontrolled roll and struck the ground in less than 30 seconds.
- The aircraft impacted at approximately 300 miles per hour.
- The crash killed all 132 people aboard; there were no survivors.
- Heiligenberg had mapped the neural circuitry behind the Jamming Avoidance Response in Eigenmannia, a weakly electric fish.

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.]]>922falsefullhttps://www.spreaker.com/episode/the-cessna-in-the-dark-who-was-mark-gietzen--73097108
Fear and meticulous obsession collide: a lone Cessna 172 went down over Nebraska on May 14, 2023, sat undiscovered for two days, and carried a 69-year-old pilot whose life was defined by forty-five years of anti-abortion activism - and a nearly $120,000 recount that changed fewer than 70 votes. What ties a lifetime of roadside crosses and political campaigns to an airplane found in the dark?

In this episode, we lay out the facts of Mark Gietzen Gietzen’s life and death, tracing his work from Boeing auditor to decades of protest and political organizing, and the final months when a costly recount and dwindling maintenance funds intersected with his private aviation. How did the ledger of his public campaigns meet the maintenance logs of his Cessna?

Person: Mark Gietzen Gietzen
Date: May 14, 2023
Age: 69
Event: Cessna 172 crash over Nebraska; wreckage found after two days
Recount cost: nearly $120,000; vote shift: fewer than 70 votes

- Born February 9, 1954 in Wichita, Kansas.
- Began protesting outside Dr. George Tiller’s clinic in 1978 and continued for 45 years.
- Served as chair of the Sedgwick County State Party starting August 13, 1992.
- Spent nearly $120,000 on a recount of the Value Them Both amendment that ultimately changed fewer than 70 votes.
- Worked as a procurement quality auditor at Boeing before and during his political activism.

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/73097108Sat, 10 Oct 2026 08:00:03 +0000Creator at ObomediaThe Cessna in the Dark: Who Was Mark Gietzen? Fear and meticulous obsession collide: a lone Cessna 172 went down over Nebraska on May 14, 2023, sat undiscovered for two days, and carried a 69-year-old pilot whose life was defined by forty-five...
Fear and meticulous obsession collide: a lone Cessna 172 went down over Nebraska on May 14, 2023, sat undiscovered for two days, and carried a 69-year-old pilot whose life was defined by forty-five years of anti-abortion activism - and a nearly $120,000 recount that changed fewer than 70 votes. What ties a lifetime of roadside crosses and political campaigns to an airplane found in the dark?

In this episode, we lay out the facts of Mark Gietzen Gietzen’s life and death, tracing his work from Boeing auditor to decades of protest and political organizing, and the final months when a costly recount and dwindling maintenance funds intersected with his private aviation. How did the ledger of his public campaigns meet the maintenance logs of his Cessna?

Person: Mark Gietzen Gietzen
Date: May 14, 2023
Age: 69
Event: Cessna 172 crash over Nebraska; wreckage found after two days
Recount cost: nearly $120,000; vote shift: fewer than 70 votes

- Born February 9, 1954 in Wichita, Kansas.
- Began protesting outside Dr. George Tiller’s clinic in 1978 and continued for 45 years.
- Served as chair of the Sedgwick County State Party starting August 13, 1992.
- Spent nearly $120,000 on a recount of the Value Them Both amendment that ultimately changed fewer than 70 votes.
- Worked as a procurement quality auditor at Boeing before and during his political activism.

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.]]>925falsefullhttps://www.spreaker.com/episode/the-plane-that-warned-us-united-585-s-silent-final-minutes--73097104
A chilling repeat: the same Boeing 737 that crashed into Widefield Park at 245 mph on March 3, 1991 had exhibited the identical sudden right roll six days earlier - and still flew again. How did a warning go unread, five flight parameters record only partial data, and twenty-five people end up trapped beneath fifteen feet of dirt?

In this episode, we lay out the factual timeline and the investigative gaps surrounding United Flight 585, describing the crew, the aircraft history, the weather and the final recorder traces - and we ask what one missing recorder parameter revealed about aviation safety and human cost.

Date: March 3, 1991
Location: Widefield Park, Colorado Springs
Aircraft: Boeing 737, tail N999UA, serial 22742
People on board: 25
Flight hours (airframe): 26,050 hours

- The aircraft struck the ground at 245 miles per hour and buried itself 15 feet into Widefield Park.
- The Boeing 737 had recorded 19,734 pressurization cycles by the accident date.
- The flight data recorder captured only five parameters: heading, altitude, airspeed, normal acceleration, and microphone keying.
- At 09:43:33 the heading rate changed by 5 degrees per second, indicating a sudden violent right rotation.
- The cockpit voice recorder captured the final audible words from First Officer Patricia Eidson: "Oh God."

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/73097104Fri, 09 Oct 2026 08:00:03 +0000Creator at ObomediaThe Plane That Warned Us: United 585's Silent Final Minutes A chilling repeat: the same Boeing 737 that crashed into Widefield Park at 245 mph on March 3, 1991 had exhibited the identical sudden right roll six days earlier - and still flew again....
A chilling repeat: the same Boeing 737 that crashed into Widefield Park at 245 mph on March 3, 1991 had exhibited the identical sudden right roll six days earlier - and still flew again. How did a warning go unread, five flight parameters record only partial data, and twenty-five people end up trapped beneath fifteen feet of dirt?

In this episode, we lay out the factual timeline and the investigative gaps surrounding United Flight 585, describing the crew, the aircraft history, the weather and the final recorder traces - and we ask what one missing recorder parameter revealed about aviation safety and human cost.

Date: March 3, 1991
Location: Widefield Park, Colorado Springs
Aircraft: Boeing 737, tail N999UA, serial 22742
People on board: 25
Flight hours (airframe): 26,050 hours

- The aircraft struck the ground at 245 miles per hour and buried itself 15 feet into Widefield Park.
- The Boeing 737 had recorded 19,734 pressurization cycles by the accident date.
- The flight data recorder captured only five parameters: heading, altitude, airspeed, normal acceleration, and microphone keying.
- At 09:43:33 the heading rate changed by 5 degrees per second, indicating a sudden violent right rotation.
- The cockpit voice recorder captured the final audible words from First Officer Patricia Eidson: "Oh God."

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.]]>1004falsefullhttps://www.spreaker.com/episode/a-rain-dampened-stall-speed-rose-fast-enough-to-strangle-takeoff--74743274
A Rain-Dampened Stall Speed Rose Fast Enough to Strangle Takeoff

In this episode, we follow the flight plan, decisions, and conditions that led a small single-engine Cessna to depart Cheyenne Regional Airport into heavy rain. The narrative traces who was aboard, how the trip was organized, and the technical and regulatory details that shaped those final minutes - and asks whether those choices made the takeoff survivable.

Person: Jessica Whitney Dubroff, age seven
Person: Lloyd Dubroff, age fifty-seven
Person: Joe Reid, flight instructor and pilot
Date: April 11, 1996; departure 08:24
Aircraft: 1975 Cessna 177B Cardinal, registration N35207

- The flight was publicized nationwide with media briefings, ABC providing a camera and souvenir apparel prepared for a coast-to-coast "Sea to Shining Sea" journey.
- Jessica had logged 33+ hours of flight time and trained with dual controls, but held no FAA medical, student, or pilot certificate.
- Joe Reid filed a VFR flight plan despite contacting a weather briefer who confirmed deteriorating conditions and an ATC declaration of IFR at Cheyenne.
- The aircraft departed overweight by 96 pounds with four people's luggage aboard, and rain increased stall speed by about 1.5%.
- Takeoff performance: a high nose attitude, slow climb, gradual right turn, then a near-vertical descent less than a mile from the runway threshold.

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/74743274Thu, 08 Oct 2026 08:00:03 +0000Creator at ObomediaA seven-year-old pilots a Cessna into a rain-soaked takeoff at Cheyenne-will the pilot’s plan survive worsening weather and rising stall speed? A Rain-Dampened Stall Speed Rose Fast Enough to Strangle Takeoff In this episode, we follow the...
A Rain-Dampened Stall Speed Rose Fast Enough to Strangle Takeoff

In this episode, we follow the flight plan, decisions, and conditions that led a small single-engine Cessna to depart Cheyenne Regional Airport into heavy rain. The narrative traces who was aboard, how the trip was organized, and the technical and regulatory details that shaped those final minutes - and asks whether those choices made the takeoff survivable.

Person: Jessica Whitney Dubroff, age seven
Person: Lloyd Dubroff, age fifty-seven
Person: Joe Reid, flight instructor and pilot
Date: April 11, 1996; departure 08:24
Aircraft: 1975 Cessna 177B Cardinal, registration N35207

- The flight was publicized nationwide with media briefings, ABC providing a camera and souvenir apparel prepared for a coast-to-coast "Sea to Shining Sea" journey.
- Jessica had logged 33+ hours of flight time and trained with dual controls, but held no FAA medical, student, or pilot certificate.
- Joe Reid filed a VFR flight plan despite contacting a weather briefer who confirmed deteriorating conditions and an ATC declaration of IFR at Cheyenne.
- The aircraft departed overweight by 96 pounds with four people's luggage aboard, and rain increased stall speed by about 1.5%.
- Takeoff performance: a high nose attitude, slow climb, gradual right turn, then a near-vertical descent less than a mile from the runway threshold.

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.]]>837falsefullhttps://www.spreaker.com/episode/who-was-the-woman-in-that-plane--73097101
She was one of the most photographed women in America and yet left no public voice: Carolyn Bessette-Kennedy gave zero interviews during her marriage and vanished with John F. Kennedy Jr. when their Piper Saratoga struck the Atlantic on July 16, 1999 - so who was she, really, beyond the images taken of her? What private life did those images hide?

In this episode, we tell the documented timeline of Carolyn’s life from White Plains to the Tribeca loft and the wedding on Cumberland Island, describe how publicity shaped her final years, and pose the central question the record cannot answer: who did she choose to be when no one else could name her?

Person: Carolyn Ann Bessette-Kennedy
Date: January 7, 1966 (birth); July 16, 1999 (crash)
Location: White Plains, New York (birth); Tribeca, New York (residence); Atlantic Ocean off Martha's Vineyard (ashes scattered)
Event: Piper Saratoga took off from Essex County Airport at 8:38 PM and never landed
Occupation: Director of show production at Calvin Klein, salary in the low six figures

- The Piper Saratoga departed Essex County Airport, New Jersey, at 8:38 PM on July 16, 1999.
- Carolyn was thirty-three years old at the time of the crash.
- She graduated from St. Mary's High School in Greenwich in 1983 and from Boston University in January 1988.
- She married John F. Kennedy Jr. on September 21, 1996, on Cumberland Island, Georgia, with roughly forty guests.
- Six days after the crash, the U.S. Navy scattered her ashes, and those of her husband and sister-in-law, from the deck of the USS Briscoe off Martha's Vineyard.

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/73097101Thu, 08 Oct 2026 08:00:03 +0000Creator at ObomediaWho was the woman in that plane? She was one of the most photographed women in America and yet left no public voice: Carolyn Bessette-Kennedy gave zero interviews during her marriage and vanished with John F. Kennedy Jr. when their Piper Saratoga...
She was one of the most photographed women in America and yet left no public voice: Carolyn Bessette-Kennedy gave zero interviews during her marriage and vanished with John F. Kennedy Jr. when their Piper Saratoga struck the Atlantic on July 16, 1999 - so who was she, really, beyond the images taken of her? What private life did those images hide?

In this episode, we tell the documented timeline of Carolyn’s life from White Plains to the Tribeca loft and the wedding on Cumberland Island, describe how publicity shaped her final years, and pose the central question the record cannot answer: who did she choose to be when no one else could name her?

Person: Carolyn Ann Bessette-Kennedy
Date: January 7, 1966 (birth); July 16, 1999 (crash)
Location: White Plains, New York (birth); Tribeca, New York (residence); Atlantic Ocean off Martha's Vineyard (ashes scattered)
Event: Piper Saratoga took off from Essex County Airport at 8:38 PM and never landed
Occupation: Director of show production at Calvin Klein, salary in the low six figures

- The Piper Saratoga departed Essex County Airport, New Jersey, at 8:38 PM on July 16, 1999.
- Carolyn was thirty-three years old at the time of the crash.
- She graduated from St. Mary's High School in Greenwich in 1983 and from Boston University in January 1988.
- She married John F. Kennedy Jr. on September 21, 1996, on Cumberland Island, Georgia, with roughly forty guests.
- Six days after the crash, the U.S. Navy scattered her ashes, and those of her husband and sister-in-law, from the deck of the USS Briscoe off Martha's Vineyard.

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.]]>1105falsefullhttps://www.spreaker.com/episode/the-flaps-stayed-up-the-clock-ran-out-before-they-could-stop-the-roll--74743272
The flaps stayed up - the clock ran out before they could stop the roll

In this episode, we follow the final minutes before Northwest Airlines Flight 255's takeoff and the sequence of choices, checks, and mechanical realities that set the stage for disaster. The narrative traces crew experience, aircraft status, and the moments of confusion that left questions investigators unable to fully close.

Date: August 16, 1987
Aircraft: McDonnell Douglas MD-82 (N312RC)
Flight: Northwest Airlines Flight 255
Location: Detroit Metropolitan Airport, runway 3C
People onboard: 154 (150 passengers, 4 crew survivors count unresolved in transcript)

- Captain John R. Maus (57) had 30,859 hours total and was known for strict adherence to procedure.
- First Officer David J. Dodds (35) had 8,044 hours total, 1,600 on the MD-82, and a record of proactively reporting issues.
- The taxi checklist that should have confirmed flap and slat extension was not completed before the takeoff roll.
- The crew had prepared performance data for runways 21L/21R but instead departed from the shorter runway 3C, prompting an in-taxi recalculation.
- Investigators focused on a small circuit breaker whose condition that night remained undetermined and central to explaining why no warning reached the cockpit.

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/74743272Wed, 07 Oct 2026 08:00:03 +0000Creator at ObomediaA heavily loaded MD‑82 lifts off Detroit with its flaps still retracted - the pilots have seconds to stop a roll. Who lives? The flaps stayed up - the clock ran out before they could stop the roll In this episode, we follow the final minutes...
The flaps stayed up - the clock ran out before they could stop the roll

In this episode, we follow the final minutes before Northwest Airlines Flight 255's takeoff and the sequence of choices, checks, and mechanical realities that set the stage for disaster. The narrative traces crew experience, aircraft status, and the moments of confusion that left questions investigators unable to fully close.

Date: August 16, 1987
Aircraft: McDonnell Douglas MD-82 (N312RC)
Flight: Northwest Airlines Flight 255
Location: Detroit Metropolitan Airport, runway 3C
People onboard: 154 (150 passengers, 4 crew survivors count unresolved in transcript)

- Captain John R. Maus (57) had 30,859 hours total and was known for strict adherence to procedure.
- First Officer David J. Dodds (35) had 8,044 hours total, 1,600 on the MD-82, and a record of proactively reporting issues.
- The taxi checklist that should have confirmed flap and slat extension was not completed before the takeoff roll.
- The crew had prepared performance data for runways 21L/21R but instead departed from the shorter runway 3C, prompting an in-taxi recalculation.
- Investigators focused on a small circuit breaker whose condition that night remained undetermined and central to explaining why no warning reached the cockpit.

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.]]>1129falsefullhttps://www.spreaker.com/episode/fourteen-seconds-how-a-small-plane-sheared-a-dc-9-s-tail--73097099
Fear of sudden, catastrophic collision: a DC‑9 lost its entire tail assembly and eighty‑three people died in fourteen seconds after a small Piper Cherokee and a commercial airliner occupied the same cubic feet of sky. The Cherokee left no usable transponder signal, controllers saw a clear sky, and the tail was found intact 300 feet from the rest of the aircraft - so what chain of assumptions allowed two planes to collide unseen?

In this episode, we recount the sequence of events on that afternoon and describe who was where, what equipment they had, and how the airspace rules left a gap between private pilots and airliners; could the belief in see‑and‑avoid have been the fatal error?

Date: September 9, 1986
Event: Midair collision resulting in tail assembly separation
Location: Near Shelbyville, Indiana (tail found in a soybean field)
Aircraft 1: McDonnell Douglas DC‑9 (Aeromexico Flight 648 / Flight 686 in LA segment)
Aircraft 2: Piper PA‑28 Cherokee (pilot Robert Carey, age 34)
Fatalities: 83

- Tail assembly discovered sitting in a soybean field 300 feet from the nearest piece of the aircraft it had been attached to.
- Entire tail was sheared clean, not bent or scorched, and found intact in the dirt.
- Eighty‑three people died in a period investigators describe as fourteen seconds.
- Piper Cherokee was not equipped with an altitude‑encoding transponder and produced no usable primary radar target at the relevant moment.
- Captain Theodore Elrod had 23,800 flight hours and was commanding the DC‑9 carrying 77 passengers and a crew of five on the flight segment described.

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/73097099Wed, 07 Oct 2026 08:00:02 +0000Creator at ObomediaFourteen Seconds: How a Small Plane Sheared a DC‑9's Tail Fear of sudden, catastrophic collision: a DC‑9 lost its entire tail assembly and eighty‑three people died in fourteen seconds after a small Piper Cherokee and a commercial airliner occupied...
Fear of sudden, catastrophic collision: a DC‑9 lost its entire tail assembly and eighty‑three people died in fourteen seconds after a small Piper Cherokee and a commercial airliner occupied the same cubic feet of sky. The Cherokee left no usable transponder signal, controllers saw a clear sky, and the tail was found intact 300 feet from the rest of the aircraft - so what chain of assumptions allowed two planes to collide unseen?

In this episode, we recount the sequence of events on that afternoon and describe who was where, what equipment they had, and how the airspace rules left a gap between private pilots and airliners; could the belief in see‑and‑avoid have been the fatal error?

Date: September 9, 1986
Event: Midair collision resulting in tail assembly separation
Location: Near Shelbyville, Indiana (tail found in a soybean field)
Aircraft 1: McDonnell Douglas DC‑9 (Aeromexico Flight 648 / Flight 686 in LA segment)
Aircraft 2: Piper PA‑28 Cherokee (pilot Robert Carey, age 34)
Fatalities: 83

- Tail assembly discovered sitting in a soybean field 300 feet from the nearest piece of the aircraft it had been attached to.
- Entire tail was sheared clean, not bent or scorched, and found intact in the dirt.
- Eighty‑three people died in a period investigators describe as fourteen seconds.
- Piper Cherokee was not equipped with an altitude‑encoding transponder and produced no usable primary radar target at the relevant moment.
- Captain Theodore Elrod had 23,800 flight hours and was commanding the DC‑9 carrying 77 passengers and a crew of five on the flight segment described.

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.]]>1108falsefullhttps://www.spreaker.com/episode/the-elt-sat-in-fairbanks-and-kept-rescuers-from-him--74743271
The ELT sat in Fairbanks and kept rescuers from him

In this episode, we follow the October 16, 1972 flight from Anchorage toward Juneau that vanished without a trace and explore how the missing emergency locator transmitter shaped the massive 39-day search. What did investigators find, and how could a plane carrying Nick Begich and Hale Boggs disappear with no wreckage, no signal, and no answers?

Date: October 16, 1972
Person: Nick Begich
Person: Hale Boggs
Event: 39-day multi-service search
Location: Anchorage to Juneau, Alaska

- A twin-engine Cessna 310 departed Anchorage bound for Juneau carrying Nick Begich, Hale Boggs, aide Russell Brown, and pilot Don Jonz.
- Alaska’s statute requiring portable emergency locator transmitters had taken effect five weeks earlier, on September 6, 1972.
- Investigators later found Don Jonz’s ELT inside a different aircraft parked at Fairbanks International Airport, and the NTSB concluded neither the pilot nor the plane carried an ELT.
- Coast Guard aircraft were airborne the afternoon of October 16; within days the Navy, Army, Air Force, Civil Air Patrol, and private pilots joined a growing search.
- After 39 days of searching Chugach Mountains, coastal passes and Gulf waters, no wreckage, no remains, and no ELT signal were ever recorded.

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/74743271Tue, 06 Oct 2026 08:00:03 +0000Creator at ObomediaA congressman flies to a Juneau fundraiser - did rescuers miss them because the emergency transmitter wasn’t aboard? The ELT sat in Fairbanks and kept rescuers from him In this episode, we follow the October 16, 1972 flight from Anchorage toward...
The ELT sat in Fairbanks and kept rescuers from him

In this episode, we follow the October 16, 1972 flight from Anchorage toward Juneau that vanished without a trace and explore how the missing emergency locator transmitter shaped the massive 39-day search. What did investigators find, and how could a plane carrying Nick Begich and Hale Boggs disappear with no wreckage, no signal, and no answers?

Date: October 16, 1972
Person: Nick Begich
Person: Hale Boggs
Event: 39-day multi-service search
Location: Anchorage to Juneau, Alaska

- A twin-engine Cessna 310 departed Anchorage bound for Juneau carrying Nick Begich, Hale Boggs, aide Russell Brown, and pilot Don Jonz.
- Alaska’s statute requiring portable emergency locator transmitters had taken effect five weeks earlier, on September 6, 1972.
- Investigators later found Don Jonz’s ELT inside a different aircraft parked at Fairbanks International Airport, and the NTSB concluded neither the pilot nor the plane carried an ELT.
- Coast Guard aircraft were airborne the afternoon of October 16; within days the Navy, Army, Air Force, Civil Air Patrol, and private pilots joined a growing search.
- After 39 days of searching Chugach Mountains, coastal passes and Gulf waters, no wreckage, no remains, and no ELT signal were ever recorded.

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.]]>909falsefullhttps://www.spreaker.com/episode/when-computers-said-descend-a-father-s-revenge-after-midair-collapse--73097098
A father’s grief turned to fury after 71 people - including 52 children - died when two planes collided over southern Germany at nearly 900 km/h. Multiple safety systems had failed, been switched off, or were ignored in the final 60 seconds, and the Tupolev’s on-board computer had correctly told the crew to climb - so why was that command overruled? What did a lone controller do in the last minute that changed everything?

In this episode, we follow the delayed school trip from Ufa, the experienced five-person Tupolev crew, the DHL crew climbing to conserve fuel, and a single air traffic controller managing a degraded Zürich sector as two tracks closed above Lake Constance. We trace how each failed system and a conflicting radio instruction set the stage for catastrophe, and ask what happened next when a grieving father took the legal fight into his own hands.

Event: Midair collision
Date: July 1, 2002
Location: Southern Germany / over Lake Constance
Fatalities: 71
Children killed: 52

- Collision occurred at 23:35:32 on July 1, 2002 at nearly 900 km/h.
- Tupolev Tu-154 (Flight 2937, registration RA-85816) departed Domodedovo at 22:22 Moscow time with 60 passengers and 9 crew.
- DHL Boeing 757 (Flight 611, registration A9C-DHL) departed Bergamo at 23:06 CEST, carrying no passengers.
- Traffic Collision Avoidance System on the Tupolev issued a CLIMB advisory 43 seconds before the collision.
- The Zurich Area Control primary radar had gone offline earlier; fallback systems, a switched-off ground collision warning, and a muted aural alert all contributed in the final minute.

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/73097098Tue, 06 Oct 2026 08:00:03 +0000Creator at ObomediaWhen Computers Said 'Descend' - A Father's Revenge After Midair Collapse A father’s grief turned to fury after 71 people - including 52 children - died when two planes collided over southern Germany at nearly 900 km/h. Multiple safety systems had...
A father’s grief turned to fury after 71 people - including 52 children - died when two planes collided over southern Germany at nearly 900 km/h. Multiple safety systems had failed, been switched off, or were ignored in the final 60 seconds, and the Tupolev’s on-board computer had correctly told the crew to climb - so why was that command overruled? What did a lone controller do in the last minute that changed everything?

In this episode, we follow the delayed school trip from Ufa, the experienced five-person Tupolev crew, the DHL crew climbing to conserve fuel, and a single air traffic controller managing a degraded Zürich sector as two tracks closed above Lake Constance. We trace how each failed system and a conflicting radio instruction set the stage for catastrophe, and ask what happened next when a grieving father took the legal fight into his own hands.

Event: Midair collision
Date: July 1, 2002
Location: Southern Germany / over Lake Constance
Fatalities: 71
Children killed: 52

- Collision occurred at 23:35:32 on July 1, 2002 at nearly 900 km/h.
- Tupolev Tu-154 (Flight 2937, registration RA-85816) departed Domodedovo at 22:22 Moscow time with 60 passengers and 9 crew.
- DHL Boeing 757 (Flight 611, registration A9C-DHL) departed Bergamo at 23:06 CEST, carrying no passengers.
- Traffic Collision Avoidance System on the Tupolev issued a CLIMB advisory 43 seconds before the collision.
- The Zurich Area Control primary radar had gone offline earlier; fallback systems, a switched-off ground collision warning, and a muted aural alert all contributed in the final minute.

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.]]>904falsefullhttps://www.spreaker.com/episode/the-forty-two-minute-delay-that-let-the-hijackers-strike-in-time--74743270
The forty‑two‑minute delay that let the hijackers strike in time

In this episode, we trace United Airlines Flight 93 from its delayed pushback through the moments the cockpit was breached and passengers faced an impossible choice. We map the timeline, the people on board, and the decisions that unfolded at thirty-five thousand feet - what did that forty-two‑minute delay change?

Flight: United Airlines Flight 93
Date: September 11, 2001
Departure airport: Newark Liberty International Airport
Delay: 42 minutes (pushback at 8:42 AM)
Cockpit crew: Captain Jason Dahl; First Officer LeRoy Homer Jr.

- The flight was scheduled to depart at 8:00 AM but did not push back until 8:42 AM due to airport congestion.
- Captain Jason Dahl and First Officer LeRoy Homer Jr. brought decades of disciplined flight experience to the cockpit that morning.
- Ziad Jarrah, seated in first class with a pilot’s license and flight training, entered the cockpit after it was breached at about 9:26 AM.
- A mistaken radio transmission at 9:31 AM meant Jarrah’s announcement to passengers was heard by Cleveland Center instead of the cabin.
- Thirty‑one minutes of choices by the passengers and crew at altitude were recorded on a cockpit voice recorder that remains unreleased to the public.

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/74743270Mon, 05 Oct 2026 08:00:03 +0000Creator at ObomediaA Newark-San Francisco flight is hijacked midair with minutes to spare - did the passengers make it in time? The forty‑two‑minute delay that let the hijackers strike in time In this episode, we trace United Airlines Flight 93 from its delayed...
The forty‑two‑minute delay that let the hijackers strike in time

In this episode, we trace United Airlines Flight 93 from its delayed pushback through the moments the cockpit was breached and passengers faced an impossible choice. We map the timeline, the people on board, and the decisions that unfolded at thirty-five thousand feet - what did that forty-two‑minute delay change?

Flight: United Airlines Flight 93
Date: September 11, 2001
Departure airport: Newark Liberty International Airport
Delay: 42 minutes (pushback at 8:42 AM)
Cockpit crew: Captain Jason Dahl; First Officer LeRoy Homer Jr.

- The flight was scheduled to depart at 8:00 AM but did not push back until 8:42 AM due to airport congestion.
- Captain Jason Dahl and First Officer LeRoy Homer Jr. brought decades of disciplined flight experience to the cockpit that morning.
- Ziad Jarrah, seated in first class with a pilot’s license and flight training, entered the cockpit after it was breached at about 9:26 AM.
- A mistaken radio transmission at 9:31 AM meant Jarrah’s announcement to passengers was heard by Cleveland Center instead of the cabin.
- Thirty‑one minutes of choices by the passengers and crew at altitude were recorded on a cockpit voice recorder that remains unreleased to the public.

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.]]>958falsefullhttps://www.spreaker.com/episode/when-10-004-hours-failed-the-flight-that-shouldn-t-have-fallen--73097095
A routine mountain hop became a mechanical chain reaction: a turboprop rolled inverted and fell 5,100 feet in 24 seconds after three separate failures combined - one engine had 10,004.1 flight hours, above the manufacturer's 10,000-hour fracture-risk threshold. How did a blade inspection in Karachi 93 hours earlier and a service bulletin from October 2015 fail to prevent this disaster?

In this episode, you will hear the documented record of the flight, the sequence of warnings and resets, and the investigative findings that followed, as we follow how the crew responded and why existing procedures proved insufficient. What precisely unfolded in the four minutes after the Mayday that no ATR had ever faced?

Event: Pakistan International Airlines Flight 661
Date: 7 December 2016
Location: Khyber Pakhtunkhwa, Pakistan
Aircraft: ATR 42-500, registration AP-BHO
Fatalities: 47 aboard

- Aircraft departed Chitral at 15:38 local time after an 8-minute delay from scheduled 15:30.
- Left-engine turbine blades had accumulated 10,004.1 flight hours at departure.
- Manufacturer's fracture-risk threshold for those blades was 10,000 flight hours.
- PEC-1 alert illuminated three minutes into flight; crew reset it three times before switching PEC off.
- Aircraft rolled inverted and descended 5,100 feet in 24 seconds after left propeller exceeded 102% and aerodynamic condition became unrecoverable.

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/73097095Mon, 05 Oct 2026 08:00:03 +0000Creator at ObomediaWhen 10,004 Hours Failed: The Flight That Shouldn't Have Fallen A routine mountain hop became a mechanical chain reaction: a turboprop rolled inverted and fell 5,100 feet in 24 seconds after three separate failures combined - one engine had...
A routine mountain hop became a mechanical chain reaction: a turboprop rolled inverted and fell 5,100 feet in 24 seconds after three separate failures combined - one engine had 10,004.1 flight hours, above the manufacturer's 10,000-hour fracture-risk threshold. How did a blade inspection in Karachi 93 hours earlier and a service bulletin from October 2015 fail to prevent this disaster?

In this episode, you will hear the documented record of the flight, the sequence of warnings and resets, and the investigative findings that followed, as we follow how the crew responded and why existing procedures proved insufficient. What precisely unfolded in the four minutes after the Mayday that no ATR had ever faced?

Event: Pakistan International Airlines Flight 661
Date: 7 December 2016
Location: Khyber Pakhtunkhwa, Pakistan
Aircraft: ATR 42-500, registration AP-BHO
Fatalities: 47 aboard

- Aircraft departed Chitral at 15:38 local time after an 8-minute delay from scheduled 15:30.
- Left-engine turbine blades had accumulated 10,004.1 flight hours at departure.
- Manufacturer's fracture-risk threshold for those blades was 10,000 flight hours.
- PEC-1 alert illuminated three minutes into flight; crew reset it three times before switching PEC off.
- Aircraft rolled inverted and descended 5,100 feet in 24 seconds after left propeller exceeded 102% and aerodynamic condition became unrecoverable.

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.]]>1117falsefullhttps://www.spreaker.com/episode/the-runway-lights-flickered-on-did-the-sleeping-controller-wake-in-time--74743269
The runway lights flickered on - did the sleeping controller wake in time?

In this episode, we follow the unfolding minutes before a Tupolev Tu-154 attempted to land at Omsk in October 1984. You’ll hear who was on the aircraft, who was on the runway, how procedures and small decisions stacked up - and the question that remained as the plane descended.

Person: Captain Boris Petrovich Stepanov
Date: October 11, 1984
Location: Omsk Airport
Aircraft: Tupolev Tu-154 B-1, manufactured 1977
Person: Ground controller Andrey Borodaenko

- The Tu-154 carried 178 people, was fully loaded, and its crew had no mechanical issues or reason to divert.
- Three maintenance vehicles with up to seven tons of jet fuel each entered the runway at 05:20 under an authorization logged only by Borodaenko.
- Regulations required warning beacons on runway vehicles; the workers switched those lights off because the rotating beacons blinded them in the wet dark.
- At 05:36 runway edge lights activated automatically as the inbound flight approached; maintenance workers attempted to contact ground control multiple times with no answer.
- Borodaenko, the 23-year-old ground controller who had authorized the convoy, closed his eyes and fell asleep in the tower while instruments continued to show the runway clear.

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/74743269Sun, 04 Oct 2026 08:00:03 +0000Creator at ObomediaA Tu-154 closes on Omsk runway as two fuel trucks sit dark below and a 23-year-old ground controller sleeps - did they wake in time? The runway lights flickered on - did the sleeping controller wake in time? In this episode, we follow the...
The runway lights flickered on - did the sleeping controller wake in time?

In this episode, we follow the unfolding minutes before a Tupolev Tu-154 attempted to land at Omsk in October 1984. You’ll hear who was on the aircraft, who was on the runway, how procedures and small decisions stacked up - and the question that remained as the plane descended.

Person: Captain Boris Petrovich Stepanov
Date: October 11, 1984
Location: Omsk Airport
Aircraft: Tupolev Tu-154 B-1, manufactured 1977
Person: Ground controller Andrey Borodaenko

- The Tu-154 carried 178 people, was fully loaded, and its crew had no mechanical issues or reason to divert.
- Three maintenance vehicles with up to seven tons of jet fuel each entered the runway at 05:20 under an authorization logged only by Borodaenko.
- Regulations required warning beacons on runway vehicles; the workers switched those lights off because the rotating beacons blinded them in the wet dark.
- At 05:36 runway edge lights activated automatically as the inbound flight approached; maintenance workers attempted to contact ground control multiple times with no answer.
- Borodaenko, the 23-year-old ground controller who had authorized the convoy, closed his eyes and fell asleep in the tower while instruments continued to show the runway clear.

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.]]>1446falsefullhttps://www.spreaker.com/episode/feathered-propeller-why-clemente-s-plane-knew-it-would-fall--73097089
The propeller from engine number two was recovered feathered on the Atlantic floor - a single mechanical clue that the pilot had recognized the failure and acted, yet the plane still plunged into the sea two minutes and forty-five seconds after takeoff. This episode reveals how a damaged engine, missing required post-impact testing, and an overloaded DC-7 combined into a lethal chain of small failures; how did dozens of preventable errors end with Roberto Clemente’s last flight?

In this episode, we lay out the sequence of events on New Year's Eve 1972, from the earlier taxiway impact to the overweight takeoff at Luis Muñoz Marín International Airport, and follow investigators as they map wreckage across the ocean floor to answer whether the crash was inevitable.

Person: Roberto Clemente Walker
Date: December 31, 1972
Location: Off San Juan, Puerto Rico (Atlantic Ocean)
Aircraft: Douglas DC-7 registration N500AE, built 1957
Overweight: 4,193 pounds over maximum gross takeoff weight

- Flight time from takeoff to impact: 2 minutes and 45 seconds
- Engine number two propeller recovered from ocean floor was feathered
- Plane's maximum gross takeoff weight: 82,852 pounds; reconstructed load exceeded by 4,193 pounds
- Engine number two had been damaged in a taxiway accident 29 days before the crash without required disassembly and magnaflux testing
- Roberto Clemente achieved his 3,000th career hit on September 30, 1972, 92 days before his death

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/73097089Sun, 04 Oct 2026 08:00:03 +0000Creator at ObomediaFeathered Propeller: Why Clemente's Plane Knew It Would Fall The propeller from engine number two was recovered feathered on the Atlantic floor - a single mechanical clue that the pilot had recognized the failure and acted, yet the plane still...
The propeller from engine number two was recovered feathered on the Atlantic floor - a single mechanical clue that the pilot had recognized the failure and acted, yet the plane still plunged into the sea two minutes and forty-five seconds after takeoff. This episode reveals how a damaged engine, missing required post-impact testing, and an overloaded DC-7 combined into a lethal chain of small failures; how did dozens of preventable errors end with Roberto Clemente’s last flight?

In this episode, we lay out the sequence of events on New Year's Eve 1972, from the earlier taxiway impact to the overweight takeoff at Luis Muñoz Marín International Airport, and follow investigators as they map wreckage across the ocean floor to answer whether the crash was inevitable.

Person: Roberto Clemente Walker
Date: December 31, 1972
Location: Off San Juan, Puerto Rico (Atlantic Ocean)
Aircraft: Douglas DC-7 registration N500AE, built 1957
Overweight: 4,193 pounds over maximum gross takeoff weight

- Flight time from takeoff to impact: 2 minutes and 45 seconds
- Engine number two propeller recovered from ocean floor was feathered
- Plane's maximum gross takeoff weight: 82,852 pounds; reconstructed load exceeded by 4,193 pounds
- Engine number two had been damaged in a taxiway accident 29 days before the crash without required disassembly and magnaflux testing
- Roberto Clemente achieved his 3,000th career hit on September 30, 1972, 92 days before his death

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.]]>1072falsefullhttps://www.spreaker.com/episode/the-500-hour-deadline-lapsed-did-2-000-extra-flight-hours-cost-them--74743268
The 500‑hour deadline lapsed - did 2,000 extra flight hours cost them?

In this episode, the story of flight OE‑LAV is laid out: the timeline from a recurring warning light through management decisions to the six fatal minutes after takeoff. What choices, pressures, and technical limits shaped the journey toward that night over the Thai jungle?

Person: Aircraft OE‑LAV (Boeing 767)
Date: May 26, 1991 (departure 23:23 local)
Event: In‑flight breakup six minutes after takeoff near Suphan Buri province
Issue: Left thrust‑reverser fault with a 500‑hour regulatory mitigation window exceeded by ~2,000 hours
Person: Hanns Pekarek (former head of maintenance)

- OE‑LAV first showed an intermittent engine‑indicating fault on December 28, 1990, flagging the left thrust‑reverser.
- Boeing’s maintenance manual allowed continued operation only within a specific 500‑hour window if the thrust‑reverser fault remained unresolved.
- The aircraft accumulated more than two thousand additional flight hours after that 500‑hour window closed on January 25, 1991.
- Hanns Pekarek, Lauda Air’s former head of maintenance, repeatedly raised safety concerns and left the airline eight months before the crash, telling his family not to fly the carrier.
- The cockpit voice recorder survived, the flight data recorder did not, and a cluster of damaged electrical cables inside the left engine strut - a key piece of evidence - was destroyed in the breakup.

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/74743268Sat, 03 Oct 2026 08:00:03 +0000Creator at ObomediaA Boeing 767 with a known thrust‑reverser fault flew past its safety deadline - can investigators piece together what happened six minutes after takeoff? The 500‑hour deadline lapsed - did 2,000 extra flight hours cost them? In this episode, the...
The 500‑hour deadline lapsed - did 2,000 extra flight hours cost them?

In this episode, the story of flight OE‑LAV is laid out: the timeline from a recurring warning light through management decisions to the six fatal minutes after takeoff. What choices, pressures, and technical limits shaped the journey toward that night over the Thai jungle?

Person: Aircraft OE‑LAV (Boeing 767)
Date: May 26, 1991 (departure 23:23 local)
Event: In‑flight breakup six minutes after takeoff near Suphan Buri province
Issue: Left thrust‑reverser fault with a 500‑hour regulatory mitigation window exceeded by ~2,000 hours
Person: Hanns Pekarek (former head of maintenance)

- OE‑LAV first showed an intermittent engine‑indicating fault on December 28, 1990, flagging the left thrust‑reverser.
- Boeing’s maintenance manual allowed continued operation only within a specific 500‑hour window if the thrust‑reverser fault remained unresolved.
- The aircraft accumulated more than two thousand additional flight hours after that 500‑hour window closed on January 25, 1991.
- Hanns Pekarek, Lauda Air’s former head of maintenance, repeatedly raised safety concerns and left the airline eight months before the crash, telling his family not to fly the carrier.
- The cockpit voice recorder survived, the flight data recorder did not, and a cluster of damaged electrical cables inside the left engine strut - a key piece of evidence - was destroyed in the breakup.

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.]]>871falsefullhttps://www.spreaker.com/episode/seconds-over-gander-the-unfinished-mystery-of-flight-1285r--73097088
A cold December morning, a DC-8 carrying 256 people failed to climb after a 51-second takeoff roll and crashed 3,500 feet beyond Gander runway end - leaving a scar visible from satellite decades later. Why did an aircraft that should have climbed instead cross the Trans-Canada Highway at low altitude with witnesses reporting a bright glow - and why did investigators split without a definitive cause?

In this episode, we present the sequence of events, the people on board, the limited flight-recording evidence, and the divided official findings to explore the single question that remains unsettled: what actually happened during those fifty-one seconds?

Date: December 12, 1985
Event: Crash of Arrow Air Flight 1285R
Aircraft: Douglas DC-8
Fatalities: 256
Takeoff roll duration: 51 seconds

- The aircraft crossed the Trans-Canada Highway roughly 900 feet beyond the runway threshold at very low altitude.
- Witnesses reported seeing a bright glow coming from the airplane during the takeoff.
- The flight data recorder recorded only four parameters: airspeed, altitude, heading, and vertical acceleration.
- The cockpit voice recorder contained no usable audio because the cockpit microphone had failed.
- Investigators formed a nine-member board that split with five concluding one cause and four concluding another, later rejected as unsupported by a former Supreme Court justice.

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/73097088Sat, 03 Oct 2026 08:00:03 +0000Creator at ObomediaSeconds Over Gander: The Unfinished Mystery of Flight 1285R A cold December morning, a DC-8 carrying 256 people failed to climb after a 51-second takeoff roll and crashed 3,500 feet beyond Gander runway end - leaving a scar visible from satellite...
A cold December morning, a DC-8 carrying 256 people failed to climb after a 51-second takeoff roll and crashed 3,500 feet beyond Gander runway end - leaving a scar visible from satellite decades later. Why did an aircraft that should have climbed instead cross the Trans-Canada Highway at low altitude with witnesses reporting a bright glow - and why did investigators split without a definitive cause?

In this episode, we present the sequence of events, the people on board, the limited flight-recording evidence, and the divided official findings to explore the single question that remains unsettled: what actually happened during those fifty-one seconds?

Date: December 12, 1985
Event: Crash of Arrow Air Flight 1285R
Aircraft: Douglas DC-8
Fatalities: 256
Takeoff roll duration: 51 seconds

- The aircraft crossed the Trans-Canada Highway roughly 900 feet beyond the runway threshold at very low altitude.
- Witnesses reported seeing a bright glow coming from the airplane during the takeoff.
- The flight data recorder recorded only four parameters: airspeed, altitude, heading, and vertical acceleration.
- The cockpit voice recorder contained no usable audio because the cockpit microphone had failed.
- Investigators formed a nine-member board that split with five concluding one cause and four concluding another, later rejected as unsupported by a former Supreme Court justice.

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.]]>1078falsefullhttps://www.spreaker.com/episode/the-controller-s-severe-wind-shift-warning-came-six-minutes-too-late--74743266
The controller's "Severe wind shift" warning came six minutes too late

In this episode, we follow the final minutes of Eastern Air Lines Flight 66’s routine arrival into JFK amid rapidly deteriorating weather. The episode lays out the crew, the warnings on the frequency, and the chain of decisions that kept the approach going - did they make it in time?

Person: Captain John W. Kleven
Person: First Officer William Eberhart
Person: Flight Engineer Gary M. Geurin
Date: June 24, 1975
Location: John F. Kennedy Airport (Runway 22L)

- Flight 66 departed New Orleans at 13:13 EDT with 124 people aboard and a Boeing 727 configured for a routine New Orleans-JFK route.
- Four men occupied a cockpit designed for three because a flight engineer check ride placed Peter J. McCullough in the jump seat to evaluate Geurin.
- Thunderstorms and heavy rain reduced visibility; by 15:52 approach control advised very light rain and required instrument flight rules.
- At 15:59 the approach controller broadcast "severe wind shift on final approach" to all aircraft on the final-approach frequency.
- Multiple preceding arrivals reported extreme conditions: a Flying Tiger DC‑8 logged "tremendous wind shear on the ground" and an L‑1011 experienced a violent loss and recovery of altitude.

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/74743266Fri, 02 Oct 2026 08:00:05 +0000Creator at ObomediaA Boeing 727 on final to JFK hears a controller warn of a "severe wind shift" six minutes before impact - what happens next? The controller's "Severe wind shift" warning came six minutes too late In this episode, we follow the final minutes of...
The controller's "Severe wind shift" warning came six minutes too late

In this episode, we follow the final minutes of Eastern Air Lines Flight 66’s routine arrival into JFK amid rapidly deteriorating weather. The episode lays out the crew, the warnings on the frequency, and the chain of decisions that kept the approach going - did they make it in time?

Person: Captain John W. Kleven
Person: First Officer William Eberhart
Person: Flight Engineer Gary M. Geurin
Date: June 24, 1975
Location: John F. Kennedy Airport (Runway 22L)

- Flight 66 departed New Orleans at 13:13 EDT with 124 people aboard and a Boeing 727 configured for a routine New Orleans-JFK route.
- Four men occupied a cockpit designed for three because a flight engineer check ride placed Peter J. McCullough in the jump seat to evaluate Geurin.
- Thunderstorms and heavy rain reduced visibility; by 15:52 approach control advised very light rain and required instrument flight rules.
- At 15:59 the approach controller broadcast "severe wind shift on final approach" to all aircraft on the final-approach frequency.
- Multiple preceding arrivals reported extreme conditions: a Flying Tiger DC‑8 logged "tremendous wind shear on the ground" and an L‑1011 experienced a violent loss and recovery of altitude.

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.]]>1364falsefullhttps://www.spreaker.com/episode/when-a-southwest-737-left-the-runway-and-killed-a-child--73097085
Snow, tailwind and a computation that gave the right number for the wrong assumptions converged into a single moment that ended a flawless safety record and a six-year-old boy’s life - how did a routine winter landing turn into a street crash? What invisible assumptions in procedures, training, and on-board systems allowed a Boeing 737 to leave the runway and strike two cars on Central Avenue?

In this episode, we tell the story of Southwest Flight 1248’s December 8, 2005 arrival at Midway Airport and the sequence of decisions, weather, and system assumptions that preceded the accident. We follow the flight from Baltimore to Chicago, the crew’s choice to land on Runway 31C with a tailwind, and the unseen errors that made the aircraft’s stopping calculation misleading - could different information or limits have changed the outcome?

Date: December 8, 2005
Event: Runway overrun onto Central Avenue
Aircraft: Boeing 737-7H4 registered N471WN
Person: Joshua Woods, age six, fatally injured
Location: Midway Airport vicinity, Central Avenue and 55th Street, Chicago

- Time of arrival: approximately 7:15 PM
- Snow on ground: approximately 8 inches across Chicago that week
- Visibility at Midway: under one mile
- Runway 31C length: 6,522 feet
- Tailwind component at touchdown: calculated later as 8 knots (Southwest limit 5 knots)

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/73097085Fri, 02 Oct 2026 08:00:04 +0000Creator at ObomediaWhen a Southwest 737 Left the Runway and Killed a Child Snow, tailwind and a computation that gave the right number for the wrong assumptions converged into a single moment that ended a flawless safety record and a six-year-old boy’s life - how did...
Snow, tailwind and a computation that gave the right number for the wrong assumptions converged into a single moment that ended a flawless safety record and a six-year-old boy’s life - how did a routine winter landing turn into a street crash? What invisible assumptions in procedures, training, and on-board systems allowed a Boeing 737 to leave the runway and strike two cars on Central Avenue?

In this episode, we tell the story of Southwest Flight 1248’s December 8, 2005 arrival at Midway Airport and the sequence of decisions, weather, and system assumptions that preceded the accident. We follow the flight from Baltimore to Chicago, the crew’s choice to land on Runway 31C with a tailwind, and the unseen errors that made the aircraft’s stopping calculation misleading - could different information or limits have changed the outcome?

Date: December 8, 2005
Event: Runway overrun onto Central Avenue
Aircraft: Boeing 737-7H4 registered N471WN
Person: Joshua Woods, age six, fatally injured
Location: Midway Airport vicinity, Central Avenue and 55th Street, Chicago

- Time of arrival: approximately 7:15 PM
- Snow on ground: approximately 8 inches across Chicago that week
- Visibility at Midway: under one mile
- Runway 31C length: 6,522 feet
- Tailwind component at touchdown: calculated later as 8 knots (Southwest limit 5 knots)

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.]]>1039falsefullhttps://www.spreaker.com/episode/the-dead-auxiliary-power-unit-kept-the-left-engine-running-did-they-make-it--74743265
The dead auxiliary power unit kept the left engine running - did they make it?

In this episode, we reconstruct the chain of decisions, equipment failures, and procedural ambiguities that followed a failed auxiliary power unit at Dryden Regional Airport. The story traces the pilots, the aircraft, the airline's operations, and the cold choices that set the flight on a dangerous path-what happened next?

Date: March 10, 1989
Aircraft: Fokker F28‑1000 Fellowship
Person: Captain George Morwood; First Officer Keith Mills
Location: Dryden Regional Airport, northwestern Ontario
Event: APU unserviceable; left engine kept running during deicing dilemma

- The APU was flagged unserviceable before the flight and Dryden had no external ground power cart available that day.
- With no ground power, the crew decided to keep the port (left) engine running to ensure engines could restart.
- The F28‑1000 manual prohibited deicing with engines running because spray could be ingested and vaporize into the cabin.
- Air Ontario’s operational instructions on handling engines‑running deicing were inconsistent and left captains without a clear, safe option.
- Snow accumulation on the wings measured between 0.6 and 1.3 centimeters while decisions were made and passengers waited.

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/74743265Thu, 01 Oct 2026 08:00:03 +0000Creator at ObomediaA thin dusting of snow coats a Fokker F28 wing as the APU fails and the left engine runs-did they make it in time to deice before takeoff? The dead auxiliary power unit kept the left engine running - did they make it? In this episode, we...
The dead auxiliary power unit kept the left engine running - did they make it?

In this episode, we reconstruct the chain of decisions, equipment failures, and procedural ambiguities that followed a failed auxiliary power unit at Dryden Regional Airport. The story traces the pilots, the aircraft, the airline's operations, and the cold choices that set the flight on a dangerous path-what happened next?

Date: March 10, 1989
Aircraft: Fokker F28‑1000 Fellowship
Person: Captain George Morwood; First Officer Keith Mills
Location: Dryden Regional Airport, northwestern Ontario
Event: APU unserviceable; left engine kept running during deicing dilemma

- The APU was flagged unserviceable before the flight and Dryden had no external ground power cart available that day.
- With no ground power, the crew decided to keep the port (left) engine running to ensure engines could restart.
- The F28‑1000 manual prohibited deicing with engines running because spray could be ingested and vaporize into the cabin.
- Air Ontario’s operational instructions on handling engines‑running deicing were inconsistent and left captains without a clear, safe option.
- Snow accumulation on the wings measured between 0.6 and 1.3 centimeters while decisions were made and passengers waited.

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.]]>856falsefullhttps://www.spreaker.com/episode/the-wing-that-stood-upright-nine-minutes-before-silence--73097083
A right wing stood upright in the shallows of Botany Bay, its registration letters still legible three miles from Sydney Airport - nine minutes after takeoff and after fifteen people had died; how could a clean, upright wing survive a crash that pulverised the rest of the aircraft without anyone on shore seeing or hearing anything? This episode focuses on that single baffling physical clue and asks what the difference between the wing and the rest of the wreckage could mean.

In this episode, we tell the story of Ansett-ANA Flight 325 from pushback to recovery, covering the aircraft, crew, timeline of radio contact and silence, and the diver-led salvage that produced a contradictory wreckage record; what does the contrast between the pulverised fuselage and the near-intact wing and tailplane suggest about those nine minutes?

Person: Captain Stan Lindsay
Person: Co-pilot Ben Costello
Date: 30 November 1961
Aircraft: Vickers Viscount 720, registration VH-TVC, named John Oxley
Event: Right outer wing recovered upright in Botany Bay three miles southeast of runway

- Takeoff time: 19:17 from Runway 07
- Reported altitude: crew radioed reaching 6,000 feet approximately five minutes after takeoff
- Passengers and crew: 15 fatalities (11 passengers, 2 air hostesses, 2 pilots)
- Aircraft hours: 16,946 hours and 12,010 flights recorded by November 1961
- Recovery: divers recovered wreckage over three months in roughly 25 feet of water, including an upright outer right wing and a nearly undamaged right tailplane

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/73097083Thu, 01 Oct 2026 08:00:03 +0000Creator at ObomediaThe Wing That Stood Upright: Nine Minutes Before Silence A right wing stood upright in the shallows of Botany Bay, its registration letters still legible three miles from Sydney Airport - nine minutes after takeoff and after fifteen people had...
A right wing stood upright in the shallows of Botany Bay, its registration letters still legible three miles from Sydney Airport - nine minutes after takeoff and after fifteen people had died; how could a clean, upright wing survive a crash that pulverised the rest of the aircraft without anyone on shore seeing or hearing anything? This episode focuses on that single baffling physical clue and asks what the difference between the wing and the rest of the wreckage could mean.

In this episode, we tell the story of Ansett-ANA Flight 325 from pushback to recovery, covering the aircraft, crew, timeline of radio contact and silence, and the diver-led salvage that produced a contradictory wreckage record; what does the contrast between the pulverised fuselage and the near-intact wing and tailplane suggest about those nine minutes?

Person: Captain Stan Lindsay
Person: Co-pilot Ben Costello
Date: 30 November 1961
Aircraft: Vickers Viscount 720, registration VH-TVC, named John Oxley
Event: Right outer wing recovered upright in Botany Bay three miles southeast of runway

- Takeoff time: 19:17 from Runway 07
- Reported altitude: crew radioed reaching 6,000 feet approximately five minutes after takeoff
- Passengers and crew: 15 fatalities (11 passengers, 2 air hostesses, 2 pilots)
- Aircraft hours: 16,946 hours and 12,010 flights recorded by November 1961
- Recovery: divers recovered wreckage over three months in roughly 25 feet of water, including an upright outer right wing and a nearly undamaged right tailplane

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.]]>1036falsefullhttps://www.spreaker.com/episode/medicine-bow-mystery-the-flight-that-vanished-into-the-peak--73097080
A mountain swallowed a four-engine airliner and left only two dark smears on a cliff face - oil stains pressed side by side fifty to seventy-five feet below Medicine Bow Peak's summit - and sixty-six people were lost. The Civil Aeronautics Board closed the file as "undetermined" after weighing four theories; what happened in the minutes before impact remains unanswered. How did a scheduled flight at ten thousand feet end up embedded in a peak that should not have been on its airway?

In this episode, we tell the sequence of events from departure to search and inquiry. You will hear the flight's delay, the planned cruise altitude for an unpressurized Douglas DC-4, the missed eight-eleven position report over Rock River, Wyoming, and the search efforts that followed - but the central question persists: what made this routine transcontinental leg collide with Medicine Bow Peak?

Date: October 6, 1955
Aircraft: Douglas DC-4, registration N30062
Passengers and crew: 66 (63 passengers, 3 crew)
Departure airport: Stapleton Airport, Denver
Missed position report: 8:11 AM over Rock River, Wyoming

- Departure from Denver was documented as eighty-three minutes late, scheduled 5:10 AM but left gate at 6:33 AM.
- The aircraft was unpressurized and assigned a cruise altitude of 10,000 feet to clear Continental Divide terrain.
- Two oil-stain smears were found on the cliff face, located approximately 50 to 75 feet below the summit of Medicine Bow Peak.
- Among the passengers were five women from the Mormon Tabernacle Choir traveling together.
- Wyoming Air National Guard launched two aircraft from Cheyenne (a T-33 and an F-80) to search after the missed position report.

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/73097080Wed, 30 Sep 2026 08:00:04 +0000Creator at ObomediaMedicine Bow Mystery: The Flight That Vanished Into the Peak A mountain swallowed a four-engine airliner and left only two dark smears on a cliff face - oil stains pressed side by side fifty to seventy-five feet below Medicine Bow Peak's summit -...
A mountain swallowed a four-engine airliner and left only two dark smears on a cliff face - oil stains pressed side by side fifty to seventy-five feet below Medicine Bow Peak's summit - and sixty-six people were lost. The Civil Aeronautics Board closed the file as "undetermined" after weighing four theories; what happened in the minutes before impact remains unanswered. How did a scheduled flight at ten thousand feet end up embedded in a peak that should not have been on its airway?

In this episode, we tell the sequence of events from departure to search and inquiry. You will hear the flight's delay, the planned cruise altitude for an unpressurized Douglas DC-4, the missed eight-eleven position report over Rock River, Wyoming, and the search efforts that followed - but the central question persists: what made this routine transcontinental leg collide with Medicine Bow Peak?

Date: October 6, 1955
Aircraft: Douglas DC-4, registration N30062
Passengers and crew: 66 (63 passengers, 3 crew)
Departure airport: Stapleton Airport, Denver
Missed position report: 8:11 AM over Rock River, Wyoming

- Departure from Denver was documented as eighty-three minutes late, scheduled 5:10 AM but left gate at 6:33 AM.
- The aircraft was unpressurized and assigned a cruise altitude of 10,000 feet to clear Continental Divide terrain.
- Two oil-stain smears were found on the cliff face, located approximately 50 to 75 feet below the summit of Medicine Bow Peak.
- Among the passengers were five women from the Mormon Tabernacle Choir traveling together.
- Wyoming Air National Guard launched two aircraft from Cheyenne (a T-33 and an F-80) to search after the missed position report.

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.]]>1000falsefullhttps://www.spreaker.com/episode/the-port-engine-gauge-wavered-and-cost-the-team-their-takeoff-time--74743264
The port engine gauge wavered and cost the team their takeoff time

In this episode, we follow the minutes and decisions around a February 6, 1958 Munich refuelling stop that preceded a catastrophic takeoff attempt. The episode lays out who was on board, the technical quirk that first caused the crew to abort, and the choices made before the final roll-did those choices buy safety or sacrifice time?

Date: February 6, 1958
Aircraft: Airspeed Ambassador G-ALZU
Passengers: 38 plus 6 crew
Event: Munich technical stop and multiple aborted takeoffs

- The aircraft reached 117 knots on the runway but needed 119 knots to fly, then began to slow.
- This was the third takeoff attempt that afternoon after two earlier aborted runs; snow began to fall between attempts.
- A fluctuation on the port engine pressure gauge during the first roll prompted Captain Rayment to pull back the throttles and taxi back.
- Engineers found no definitive fault and linked the fluctuation to the Elizabethan's Centaurus engines over-accelerating on rich mixture.
- Captain Thain proposed advancing the throttles more slowly on the next attempt rather than grounding the aircraft.

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/74743264Wed, 30 Sep 2026 08:00:03 +0000Creator at ObomediaA British airliner pauses on a Munich runway as the port engine gauge wavers during takeoff-did the crew fix the engine problem in time? The port engine gauge wavered and cost the team their takeoff time In this episode, we follow the minutes...
The port engine gauge wavered and cost the team their takeoff time

In this episode, we follow the minutes and decisions around a February 6, 1958 Munich refuelling stop that preceded a catastrophic takeoff attempt. The episode lays out who was on board, the technical quirk that first caused the crew to abort, and the choices made before the final roll-did those choices buy safety or sacrifice time?

Date: February 6, 1958
Aircraft: Airspeed Ambassador G-ALZU
Passengers: 38 plus 6 crew
Event: Munich technical stop and multiple aborted takeoffs

- The aircraft reached 117 knots on the runway but needed 119 knots to fly, then began to slow.
- This was the third takeoff attempt that afternoon after two earlier aborted runs; snow began to fall between attempts.
- A fluctuation on the port engine pressure gauge during the first roll prompted Captain Rayment to pull back the throttles and taxi back.
- Engineers found no definitive fault and linked the fluctuation to the Elizabethan's Centaurus engines over-accelerating on rich mixture.
- Captain Thain proposed advancing the throttles more slowly on the next attempt rather than grounding the aircraft.

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.]]>1312falsefullhttps://www.spreaker.com/episode/the-wooden-planks-dropped-onto-the-peat-formed-a-raft-that-carried-survivors-out--74743262
The wooden planks dropped onto the peat formed a raft that carried survivors out

In this episode, we follow the moments after a Douglas DC-4 struck treetops near Gander, Newfoundland on 18 September 1946. The narrative covers the crash, the difficult terrain of boreal peat, and the improvised decisions rescuers made-could those choices save the survivors?

Date: 18 September 1946
Aircraft: Douglas DC-4, registration OO-CBG
People aboard: 43 (37 passengers, 6 crew)
Survivors initially: 17
Fatalities at scene: 27

- The flight was the ninth test run of Sabena’s new transatlantic service, aimed at proving the route and aircraft for future commercial service.
- Clouds were sitting at ground level over Gander; the crew descended into invisible treetops and the aircraft struck the forest at 02:42.
- The crash scattered passengers into branches and burning fuselage sections across dense spruce growing on waterlogged peat with no roads or trails.
- Gander tower lost radio contact; a USCG PBY Catalina and a TWA approach plane located the fire but could not reach the site by conventional means.
- Rescuers improvised: seaplanes dropped wooden planks onto the peat and used machines not previously used for civilian rescues to access the wreck.

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/74743262Tue, 29 Sep 2026 08:00:04 +0000Creator at ObomediaA burned DC-4 lies in a Newfoundland bog at dawn; rescuers improvise a seaplane rescue - did they make it in time? The wooden planks dropped onto the peat formed a raft that carried survivors out In this episode, we follow the moments after a...
The wooden planks dropped onto the peat formed a raft that carried survivors out

In this episode, we follow the moments after a Douglas DC-4 struck treetops near Gander, Newfoundland on 18 September 1946. The narrative covers the crash, the difficult terrain of boreal peat, and the improvised decisions rescuers made-could those choices save the survivors?

Date: 18 September 1946
Aircraft: Douglas DC-4, registration OO-CBG
People aboard: 43 (37 passengers, 6 crew)
Survivors initially: 17
Fatalities at scene: 27

- The flight was the ninth test run of Sabena’s new transatlantic service, aimed at proving the route and aircraft for future commercial service.
- Clouds were sitting at ground level over Gander; the crew descended into invisible treetops and the aircraft struck the forest at 02:42.
- The crash scattered passengers into branches and burning fuselage sections across dense spruce growing on waterlogged peat with no roads or trails.
- Gander tower lost radio contact; a USCG PBY Catalina and a TWA approach plane located the fire but could not reach the site by conventional means.
- Rescuers improvised: seaplanes dropped wooden planks onto the peat and used machines not previously used for civilian rescues to access the wreck.

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/final-words-that-s-ok-that-s-ok-the-mountain-took-flight-241--73097079
The most chilling message from PMTair Flight 241 was four calm words: "That's ok, that's ok" - two minutes before the aircraft vanished from radar and twenty-two people died on a mountain. How could a routine domestic hop end in total silence when both flight recorders yielded no usable data, leaving the single unanswered question: did anyone in the cockpit or on the ground know the danger they were about to meet?

In this episode, we present the known facts about the flight, the crew, the aircraft and the investigation, laying out what is verifiable and what remains unknown. We follow the timeline from departure in Siem Reap to the moment the aircraft drifted off course and disappeared, and ask whether missing navigation infrastructure or a language gap could explain the crash.

Person: Captain Nikolay Pavlenko (56 years old, 10,345 total flight hours, >5,000 hours on An-24)
Person: Co-pilot Uth Chan Dara (42 years old, 3,520 total flight hours)
Event: Date of crash - June 25, 2007
Aircraft: Antonov An-24B, registration XU-U4A, manufactured 1969, 38 years old, >25,000 flight cycles
Location: Phnom Damrey (Elephant Mountain), 2,700 feet high, 47 km from Sihanoukville

- Departure time from Siem Reap: 10:01 local time; expected wheels-down at 10:55.
- Last radio exchange recorded at 10:48 with calm reply "That's ok, that's ok"; aircraft vanished from radar two minutes later.
- Both flight recorders were recovered but declared completely unusable with no data, no cockpit audio, no flight parameters.
- PMTair route between Siem Reap and Sihanoukville began January 2007 with six round trips per week; airline also served South Korea.
- Sihanoukville Airport lacked radar, VOR, DME and any instrument landing system on the morning of 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/73097079Tue, 29 Sep 2026 08:00:04 +0000Creator at ObomediaFinal Words: 'That's OK, That's OK' - The Mountain Took Flight 241 The most chilling message from PMTair Flight 241 was four calm words: "That's ok, that's ok" - two minutes before the aircraft vanished from radar and twenty-two people died on a...
The most chilling message from PMTair Flight 241 was four calm words: "That's ok, that's ok" - two minutes before the aircraft vanished from radar and twenty-two people died on a mountain. How could a routine domestic hop end in total silence when both flight recorders yielded no usable data, leaving the single unanswered question: did anyone in the cockpit or on the ground know the danger they were about to meet?

In this episode, we present the known facts about the flight, the crew, the aircraft and the investigation, laying out what is verifiable and what remains unknown. We follow the timeline from departure in Siem Reap to the moment the aircraft drifted off course and disappeared, and ask whether missing navigation infrastructure or a language gap could explain the crash.

Person: Captain Nikolay Pavlenko (56 years old, 10,345 total flight hours, >5,000 hours on An-24)
Person: Co-pilot Uth Chan Dara (42 years old, 3,520 total flight hours)
Event: Date of crash - June 25, 2007
Aircraft: Antonov An-24B, registration XU-U4A, manufactured 1969, 38 years old, >25,000 flight cycles
Location: Phnom Damrey (Elephant Mountain), 2,700 feet high, 47 km from Sihanoukville

- Departure time from Siem Reap: 10:01 local time; expected wheels-down at 10:55.
- Last radio exchange recorded at 10:48 with calm reply "That's ok, that's ok"; aircraft vanished from radar two minutes later.
- Both flight recorders were recovered but declared completely unusable with no data, no cockpit audio, no flight parameters.
- PMTair route between Siem Reap and Sihanoukville began January 2007 with six round trips per week; airline also served South Korea.
- Sihanoukville Airport lacked radar, VOR, DME and any instrument landing system on the morning of 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.]]>1133falsefullhttps://www.spreaker.com/episode/the-three-miles-of-final-approach-that-swallowed-their-last-two-minutes--74743261
The three miles of final approach that swallowed their last two minutes

In this episode, we reconstruct the flight and descent that ended in a crash two minutes after radar disappearance, tracing the passengers, crew, route changes and the fog that closed Heathrow. We follow the choices and procedures that guided the aircraft into those final three miles and ask what on that approach remained unexplained.

Date: 17 February 1959
Person: Adnan Menderes
Aircraft: Vickers Viscount TC‑SEV (Type 793)
Location: Three miles short of Gatwick runway, Surrey wood
Status: Official verdict - cause undetermined

- The flight left Rome Ciampino at 13:13 for London carrying Prime Minister Adnan Menderes and a 24‑person delegation on a high‑stakes diplomatic mission.
- Heathrow closed in dense fog; controllers redirected TC‑SEV to Gatwick and cleared a standard instrument approach toward runway 08R.
- The nearly new Viscount, with 548 hours total time and four Rolls‑Royce Dart engines, descended from holding at Mayfield following issued altitudes and headings.
- Cockpit crew included Captain Münir Özbek and two co‑pilots; the delegation included cabinet ministers, the national news agency director and Turkish Airlines’ director general.
- At 16:42 the aircraft disappeared from radar three miles out, and two minutes later wreckage was found upside down in a Surrey wood amid unreported local fog.

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/74743261Mon, 28 Sep 2026 08:00:03 +0000Creator at ObomediaA Turkish prime minister’s Vickers Viscount vanishes from radar three miles out during a routine instrument approach - did they make it in time? The three miles of final approach that swallowed their last two minutes In this episode, we...
The three miles of final approach that swallowed their last two minutes

In this episode, we reconstruct the flight and descent that ended in a crash two minutes after radar disappearance, tracing the passengers, crew, route changes and the fog that closed Heathrow. We follow the choices and procedures that guided the aircraft into those final three miles and ask what on that approach remained unexplained.

Date: 17 February 1959
Person: Adnan Menderes
Aircraft: Vickers Viscount TC‑SEV (Type 793)
Location: Three miles short of Gatwick runway, Surrey wood
Status: Official verdict - cause undetermined

- The flight left Rome Ciampino at 13:13 for London carrying Prime Minister Adnan Menderes and a 24‑person delegation on a high‑stakes diplomatic mission.
- Heathrow closed in dense fog; controllers redirected TC‑SEV to Gatwick and cleared a standard instrument approach toward runway 08R.
- The nearly new Viscount, with 548 hours total time and four Rolls‑Royce Dart engines, descended from holding at Mayfield following issued altitudes and headings.
- Cockpit crew included Captain Münir Özbek and two co‑pilots; the delegation included cabinet ministers, the national news agency director and Turkish Airlines’ director general.
- At 16:42 the aircraft disappeared from radar three miles out, and two minutes later wreckage was found upside down in a Surrey wood amid unreported local fog.

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.]]>1080falsefullhttps://www.spreaker.com/episode/star-dust-stendec-the-glacier-that-swallowed-eleven-lives--73097076
A chill of dread: an aircraft vanished in 1947, its tyre resurfacing fifty-three years later, still inflated, while an unexplained final Morse word - STENDEC - echoed unanswered. What silent force buried wreckage for over half a century and why did the radio operator send that baffling message?

In this episode, we tell the facts surrounding the disappearance of a British South American Airways Lancastrian named Star Dust and the passengers and crew it carried, and we follow the timeline from departure to the last transmission to ask what STENDEC signaled and how the glacier hid the aircraft for decades.

Person: Captain Reginald Cook
Date: 2 August 1947
Location: Tupungato Glacier / Andes corridor en route Buenos Aires to Santiago
Event: Final Morse transmission "ETA SANTIAGO SEVENTEEN FORTY-FIVE HOURS STENDEC" repeated three times
Status: Wreckage remained unseen in glacier for fifty-one to fifty-three years

- Departure time: 13:46 from Buenos Aires on 2 August 1947
- Scheduled ETA: 17:45 to Santiago, four minutes after last routine position report
- Occupants: 11 people aboard (5 crew, 6 passengers)
- Aircraft type and registration: Avro 691 Lancastrian, registration G-AGWH, named Star Dust
- Aircraft age: First flown 27 November 1945, delivered 12 January 1946 (less than two years old)

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/73097076Mon, 28 Sep 2026 08:00:03 +0000Creator at ObomediaStar Dust: 'STENDEC' - The Glacier That Swallowed Eleven Lives A chill of dread: an aircraft vanished in 1947, its tyre resurfacing fifty-three years later, still inflated, while an unexplained final Morse word - STENDEC - echoed unanswered. What...
A chill of dread: an aircraft vanished in 1947, its tyre resurfacing fifty-three years later, still inflated, while an unexplained final Morse word - STENDEC - echoed unanswered. What silent force buried wreckage for over half a century and why did the radio operator send that baffling message?

In this episode, we tell the facts surrounding the disappearance of a British South American Airways Lancastrian named Star Dust and the passengers and crew it carried, and we follow the timeline from departure to the last transmission to ask what STENDEC signaled and how the glacier hid the aircraft for decades.

Person: Captain Reginald Cook
Date: 2 August 1947
Location: Tupungato Glacier / Andes corridor en route Buenos Aires to Santiago
Event: Final Morse transmission "ETA SANTIAGO SEVENTEEN FORTY-FIVE HOURS STENDEC" repeated three times
Status: Wreckage remained unseen in glacier for fifty-one to fifty-three years

- Departure time: 13:46 from Buenos Aires on 2 August 1947
- Scheduled ETA: 17:45 to Santiago, four minutes after last routine position report
- Occupants: 11 people aboard (5 crew, 6 passengers)
- Aircraft type and registration: Avro 691 Lancastrian, registration G-AGWH, named Star Dust
- Aircraft age: First flown 27 November 1945, delivered 12 January 1946 (less than two years old)

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.]]>1105falsefullhttps://www.spreaker.com/episode/the-mountain-that-knew-how-to-kill-superjet-s-fatal-1-254-foot-error--73097073
Fear of a hidden obstacle: the crew was cleared to 6,000 feet while Mount Salak rose to 7,254 feet - a 1,254-foot difference that none of the 45 people on board realized until impact. The mountain had already claimed seven aircraft in the previous decade, yet the Sukhoi Superjet's team flew into terrain that was, for them, effectively invisible. How did a new airliner, a veteran test pilot and multiple cockpit warnings still end up on a mountainside?

In this episode, we describe the flight's timeline, the aircraft's role as a national showcase, and the decisions and missing charts that shaped the final minutes of the flight. We trace the demonstration tour context, the crew composition, and the unanswered question of why terrain information was not used, asking how sequentially reasonable choices became fatal.

Date: May 9, 2012
Aircraft: Sukhoi Superjet 100, registration RA-97004
Fatalities: 45
Crew Captain: Alexander Yablontsev, age 57
Location: Mount Salak, Indonesia

- Cleared altitude by Jakarta Approach: 6,000 feet
- Actual mountain elevation: 7,254 feet, creating a 1,254-foot clearance deficit
- Passengers on board: 45, none survived
- Number of previous crashes on Mount Salak in prior decade: 7
- Aircraft entered service: April 2011; demonstration tour across Asia in spring 2012

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/73097073Sun, 27 Sep 2026 08:00:03 +0000Creator at ObomediaThe Mountain That Knew How to Kill: Superjet's Fatal 1,254-Foot Error Fear of a hidden obstacle: the crew was cleared to 6,000 feet while Mount Salak rose to 7,254 feet - a 1,254-foot difference that none of the 45 people on board realized until...
Fear of a hidden obstacle: the crew was cleared to 6,000 feet while Mount Salak rose to 7,254 feet - a 1,254-foot difference that none of the 45 people on board realized until impact. The mountain had already claimed seven aircraft in the previous decade, yet the Sukhoi Superjet's team flew into terrain that was, for them, effectively invisible. How did a new airliner, a veteran test pilot and multiple cockpit warnings still end up on a mountainside?

In this episode, we describe the flight's timeline, the aircraft's role as a national showcase, and the decisions and missing charts that shaped the final minutes of the flight. We trace the demonstration tour context, the crew composition, and the unanswered question of why terrain information was not used, asking how sequentially reasonable choices became fatal.

Date: May 9, 2012
Aircraft: Sukhoi Superjet 100, registration RA-97004
Fatalities: 45
Crew Captain: Alexander Yablontsev, age 57
Location: Mount Salak, Indonesia

- Cleared altitude by Jakarta Approach: 6,000 feet
- Actual mountain elevation: 7,254 feet, creating a 1,254-foot clearance deficit
- Passengers on board: 45, none survived
- Number of previous crashes on Mount Salak in prior decade: 7
- Aircraft entered service: April 2011; demonstration tour across Asia in spring 2012

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.]]>1055falsefullhttps://www.spreaker.com/episode/the-midnight-coordinate-change-shifted-their-course-did-they-escape--74743258
The midnight coordinate change shifted their course - did they escape?

In this episode, we follow the flight from Auckland to Antarctica, the crew's preparations, and the single, uncommunicated coordinate change that altered the aircraft's route hours before takeoff. We trace the mechanics of the navigation, the human decisions in the cockpit, and the environmental conditions that conspired to hide a looming mountain - how did one small edit create such catastrophic risk?

Person: Captain Thomas James Collins
Aircraft: McDonnell Douglas DC-10 ZK-NZP
Passengers: 257
Event: Antarctic sightseeing flight, November 28, 1979
Phenomenon: sector whiteout conditions

- A coordinate in Air New Zealand's central computer was changed around 1:40 a.m., shifting the route 27 nautical miles east without alerting the crew.
- The printed flight plan given to the pilots reflected the new coordinates while Captain Collins's personal map notes used briefing materials from November 9 with the old coordinates.
- The DC-10, with over 20,700 flight hours and an experienced three-person crew, departed Auckland at 8:00 a.m. on a routinized Antarctic sightseeing service.
- As the aircraft descended at 12:39 p.m., passengers and crew crossed from clear skies into a cloud layer whose light fused cloud and snow into a featureless white.
- Flight engineer Gordon Brooks announced the start of sea ice visibility and onboard guide Peter Mulgrew began describing the landscape just before the crew encountered the visual conditions that hid the mountain.

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/74743258Sun, 27 Sep 2026 08:00:02 +0000Creator at ObomediaA sightseeing DC-10 over Antarctica had its flight plan silently changed overnight - did the crew make it in time? The midnight coordinate change shifted their course - did they escape? In this episode, we follow the flight from Auckland to...
The midnight coordinate change shifted their course - did they escape?

In this episode, we follow the flight from Auckland to Antarctica, the crew's preparations, and the single, uncommunicated coordinate change that altered the aircraft's route hours before takeoff. We trace the mechanics of the navigation, the human decisions in the cockpit, and the environmental conditions that conspired to hide a looming mountain - how did one small edit create such catastrophic risk?

Person: Captain Thomas James Collins
Aircraft: McDonnell Douglas DC-10 ZK-NZP
Passengers: 257
Event: Antarctic sightseeing flight, November 28, 1979
Phenomenon: sector whiteout conditions

- A coordinate in Air New Zealand's central computer was changed around 1:40 a.m., shifting the route 27 nautical miles east without alerting the crew.
- The printed flight plan given to the pilots reflected the new coordinates while Captain Collins's personal map notes used briefing materials from November 9 with the old coordinates.
- The DC-10, with over 20,700 flight hours and an experienced three-person crew, departed Auckland at 8:00 a.m. on a routinized Antarctic sightseeing service.
- As the aircraft descended at 12:39 p.m., passengers and crew crossed from clear skies into a cloud layer whose light fused cloud and snow into a featureless white.
- Flight engineer Gordon Brooks announced the start of sea ice visibility and onboard guide Peter Mulgrew began describing the landscape just before the crew encountered the visual conditions that hid the mountain.

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.]]>959falsefullhttps://www.spreaker.com/episode/millibar-how-a-tiny-pressure-error-killed-98-at-ljubljana--74743256
Millibar: How a Tiny Pressure Error Killed 98 at Ljubljana

In this episode we follow the final minutes of Britannia Airways Flight 105 as it approaches Ljubljana on 1 September 1966. The episode lays out the cockpit pressures, the approach path and the decisions that determined altitude - and asks whether the crew recognized the mismatch in time.

Date: 1 September 1966
Aircraft: Bristol 175 Britannia G-ANBB
Location: Ljubljana Runway 31 approach / Nasovče forest
Difference: 43 millibar (≈1,100 feet)
Survivors: 19; Fatalities: 98

- Departure from Luton at 21:10 GMT with 110 passengers aboard a Britannia with 18,444 flight hours and 5,380 landings.
- Air traffic control transmitted QNH 1001 and QFE 968 millibars; captain's and first officer's altimeter subscales differed.
- Crew were required by Britannia Airways procedure to cross-check altimeter subscales before approach; that check was not completed.
- The approach cleared to Runway 31 crossed dark Nasovče forest two nautical miles short of the runway on rising terrain with calm winds and 12 nm visibility.
- The Ljubljana controller left the radar console to switch on approach lights while the aircraft drifted right of the extended centerline unseen.

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/74743256Sat, 26 Sep 2026 08:00:03 +0000Creator at ObomediaA Bristol Britannia descends toward Ljubljana on a clear night with two pressure settings in the cockpit - did a 43 millibar error doom the approach? Millibar: How a Tiny Pressure Error Killed 98 at Ljubljana In this episode we follow the final...
Millibar: How a Tiny Pressure Error Killed 98 at Ljubljana

In this episode we follow the final minutes of Britannia Airways Flight 105 as it approaches Ljubljana on 1 September 1966. The episode lays out the cockpit pressures, the approach path and the decisions that determined altitude - and asks whether the crew recognized the mismatch in time.

Date: 1 September 1966
Aircraft: Bristol 175 Britannia G-ANBB
Location: Ljubljana Runway 31 approach / Nasovče forest
Difference: 43 millibar (≈1,100 feet)
Survivors: 19; Fatalities: 98

- Departure from Luton at 21:10 GMT with 110 passengers aboard a Britannia with 18,444 flight hours and 5,380 landings.
- Air traffic control transmitted QNH 1001 and QFE 968 millibars; captain's and first officer's altimeter subscales differed.
- Crew were required by Britannia Airways procedure to cross-check altimeter subscales before approach; that check was not completed.
- The approach cleared to Runway 31 crossed dark Nasovče forest two nautical miles short of the runway on rising terrain with calm winds and 12 nm visibility.
- The Ljubljana controller left the radar console to switch on approach lights while the aircraft drifted right of the extended centerline unseen.

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.]]>843falsefullhttps://www.spreaker.com/episode/the-light-that-stayed-dark-how-silence-doomed-flight-173--73097067
A single green indicator bulb failed to illuminate on a DC-8 that night, and that dark light set off an hour of hesitation that ended in catastrophe-ten dead, twenty-one seriously injured, and a three-year-old orphan among the wreckage. How did experienced pilots, a full crew, and clear fuel readings still let a perfect airframe run out of fuel while circling with landing gear down?

In this episode, we tell the sequence of events from takeoff in Denver to the fatal descent near Portland, focusing on the decisions, the missing light, and the cockpit dynamics that kept crucial information unspoken. What choices in the cockpit turned a solved mechanical problem into a human-made disaster?

Date: December 28, 1978
Aircraft: DC-8-61, registration N8082U
Departure: Denver Stapleton Airport at 15:47 MST
Passengers: 181
Fatalities: 10

- Engines stopped: all four engines failed at 18:06 PST.
- Fuel on departure: 46,700 pounds versus flight plan requirement of 31,900 pounds.
- Time in holding: the aircraft circled Portland for nearly 60 minutes before impact.
- Crew flight hours: Captain Buddy McBroom had 27,600 total flight hours; 5,500 on DC-8.
- Damage cause: right main gear retraction cylinder corroded, causing free-fall drop that damaged the gear-locked microswitch.

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/73097067Sat, 26 Sep 2026 08:00:03 +0000Creator at ObomediaThe Light That Stayed Dark: How Silence Doomed Flight 173 A single green indicator bulb failed to illuminate on a DC-8 that night, and that dark light set off an hour of hesitation that ended in catastrophe-ten dead, twenty-one seriously injured,...
A single green indicator bulb failed to illuminate on a DC-8 that night, and that dark light set off an hour of hesitation that ended in catastrophe-ten dead, twenty-one seriously injured, and a three-year-old orphan among the wreckage. How did experienced pilots, a full crew, and clear fuel readings still let a perfect airframe run out of fuel while circling with landing gear down?

In this episode, we tell the sequence of events from takeoff in Denver to the fatal descent near Portland, focusing on the decisions, the missing light, and the cockpit dynamics that kept crucial information unspoken. What choices in the cockpit turned a solved mechanical problem into a human-made disaster?

Date: December 28, 1978
Aircraft: DC-8-61, registration N8082U
Departure: Denver Stapleton Airport at 15:47 MST
Passengers: 181
Fatalities: 10

- Engines stopped: all four engines failed at 18:06 PST.
- Fuel on departure: 46,700 pounds versus flight plan requirement of 31,900 pounds.
- Time in holding: the aircraft circled Portland for nearly 60 minutes before impact.
- Crew flight hours: Captain Buddy McBroom had 27,600 total flight hours; 5,500 on DC-8.
- Damage cause: right main gear retraction cylinder corroded, causing free-fall drop that damaged the gear-locked microswitch.

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-altitude-selector-set-to-zero-feet-did-they-make-it-in-time--74743254
The altitude selector set to zero feet - did they make it in time?

In this episode, we follow the final hours of Yemenia Flight 626 and the sequence of decisions, warnings, and operational details that led up to the critical night approach into Moroni. Who made the choices in the cockpit and on the ground, and what gaps in training and maintenance set the stage for the emergency question everyone would later ask?

Flight: Yemenia Flight 626
Date: Night of 29-30 June 2009
Aircraft: Airbus A310-324, registration 7O-ADJ
People: 142 passengers, 11 crew (153 total)
Location: Approach to Prince Said Ibrahim International Airport, Moroni

- Departure delayed ~24 minutes due to an auxiliary power unit fault before the long leg south to Comoros.
- Aircraft banned from French airspace after a 2007 DGAC inspection for serious deficiencies but continued flying other routes.
- Captain Khaled Hajeb (44) and First Officer Ali Atef (50) had extensive A310 hours, yet Hajeb lacked the airline’s required Category C approach training for Moroni.
- Twenty-five nautical miles out a wind shift forced a runway change requiring a dark, low-altitude circling approach with approach lights off and no moon.
- Flight data shows the altitude selector rotary knob was set to zero feet during the final approach, a single input embedded in a wider chain of errors.

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/74743254Fri, 25 Sep 2026 08:00:04 +0000Creator at ObomediaA flight bound for Moroni circles at night over a black Indian Ocean as the altitude selector is set to zero feet - did they make it in time? The altitude selector set to zero feet - did they make it in time? In this episode, we follow the final...
The altitude selector set to zero feet - did they make it in time?

In this episode, we follow the final hours of Yemenia Flight 626 and the sequence of decisions, warnings, and operational details that led up to the critical night approach into Moroni. Who made the choices in the cockpit and on the ground, and what gaps in training and maintenance set the stage for the emergency question everyone would later ask?

Flight: Yemenia Flight 626
Date: Night of 29-30 June 2009
Aircraft: Airbus A310-324, registration 7O-ADJ
People: 142 passengers, 11 crew (153 total)
Location: Approach to Prince Said Ibrahim International Airport, Moroni

- Departure delayed ~24 minutes due to an auxiliary power unit fault before the long leg south to Comoros.
- Aircraft banned from French airspace after a 2007 DGAC inspection for serious deficiencies but continued flying other routes.
- Captain Khaled Hajeb (44) and First Officer Ali Atef (50) had extensive A310 hours, yet Hajeb lacked the airline’s required Category C approach training for Moroni.
- Twenty-five nautical miles out a wind shift forced a runway change requiring a dark, low-altitude circling approach with approach lights off and no moon.
- Flight data shows the altitude selector rotary knob was set to zero feet during the final approach, a single input embedded in a wider chain of errors.

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.]]>793falsefullhttps://www.spreaker.com/episode/seconds-to-impact-how-faked-pilot-papers-sent-flight-363-down--73097062
A Boeing 737 plunged nose-first at a 75-degree angle and hit the ground at over 450 km/h; the whole sequence from go-around to impact lasted 45 seconds and all 50 aboard died - so how did the crew stop providing any control inputs during the only seconds that mattered? What hidden paperwork failures had been guiding the flight long before it left Moscow?

In this episode, we follow the facts recorded by the flight data recorder, eyewitness surveillance footage from Kazan International Airport, and the official incident history to show what happened in those final forty-five seconds and why investigators traced the cause back to the system that certified the crew rather than to the airplane itself.

Person: Captain Rustem Gabdrakhmanovich Salikhov
Person: First Officer Viktor Nikiforovich Gutsul
Event: Impact at 19:19:24 local time after 45-second descent
Aircraft: Boeing 737-533 registration VQ-BBN, built 1990
Passengers and crew: 50 aboard, zero survivors

- The aircraft nose was pitched 75 degrees down at impact.
- The aircraft hit the ground at more than 450 km/h.
- The recorded sequence from go-around to impact lasted 45 seconds.
- Captain Salikhov had 2,755 total flight hours, 2,509 on the 737, and 527 as captain.
- The aircraft had previously landed short on 17 December 2001 and made an emergency landing on 26 November 2012.

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/73097062Fri, 25 Sep 2026 08:00:02 +0000Creator at ObomediaSeconds to Impact: How Faked Pilot Papers Sent Flight 363 Down A Boeing 737 plunged nose-first at a 75-degree angle and hit the ground at over 450 km/h; the whole sequence from go-around to impact lasted 45 seconds and all 50 aboard died - so how...
A Boeing 737 plunged nose-first at a 75-degree angle and hit the ground at over 450 km/h; the whole sequence from go-around to impact lasted 45 seconds and all 50 aboard died - so how did the crew stop providing any control inputs during the only seconds that mattered? What hidden paperwork failures had been guiding the flight long before it left Moscow?

In this episode, we follow the facts recorded by the flight data recorder, eyewitness surveillance footage from Kazan International Airport, and the official incident history to show what happened in those final forty-five seconds and why investigators traced the cause back to the system that certified the crew rather than to the airplane itself.

Person: Captain Rustem Gabdrakhmanovich Salikhov
Person: First Officer Viktor Nikiforovich Gutsul
Event: Impact at 19:19:24 local time after 45-second descent
Aircraft: Boeing 737-533 registration VQ-BBN, built 1990
Passengers and crew: 50 aboard, zero survivors

- The aircraft nose was pitched 75 degrees down at impact.
- The aircraft hit the ground at more than 450 km/h.
- The recorded sequence from go-around to impact lasted 45 seconds.
- Captain Salikhov had 2,755 total flight hours, 2,509 on the 737, and 527 as captain.
- The aircraft had previously landed short on 17 December 2001 and made an emergency landing on 26 November 2012.

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.]]>1212falsefullhttps://www.spreaker.com/episode/the-phrase-cleared-for-the-approach-let-them-descend-into-the-mountain--74743253
The phrase "Cleared for the approach" let them descend into the mountain

In this episode, we lay out the flight, the crew, the weather, and the procedural handoffs that framed a descent into terrain on a published instrument approach. What gap inside a familiar phrase and the system’s silence preceded the final minutes?

Date: December 1, 1974
Flight: TWA Flight 514
Location: Mount Weather, Virginia (approach to Washington Dulles)
Aircraft: Boeing 727 (in service since March 3, 1970; 11,997 hours)
People: Captain Richard I. Brock; First Officer Lenard W. Kreshec; Flight Engineer Thomas C. Safranek

- The crew were seasoned professionals with thousands of hours and specific experience on the 727.
- Dulles was accepted as the diversion airport after severe crosswinds at National; the approach chart for Runway 12 was published and on the flight deck.
- Controllers issued the routine clearance: "Cleared for the approach," a four-word handoff heard as descent permission by the crew.
- The approach procedure used step-down minimum safe altitudes tied to crossing named fixes; terrain rose beneath the inbound path.
- Six weeks earlier, another airline crew nearly impacted the same mountainside on the same approach, but that near-miss was never reported to the system.

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/74743253Thu, 24 Sep 2026 08:00:04 +0000Creator at ObomediaA routine "Cleared for the approach" sends a Boeing 727 toward Mount Weather-did they make it in time? The phrase "Cleared for the approach" let them descend into the mountain In this episode, we lay out the flight, the crew, the weather, and...
The phrase "Cleared for the approach" let them descend into the mountain

In this episode, we lay out the flight, the crew, the weather, and the procedural handoffs that framed a descent into terrain on a published instrument approach. What gap inside a familiar phrase and the system’s silence preceded the final minutes?

Date: December 1, 1974
Flight: TWA Flight 514
Location: Mount Weather, Virginia (approach to Washington Dulles)
Aircraft: Boeing 727 (in service since March 3, 1970; 11,997 hours)
People: Captain Richard I. Brock; First Officer Lenard W. Kreshec; Flight Engineer Thomas C. Safranek

- The crew were seasoned professionals with thousands of hours and specific experience on the 727.
- Dulles was accepted as the diversion airport after severe crosswinds at National; the approach chart for Runway 12 was published and on the flight deck.
- Controllers issued the routine clearance: "Cleared for the approach," a four-word handoff heard as descent permission by the crew.
- The approach procedure used step-down minimum safe altitudes tied to crossing named fixes; terrain rose beneath the inbound path.
- Six weeks earlier, another airline crew nearly impacted the same mountainside on the same approach, but that near-miss was never reported to the system.

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.]]>998falsefullhttps://www.spreaker.com/episode/seconds-too-late-how-flight-518-climbed-blind-into-the-andes--73097059
Twenty-eight seconds separated forty-six people from a safe landing - an AHRS that needed 180 seconds to initialize lost exactly 28 seconds on the ramp, and the ATR 42-300 climbed into the Venezuelan Andes without reliable attitude data; how did a coffee break and a compressed checklist turn into disaster?

In this episode, we tell the story of Flight 518’s departure from Alberto Carnevalli Airport and the sequence of delays, decisions, and instrument timing that preceded its disappearance, asking whether routine shortcuts and one successful prior flight taught a deadly lesson.

Date: February 21, 2008
Aircraft: ATR 42-300, registration YV1449
Location: Alberto Carnevalli Airport, Mérida, Venezuela
Passengers: 43 passengers, plus crew totalling 46 people on board
System: AHRS required 180 seconds to initialize; investigators calculated 28 seconds short

- 28 seconds was the exact time investigators say the AHRS initialization was short when the aircraft departed.
- Alberto Carnevalli Airport elevation is 5,212 feet above sea level, with narrow approach corridors.
- The ATR 42-300 had over 37,000 flight cycles on its airframe at the time of departure.
- Captain Aldino Garanito Gómez had logged more than 5,000 flight hours; First Officer Denis Ferreira Quintal had over 2,000 hours.
- Night flights were prohibited at Alberto Carnevalli Airport by Venezuelan aviation regulations due to steep surrounding terrain.

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/73097059Thu, 24 Sep 2026 08:00:03 +0000Creator at ObomediaSeconds Too Late: How Flight 518 Climbed Blind Into The Andes Twenty-eight seconds separated forty-six people from a safe landing - an AHRS that needed 180 seconds to initialize lost exactly 28 seconds on the ramp, and the ATR 42-300 climbed into...
Twenty-eight seconds separated forty-six people from a safe landing - an AHRS that needed 180 seconds to initialize lost exactly 28 seconds on the ramp, and the ATR 42-300 climbed into the Venezuelan Andes without reliable attitude data; how did a coffee break and a compressed checklist turn into disaster?

In this episode, we tell the story of Flight 518’s departure from Alberto Carnevalli Airport and the sequence of delays, decisions, and instrument timing that preceded its disappearance, asking whether routine shortcuts and one successful prior flight taught a deadly lesson.

Date: February 21, 2008
Aircraft: ATR 42-300, registration YV1449
Location: Alberto Carnevalli Airport, Mérida, Venezuela
Passengers: 43 passengers, plus crew totalling 46 people on board
System: AHRS required 180 seconds to initialize; investigators calculated 28 seconds short

- 28 seconds was the exact time investigators say the AHRS initialization was short when the aircraft departed.
- Alberto Carnevalli Airport elevation is 5,212 feet above sea level, with narrow approach corridors.
- The ATR 42-300 had over 37,000 flight cycles on its airframe at the time of departure.
- Captain Aldino Garanito Gómez had logged more than 5,000 flight hours; First Officer Denis Ferreira Quintal had over 2,000 hours.
- Night flights were prohibited at Alberto Carnevalli Airport by Venezuelan aviation regulations due to steep surrounding terrain.

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.]]>1134falsefullhttps://www.spreaker.com/episode/the-ungrooved-runway-sent-the-a320-hydroplaning-did-they-stop-in-time--74743251
The ungrooved runway sent the A320 hydroplaning - did they stop in time?

In this episode, listeners follow the minutes and decisions leading up to an Airbus A320 touchdown on a wet Congonhas runway with one thrust reverser deactivated and the city immediately beyond. The episode traces the airport's resurfacing choices, crew experience, and prior warnings - and asks whether enough was done to prevent catastrophe.

Date: July 17, 2007
Location: Congonhas Airport, São Paulo
Aircraft: Airbus A320-233, registration PR-MBK
Crew: Captains Henrique Stefanini Di Sacco and Kleyber Aguiar Lima
Runway status: Resurfaced June 29, grooves not cut; wet conditions reported the day before

- Runway 35L measured 1,940 meters with no runway-end safety area and a four-story warehouse and gas station beyond the far end.
- Resurfacing finished June 29 but the standard transverse grooves to channel water were not cut; Infraero said 30 more days were needed.
- Pilots had reported poor braking on July 16; one TAM stopped meters from the end and a Pantanal ATR hydroplaned and was written off.
- The A320 had one thrust reverser deactivated per a maintenance note but was released for flight and departed Porto Alegre at 17:17 BRT.
- The approach began at 18:48 BRT into wet conditions with 26 seconds between threshold crossing and the point the pilots would need to 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/74743251Wed, 23 Sep 2026 08:00:04 +0000Creator at ObomediaAn A320 fights to stop on a short, ungrooved São Paulo runway in a downpour as the city looms; did they make it in time? The ungrooved runway sent the A320 hydroplaning - did they stop in time? In this episode, listeners follow the minutes and...
The ungrooved runway sent the A320 hydroplaning - did they stop in time?

In this episode, listeners follow the minutes and decisions leading up to an Airbus A320 touchdown on a wet Congonhas runway with one thrust reverser deactivated and the city immediately beyond. The episode traces the airport's resurfacing choices, crew experience, and prior warnings - and asks whether enough was done to prevent catastrophe.

Date: July 17, 2007
Location: Congonhas Airport, São Paulo
Aircraft: Airbus A320-233, registration PR-MBK
Crew: Captains Henrique Stefanini Di Sacco and Kleyber Aguiar Lima
Runway status: Resurfaced June 29, grooves not cut; wet conditions reported the day before

- Runway 35L measured 1,940 meters with no runway-end safety area and a four-story warehouse and gas station beyond the far end.
- Resurfacing finished June 29 but the standard transverse grooves to channel water were not cut; Infraero said 30 more days were needed.
- Pilots had reported poor braking on July 16; one TAM stopped meters from the end and a Pantanal ATR hydroplaned and was written off.
- The A320 had one thrust reverser deactivated per a maintenance note but was released for flight and departed Porto Alegre at 17:17 BRT.
- The approach began at 18:48 BRT into wet conditions with 26 seconds between threshold crossing and the point the pilots would need to 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.]]>1283falsefullhttps://www.spreaker.com/episode/ten-seconds-to-impact-snowplow-on-runway-43-dead--73097057
A routine regional flight landed ten minutes early into heavy snow with a snowplow actively clearing Runway Sixteen - and ten seconds after touchdown forty-three people were dead. The crew never knew the plow was there, the airport was uncontrolled, and five separate failures stacked together; what single decision, if changed, would have stopped the chain?

In this episode, we follow the facts of Flight 314’s February 11, 1978 arrival at Cranbrook and trace how timing, communication, and procedure combined to create a catastrophe. We cover the crew’s experience, the airport’s limitations, the ground crew activity, and the missed communications that left a snowplow on the active runway - could one radio call have prevented the accident?

Date: February 11, 1978
Location: Cranbrook, British Columbia
Flight: Pacific Western Airlines Flight 314
Aircraft: Boeing 737-275 with Pratt & Whitney JT8D-9A engines
Casualties: 43 dead

- Flight 314 was released from Calgary ATC at 12:32 and estimated to arrive Cranbrook at 13:05, an ETA that proved ten minutes late.
- At 12:46 the crew reported position to Cranbrook aero-radio and were told visibility 3/4 mile with snow falling and “there was a snowplow on the runway.”
- First Officer Peter Van Oort acknowledged with “Three Fourteen checks,” four words that were the last transmission from the crew before the approach.
- Captain Chris Miles had 5,173 total flight hours with 2,780 hours on the Boeing 737; First Officer Van Oort had 81 hours on type, having qualified in December 1977.
- The airport was uncontrolled; the aero-radio station could pass advisories but had no authority to instruct the snowplow operator, Terry George, to leave 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/73097057Wed, 23 Sep 2026 08:00:03 +0000Creator at ObomediaTen Seconds to Impact: Snowplow on Runway, 43 Dead A routine regional flight landed ten minutes early into heavy snow with a snowplow actively clearing Runway Sixteen - and ten seconds after touchdown forty-three people were dead. The crew never...
A routine regional flight landed ten minutes early into heavy snow with a snowplow actively clearing Runway Sixteen - and ten seconds after touchdown forty-three people were dead. The crew never knew the plow was there, the airport was uncontrolled, and five separate failures stacked together; what single decision, if changed, would have stopped the chain?

In this episode, we follow the facts of Flight 314’s February 11, 1978 arrival at Cranbrook and trace how timing, communication, and procedure combined to create a catastrophe. We cover the crew’s experience, the airport’s limitations, the ground crew activity, and the missed communications that left a snowplow on the active runway - could one radio call have prevented the accident?

Date: February 11, 1978
Location: Cranbrook, British Columbia
Flight: Pacific Western Airlines Flight 314
Aircraft: Boeing 737-275 with Pratt & Whitney JT8D-9A engines
Casualties: 43 dead

- Flight 314 was released from Calgary ATC at 12:32 and estimated to arrive Cranbrook at 13:05, an ETA that proved ten minutes late.
- At 12:46 the crew reported position to Cranbrook aero-radio and were told visibility 3/4 mile with snow falling and “there was a snowplow on the runway.”
- First Officer Peter Van Oort acknowledged with “Three Fourteen checks,” four words that were the last transmission from the crew before the approach.
- Captain Chris Miles had 5,173 total flight hours with 2,780 hours on the Boeing 737; First Officer Van Oort had 81 hours on type, having qualified in December 1977.
- The airport was uncontrolled; the aero-radio station could pass advisories but had no authority to instruct the snowplow operator, Terry George, to leave 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.]]>1095falsefullhttps://www.spreaker.com/episode/the-silent-right-strut-stopped-the-reversers-did-they-stop-in-time--74743250
The silent right strut stopped the reversers - did they stop in time?

In this episode, we follow a repositioning Tupolev Tu-204 landing at Vnukovo where a single missing strut signal triggered a cascade of system failures across thirty-two seconds after touchdown. The episode traces the crew, the aircraft, the weather, and the chain of maintenance and reporting that connect this crash to an earlier near-identical event-what does that chain mean for the people on board?

Date: December 29, 2012
Location: Vnukovo Airport, Runway 19
Aircraft: Tupolev Tu-204-100B, registration RA-64047
Crew: 8 (3 cockpit, 5 cabin), Captain Gennady D. Shmelev, First Officer Evgeny I. Astashenkov, Flight Engineer Igor N. Fisenko
Weather: Snow with crosswind gusts up to 29 knots (11.5 m/s)

- Touchdown occurred between 900 and 1,000 meters past threshold at 260 km/h, within published limits.
- At the moment of main gear contact only the left main strut registered compression; the right strut sent no signal.
- Tu-204 reverser interlock requires simultaneous compression signals from both main struts to deploy.
- With no right-strut signal the reversers stayed locked and throttle advanced, producing forward thrust during rollout.
- Investigators compared flight data recorder seconds to a near-identical event nine days earlier linked by a maintenance directive and manufacturer notification.

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/74743250Tue, 22 Sep 2026 08:00:03 +0000Creator at ObomediaA Tupolev touches down at Vnukovo and one right main strut sends no compression signal-did the silent strut stop the reversers in time? The silent right strut stopped the reversers - did they stop in time? In this episode, we follow a...
The silent right strut stopped the reversers - did they stop in time?

In this episode, we follow a repositioning Tupolev Tu-204 landing at Vnukovo where a single missing strut signal triggered a cascade of system failures across thirty-two seconds after touchdown. The episode traces the crew, the aircraft, the weather, and the chain of maintenance and reporting that connect this crash to an earlier near-identical event-what does that chain mean for the people on board?

Date: December 29, 2012
Location: Vnukovo Airport, Runway 19
Aircraft: Tupolev Tu-204-100B, registration RA-64047
Crew: 8 (3 cockpit, 5 cabin), Captain Gennady D. Shmelev, First Officer Evgeny I. Astashenkov, Flight Engineer Igor N. Fisenko
Weather: Snow with crosswind gusts up to 29 knots (11.5 m/s)

- Touchdown occurred between 900 and 1,000 meters past threshold at 260 km/h, within published limits.
- At the moment of main gear contact only the left main strut registered compression; the right strut sent no signal.
- Tu-204 reverser interlock requires simultaneous compression signals from both main struts to deploy.
- With no right-strut signal the reversers stayed locked and throttle advanced, producing forward thrust during rollout.
- Investigators compared flight data recorder seconds to a near-identical event nine days earlier linked by a maintenance directive and manufacturer notification.

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.]]>892falsefullhttps://www.spreaker.com/episode/seconds-of-fog-how-luxair-9642-s-small-failures-killed-20--73097054
A cold, dense fog hid a cascading chain of small decisions that left 20 of 22 people dead - the aircraft had 24,068 cycles, the runway visual range fell below the Fokker Fifty minimum, and the maintenance log showed an anti-skid defect signed off the day before. Who flipped the last switch that turned a survivable error into a fatal sequence?

In this episode, we tell what happened on the approach to Luxembourg Findel on 6 November 2002, how crew, air traffic control and maintenance entries converged, and why a missing approach briefing and an unshared minimum became central to the crash. Could a single agreed abort point have changed everything?

Aircraft: Fokker Fifty LX-LGB
Date: 6 November 2002
Location: Luxembourg Findel Airport
Passengers and crew: 22 aboard (19 passengers, 3 crew)
Runway visual range: dropped from 275 m to 250 m during approach

- Aircraft total cycles: 24,068 flight cycles
- Captain total hours: 4,242 hours (2,864 on Fokker Fifty)
- First Officer hours on type: 443 hours
- Reported runway visual range at 08:55: 275 metres (minimum 300 m for Fokker Fifty)
- Controller reported runway visual range at 09:04: exactly 300 metres

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/73097054Tue, 22 Sep 2026 08:00:03 +0000Creator at ObomediaSeconds of Fog: How Luxair 9642's Small Failures Killed 20 A cold, dense fog hid a cascading chain of small decisions that left 20 of 22 people dead - the aircraft had 24,068 cycles, the runway visual range fell below the Fokker Fifty minimum, and...
A cold, dense fog hid a cascading chain of small decisions that left 20 of 22 people dead - the aircraft had 24,068 cycles, the runway visual range fell below the Fokker Fifty minimum, and the maintenance log showed an anti-skid defect signed off the day before. Who flipped the last switch that turned a survivable error into a fatal sequence?

In this episode, we tell what happened on the approach to Luxembourg Findel on 6 November 2002, how crew, air traffic control and maintenance entries converged, and why a missing approach briefing and an unshared minimum became central to the crash. Could a single agreed abort point have changed everything?

Aircraft: Fokker Fifty LX-LGB
Date: 6 November 2002
Location: Luxembourg Findel Airport
Passengers and crew: 22 aboard (19 passengers, 3 crew)
Runway visual range: dropped from 275 m to 250 m during approach

- Aircraft total cycles: 24,068 flight cycles
- Captain total hours: 4,242 hours (2,864 on Fokker Fifty)
- First Officer hours on type: 443 hours
- Reported runway visual range at 08:55: 275 metres (minimum 300 m for Fokker Fifty)
- Controller reported runway visual range at 09:04: exactly 300 metres

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.]]>956falsefullhttps://www.spreaker.com/episode/the-slats-stayed-retracted-and-stole-their-climb-seconds--74743249
The slats stayed retracted and stole their climb seconds

In this episode, we follow the minutes from gate to impact as crew, maintenance, and air traffic interactions set the stage for catastrophe. The narrative traces every procedural choice and mechanical state that mattered - could a chain of routine decisions explain how a jet failed to climb?

Flight: Northwest Airlines Flight 255
Date: August 16, 1987
Location: Detroit Metropolitan Airport / Middlebelt Road
Aircraft: McDonnell Douglas MD-82, N312RC
Survivor: Cecelia Cichan, four years old

- Captain John R. Maus (57) and First Officer David J. Dodds (35) had extensive experience and logged thousands of flight hours.
- The crew began with planned takeoff from Runway 21L/21R but were reassigned to shorter Runway 3C; Dodds recalculated performance and reprogrammed the computer.
- At 20:44:21 the throttles advanced; the MD-82 rotated at 170 knots but climbed fewer than fifty feet before lateral roll and deteriorating climb rate.
- Inspectors found no maintenance flags earlier that day; a Northwest mechanic had checked the aircraft and its log in Detroit with nothing noted.
- Witnesses and investigators observed the aircraft’s flaps and slats were retracted during takeoff, leaving the wings without the low-speed lift devices needed to climb.

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/74743249Mon, 21 Sep 2026 08:00:03 +0000Creator at ObomediaA four-year-old clung to a flipped seat on Middlebelt Road - did the retracted slats cost them their seconds? The slats stayed retracted and stole their climb seconds In this episode, we follow the minutes from gate to impact as crew,...
The slats stayed retracted and stole their climb seconds

In this episode, we follow the minutes from gate to impact as crew, maintenance, and air traffic interactions set the stage for catastrophe. The narrative traces every procedural choice and mechanical state that mattered - could a chain of routine decisions explain how a jet failed to climb?

Flight: Northwest Airlines Flight 255
Date: August 16, 1987
Location: Detroit Metropolitan Airport / Middlebelt Road
Aircraft: McDonnell Douglas MD-82, N312RC
Survivor: Cecelia Cichan, four years old

- Captain John R. Maus (57) and First Officer David J. Dodds (35) had extensive experience and logged thousands of flight hours.
- The crew began with planned takeoff from Runway 21L/21R but were reassigned to shorter Runway 3C; Dodds recalculated performance and reprogrammed the computer.
- At 20:44:21 the throttles advanced; the MD-82 rotated at 170 knots but climbed fewer than fifty feet before lateral roll and deteriorating climb rate.
- Inspectors found no maintenance flags earlier that day; a Northwest mechanic had checked the aircraft and its log in Detroit with nothing noted.
- Witnesses and investigators observed the aircraft’s flaps and slats were retracted during takeoff, leaving the wings without the low-speed lift devices needed to climb.

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.]]>1155falsefullhttps://www.spreaker.com/episode/he-pulled-one-breaker-162-lives-lost-in-60-seconds--73097051
The ordinary morning that led to 162 deaths began with a two-second action: a pilot resetting a single circuit breaker at 06:16:45. A cracked solder joint inside the Rudder Travel Limiter Unit had triggered the same warning 23 times in the prior 12 months, and four minutes after that reset the aircraft entered a fatal aerodynamic stall - so how did routine maintenance and one breaker create a cascade no one foresaw?

In this episode, we present the sequence of events from pushback to stall, the maintenance history of the aircraft, and the profiles of the crew and passengers to ask whether repeated resets and an unverified fault made disaster inevitable. Could a tiny cracked solder joint and a non-approved cockpit action remove every layer of protection in under a minute?

Event: Indonesia AirAsia flight QZ8501 crash
Date: 28 December 2014, 06:16:45 onward
Aircraft: Airbus A320, registration PK-AXC, delivered 15 October 2008
Faulty component: Rudder Travel Limiter Unit (RTLU) with cracked solder joint
Passengers aboard: 162 total (including 155 passengers and crew; nationalities noted)

- The RTLU warning had occurred 23 times in the previous 12 months and each instance was cleared by a reset.
- The breaker reset by the pilot took less than two seconds at 06:16:45.
- Four minutes after that reset, the aircraft entered a full aerodynamic stall with no distress signal sent.
- Captain Iriyanto had 20,537 total flight hours and 4,687 hours on the A320; First Officer Rémi Plesel had 2,247 total hours and 1,367 on the A320.
- The aircraft had about 23,000 airframe hours and 13,600 cycles; last scheduled maintenance was completed on 16 November 2014.

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/73097051Mon, 21 Sep 2026 08:00:03 +0000Creator at ObomediaHe Pulled One Breaker - 162 Lives Lost in 60 Seconds The ordinary morning that led to 162 deaths began with a two-second action: a pilot resetting a single circuit breaker at 06:16:45. A cracked solder joint inside the Rudder Travel Limiter Unit...
The ordinary morning that led to 162 deaths began with a two-second action: a pilot resetting a single circuit breaker at 06:16:45. A cracked solder joint inside the Rudder Travel Limiter Unit had triggered the same warning 23 times in the prior 12 months, and four minutes after that reset the aircraft entered a fatal aerodynamic stall - so how did routine maintenance and one breaker create a cascade no one foresaw?

In this episode, we present the sequence of events from pushback to stall, the maintenance history of the aircraft, and the profiles of the crew and passengers to ask whether repeated resets and an unverified fault made disaster inevitable. Could a tiny cracked solder joint and a non-approved cockpit action remove every layer of protection in under a minute?

Event: Indonesia AirAsia flight QZ8501 crash
Date: 28 December 2014, 06:16:45 onward
Aircraft: Airbus A320, registration PK-AXC, delivered 15 October 2008
Faulty component: Rudder Travel Limiter Unit (RTLU) with cracked solder joint
Passengers aboard: 162 total (including 155 passengers and crew; nationalities noted)

- The RTLU warning had occurred 23 times in the previous 12 months and each instance was cleared by a reset.
- The breaker reset by the pilot took less than two seconds at 06:16:45.
- Four minutes after that reset, the aircraft entered a full aerodynamic stall with no distress signal sent.
- Captain Iriyanto had 20,537 total flight hours and 4,687 hours on the A320; First Officer Rémi Plesel had 2,247 total hours and 1,367 on the A320.
- The aircraft had about 23,000 airframe hours and 13,600 cycles; last scheduled maintenance was completed on 16 November 2014.

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.]]>1192falsefullhttps://www.spreaker.com/episode/the-disabled-runway-alarms-kept-warning-silent-did-they-make-it--74743248
The Disabled Runway Alarms Kept Warning Silent - Did They Make It?

In this episode, we reconstruct the sequence of decisions, equipment failures and procedural gaps at Milan Linate Airport on October 8, 2001 that left controllers without working ground radar and with runway alarms switched off. We follow the crews, the airport's systems and the bureaucratic history that set the scene - could layered mistakes be stopped before catastrophe?

Date: October 8, 2001
Location: Milan Linate Airport
Event: Ground radar non-operational; runway incursion alarms disabled
Aircraft: SAS Flight 686 (MD-87) and Cessna Citation 525-A
People: Captain Joakim Gustafsson; First Officer Anders Hyllander; Captain Horst Königsmann; First Officer Martin Schneider; passenger group of Swedish go-kart drivers

- At 08:10 the tower received a radio call reporting position "S four," a taxiway designation that did not exist on the controller’s map.
- Linate was enveloped in dense fog with visibility around 100 meters while flights continued under low-visibility procedures.
- The ground radar decommissioned in November 1999 had not been replaced despite approval for a new system in 1995, leaving controllers blind on the ground for six years.
- The airport's runway incursion warning alarms were intentionally switched off because recurring false alerts from vehicles and animals made them a nuisance.
- Multiple authorities - the airport operator, the national air navigation service and the civil aviation directorate - shared responsibility for infrastructure decisions and budget handoffs leading up to 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/74743248Sun, 20 Sep 2026 08:00:03 +0000Creator at ObomediaA foggy October morning at Milan Linate: controllers are blind on the ground, runway alarms deliberately silenced - did they make it in time? The Disabled Runway Alarms Kept Warning Silent - Did They Make It? In this episode, we reconstruct the...
The Disabled Runway Alarms Kept Warning Silent - Did They Make It?

In this episode, we reconstruct the sequence of decisions, equipment failures and procedural gaps at Milan Linate Airport on October 8, 2001 that left controllers without working ground radar and with runway alarms switched off. We follow the crews, the airport's systems and the bureaucratic history that set the scene - could layered mistakes be stopped before catastrophe?

Date: October 8, 2001
Location: Milan Linate Airport
Event: Ground radar non-operational; runway incursion alarms disabled
Aircraft: SAS Flight 686 (MD-87) and Cessna Citation 525-A
People: Captain Joakim Gustafsson; First Officer Anders Hyllander; Captain Horst Königsmann; First Officer Martin Schneider; passenger group of Swedish go-kart drivers

- At 08:10 the tower received a radio call reporting position "S four," a taxiway designation that did not exist on the controller’s map.
- Linate was enveloped in dense fog with visibility around 100 meters while flights continued under low-visibility procedures.
- The ground radar decommissioned in November 1999 had not been replaced despite approval for a new system in 1995, leaving controllers blind on the ground for six years.
- The airport's runway incursion warning alarms were intentionally switched off because recurring false alerts from vehicles and animals made them a nuisance.
- Multiple authorities - the airport operator, the national air navigation service and the civil aviation directorate - shared responsibility for infrastructure decisions and budget handoffs leading up to 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.]]>840falsefullhttps://www.spreaker.com/episode/three-minutes-over-the-red-sea-how-flight-604-vanished--73097050
Fear of sudden loss - 148 lives gone three minutes after takeoff when a Boeing 737 rolled past vertical and slammed into the Red Sea at 412 knots; what in the cockpit unfolded that morning, and who decided what it meant? What triggered the autopilot to disconnect and why did the aircraft enter an uncontrollable right bank?

In this episode, we follow the flight timeline, crew backgrounds, and the recovered cockpit voice and flight data recorders to outline the final three minutes and the unresolved conclusions investigators reached. The episode covers the takeoff, the sudden autopilot disengagement, the crew calls in the cockpit and the flight's final flight-data traces that left three nations at odds over a single cause.

Person: Captain Khedr Abdullah, 53 years old, ~7,500 total flight hours, ~474 hours on the 737
Person: First Officer Amr al‑Shaafei, 25 years old,

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/73097050Sun, 20 Sep 2026 08:00:03 +0000Creator at ObomediaThree Minutes Over the Red Sea: How Flight 604 Vanished Fear of sudden loss - 148 lives gone three minutes after takeoff when a Boeing 737 rolled past vertical and slammed into the Red Sea at 412 knots; what in the cockpit unfolded that morning,...
Fear of sudden loss - 148 lives gone three minutes after takeoff when a Boeing 737 rolled past vertical and slammed into the Red Sea at 412 knots; what in the cockpit unfolded that morning, and who decided what it meant? What triggered the autopilot to disconnect and why did the aircraft enter an uncontrollable right bank?

In this episode, we follow the flight timeline, crew backgrounds, and the recovered cockpit voice and flight data recorders to outline the final three minutes and the unresolved conclusions investigators reached. The episode covers the takeoff, the sudden autopilot disengagement, the crew calls in the cockpit and the flight's final flight-data traces that left three nations at odds over a single cause.

Person: Captain Khedr Abdullah, 53 years old, ~7,500 total flight hours, ~474 hours on the 737
Person: First Officer Amr al‑Shaafei, 25 years old,

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.]]>1050falsefullhttps://www.spreaker.com/episode/the-pressure-setting-spoken-over-the-radio-pushed-them-below-safety-in-time--74743245
The pressure setting spoken over the radio pushed them below safety in time

In this episode, we lay out the sequence of decisions, procedures, and missing steps that preceded the crash of Independent Air Flight 1851. We follow the crew, the aging Boeing 707, the outdated charts, and the radio call that shifted the aircraft's altitude - who missed the correction and why does it matter?

Event: Independent Air Flight 1851 crash
Date: February 8, 1989
Location: Pico Alto, Santa Maria, Azores
Aircraft: Boeing 707, registration N7231T, 21 years old
Passengers: 137 Italian vacationers

- The aircraft departed Bergamo after delays, bound for Punta Cana with a refueling stop at Santa Maria in the Azores.
- Navigation charts aboard the flight were dated February 1, 1962, and listed the destination runway elevation incorrectly as zero feet.
- A trainee air traffic controller transmitted a pressure setting nine units too high, which would place the aircraft 240 feet lower than indicated.
- A supervisor noticed the incorrect transmission, was interrupted by a phone call, and did not correct the pressure setting over the radio.
- The crew descended below the sector's minimum safe altitude without completing the approach briefing that would have shown the correct figure.

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/74743245Sat, 19 Sep 2026 08:00:03 +0000Creator at ObomediaA trainee controller read the wrong pressure over radio, placing the jet low over Pico Alto - did they make it in time? The pressure setting spoken over the radio pushed them below safety in time In this episode, we lay out the sequence of...
The pressure setting spoken over the radio pushed them below safety in time

In this episode, we lay out the sequence of decisions, procedures, and missing steps that preceded the crash of Independent Air Flight 1851. We follow the crew, the aging Boeing 707, the outdated charts, and the radio call that shifted the aircraft's altitude - who missed the correction and why does it matter?

Event: Independent Air Flight 1851 crash
Date: February 8, 1989
Location: Pico Alto, Santa Maria, Azores
Aircraft: Boeing 707, registration N7231T, 21 years old
Passengers: 137 Italian vacationers

- The aircraft departed Bergamo after delays, bound for Punta Cana with a refueling stop at Santa Maria in the Azores.
- Navigation charts aboard the flight were dated February 1, 1962, and listed the destination runway elevation incorrectly as zero feet.
- A trainee air traffic controller transmitted a pressure setting nine units too high, which would place the aircraft 240 feet lower than indicated.
- A supervisor noticed the incorrect transmission, was interrupted by a phone call, and did not correct the pressure setting over the radio.
- The crew descended below the sector's minimum safe altitude without completing the approach briefing that would have shown the correct figure.

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.]]>1023falsefullhttps://www.spreaker.com/episode/snow-signal-silence-how-pilots-landed-between-runway-and-death--73097045
A buried antenna bent a navigation beam roughly 200 feet off course and six crews flew that same misleading signal for five days-so why did nobody report it before a jet landed in a snow-covered field? What the cockpit voice recorder and NTSB would reveal about fatigue, training, and silence can only be heard by pressing play.

In this episode, we lay out the sequence of events, the human and technical factors at play, and the unresolved questions that followed the March 4, 2019 event. Was it a failure of systems, procedures, or people that let a localizer steer aircraft into a frozen field?

Date: March 4, 2019
Aircraft: Embraer EMB-145XR, registration N14171
Operator: CommutAir operating as United Express
Location: Presque Isle International Airport, Maine
Reported deviation: Localizer signal displaced approximately 200 feet to the right

- The localizer antenna was buried under two to five feet of snow, bending the signal toward a grass field.
- Six CommutAir crews noticed the localizer problem within five days; none filed an internal safety report before the accident.
- One crew reported a lateral localizer error to Boston ARTCC 36 hours before the accident; FAA procedure required a second independent report for action.
- First officer had ~5,000 total flight hours and ~470 hours on the EMB-145XR; he had about five hours of sleep the night before.
- Captain had ~5,655 total flight hours with 1,044 hours on the EMB-145XR and a documented history of training issues and increased company scrutiny.

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/73097045Sat, 19 Sep 2026 08:00:03 +0000Creator at ObomediaSnow, Signal, Silence: How Pilots Landed Between Runway and Death A buried antenna bent a navigation beam roughly 200 feet off course and six crews flew that same misleading signal for five days-so why did nobody report it before a jet landed in a...
A buried antenna bent a navigation beam roughly 200 feet off course and six crews flew that same misleading signal for five days-so why did nobody report it before a jet landed in a snow-covered field? What the cockpit voice recorder and NTSB would reveal about fatigue, training, and silence can only be heard by pressing play.

In this episode, we lay out the sequence of events, the human and technical factors at play, and the unresolved questions that followed the March 4, 2019 event. Was it a failure of systems, procedures, or people that let a localizer steer aircraft into a frozen field?

Date: March 4, 2019
Aircraft: Embraer EMB-145XR, registration N14171
Operator: CommutAir operating as United Express
Location: Presque Isle International Airport, Maine
Reported deviation: Localizer signal displaced approximately 200 feet to the right

- The localizer antenna was buried under two to five feet of snow, bending the signal toward a grass field.
- Six CommutAir crews noticed the localizer problem within five days; none filed an internal safety report before the accident.
- One crew reported a lateral localizer error to Boston ARTCC 36 hours before the accident; FAA procedure required a second independent report for action.
- First officer had ~5,000 total flight hours and ~470 hours on the EMB-145XR; he had about five hours of sleep the night before.
- Captain had ~5,655 total flight hours with 1,044 hours on the EMB-145XR and a documented history of training issues and increased company scrutiny.

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.]]>1156falsefullhttps://www.spreaker.com/episode/the-cargo-door-began-to-open-thirty-three-seconds-after-takeoff-enough-time--74743244
The cargo door began to open thirty‑three seconds after takeoff - enough time?

In this episode, we follow the minutes after a McDonnell Douglas DC‑9’s cargo door began to open thirty‑three seconds after liftoff. The episode lays out the cockpit actions, the aircraft’s history and the chain of technical and procedural gaps that set the stage - could routine habits and a broken warning light be enough to avert disaster?

Person: Gerald Jack McCall
Person: Thomas Bill Johnston
Date: March 18, 1989
Aircraft: McDonnell Douglas DC‑9, registration N931F
Event: Cargo door began to open 33 seconds after takeoff

- Both pilots had extensive combined flight experience and specific DC‑9 hours, with McCall serving as a check airman.
- The cargo door warning light on the instrument panel was broken and had been nonfunctional for years without being fixed.
- A safety modification that could have prevented the failure existed thirteen years before the accident but was never made mandatory.
- After takeoff the crew heard wind noise and received multiple GPWS alerts, then reported “Okay, we got a cargo door open” and initiated a return to Carswell.
- The CVR and flight data show the crew climbed to 2,500 feet and began an emergency approach with less than two minutes of controlled flight remaining.

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/74743244Fri, 18 Sep 2026 08:00:03 +0000Creator at ObomediaThirty-three seconds after takeoff a DC‑9’s cargo door began to peel open over Fort Worth - did they make it in time? The cargo door began to open thirty‑three seconds after takeoff - enough time? In this episode, we follow the minutes after a...
The cargo door began to open thirty‑three seconds after takeoff - enough time?

In this episode, we follow the minutes after a McDonnell Douglas DC‑9’s cargo door began to open thirty‑three seconds after liftoff. The episode lays out the cockpit actions, the aircraft’s history and the chain of technical and procedural gaps that set the stage - could routine habits and a broken warning light be enough to avert disaster?

Person: Gerald Jack McCall
Person: Thomas Bill Johnston
Date: March 18, 1989
Aircraft: McDonnell Douglas DC‑9, registration N931F
Event: Cargo door began to open 33 seconds after takeoff

- Both pilots had extensive combined flight experience and specific DC‑9 hours, with McCall serving as a check airman.
- The cargo door warning light on the instrument panel was broken and had been nonfunctional for years without being fixed.
- A safety modification that could have prevented the failure existed thirteen years before the accident but was never made mandatory.
- After takeoff the crew heard wind noise and received multiple GPWS alerts, then reported “Okay, we got a cargo door open” and initiated a return to Carswell.
- The CVR and flight data show the crew climbed to 2,500 feet and began an emergency approach with less than two minutes of controlled flight remaining.

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.]]>930falsefullhttps://www.spreaker.com/episode/they-survived-impact-then-a-windshield-lie-burned-78-alive--73097042
Rain on a windshield, a thirty-day-old Tu-134, and every person on board surviving impact - yet seventy-eight died afterward. A precise optical illusion in a cumulonimbus storm fooled an experienced crew into a runway they could not actually see; what happened in the three seconds before impact that no investigator could fully explain?

In this episode, we follow Aviogenex Flight JJ 130 from Gatwick to Rijeka and describe the flight, the crew, the weather, and the moments that led from a surviving impact to a fatal post-crash fire. How did instrument flying through heavy rain, a disrupted stabilized approach, and a windshield illusion combine to kill so many people who had already survived the crash?

Date: May 23, 1971
Aircraft: Tupolev Tu-134A YU-AHZ
Passengers and crew: 83 people on board
Survivors of impact: 83 survived the impact; 78 later died
Flight route: Gatwick Airport to Rijeka

- Aircraft had 111 hours of flight time and had been in Yugoslavia for 30 days.
- Captain Miloš Markićević had 9,230 total flight hours and 138 hours on the Tu-134A.
- First officer Stevan Mandić had 2,300 total hours and 899 hours on the Tu-134 (nearly seven times more Tu-134 time than the captain).
- Cloud base was 600 meters with a cumulonimbus producing torrential rain over the Učka range during descent.
- A burst of turbulence 50 seconds before impact rolled the aircraft right, leaving the approach high, fast and displaced; no recorded call for a go-around followed.

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/73097042Fri, 18 Sep 2026 08:00:03 +0000Creator at ObomediaThey Survived Impact - Then a Windshield Lie Burned 78 Alive Rain on a windshield, a thirty-day-old Tu-134, and every person on board surviving impact - yet seventy-eight died afterward. A precise optical illusion in a cumulonimbus storm fooled an...
Rain on a windshield, a thirty-day-old Tu-134, and every person on board surviving impact - yet seventy-eight died afterward. A precise optical illusion in a cumulonimbus storm fooled an experienced crew into a runway they could not actually see; what happened in the three seconds before impact that no investigator could fully explain?

In this episode, we follow Aviogenex Flight JJ 130 from Gatwick to Rijeka and describe the flight, the crew, the weather, and the moments that led from a surviving impact to a fatal post-crash fire. How did instrument flying through heavy rain, a disrupted stabilized approach, and a windshield illusion combine to kill so many people who had already survived the crash?

Date: May 23, 1971
Aircraft: Tupolev Tu-134A YU-AHZ
Passengers and crew: 83 people on board
Survivors of impact: 83 survived the impact; 78 later died
Flight route: Gatwick Airport to Rijeka

- Aircraft had 111 hours of flight time and had been in Yugoslavia for 30 days.
- Captain Miloš Markićević had 9,230 total flight hours and 138 hours on the Tu-134A.
- First officer Stevan Mandić had 2,300 total hours and 899 hours on the Tu-134 (nearly seven times more Tu-134 time than the captain).
- Cloud base was 600 meters with a cumulonimbus producing torrential rain over the Učka range during descent.
- A burst of turbulence 50 seconds before impact rolled the aircraft right, leaving the approach high, fast and displaced; no recorded call for a go-around followed.

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.]]>1021falsefullhttps://www.spreaker.com/episode/a-ten-month-old-q400-stalled-its-landing-and-cost-fifty-lives--74743243
A ten‑month‑old Q400 stalled its landing and cost fifty lives

In this episode we follow the flight from Newark to Buffalo and the fifty-nine minutes between departure and impact, tracing decisions, crew condition, and procedural gaps that shaped the final moments. What choices and missing data created the pathway to catastrophe?

Date: February 12, 2009
Aircraft: Bombardier Q400, registration N200WQ
Flight: Colgan Air Flight 3407, Newark to Buffalo
People: 45 passengers, 2 flight attendants, 2 cockpit crew
Location: struck house at 6038 Long Street, Clarence Center, New York

- Captain Marvin Renslow, 47, with 3,379 total hours but only 111 hours as Q400 captain and prior failed check rides the airline did not see.
- First Officer Rebecca Lynne Shaw, 24, with 2,244 total hours, had commuted overnight from Seattle and had not slept in a bed before reporting for duty.
- The newly delivered Q400 was ten months old with 18,119 hours/cycles and showed no systemic mechanical failure in initial data.
- The cockpit voice recorder captured the last 41 seconds of silence where a mayday would normally occur, while investigators focused on crew actions rather than equipment.
- The training-records database that would have revealed Renslow’s full history did not exist at the time and became operational only in May 2021.

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/74743243Thu, 17 Sep 2026 08:00:03 +0000Creator at ObomediaA ten-month-old Q400 vanishes from radar five miles short of Buffalo. Did they make it in time? A ten‑month‑old Q400 stalled its landing and cost fifty lives In this episode we follow the flight from Newark to Buffalo and the fifty-nine minutes...
A ten‑month‑old Q400 stalled its landing and cost fifty lives

In this episode we follow the flight from Newark to Buffalo and the fifty-nine minutes between departure and impact, tracing decisions, crew condition, and procedural gaps that shaped the final moments. What choices and missing data created the pathway to catastrophe?

Date: February 12, 2009
Aircraft: Bombardier Q400, registration N200WQ
Flight: Colgan Air Flight 3407, Newark to Buffalo
People: 45 passengers, 2 flight attendants, 2 cockpit crew
Location: struck house at 6038 Long Street, Clarence Center, New York

- Captain Marvin Renslow, 47, with 3,379 total hours but only 111 hours as Q400 captain and prior failed check rides the airline did not see.
- First Officer Rebecca Lynne Shaw, 24, with 2,244 total hours, had commuted overnight from Seattle and had not slept in a bed before reporting for duty.
- The newly delivered Q400 was ten months old with 18,119 hours/cycles and showed no systemic mechanical failure in initial data.
- The cockpit voice recorder captured the last 41 seconds of silence where a mayday would normally occur, while investigators focused on crew actions rather than equipment.
- The training-records database that would have revealed Renslow’s full history did not exist at the time and became operational only in May 2021.

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.]]>900falsefullhttps://www.spreaker.com/episode/missing-safety-why-dash-8-flight-1600-vanished-in-13-minutes--73097040
A 30-minute hop became silence in 13 minutes: a Dash 8 with 38,421 flight hours and two experienced pilots disappeared after departing Lae, killing 28 of 32 on board - and investigators found a missing safety device that should have stopped it. What prevented a routine flight from becoming a catastrophe, and why was that safety mechanism not fitted?

In this episode, we tell what happened on Flight 1600 from takeoff at 16:47 on October 13, 2011, through the decision to deviate around a storm and the descent that followed, and we follow the investigation that led to a June 15, 2014 report changing Dash 8 regulations. How did a routine diversion and a missing mechanical stop lead to crash near the mouth of the Guabe River?

Date: October 13, 2011
Aircraft: de Havilland Dash 8 (registration P2-MCJ)
Flight: Airlines PNG Flight 1600, Lae Nadzab to Madang
Casualties: 28 fatalities out of 32 occupants
Report: Final investigation issued June 15, 2014

- Departure time: 16:47 local time from Lae Nadzab Airport
- Scheduled flight time: 30 minutes; aircraft disappeared 13 minutes after takeoff
- Airframe hours/cycles: 38,421 flight hours, 48,093 cycles
- Crew hours: Captain William Spencer 18,200 total hours (500 on type); First Officer Campbell Wagstaff 2,725 total hours (390 on type)
- Aircraft configuration: delivered without a specific safety mechanism (flight idle gate absence noted)

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/73097040Thu, 17 Sep 2026 08:00:02 +0000Creator at ObomediaMissing Safety: Why Dash 8 Flight 1600 Vanished in 13 Minutes A 30-minute hop became silence in 13 minutes: a Dash 8 with 38,421 flight hours and two experienced pilots disappeared after departing Lae, killing 28 of 32 on board - and investigators...
A 30-minute hop became silence in 13 minutes: a Dash 8 with 38,421 flight hours and two experienced pilots disappeared after departing Lae, killing 28 of 32 on board - and investigators found a missing safety device that should have stopped it. What prevented a routine flight from becoming a catastrophe, and why was that safety mechanism not fitted?

In this episode, we tell what happened on Flight 1600 from takeoff at 16:47 on October 13, 2011, through the decision to deviate around a storm and the descent that followed, and we follow the investigation that led to a June 15, 2014 report changing Dash 8 regulations. How did a routine diversion and a missing mechanical stop lead to crash near the mouth of the Guabe River?

Date: October 13, 2011
Aircraft: de Havilland Dash 8 (registration P2-MCJ)
Flight: Airlines PNG Flight 1600, Lae Nadzab to Madang
Casualties: 28 fatalities out of 32 occupants
Report: Final investigation issued June 15, 2014

- Departure time: 16:47 local time from Lae Nadzab Airport
- Scheduled flight time: 30 minutes; aircraft disappeared 13 minutes after takeoff
- Airframe hours/cycles: 38,421 flight hours, 48,093 cycles
- Crew hours: Captain William Spencer 18,200 total hours (500 on type); First Officer Campbell Wagstaff 2,725 total hours (390 on type)
- Aircraft configuration: delivered without a specific safety mechanism (flight idle gate absence noted)

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.]]>978falsefullhttps://www.spreaker.com/episode/the-word-emergency-never-came-and-the-fuel-ran-out-sixteen-miles-short--74743242
The word "emergency" never came - and the fuel ran out sixteen miles short

In this episode, we reconstruct the timeline, calls, and cockpit decisions from departure in Medellín to the hillside in Cove Neck, showing how fuel, weather, maintenance quirks, and radio exchanges converged. What choices and missed words made the difference between reaching a runway and losing radio contact?

Person: Captain Laureano Caviedes Hoyos
Person: First Officer Mauricio Klotz
Person: Flight Engineer Matias Moyano
Aircraft: Boeing 707 HK-2016
Event: Fuel exhaustion sixteen miles from Kennedy

- Departed Medellín at 15:08 EST with 78,000 pounds of fuel against a 73,930-pound minimum.
- Autopilot and altitude-hold disabled before flight, requiring manual flying during the New York leg.
- Hush kits and airframe age raised fuel burn by roughly five percent each, increasing consumption over the planned rate.
- Kennedy was operating in dense fog, low ceiling, wind shear advisories, and stacked arrivals that imposed extended holding.
- A New York Approach controller asked at 21:34 whether Flight 052 had enough fuel and received no reply.

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/74743242Wed, 16 Sep 2026 08:00:03 +0000Creator at ObomediaA Bogotá-New York Boeing 707 runs low on fuel and falls silent sixteen miles from Kennedy as controllers wait - did they declare an emergency in time? The word "emergency" never came - and the fuel ran out sixteen miles short In this episode, we...
The word "emergency" never came - and the fuel ran out sixteen miles short

In this episode, we reconstruct the timeline, calls, and cockpit decisions from departure in Medellín to the hillside in Cove Neck, showing how fuel, weather, maintenance quirks, and radio exchanges converged. What choices and missed words made the difference between reaching a runway and losing radio contact?

Person: Captain Laureano Caviedes Hoyos
Person: First Officer Mauricio Klotz
Person: Flight Engineer Matias Moyano
Aircraft: Boeing 707 HK-2016
Event: Fuel exhaustion sixteen miles from Kennedy

- Departed Medellín at 15:08 EST with 78,000 pounds of fuel against a 73,930-pound minimum.
- Autopilot and altitude-hold disabled before flight, requiring manual flying during the New York leg.
- Hush kits and airframe age raised fuel burn by roughly five percent each, increasing consumption over the planned rate.
- Kennedy was operating in dense fog, low ceiling, wind shear advisories, and stacked arrivals that imposed extended holding.
- A New York Approach controller asked at 21:34 whether Flight 052 had enough fuel and received no reply.

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.]]>998falsefullhttps://www.spreaker.com/episode/the-invisible-force-that-pulled-flight-771-from-the-sky--73097039
A routine morning flight became a silent catastrophe: an eight-month-old Airbus A330 hit the ground at 262 knots, killing 103 of the 104 people on board and leaving a single nine-year-old survivor. How did an aircraft with every system working and crews who had rested still end up crashing on approach - and what hidden event two weeks earlier was waiting unread on the flight data recorder?

In this episode, we tell the sequence of events on Afriqiyah Airways Flight 771 from boarding in Johannesburg to the final minutes approaching Tripoli, outlining the passengers, crew, aircraft history and the procedural gaps that preceded impact. What exactly in the cockpit conversation and the aircraft’s recent history allowed disaster to unfold?

Event: Afriqiyah Airways Flight 771
Date: 12 May 2010
Aircraft: Airbus A330-202, registration 5A-ONG
People on board: 104 (103 fatalities, 1 survivor)
Captain total hours: 17,016

- Impact speed recorded at 262 knots on ground strike.
- Aircraft entry into service: 15 September 2009; approximately 2,175 flight hours and 572 cycles by crash.
- Seventy-one of 104 passengers were Dutch, with 38 booked through Stip and 24 through Kras.
- Crew on duty: three Libyan pilots with identical A330 time listed as 516 hours each.
- An unreported overspeed event occurred on 28 April 2010, recorded in 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/73097039Wed, 16 Sep 2026 08:00:03 +0000Creator at ObomediaThe Invisible Force That Pulled Flight 771 From the Sky A routine morning flight became a silent catastrophe: an eight-month-old Airbus A330 hit the ground at 262 knots, killing 103 of the 104 people on board and leaving a single nine-year-old...
A routine morning flight became a silent catastrophe: an eight-month-old Airbus A330 hit the ground at 262 knots, killing 103 of the 104 people on board and leaving a single nine-year-old survivor. How did an aircraft with every system working and crews who had rested still end up crashing on approach - and what hidden event two weeks earlier was waiting unread on the flight data recorder?

In this episode, we tell the sequence of events on Afriqiyah Airways Flight 771 from boarding in Johannesburg to the final minutes approaching Tripoli, outlining the passengers, crew, aircraft history and the procedural gaps that preceded impact. What exactly in the cockpit conversation and the aircraft’s recent history allowed disaster to unfold?

Event: Afriqiyah Airways Flight 771
Date: 12 May 2010
Aircraft: Airbus A330-202, registration 5A-ONG
People on board: 104 (103 fatalities, 1 survivor)
Captain total hours: 17,016

- Impact speed recorded at 262 knots on ground strike.
- Aircraft entry into service: 15 September 2009; approximately 2,175 flight hours and 572 cycles by crash.
- Seventy-one of 104 passengers were Dutch, with 38 booked through Stip and 24 through Kras.
- Crew on duty: three Libyan pilots with identical A330 time listed as 516 hours each.
- An unreported overspeed event occurred on 28 April 2010, recorded in 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.]]>1122falsefullhttps://www.spreaker.com/episode/the-temperature-column-that-cut-nine-knots-and-stole-time--74743241
The temperature column that cut nine knots and stole time

In this episode, we follow the moments leading up to a February 16, 1995 ferry flight where a three-engine Douglas DC-8 prepared to depart Kansas City. The episode traces the aircraft's history, the crew's records and the critical preflight calculation that would shape the final minutes - could one temperature column have cost them control?

Date: February 16, 1995
Aircraft: Douglas DC-8-63F N782AL
Location: Kansas City, runway 01L
Crew: Walter Miga Sr., Mark Ulmer, Kerry Hardy
Flight hours (aircraft): 77,096 hours

- The DC-8 had been built in 1968 and cycled through six operators before ATI acquired it in 1994.
- N782AL had 22,404 takeoff-and-landing cycles and one engine that would not start for the repositioning leg.
- Captain Walter Miga had mixed evaluations and this was his first three-engine ferry as captain.
- First officer Mark Ulmer lacked a DC-8 type rating and had multiple prior failed checks; both he and the flight engineer were on probation.
- Flight engineer Kerry Hardy computed Vmc using a temperature conversion column and wrote 107 knots when the correct Vmc was 116 knots.

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/74743241Tue, 15 Sep 2026 08:00:03 +0000Creator at ObomediaA Kansas City flight crew misreads a performance chart and sets takeoff speed nine knots too low - did they make it in time? The temperature column that cut nine knots and stole time In this episode, we follow the moments leading up to a...
The temperature column that cut nine knots and stole time

In this episode, we follow the moments leading up to a February 16, 1995 ferry flight where a three-engine Douglas DC-8 prepared to depart Kansas City. The episode traces the aircraft's history, the crew's records and the critical preflight calculation that would shape the final minutes - could one temperature column have cost them control?

Date: February 16, 1995
Aircraft: Douglas DC-8-63F N782AL
Location: Kansas City, runway 01L
Crew: Walter Miga Sr., Mark Ulmer, Kerry Hardy
Flight hours (aircraft): 77,096 hours

- The DC-8 had been built in 1968 and cycled through six operators before ATI acquired it in 1994.
- N782AL had 22,404 takeoff-and-landing cycles and one engine that would not start for the repositioning leg.
- Captain Walter Miga had mixed evaluations and this was his first three-engine ferry as captain.
- First officer Mark Ulmer lacked a DC-8 type rating and had multiple prior failed checks; both he and the flight engineer were on probation.
- Flight engineer Kerry Hardy computed Vmc using a temperature conversion column and wrote 107 knots when the correct Vmc was 116 knots.

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.]]>758falsefullhttps://www.spreaker.com/episode/thirteen-journalists-one-monsoon-night-the-missing-reports-of-1949--73097036
A four-engine Constellation carrying 45 people slammed into a Bombay hillside at 0:07 on July 12, 1949, wiping out thirteen top American journalists whose dispatches never reached their newspapers - so what were they doing on a Dutch government charter and what did the wreckage hide from the public? How did a routine press tour meant to sway American opinion end with no stories filed and no survivors?

In this episode, we lay out the sequence of events that put those reporting legends on board, describe the Dutch-organized itinerary through the Dutch East Indies, and trace the flight’s final hours through monsoon cloud to the unresolved question of what the press tour was meant to accomplish and why those conclusions never appeared.

Date: July 12, 1949
Event: Aircraft struck a hill near Ghatkopar
Aircraft: Lockheed L-749 Constellation PH-TDF named Franeker
Passengers aboard: 45
Journalists killed: 13 from major US news outlets

- Crash time recorded at seven minutes past midnight (00:07) local time.
- Aircraft was two minutes from the runway when it struck the hill.
- The press tour had covered six thousand kilometres across the Dutch East Indies.
- Captain Arnoldus Marcelis van der Vaart logged over 4,000 total flight hours and more than 1,300 on the Constellation.
- The Franeker had been in service since 1947 and accumulated several thousand flight hours without a serious incident.

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/73097036Tue, 15 Sep 2026 08:00:03 +0000Creator at ObomediaThirteen Journalists, One Monsoon Night: The Missing Reports of 1949 A four-engine Constellation carrying 45 people slammed into a Bombay hillside at 0:07 on July 12, 1949, wiping out thirteen top American journalists whose dispatches never reached...
A four-engine Constellation carrying 45 people slammed into a Bombay hillside at 0:07 on July 12, 1949, wiping out thirteen top American journalists whose dispatches never reached their newspapers - so what were they doing on a Dutch government charter and what did the wreckage hide from the public? How did a routine press tour meant to sway American opinion end with no stories filed and no survivors?

In this episode, we lay out the sequence of events that put those reporting legends on board, describe the Dutch-organized itinerary through the Dutch East Indies, and trace the flight’s final hours through monsoon cloud to the unresolved question of what the press tour was meant to accomplish and why those conclusions never appeared.

Date: July 12, 1949
Event: Aircraft struck a hill near Ghatkopar
Aircraft: Lockheed L-749 Constellation PH-TDF named Franeker
Passengers aboard: 45
Journalists killed: 13 from major US news outlets

- Crash time recorded at seven minutes past midnight (00:07) local time.
- Aircraft was two minutes from the runway when it struck the hill.
- The press tour had covered six thousand kilometres across the Dutch East Indies.
- Captain Arnoldus Marcelis van der Vaart logged over 4,000 total flight hours and more than 1,300 on the Constellation.
- The Franeker had been in service since 1947 and accumulated several thousand flight hours without a serious incident.

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.]]>1120falsefullhttps://www.spreaker.com/episode/the-piper-s-missing-clearance-ran-into-the-dc-9-did-anyone-make-it-out--74743240
The Piper's missing clearance ran into the DC‑9 - did anyone make it out?

In this episode, we follow the minutes before and after two aircraft occupied the same cubic foot of sky above Cerritos, California, on August 31, 1986, and trace how parallel decisions and system gaps converged into disaster. What breakdowns allowed a private Piper to enter protected terminal airspace and collide with a commercial DC‑9?

Date: August 31, 1986
Location: Cerritos, California
Event: Midair collision between Piper PA‑28 and McDonnell Douglas DC‑9‑32
Aircraft: Piper PA‑28‑181 Archer N4891F; DC‑9‑32 XA‑JED (Hermosillo)
Casualties: 82 fatalities reported

- At 11:40 AM the Piper departed Torrance bound for Big Bear City and entered the outer edge of the Los Angeles Terminal Control Area without recorded clearance.
- Aeroméxico Flight 498, DC‑9 XA‑JED, was on approach to LAX after stops in Guadalajara, Loreto, and Tijuana with 64 aboard and experienced crews current on type.
- At 11:52 AM both airplanes occupied the same cubic foot of sky above Cerritos; neither crew saw the other before impact.
- The Piper struck the DC‑9 at the base of the horizontal stabilizer, shearing control surfaces and immediately rendering the jet uncontrollable.
- The Piper crashed onto an empty school playground while the DC‑9 plunged into Ashworth Place, destroying homes and igniting fires across a residential block.

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/74743240Mon, 14 Sep 2026 08:00:03 +0000Creator at ObomediaA small Piper without clearance crossed into LAX terminal airspace and struck a DC‑9 over Cerritos - did anyone make it in time? The Piper's missing clearance ran into the DC‑9 - did anyone make it out? In this episode, we follow the minutes...
The Piper's missing clearance ran into the DC‑9 - did anyone make it out?

In this episode, we follow the minutes before and after two aircraft occupied the same cubic foot of sky above Cerritos, California, on August 31, 1986, and trace how parallel decisions and system gaps converged into disaster. What breakdowns allowed a private Piper to enter protected terminal airspace and collide with a commercial DC‑9?

Date: August 31, 1986
Location: Cerritos, California
Event: Midair collision between Piper PA‑28 and McDonnell Douglas DC‑9‑32
Aircraft: Piper PA‑28‑181 Archer N4891F; DC‑9‑32 XA‑JED (Hermosillo)
Casualties: 82 fatalities reported

- At 11:40 AM the Piper departed Torrance bound for Big Bear City and entered the outer edge of the Los Angeles Terminal Control Area without recorded clearance.
- Aeroméxico Flight 498, DC‑9 XA‑JED, was on approach to LAX after stops in Guadalajara, Loreto, and Tijuana with 64 aboard and experienced crews current on type.
- At 11:52 AM both airplanes occupied the same cubic foot of sky above Cerritos; neither crew saw the other before impact.
- The Piper struck the DC‑9 at the base of the horizontal stabilizer, shearing control surfaces and immediately rendering the jet uncontrollable.
- The Piper crashed onto an empty school playground while the DC‑9 plunged into Ashworth Place, destroying homes and igniting fires across a residential block.

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.]]>1214falsefullhttps://www.spreaker.com/episode/the-ring-that-survived-mike-todd-s-overloaded-flight-to-nowhere--73097034
A single wedding ring returned intact while a twin-engine Lockheed Lodestar exploded and scattered four men across a desert hillside near Grants, New Mexico. The flight carried extra fuel tanks that pushed the aircraft above its maximum gross weight, ice formed at altitude, and one engine failed - so how did small decisions before takeoff turn a routine trip into a fatal crash?

In this episode, we tell the sequence of events on March 22, 1958, from Mike Todd’s last-minute calls and the plane’s known overload to the investigators’ reconstruction of engine failure and icing; what decisions stacked together made a survivable failure deadly?

Person: Mike Todd
Date: March 22, 1958
Location: Near Grants, New Mexico
Event: Lockheed Lodestar crash with engine failure and icing at altitude
Status: Four fatalities, one returned wedding ring intact

- Aircraft: Lockheed Lodestar modified with two extra fuel tanks filled to capacity that night.
- Weight: Modifications and full tanks pushed the aircraft above its official maximum gross weight.
- Occupants: Four men aboard - Mike Todd, pilot Bill Verner, co-pilot Tom Barclay, and writer Art Cohn; no survivors.
- Prior flight: Same aircraft flew overloaded to Albuquerque five days earlier and landed without incident.
- Cause findings: Evidence of icing at altitude and the documented failure of one engine during 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/73097034Mon, 14 Sep 2026 08:00:02 +0000Creator at ObomediaThe Ring That Survived: Mike Todd's Overloaded Flight to Nowhere A single wedding ring returned intact while a twin-engine Lockheed Lodestar exploded and scattered four men across a desert hillside near Grants, New Mexico. The flight carried extra...
A single wedding ring returned intact while a twin-engine Lockheed Lodestar exploded and scattered four men across a desert hillside near Grants, New Mexico. The flight carried extra fuel tanks that pushed the aircraft above its maximum gross weight, ice formed at altitude, and one engine failed - so how did small decisions before takeoff turn a routine trip into a fatal crash?

In this episode, we tell the sequence of events on March 22, 1958, from Mike Todd’s last-minute calls and the plane’s known overload to the investigators’ reconstruction of engine failure and icing; what decisions stacked together made a survivable failure deadly?

Person: Mike Todd
Date: March 22, 1958
Location: Near Grants, New Mexico
Event: Lockheed Lodestar crash with engine failure and icing at altitude
Status: Four fatalities, one returned wedding ring intact

- Aircraft: Lockheed Lodestar modified with two extra fuel tanks filled to capacity that night.
- Weight: Modifications and full tanks pushed the aircraft above its official maximum gross weight.
- Occupants: Four men aboard - Mike Todd, pilot Bill Verner, co-pilot Tom Barclay, and writer Art Cohn; no survivors.
- Prior flight: Same aircraft flew overloaded to Albuquerque five days earlier and landed without incident.
- Cause findings: Evidence of icing at altitude and the documented failure of one engine during 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.]]>1029falsefullhttps://www.spreaker.com/episode/the-missing-control-tower-left-them-ten-feet-to-decide--74743238
The missing control tower left them ten feet to decide

In this episode, we follow the flight that brought Delta executives to Muscogee County Airport and the trainer pilot who approached without using the traffic pattern. We outline the decisions, aircraft, and procedures in play-and ask how two crews could meet so closely with no tower to coordinate them.

Date: April 22, 1947
Location: Muscogee County Airport, Columbus, Georgia
Person: Captain George R. Cushing
Aircraft: DC-3 (NC49657) and Vultee BT‑13
Status: No control tower; perfect visibility

- Delta’s DC‑3 "Survey" was a converted military transport on a routine airport evaluation flight carrying eight executives.
- Captain George R. Cushing logged 11,091 total hours and was both Delta’s Vice President of Operations and the pilot commanding the mission.
- Muscogee County Airport had no control tower, requiring pilots to fly the standard left-hand traffic pattern and self-separate by visual lookout.
- The BT‑13 trainer, piloted by Joseph Fussell, lifted off minutes earlier and approached from the southeast without flying the published circuit or making position calls.
- At 10:40, Cushing’s DC‑3 was one and a half patterns in and ten feet above the runway when the BT‑13 descended into the same approach path.

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/74743238Sun, 13 Sep 2026 08:00:03 +0000Creator at ObomediaA Delta DC‑3 and a Vultee trainer converge over Muscogee County Airport-ten feet separates life from catastrophe, and no tower to stop it? The missing control tower left them ten feet to decide In this episode, we follow the flight that brought...
The missing control tower left them ten feet to decide

In this episode, we follow the flight that brought Delta executives to Muscogee County Airport and the trainer pilot who approached without using the traffic pattern. We outline the decisions, aircraft, and procedures in play-and ask how two crews could meet so closely with no tower to coordinate them.

Date: April 22, 1947
Location: Muscogee County Airport, Columbus, Georgia
Person: Captain George R. Cushing
Aircraft: DC-3 (NC49657) and Vultee BT‑13
Status: No control tower; perfect visibility

- Delta’s DC‑3 "Survey" was a converted military transport on a routine airport evaluation flight carrying eight executives.
- Captain George R. Cushing logged 11,091 total hours and was both Delta’s Vice President of Operations and the pilot commanding the mission.
- Muscogee County Airport had no control tower, requiring pilots to fly the standard left-hand traffic pattern and self-separate by visual lookout.
- The BT‑13 trainer, piloted by Joseph Fussell, lifted off minutes earlier and approached from the southeast without flying the published circuit or making position calls.
- At 10:40, Cushing’s DC‑3 was one and a half patterns in and ten feet above the runway when the BT‑13 descended into the same approach path.

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.]]>868falsefullhttps://www.spreaker.com/episode/when-two-invisible-defects-turned-a-routine-takeoff-fatal--73097029
A routine morning flight ended thirty-five seconds after liftoff when two unseen defects - twenty pounds and five percent - combined to make a certified aircraft uncontrollable. How could an aircraft depart with no warnings while carrying 580 pounds over max takeoff weight and a center of gravity five percent aft of limits?

In this episode, we present the sequence of events, the people involved, and the mechanical and regulatory gaps that allowed those two conditions to coexist on Flight 5481. What breakdowns in maintenance, weight standards, and procedures left the crew without options?

Event: US Airways Express Flight 5481
Date: January 8, 2003
Aircraft: Beechcraft 1900D, registration N233YV
People aboard: 21 (2 crew, 19 passengers)
Overweight: 580 pounds; center of gravity 5% aft of limit

- Takeoff clearance from Charlotte Douglas International Airport at 08:46 on a Wednesday morning.
- Aircraft lifted off runway 18R and crashed 35 seconds later, killing all 21 aboard.
- Elevator control cables had been adjusted at Vertex Aerospace in Huntington two nights earlier with incorrectly set turnbuckles.
- FAA passenger weight standards used in calculations had not been updated since 1936.
- On paper, weight and balance calculations were within approved limits, but actual weight exceeded max takeoff weight by 580 pounds.

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/73097029Sun, 13 Sep 2026 08:00:03 +0000Creator at ObomediaWhen Two Invisible Defects Turned a Routine Takeoff Fatal A routine morning flight ended thirty-five seconds after liftoff when two unseen defects - twenty pounds and five percent - combined to make a certified aircraft uncontrollable. How could an...
A routine morning flight ended thirty-five seconds after liftoff when two unseen defects - twenty pounds and five percent - combined to make a certified aircraft uncontrollable. How could an aircraft depart with no warnings while carrying 580 pounds over max takeoff weight and a center of gravity five percent aft of limits?

In this episode, we present the sequence of events, the people involved, and the mechanical and regulatory gaps that allowed those two conditions to coexist on Flight 5481. What breakdowns in maintenance, weight standards, and procedures left the crew without options?

Event: US Airways Express Flight 5481
Date: January 8, 2003
Aircraft: Beechcraft 1900D, registration N233YV
People aboard: 21 (2 crew, 19 passengers)
Overweight: 580 pounds; center of gravity 5% aft of limit

- Takeoff clearance from Charlotte Douglas International Airport at 08:46 on a Wednesday morning.
- Aircraft lifted off runway 18R and crashed 35 seconds later, killing all 21 aboard.
- Elevator control cables had been adjusted at Vertex Aerospace in Huntington two nights earlier with incorrectly set turnbuckles.
- FAA passenger weight standards used in calculations had not been updated since 1936.
- On paper, weight and balance calculations were within approved limits, but actual weight exceeded max takeoff weight by 580 pounds.

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.]]>1084falsefullhttps://www.spreaker.com/episode/the-last-end-play-check-missed-did-the-dry-jackscrew-run-out-of-minutes--74743237
The last end-play check missed-did the dry jackscrew run out of minutes?

In this episode, we follow the flight, the plane, and the maintenance history that preceded a catastrophic loss of control. It outlines who was aboard, what the jackscrew did, and how routine inspections and lubrication were supposed to prevent this - but did they do enough in time?

Date: January 31, 2000
Flight: Alaska Airlines Flight 261
Aircraft: McDonnell Douglas MD-83, registration N963AS
Component: Jackscrew and acme nut end-play check last done September 1997
People aboard: 88 (including flight crew, three flight attendants, 83 passengers)

- Captain Ted Thompson and First Officer William Tansky brought a combined 25+ years of MD-80 experience into the cockpit that afternoon.
- The jackscrew was a 22-inch hardened steel rod that moved the horizontal stabilizer through a softer acme nut with two thread sets.
- The aircraft had completed 14,315 pressurization cycles over eight years, a metric investigators used to assess cumulative fatigue.
- Maintenance records show the last proper measurement of the acme nut’s wear-the end-play check-was performed in September 1997, more than two years before the crash.
- Wreckage recovered from the ocean revealed 90% of the acme nut thread worn away and evidence the jackscrew had been running without required lubrication.

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/74743237Sat, 12 Sep 2026 08:00:03 +0000Creator at ObomediaA worn jackscrew and overdue checks leave an MD-83 climbing out of Puerto Vallarta - did the maintenance math run out? The last end-play check missed-did the dry jackscrew run out of minutes? In this episode, we follow the flight, the plane, and...
The last end-play check missed-did the dry jackscrew run out of minutes?

In this episode, we follow the flight, the plane, and the maintenance history that preceded a catastrophic loss of control. It outlines who was aboard, what the jackscrew did, and how routine inspections and lubrication were supposed to prevent this - but did they do enough in time?

Date: January 31, 2000
Flight: Alaska Airlines Flight 261
Aircraft: McDonnell Douglas MD-83, registration N963AS
Component: Jackscrew and acme nut end-play check last done September 1997
People aboard: 88 (including flight crew, three flight attendants, 83 passengers)

- Captain Ted Thompson and First Officer William Tansky brought a combined 25+ years of MD-80 experience into the cockpit that afternoon.
- The jackscrew was a 22-inch hardened steel rod that moved the horizontal stabilizer through a softer acme nut with two thread sets.
- The aircraft had completed 14,315 pressurization cycles over eight years, a metric investigators used to assess cumulative fatigue.
- Maintenance records show the last proper measurement of the acme nut’s wear-the end-play check-was performed in September 1997, more than two years before the crash.
- Wreckage recovered from the ocean revealed 90% of the acme nut thread worn away and evidence the jackscrew had been running without required lubrication.

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.]]>961falsefullhttps://www.spreaker.com/episode/when-a-22-inch-screw-killed-88-the-jackscrew-that-failed-flight-261--73097025
A small sundial in Port Hueneme marks 4:22 PM on January 31-the exact minute 88 people hit the Pacific Ocean after Alaska Airlines Flight 261 lost pitch control. Investigators found a 22‑inch jackscrew with 90% of its threading worn away and almost no lubrication-how did maintenance decisions let that happen?

In this episode, we tell the story of Alaska Airlines Flight 261 and the mechanical and procedural failures that led to the loss of control on January 31, 2000. You’ll hear how maintenance records, a seized federal raid, and warnings from a mechanic fit together to explain why the jackscrew failed.

Person: Captain Ted Thompson, 53, 17,750 total flight hours, over 4,000 on MD-80 series
Person: First Officer William Tansky, 57, 8,060 hours on MD-80
Event: Date of crash, January 31, 2000, time marked at 4:22 PM
Aircraft: MD-83 delivered 1992, 26,584 flight hours, 14,315 cycles
Component: Jackscrew length ~22 inches, 90% of threading worn away

- The sundial at a park near Port Hueneme marks exactly 4:22 PM on January 31, the moment the aircraft hit the ocean.
- Investigators recovered a steel jackscrew roughly the size of a man's forearm, no longer than 22 inches, with 90% of its threading gone.
- The last recorded measurement of end-play was in September 1997, 2 years and 4 months before the crash.
- The last lubrication was performed in September 1999 in San Francisco, listed as a 4‑hour job but recorded as taking approximately 1 hour.
- The aircraft had accumulated 26,584 flight hours and 14,315 cycles by January 31, 2000.

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/73097025Sat, 12 Sep 2026 08:00:02 +0000Creator at ObomediaWhen a 22‑inch Screw Killed 88: The Jackscrew That Failed Flight 261 A small sundial in Port Hueneme marks 4:22 PM on January 31-the exact minute 88 people hit the Pacific Ocean after Alaska Airlines Flight 261 lost pitch control. Investigators...
A small sundial in Port Hueneme marks 4:22 PM on January 31-the exact minute 88 people hit the Pacific Ocean after Alaska Airlines Flight 261 lost pitch control. Investigators found a 22‑inch jackscrew with 90% of its threading worn away and almost no lubrication-how did maintenance decisions let that happen?

In this episode, we tell the story of Alaska Airlines Flight 261 and the mechanical and procedural failures that led to the loss of control on January 31, 2000. You’ll hear how maintenance records, a seized federal raid, and warnings from a mechanic fit together to explain why the jackscrew failed.

Person: Captain Ted Thompson, 53, 17,750 total flight hours, over 4,000 on MD-80 series
Person: First Officer William Tansky, 57, 8,060 hours on MD-80
Event: Date of crash, January 31, 2000, time marked at 4:22 PM
Aircraft: MD-83 delivered 1992, 26,584 flight hours, 14,315 cycles
Component: Jackscrew length ~22 inches, 90% of threading worn away

- The sundial at a park near Port Hueneme marks exactly 4:22 PM on January 31, the moment the aircraft hit the ocean.
- Investigators recovered a steel jackscrew roughly the size of a man's forearm, no longer than 22 inches, with 90% of its threading gone.
- The last recorded measurement of end-play was in September 1997, 2 years and 4 months before the crash.
- The last lubrication was performed in September 1999 in San Francisco, listed as a 4‑hour job but recorded as taking approximately 1 hour.
- The aircraft had accumulated 26,584 flight hours and 14,315 cycles by January 31, 2000.

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.]]>1130falsefullhttps://www.spreaker.com/episode/the-turnbuckles-jammed-the-elevator-did-they-make-it-to-level-flight--74743236
The turnbuckles jammed the elevator - did they make it to level flight?

In this episode, we follow the moments before Air Midwest Flight 5481 departed Charlotte on a short commuter run and the hidden failures that set the stage for catastrophe. It lays out the maintenance error and the outdated passenger-weight assumptions that combined to create an invisible threat - did routine checks miss the danger?

Person: Captain Catherine "Katie" Leslie, 25, 1,865 hours with Air Midwest
Person: First Officer Jonathan Gibbs, 27, 706 hours on the 1900D
Event: Maintenance adjustment of elevator control cables at Tri-State Airport, January 6, 2003
Location: Charlotte Douglas International Airport; flight to Greenville-Spartanburg
Status: Aircraft 580 pounds over takeoff weight and center of gravity 5% aft of approved limit

- A mechanic unfamiliar with the Beechcraft 1900D adjusted elevator cable turnbuckles at a contracted maintenance facility.
- The turnbuckles were set so elevator travel was dramatically restricted, reducing nose-down control authority.
- The required post-adjustment full-range control check was not performed, and the supervisor also acted as quality inspector.
- The aircraft flew from Huntington to Charlotte without obvious problems, leaving no immediate alarm for crew or ramp personnel.
- Air Midwest used an FAA-approved average passenger weight last reviewed in 1936, underestimating actual weights by over 20 pounds per person.

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/74743236Fri, 11 Sep 2026 08:00:03 +0000Creator at ObomediaA commuter turboprop is overloaded and its elevator jammed-can the pilots overcome and make it to level flight? The turnbuckles jammed the elevator - did they make it to level flight? In this episode, we follow the moments before Air Midwest...
The turnbuckles jammed the elevator - did they make it to level flight?

In this episode, we follow the moments before Air Midwest Flight 5481 departed Charlotte on a short commuter run and the hidden failures that set the stage for catastrophe. It lays out the maintenance error and the outdated passenger-weight assumptions that combined to create an invisible threat - did routine checks miss the danger?

Person: Captain Catherine "Katie" Leslie, 25, 1,865 hours with Air Midwest
Person: First Officer Jonathan Gibbs, 27, 706 hours on the 1900D
Event: Maintenance adjustment of elevator control cables at Tri-State Airport, January 6, 2003
Location: Charlotte Douglas International Airport; flight to Greenville-Spartanburg
Status: Aircraft 580 pounds over takeoff weight and center of gravity 5% aft of approved limit

- A mechanic unfamiliar with the Beechcraft 1900D adjusted elevator cable turnbuckles at a contracted maintenance facility.
- The turnbuckles were set so elevator travel was dramatically restricted, reducing nose-down control authority.
- The required post-adjustment full-range control check was not performed, and the supervisor also acted as quality inspector.
- The aircraft flew from Huntington to Charlotte without obvious problems, leaving no immediate alarm for crew or ramp personnel.
- Air Midwest used an FAA-approved average passenger weight last reviewed in 1936, underestimating actual weights by over 20 pounds per person.

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.]]>850falsefullhttps://www.spreaker.com/episode/why-was-tyler-perry-executive-s-vans-rv-12-found-inverted-on-a-road--73097016
A single-engine Vans RV-12IS lay inverted on a public road in Homosassa, Florida on the morning of December 6, 2024 - a light sport aircraft barely larger than a car, owned by Steve Mensch, president and general manager of Tyler Perry Studios. Why was the man who ran a 330-acre studio campus, with twelve soundstages and a paused $800 million expansion because of generative video AI, flying that small two-seat plane in Florida that morning?

In this episode, we present the facts surrounding the crash scene, the scale of Tyler Perry Studios under Mensch’s management, and the unresolved official record about his presence in Homosassa; can the details of the aircraft and the timing of his death explain what happened?

Person: Steve Mensch
Event: Plane crash on road
Date: December 6, 2024
Location: Homosassa, Florida
Aircraft: Vans RV-12IS, light sport, two-seat, wingspan ~26 feet

- The aircraft was found inverted on a road rather than on or near an airfield.
- Steve Mensch served as president and general manager of Tyler Perry Studios.
- Tyler Perry Studios occupies 330 acres on the former Fort McPherson site in southwest Atlanta.
- The campus contains twelve named soundstages and full-scale sets including a replica White House and a 16,000-square-foot mansion.
- In February 2024 Tyler Perry paused an $800 million campus expansion citing advances in generative video AI.

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/73097016Fri, 11 Sep 2026 08:00:03 +0000Creator at ObomediaWhy Was Tyler Perry Executive's Vans RV-12 Found Inverted On A Road? A single-engine Vans RV-12IS lay inverted on a public road in Homosassa, Florida on the morning of December 6, 2024 - a light sport aircraft barely larger than a car, owned by...
A single-engine Vans RV-12IS lay inverted on a public road in Homosassa, Florida on the morning of December 6, 2024 - a light sport aircraft barely larger than a car, owned by Steve Mensch, president and general manager of Tyler Perry Studios. Why was the man who ran a 330-acre studio campus, with twelve soundstages and a paused $800 million expansion because of generative video AI, flying that small two-seat plane in Florida that morning?

In this episode, we present the facts surrounding the crash scene, the scale of Tyler Perry Studios under Mensch’s management, and the unresolved official record about his presence in Homosassa; can the details of the aircraft and the timing of his death explain what happened?

Person: Steve Mensch
Event: Plane crash on road
Date: December 6, 2024
Location: Homosassa, Florida
Aircraft: Vans RV-12IS, light sport, two-seat, wingspan ~26 feet

- The aircraft was found inverted on a road rather than on or near an airfield.
- Steve Mensch served as president and general manager of Tyler Perry Studios.
- Tyler Perry Studios occupies 330 acres on the former Fort McPherson site in southwest Atlanta.
- The campus contains twelve named soundstages and full-scale sets including a replica White House and a 16,000-square-foot mansion.
- In February 2024 Tyler Perry paused an $800 million campus expansion citing advances in generative video AI.

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.]]>1093falsefullhttps://www.spreaker.com/episode/the-stripped-acme-nut-sheared-at-cruise-speed-did-they-land-in-time--74743235
The stripped Acme nut sheared at cruise speed - did they land in time?

In this episode, we follow the final hours of Alaska Airlines Flight 261 and the chain of maintenance decisions, measurements, and missed warnings that set the stage for an in-flight emergency. The narrative tracks the aircraft, crew actions, and the failing jackscrew assembly while asking whether earlier choices cost crucial minutes.

Aircraft: MD-83 N963AS
Event: In-flight jam of horizontal stabilizer trim system
Date: January 31 (timeframe given in transcript)
Crew: Captain Ted Thompson; First Officer William Tansky; three flight attendants
Maintenance history: Last measured September 1997; last lubrication September 1999

- A steel jackscrew rotated through an aluminum-alloy Acme nut beneath the cockpit floor that translated rotation into stabilizer movement.
- Ninety percent of the nut’s threads were gone when the plane departed, described in the transcript as “not worn, gone.”
- A mechanic had warned supervisors three years earlier about this part on that specific aircraft and was later placed on paid leave.
- Scheduled inspections used nonstandard tools and the last formal measurement missed the true condition; lubrication recorded as a four-hour job was logged as about one hour.
- During the flight the trim system jammed, the captain applied continuous force to the yoke, and the crew debated diverting to Los Angeles versus continuing to San Francisco.

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/74743235Thu, 10 Sep 2026 08:00:04 +0000Creator at ObomediaA routine northbound flight faces a hidden crisis when an Acme nut controlling pitch has stripped most threads - did they land in time? The stripped Acme nut sheared at cruise speed - did they land in time? In this episode, we follow the final...
The stripped Acme nut sheared at cruise speed - did they land in time?

In this episode, we follow the final hours of Alaska Airlines Flight 261 and the chain of maintenance decisions, measurements, and missed warnings that set the stage for an in-flight emergency. The narrative tracks the aircraft, crew actions, and the failing jackscrew assembly while asking whether earlier choices cost crucial minutes.

Aircraft: MD-83 N963AS
Event: In-flight jam of horizontal stabilizer trim system
Date: January 31 (timeframe given in transcript)
Crew: Captain Ted Thompson; First Officer William Tansky; three flight attendants
Maintenance history: Last measured September 1997; last lubrication September 1999

- A steel jackscrew rotated through an aluminum-alloy Acme nut beneath the cockpit floor that translated rotation into stabilizer movement.
- Ninety percent of the nut’s threads were gone when the plane departed, described in the transcript as “not worn, gone.”
- A mechanic had warned supervisors three years earlier about this part on that specific aircraft and was later placed on paid leave.
- Scheduled inspections used nonstandard tools and the last formal measurement missed the true condition; lubrication recorded as a four-hour job was logged as about one hour.
- During the flight the trim system jammed, the captain applied continuous force to the yoke, and the crew debated diverting to Los Angeles versus continuing to San Francisco.

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.]]>1232falsefullhttps://www.spreaker.com/episode/eighteen-feet-of-sky-the-flight-that-lost-its-roof--73097013
Blue sky where an aircraft ceiling should be: at 1:46 PM on April 28, 1988, eighteen feet of fuselage roof peeled away at 24,000 feet over the Pacific, yet the plane kept flying - how did a 19‑year‑old Boeing 737 lose its roof with no weather warning and no alarm?

In this episode, we tell what happened on Flight 243 and follow the sequence of events, the people on board, and the maintenance realities that allowed microscopic cracks to grow for years; could a single missed crack at the gate have been the same crack that opened the sky?

Date: April 28, 1988
Aircraft: Boeing 737, registration N73711, line number 152
Altitude at failure: 24,000 feet
Passengers and crew aboard: 96
Fatalities: 1 (Clarabelle Lansing)

- The forward fuselage roof separated in an 18‑foot section at 1:46 PM.
- The aircraft had accumulated 35,496 flight hours and 89,680 flight cycles by that date.
- One person, Clarabelle "C.B." Lansing, age 58, was swept out and did not survive; her body was never recovered.
- The airplane used cold‑bonded lap joints with epoxy and scrim cloth that wicked moisture over 19 years.
- A passenger, Gayle Yamamoto, saw a crack at the gate in Hilo before boarding and did not report it.

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/73097013Thu, 10 Sep 2026 08:00:02 +0000Creator at ObomediaEighteen Feet of Sky: The Flight That Lost Its Roof Blue sky where an aircraft ceiling should be: at 1:46 PM on April 28, 1988, eighteen feet of fuselage roof peeled away at 24,000 feet over the Pacific, yet the plane kept flying - how did a...
Blue sky where an aircraft ceiling should be: at 1:46 PM on April 28, 1988, eighteen feet of fuselage roof peeled away at 24,000 feet over the Pacific, yet the plane kept flying - how did a 19‑year‑old Boeing 737 lose its roof with no weather warning and no alarm?

In this episode, we tell what happened on Flight 243 and follow the sequence of events, the people on board, and the maintenance realities that allowed microscopic cracks to grow for years; could a single missed crack at the gate have been the same crack that opened the sky?

Date: April 28, 1988
Aircraft: Boeing 737, registration N73711, line number 152
Altitude at failure: 24,000 feet
Passengers and crew aboard: 96
Fatalities: 1 (Clarabelle Lansing)

- The forward fuselage roof separated in an 18‑foot section at 1:46 PM.
- The aircraft had accumulated 35,496 flight hours and 89,680 flight cycles by that date.
- One person, Clarabelle "C.B." Lansing, age 58, was swept out and did not survive; her body was never recovered.
- The airplane used cold‑bonded lap joints with epoxy and scrim cloth that wicked moisture over 19 years.
- A passenger, Gayle Yamamoto, saw a crack at the gate in Hilo before boarding and did not report it.

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.]]>1109falsefullhttps://www.spreaker.com/episode/the-night-a-number-one-song-killed-hawksaw-hawkins--73097009
A sudden, small kindness put a rising star on a private plane that crashed 22 minutes after takeoff - killing him three days after his song entered the Billboard country charts. How did a trade of a commercial airline seat for a spot on a four-seat Piper Comanche become the moment that ended Hawkshaw Hawkins's life and stalled a number-one record?

In this episode, we tell the story of Hawkshaw Hawkins from his childhood trade of five rabbits for a guitar through war, radio shows, and a career finally reaching the charts - and the fatal decision on the night of March 5th that led to the Camden, Tennessee crash. What unfolded in the 72 hours between his song charting and the wreckage in the woods?

Person: Harold "Hawkshaw" Hawkins
Date: March 5, 1963
Location: Camden, Tennessee
Event: Piper Comanche crash
Topic: "Lonesome 7-7203" entering the Billboard country charts three days before the crash

- The plane had been airborne for exactly 22 minutes before crashing into a stand of trees outside Camden, Tennessee.
- "Lonesome 7-7203" entered the Billboard country charts on March 2, 1963, 72 hours before the crash.
- Hawkshaw Hawkins was 41 years old at the time of the crash and had a pregnant wife, Jean, and two children, Donnie and adopted daughter Susan Marlene.
- Hawkins had traded five rabbits for his first guitar as a child and later performed on radio shows including WCMI, WSAZ, and WCHS.
- Four people were on the Piper Comanche: Hawkshaw Hawkins, Patsy Cline, Cowboy Copas, and pilot Randy Hughes; Hawkins had given his commercial airline seat to Billy Walker and took the private plane seat instead.

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/73097009Wed, 09 Sep 2026 08:00:03 +0000Creator at ObomediaThe Night a Number-One Song Killed Hawksaw Hawkins A sudden, small kindness put a rising star on a private plane that crashed 22 minutes after takeoff - killing him three days after his song entered the Billboard country charts. How did a trade of...
A sudden, small kindness put a rising star on a private plane that crashed 22 minutes after takeoff - killing him three days after his song entered the Billboard country charts. How did a trade of a commercial airline seat for a spot on a four-seat Piper Comanche become the moment that ended Hawkshaw Hawkins's life and stalled a number-one record?

In this episode, we tell the story of Hawkshaw Hawkins from his childhood trade of five rabbits for a guitar through war, radio shows, and a career finally reaching the charts - and the fatal decision on the night of March 5th that led to the Camden, Tennessee crash. What unfolded in the 72 hours between his song charting and the wreckage in the woods?

Person: Harold "Hawkshaw" Hawkins
Date: March 5, 1963
Location: Camden, Tennessee
Event: Piper Comanche crash
Topic: "Lonesome 7-7203" entering the Billboard country charts three days before the crash

- The plane had been airborne for exactly 22 minutes before crashing into a stand of trees outside Camden, Tennessee.
- "Lonesome 7-7203" entered the Billboard country charts on March 2, 1963, 72 hours before the crash.
- Hawkshaw Hawkins was 41 years old at the time of the crash and had a pregnant wife, Jean, and two children, Donnie and adopted daughter Susan Marlene.
- Hawkins had traded five rabbits for his first guitar as a child and later performed on radio shows including WCMI, WSAZ, and WCHS.
- Four people were on the Piper Comanche: Hawkshaw Hawkins, Patsy Cline, Cowboy Copas, and pilot Randy Hughes; Hawkins had given his commercial airline seat to Billy Walker and took the private plane seat instead.

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.]]>1031falsefullhttps://www.spreaker.com/episode/they-never-said-emergency-the-night-flight-052-ran-out-of-fuel--74743233
They Never Said "Emergency": The Night Flight 052 Ran Out of Fuel

In this episode, we follow the nine-hour flight from Medellín to New York that ended when a Boeing 707 ran out of fuel and struck trees at Cove Neck. The episode traces the crew, aircraft history, fuel planning and the chain of decisions and silences that unfolded - could clearer communication or different choices have changed what happened?

Date: January 25, 1990
Aircraft: Boeing 707
People: 158 aboard
Captain: Laureano Caviedes Hoyos, 51, 16,000+ hours
Fuel at departure: 78,000 pounds

- The flight departed Medellín at 15:03 EST and had been airborne for over nine hours when the engines stopped.
- Avianca's maintenance records noted a hush kit and aircraft age raised fuel burn by about 10% compared with a newer 707.
- The autopilot altitude-hold was inoperative before departure, requiring full manual flying for the whole route.
- The flight entered holding patterns (first over Norfolk at 19:04) and circled New York airspace for more than an hour while ATC communicated with the crew.
- The cockpit voice recorder had been wrapped in adhesive tape before departure, leaving investigators to rely on audio transmissions to piece together the final hour.

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/74743233Wed, 09 Sep 2026 08:00:02 +0000Creator at ObomediaA Boeing 707 circles over New York with engines and radios working but no one ever declares "emergency" - did they make it in time? They Never Said "Emergency": The Night Flight 052 Ran Out of Fuel In this episode, we follow the nine-hour flight...
They Never Said "Emergency": The Night Flight 052 Ran Out of Fuel

In this episode, we follow the nine-hour flight from Medellín to New York that ended when a Boeing 707 ran out of fuel and struck trees at Cove Neck. The episode traces the crew, aircraft history, fuel planning and the chain of decisions and silences that unfolded - could clearer communication or different choices have changed what happened?

Date: January 25, 1990
Aircraft: Boeing 707
People: 158 aboard
Captain: Laureano Caviedes Hoyos, 51, 16,000+ hours
Fuel at departure: 78,000 pounds

- The flight departed Medellín at 15:03 EST and had been airborne for over nine hours when the engines stopped.
- Avianca's maintenance records noted a hush kit and aircraft age raised fuel burn by about 10% compared with a newer 707.
- The autopilot altitude-hold was inoperative before departure, requiring full manual flying for the whole route.
- The flight entered holding patterns (first over Norfolk at 19:04) and circled New York airspace for more than an hour while ATC communicated with the crew.
- The cockpit voice recorder had been wrapped in adhesive tape before departure, leaving investigators to rely on audio transmissions to piece together the final hour.

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.]]>929falsefullhttps://www.spreaker.com/episode/the-eighteen-foot-roof-tore-away-did-anyone-reach-the-exit-in-time--74743231
The eighteen‑foot roof tore away - did anyone reach the exit in time?

In this episode, we follow the sequence of a routine Hawaiian inter‑island flight on April 28, 1988, when an eighteen‑foot section of a Boeing 737’s upper fuselage separated at cruise altitude. The narrative traces the aircraft’s long service, the crew on duty, and the moments before and after the roof failed - what happened next is the central question.

Date: April 28, 1988
Aircraft: Boeing 737 registered N73711
Location: 24,000 feet over the Pacific, 23 nm SSE of Kahului, Maui
Person: Clarabelle Lansing (chief flight attendant, 37 years of service)
Event: Eighteen‑foot section of upper fuselage separated during flight

- The airplane had completed 89,680 pressurization cycles over 19 years on short Hawaiian hops, far exceeding the conditions of its certification lab tests.
- The missing fuselage section spanned from just behind the cockpit to the forward edge of the wing, removing the cockpit door and first‑class ceiling.
- A passenger, Gayle Yamamoto, noticed a crack near the forward door on the jetway before boarding but did not report it.
- The crew that day included Captain Robert Schornstheimer and First Officer Mimi Tompkins, both highly experienced on the 737, with Lansing conducting cabin service near row five.
- At 13:46 HST, witnesses described a single whoosh and sudden wind as insulation and ceiling elements blew into the cabin and cockpit.

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/74743231Tue, 08 Sep 2026 08:00:03 +0000Creator at ObomediaA flight attendant walks the aisle when an eighteen‑foot section of fuselage peels away midflight - did anyone reach the exit in time? The eighteen‑foot roof tore away - did anyone reach the exit in time? In this episode, we follow the sequence...
The eighteen‑foot roof tore away - did anyone reach the exit in time?

In this episode, we follow the sequence of a routine Hawaiian inter‑island flight on April 28, 1988, when an eighteen‑foot section of a Boeing 737’s upper fuselage separated at cruise altitude. The narrative traces the aircraft’s long service, the crew on duty, and the moments before and after the roof failed - what happened next is the central question.

Date: April 28, 1988
Aircraft: Boeing 737 registered N73711
Location: 24,000 feet over the Pacific, 23 nm SSE of Kahului, Maui
Person: Clarabelle Lansing (chief flight attendant, 37 years of service)
Event: Eighteen‑foot section of upper fuselage separated during flight

- The airplane had completed 89,680 pressurization cycles over 19 years on short Hawaiian hops, far exceeding the conditions of its certification lab tests.
- The missing fuselage section spanned from just behind the cockpit to the forward edge of the wing, removing the cockpit door and first‑class ceiling.
- A passenger, Gayle Yamamoto, noticed a crack near the forward door on the jetway before boarding but did not report it.
- The crew that day included Captain Robert Schornstheimer and First Officer Mimi Tompkins, both highly experienced on the 737, with Lansing conducting cabin service near row five.
- At 13:46 HST, witnesses described a single whoosh and sudden wind as insulation and ceiling elements blew into the cabin and cockpit.

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.]]>954falsefullhttps://www.spreaker.com/episode/the-engine-fell-off-flight-191-kept-flying-for-31-seconds--73097006
A missing engine, a clear May afternoon, and 31 seconds of apparent normal flight before the deadliest aviation accident in U.S. history claimed 273 lives - could following the checklist have become the fatal mistake? The engine detached and landed on the runway while the DC-10 climbed away; what the crew could not see would unravel into a year-long investigation into hidden structural damage and procedural consequences.

In this episode, we present the sequence of events from pushback to the moment the left engine separated, outline the crew and aircraft details, and trace how an invisible eight-week-old crack turned a routine departure into catastrophe - would different decisions or inspections have changed what happened?

Date: May 25, 1979
Aircraft: McDonnell Douglas DC-10
People on board: 273
Captain: Walter Lux, 53 years old, ~22,000 flight hours
Event: Left-engine pylon fracture and separation during takeoff

- The left engine separated at rotation and landed on the runway behind the aircraft.
- The DC-10 continued to climb for 31 seconds after the engine fell off.
- The aircraft had carried the hidden pylon crack for eight weeks before failure.
- There were 258 passengers and 15 crew aboard, totaling 273 people on board.
- The speed for a safe single-engine climb in a DC-10 was 153 knots as stated in the manual.

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/73097006Tue, 08 Sep 2026 08:00:02 +0000Creator at ObomediaThe Engine Fell Off - Flight 191 Kept Flying for 31 Seconds A missing engine, a clear May afternoon, and 31 seconds of apparent normal flight before the deadliest aviation accident in U.S. history claimed 273 lives - could following the checklist...
A missing engine, a clear May afternoon, and 31 seconds of apparent normal flight before the deadliest aviation accident in U.S. history claimed 273 lives - could following the checklist have become the fatal mistake? The engine detached and landed on the runway while the DC-10 climbed away; what the crew could not see would unravel into a year-long investigation into hidden structural damage and procedural consequences.

In this episode, we present the sequence of events from pushback to the moment the left engine separated, outline the crew and aircraft details, and trace how an invisible eight-week-old crack turned a routine departure into catastrophe - would different decisions or inspections have changed what happened?

Date: May 25, 1979
Aircraft: McDonnell Douglas DC-10
People on board: 273
Captain: Walter Lux, 53 years old, ~22,000 flight hours
Event: Left-engine pylon fracture and separation during takeoff

- The left engine separated at rotation and landed on the runway behind the aircraft.
- The DC-10 continued to climb for 31 seconds after the engine fell off.
- The aircraft had carried the hidden pylon crack for eight weeks before failure.
- There were 258 passengers and 15 crew aboard, totaling 273 people on board.
- The speed for a safe single-engine climb in a DC-10 was 153 knots as stated in the manual.

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.]]>1048falsefullhttps://www.spreaker.com/episode/the-radio-died-he-kept-broadcasting-the-pilot-s-location-and-burned-up--74743230
The radio died - he kept broadcasting the pilot's location and burned up

In this episode, we follow Lieutenant Colonel William Atkinson Jones III on a September 1, 1968 rescue mission over North Vietnam, tracing the decisions, equipment, and terrain that shaped his choices. What compelled him to keep transmitting while his aircraft burned, and how did that shape the rescue attempt?

Person: William Atkinson Jones III
Date: September 1, 1968
Location: Karst limestone country northwest of Đồng Hới, North Vietnam
Aircraft: A-1H Skyraider
Squadron: 602nd Special Operations Squadron, Nakhon Phanom RTAFB

- Jones left Nakhon Phanom leading four Skyraiders with two helicopters to recover a downed F-4 pilot twenty miles northwest of Đồng Hới.
- The Skyraider’s role was low-altitude loitering: suppress enemy fire, broadcast coordinates, and protect arriving helicopters.
- Cockpit smoke began from an explosion while Jones was running a search pattern over karst towers riddled with gun positions.
- Jones located the downed pilot near a limestone tower with a multiple-barrel gun and made repeated low, direct attack passes with cannon and rockets.
- As he pressed attacks, Jones continuously transmitted the survivor’s location to the rescue aircraft despite his radio and cockpit being compromised.

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/74743230Mon, 07 Sep 2026 08:00:04 +0000Creator at ObomediaA Skyraider pilot’s cockpit fills with smoke over karst limestone as he keeps broadcasting a downed F-4 pilot’s location - did they make it in time? The radio died - he kept broadcasting the pilot's location and burned up In this episode, we...
The radio died - he kept broadcasting the pilot's location and burned up

In this episode, we follow Lieutenant Colonel William Atkinson Jones III on a September 1, 1968 rescue mission over North Vietnam, tracing the decisions, equipment, and terrain that shaped his choices. What compelled him to keep transmitting while his aircraft burned, and how did that shape the rescue attempt?

Person: William Atkinson Jones III
Date: September 1, 1968
Location: Karst limestone country northwest of Đồng Hới, North Vietnam
Aircraft: A-1H Skyraider
Squadron: 602nd Special Operations Squadron, Nakhon Phanom RTAFB

- Jones left Nakhon Phanom leading four Skyraiders with two helicopters to recover a downed F-4 pilot twenty miles northwest of Đồng Hới.
- The Skyraider’s role was low-altitude loitering: suppress enemy fire, broadcast coordinates, and protect arriving helicopters.
- Cockpit smoke began from an explosion while Jones was running a search pattern over karst towers riddled with gun positions.
- Jones located the downed pilot near a limestone tower with a multiple-barrel gun and made repeated low, direct attack passes with cannon and rockets.
- As he pressed attacks, Jones continuously transmitted the survivor’s location to the rescue aircraft despite his radio and cockpit being compromised.

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.]]>1020falsefullhttps://www.spreaker.com/episode/pieces-of-towel-cloth-in-a-fuel-line-killed-two-men-over-connecticut-pine-woods--73097004
A fragment of ordinary shop towel cloth lodged inside a Cessna 182 fuel line and silenced an engine over the pine woods of Plainville, Connecticut - two men aboard did not survive. How did such a small, mundane piece of cloth end a four-decade racing career and a routine flight in one afternoon?

In this episode, we present the documented account of the September 16, 2017 flight, the subsequent NTSB investigation, and the unanswered question about how shop towel material entered the aircraft fuel system; what the record finds - and what it does not - is the subject we pursue.

Person: Ted Christopher
Person: Charles "Pat" Dundas
Date: September 16, 2017
Location: pine woods south of Plainville Airport, Connecticut
Event: engine stoppage due to pieces of towel cloth obstructing a fuel line

- Ted Christopher was 54 years old at the time of the crash.
- The NTSB report states "pieces of towel cloth obstructing a fuel line" as the cause.
- Ted Christopher had 131 feature wins at Stafford Motor Speedway.
- The aircraft was a single-engine Cessna 182 that departed Plainville Airport in the early afternoon.
- Both occupants, Ted Christopher and Charles Dundas, were killed when the engine stopped and the plane crashed.

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/73097004Mon, 07 Sep 2026 08:00:02 +0000Creator at ObomediaPieces of towel cloth in a fuel line killed two men over Connecticut pine woods A fragment of ordinary shop towel cloth lodged inside a Cessna 182 fuel line and silenced an engine over the pine woods of Plainville, Connecticut - two men aboard did...
A fragment of ordinary shop towel cloth lodged inside a Cessna 182 fuel line and silenced an engine over the pine woods of Plainville, Connecticut - two men aboard did not survive. How did such a small, mundane piece of cloth end a four-decade racing career and a routine flight in one afternoon?

In this episode, we present the documented account of the September 16, 2017 flight, the subsequent NTSB investigation, and the unanswered question about how shop towel material entered the aircraft fuel system; what the record finds - and what it does not - is the subject we pursue.

Person: Ted Christopher
Person: Charles "Pat" Dundas
Date: September 16, 2017
Location: pine woods south of Plainville Airport, Connecticut
Event: engine stoppage due to pieces of towel cloth obstructing a fuel line

- Ted Christopher was 54 years old at the time of the crash.
- The NTSB report states "pieces of towel cloth obstructing a fuel line" as the cause.
- Ted Christopher had 131 feature wins at Stafford Motor Speedway.
- The aircraft was a single-engine Cessna 182 that departed Plainville Airport in the early afternoon.
- Both occupants, Ted Christopher and Charles Dundas, were killed when the engine stopped and the plane crashed.

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-single-word-they-never-spoke-ran-the-engines-dead--74743229
The single word they never spoke ran the engines dead

In this episode, we follow the final hours of Avianca Flight 052 as its crew faces creeping fuel starvation, repeated holding patterns, and communication barriers with New York controllers. The episode traces the technical, procedural, and human factors that left the system waiting for a single word-what happens when language is the last line of defense?

Date: January 25, 1990
Aircraft: Boeing 707
Flight: Avianca Flight 052
Location: Cove Neck, Long Island / near JFK Airport
Fatalities: 73

- The flight departed Medellín with block fuel requirements listed and an extra dispatch increment, but modifications and age had quietly increased fuel burn.
- The aircraft carried noise-reduction kits and accumulated over 61,000 flight hours, both factors adding roughly five percent each to fuel consumption.
- The autopilot’s altitude-hold had a known recurring fault; the captain prepared to hand-fly the approach in low visibility with fuel critically low.
- The crew endured three holding stacks-Norfolk, Atlantic City, and CAMRN-totaling ninety-three minutes of extra fuel burn on top of the planned margins.
- Cockpit voice recordings show the crew using trained phrases yet never uttering the specific seven-letter word required by controllers’ emergency protocol.

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/74743229Sun, 06 Sep 2026 08:00:03 +0000Creator at ObomediaA Boeing 707 circles over New York with fuel running low while its crew never says the word that would trigger an emergency-did they make it in time? The single word they never spoke ran the engines dead In this episode, we follow the final...
The single word they never spoke ran the engines dead

In this episode, we follow the final hours of Avianca Flight 052 as its crew faces creeping fuel starvation, repeated holding patterns, and communication barriers with New York controllers. The episode traces the technical, procedural, and human factors that left the system waiting for a single word-what happens when language is the last line of defense?

Date: January 25, 1990
Aircraft: Boeing 707
Flight: Avianca Flight 052
Location: Cove Neck, Long Island / near JFK Airport
Fatalities: 73

- The flight departed Medellín with block fuel requirements listed and an extra dispatch increment, but modifications and age had quietly increased fuel burn.
- The aircraft carried noise-reduction kits and accumulated over 61,000 flight hours, both factors adding roughly five percent each to fuel consumption.
- The autopilot’s altitude-hold had a known recurring fault; the captain prepared to hand-fly the approach in low visibility with fuel critically low.
- The crew endured three holding stacks-Norfolk, Atlantic City, and CAMRN-totaling ninety-three minutes of extra fuel burn on top of the planned margins.
- Cockpit voice recordings show the crew using trained phrases yet never uttering the specific seven-letter word required by controllers’ emergency protocol.

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.]]>1033falsefullhttps://www.spreaker.com/episode/the-man-who-measured-seven-cycles-lost-on-flight-191--73097001
Fear of sudden loss and the uncanny precision of a measured human frequency: Itzhak Bentov recorded "seven cycles per second" inside his own body and boarded American Airlines Flight 191 on May 25, 1979 - a flight that crashed seconds after takeoff, killing all 273 aboard. How did a Holocaust survivor, weapons engineer, and medical inventor end up with a basement lab, a Japanese audience waiting, and a measurement that still haunts the border between science and mysticism?

In this episode, we follow the documented life and work of Itzhak Bentov and the circumstances around Flight 191. The episode covers his measurement of seven cycles per second, his inventions and company, and the crash that ended his trip - leaving the central question: what did he mean to prove, and who was waiting to hear it?

Person: Itzhak Bentov
Date: May 25, 1979
Event: American Airlines Flight 191 crash
Location: O'Hare International Airport, Chicago departure
Number aboard: 273

- Bentov measured "seven cycles per second" inside his own body using electrodes connected to a function generator.
- American Airlines Flight 191 crashed seconds after takeoff from O'Hare on May 25, 1979, killing all 273 people aboard.
- Bentov was born August 9, 1923, in Humenné (then Czechoslovakia) and was 55 at the time of the crash.
- In 1969 Bentov co-founded Medi-Tech with John Abele; in 1979 Medi-Tech was acquired by the company that became Boston Scientific.
- Bentov built Israel's first rocket in his mid-twenties while working for HEMED during the 1948 period under an arms embargo.

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/73097001Sun, 06 Sep 2026 08:00:03 +0000Creator at ObomediaThe Man Who Measured Seven Cycles - Lost on Flight 191 Fear of sudden loss and the uncanny precision of a measured human frequency: Itzhak Bentov recorded "seven cycles per second" inside his own body and boarded American Airlines Flight 191 on May...
Fear of sudden loss and the uncanny precision of a measured human frequency: Itzhak Bentov recorded "seven cycles per second" inside his own body and boarded American Airlines Flight 191 on May 25, 1979 - a flight that crashed seconds after takeoff, killing all 273 aboard. How did a Holocaust survivor, weapons engineer, and medical inventor end up with a basement lab, a Japanese audience waiting, and a measurement that still haunts the border between science and mysticism?

In this episode, we follow the documented life and work of Itzhak Bentov and the circumstances around Flight 191. The episode covers his measurement of seven cycles per second, his inventions and company, and the crash that ended his trip - leaving the central question: what did he mean to prove, and who was waiting to hear it?

Person: Itzhak Bentov
Date: May 25, 1979
Event: American Airlines Flight 191 crash
Location: O'Hare International Airport, Chicago departure
Number aboard: 273

- Bentov measured "seven cycles per second" inside his own body using electrodes connected to a function generator.
- American Airlines Flight 191 crashed seconds after takeoff from O'Hare on May 25, 1979, killing all 273 people aboard.
- Bentov was born August 9, 1923, in Humenné (then Czechoslovakia) and was 55 at the time of the crash.
- In 1969 Bentov co-founded Medi-Tech with John Abele; in 1979 Medi-Tech was acquired by the company that became Boston Scientific.
- Bentov built Israel's first rocket in his mid-twenties while working for HEMED during the 1948 period under an arms embargo.

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.]]>975falsefullhttps://www.spreaker.com/episode/the-delayed-clearance-that-let-the-dc-9-meet-the-seawall--74743227
The delayed clearance that let the DC‑9 meet the seawall

In this episode, we follow the final minutes before a routine Boston approach turned catastrophic, tracing the sequence of decisions, instruments and absences that preceded impact. Why did a chain of small errors and a late clearance leave one passenger officially missing from the record?

Date: July 31, 1973
Flight: Delta Air Lines Flight Seven Twenty-Three
Aircraft: McDonnell Douglas DC‑9, N975NE
Person: Leopold Chouinard, age 20
Location: Logan International International, Boston

- The DC‑9 departed Burlington, stopped in Manchester, then flew the short final leg to Boston under instrument meteorological conditions.
- Captain John N. Streil, First Officer Sidney W. Burrill, and observer Joseph E. Burrell occupied the cockpit; all three pilots later died.
- The ILS approach to Runway 4R required strict adherence to localizer and glideslope guidance amid a 400‑foot ceiling and half‑mile visibility.
- A clearance reached the crew later than expected, creating a critical timing decision during the final approach.
- One survivor, Leopold Chouinard, lived 133 days after the crash but was excluded from the official toll by the seven‑day rule then in force.

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/74743227Sat, 05 Sep 2026 08:00:03 +0000Creator at ObomediaA DC‑9 on ILS into fog at Logan races a delayed clearance toward a seawall as instruments and cockpit silence conspire - did they make it in time? The delayed clearance that let the DC‑9 meet the seawall In this episode, we follow the final...
The delayed clearance that let the DC‑9 meet the seawall

In this episode, we follow the final minutes before a routine Boston approach turned catastrophic, tracing the sequence of decisions, instruments and absences that preceded impact. Why did a chain of small errors and a late clearance leave one passenger officially missing from the record?

Date: July 31, 1973
Flight: Delta Air Lines Flight Seven Twenty-Three
Aircraft: McDonnell Douglas DC‑9, N975NE
Person: Leopold Chouinard, age 20
Location: Logan International International, Boston

- The DC‑9 departed Burlington, stopped in Manchester, then flew the short final leg to Boston under instrument meteorological conditions.
- Captain John N. Streil, First Officer Sidney W. Burrill, and observer Joseph E. Burrell occupied the cockpit; all three pilots later died.
- The ILS approach to Runway 4R required strict adherence to localizer and glideslope guidance amid a 400‑foot ceiling and half‑mile visibility.
- A clearance reached the crew later than expected, creating a critical timing decision during the final approach.
- One survivor, Leopold Chouinard, lived 133 days after the crash but was excluded from the official toll by the seven‑day rule then in force.

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.]]>989falsefullhttps://www.spreaker.com/episode/when-safety-systems-slept-the-deadly-george-inlet-midair-collision--73096998
A pristine Alaskan sky hid three bent propeller blades and six dead after two sightseeing seaplanes collided above George Inlet on May 13, 2019 - and the collision happened while a critical safety device on one aircraft had been switched off for 14 days. How did cockpit geometry, converging speeds and a switched-off collision-avoidance system conspire to leave two experienced pilots blind to each other until it was too late?

In this episode, we tell the sequence of events leading up to the midair collision, outline the operational context of sightseeing flights out of Ketchikan, and follow the investigators as they uncover the administrative decisions and equipment status that removed layers of protection - so what exactly failed, and why did no one catch it beforehand?

Event: Midair collision above George Inlet
Date: May 13, 2019 at 12:21 PM
Persons: Randy Sullivan; Lou Beck
Aircraft: DHC-2 Beaver N952DB (Beaver) and DHC-3 Otter N959PA (Otter)
Fatalities: Six

- The Beaver was traveling at 107 knots at approximately 3,350 feet MSL heading west-southwest toward Ketchikan Harbor.
- The Otter was descending from 4,000 feet at 126 knots on a heading between 224° and 237°.
- A device on the Otter that would have watched for converging traffic had been switched off for 14 days prior to the accident.
- The Beaver's cockpit structure, right wing and a passenger in the right front seat blocked Sullivan's view of the Otter.
- The Otter's left front window post obscured the Beaver from Beck's view for 11 seconds before impact.

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/73096998Sat, 05 Sep 2026 08:00:02 +0000Creator at ObomediaWhen Safety Systems Slept: The Deadly George Inlet Midair Collision A pristine Alaskan sky hid three bent propeller blades and six dead after two sightseeing seaplanes collided above George Inlet on May 13, 2019 - and the collision happened while a...
A pristine Alaskan sky hid three bent propeller blades and six dead after two sightseeing seaplanes collided above George Inlet on May 13, 2019 - and the collision happened while a critical safety device on one aircraft had been switched off for 14 days. How did cockpit geometry, converging speeds and a switched-off collision-avoidance system conspire to leave two experienced pilots blind to each other until it was too late?

In this episode, we tell the sequence of events leading up to the midair collision, outline the operational context of sightseeing flights out of Ketchikan, and follow the investigators as they uncover the administrative decisions and equipment status that removed layers of protection - so what exactly failed, and why did no one catch it beforehand?

Event: Midair collision above George Inlet
Date: May 13, 2019 at 12:21 PM
Persons: Randy Sullivan; Lou Beck
Aircraft: DHC-2 Beaver N952DB (Beaver) and DHC-3 Otter N959PA (Otter)
Fatalities: Six

- The Beaver was traveling at 107 knots at approximately 3,350 feet MSL heading west-southwest toward Ketchikan Harbor.
- The Otter was descending from 4,000 feet at 126 knots on a heading between 224° and 237°.
- A device on the Otter that would have watched for converging traffic had been switched off for 14 days prior to the accident.
- The Beaver's cockpit structure, right wing and a passenger in the right front seat blocked Sullivan's view of the Otter.
- The Otter's left front window post obscured the Beaver from Beck's view for 11 seconds before impact.

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.]]>1071falsefullhttps://www.spreaker.com/episode/they-never-walked-away-the-big-bopper-s-final-100-feet--74743226
They Never Walked Away: The Big Bopper's Final 100 Feet

In this episode, we trace the last hours before the Beechcraft Bonanza left a Clear Lake runway and the few minutes that followed in an Iowa cornfield. The story follows Jiles Perry Richardson Jr.’s rise, the Winter Dance Party’s fraying tour, and the decisions that put four men on a tiny plane - what happened next?

Person: Jiles Perry Richardson Jr.
Event: Plane crash in a cornfield after takeoff from Mason City area runway
Date: February 3, 1959
Location: Clear Lake, Iowa / nearby cornfield
Topic: The Big Bopper’s final minutes and rumors about survival

- Richardson’s body was found about one hundred feet from the wreckage of the Beechcraft Bonanza.
- He was twenty-eight, with a pregnant wife and unfinished songs and demos at home.
- The Winter Dance Party tour had eleven grueling nights of frozen buses, missed meals, and exhaustion.
- Buddy Holly chartered a four-seat Beechcraft Bonanza from Dwyer Flying Service to avoid the bus.
- Persistent rumors claimed Richardson crawled away alive, prompting a later forensic exhumation decades after the crash.

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/74743226Fri, 04 Sep 2026 08:00:03 +0000Creator at ObomediaA grieving band faces a desperate flight from a freezing Iowa night when rock star The Big Bopper boards a small plane - did they make it in time? They Never Walked Away: The Big Bopper's Final 100 Feet In this episode, we trace the last hours...
They Never Walked Away: The Big Bopper's Final 100 Feet

In this episode, we trace the last hours before the Beechcraft Bonanza left a Clear Lake runway and the few minutes that followed in an Iowa cornfield. The story follows Jiles Perry Richardson Jr.’s rise, the Winter Dance Party’s fraying tour, and the decisions that put four men on a tiny plane - what happened next?

Person: Jiles Perry Richardson Jr.
Event: Plane crash in a cornfield after takeoff from Mason City area runway
Date: February 3, 1959
Location: Clear Lake, Iowa / nearby cornfield
Topic: The Big Bopper’s final minutes and rumors about survival

- Richardson’s body was found about one hundred feet from the wreckage of the Beechcraft Bonanza.
- He was twenty-eight, with a pregnant wife and unfinished songs and demos at home.
- The Winter Dance Party tour had eleven grueling nights of frozen buses, missed meals, and exhaustion.
- Buddy Holly chartered a four-seat Beechcraft Bonanza from Dwyer Flying Service to avoid the bus.
- Persistent rumors claimed Richardson crawled away alive, prompting a later forensic exhumation decades after the crash.

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/a-mountain-that-wasn-t-on-the-map-the-crash-of-siv--73096996
Two hundred and fifty feet separated the last radar return from the summit of Sweden's highest mountain - roughly the height of a twenty-story building - and the Norwegian C-130J named Siv flew straight into it as if the peak simply did not exist. How could five highly experienced aircrew on a routine fifty-minute transit, flying straight and level with no alarms, descend into Kebnekaise when every system that should have warned them stayed silent?

In this episode, we follow the flight of Siv on March 15, 2012, its planned route from Evenes to Kiruna during the Cold Response exercise, and the sequence of clearances, radar returns, and system behavior that preceded the crash. What combination of charting, clearances, and system configuration left a mountain virtually absent from the crew's situational picture?

Date: March 15, 2012
Aircraft: C-130J Super Hercules serial number 5630
Crew: Five Royal Norwegian Air Force officers (Captain Ståle Garberg, First Officer Truls Audun Ørpen, plus three others)
Location: Kebnekaise, Lapporten corridor, northern Sweden
Final radar: Civil radar at Kiruna recorded final return at 14:56 with altitude 7,200 ft; military radar at Sørreisa logged ~7,600 ft

- Last radar return was 250 feet from the summit of Kebnekaise (6,950 ft above sea level).
- Clearance to descend to 7,000 ft was issued during the approach to Kiruna.
- Captain Ståle Garberg had 6,229 flight hours; First Officer Truls Audun Ørpen had 3,286 hours.
- The flight departed Evenes Airport at 13:40 bound for Kiruna with a planned duration of 50 minutes.
- Siv's Terrain Awareness and Warning System (TAWS) was installed and functioning as configured, yet produced no warning.

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/73096996Fri, 04 Sep 2026 08:00:03 +0000Creator at ObomediaA Mountain That Wasn't on the Map: The Crash of Siv Two hundred and fifty feet separated the last radar return from the summit of Sweden's highest mountain - roughly the height of a twenty-story building - and the Norwegian C-130J named Siv flew...
Two hundred and fifty feet separated the last radar return from the summit of Sweden's highest mountain - roughly the height of a twenty-story building - and the Norwegian C-130J named Siv flew straight into it as if the peak simply did not exist. How could five highly experienced aircrew on a routine fifty-minute transit, flying straight and level with no alarms, descend into Kebnekaise when every system that should have warned them stayed silent?

In this episode, we follow the flight of Siv on March 15, 2012, its planned route from Evenes to Kiruna during the Cold Response exercise, and the sequence of clearances, radar returns, and system behavior that preceded the crash. What combination of charting, clearances, and system configuration left a mountain virtually absent from the crew's situational picture?

Date: March 15, 2012
Aircraft: C-130J Super Hercules serial number 5630
Crew: Five Royal Norwegian Air Force officers (Captain Ståle Garberg, First Officer Truls Audun Ørpen, plus three others)
Location: Kebnekaise, Lapporten corridor, northern Sweden
Final radar: Civil radar at Kiruna recorded final return at 14:56 with altitude 7,200 ft; military radar at Sørreisa logged ~7,600 ft

- Last radar return was 250 feet from the summit of Kebnekaise (6,950 ft above sea level).
- Clearance to descend to 7,000 ft was issued during the approach to Kiruna.
- Captain Ståle Garberg had 6,229 flight hours; First Officer Truls Audun Ørpen had 3,286 hours.
- The flight departed Evenes Airport at 13:40 bound for Kiruna with a planned duration of 50 minutes.
- Siv's Terrain Awareness and Warning System (TAWS) was installed and functioning as configured, yet produced no warning.

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.]]>1135falsefullhttps://www.spreaker.com/episode/the-phone-calls-that-bought-eight-minutes-did-anyone-reach-safety--74743225
The Phone Calls That Bought Eight Minutes - Did Anyone Reach Safety?

In this episode, we follow United Airlines Flight 175 from takeoff to impact, focusing on the last minutes inside the cabin and the phone calls that became key evidence. We trace who was aboard, how the hijackers moved through the plane, and the decisions made as passengers tried to warn the outside world-what did those calls change?

Date: September 11, 2001
Flight: United Airlines Flight 175
Aircraft: Boeing 767-200, registration N612UA
People on board: 60
Survivors above impact: 18

- Captain Victor Saracini and First Officer Michael Horrocks, both former military pilots, were in the cockpit when the hijacking occurred.
- Five men moved through the sparsely filled cabin aided by empty rows and passenger relocations before forcing passengers to gather.
- Peter Hanson shifted seats before boarding and used a rear phone to call his father twice in the final eight minutes.
- Flight recorders were never recovered; reconstructions rely on radar, transponder data, and calls made from the aircraft.
- Flight 175 struck the South Tower 49 minutes after takeoff, and 56 minutes passed between impact and the tower’s collapse.

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/74743225Thu, 03 Sep 2026 08:00:03 +0000Creator at ObomediaA Boeing 767 is hijacked en route to California; frantic phone calls buy eight minutes as passengers try to reach safety-did anyone make it out? The Phone Calls That Bought Eight Minutes - Did Anyone Reach Safety? In this episode, we follow...
The Phone Calls That Bought Eight Minutes - Did Anyone Reach Safety?

In this episode, we follow United Airlines Flight 175 from takeoff to impact, focusing on the last minutes inside the cabin and the phone calls that became key evidence. We trace who was aboard, how the hijackers moved through the plane, and the decisions made as passengers tried to warn the outside world-what did those calls change?

Date: September 11, 2001
Flight: United Airlines Flight 175
Aircraft: Boeing 767-200, registration N612UA
People on board: 60
Survivors above impact: 18

- Captain Victor Saracini and First Officer Michael Horrocks, both former military pilots, were in the cockpit when the hijacking occurred.
- Five men moved through the sparsely filled cabin aided by empty rows and passenger relocations before forcing passengers to gather.
- Peter Hanson shifted seats before boarding and used a rear phone to call his father twice in the final eight minutes.
- Flight recorders were never recovered; reconstructions rely on radar, transponder data, and calls made from the aircraft.
- Flight 175 struck the South Tower 49 minutes after takeoff, and 56 minutes passed between impact and the tower’s collapse.

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.]]>1038falsefullhttps://www.spreaker.com/episode/thirty-five-thousand-feet-of-silence-the-rudder-that-took-flight--73096994
A terrifying uncommanded roll at 35,000 feet left a 747 heeling 30-40 degrees with no crew input, caused by a hidden metal fatigue crack in the lower rudder power control module; how did four pilots with no procedure invent a fix while the Bering Sea waited below? What choices did they make when no checklist, radio contact, or manual could save them?

In this episode, we follow Northwest Airlines Flight 85 from routine long-haul rotation to an unprecedented flight control fracture, and we hear how the crew confronted an unknown failure and navigational isolation while trying to keep the aircraft stable. Could improvised procedures and human judgment be enough when the manuals fail?

Aircraft: N661US (original 747-400 prototype)
Event: Uncommanded 30-40° left roll
Date: October 9, 2002
Route: Detroit Metropolitan Airport to Tokyo Narita (over Bering Sea)
Crew: Four pilots (Senior Captain John Hanson, First Officer Mike Fagan, Junior Captain Frank Geib, First Officer David Smith)

- The aircraft first flew as N401PW in April 1988 and was delivered to Northwest on December 8, 1989.
- By October 9, 2002 the airframe had 13 years of pressurization cycles and oceanic crossings.
- At approximately 5:40 PM Alaska Daylight Time, the aircraft rolled 30-40 degrees left with no control input.
- The end section of the lower rudder power control module housing fractured, allowing the actuator to drive the lower rudder to full left hardover.
- Flight crew transmissions received no reply because the airplane was in a Bering Sea communications dead zone.

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/73096994Thu, 03 Sep 2026 08:00:02 +0000Creator at ObomediaThirty-Five Thousand Feet of Silence: The Rudder That Took Flight A terrifying uncommanded roll at 35,000 feet left a 747 heeling 30-40 degrees with no crew input, caused by a hidden metal fatigue crack in the lower rudder power control module; how...
A terrifying uncommanded roll at 35,000 feet left a 747 heeling 30-40 degrees with no crew input, caused by a hidden metal fatigue crack in the lower rudder power control module; how did four pilots with no procedure invent a fix while the Bering Sea waited below? What choices did they make when no checklist, radio contact, or manual could save them?

In this episode, we follow Northwest Airlines Flight 85 from routine long-haul rotation to an unprecedented flight control fracture, and we hear how the crew confronted an unknown failure and navigational isolation while trying to keep the aircraft stable. Could improvised procedures and human judgment be enough when the manuals fail?

Aircraft: N661US (original 747-400 prototype)
Event: Uncommanded 30-40° left roll
Date: October 9, 2002
Route: Detroit Metropolitan Airport to Tokyo Narita (over Bering Sea)
Crew: Four pilots (Senior Captain John Hanson, First Officer Mike Fagan, Junior Captain Frank Geib, First Officer David Smith)

- The aircraft first flew as N401PW in April 1988 and was delivered to Northwest on December 8, 1989.
- By October 9, 2002 the airframe had 13 years of pressurization cycles and oceanic crossings.
- At approximately 5:40 PM Alaska Daylight Time, the aircraft rolled 30-40 degrees left with no control input.
- The end section of the lower rudder power control module housing fractured, allowing the actuator to drive the lower rudder to full left hardover.
- Flight crew transmissions received no reply because the airplane was in a Bering Sea communications dead zone.

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.]]>1066falsefullhttps://www.spreaker.com/episode/the-0-05-mhz-readback-that-silenced-the-piper-did-they-make-it--74743224
The 0.05 MHz readback that silenced the Piper - did they make it?

In this episode, we follow the minutes before two aircraft converged over the Hudson River on August 8, 2009, tracing radio handoffs, radar alerts, and the small decisions that set events in motion. The narrative asks how a five-hundredths-of-a-megahertz error and a missed radio call left a corridor designed for visual flight with no one listening.

Date: August 8, 2009
Location: Hudson River corridor / Teterboro and Manhattan airspace
Aircraft: Piper PA-32R-300 Cherokee Lance; Eurocopter AS350
Person: Steven Altman
Report: NTSB final report released September 14, 2010

- Teterboro cleared Steven Altman for departure and gave a handoff frequency to Newark Liberty: 127.85 MHz; Altman read back 127.8 MHz.
- The 0.05 MHz misread put Altman on a dead channel where Newark and Teterboro could not reach him by voice.
- The Teterboro controller was recorded on a personal phone call at the moment of the frequency exchange and did not catch the readback error.
- Newark controllers saw the Piper's transponder on radar moving toward the Hudson and attempted to contact Teterboro to reestablish radio communication.
- A pilot on the ground observed the convergence, called out on the radio, and received no response as an automated conflict alert appeared on radar screens.

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/74743224Wed, 02 Sep 2026 08:00:03 +0000Creator at ObomediaA pilot misreads a handoff and vanishes from the only voice channel over the Hudson River as another helicopter approaches - did they make it in time? The 0.05 MHz readback that silenced the Piper - did they make it? In this episode, we follow...
The 0.05 MHz readback that silenced the Piper - did they make it?

In this episode, we follow the minutes before two aircraft converged over the Hudson River on August 8, 2009, tracing radio handoffs, radar alerts, and the small decisions that set events in motion. The narrative asks how a five-hundredths-of-a-megahertz error and a missed radio call left a corridor designed for visual flight with no one listening.

Date: August 8, 2009
Location: Hudson River corridor / Teterboro and Manhattan airspace
Aircraft: Piper PA-32R-300 Cherokee Lance; Eurocopter AS350
Person: Steven Altman
Report: NTSB final report released September 14, 2010

- Teterboro cleared Steven Altman for departure and gave a handoff frequency to Newark Liberty: 127.85 MHz; Altman read back 127.8 MHz.
- The 0.05 MHz misread put Altman on a dead channel where Newark and Teterboro could not reach him by voice.
- The Teterboro controller was recorded on a personal phone call at the moment of the frequency exchange and did not catch the readback error.
- Newark controllers saw the Piper's transponder on radar moving toward the Hudson and attempted to contact Teterboro to reestablish radio communication.
- A pilot on the ground observed the convergence, called out on the radio, and received no response as an automated conflict alert appeared on radar screens.

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.]]>896falsefullhttps://www.spreaker.com/episode/sixteen-seconds-to-nightfall-the-sosoliso-flight-1145-tragedy--73096993
A contained dread: a documented concrete culvert sat 70 meters left of Runway 21 and a DC-9 traveling 160 knots struck it on 10 December 2005 - 108 of 110 aboard died. How did visible hazards, unreported weather and a crew choice converge in sixteen seconds to produce one of Nigeria's deadliest crashes?

In this episode, we present the sequence of events, the aircraft and crew details, and the operational failures that preceded impact, closing on the decision altitude breach that turned a routine approach into catastrophe. What chain of known problems left so little time to survive?

Date: 10 December 2005
Aircraft: McDonnell Douglas DC-9-32
Location: Port Harcourt International Airport
Fatalities: 108 of 110 onboard
Approach runway: Runway 21

- The concrete culvert was located approximately 70 meters left of Runway 21 and was shown on airport maps.
- The aircraft was traveling at 160 knots when it struck terrain.
- Fifty-nine of the sixty Loyola Jesuit College students on board were returning home for Christmas.
- The DC-9 was built in 1972, registered in Nigeria in June 2003, with a valid airworthiness certificate issued March 2005.
- The decision altitude for the Runway 21 approach was 307 feet above ground; the captain descended below it without a visual runway reference.

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/73096993Wed, 02 Sep 2026 08:00:02 +0000Creator at ObomediaSixteen Seconds to Nightfall: The Sosoliso Flight 1145 Tragedy A contained dread: a documented concrete culvert sat 70 meters left of Runway 21 and a DC-9 traveling 160 knots struck it on 10 December 2005 - 108 of 110 aboard died. How did visible...
A contained dread: a documented concrete culvert sat 70 meters left of Runway 21 and a DC-9 traveling 160 knots struck it on 10 December 2005 - 108 of 110 aboard died. How did visible hazards, unreported weather and a crew choice converge in sixteen seconds to produce one of Nigeria's deadliest crashes?

In this episode, we present the sequence of events, the aircraft and crew details, and the operational failures that preceded impact, closing on the decision altitude breach that turned a routine approach into catastrophe. What chain of known problems left so little time to survive?

Date: 10 December 2005
Aircraft: McDonnell Douglas DC-9-32
Location: Port Harcourt International Airport
Fatalities: 108 of 110 onboard
Approach runway: Runway 21

- The concrete culvert was located approximately 70 meters left of Runway 21 and was shown on airport maps.
- The aircraft was traveling at 160 knots when it struck terrain.
- Fifty-nine of the sixty Loyola Jesuit College students on board were returning home for Christmas.
- The DC-9 was built in 1972, registered in Nigeria in June 2003, with a valid airworthiness certificate issued March 2005.
- The decision altitude for the Runway 21 approach was 307 feet above ground; the captain descended below it without a visual runway reference.

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.]]>1094falsefullhttps://www.spreaker.com/episode/the-yellow-rotor-blade-flew-four-hundred-meters-could-they-stop-the-crash--74743223
The yellow rotor blade flew four hundred meters - could they stop the crash?

In this episode, we follow the minutes before and after Los Angeles Airways Flight 417 came apart over a Compton neighborhood on August 14, 1968. We lay out the aircraft, the crew, and the mechanical clue that baffled inspectors - could routine checks have missed a lethal crack?

Person: Captain Kenneth Lee Waggoner
Event: Los Angeles Airways Flight 417 breakup
Date: August 14, 1968
Location: Lueders Park, Compton / Rosecrans Avenue
Aircraft: Sikorsky S-61L, N300Y (prototype)

- The prototype S-61L, N300Y, had logged 11,863.64 flight hours and already flown three round trips that morning.
- Flight 417 departed LAX at 10:26 AM with 21 aboard and normal weight, fuel (1,000 lb JP‑4) and center-of-gravity within limits.
- Ninety-one ground witnesses described hearing a wrong sound, seeing a separate object in the air, then watching the helicopter destabilize and rotate.
- One yellow rotor blade landed 400 meters away, a scatter distance investigators treated as a crucial physical clue rather than random debris.
- The destroyed component showed a long-growing crack that had passed inspection, prompting a post-crash FAA emergency airworthiness directive two days later.

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/74743223Tue, 01 Sep 2026 08:00:04 +0000Creator at ObomediaA yellow rotor blade flew 400 meters from the wreckage as a prototype Sikorsky S-61L broke apart over Compton - could they stop the crash? The yellow rotor blade flew four hundred meters - could they stop the crash? In this episode, we follow...
The yellow rotor blade flew four hundred meters - could they stop the crash?

In this episode, we follow the minutes before and after Los Angeles Airways Flight 417 came apart over a Compton neighborhood on August 14, 1968. We lay out the aircraft, the crew, and the mechanical clue that baffled inspectors - could routine checks have missed a lethal crack?

Person: Captain Kenneth Lee Waggoner
Event: Los Angeles Airways Flight 417 breakup
Date: August 14, 1968
Location: Lueders Park, Compton / Rosecrans Avenue
Aircraft: Sikorsky S-61L, N300Y (prototype)

- The prototype S-61L, N300Y, had logged 11,863.64 flight hours and already flown three round trips that morning.
- Flight 417 departed LAX at 10:26 AM with 21 aboard and normal weight, fuel (1,000 lb JP‑4) and center-of-gravity within limits.
- Ninety-one ground witnesses described hearing a wrong sound, seeing a separate object in the air, then watching the helicopter destabilize and rotate.
- One yellow rotor blade landed 400 meters away, a scatter distance investigators treated as a crucial physical clue rather than random debris.
- The destroyed component showed a long-growing crack that had passed inspection, prompting a post-crash FAA emergency airworthiness directive two days later.

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.]]>975falsefullhttps://www.spreaker.com/episode/a-brand-new-airplane-two-experienced-pilots-thirty-seconds-and-sixty-eight-people-were-gone--73096991
Cold, fast, and almost bureaucratic: investigators found sixty-eight people reduced to a compressed layer pressed into frozen soil after an ATR-72 struck the ground nose-down at 375 knots and 38 degrees - an impact described as an erasure. Why did routine procedures and a brand-new aircraft fail to stop a catastrophe that unfolded in just twenty-two minutes and thirty seconds?

In this episode, we follow the timeline from Indianapolis departure to the moment of impact and outline the gaps in the information flow, cockpit actions, and systems that precede the accident. What missing report, procedural silence, or system behavior allowed ice and confusion to combine into disaster?

Flight: American Eagle 51260
Date: October 31, 1994
Aircraft: ATR-72
Impact speed: 375 knots
Impact angle: 38 degrees nose down

- Departure-to-impact elapsed time: 22 minutes from Indianapolis to crash site.
- Captain absence from cockpit: 4 minutes 29 seconds, confirmed by cockpit voice recorder.
- Aircraft delivery to airline: 7 months earlier, on March 7, 1994.
- Holding clearance altitude reported for nearby Beech Baron: 4,000 feet over Roselawn VOR at 15 minutes before accident.
- Number of occupants reduced to compressed residue: 68 people.

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/73096991Tue, 01 Sep 2026 08:00:02 +0000Creator at ObomediaA brand-new airplane, two experienced pilots, thirty seconds - and sixty-eight people were gone Cold, fast, and almost bureaucratic: investigators found sixty-eight people reduced to a compressed layer pressed into frozen soil after an ATR-72...
Cold, fast, and almost bureaucratic: investigators found sixty-eight people reduced to a compressed layer pressed into frozen soil after an ATR-72 struck the ground nose-down at 375 knots and 38 degrees - an impact described as an erasure. Why did routine procedures and a brand-new aircraft fail to stop a catastrophe that unfolded in just twenty-two minutes and thirty seconds?

In this episode, we follow the timeline from Indianapolis departure to the moment of impact and outline the gaps in the information flow, cockpit actions, and systems that precede the accident. What missing report, procedural silence, or system behavior allowed ice and confusion to combine into disaster?

Flight: American Eagle 51260
Date: October 31, 1994
Aircraft: ATR-72
Impact speed: 375 knots
Impact angle: 38 degrees nose down

- Departure-to-impact elapsed time: 22 minutes from Indianapolis to crash site.
- Captain absence from cockpit: 4 minutes 29 seconds, confirmed by cockpit voice recorder.
- Aircraft delivery to airline: 7 months earlier, on March 7, 1994.
- Holding clearance altitude reported for nearby Beech Baron: 4,000 feet over Roselawn VOR at 15 minutes before accident.
- Number of occupants reduced to compressed residue: 68 people.

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.]]>1016falsefullhttps://www.spreaker.com/episode/the-darkened-navigational-beacons-hid-the-mountains-and-cost-them-their-lives--74743222
The darkened navigational beacons hid the mountains and cost them their lives

In this episode, we follow the final hours before a scheduled flight from Las Vegas to Los Angeles when safety measures left the crew without beacon guidance. The story traces decisions, personal histories, and the concrete choices that put twenty-two people aboard TWA Flight 3 on a collision course with the Spring Mountains - but did they have any warning?

Person: Carole Lombard
Date: January 16, 1942
Event: TWA Flight 3 struck Double Up Peak on Potosi Mountain
Location: Las Vegas to Los Angeles route, Spring Mountains / Potosi Mountain
Status: Navigational beacons switched off as a wartime precaution

- Flight departed Las Vegas at 7:07 PM, thirty-three minutes before impact.
- Navigational beacons had been switched off to prevent enemy bombers from using them.
- The aircraft struck Double Up Peak at approximately 8,300 feet.
- Carole Lombard had flown after raising two million dollars in war bonds the previous evening.
- The passenger manifest included fifteen U.S. Army soldiers who boarded in Las Vegas.

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/74743222Mon, 31 Aug 2026 08:00:03 +0000Creator at ObomediaCarole Lombard boards a night flight from Las Vegas with navigational beacons switched off; the mountains ahead are invisible and time is running out. The darkened navigational beacons hid the mountains and cost them their lives In this episode,...
The darkened navigational beacons hid the mountains and cost them their lives

In this episode, we follow the final hours before a scheduled flight from Las Vegas to Los Angeles when safety measures left the crew without beacon guidance. The story traces decisions, personal histories, and the concrete choices that put twenty-two people aboard TWA Flight 3 on a collision course with the Spring Mountains - but did they have any warning?

Person: Carole Lombard
Date: January 16, 1942
Event: TWA Flight 3 struck Double Up Peak on Potosi Mountain
Location: Las Vegas to Los Angeles route, Spring Mountains / Potosi Mountain
Status: Navigational beacons switched off as a wartime precaution

- Flight departed Las Vegas at 7:07 PM, thirty-three minutes before impact.
- Navigational beacons had been switched off to prevent enemy bombers from using them.
- The aircraft struck Double Up Peak at approximately 8,300 feet.
- Carole Lombard had flown after raising two million dollars in war bonds the previous evening.
- The passenger manifest included fifteen U.S. Army soldiers who boarded in Las Vegas.

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.]]>910falsefullhttps://www.spreaker.com/episode/glider-over-georgia-when-both-engines-failed-midflight--73096989
Danger and disbelief: at 15:17 on April 4, 1977, a DC-9 with 85 people aboard became a powerless glider after both engines failed from extreme water and hail - the first documented simultaneous dual-engine loss in commercial aviation history. How did routine decisions and a radar gap turn a familiar regional hop into Georgia’s worst aviation disaster, and who survived against the odds?

In this episode, we tell what happened in the 47 minutes between takeoff and impact, how the crew’s expectations clashed with a reorganized squall line, and why the official investigation found no single cause that fully explains the wreckage. Could ordinary procedures and one missed weather update together produce a catastrophe?

Event: Southern Airways Flight 242
Date: April 4, 1977
Location: New Hope, Paulding County, Georgia
Aircraft: DC-9-31, registration N1335U
Fatalities: 72 (total), 24 survived

- Time of landing on the highway: 15:17 (17 minutes past three in the afternoon)
- Passengers aboard: 81 passengers plus crew, total 85 people on board
- Captain William W. McKenzie flight hours: 19,380 total, 3,205 on DC-9
- First Officer Lyman W. Keele Jr. flight hours: 3,878 total, 235 on DC-9
- Engines failed after ingestion of extreme concentration of water and hail into JT8D engines

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/73096989Mon, 31 Aug 2026 08:00:03 +0000Creator at ObomediaGlider Over Georgia: When Both Engines Failed Midflight Danger and disbelief: at 15:17 on April 4, 1977, a DC-9 with 85 people aboard became a powerless glider after both engines failed from extreme water and hail - the first documented...
Danger and disbelief: at 15:17 on April 4, 1977, a DC-9 with 85 people aboard became a powerless glider after both engines failed from extreme water and hail - the first documented simultaneous dual-engine loss in commercial aviation history. How did routine decisions and a radar gap turn a familiar regional hop into Georgia’s worst aviation disaster, and who survived against the odds?

In this episode, we tell what happened in the 47 minutes between takeoff and impact, how the crew’s expectations clashed with a reorganized squall line, and why the official investigation found no single cause that fully explains the wreckage. Could ordinary procedures and one missed weather update together produce a catastrophe?

Event: Southern Airways Flight 242
Date: April 4, 1977
Location: New Hope, Paulding County, Georgia
Aircraft: DC-9-31, registration N1335U
Fatalities: 72 (total), 24 survived

- Time of landing on the highway: 15:17 (17 minutes past three in the afternoon)
- Passengers aboard: 81 passengers plus crew, total 85 people on board
- Captain William W. McKenzie flight hours: 19,380 total, 3,205 on DC-9
- First Officer Lyman W. Keele Jr. flight hours: 3,878 total, 235 on DC-9
- Engines failed after ingestion of extreme concentration of water and hail into JT8D engines

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.]]>1090falsefullhttps://www.spreaker.com/episode/the-epr-reading-that-fooled-the-autothrottle-did-they-land-in-time--74743221
The EPR reading that fooled the autothrottle - did they land in time?

In this episode, we follow the final thirty-two minutes of Air Algérie Flight AH5017, piecing together flight-data traces, maintenance logs, and crew records to show the chain of events that unfolded over the Sahara. What decisions, warnings, and system failures shaped those last minutes, and could the crew have known what was happening soon enough?

Date: 24 July 2014
Flight: AH5017
Aircraft: McDonnell Douglas MD-80, registration EC-LTV
Crew: Captain Agustín Comerón Mogio (47), First Officer Isabel Gost Caimari (42)
Passengers: 116 aboard (including French military personnel)

- Departed Ouagadougou at 01:15 local time en route to Algiers, scheduled arrival 05:10.
- Flight data recorder stopped transmitting at 01:47; the final 32 minutes became the focus of reconstruction.
- Maintenance history shows four interventions on EPR/autothrottle systems within 13 months, plus an engine replacement after a June rejected takeoff.
- The cockpit voice recorder’s magnetic tracks were unreadable, leaving crew dialogue and warnings undocumented.
- The autothrottle relied on EPR transmitters that had been replaced or repaired multiple times before this night 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/74743221Sun, 30 Aug 2026 08:00:03 +0000Creator at ObomediaA night flight over the Sahara loses its autothrottle signals and the cockpit falls silent - did they land in time? The EPR reading that fooled the autothrottle - did they land in time? In this episode, we follow the final thirty-two minutes of...
The EPR reading that fooled the autothrottle - did they land in time?

In this episode, we follow the final thirty-two minutes of Air Algérie Flight AH5017, piecing together flight-data traces, maintenance logs, and crew records to show the chain of events that unfolded over the Sahara. What decisions, warnings, and system failures shaped those last minutes, and could the crew have known what was happening soon enough?

Date: 24 July 2014
Flight: AH5017
Aircraft: McDonnell Douglas MD-80, registration EC-LTV
Crew: Captain Agustín Comerón Mogio (47), First Officer Isabel Gost Caimari (42)
Passengers: 116 aboard (including French military personnel)

- Departed Ouagadougou at 01:15 local time en route to Algiers, scheduled arrival 05:10.
- Flight data recorder stopped transmitting at 01:47; the final 32 minutes became the focus of reconstruction.
- Maintenance history shows four interventions on EPR/autothrottle systems within 13 months, plus an engine replacement after a June rejected takeoff.
- The cockpit voice recorder’s magnetic tracks were unreadable, leaving crew dialogue and warnings undocumented.
- The autothrottle relied on EPR transmitters that had been replaced or repaired multiple times before this night 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.]]>967falsefullhttps://www.spreaker.com/episode/mph-over-the-highway-how-flight-331-skidded-past-disaster--73096987
A fully loaded Boeing 737 crossed a public highway at 72 miles per hour and stopped meters from Kingston Harbor with 154 people on board - and no fatalities. How did a touchdown 4,100 feet down an 8,910-foot runway, a 16 mph tailwind, and a known regulatory gap almost become a catastrophe?

In this episode, we tell the sequence of events aboard American Airlines Flight 331 and the institutional context that allowed them to converge, from crew experience to airport conditions and prior safety recommendations. What did investigators already know, and why had the critical recommendation not been made mandatory?

Event: American Airlines Flight 331
Date: December 22, 2009
Aircraft: Boeing 737
Passengers and crew: 154 on board
Injuries: 85 injured

- Touchdown occurred at 22:22 local time on December 22, 2009.
- Main landing gear touched down 4,100 feet from the threshold of an 8,910-foot Runway 12.
- A 16 mph tailwind was present, one mile per hour inside the aircraft's published tailwind landing limit of 17 mph.
- Approach lighting system at Norman Manley International was not functioning before departure; runway lights were functioning.
- The National Transportation Safety Board had issued a recommendation about this regulatory gap years before the accident.

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/73096987Sun, 30 Aug 2026 08:00:02 +0000Creator at ObomediaMPH Over the Highway: How Flight 331 Skidded Past Disaster A fully loaded Boeing 737 crossed a public highway at 72 miles per hour and stopped meters from Kingston Harbor with 154 people on board - and no fatalities. How did a touchdown 4,100 feet...
A fully loaded Boeing 737 crossed a public highway at 72 miles per hour and stopped meters from Kingston Harbor with 154 people on board - and no fatalities. How did a touchdown 4,100 feet down an 8,910-foot runway, a 16 mph tailwind, and a known regulatory gap almost become a catastrophe?

In this episode, we tell the sequence of events aboard American Airlines Flight 331 and the institutional context that allowed them to converge, from crew experience to airport conditions and prior safety recommendations. What did investigators already know, and why had the critical recommendation not been made mandatory?

Event: American Airlines Flight 331
Date: December 22, 2009
Aircraft: Boeing 737
Passengers and crew: 154 on board
Injuries: 85 injured

- Touchdown occurred at 22:22 local time on December 22, 2009.
- Main landing gear touched down 4,100 feet from the threshold of an 8,910-foot Runway 12.
- A 16 mph tailwind was present, one mile per hour inside the aircraft's published tailwind landing limit of 17 mph.
- Approach lighting system at Norman Manley International was not functioning before departure; runway lights were functioning.
- The National Transportation Safety Board had issued a recommendation about this regulatory gap years before the accident.

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.]]>1002falsefullhttps://www.spreaker.com/episode/the-chart-that-showed-forty-five-feet-forced-the-plane-to-hit-the-wires--74743219
The chart that showed forty‑five feet forced the plane to hit the wires

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74743219Sat, 29 Aug 2026 08:00:03 +0000Creator at ObomediaA decorated KLM captain lines up a visual approach to Prestwick with charts showing 45 feet obstruction - did he make it in time? The chart that showed forty‑five feet forced the plane to hit the wires In this episode, we follow the Nijmegen's...
The chart that showed forty‑five feet forced the plane to hit the wires

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>832falsefullhttps://www.spreaker.com/episode/the-silent-gauge-why-flight-389-vanished-into-lake-michigan--73096985
A new Boeing 727 with a spotless maintenance record and three experienced pilots descended from 35,000 feet and struck Lake Michigan at roughly 200 knots - with no distress call and a final cockpit transmission of a single word: "Roger." How could a perfectly functioning jet and seasoned crew believe they were still safely in the sky until impact?

In this episode, we recount the timeline, the crew credentials, and the physical evidence recovered from the wreckage to explore the one subtle instrument failure investigators found that could explain the crew's fatal misperception. What hidden instrument on the panel had already failed them before anyone on the ground realized something was wrong?

Date: August 16, 1965
Event: Controlled flight into water
Aircraft: Boeing 727-022, N7036U
Fatalities: 30
Last transmission: "Roger"

- Time of sighting by lifeguard Wallace Whigam: 9:21 PM
- Estimated source distance from shore based on sound delay: ~3,375 feet offshore
- Aircraft descent: uninterrupted from 35,000 feet to impact
- Impact speed: approximately 200 knots
- Flight age at accident: in service 74 days, 138 flight cycles

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/73096985Sat, 29 Aug 2026 08:00:02 +0000Creator at ObomediaThe Silent Gauge: Why Flight 389 Vanished Into Lake Michigan A new Boeing 727 with a spotless maintenance record and three experienced pilots descended from 35,000 feet and struck Lake Michigan at roughly 200 knots - with no distress call and a...
A new Boeing 727 with a spotless maintenance record and three experienced pilots descended from 35,000 feet and struck Lake Michigan at roughly 200 knots - with no distress call and a final cockpit transmission of a single word: "Roger." How could a perfectly functioning jet and seasoned crew believe they were still safely in the sky until impact?

In this episode, we recount the timeline, the crew credentials, and the physical evidence recovered from the wreckage to explore the one subtle instrument failure investigators found that could explain the crew's fatal misperception. What hidden instrument on the panel had already failed them before anyone on the ground realized something was wrong?

Date: August 16, 1965
Event: Controlled flight into water
Aircraft: Boeing 727-022, N7036U
Fatalities: 30
Last transmission: "Roger"

- Time of sighting by lifeguard Wallace Whigam: 9:21 PM
- Estimated source distance from shore based on sound delay: ~3,375 feet offshore
- Aircraft descent: uninterrupted from 35,000 feet to impact
- Impact speed: approximately 200 knots
- Flight age at accident: in service 74 days, 138 flight cycles

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.]]>1037falsefullhttps://www.spreaker.com/episode/the-radar-scale-maxed-out-and-they-had-five-minutes-to-live--74743218
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/74743218Sat, 29 Aug 2026 05:59:01 +0000Creator at ObomediaA 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--74743217
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/74743217Sat, 29 Aug 2026 05:58:56 +0000Creator at ObomediaA 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--74743216
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/74743216Sat, 29 Aug 2026 05:58:52 +0000Creator at ObomediaA 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--74743215
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/74743215Sat, 29 Aug 2026 05:58:48 +0000Creator at ObomediaA 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--74743214
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/74743214Sat, 29 Aug 2026 05:58:44 +0000Creator at ObomediaA 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--74743213
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/74743213Sat, 29 Aug 2026 05:58:41 +0000Creator at ObomediaA 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--74743212
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/74743212Sat, 29 Aug 2026 05:58:36 +0000Creator at ObomediaA 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--74743211
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/74743211Sat, 29 Aug 2026 05:58:32 +0000Creator at ObomediaA 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--74743210
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/74743210Sat, 29 Aug 2026 05:58:29 +0000Creator at ObomediaA 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--74743209
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/74743209Sat, 29 Aug 2026 05:58:25 +0000Creator at ObomediaA 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--74743208
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/74743208Sat, 29 Aug 2026 05:58:20 +0000Creator at ObomediaA 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--74743207
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/74743207Sat, 29 Aug 2026 05:58:16 +0000Creator at ObomediaA 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--74743205
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/74743205Sat, 29 Aug 2026 05:58:12 +0000Creator at ObomediaA 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--74743204
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/74743204Sat, 29 Aug 2026 05:58:08 +0000Creator at ObomediaA 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--74743203
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/74743203Sat, 29 Aug 2026 05:58:04 +0000Creator at ObomediaA 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--74743202
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/74743202Sat, 29 Aug 2026 05:58:01 +0000Creator at ObomediaAn 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--74743201
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/74743201Sat, 29 Aug 2026 05:57:57 +0000Creator at ObomediaA 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--74743199
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/74743199Sat, 29 Aug 2026 05:57:52 +0000Creator at ObomediaA 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--74743198
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/74743198Sat, 29 Aug 2026 05:57:49 +0000Creator at ObomediaA 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--74743196
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/74743196Sat, 29 Aug 2026 05:57:44 +0000Creator at ObomediaA 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--74743195
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/74743195Sat, 29 Aug 2026 05:57:40 +0000Creator at ObomediaA 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--74743194
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/74743194Sat, 29 Aug 2026 05:57:36 +0000Creator at ObomediaA 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--74743193
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/74743193Sat, 29 Aug 2026 05:57:32 +0000Creator at ObomediaA 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--74743191
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/74743191Sat, 29 Aug 2026 05:57:29 +0000Creator at ObomediaA 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--74743189
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/74743189Sat, 29 Aug 2026 05:57:25 +0000Creator at ObomediaA 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--74743188
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/74743188Sat, 29 Aug 2026 05:57:21 +0000Creator at ObomediaA 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--74743187
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/74743187Sat, 29 Aug 2026 05:57:17 +0000Creator at ObomediaA 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.]]>1322falsefullhttps://www.spreaker.com/episode/the-thirty-five-thousand-foot-altitude-put-them-on-a-collision-clock--74743186
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/74743186Sat, 29 Aug 2026 05:57:12 +0000Creator at ObomediaA 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--74743184
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/74743184Sat, 29 Aug 2026 05:57:08 +0000Creator at ObomediaA 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--74743183
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/74743183Sat, 29 Aug 2026 05:57:05 +0000Creator at ObomediaA 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--74743182
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/74743182Sat, 29 Aug 2026 05:57:01 +0000Creator at ObomediaAn 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--74743180
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/74743180Sat, 29 Aug 2026 05:56:56 +0000Creator at ObomediaA 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--74743179
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/74743179Sat, 29 Aug 2026 05:56:53 +0000Creator at ObomediaA 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--74743178
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/74743178Sat, 29 Aug 2026 05:56:48 +0000Creator at ObomediaA 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--74743177
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/74743177Sat, 29 Aug 2026 05:56:44 +0000Creator at ObomediaA 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--74743176
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/74743176Sat, 29 Aug 2026 05:56:40 +0000Creator at ObomediaA 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--74743175
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/74743175Sat, 29 Aug 2026 05:56:36 +0000Creator at ObomediaA 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--74743174
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/74743174Sat, 29 Aug 2026 05:56:33 +0000Creator at ObomediaA 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--74743173
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/74743173Sat, 29 Aug 2026 05:56:29 +0000Creator at ObomediaA 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--74743172
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/74743172Sat, 29 Aug 2026 05:56:25 +0000Creator at ObomediaA 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.]]>899falsefullhttps://www.spreaker.com/episode/the-night-a-single-coordinate-killed-257-souls--73096980
A single changed set of numbers - entered into a navigation database at 1:40 a.m. - redirected a sightseeing DC‑10 straight toward a 12,448‑foot volcano and ended 257 lives. How did one small coordinate swap, invisible to a prepared captain, turn a routine Antarctic flight into a catastrophe?

In this episode, we tell what happened on Air New Zealand Flight 901 and how navigation data, crew briefing materials, and a late-night amendment shaped the fatal flight path. You’ll hear the sequence of events that led to the silence on the cockpit voice recorder and ask whether responsibility lay with a database change, the airline, or something else.

Event: Mount Erebus crash
Date: 28 November 1979
Aircraft: McDonnell Douglas DC-10-30, registration ZK-NZP
Fatalities: 257
Price: NZ$359 per sightseeing ticket

- Six seconds after the go‑around alarm sounded, the cockpit voice recorder went silent.
- The navigation coordinates were altered at 1:40 a.m. while the crew slept.
- The volcano Mount Erebus has an elevation of 12,448 feet and the wreckage remains on its slopes.
- Captain Thomas James Collins had 11,151 total flight hours and 2,872 hours on the DC‑10.
- The flight carried 237 passengers including Peter Mulgrew as guest commentator.

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/73096980Fri, 28 Aug 2026 08:00:02 +0000Creator at ObomediaThe Night a Single Coordinate Killed 257 Souls A single changed set of numbers - entered into a navigation database at 1:40 a.m. - redirected a sightseeing DC‑10 straight toward a 12,448‑foot volcano and ended 257 lives. How did one small...
A single changed set of numbers - entered into a navigation database at 1:40 a.m. - redirected a sightseeing DC‑10 straight toward a 12,448‑foot volcano and ended 257 lives. How did one small coordinate swap, invisible to a prepared captain, turn a routine Antarctic flight into a catastrophe?

In this episode, we tell what happened on Air New Zealand Flight 901 and how navigation data, crew briefing materials, and a late-night amendment shaped the fatal flight path. You’ll hear the sequence of events that led to the silence on the cockpit voice recorder and ask whether responsibility lay with a database change, the airline, or something else.

Event: Mount Erebus crash
Date: 28 November 1979
Aircraft: McDonnell Douglas DC-10-30, registration ZK-NZP
Fatalities: 257
Price: NZ$359 per sightseeing ticket

- Six seconds after the go‑around alarm sounded, the cockpit voice recorder went silent.
- The navigation coordinates were altered at 1:40 a.m. while the crew slept.
- The volcano Mount Erebus has an elevation of 12,448 feet and the wreckage remains on its slopes.
- Captain Thomas James Collins had 11,151 total flight hours and 2,872 hours on the DC‑10.
- The flight carried 237 passengers including Peter Mulgrew as guest commentator.

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.]]>1141falsefullhttps://www.spreaker.com/episode/one-wrong-dial-how-1-100-feet-killed-britannia-flight-105--73096978
The clear night, full runway lights and nearly twelve nautical miles visibility should have made this approach routine - yet one incorrect pressure setting put the Britannia 1,100 feet lower than the crew believed. Two different barometric values were transmitted in a single radio call and the required cross-check never happened; how did a standard instrument call lead to ninety-eight fatalities in a Slovenian forest?

In this episode, we follow the final hours of Britannia Flight Flight 105 from London Luton to Ljubljana Brnik and detail the procedural and instrument facts that led to the crash, asking how a single mis-set altimeter could turn a perfectly lit approach into disaster.

Date: August 31-September 1, 1966
Aircraft: Bristol 175 Britannia 102, registration G-ANBB
Passengers and Crew: 117 (110 passengers, 7 crew)
Altitude discrepancy: approximately 1,100 feet between QNH and QFE
Wreckage found: altimeter instrument recovered 2.8 kilometers short of runway

- Departure time from Luton: 21:10 GMT
- Radar contact lost at 00:23:47 GMT on September 1, 1966
- Aircraft total airframe time: 18,444 hours
- Pressurization cycles: 5,380 cycles
- Required QFE setting for approach: 968 millibars (QNH given as 1011 millibars)

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/73096978Thu, 27 Aug 2026 08:00:03 +0000Creator at ObomediaOne Wrong Dial: How 1,100 Feet Killed Britannia Flight 105 The clear night, full runway lights and nearly twelve nautical miles visibility should have made this approach routine - yet one incorrect pressure setting put the Britannia 1,100 feet...
The clear night, full runway lights and nearly twelve nautical miles visibility should have made this approach routine - yet one incorrect pressure setting put the Britannia 1,100 feet lower than the crew believed. Two different barometric values were transmitted in a single radio call and the required cross-check never happened; how did a standard instrument call lead to ninety-eight fatalities in a Slovenian forest?

In this episode, we follow the final hours of Britannia Flight Flight 105 from London Luton to Ljubljana Brnik and detail the procedural and instrument facts that led to the crash, asking how a single mis-set altimeter could turn a perfectly lit approach into disaster.

Date: August 31-September 1, 1966
Aircraft: Bristol 175 Britannia 102, registration G-ANBB
Passengers and Crew: 117 (110 passengers, 7 crew)
Altitude discrepancy: approximately 1,100 feet between QNH and QFE
Wreckage found: altimeter instrument recovered 2.8 kilometers short of runway

- Departure time from Luton: 21:10 GMT
- Radar contact lost at 00:23:47 GMT on September 1, 1966
- Aircraft total airframe time: 18,444 hours
- Pressurization cycles: 5,380 cycles
- Required QFE setting for approach: 968 millibars (QNH given as 1011 millibars)

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.]]>1090falsefullhttps://www.spreaker.com/episode/minutes-over-mamala-bay-how-a-737-lost-its-engine--73096976
A single vertical tail fin floated in Māmala Bay at 2:30 a.m., and one man clung to it while the rest of the Boeing 737 vanished in eleven minutes - a freighter with a 45-year-old airframe and engines designed for an earlier model lost an engine during takeoff. How did corrosion inside a Pratt & Whitney JT8D-9A high-pressure turbine lead to a sudden failure that left two experienced pilots fighting for control?

In this episode, we describe the flight, the crew, the aircraft history, and the sequence of events from takeoff to the moment one pilot misidentified which engine had failed, and we ask how maintenance records and prior incidents may have set the stage for what happened that night.

Person: Henry Okai, 58 years old, approximately 15,781 total flight hours, 871 hours on the 737-200
Person: Gregory Ryan, 50 years old, approximately 5,272 total flight hours, 908 hours on the 737-200
Event: Takeoff at 1:33 a.m. from Honolulu International Airport on July 2, 2021
Aircraft: N810TA, Boeing 737-200 freighter, 45 years old, Pratt & Whitney JT8D-9A engines
Investigation: FAA compliance investigation opened into Rhoades Aviation in 2020; prior left engine failures recorded in 2018 and 2019

- The crew had a combined total of over 21,000 flight hours entering the flight.
- The aircraft experienced a sharp mechanical thud and abnormal vibrations during the takeoff roll at 1:33 a.m.
- Corrosion-induced fractures in high-pressure turbine blades of engine number two caused material to shed and the engine to lose thrust.
- The right engine (engine number two) produced the initial thud, vibrations, and yaw, but First Officer Ryan later identified the failing engine as the left engine.
- FAA service difficulty reports documented left engine failures on N810TA in both 2018 and 2019.

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/73096976Wed, 26 Aug 2026 08:00:02 +0000Creator at ObomediaMinutes Over Māmala Bay: How a 737 Lost Its Engine A single vertical tail fin floated in Māmala Bay at 2:30 a.m., and one man clung to it while the rest of the Boeing 737 vanished in eleven minutes - a freighter with a 45-year-old airframe and...
A single vertical tail fin floated in Māmala Bay at 2:30 a.m., and one man clung to it while the rest of the Boeing 737 vanished in eleven minutes - a freighter with a 45-year-old airframe and engines designed for an earlier model lost an engine during takeoff. How did corrosion inside a Pratt & Whitney JT8D-9A high-pressure turbine lead to a sudden failure that left two experienced pilots fighting for control?

In this episode, we describe the flight, the crew, the aircraft history, and the sequence of events from takeoff to the moment one pilot misidentified which engine had failed, and we ask how maintenance records and prior incidents may have set the stage for what happened that night.

Person: Henry Okai, 58 years old, approximately 15,781 total flight hours, 871 hours on the 737-200
Person: Gregory Ryan, 50 years old, approximately 5,272 total flight hours, 908 hours on the 737-200
Event: Takeoff at 1:33 a.m. from Honolulu International Airport on July 2, 2021
Aircraft: N810TA, Boeing 737-200 freighter, 45 years old, Pratt & Whitney JT8D-9A engines
Investigation: FAA compliance investigation opened into Rhoades Aviation in 2020; prior left engine failures recorded in 2018 and 2019

- The crew had a combined total of over 21,000 flight hours entering the flight.
- The aircraft experienced a sharp mechanical thud and abnormal vibrations during the takeoff roll at 1:33 a.m.
- Corrosion-induced fractures in high-pressure turbine blades of engine number two caused material to shed and the engine to lose thrust.
- The right engine (engine number two) produced the initial thud, vibrations, and yaw, but First Officer Ryan later identified the failing engine as the left engine.
- FAA service difficulty reports documented left engine failures on N810TA in both 2018 and 2019.

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.]]>1129falsefullhttps://www.spreaker.com/episode/the-silent-65-minutes-how-nc13357-vanished-over-wasatch-peaks--73096970
Two wristwatches stopped at 3:05 PM at the crash site, and eight people had boarded a United Air Lines Boeing 247 in Salt Lake City at 2:00 PM - then 65 minutes of silence. How did a well‑flown pilot with 7,000 hours and a second crewman vanish into the Wasatch in weather described as the worst in the region without leaving a single determinative clue?

In this episode, we tell the documented record of United Air Lines flight NC13357: who was aboard, the mountain and weather the flight encountered, the search that followed, and the unanswered question about what happened in those sixty‑five minutes.

Date: February 23, 1934
Aircraft: United Air Lines Boeing 247
Persons aboard: 8 (2 crew, 5 passengers, 1 stewardess)
Pilot hours: 7,000+ logged hours for Lloyd Anderson
Last radio contact: 2:20 PM; two wristwatches stopped at 3:05 PM

- Departure time from Salt Lake City: 2:00 PM
- Last radio transmission: “all was okay” at 2:20 PM
- Watches at wreck stopped at: 3:05 PM
- Fuel noted depleted by: 6:30 AM Saturday
- Pilot Lloyd Anderson age and license year: 32 years old, licensed in 1926

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/73096970Tue, 25 Aug 2026 08:00:03 +0000Creator at ObomediaThe Silent 65 Minutes: How NC13357 Vanished Over Wasatch Peaks Two wristwatches stopped at 3:05 PM at the crash site, and eight people had boarded a United Air Lines Boeing 247 in Salt Lake City at 2:00 PM - then 65 minutes of silence. How did a...
Two wristwatches stopped at 3:05 PM at the crash site, and eight people had boarded a United Air Lines Boeing 247 in Salt Lake City at 2:00 PM - then 65 minutes of silence. How did a well‑flown pilot with 7,000 hours and a second crewman vanish into the Wasatch in weather described as the worst in the region without leaving a single determinative clue?

In this episode, we tell the documented record of United Air Lines flight NC13357: who was aboard, the mountain and weather the flight encountered, the search that followed, and the unanswered question about what happened in those sixty‑five minutes.

Date: February 23, 1934
Aircraft: United Air Lines Boeing 247
Persons aboard: 8 (2 crew, 5 passengers, 1 stewardess)
Pilot hours: 7,000+ logged hours for Lloyd Anderson
Last radio contact: 2:20 PM; two wristwatches stopped at 3:05 PM

- Departure time from Salt Lake City: 2:00 PM
- Last radio transmission: “all was okay” at 2:20 PM
- Watches at wreck stopped at: 3:05 PM
- Fuel noted depleted by: 6:30 AM Saturday
- Pilot Lloyd Anderson age and license year: 32 years old, licensed in 1926

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.]]>1013falsefullhttps://www.spreaker.com/episode/when-instruments-lied-the-89-second-crash-of-tarom-371--73096966
The climb from Bucharest lasted just eighty-nine seconds before an Airbus A310 struck the ground at 324 knots and carved a six-metre crater; sixty people were aboard and the flight recorders captured every moment-but the criminal case files later vanished. How did a known engine fault, a captain’s sudden collapse, and instruments that displayed opposite motions combine into a sequence of failures none of the crew could survive?

In this episode, we tell the sequence of events from takeoff at Otopeni to impact near Balotești, describing crew experience, aircraft history, and the mechanical anomalies that were known before the flight. Could the interplay of a documented autothrottle engine fault, a captain incapacitated mid-climb, and an attitude indicator that behaved opposite to older Soviet instruments explain why there was no recovery?

Date: March 31, 1995
Aircraft: Airbus A310, registration YR-LCC
Location: Near Balotești, after takeoff from Bucharest Otopeni Airport
Speed at impact: 324 knots
Occupants: 60 people aboard

- Takeoff occurred at 09:06:44 and impact happened 89 seconds later.
- The crash created a crater six metres deep near the village of Balotești.
- Captain Liviu Bătănoiu had 14,312 total flight hours and 1,735 hours on the A310.
- First Officer Ionel Stoi had nearly 9,000 total flight hours and 650 hours on the A310.
- Engine number one had a documented tendency to retard to idle during climb-to-cruise transitions; the fault occurred again on March 16, fifteen days before the accident.

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/73096966Mon, 24 Aug 2026 08:00:03 +0000Creator at ObomediaWhen Instruments Lied: The 89-Second Crash of TAROM 371 The climb from Bucharest lasted just eighty-nine seconds before an Airbus A310 struck the ground at 324 knots and carved a six-metre crater; sixty people were aboard and the flight recorders...
The climb from Bucharest lasted just eighty-nine seconds before an Airbus A310 struck the ground at 324 knots and carved a six-metre crater; sixty people were aboard and the flight recorders captured every moment-but the criminal case files later vanished. How did a known engine fault, a captain’s sudden collapse, and instruments that displayed opposite motions combine into a sequence of failures none of the crew could survive?

In this episode, we tell the sequence of events from takeoff at Otopeni to impact near Balotești, describing crew experience, aircraft history, and the mechanical anomalies that were known before the flight. Could the interplay of a documented autothrottle engine fault, a captain incapacitated mid-climb, and an attitude indicator that behaved opposite to older Soviet instruments explain why there was no recovery?

Date: March 31, 1995
Aircraft: Airbus A310, registration YR-LCC
Location: Near Balotești, after takeoff from Bucharest Otopeni Airport
Speed at impact: 324 knots
Occupants: 60 people aboard

- Takeoff occurred at 09:06:44 and impact happened 89 seconds later.
- The crash created a crater six metres deep near the village of Balotești.
- Captain Liviu Bătănoiu had 14,312 total flight hours and 1,735 hours on the A310.
- First Officer Ionel Stoi had nearly 9,000 total flight hours and 650 hours on the A310.
- Engine number one had a documented tendency to retard to idle during climb-to-cruise transitions; the fault occurred again on March 16, fifteen days before the accident.

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.]]>1120falsefullhttps://www.spreaker.com/episode/the-palm-that-killed-125-when-a-throttle-whispered-disaster--73096961
A single palm’s width of movement on a throttle lever - roughly 400 grams of force or less - set off a chain that ended with 125 people killed on the runway. The left engine throttle coupling had never been inspected in 19 years, a warning sounded and was dismissed, and a deferred reverser created a procedural trap that no training had closed. How did routine checks, a tiny mechanical play, and human habit combine to make disaster inevitable?

In this episode, we present the sequence of events, crew backgrounds, mechanical history, and investigative outcomes surrounding S7 Airlines Flight 778 to show how small margins and missing procedures matter; could a different scan, a practiced hand, or one inspection have changed everything?

Person: Sergey Gennadyevich Shibanov, 45, Captain, 10,611 total hours, ~1,000 hours on A310
Person: Vladimir Gennadyevich Chernykh, 48, First Officer, 9,771 total hours, 158 hours on A310
Date: July 9, 2006
Aircraft: Airbus A310-324, registration F-OGYP, 19 years old
Event: 125 fatalities on landing at Irkutsk after runway fire

- 203 people were aboard S7 Airlines Flight 778 at pushback.
- 14 children aged 12 or younger were on board.
- The left engine throttle coupling had never been inspected in 19 years of service.
- A properly calibrated coupling required roughly 400 grams of force to move; the actual lever offered almost no resistance.
- The criminal investigation lasted nearly four years, was extended three times, and closed silently in March 2010.

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/73096961Sun, 23 Aug 2026 08:00:02 +0000Creator at ObomediaThe Palm That Killed 125: When a Throttle Whispered Disaster A single palm’s width of movement on a throttle lever - roughly 400 grams of force or less - set off a chain that ended with 125 people killed on the runway. The left engine throttle...
A single palm’s width of movement on a throttle lever - roughly 400 grams of force or less - set off a chain that ended with 125 people killed on the runway. The left engine throttle coupling had never been inspected in 19 years, a warning sounded and was dismissed, and a deferred reverser created a procedural trap that no training had closed. How did routine checks, a tiny mechanical play, and human habit combine to make disaster inevitable?

In this episode, we present the sequence of events, crew backgrounds, mechanical history, and investigative outcomes surrounding S7 Airlines Flight 778 to show how small margins and missing procedures matter; could a different scan, a practiced hand, or one inspection have changed everything?

Person: Sergey Gennadyevich Shibanov, 45, Captain, 10,611 total hours, ~1,000 hours on A310
Person: Vladimir Gennadyevich Chernykh, 48, First Officer, 9,771 total hours, 158 hours on A310
Date: July 9, 2006
Aircraft: Airbus A310-324, registration F-OGYP, 19 years old
Event: 125 fatalities on landing at Irkutsk after runway fire

- 203 people were aboard S7 Airlines Flight 778 at pushback.
- 14 children aged 12 or younger were on board.
- The left engine throttle coupling had never been inspected in 19 years of service.
- A properly calibrated coupling required roughly 400 grams of force to move; the actual lever offered almost no resistance.
- The criminal investigation lasted nearly four years, was extended three times, and closed silently in March 2010.

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.]]>1058falsefullhttps://www.spreaker.com/episode/seconds-of-silence-how-a-faulty-arthur-killed-six-on-flight-3838--73096960
A familiar warning light had blinked on this jet eight times in forty months, and the cockpit voice recorder was already broken before takeoff - leaving forty-seven minutes of flight, including the fatal twenty-four seconds, unrecorded. How did a misconfigured control system called Arthur turn routine inputs into a catastrophe that killed six people?

In this episode, we tell what happened on September 14, 1999, aboard a Dassault Falcon 900B registered SX-ECH, describe the sequence of maintenance warnings and crew decisions during cruise, and trace the unanswered question: could routine resets and flawed training have masked a system that was silently set to low-speed mode?

Date: September 14, 1999
Aircraft: Dassault Falcon 900B
Registration: SX-ECH
Location: departed Athens (Ellinikon Airport) bound for Bucharest
Passengers: 11

- The cockpit voice recorder on SX-ECH was broken before the aircraft left Athens, the tape sitting in two pieces.
- The PITCH FEEL annunciator had been illuminated on this aircraft eight times in the previous forty months and was glowing since climb-out.
- The Arthur unit had been silently misconfigured in low-speed configuration prior to and during the flight.
- Captain Yiannis Androulakis had 8,239 total flight hours; co-pilot Grigoris Sinekoglou had 7,465 hours, with fewer than 501 combined hours on the Falcon 900B.
- The critical twenty-four seconds that killed six people occurred during cruise at 332 knots as the aircraft later began descent toward 15,000 feet.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/73096960Sat, 22 Aug 2026 08:00:03 +0000Creator at ObomediaSeconds of Silence: How a Faulty 'Arthur' Killed Six on Flight 3838 A familiar warning light had blinked on this jet eight times in forty months, and the cockpit voice recorder was already broken before takeoff - leaving forty-seven minutes of...
A familiar warning light had blinked on this jet eight times in forty months, and the cockpit voice recorder was already broken before takeoff - leaving forty-seven minutes of flight, including the fatal twenty-four seconds, unrecorded. How did a misconfigured control system called Arthur turn routine inputs into a catastrophe that killed six people?

In this episode, we tell what happened on September 14, 1999, aboard a Dassault Falcon 900B registered SX-ECH, describe the sequence of maintenance warnings and crew decisions during cruise, and trace the unanswered question: could routine resets and flawed training have masked a system that was silently set to low-speed mode?

Date: September 14, 1999
Aircraft: Dassault Falcon 900B
Registration: SX-ECH
Location: departed Athens (Ellinikon Airport) bound for Bucharest
Passengers: 11

- The cockpit voice recorder on SX-ECH was broken before the aircraft left Athens, the tape sitting in two pieces.
- The PITCH FEEL annunciator had been illuminated on this aircraft eight times in the previous forty months and was glowing since climb-out.
- The Arthur unit had been silently misconfigured in low-speed configuration prior to and during the flight.
- Captain Yiannis Androulakis had 8,239 total flight hours; co-pilot Grigoris Sinekoglou had 7,465 hours, with fewer than 501 combined hours on the Falcon 900B.
- The critical twenty-four seconds that killed six people occurred during cruise at 332 knots as the aircraft later began descent toward 15,000 feet.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1160falsefullhttps://www.spreaker.com/episode/the-fingertip-switch-that-turned-a-routine-flight-into-a-belly-landing--73096956
A fingertip-sized circuit breaker hidden low on the cockpit floor tripped during approach and kept the landing gear from extending, forcing a Boeing 767 to belly-land on foam at Warsaw Chopin Airport - 231 people evacuated with no serious injuries. How did a single unnoticed switch set off one of the most closely watched emergency landings in European aviation history, and who missed it?

In this episode, we tell the sequence of events from Newark departure to the belly landing in Warsaw, describing the mechanical failure, crew decisions, and emergency response that shaped the outcome. Could a reset of that tiny breaker have turned this emergency back into an ordinary arrival?

Date: November 1, 2011
Aircraft: Boeing 767, registration SP-LPC, named Poznań
Passengers and crew: 231 people on board (220 passengers, 11 crew)
Flight origin and destination: Newark Liberty International Airport to Warsaw Chopin Airport
Outcome: Belly landing on Runway 33 with foam; no serious injuries

- The aircraft was built in 1997 and had 85,429 flight hours and 8,002 pressurization cycles.
- The crew logged more than 25,000 flight hours combined, with 15,000 hours on the 767.
- Less than 30 minutes after takeoff a center hydraulic hose failed, causing total loss of the primary landing gear system.
- The gear handle moved on approach but the landing gear did not extend, prompting a go-around and a coordinated emergency response.
- Runway 33 was foamed and emergency crews waited over an hour as Polish Air Force fighters circled overhead before the belly landing.

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/73096956Fri, 21 Aug 2026 08:00:03 +0000Creator at ObomediaThe Fingertip Switch That Turned a Routine Flight into a Belly Landing A fingertip-sized circuit breaker hidden low on the cockpit floor tripped during approach and kept the landing gear from extending, forcing a Boeing 767 to belly-land on foam at...
A fingertip-sized circuit breaker hidden low on the cockpit floor tripped during approach and kept the landing gear from extending, forcing a Boeing 767 to belly-land on foam at Warsaw Chopin Airport - 231 people evacuated with no serious injuries. How did a single unnoticed switch set off one of the most closely watched emergency landings in European aviation history, and who missed it?

In this episode, we tell the sequence of events from Newark departure to the belly landing in Warsaw, describing the mechanical failure, crew decisions, and emergency response that shaped the outcome. Could a reset of that tiny breaker have turned this emergency back into an ordinary arrival?

Date: November 1, 2011
Aircraft: Boeing 767, registration SP-LPC, named Poznań
Passengers and crew: 231 people on board (220 passengers, 11 crew)
Flight origin and destination: Newark Liberty International Airport to Warsaw Chopin Airport
Outcome: Belly landing on Runway 33 with foam; no serious injuries

- The aircraft was built in 1997 and had 85,429 flight hours and 8,002 pressurization cycles.
- The crew logged more than 25,000 flight hours combined, with 15,000 hours on the 767.
- Less than 30 minutes after takeoff a center hydraulic hose failed, causing total loss of the primary landing gear system.
- The gear handle moved on approach but the landing gear did not extend, prompting a go-around and a coordinated emergency response.
- Runway 33 was foamed and emergency crews waited over an hour as Polish Air Force fighters circled overhead before the belly landing.

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.]]>1056falsefullhttps://www.spreaker.com/episode/the-knob-that-killed-how-a320-flight-605-vanished-two-seconds-from-runway--73096953
Fear that a single human error can turn routine into catastrophe: a brand-new Airbus A320 hit a golf course 2,800 feet short of Bangalore's runway on February 14, 1990, killing 92 of 146 people aboard - and investigators said the disaster hinged on one knob and two seconds. What exactly happened in that cockpit in those final moments?

In this episode, we tell the story of Indian Airlines Flight 605 from takeoff to impact, describe the crew, aircraft and sequence of events, and follow the unanswered question about the decisive action that sent the plane into the ground.

Event: Indian Airlines Flight 605
Date: February 14, 1990
Location: Bangalore (HAL Airport)
Aircraft: Airbus A320, serial number 79, registration VT-EPN
Casualties: 92 dead, 54 survived (all injured)

- The aircraft struck terrain 2,800 feet short of the runway on a golf course.
- 146 people were on board at the time of impact.
- VT-EPN had accumulated approximately 370 flight hours across 302 flights and had been in service for five months.
- Captain Cyril Fernandez had 9,307 total flight hours and 68 hours on the A320.
- Captain Satish Gopujkar had 10,340 total flight hours and 255 hours on the A320 while serving as check pilot.

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/73096953Thu, 20 Aug 2026 08:00:05 +0000Creator at ObomediaThe Knob That Killed: How A320 Flight 605 Vanished Two Seconds From Runway Fear that a single human error can turn routine into catastrophe: a brand-new Airbus A320 hit a golf course 2,800 feet short of Bangalore's runway on February 14, 1990,...
Fear that a single human error can turn routine into catastrophe: a brand-new Airbus A320 hit a golf course 2,800 feet short of Bangalore's runway on February 14, 1990, killing 92 of 146 people aboard - and investigators said the disaster hinged on one knob and two seconds. What exactly happened in that cockpit in those final moments?

In this episode, we tell the story of Indian Airlines Flight 605 from takeoff to impact, describe the crew, aircraft and sequence of events, and follow the unanswered question about the decisive action that sent the plane into the ground.

Event: Indian Airlines Flight 605
Date: February 14, 1990
Location: Bangalore (HAL Airport)
Aircraft: Airbus A320, serial number 79, registration VT-EPN
Casualties: 92 dead, 54 survived (all injured)

- The aircraft struck terrain 2,800 feet short of the runway on a golf course.
- 146 people were on board at the time of impact.
- VT-EPN had accumulated approximately 370 flight hours across 302 flights and had been in service for five months.
- Captain Cyril Fernandez had 9,307 total flight hours and 68 hours on the A320.
- Captain Satish Gopujkar had 10,340 total flight hours and 255 hours on the A320 while serving as check pilot.

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.]]>1088falsefullhttps://www.spreaker.com/episode/too-tired-to-land-how-two-veteran-pilots-misjudged-narita-runway--73096951
Sleep-deprived and flying a converted MD-11 with over 19,000 combined hours between them, two veteran pilots failed to get a heavy freighter safely onto Narita's 13,125-foot runway - the aircraft bounced, porpoised, the left wing failed, and the jet rolled inverted five minutes before its scheduled arrival. Neither pilot survived, and investigators later found hotel records, credit card receipts, and cockpit voice recorder audio pointing to a quieter culprit: severe fatigue. How did two experienced military-trained aviators make a series of mistakes that no onboard systems or weather should have allowed?

In this episode, we lay out the sequence of events, the pilots’ backgrounds and flight hours, the aircraft’s history, and the investigator findings that connected fragmented sleep and duty patterns to the final minutes of FedEx Express Flight 80. What exactly did the cockpit voice recorder reveal about their condition and actions on final approach?

Date: March 23, 2009
Event: FedEx Express Flight 80 crash at Narita International Airport
Aircraft: McDonnell Douglas MD-11, registration N526FE
Person: Captain Kevin Kyle Mosley - 54 years old, ~12,800 total hours, 3,648 MD-11 hours
Person: First Officer Anthony Stephen Stephen - 49 years old, ~6,300 total hours, 879 MD-11 hours

- Takeoff time from Guangzhou Baiyun International Airport: 02:02 China Standard Time
- Runway length at Narita involved: 13,125 feet (Runway 34L)
- Time of incident: 06:48 in the morning local time
- Both pilots had no more than four consecutive hours of sleep in the 24 hours before departure
- Aircraft history: built 1994, served as NASA test platform, then Delta (1996-2004), acquired by FedEx Oct 2004, converted to freighter and in FedEx service late 2006

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/73096951Wed, 19 Aug 2026 08:00:03 +0000Creator at ObomediaToo Tired to Land: How Two Veteran Pilots Misjudged Narita Runway Sleep-deprived and flying a converted MD-11 with over 19,000 combined hours between them, two veteran pilots failed to get a heavy freighter safely onto Narita's 13,125-foot runway -...
Sleep-deprived and flying a converted MD-11 with over 19,000 combined hours between them, two veteran pilots failed to get a heavy freighter safely onto Narita's 13,125-foot runway - the aircraft bounced, porpoised, the left wing failed, and the jet rolled inverted five minutes before its scheduled arrival. Neither pilot survived, and investigators later found hotel records, credit card receipts, and cockpit voice recorder audio pointing to a quieter culprit: severe fatigue. How did two experienced military-trained aviators make a series of mistakes that no onboard systems or weather should have allowed?

In this episode, we lay out the sequence of events, the pilots’ backgrounds and flight hours, the aircraft’s history, and the investigator findings that connected fragmented sleep and duty patterns to the final minutes of FedEx Express Flight 80. What exactly did the cockpit voice recorder reveal about their condition and actions on final approach?

Date: March 23, 2009
Event: FedEx Express Flight 80 crash at Narita International Airport
Aircraft: McDonnell Douglas MD-11, registration N526FE
Person: Captain Kevin Kyle Mosley - 54 years old, ~12,800 total hours, 3,648 MD-11 hours
Person: First Officer Anthony Stephen Stephen - 49 years old, ~6,300 total hours, 879 MD-11 hours

- Takeoff time from Guangzhou Baiyun International Airport: 02:02 China Standard Time
- Runway length at Narita involved: 13,125 feet (Runway 34L)
- Time of incident: 06:48 in the morning local time
- Both pilots had no more than four consecutive hours of sleep in the 24 hours before departure
- Aircraft history: built 1994, served as NASA test platform, then Delta (1996-2004), acquired by FedEx Oct 2004, converted to freighter and in FedEx service late 2006

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.]]>1088falsefullhttps://www.spreaker.com/episode/five-feet-short-the-commuter-flight-that-never-reached-runway-33--73096948
A commuter Beechcraft Model 99A struck an embankment just 100 yards short of Johnstown-Cambria County Airport and came to rest with the runway in sight - it was, an airline official later said, a matter of five feet. Seventeen people were on board; twelve died, the floor structure and seat tracks were destroyed, and rescuers did not arrive for fifty minutes - so what exactly went wrong in those final seconds?

In this episode, we lay out the factual timeline from departure to impact, describe the aircraft and crew experience, and follow the investigation questions left open by the record. How did a twin‑engine commuter plane, on a routine forty‑minute hop, descend below the safe approach slope and end its flight nose‑up, wings‑level, one hundred yards short of Runway 33?

Date: January 1974
Aircraft: Beechcraft Model 99A, registration N125AE
Flight: Commonwealth Commuter Flight 317 (operated by Air East for Allegheny Airlines)
People on board: 17 (15 passengers, 2 crew)
Casualties: 12 fatalities

- Departure time from Pittsburgh International: approximately 18:30.
- Aircraft total airframe hours: 7,503 hours and 2 Pratt & Whitney Canada PT6 turboprop engines.
- Captain Daniel Brannon: 39 years old, 6,331 total flight hours, 383 hours on type.
- First Officer Gerald Knouff: 24 years old, 1,790 total flight hours, 380 hours on type.
- First rescue vehicle arrival: approximately 19:55, about 50 minutes after impact.

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/73096948Tue, 18 Aug 2026 08:00:03 +0000Creator at ObomediaFive Feet Short: The Commuter Flight That Never Reached Runway 33 A commuter Beechcraft Model 99A struck an embankment just 100 yards short of Johnstown-Cambria County Airport and came to rest with the runway in sight - it was, an airline official...
A commuter Beechcraft Model 99A struck an embankment just 100 yards short of Johnstown-Cambria County Airport and came to rest with the runway in sight - it was, an airline official later said, a matter of five feet. Seventeen people were on board; twelve died, the floor structure and seat tracks were destroyed, and rescuers did not arrive for fifty minutes - so what exactly went wrong in those final seconds?

In this episode, we lay out the factual timeline from departure to impact, describe the aircraft and crew experience, and follow the investigation questions left open by the record. How did a twin‑engine commuter plane, on a routine forty‑minute hop, descend below the safe approach slope and end its flight nose‑up, wings‑level, one hundred yards short of Runway 33?

Date: January 1974
Aircraft: Beechcraft Model 99A, registration N125AE
Flight: Commonwealth Commuter Flight 317 (operated by Air East for Allegheny Airlines)
People on board: 17 (15 passengers, 2 crew)
Casualties: 12 fatalities

- Departure time from Pittsburgh International: approximately 18:30.
- Aircraft total airframe hours: 7,503 hours and 2 Pratt & Whitney Canada PT6 turboprop engines.
- Captain Daniel Brannon: 39 years old, 6,331 total flight hours, 383 hours on type.
- First Officer Gerald Knouff: 24 years old, 1,790 total flight hours, 380 hours on type.
- First rescue vehicle arrival: approximately 19:55, about 50 minutes after impact.

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.]]>1013falsefullhttps://www.spreaker.com/episode/when-a-turn-killed-65-the-aviateca-flight-901-mystery--73096946
Darkness, delay and a single unannounced turn put a Boeing 737 twelve miles off the expected approach and on a collision course with a volcano; sixty-five people died that night - so how did a routine decision become lethal? This episode pulls at the minute-long gap between where air traffic control thought the plane was and where it actually flew, and asks: why did the crew change course without telling anyone?

In this episode, we present the timeline of Aviateca Flight 901 from departure delays through the critical final minutes, describe the crew and aircraft details available from the record, and follow the path that led to impact on San Vicente - could a different communication or choice have saved them?

Date: August 9, 1995
Aircraft: Boeing 737, registration N125GU
Fatalities: 65
Captain: Axel Byron Miranda Herrera, 39, 9,828 flight hours
First Officer: Víctor Francisco Sandoval Salguero, 36, 4,696 flight hours

- Flight departed Guatemala City roughly two hours late due to storms.
- Aircraft had been added to the Aviateca fleet in March 1995 and had 16,645 hours.
- The crew elected to approach Runway 07 using the ILS, turning the flight path 12 miles closer to San Vicente volcano.
- San Vicente summit rises to 7,159 feet; the approach to Runway 07 required staying above 7,500 feet until clear of terrain.
- Air traffic controller José Alberto Chávez had no indication the aircraft had deviated from the standard airway G346 when he cleared descent.

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/73096946Mon, 17 Aug 2026 08:00:03 +0000Creator at ObomediaWhen a Turn Killed 65: The Aviateca Flight 901 Mystery Darkness, delay and a single unannounced turn put a Boeing 737 twelve miles off the expected approach and on a collision course with a volcano; sixty-five people died that night - so how did a...
Darkness, delay and a single unannounced turn put a Boeing 737 twelve miles off the expected approach and on a collision course with a volcano; sixty-five people died that night - so how did a routine decision become lethal? This episode pulls at the minute-long gap between where air traffic control thought the plane was and where it actually flew, and asks: why did the crew change course without telling anyone?

In this episode, we present the timeline of Aviateca Flight 901 from departure delays through the critical final minutes, describe the crew and aircraft details available from the record, and follow the path that led to impact on San Vicente - could a different communication or choice have saved them?

Date: August 9, 1995
Aircraft: Boeing 737, registration N125GU
Fatalities: 65
Captain: Axel Byron Miranda Herrera, 39, 9,828 flight hours
First Officer: Víctor Francisco Sandoval Salguero, 36, 4,696 flight hours

- Flight departed Guatemala City roughly two hours late due to storms.
- Aircraft had been added to the Aviateca fleet in March 1995 and had 16,645 hours.
- The crew elected to approach Runway 07 using the ILS, turning the flight path 12 miles closer to San Vicente volcano.
- San Vicente summit rises to 7,159 feet; the approach to Runway 07 required staying above 7,500 feet until clear of terrain.
- Air traffic controller José Alberto Chávez had no indication the aircraft had deviated from the standard airway G346 when he cleared descent.

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.]]>1091falsefullhttps://www.spreaker.com/episode/silent-stall-how-a-signed-off-warning-failed-flight-827--73096945
The idea that a freshly tested stall warning system could stay silent while a thirty-year-old DC-8 hit a Virginia mountainside at 240 knots creates a chilling gap between certification and catastrophe; investigators found the stabilizer trim set nine knots below the crew's instructed setting - so what quiet failure hid behind a signed-off test?

In this episode, we describe the flight, the crew, the maintenance and the sequence of events leading up to impact, and ask how organizational gaps and undocumented procedures may have shaped the outcome.

Date: December 22, 1996
Aircraft: Douglas DC-8, tail number N827AX
Operator: ABX Air (cargo division of Airborne Express)
Location: Departed Greensboro; impact on a Virginia mountainside
Event: Post-maintenance evaluation flight with a non-sounding stall warning system

- Impact speed recorded as 240 knots.
- Stabilizer trim measured nine knots below the setting the crew had been told to use.
- Aircraft built in 1967 with 62,800 flight hours and 24,234 pressurization cycles.
- Stall warning system tested and signed off three days before the flight (returned to ABX on December 15).
- Six men on board: three flight crew (Avery, Leming, Waelti) and three technicians (Goettsch, Athey, Scully).

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/73096945Sun, 16 Aug 2026 08:00:03 +0000Creator at ObomediaSilent Stall: How a Signed-Off Warning Failed Flight 827 The idea that a freshly tested stall warning system could stay silent while a thirty-year-old DC-8 hit a Virginia mountainside at 240 knots creates a chilling gap between certification and...
The idea that a freshly tested stall warning system could stay silent while a thirty-year-old DC-8 hit a Virginia mountainside at 240 knots creates a chilling gap between certification and catastrophe; investigators found the stabilizer trim set nine knots below the crew's instructed setting - so what quiet failure hid behind a signed-off test?

In this episode, we describe the flight, the crew, the maintenance and the sequence of events leading up to impact, and ask how organizational gaps and undocumented procedures may have shaped the outcome.

Date: December 22, 1996
Aircraft: Douglas DC-8, tail number N827AX
Operator: ABX Air (cargo division of Airborne Express)
Location: Departed Greensboro; impact on a Virginia mountainside
Event: Post-maintenance evaluation flight with a non-sounding stall warning system

- Impact speed recorded as 240 knots.
- Stabilizer trim measured nine knots below the setting the crew had been told to use.
- Aircraft built in 1967 with 62,800 flight hours and 24,234 pressurization cycles.
- Stall warning system tested and signed off three days before the flight (returned to ABX on December 15).
- Six men on board: three flight crew (Avery, Leming, Waelti) and three technicians (Goettsch, Athey, Scully).

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.]]>1069falsefullhttps://www.spreaker.com/episode/four-alarms-four-chances-to-climb-four-times-the-crew-did-not-one-mountain-waiting--73096942
A flight left with two known, uncorrected defects - an inoperative VOR receiver and a missing flight director modification - and crashed into Mount Kaimaktsalan less than four minutes after takeoff. How did a crew with nearly 26,000 combined hours and no prior experience into Thessaloniki follow a departure that ended in controlled flight into terrain?

In this episode, we tell the sequence of decisions and documented failures that preceded the December 21, 1997 crash of a Lviv Airlines Yak-42, from the last-minute aircraft substitution to the cockpit warnings that were ignored. What combination of human, technical, and procedural breaks turned routine pages of paperwork into a fatal flight?

Date: December 21, 1997
Aircraft: Yakovlev Yak-42, registration UR-42334
Operator: Lviv Airlines
Passengers and crew: 166 passengers, 8 crew
Location: Mount Kaimaktsalan, Pieria Mountains (near Thessaloniki)

- Original aircraft (Boeing 737) grounded for engine problems and replaced by Yak-42 before the flight.
- Yak-42 had an inoperative VOR receiver identified before leaving Ukrainian airspace.
- Yak-42 lacked evidence of a required flight director modification; the system was installed but not properly fixed.
- Flight crew included a captain with 9,850 flight hours and a flight instructor with 16,210 hours, yet none had flown into Thessaloniki before.
- Aircraft struck the northern slope of Mount Kaimaktsalan less than four minutes after takeoff; there were no survivors.

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/73096942Sat, 15 Aug 2026 08:00:03 +0000Creator at ObomediaFour alarms. Four chances to climb. Four times the crew did not. One mountain waiting A flight left with two known, uncorrected defects - an inoperative VOR receiver and a missing flight director modification - and crashed into Mount Kaimaktsalan...
A flight left with two known, uncorrected defects - an inoperative VOR receiver and a missing flight director modification - and crashed into Mount Kaimaktsalan less than four minutes after takeoff. How did a crew with nearly 26,000 combined hours and no prior experience into Thessaloniki follow a departure that ended in controlled flight into terrain?

In this episode, we tell the sequence of decisions and documented failures that preceded the December 21, 1997 crash of a Lviv Airlines Yak-42, from the last-minute aircraft substitution to the cockpit warnings that were ignored. What combination of human, technical, and procedural breaks turned routine pages of paperwork into a fatal flight?

Date: December 21, 1997
Aircraft: Yakovlev Yak-42, registration UR-42334
Operator: Lviv Airlines
Passengers and crew: 166 passengers, 8 crew
Location: Mount Kaimaktsalan, Pieria Mountains (near Thessaloniki)

- Original aircraft (Boeing 737) grounded for engine problems and replaced by Yak-42 before the flight.
- Yak-42 had an inoperative VOR receiver identified before leaving Ukrainian airspace.
- Yak-42 lacked evidence of a required flight director modification; the system was installed but not properly fixed.
- Flight crew included a captain with 9,850 flight hours and a flight instructor with 16,210 hours, yet none had flown into Thessaloniki before.
- Aircraft struck the northern slope of Mount Kaimaktsalan less than four minutes after takeoff; there were no survivors.

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.]]>978falsefullhttps://www.spreaker.com/episode/ten-feet-above-ground-how-two-planes-locked-and-fell-in-90-seconds--73096937
Ten feet above the runway, in perfect visibility, a DC-3 on final approach and a Vultee BT-13 collided and locked together - then both fell and nine people died within roughly ninety seconds. Who owned the decision to fly in that uncontrolled airspace, and why did two experienced pilots fail to see each other until it was too late?

In this episode, we tell what happened on April 22, 1947, during a Delta survey flight into Muscogee County Airport and a concurrent BT-13 departure, laying out the sequence of events, the aircraft involved, and the unresolved questions about responsibility and visibility that the Civil Aeronautics Board later addressed. What caused the training aircraft to be in the same traffic pattern as the Survey, and how did the absence of a control tower factor into the crash?

Date: April 22, 1947
Location: Muscogee County Airport, Columbus, Georgia
Event: Mid-air collision between Douglas DC-3 (Survey) and Vultee BT-13 Valiant
Person: George Robert Cushing, 48 years old, 11,091 total flight hours
Status: Nine fatalities (all aboard both aircraft)

- The DC-3 named Survey was on final approach at ten forty, roughly ten feet above the runway, when struck from behind and above.
- The collision occurred after the Survey had completed one and a half left-hand traffic circuits following standard procedure.
- The BT-13 departed at ten thirty from Columbus Municipal Airport and had about 100 total flight hours.
- The DC-3 had accumulated 2,899 total flight hours and had two Pratt & Whitney R-1830-92 engines, each 1,200 horsepower.
- The Civil Aeronautics Board assigned responsibility to one individual and criticized the lack of a control tower at Muscogee County Airport.

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/73096937Fri, 14 Aug 2026 08:00:02 +0000Creator at ObomediaTen Feet Above Ground: How Two Planes Locked and Fell in 90 Seconds Ten feet above the runway, in perfect visibility, a DC-3 on final approach and a Vultee BT-13 collided and locked together - then both fell and nine people died within roughly...
Ten feet above the runway, in perfect visibility, a DC-3 on final approach and a Vultee BT-13 collided and locked together - then both fell and nine people died within roughly ninety seconds. Who owned the decision to fly in that uncontrolled airspace, and why did two experienced pilots fail to see each other until it was too late?

In this episode, we tell what happened on April 22, 1947, during a Delta survey flight into Muscogee County Airport and a concurrent BT-13 departure, laying out the sequence of events, the aircraft involved, and the unresolved questions about responsibility and visibility that the Civil Aeronautics Board later addressed. What caused the training aircraft to be in the same traffic pattern as the Survey, and how did the absence of a control tower factor into the crash?

Date: April 22, 1947
Location: Muscogee County Airport, Columbus, Georgia
Event: Mid-air collision between Douglas DC-3 (Survey) and Vultee BT-13 Valiant
Person: George Robert Cushing, 48 years old, 11,091 total flight hours
Status: Nine fatalities (all aboard both aircraft)

- The DC-3 named Survey was on final approach at ten forty, roughly ten feet above the runway, when struck from behind and above.
- The collision occurred after the Survey had completed one and a half left-hand traffic circuits following standard procedure.
- The BT-13 departed at ten thirty from Columbus Municipal Airport and had about 100 total flight hours.
- The DC-3 had accumulated 2,899 total flight hours and had two Pratt & Whitney R-1830-92 engines, each 1,200 horsepower.
- The Civil Aeronautics Board assigned responsibility to one individual and criticized the lack of a control tower at Muscogee County Airport.

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.]]>1111falsefullhttps://www.spreaker.com/episode/the-day-a-worn-jackscrew-turned-seattle-flight-261-deadly--73096934
A terrifying mechanical drift turned ordinary travel into disaster: the jackscrew that controlled Alaska Airlines Flight 261's horizontal stabilizer had been wearing at twelve times the expected rate for years, and a warning three years earlier had been overruled. Ninety seconds after the pilot asked for a few minutes to check control, the plane was upside down at seventeen thousand feet-how many times could this failure have been prevented?

In this episode, we follow the final flight and the lead-up in factual detail, outlining the crew, the aircraft, the maintenance history, and the decisions that set the stage for catastrophe. What chain of missed inspections, overruled warnings, and maintenance choices allowed a single steel rod to destroy a flight?

Date: January 31, 2000
Event: Alaska Airlines Flight 261 mechanical failure and crash
Aircraft: MD-83, registration N963AS
Jackscrew wear rate: twelve times expected rate
Flight hours on aircraft: 26,584 hours across 14,315 cycles

- Pilot Ted Thompson had 17,750 total flight hours, including more than 4,000 on the MD-80 series.
- First officer William "Bill" Tansky had 8,060 hours specifically on the MD-80.
- The jackscrew measured 22 inches long and 1.5 inches in diameter, threaded through a copper-alloy nut.
- At 15:37 PST the aircraft boarded in Puerto Vallarta and departed under routine conditions.
- Four minutes before 16:00 the captain was holding continuous ten pounds of force on the controls to keep the nose 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/73096934Thu, 13 Aug 2026 08:00:35 +0000Creator at ObomediaThe Day a Worn Jackscrew Turned Seattle Flight 261 Deadly A terrifying mechanical drift turned ordinary travel into disaster: the jackscrew that controlled Alaska Airlines Flight 261's horizontal stabilizer had been wearing at twelve times the...
A terrifying mechanical drift turned ordinary travel into disaster: the jackscrew that controlled Alaska Airlines Flight 261's horizontal stabilizer had been wearing at twelve times the expected rate for years, and a warning three years earlier had been overruled. Ninety seconds after the pilot asked for a few minutes to check control, the plane was upside down at seventeen thousand feet-how many times could this failure have been prevented?

In this episode, we follow the final flight and the lead-up in factual detail, outlining the crew, the aircraft, the maintenance history, and the decisions that set the stage for catastrophe. What chain of missed inspections, overruled warnings, and maintenance choices allowed a single steel rod to destroy a flight?

Date: January 31, 2000
Event: Alaska Airlines Flight 261 mechanical failure and crash
Aircraft: MD-83, registration N963AS
Jackscrew wear rate: twelve times expected rate
Flight hours on aircraft: 26,584 hours across 14,315 cycles

- Pilot Ted Thompson had 17,750 total flight hours, including more than 4,000 on the MD-80 series.
- First officer William "Bill" Tansky had 8,060 hours specifically on the MD-80.
- The jackscrew measured 22 inches long and 1.5 inches in diameter, threaded through a copper-alloy nut.
- At 15:37 PST the aircraft boarded in Puerto Vallarta and departed under routine conditions.
- Four minutes before 16:00 the captain was holding continuous ten pounds of force on the controls to keep the nose 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.]]>998falsefullhttps://www.spreaker.com/episode/how-a-cult-leader-s-private-plane-became-a-floating-coffin-over-tennessee--73096931
Fear of betrayal and the lure of absolute certainty: a movement that grew from mall meetings to 250,000 enrolled in 21,000 classes would collapse into an isolated church whose leader amassed multiple luxury cars and mansions - how did a diet program end in brain-dead children and a private plane turned coffin?

In this episode, we lay out the rise of a woman with a master’s in biochemistry who built a nationwide ministry, the doctrinal rupture that shrank her network, and the personal wealth and properties that followed; what happened next that turned faith into tragedy?

Person: Gwendolyn Kay Henley (Gwen Shamblin)
Event: Weigh Down Workshop expansion to 21,000 classes and 250,000 people
Date: October 8, 2003
Location: Franklin/Brentwood, Tennessee; initial origins in Memphis
Status: Remnant Fellowship founded 1999, major split after August 10, 2000 email

- Gwen earned a master's degree in nutrition and biochemistry from the University of Tennessee in Knoxville.
- By August 1998, 250,000 people were enrolled in 21,000 Weigh Down classes across states and countries.
- In 1997 Gwen published The Weigh Down Diet, which sold over 1.2 million copies.
- On August 10, 2000, Gwen sent an email declaring the Trinity unsupported by the Bible, triggering mass departures.
- On October 8, 2003, an eight-year-old boy named Josef Smith was found brain-dead after being inside a wicker box with electrical cables in Georgia.

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/73096931Wed, 12 Aug 2026 08:00:04 +0000Creator at ObomediaHow a Cult Leader's Private Plane Became a Floating Coffin over Tennessee Fear of betrayal and the lure of absolute certainty: a movement that grew from mall meetings to 250,000 enrolled in 21,000 classes would collapse into an isolated church...
Fear of betrayal and the lure of absolute certainty: a movement that grew from mall meetings to 250,000 enrolled in 21,000 classes would collapse into an isolated church whose leader amassed multiple luxury cars and mansions - how did a diet program end in brain-dead children and a private plane turned coffin?

In this episode, we lay out the rise of a woman with a master’s in biochemistry who built a nationwide ministry, the doctrinal rupture that shrank her network, and the personal wealth and properties that followed; what happened next that turned faith into tragedy?

Person: Gwendolyn Kay Henley (Gwen Shamblin)
Event: Weigh Down Workshop expansion to 21,000 classes and 250,000 people
Date: October 8, 2003
Location: Franklin/Brentwood, Tennessee; initial origins in Memphis
Status: Remnant Fellowship founded 1999, major split after August 10, 2000 email

- Gwen earned a master's degree in nutrition and biochemistry from the University of Tennessee in Knoxville.
- By August 1998, 250,000 people were enrolled in 21,000 Weigh Down classes across states and countries.
- In 1997 Gwen published The Weigh Down Diet, which sold over 1.2 million copies.
- On August 10, 2000, Gwen sent an email declaring the Trinity unsupported by the Bible, triggering mass departures.
- On October 8, 2003, an eight-year-old boy named Josef Smith was found brain-dead after being inside a wicker box with electrical cables in Georgia.

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.]]>979falsefullhttps://www.spreaker.com/episode/the-judge-who-chose-war-over-the-supreme-court-died-on-flight-6780--73096928
A sixty-year-old federal judge who once refused a Supreme Court seat and helped build the U.S. wartime military died on January 22, 1952, when American Airlines Flight 6780 crashed on approach to Newark - so what drove him from the bench into the Pentagon and then back into a routine client trip that ended his life?

In this episode, we tell the life and contradictions of Robert Porter Patterson Sr., covering his military decorations in World War I, two federal judicial appointments he resigned, his role as Under Secretary and Secretary of War during World War II, and the controversial policy decisions he signed; could the choices that defined his career explain the man who boarded Flight 6780?

Person: Robert Porter Patterson Sr.
Date of crash: January 22, 1952
Birth date: February 12, 1891
Military honors: Distinguished Service Cross and Silver Star
Flight: American Airlines Flight 6780, crashed on approach over Elizabeth, New Jersey

- Patterson resigned two federal judgeships, including the Second Circuit seat he accepted in March 1939, within sixteen months.
- He left the bench in 1940 to become Assistant Secretary of War and was Under Secretary and then Secretary of War through 1947.
- He was instrumental in creating the African-American fighter group trained at Tuskegee Institute during World War II.
- In April 1946 Patterson signed the Gillem Board report that recommended retaining racial segregation in the armed forces while calling for equal opportunity.
- He died at age 60 when American Airlines Flight 6780 went down on approach to Newark Airport on January 22, 1952.

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/73096928Tue, 11 Aug 2026 08:00:03 +0000Creator at ObomediaThe Judge Who Chose War Over the Supreme Court - Died on Flight 6780 A sixty-year-old federal judge who once refused a Supreme Court seat and helped build the U.S. wartime military died on January 22, 1952, when American Airlines Flight 6780...
A sixty-year-old federal judge who once refused a Supreme Court seat and helped build the U.S. wartime military died on January 22, 1952, when American Airlines Flight 6780 crashed on approach to Newark - so what drove him from the bench into the Pentagon and then back into a routine client trip that ended his life?

In this episode, we tell the life and contradictions of Robert Porter Patterson Sr., covering his military decorations in World War I, two federal judicial appointments he resigned, his role as Under Secretary and Secretary of War during World War II, and the controversial policy decisions he signed; could the choices that defined his career explain the man who boarded Flight 6780?

Person: Robert Porter Patterson Sr.
Date of crash: January 22, 1952
Birth date: February 12, 1891
Military honors: Distinguished Service Cross and Silver Star
Flight: American Airlines Flight 6780, crashed on approach over Elizabeth, New Jersey

- Patterson resigned two federal judgeships, including the Second Circuit seat he accepted in March 1939, within sixteen months.
- He left the bench in 1940 to become Assistant Secretary of War and was Under Secretary and then Secretary of War through 1947.
- He was instrumental in creating the African-American fighter group trained at Tuskegee Institute during World War II.
- In April 1946 Patterson signed the Gillem Board report that recommended retaining racial segregation in the armed forces while calling for equal opportunity.
- He died at age 60 when American Airlines Flight 6780 went down on approach to Newark Airport on January 22, 1952.

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.]]>1089falsefullhttps://www.spreaker.com/episode/mayor-ex-mlb-pitcher-plane-vanishes-near-culpeper-1958--73096925
A sitting mayor and former major-league pitcher vanished when his twin-engine plane went down near Culpeper, Virginia, in the summer of 1958 - he was 50 years old and traveling to Baltimore to watch a baseball game. The crash was ruled accidental and no cause was ever recorded; how did a man who built an airport terminal and whose name would later be given to it die without explanation?

In this episode, we tell the record of who William Fort McAfee Jr. was, what he built, and what remained unfinished after his death, asking whether the gaps in the official account leave a fuller story untold.

Person: William Fort McAfee Jr.
Event: Plane crash near Culpeper, Virginia
Date: Summer of 1958
Age: 50
Occupation: Mayor of Albany, Georgia

- McAfee was born September 7, 1907, in Smithville, Georgia.
- He made his MLB debut May 12, 1930, with the Chicago Cubs and faced ten batters in one inning across two appearances.
- In 1929 he traveled to Japan with a college baseball team and went 11-2 across 13 games.
- He served as the Senators' chief relief pitcher in 1933, throwing 61 2/3 innings with a 3-2 record.
- The airport terminal he helped fight for was named after him the year following the 1958 crash.

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/73096925Mon, 10 Aug 2026 08:00:06 +0000Creator at ObomediaMayor, Ex-MLB Pitcher: Plane Vanishes Near Culpeper, 1958 A sitting mayor and former major-league pitcher vanished when his twin-engine plane went down near Culpeper, Virginia, in the summer of 1958 - he was 50 years old and traveling to Baltimore...
A sitting mayor and former major-league pitcher vanished when his twin-engine plane went down near Culpeper, Virginia, in the summer of 1958 - he was 50 years old and traveling to Baltimore to watch a baseball game. The crash was ruled accidental and no cause was ever recorded; how did a man who built an airport terminal and whose name would later be given to it die without explanation?

In this episode, we tell the record of who William Fort McAfee Jr. was, what he built, and what remained unfinished after his death, asking whether the gaps in the official account leave a fuller story untold.

Person: William Fort McAfee Jr.
Event: Plane crash near Culpeper, Virginia
Date: Summer of 1958
Age: 50
Occupation: Mayor of Albany, Georgia

- McAfee was born September 7, 1907, in Smithville, Georgia.
- He made his MLB debut May 12, 1930, with the Chicago Cubs and faced ten batters in one inning across two appearances.
- In 1929 he traveled to Japan with a college baseball team and went 11-2 across 13 games.
- He served as the Senators' chief relief pitcher in 1933, throwing 61 2/3 innings with a 3-2 record.
- The airport terminal he helped fight for was named after him the year following the 1958 crash.

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.]]>992falsefullhttps://www.spreaker.com/episode/tail-number-repainted-how-alan-kulwicki-s-plane-stopped-flying--73096922
Danger can arrive in small, mechanical choices: a Swearingen Merlin III repainted from N300EF to N300AK crashed into a field beside Interstate 81 on April 1, 1993 - the reigning NASCAR champion and 38-year-old Alan Kulwicki did not survive. What single decision about the aircraft’s systems did investigators say allowed ice to build where it should not have, and how did that one omission end a life built on engineering precision?

In this episode, we tell the story of the plane, the pilot, and the champion whose initials the aircraft bore, covering the flight, the crash, and the factors that led to the National Transportation Safety Board’s finding that a left anti-ice system had not been activated. How did a man who trusted numbers above all else end up in a cockpit where a required action went unmade?

Person: Alan Kulwicki
Date: April 1, 1993
Location: Field beside Interstate 81 near Blountville, Tennessee
Age: 38
Cause: Engine inlet anti-ice system not activated (NTSB finding)

- Tail number repainted three months before the crash from N300EF to N300AK.
- Kulwicki won the 1992 NASCAR Winston Cup championship by a margin of ten points.
- Kulwicki held a Bachelor of Science in Mechanical Engineering from the University of Wisconsin-Milwaukee, class of 1977.
- The aircraft was a Swearingen Merlin III leased from Robert Brooks, chairman of Hooters, and flew in Hooters livery.
- At a January 1993 civic event, 4,000 to 5,000 people attended Alan Kulwicki Day where he spent six hours signing autographs.

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/73096922Sun, 09 Aug 2026 08:00:03 +0000Creator at ObomediaTail Number Repainted: How Alan Kulwicki's Plane Stopped Flying Danger can arrive in small, mechanical choices: a Swearingen Merlin III repainted from N300EF to N300AK crashed into a field beside Interstate 81 on April 1, 1993 - the reigning NASCAR...
Danger can arrive in small, mechanical choices: a Swearingen Merlin III repainted from N300EF to N300AK crashed into a field beside Interstate 81 on April 1, 1993 - the reigning NASCAR champion and 38-year-old Alan Kulwicki did not survive. What single decision about the aircraft’s systems did investigators say allowed ice to build where it should not have, and how did that one omission end a life built on engineering precision?

In this episode, we tell the story of the plane, the pilot, and the champion whose initials the aircraft bore, covering the flight, the crash, and the factors that led to the National Transportation Safety Board’s finding that a left anti-ice system had not been activated. How did a man who trusted numbers above all else end up in a cockpit where a required action went unmade?

Person: Alan Kulwicki
Date: April 1, 1993
Location: Field beside Interstate 81 near Blountville, Tennessee
Age: 38
Cause: Engine inlet anti-ice system not activated (NTSB finding)

- Tail number repainted three months before the crash from N300EF to N300AK.
- Kulwicki won the 1992 NASCAR Winston Cup championship by a margin of ten points.
- Kulwicki held a Bachelor of Science in Mechanical Engineering from the University of Wisconsin-Milwaukee, class of 1977.
- The aircraft was a Swearingen Merlin III leased from Robert Brooks, chairman of Hooters, and flew in Hooters livery.
- At a January 1993 civic event, 4,000 to 5,000 people attended Alan Kulwicki Day where he spent six hours signing autographs.

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.]]>952falsefullhttps://www.spreaker.com/episode/last-voices-of-flight-175-the-rear-seat-call-that-failed--73096920
Tension spiraled from a routine cross-country flight into a sealed, suffocating silence: at 8:52 AM on September 11, 2001, a 32-year-old passenger used a rear airphone to tell his father there were men on the plane with knives - then the line went quiet. Eight minutes later a second call came, 303 seconds before impact; what can those last documented voices and scattered airphone, radar and wreckage clues tell us about the final minutes of United Flight 175?

In this episode, we lay out the sequence of calls, the crew and passenger details, and the fragmentary communications that formed the investigators’ picture; we follow the airphone records, the ACARS message, and radar hints to ask how sixty people left Boston and never arrived.

Person: Peter Hanson
Date: September 11, 2001
Location: Boston to Los Angeles (flight departed Gate 19, Terminal C)
Event: Hijacking of United Airlines Flight 175
Aircraft: Boeing 767, registration N612UA

- Flight pushed back at 7:58 AM and lifted off Runway 9 at 8:14 AM.
- Load factor: 33%, sixty people on board including nine crew and three children under five.
- First rear-cabin call from Peter Hanson to his father lasted less than two minutes at 8:52 AM and reported men with knives.
- Flight attendant Robert Fangman called United maintenance at 8:52 AM for 1 minute 15 seconds, reporting pilots dead and a stabbing.
- An ACARS maintenance message reading "Plz verify all is normal" was sent with no reply.

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/73096920Sat, 08 Aug 2026 08:00:05 +0000Creator at ObomediaLast Voices of Flight 175: The Rear-Seat Call That Failed Tension spiraled from a routine cross-country flight into a sealed, suffocating silence: at 8:52 AM on September 11, 2001, a 32-year-old passenger used a rear airphone to tell his father...
Tension spiraled from a routine cross-country flight into a sealed, suffocating silence: at 8:52 AM on September 11, 2001, a 32-year-old passenger used a rear airphone to tell his father there were men on the plane with knives - then the line went quiet. Eight minutes later a second call came, 303 seconds before impact; what can those last documented voices and scattered airphone, radar and wreckage clues tell us about the final minutes of United Flight 175?

In this episode, we lay out the sequence of calls, the crew and passenger details, and the fragmentary communications that formed the investigators’ picture; we follow the airphone records, the ACARS message, and radar hints to ask how sixty people left Boston and never arrived.

Person: Peter Hanson
Date: September 11, 2001
Location: Boston to Los Angeles (flight departed Gate 19, Terminal C)
Event: Hijacking of United Airlines Flight 175
Aircraft: Boeing 767, registration N612UA

- Flight pushed back at 7:58 AM and lifted off Runway 9 at 8:14 AM.
- Load factor: 33%, sixty people on board including nine crew and three children under five.
- First rear-cabin call from Peter Hanson to his father lasted less than two minutes at 8:52 AM and reported men with knives.
- Flight attendant Robert Fangman called United maintenance at 8:52 AM for 1 minute 15 seconds, reporting pilots dead and a stabbing.
- An ACARS maintenance message reading "Plz verify all is normal" was sent with no reply.

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.]]>1135falsefullhttps://www.spreaker.com/episode/the-invisible-kill-how-a-wind-shear-turned-routine-landing-deadly--73096919
The calm of a routine descent hid an invisible menace: at 6:06:05 PM a Lockheed L-1011 crossed a Texas highway at rooftop level traveling over 200 miles per hour, and 137 people died in eight seconds - but a Learjet that passed the same storm three minutes earlier landed without a scratch. What was the storm hiding that the radar, pilots, and controllers could all see yet still could not predict?

In this episode, we tell the sequence of events leading up to Delta Air Lines Flight 191’s final seconds, the crew’s experience, and the puzzling contrast with the Learjet that landed safely, asking how established procedures and the technology of 1985 failed to reveal the hazard.

Person: Captain Edward Michael Connors Jr.
Person: First Officer Rudolph Przydzial Price Jr.
Person: Flight Engineer Nicholas Nestor Nassick
Aircraft: Lockheed L-1011-385-1 TriStar, tail N726DA
Event: Delta Air Lines Flight 191 crash, 137 fatalities

- The aircraft crossed a Texas highway at rooftop level traveling over 200 miles per hour at 6:06:05 PM.
- One hundred and thirty-seven people died within eight seconds after that moment.
- The crew had a combined total of more than 42,000 flight hours.
- The aircraft was delivered to Delta on February 28, 1979, and had three Rolls-Royce RB211 engines.
- A Learjet 25 flew through the same storm and landed three minutes earlier without incident.

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/73096919Fri, 07 Aug 2026 08:00:05 +0000Creator at ObomediaThe Invisible Kill: How a Wind Shear Turned Routine Landing Deadly The calm of a routine descent hid an invisible menace: at 6:06:05 PM a Lockheed L-1011 crossed a Texas highway at rooftop level traveling over 200 miles per hour, and 137 people...
The calm of a routine descent hid an invisible menace: at 6:06:05 PM a Lockheed L-1011 crossed a Texas highway at rooftop level traveling over 200 miles per hour, and 137 people died in eight seconds - but a Learjet that passed the same storm three minutes earlier landed without a scratch. What was the storm hiding that the radar, pilots, and controllers could all see yet still could not predict?

In this episode, we tell the sequence of events leading up to Delta Air Lines Flight 191’s final seconds, the crew’s experience, and the puzzling contrast with the Learjet that landed safely, asking how established procedures and the technology of 1985 failed to reveal the hazard.

Person: Captain Edward Michael Connors Jr.
Person: First Officer Rudolph Przydzial Price Jr.
Person: Flight Engineer Nicholas Nestor Nassick
Aircraft: Lockheed L-1011-385-1 TriStar, tail N726DA
Event: Delta Air Lines Flight 191 crash, 137 fatalities

- The aircraft crossed a Texas highway at rooftop level traveling over 200 miles per hour at 6:06:05 PM.
- One hundred and thirty-seven people died within eight seconds after that moment.
- The crew had a combined total of more than 42,000 flight hours.
- The aircraft was delivered to Delta on February 28, 1979, and had three Rolls-Royce RB211 engines.
- A Learjet 25 flew through the same storm and landed three minutes earlier without incident.

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.]]>1238falsefullhttps://www.spreaker.com/episode/survived-the-crash-died-133-days-later-officially-a-survivor--73096917
Fear and bureaucratic indifference collide in a case where a man pulled alive from a jetliner wreckage lived 133 days after the crash yet was still officially counted as a survivor - a rule written into federal law. How did an experienced crew, a well-maintained DC‑9 and an approach designed for the weather end with the aircraft striking a seawall 3,000 feet short of the runway?

In this episode, we lay out the sequence of events on July 31, 1973, from the flight crew and aircraft history to the air traffic controller’s distraction and the late clearance that altered the approach geometry, asking how small failures stacked until catastrophe became inevitable.

Person: Leopold Chouinard
Date: July 31, 1973
Event: Delta Air Lines Flight 723 struck seawall and disintegrated
Aircraft: McDonnell Douglas DC-9, registration N975NE
Location: Boston Logan International vicinity (165 feet off centerline, 3,000 feet short)

- Impact time: 11:08 AM on July 31, 1973.
- Fatalities on impact: 87 people died immediately.
- Survivors pulled from wreckage alive: 2 people.
- Survivor later died: Leopold Chouinard survived 133 days, died December 11, 1973.
- Aircraft distance from runway at impact: 3,000 feet short and 165 feet off the runway centerline.

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/73096917Thu, 06 Aug 2026 08:00:03 +0000Creator at ObomediaSurvived the Crash - Died 133 Days Later, Officially a Survivor Fear and bureaucratic indifference collide in a case where a man pulled alive from a jetliner wreckage lived 133 days after the crash yet was still officially counted as a survivor - a...
Fear and bureaucratic indifference collide in a case where a man pulled alive from a jetliner wreckage lived 133 days after the crash yet was still officially counted as a survivor - a rule written into federal law. How did an experienced crew, a well-maintained DC‑9 and an approach designed for the weather end with the aircraft striking a seawall 3,000 feet short of the runway?

In this episode, we lay out the sequence of events on July 31, 1973, from the flight crew and aircraft history to the air traffic controller’s distraction and the late clearance that altered the approach geometry, asking how small failures stacked until catastrophe became inevitable.

Person: Leopold Chouinard
Date: July 31, 1973
Event: Delta Air Lines Flight 723 struck seawall and disintegrated
Aircraft: McDonnell Douglas DC-9, registration N975NE
Location: Boston Logan International vicinity (165 feet off centerline, 3,000 feet short)

- Impact time: 11:08 AM on July 31, 1973.
- Fatalities on impact: 87 people died immediately.
- Survivors pulled from wreckage alive: 2 people.
- Survivor later died: Leopold Chouinard survived 133 days, died December 11, 1973.
- Aircraft distance from runway at impact: 3,000 feet short and 165 feet off the runway centerline.

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.]]>1018falsefullhttps://www.spreaker.com/episode/the-day-a-congressman-vanished-alaska-s-unfound-cessna-mystery--73096916
Fear of the unknown in the wild: a Cessna 310 carrying a sitting congressman and the House Majority Leader disappeared without a trace over Alaska’s most unforgiving terrain - and not a single piece of wreckage or one of the four men was ever found. How could a plane vanish after a 39-day multi-service search that produced nothing, and what role did a missing emergency locator transmitter play?

In this episode, we tell the story of that flight, the people aboard, the law about emergency beacons that had just taken effect five weeks earlier, and the massive search that found only absence - could one missing device be the reason nothing was recovered?

Date: October 16, 1972
Person: Nick Begich
Person: Hale Boggs
Person: Don Jonz
Event: 39-day multi-agency search

- Flight carried four men: Nick Begich, Hale Boggs, Russell Brown, and pilot Don Jonz.
- Alaska law requiring emergency locator transmitters took effect on September 6, 1972 - five weeks before the flight.
- Don Jonz’s portable transmitter was later found in a different aircraft in Fairbanks, approximately 300 miles away.
- Search lasted thirty-nine days and included the Coast Guard, Navy, Army, Air Force, Civil Air Patrol, and civilian volunteers.
- No wreckage, no personal belongings, and none of the four men were ever recovered.

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/73096916Wed, 05 Aug 2026 08:00:03 +0000Creator at ObomediaThe Day a Congressman Vanished: Alaska's Unfound Cessna Mystery Fear of the unknown in the wild: a Cessna 310 carrying a sitting congressman and the House Majority Leader disappeared without a trace over Alaska’s most unforgiving terrain - and not...
Fear of the unknown in the wild: a Cessna 310 carrying a sitting congressman and the House Majority Leader disappeared without a trace over Alaska’s most unforgiving terrain - and not a single piece of wreckage or one of the four men was ever found. How could a plane vanish after a 39-day multi-service search that produced nothing, and what role did a missing emergency locator transmitter play?

In this episode, we tell the story of that flight, the people aboard, the law about emergency beacons that had just taken effect five weeks earlier, and the massive search that found only absence - could one missing device be the reason nothing was recovered?

Date: October 16, 1972
Person: Nick Begich
Person: Hale Boggs
Person: Don Jonz
Event: 39-day multi-agency search

- Flight carried four men: Nick Begich, Hale Boggs, Russell Brown, and pilot Don Jonz.
- Alaska law requiring emergency locator transmitters took effect on September 6, 1972 - five weeks before the flight.
- Don Jonz’s portable transmitter was later found in a different aircraft in Fairbanks, approximately 300 miles away.
- Search lasted thirty-nine days and included the Coast Guard, Navy, Army, Air Force, Civil Air Patrol, and civilian volunteers.
- No wreckage, no personal belongings, and none of the four men were ever recovered.

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.]]>1035falsefullhttps://www.spreaker.com/episode/the-pilot-who-landed-a-burning-plane-then-went-back-inside--73096914
Fear of what happens next: a Boeing 707 and a Lockheed Constellation converged over Putnam County, New York on December 4, 1965, separated by exactly 1,000 feet until an optical illusion erased that margin and two airliners collided - who chose to re-enter a burning fuselage after landing, and why?

In this episode, we tell the sequence of events from departure to impact and the immediate aftermath, tracing the crews, aircraft types, and the cloud phenomenon that led to the disaster. What did the up-slope effect of cloud tops do to the Constellation crew's perception, and how did one captain's decision change the end of the story?

Date: December 4, 1965
Event: Midair collision near Carmel VORTAC, Putnam County, New York
Aircraft 1: Boeing 707, registration N-748TW, TWA Flight 42, assigned 11,000 ft
Aircraft 2: Lockheed L-1049C Super Constellation, registration N-6218C, Eastern Flight 853, assigned 10,000 ft
People aboard Boeing 707: 51 passengers, 4 flight attendants; Flight crew: Capt. Thomas Carroll (45), FO Leo Smith (42), FE Ernest Hall
People aboard Constellation: 49 passengers, 2 flight attendants; Flight crew: Capt. Charles White (42), FO Roger Holt Jr. (34), FE Emile Greenway (27)

- Separation between the two flights before collision was exactly 1,000 feet in altitude.
- TWA Flight 42's Boeing 707 had nearly 13,000 flight hours on the airframe and Capt. Carroll had nearly 19,000 total flight hours.
- Eastern Flight 853's Constellation airframe had nearly 33,000 flight hours and was twelve years old.
- The Constellation was assigned to fly at 10,000 ft and the Boeing 707 at 11,000 ft when both converged on the Carmel VORTAC.
- At approximately 2:45 PM, First Officer Roger Holt Jr. of Eastern shouted "Look out" seconds 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/73096914Tue, 04 Aug 2026 08:00:02 +0000Creator at ObomediaThe Pilot Who Landed a Burning Plane - Then Went Back Inside Fear of what happens next: a Boeing 707 and a Lockheed Constellation converged over Putnam County, New York on December 4, 1965, separated by exactly 1,000 feet until an optical illusion...
Fear of what happens next: a Boeing 707 and a Lockheed Constellation converged over Putnam County, New York on December 4, 1965, separated by exactly 1,000 feet until an optical illusion erased that margin and two airliners collided - who chose to re-enter a burning fuselage after landing, and why?

In this episode, we tell the sequence of events from departure to impact and the immediate aftermath, tracing the crews, aircraft types, and the cloud phenomenon that led to the disaster. What did the up-slope effect of cloud tops do to the Constellation crew's perception, and how did one captain's decision change the end of the story?

Date: December 4, 1965
Event: Midair collision near Carmel VORTAC, Putnam County, New York
Aircraft 1: Boeing 707, registration N-748TW, TWA Flight 42, assigned 11,000 ft
Aircraft 2: Lockheed L-1049C Super Constellation, registration N-6218C, Eastern Flight 853, assigned 10,000 ft
People aboard Boeing 707: 51 passengers, 4 flight attendants; Flight crew: Capt. Thomas Carroll (45), FO Leo Smith (42), FE Ernest Hall
People aboard Constellation: 49 passengers, 2 flight attendants; Flight crew: Capt. Charles White (42), FO Roger Holt Jr. (34), FE Emile Greenway (27)

- Separation between the two flights before collision was exactly 1,000 feet in altitude.
- TWA Flight 42's Boeing 707 had nearly 13,000 flight hours on the airframe and Capt. Carroll had nearly 19,000 total flight hours.
- Eastern Flight 853's Constellation airframe had nearly 33,000 flight hours and was twelve years old.
- The Constellation was assigned to fly at 10,000 ft and the Boeing 707 at 11,000 ft when both converged on the Carmel VORTAC.
- At approximately 2:45 PM, First Officer Roger Holt Jr. of Eastern shouted "Look out" seconds 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.]]>1128falsefullhttps://www.spreaker.com/episode/when-two-flew-at-the-same-altitude-the-atlantic-midair-collapse--73096912
At 15:03 UTC over the South Atlantic, two military transports from different nations reached 35,000 feet, then the C-141 crew asked for oxygen masks and flashlights - wreckage was only partly recovered days later. How did a single altitude violation, failing communications systems, and absent collision-avoidance gear turn into thirty-three deaths that no one on the ground could prevent?

In this episode, we tell what happened on September 13, 1997, between REACH 4201 and GAF 074, laying out the flight paths, the broken AFnet communications, and the institutional gaps that let two crews occupy the same flight level - and ask whether this was an accident or an avoidable chain of failures.

Person: Capt. Peter Vallejo, 34
Person: Capt. Jason Ramsey, 27
Person: Aircraft: C-141B Starlifter tail 65-9405 and Tupolev Tu-154M tail 11+02
Date: September 13, 1997
Location: South Atlantic, route between Windhoek and Ascension Island

- Time of incident: 15:03 UTC when requests for oxygen masks were made
- Total fatalities: 33 people aboard both aircraft
- REACH 4201 departure time: 14:11 UTC from Windhoek, Namibia
- GAF 074 departure from Niamey: 10:35 UTC, route to Windhoek then Cape Town
- Missing safety equipment: neither aircraft was equipped with TCAS despite known need and prior listing on C-141B Project Objective Memorandum

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/73096912Mon, 03 Aug 2026 08:00:03 +0000Creator at ObomediaWhen Two Flew at the Same Altitude: The Atlantic Midair Collapse At 15:03 UTC over the South Atlantic, two military transports from different nations reached 35,000 feet, then the C-141 crew asked for oxygen masks and flashlights - wreckage was...
At 15:03 UTC over the South Atlantic, two military transports from different nations reached 35,000 feet, then the C-141 crew asked for oxygen masks and flashlights - wreckage was only partly recovered days later. How did a single altitude violation, failing communications systems, and absent collision-avoidance gear turn into thirty-three deaths that no one on the ground could prevent?

In this episode, we tell what happened on September 13, 1997, between REACH 4201 and GAF 074, laying out the flight paths, the broken AFnet communications, and the institutional gaps that let two crews occupy the same flight level - and ask whether this was an accident or an avoidable chain of failures.

Person: Capt. Peter Vallejo, 34
Person: Capt. Jason Ramsey, 27
Person: Aircraft: C-141B Starlifter tail 65-9405 and Tupolev Tu-154M tail 11+02
Date: September 13, 1997
Location: South Atlantic, route between Windhoek and Ascension Island

- Time of incident: 15:03 UTC when requests for oxygen masks were made
- Total fatalities: 33 people aboard both aircraft
- REACH 4201 departure time: 14:11 UTC from Windhoek, Namibia
- GAF 074 departure from Niamey: 10:35 UTC, route to Windhoek then Cape Town
- Missing safety equipment: neither aircraft was equipped with TCAS despite known need and prior listing on C-141B Project Objective Memorandum

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.]]>1149falsefullhttps://www.spreaker.com/episode/when-twenty-six-became-thirteen-the-fire-that-fell-from-the-sky--73096911
A transatlantic passenger jet was consumed by a hidden factory mistake: thirteen tiny metal rollers had been installed where twenty-six were required, turning a four-year-old Ilyushin Il-62M into a time bomb. One book survived the fall into Kabaty Woods; 182 people did not - how did a manufacturing decision years earlier become a midair catastrophe?

In this episode, we tell what happened on LOT Polish Airlines Flight 5055 from departure to impact, the technical failure that started the fire, and the human traces left behind - including the single handwritten New Testament found in the wreckage. How did an internal bearing failure cascade into an uncontrollable in-flight fire and loss of control?

Person: Halina Domeracka
Event: LOT Polish Airlines Flight 5055 in-flight fire and crash
Date: May 9, 1987
Aircraft: Ilyushin Il-62M, registration SP-LBG, built 1983
Location: Kabaty Woods, outskirts of Warsaw

- 183 people were aboard Flight 5055; 182 bodies were recovered and one person remained missing.
- The aircraft carried 155 Polish citizens and 17 American passport holders.
- Engine number two failed nine minutes after takeoff at 8,200 meters altitude.
- Thirteen metal rollers were installed where twenty-six were designed to be, halving the bearing’s load capacity.
- The bearing overheated toward 1,000°C, the turbine disk exploded, fragments ruptured fuselage skin and opened a hole into cargo hold four.

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/73096911Sun, 02 Aug 2026 08:00:03 +0000Creator at ObomediaWhen Twenty-Six Became Thirteen: The Fire That Fell from the Sky A transatlantic passenger jet was consumed by a hidden factory mistake: thirteen tiny metal rollers had been installed where twenty-six were required, turning a four-year-old Ilyushin...
A transatlantic passenger jet was consumed by a hidden factory mistake: thirteen tiny metal rollers had been installed where twenty-six were required, turning a four-year-old Ilyushin Il-62M into a time bomb. One book survived the fall into Kabaty Woods; 182 people did not - how did a manufacturing decision years earlier become a midair catastrophe?

In this episode, we tell what happened on LOT Polish Airlines Flight 5055 from departure to impact, the technical failure that started the fire, and the human traces left behind - including the single handwritten New Testament found in the wreckage. How did an internal bearing failure cascade into an uncontrollable in-flight fire and loss of control?

Person: Halina Domeracka
Event: LOT Polish Airlines Flight 5055 in-flight fire and crash
Date: May 9, 1987
Aircraft: Ilyushin Il-62M, registration SP-LBG, built 1983
Location: Kabaty Woods, outskirts of Warsaw

- 183 people were aboard Flight 5055; 182 bodies were recovered and one person remained missing.
- The aircraft carried 155 Polish citizens and 17 American passport holders.
- Engine number two failed nine minutes after takeoff at 8,200 meters altitude.
- Thirteen metal rollers were installed where twenty-six were designed to be, halving the bearing’s load capacity.
- The bearing overheated toward 1,000°C, the turbine disk exploded, fragments ruptured fuselage skin and opened a hole into cargo hold four.

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.]]>1048falsefullhttps://www.spreaker.com/episode/sixty-four-seconds-why-pan-am-759-vanished-into-a-microburst--73096910
A sudden, violent wind shredded a routine takeoff and in sixty-four seconds Pan Am Flight 759 fell from about 95-150 feet and slammed into a Kenner neighborhood, killing 153 people. How could three pilots with a combined 37,758 flight hours and a mechanically sound Boeing 727 be powerless against a stormy afternoon-what crucial weather information never reached the crew?

In this episode, we tell the sequence of events from pushback to impact, describe the aircraft and crew credentials, and follow the moments on the ground in Kenner as thunderstorms built nearby. What happened in those final seconds, and why the crew could not have stopped it, is the central question driving the story.

Aircraft: Boeing 727
Date: July 9, 1982
Location: Kenner, Louisiana (about four miles from the runway threshold)
People aboard: 145 (137 passengers, 7 cabin crew, 1 non-revenue cockpit jumpseat)
Total fatalities: 153

- Takeoff roll began at 16:07:57 Central Daylight Time from Runway Ten.
- Aircraft reached between 95 and 150 feet above the ground before descending.
- Crew combined flight hours totaled 37,758 (Captain 11,727; First Officer 6,127; Flight Engineer 19,904).
- Aircraft had been in service since January 31, 1968 and was 14 years old at the time.
- Thunderstorms were building to the east and east-northeast of the airport by 16:00, with witnesses reporting gusty, swirling winds near 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/73096910Sat, 01 Aug 2026 08:00:03 +0000Creator at ObomediaSixty-Four Seconds: Why Pan Am 759 Vanished into a Microburst A sudden, violent wind shredded a routine takeoff and in sixty-four seconds Pan Am Flight 759 fell from about 95-150 feet and slammed into a Kenner neighborhood, killing 153 people. How...
A sudden, violent wind shredded a routine takeoff and in sixty-four seconds Pan Am Flight 759 fell from about 95-150 feet and slammed into a Kenner neighborhood, killing 153 people. How could three pilots with a combined 37,758 flight hours and a mechanically sound Boeing 727 be powerless against a stormy afternoon-what crucial weather information never reached the crew?

In this episode, we tell the sequence of events from pushback to impact, describe the aircraft and crew credentials, and follow the moments on the ground in Kenner as thunderstorms built nearby. What happened in those final seconds, and why the crew could not have stopped it, is the central question driving the story.

Aircraft: Boeing 727
Date: July 9, 1982
Location: Kenner, Louisiana (about four miles from the runway threshold)
People aboard: 145 (137 passengers, 7 cabin crew, 1 non-revenue cockpit jumpseat)
Total fatalities: 153

- Takeoff roll began at 16:07:57 Central Daylight Time from Runway Ten.
- Aircraft reached between 95 and 150 feet above the ground before descending.
- Crew combined flight hours totaled 37,758 (Captain 11,727; First Officer 6,127; Flight Engineer 19,904).
- Aircraft had been in service since January 31, 1968 and was 14 years old at the time.
- Thunderstorms were building to the east and east-northeast of the airport by 16:00, with witnesses reporting gusty, swirling winds near 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.]]>1017falsefullhttps://www.spreaker.com/episode/forty-nine-seconds-how-a-chain-of-small-decisions-killed-flight-1363--73096909
Fear that a single routine choice can become fatal: Flight 1363 was airborne for only forty-nine seconds before striking trees, killing twenty-four people, after a chain of small decisions beginning hours earlier. How did an experienced captain with 24,100 flight hours end up accepting a departure with an inoperative APU and snow on the wings-what single moment turned routine into catastrophe?

In this episode, you will hear a chronological account of the flight from Thunder Bay to Dryden and the choices made on the ground that led to the accident, including equipment status, runway conditions, and crew actions that set the final minutes in motion. What combination of practical pressures and procedural gaps made the obvious invisible?

Date: March 10, 1989
Event: Air Ontario Flight 1363 crash
Aircraft: Fokker F28-1000
Person: Captain George Morwood - 24,100 flight hours
Fatalities: 24

- Flight time airborne after takeoff: 49 seconds.
- Passengers aboard: 65; crew: 4.
- Captain George Morwood age: 52; with Air Ontario 34 years.
- First Officer Keith Mills age: 35; over 10,000 flight hours.
- Aircraft manufacture year: 1972; acquired by Air Ontario November 1987.

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/73096909Fri, 31 Jul 2026 08:00:02 +0000Creator at ObomediaForty-Nine Seconds: How a Chain of Small Decisions Killed Flight 1363 Fear that a single routine choice can become fatal: Flight 1363 was airborne for only forty-nine seconds before striking trees, killing twenty-four people, after a chain of small...
Fear that a single routine choice can become fatal: Flight 1363 was airborne for only forty-nine seconds before striking trees, killing twenty-four people, after a chain of small decisions beginning hours earlier. How did an experienced captain with 24,100 flight hours end up accepting a departure with an inoperative APU and snow on the wings-what single moment turned routine into catastrophe?

In this episode, you will hear a chronological account of the flight from Thunder Bay to Dryden and the choices made on the ground that led to the accident, including equipment status, runway conditions, and crew actions that set the final minutes in motion. What combination of practical pressures and procedural gaps made the obvious invisible?

Date: March 10, 1989
Event: Air Ontario Flight 1363 crash
Aircraft: Fokker F28-1000
Person: Captain George Morwood - 24,100 flight hours
Fatalities: 24

- Flight time airborne after takeoff: 49 seconds.
- Passengers aboard: 65; crew: 4.
- Captain George Morwood age: 52; with Air Ontario 34 years.
- First Officer Keith Mills age: 35; over 10,000 flight hours.
- Aircraft manufacture year: 1972; acquired by Air Ontario November 1987.

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.]]>1088falsefullhttps://www.spreaker.com/episode/the-menu-card-fourteen-signatures-and-eight-never-returned--73096908
A preserved menu card from a Belgrade hotel dinner lists fourteen signatures - eight of those men never came home after the Munich air disaster. Why did a runway decision, a written warning, and three attempted takeoffs end with twenty-three dead and a generation of talent lost?

In this episode, we tell who these players were, what happened on the Riem Airport runway that afternoon, and why one engineer's written recommendation was ignored - could those eight men have been saved?

Person: Duncan Edwards
Person: Roger Byrne
Person: Person: Tommy Taylor
Person: Person: Liam (Billy) Whelan
Event: Munich air disaster
Date: 6 February 1958

- Fourteen men signed the Majestic Hotel menu on the night of 5 February 1958.
- Eight of those signatories never returned home after the crash on 6 February 1958.
- The aircraft was an Elizabethan-class airliner, registration G-ALZU, named Lord Burghley.
- The flight had stopped to refuel at Riem Airport with forty-four people aboard.
- There were three take-off attempts that day, with two aborted before the third attempt that ended in disaster.

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/73096908Thu, 30 Jul 2026 08:00:02 +0000Creator at ObomediaThe Menu Card, Fourteen Signatures-and Eight Never Returned A preserved menu card from a Belgrade hotel dinner lists fourteen signatures - eight of those men never came home after the Munich air disaster. Why did a runway decision, a written...
A preserved menu card from a Belgrade hotel dinner lists fourteen signatures - eight of those men never came home after the Munich air disaster. Why did a runway decision, a written warning, and three attempted takeoffs end with twenty-three dead and a generation of talent lost?

In this episode, we tell who these players were, what happened on the Riem Airport runway that afternoon, and why one engineer's written recommendation was ignored - could those eight men have been saved?

Person: Duncan Edwards
Person: Roger Byrne
Person: Person: Tommy Taylor
Person: Person: Liam (Billy) Whelan
Event: Munich air disaster
Date: 6 February 1958

- Fourteen men signed the Majestic Hotel menu on the night of 5 February 1958.
- Eight of those signatories never returned home after the crash on 6 February 1958.
- The aircraft was an Elizabethan-class airliner, registration G-ALZU, named Lord Burghley.
- The flight had stopped to refuel at Riem Airport with forty-four people aboard.
- There were three take-off attempts that day, with two aborted before the third attempt that ended in disaster.

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.]]>1165falsefullhttps://www.spreaker.com/episode/three-broken-watches-forty-five-dead-the-night-i-lake-hit-somma--73096904
Averaging three stopped wristwatches gave investigators the official time of death for all forty-five victims - but those three clocks disagreed with each other. A perfectly functioning Vickers Viscount struck the northern face of Mount Somma with engines running and experienced pilots aboard; how did terrain arrive before anyone expected it?

In this episode, we present the sequence of events, crew background, passenger identities, aircraft details and the weather information received before impact, and ask how a routine one-hundred-mile hop from Rome to Naples ended in Controlled Flight Into Terrain.

Date: March 28, 1964
Aircraft: Vickers Viscount 785D, registration I-LAKE
Passengers and crew: 45 dead, 0 survivors
Delay: 45 minutes departure delay in Rome due to oil temperature indicator replacement
Weather report at 22:28: visibility 6 kilometers, winds 180-210° at 12 knots, clouds at 2,000-7,000 feet

- The aircraft’s first flight was on August 18, 1957, and it was delivered to Alitalia on October 1, 1957.
- Wheels-up for the Rome-Naples leg occurred at 22:10 after a 45-minute delay from the scheduled 21:25.
- Contact with Naples approach control occurred at 22:28, less than 20 minutes after takeoff.
- Captain Pasquale Umana was 53 years old; First Officer Italo Billau was 32; third pilot Giuseppe Camponi was 28.
- Among the passengers were Major Lawrence Mancini (38) with wife Fay (38), daughter Jill (11) and son Steven (8), and Antoine Henry Azan (27) with son Ubert (3).

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/73096904Wed, 29 Jul 2026 08:00:02 +0000Creator at ObomediaThree Broken Watches, Forty-Five Dead: The Night I-LAKE Hit Somma Averaging three stopped wristwatches gave investigators the official time of death for all forty-five victims - but those three clocks disagreed with each other. A perfectly...
Averaging three stopped wristwatches gave investigators the official time of death for all forty-five victims - but those three clocks disagreed with each other. A perfectly functioning Vickers Viscount struck the northern face of Mount Somma with engines running and experienced pilots aboard; how did terrain arrive before anyone expected it?

In this episode, we present the sequence of events, crew background, passenger identities, aircraft details and the weather information received before impact, and ask how a routine one-hundred-mile hop from Rome to Naples ended in Controlled Flight Into Terrain.

Date: March 28, 1964
Aircraft: Vickers Viscount 785D, registration I-LAKE
Passengers and crew: 45 dead, 0 survivors
Delay: 45 minutes departure delay in Rome due to oil temperature indicator replacement
Weather report at 22:28: visibility 6 kilometers, winds 180-210° at 12 knots, clouds at 2,000-7,000 feet

- The aircraft’s first flight was on August 18, 1957, and it was delivered to Alitalia on October 1, 1957.
- Wheels-up for the Rome-Naples leg occurred at 22:10 after a 45-minute delay from the scheduled 21:25.
- Contact with Naples approach control occurred at 22:28, less than 20 minutes after takeoff.
- Captain Pasquale Umana was 53 years old; First Officer Italo Billau was 32; third pilot Giuseppe Camponi was 28.
- Among the passengers were Major Lawrence Mancini (38) with wife Fay (38), daughter Jill (11) and son Steven (8), and Antoine Henry Azan (27) with son Ubert (3).

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.]]>1064falsefullhttps://www.spreaker.com/episode/the-prime-minister-the-perfect-plane-and-the-silent-crash-at-jordan-s-wood--73096903
A sudden blanket of fog swallowed the approach to Gatwick and a nearly new Vickers Viscount hit trees 2.8 nautical miles short of the runway, killing 14 of 24 aboard - including Turkey's Prime Minister - in a crash with no mechanical faults and no distress call. How did reports that visibility was "one to five feet" become the reality of fog reaching 650-700 feet, and what gap between information and sky doomed TC-SEV?

In this episode, we tell the sequence of events from departure to impact, outline who was on board and what the crew were told about weather, and follow the official investigation's inability to explain why the aircraft struck trees that afternoon. Could the mismatch between reported visibility and actual conditions be the key to the unanswered question?

Date: February 17, 1959
Aircraft: Vickers Viscount Type 793, serial number 429
Flight: TC-SEV, Rome to London (diverted to Gatwick)
Fatalities: 14 of 24 aboard
Accident location: Jordan's Wood, 2.8 nautical miles south of Gatwick

- Departure time from Rome: 13:02
- Crossed Abbeville and called London Area Control by 15:56
- Diverted to Gatwick at 16:21 due to Heathrow closure for fog
- Left the Epsom beacon at 16:27 on ILS approach to Runway 08R at 6,000 feet
- Reported fog depth to crew: 1-5 feet versus actual fog reaching 650-700 feet

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/73096903Tue, 28 Jul 2026 08:00:24 +0000Creator at ObomediaThe Prime Minister, the Perfect Plane, and the Silent Crash at Jordan's Wood A sudden blanket of fog swallowed the approach to Gatwick and a nearly new Vickers Viscount hit trees 2.8 nautical miles short of the runway, killing 14 of 24 aboard -...
A sudden blanket of fog swallowed the approach to Gatwick and a nearly new Vickers Viscount hit trees 2.8 nautical miles short of the runway, killing 14 of 24 aboard - including Turkey's Prime Minister - in a crash with no mechanical faults and no distress call. How did reports that visibility was "one to five feet" become the reality of fog reaching 650-700 feet, and what gap between information and sky doomed TC-SEV?

In this episode, we tell the sequence of events from departure to impact, outline who was on board and what the crew were told about weather, and follow the official investigation's inability to explain why the aircraft struck trees that afternoon. Could the mismatch between reported visibility and actual conditions be the key to the unanswered question?

Date: February 17, 1959
Aircraft: Vickers Viscount Type 793, serial number 429
Flight: TC-SEV, Rome to London (diverted to Gatwick)
Fatalities: 14 of 24 aboard
Accident location: Jordan's Wood, 2.8 nautical miles south of Gatwick

- Departure time from Rome: 13:02
- Crossed Abbeville and called London Area Control by 15:56
- Diverted to Gatwick at 16:21 due to Heathrow closure for fog
- Left the Epsom beacon at 16:27 on ILS approach to Runway 08R at 6,000 feet
- Reported fog depth to crew: 1-5 feet versus actual fog reaching 650-700 feet

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1110falsefullhttps://www.spreaker.com/episode/silence-before-impact-how-flight-5601-vanished-into-mount-puntang--73096901
A brand-new CN-235 smashed into Mount Puntang at 420 km/h with no distress call and every radar and radio contact dropping simultaneously-31 people died and the last radio was just 16 minutes before impact; how did a captain with over 6,000 flight hours end up 21 degrees off course into a mountain she could not see?

In this episode, we tell the sequence of events from takeoff to wreckage, describe the crew and aircraft, and follow the official investigation that recovered both flight recorders and mapped the deviation-what exactly caused that fatal course change?

Person: Captain Fierda Basaria Panggabean
Person: First Officer Adnan S. Paago
Date: 18 October 1992
Aircraft: CN-235 serial number N.013
Event: Impact with Mount Puntang at 420 km/h

- Flight departed Semarang at 13:05 under clear skies.
- At 13:35 the airplane contacted Bandung approach at 12,500 feet and was told visibility ahead was 4-5 km.
- The crew requested and received a switch from instrument flight rules to visual flight rules.
- Sixteen minutes elapsed between the last radio call and impact.
- The aircraft drifted 21 degrees off course and descended through cloud into mountainous terrain.

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/73096901Mon, 27 Jul 2026 08:00:03 +0000Creator at ObomediaSilence Before Impact: How Flight 5601 Vanished into Mount Puntang A brand-new CN-235 smashed into Mount Puntang at 420 km/h with no distress call and every radar and radio contact dropping simultaneously-31 people died and the last radio was just...
A brand-new CN-235 smashed into Mount Puntang at 420 km/h with no distress call and every radar and radio contact dropping simultaneously-31 people died and the last radio was just 16 minutes before impact; how did a captain with over 6,000 flight hours end up 21 degrees off course into a mountain she could not see?

In this episode, we tell the sequence of events from takeoff to wreckage, describe the crew and aircraft, and follow the official investigation that recovered both flight recorders and mapped the deviation-what exactly caused that fatal course change?

Person: Captain Fierda Basaria Panggabean
Person: First Officer Adnan S. Paago
Date: 18 October 1992
Aircraft: CN-235 serial number N.013
Event: Impact with Mount Puntang at 420 km/h

- Flight departed Semarang at 13:05 under clear skies.
- At 13:35 the airplane contacted Bandung approach at 12,500 feet and was told visibility ahead was 4-5 km.
- The crew requested and received a switch from instrument flight rules to visual flight rules.
- Sixteen minutes elapsed between the last radio call and impact.
- The aircraft drifted 21 degrees off course and descended through cloud into mountainous terrain.

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.]]>996falsefullhttps://www.spreaker.com/episode/they-thought-they-were-at-11-500-feet-christmas-eve-crash-mystery--73096898
Fear of being inches from death in plain daylight: a Bristol Britannia 312 on a routine test flight descended believing it had 11,500 feet beneath it when it actually had 1,500 - a ten-thousand-foot error that left nine dead and snapped telegraph poles like matchsticks. How could two trained crew, working instruments that functioned correctly, misread a single dial with such catastrophic consequences?

In this episode, we tell the story of that Christmas Eve flight and the chain of ordinary events - fog, a diversion to Hurn, a routine airworthiness check flight from Heathrow - that combined into disaster; we follow the wreckage trail across Burley Road and the questions investigators had to answer: what led a functioning aircraft and professional crew to collide with the ground?

Person: Nine fatalities on board
Date: 24 December 1958
Aircraft: Bristol Britannia 312, registration G-AOVD
Departure: Heathrow Airport at 10:10
Clearance: Descend from 12,000 ft to 3,000 ft toward Hurn

- The crew were cleared to descend from 12,000 feet to 3,000 feet but the aircraft was actually at 1,500 feet when descent began.
- Visibility was reduced by a dense, low maritime fog across southern England, making fog visually indistinguishable from cloud from above.
- The flight was a non-revenue airworthiness renewal test flight with twelve people aboard (seven in the cabin, five crew).
- Telegraph poles along Burley Road were snapped at the base, their wires dragged across the frozen ground marking the wreckage path.
- G-AOVD lifted off from Heathrow at 10:10 and contact with Hurn was noted at 11:58; three minutes later there was no further contact.

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/73096898Sun, 26 Jul 2026 08:00:03 +0000Creator at ObomediaThey Thought They Were at 11,500 Feet - Christmas Eve Crash Mystery Fear of being inches from death in plain daylight: a Bristol Britannia 312 on a routine test flight descended believing it had 11,500 feet beneath it when it actually had 1,500 - a...
Fear of being inches from death in plain daylight: a Bristol Britannia 312 on a routine test flight descended believing it had 11,500 feet beneath it when it actually had 1,500 - a ten-thousand-foot error that left nine dead and snapped telegraph poles like matchsticks. How could two trained crew, working instruments that functioned correctly, misread a single dial with such catastrophic consequences?

In this episode, we tell the story of that Christmas Eve flight and the chain of ordinary events - fog, a diversion to Hurn, a routine airworthiness check flight from Heathrow - that combined into disaster; we follow the wreckage trail across Burley Road and the questions investigators had to answer: what led a functioning aircraft and professional crew to collide with the ground?

Person: Nine fatalities on board
Date: 24 December 1958
Aircraft: Bristol Britannia 312, registration G-AOVD
Departure: Heathrow Airport at 10:10
Clearance: Descend from 12,000 ft to 3,000 ft toward Hurn

- The crew were cleared to descend from 12,000 feet to 3,000 feet but the aircraft was actually at 1,500 feet when descent began.
- Visibility was reduced by a dense, low maritime fog across southern England, making fog visually indistinguishable from cloud from above.
- The flight was a non-revenue airworthiness renewal test flight with twelve people aboard (seven in the cabin, five crew).
- Telegraph poles along Burley Road were snapped at the base, their wires dragged across the frozen ground marking the wreckage path.
- G-AOVD lifted off from Heathrow at 10:10 and contact with Hurn was noted at 11:58; three minutes later there was no further contact.

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.]]>1016falsefullhttps://www.spreaker.com/episode/concrete-berm-silent-black-box-how-179-could-ve-lived--73096896
A morning landing turned into a funeral: a Boeing 737 slid on its belly for hundreds of meters at Muan, South Korea, hit a four-meter concrete berm and scattered wreckage across 300 meters - all 179 people on board were confirmed dead. A government simulation thirteen months later concluded every single person could have survived if that berm had not stood in the way - so why was a known hazard still there?

In this episode, we outline the moments before, during and after Jeju Air Flight 2216's final approach and the chain of operational gaps tied to the runway and airport. We trace the flight's timeline from takeoff in Bangkok through the simultaneous loss of both recorders and the failed landing that met a concrete berm - could different airport decisions have changed the outcome?

Person: Captain with 6,820 total flight hours and 6,096 on the 737
Person: First officer with 1,650 total flight hours
Date: December 29, 2024
Location: Muan International Airport, South Korea
Event: Both cockpit voice recorder and flight data recorder stopped at 08:58:50

- 54 seconds: length of rooftop footage showing the 737 sliding on its belly
- 4 meters: height of the concrete berm at the end of the runway
- 300 meters: distance over which wreckage scattered across scorched ground
- 179: number of people on board and later confirmed dead
- 13 months: time until a government simulation concluded all could have survived without the berm

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/73096896Sat, 25 Jul 2026 08:00:02 +0000Creator at ObomediaConcrete Berm, Silent Black Box: How 179 Could've Lived A morning landing turned into a funeral: a Boeing 737 slid on its belly for hundreds of meters at Muan, South Korea, hit a four-meter concrete berm and scattered wreckage across 300 meters -...
A morning landing turned into a funeral: a Boeing 737 slid on its belly for hundreds of meters at Muan, South Korea, hit a four-meter concrete berm and scattered wreckage across 300 meters - all 179 people on board were confirmed dead. A government simulation thirteen months later concluded every single person could have survived if that berm had not stood in the way - so why was a known hazard still there?

In this episode, we outline the moments before, during and after Jeju Air Flight 2216's final approach and the chain of operational gaps tied to the runway and airport. We trace the flight's timeline from takeoff in Bangkok through the simultaneous loss of both recorders and the failed landing that met a concrete berm - could different airport decisions have changed the outcome?

Person: Captain with 6,820 total flight hours and 6,096 on the 737
Person: First officer with 1,650 total flight hours
Date: December 29, 2024
Location: Muan International Airport, South Korea
Event: Both cockpit voice recorder and flight data recorder stopped at 08:58:50

- 54 seconds: length of rooftop footage showing the 737 sliding on its belly
- 4 meters: height of the concrete berm at the end of the runway
- 300 meters: distance over which wreckage scattered across scorched ground
- 179: number of people on board and later confirmed dead
- 13 months: time until a government simulation concluded all could have survived without the berm

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.]]>1163falsefullhttps://www.spreaker.com/episode/cash-intact-passengers-gone-the-dorothy-hunt-midway-mystery--73096892
An envelope with $10,000 in hundred-dollar bills survived the impact intact while the woman carrying it, Dorothy Hunt, did not - a single, strange detail that sparked Watergate rumors within days. Why did a functioning stick shaker scream for six seconds before the Boeing 737 hit trees one minute and forty seconds from Midway, and what did a broken flight data recorder and intact cash really mean?

In this episode, we tell what happened on United Air Lines Flight 553 on December 8, 1972, how the final approach unfolded, and why a technical investigation and immediate conspiracy claims ran side by side; could the cockpit discussion about a known broken recorder and a faulty instrument explain those last six seconds?

Date: December 8, 1972
Aircraft: Boeing 737-222, registration N9031U
Flight: United Air Lines Flight 553
Fatalities: 45 aboard died (43 remained in the neighborhood; two more died on the ground)
Notable passengers: Dorothy Hunt (age 52), Michele Clark (age 33), Congressman George W. Collins

- The stick shaker activated and vibrated controls for six full seconds before impact.
- The flight was one minute and forty seconds from Midway Airport at 14:27 when events culminated.
- The flight data recorder was nonfunctional before departure and was discussed by the crew during the flight.
- The cockpit voice recorder was recovered and captured the crew conversation; the flight data recorder recorded nothing.
- Investigators found a sealed envelope with $10,000 in hundred-dollar bills among Dorothy Hunt’s personal effects, the cash intact.

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/73096892Fri, 24 Jul 2026 08:00:05 +0000Creator at ObomediaCash Intact, Passengers Gone: The Dorothy Hunt Midway Mystery An envelope with $10,000 in hundred-dollar bills survived the impact intact while the woman carrying it, Dorothy Hunt, did not - a single, strange detail that sparked Watergate rumors...
An envelope with $10,000 in hundred-dollar bills survived the impact intact while the woman carrying it, Dorothy Hunt, did not - a single, strange detail that sparked Watergate rumors within days. Why did a functioning stick shaker scream for six seconds before the Boeing 737 hit trees one minute and forty seconds from Midway, and what did a broken flight data recorder and intact cash really mean?

In this episode, we tell what happened on United Air Lines Flight 553 on December 8, 1972, how the final approach unfolded, and why a technical investigation and immediate conspiracy claims ran side by side; could the cockpit discussion about a known broken recorder and a faulty instrument explain those last six seconds?

Date: December 8, 1972
Aircraft: Boeing 737-222, registration N9031U
Flight: United Air Lines Flight 553
Fatalities: 45 aboard died (43 remained in the neighborhood; two more died on the ground)
Notable passengers: Dorothy Hunt (age 52), Michele Clark (age 33), Congressman George W. Collins

- The stick shaker activated and vibrated controls for six full seconds before impact.
- The flight was one minute and forty seconds from Midway Airport at 14:27 when events culminated.
- The flight data recorder was nonfunctional before departure and was discussed by the crew during the flight.
- The cockpit voice recorder was recovered and captured the crew conversation; the flight data recorder recorded nothing.
- Investigators found a sealed envelope with $10,000 in hundred-dollar bills among Dorothy Hunt’s personal effects, the cash intact.

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.]]>1115falsefullhttps://www.spreaker.com/episode/they-turned-off-the-alert-how-flight-197-flew-into-a-mountain--73096891
The chill fact: a functioning aircraft with running engines and a living crew flew straight into a mountain with its terrain warning system disabled - three separate times - and the cockpit voice recorder preserved every word. How did a twin-engine Twin Otter, built for these valleys, end up at 14,500 feet in snowfall with no mechanical failure to blame?

In this episode, we lay out the sequence of departures, weather reports, crew decisions and the moment-by-moment cockpit audio that led to the crash, and we ask how a system designed to prevent controlled flight into terrain ended up turned off before the aircraft ever left the ground.

Person: Pilot in command, age 62
Date: 29 May 2022
Location: Pokhara to Jomsom, Mustang corridor, Nepal
Aircraft: De Havilland Canada Twin Otter, registration 9N-AET
Fatal site elevation: 14,500 feet

- Flight departed Pokhara with 22 people on board (19 passengers, 1 flight attendant, 2 pilots).
- Aircraft maiden flight was 21 April 1979, making the airframe 43 years old at time of crash.
- Jomsom Airport elevation is approximately 8,900 feet and the route duration is about 20 minutes.
- Another aircraft (9N-AKZ) reported adverse weather at waypoints Lete and Tatopani before Flight 197 departed.
- The wreckage was reached nearly 20 hours after the crash, with the flight recorder surviving and preserving cockpit audio.

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/73096891Thu, 23 Jul 2026 08:00:02 +0000Creator at ObomediaThey Turned Off the Alert: How Flight 197 Flew Into A Mountain The chill fact: a functioning aircraft with running engines and a living crew flew straight into a mountain with its terrain warning system disabled - three separate times - and the...
The chill fact: a functioning aircraft with running engines and a living crew flew straight into a mountain with its terrain warning system disabled - three separate times - and the cockpit voice recorder preserved every word. How did a twin-engine Twin Otter, built for these valleys, end up at 14,500 feet in snowfall with no mechanical failure to blame?

In this episode, we lay out the sequence of departures, weather reports, crew decisions and the moment-by-moment cockpit audio that led to the crash, and we ask how a system designed to prevent controlled flight into terrain ended up turned off before the aircraft ever left the ground.

Person: Pilot in command, age 62
Date: 29 May 2022
Location: Pokhara to Jomsom, Mustang corridor, Nepal
Aircraft: De Havilland Canada Twin Otter, registration 9N-AET
Fatal site elevation: 14,500 feet

- Flight departed Pokhara with 22 people on board (19 passengers, 1 flight attendant, 2 pilots).
- Aircraft maiden flight was 21 April 1979, making the airframe 43 years old at time of crash.
- Jomsom Airport elevation is approximately 8,900 feet and the route duration is about 20 minutes.
- Another aircraft (9N-AKZ) reported adverse weather at waypoints Lete and Tatopani before Flight 197 departed.
- The wreckage was reached nearly 20 hours after the crash, with the flight recorder surviving and preserving cockpit audio.

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.]]>1102falsefullhttps://www.spreaker.com/episode/thirty-two-seconds-ice-on-the-wings-a-known-danger-nobody-told-the-crew--73096888
Fear that routine nights can hide fatal surprises: a cargo DC-9 airborne for only thirty-two seconds in freezing drizzle, with documented wing sensitivity to ice that the crew never knew about - how did an industry warning go unanswered and a known hazard reach the runway? What exactly happened in those thirty-two seconds?

In this episode, we tell the flight’s timeline, the weather and aircraft facts, the crew background, and the regulatory context that left a two-man crew unaware of a specific aerodynamic danger - could a thin, nearly invisible glaze on the wings explain everything?

Date: February 17, 1988
Aircraft: Douglas DC-9 Series 10
Flight: Ryan International Airlines Flight 590
Location: Cleveland Hopkins International Airport
Condition: Freezing drizzle, ambient ~23°F

- Time airborne from liftoff to cockpit voice recorder silence: 32 seconds
- Aircraft age at accident: 22 years in commercial service
- First officer tenure at airline: 20 days employed by Ryan International
- Weather temperature reported: approximately 23 degrees Fahrenheit
- Deicing action taken: engine anti-ice activated; no wing deicing and no tactile wing inspection performed

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/73096888Wed, 22 Jul 2026 08:00:03 +0000Creator at ObomediaThirty-two seconds. Ice on the wings. A known danger nobody told the crew Fear that routine nights can hide fatal surprises: a cargo DC-9 airborne for only thirty-two seconds in freezing drizzle, with documented wing sensitivity to ice that the...
Fear that routine nights can hide fatal surprises: a cargo DC-9 airborne for only thirty-two seconds in freezing drizzle, with documented wing sensitivity to ice that the crew never knew about - how did an industry warning go unanswered and a known hazard reach the runway? What exactly happened in those thirty-two seconds?

In this episode, we tell the flight’s timeline, the weather and aircraft facts, the crew background, and the regulatory context that left a two-man crew unaware of a specific aerodynamic danger - could a thin, nearly invisible glaze on the wings explain everything?

Date: February 17, 1988
Aircraft: Douglas DC-9 Series 10
Flight: Ryan International Airlines Flight 590
Location: Cleveland Hopkins International Airport
Condition: Freezing drizzle, ambient ~23°F

- Time airborne from liftoff to cockpit voice recorder silence: 32 seconds
- Aircraft age at accident: 22 years in commercial service
- First officer tenure at airline: 20 days employed by Ryan International
- Weather temperature reported: approximately 23 degrees Fahrenheit
- Deicing action taken: engine anti-ice activated; no wing deicing and no tactile wing inspection performed

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.]]>1042falsefullhttps://www.spreaker.com/episode/two-experienced-pilots-trained-for-exactly-this-emergency-and-it-still-wasn-t-enough--73096885
The lightning strike that hit D-CABB killed every instrument and both recorders in one instant, sending a six-year-old Metroliner III into a chaotic descent over the Ruhr River; the aircraft had about 9,200 flight hours and carried 21 people when it broke apart. How could two pilots with over 2,500 hours each and simulator training for electrical failure lose control when redundancy met regulation?

In this episode, we tell the sequence of events from pushback at Hannover through the last radio transmission and the sudden total electrical failure, laying out what the crew knew, what the aircraft carried, and the weather that closed in - and ask whether the rules and equipment in force that morning were enough to protect the flight.

Person: Ralf Borsdorf
Person: Sibylle Heilmann
Event: lightning strike causing total electrical failure
Date: 8 February 1988
Aircraft: Swearingen SA-227AC Metroliner III, registration D-CABB

- Both pilots had more than 2,500 total flight hours: Borsdorf ~2,500 and Heilmann over 2,500.
- Heilmann logged more than 1,300 hours specifically on the Metroliner III.
- D-CABB had accumulated approximately 9,200 flight hours across six years of service.
- There were 21 people on board: two pilots and nineteen passengers.
- The aircraft did not carry an emergency power source because West German regulations did not require one for this class in 1988.

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/73096885Wed, 22 Jul 2026 01:12:18 +0000Creator at ObomediaTwo experienced pilots, trained for exactly this emergency - and it still wasn't enough The lightning strike that hit D-CABB killed every instrument and both recorders in one instant, sending a six-year-old Metroliner III into a chaotic descent...
The lightning strike that hit D-CABB killed every instrument and both recorders in one instant, sending a six-year-old Metroliner III into a chaotic descent over the Ruhr River; the aircraft had about 9,200 flight hours and carried 21 people when it broke apart. How could two pilots with over 2,500 hours each and simulator training for electrical failure lose control when redundancy met regulation?

In this episode, we tell the sequence of events from pushback at Hannover through the last radio transmission and the sudden total electrical failure, laying out what the crew knew, what the aircraft carried, and the weather that closed in - and ask whether the rules and equipment in force that morning were enough to protect the flight.

Person: Ralf Borsdorf
Person: Sibylle Heilmann
Event: lightning strike causing total electrical failure
Date: 8 February 1988
Aircraft: Swearingen SA-227AC Metroliner III, registration D-CABB

- Both pilots had more than 2,500 total flight hours: Borsdorf ~2,500 and Heilmann over 2,500.
- Heilmann logged more than 1,300 hours specifically on the Metroliner III.
- D-CABB had accumulated approximately 9,200 flight hours across six years of service.
- There were 21 people on board: two pilots and nineteen passengers.
- The aircraft did not carry an emergency power source because West German regulations did not require one for this class in 1988.

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-day-a-hockey-team-vanished-inside-yaroslavl-s-runway-tragedy--73096882
A sudden, inexplicable failure to climb turned a routine takeoff into a scene of wreckage stretched across two kilometers - and a metal antenna mast stood unmoved amid the fire. Forty-four people aboard a Yakovlev Yak-42D, including veteran NHL players and the club’s new head coach, died when the aircraft never cleared the tree line; what single chain of decisions let a functioning plane fail in just 400 meters?

In this episode, you will hear how the flight unfolded from Tunoshna Airport and what investigators ultimately found in documents, medications, and crew actions that made the crash possible. How did a full-power takeoff at 230 km/h still leave the aircraft on the ground until it hit trees and a riverbank?

Date: 7 September 2011
Location: Tunoshna Airport, Yaroslavl, Russia
Aircraft: Yakovlev Yak-42D, registration RA-42434
People aboard: 45 (44 on the fatal flight)
Airline: YAK-Service

- Runway length available from the crew’s taxi position: 2,700 meters
- Speed on runway end before lift: 230 kilometers per hour
- Distance the wreckage was scattered across: 2 kilometers
- Distance rolled past runway end before nose lifted: 400 meters
- Aircraft manufacture year: 1993

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/73096882Wed, 22 Jul 2026 01:12:07 +0000Creator at ObomediaThe Day a Hockey Team Vanished: Inside Yaroslavl's Runway Tragedy A sudden, inexplicable failure to climb turned a routine takeoff into a scene of wreckage stretched across two kilometers - and a metal antenna mast stood unmoved amid the fire....
A sudden, inexplicable failure to climb turned a routine takeoff into a scene of wreckage stretched across two kilometers - and a metal antenna mast stood unmoved amid the fire. Forty-four people aboard a Yakovlev Yak-42D, including veteran NHL players and the club’s new head coach, died when the aircraft never cleared the tree line; what single chain of decisions let a functioning plane fail in just 400 meters?

In this episode, you will hear how the flight unfolded from Tunoshna Airport and what investigators ultimately found in documents, medications, and crew actions that made the crash possible. How did a full-power takeoff at 230 km/h still leave the aircraft on the ground until it hit trees and a riverbank?

Date: 7 September 2011
Location: Tunoshna Airport, Yaroslavl, Russia
Aircraft: Yakovlev Yak-42D, registration RA-42434
People aboard: 45 (44 on the fatal flight)
Airline: YAK-Service

- Runway length available from the crew’s taxi position: 2,700 meters
- Speed on runway end before lift: 230 kilometers per hour
- Distance the wreckage was scattered across: 2 kilometers
- Distance rolled past runway end before nose lifted: 400 meters
- Aircraft manufacture year: 1993

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.]]>1087falsefullhttps://www.spreaker.com/episode/when-a-plane-hit-a-cotton-truck-55-killed-by-seven-years-neglect--73096879
A routine takeoff turned into a catastrophe when a Boeing 737 struck a cotton-laden truck crossing an aerodrome boundary with a missing gate - the collision killed 55 people in seconds and the unsafe condition had existed for seven years. How did cockpit technique, three conflicting weight figures, and a removed gate combine to make this disaster possible?

In this episode, you will hear the facts about the flight, the airport, the crew, and the road that crossed the runway perimeter - and follow the central question: which of these failures caused the crash and how were they allowed to persist?

Event: Indian Airlines Flight IC 149 collision on 26 April 1993
Aircraft: Boeing 737, registration VT-EAH, 43,887 flight hours, 18 years in service
People: 141 on board including crew; 55 fatalities from the collision
Crew: Captain Satendra Kumar Singh, 51 years old, >15,000 flight hours; First Officer S.K. Mohan, 38 years old
Airport: Aurangabad Airport; gate removed in 1986 leaving road crossing aerodrome perimeter for 7 years

- The collision occurred on 26 April 1993 at Aurangabad Airport when a rolling Boeing 737 struck a truck loaded with cotton bales on a road crossing the aerodrome boundary.
- Fifty-five people were killed as a result of the impact that happened during takeoff seconds after the aircraft began its roll.
- First Officer S.K. Mohan later estimated the aircraft was overloaded by approximately 4.5 metric tons at departure.
- Investigators' independent calculation found the aircraft was overweight by approximately 118 kilograms when it left the gate.
- The aerodrome gate at the road crossing had been removed in 1986 and was not replaced for seven years, allowing vehicles to cross close to 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/73096879Wed, 22 Jul 2026 01:11:55 +0000Creator at ObomediaWhen a Plane Hit a Cotton Truck: 55 Killed by Seven Years' Neglect A routine takeoff turned into a catastrophe when a Boeing 737 struck a cotton-laden truck crossing an aerodrome boundary with a missing gate - the collision killed 55 people in...
A routine takeoff turned into a catastrophe when a Boeing 737 struck a cotton-laden truck crossing an aerodrome boundary with a missing gate - the collision killed 55 people in seconds and the unsafe condition had existed for seven years. How did cockpit technique, three conflicting weight figures, and a removed gate combine to make this disaster possible?

In this episode, you will hear the facts about the flight, the airport, the crew, and the road that crossed the runway perimeter - and follow the central question: which of these failures caused the crash and how were they allowed to persist?

Event: Indian Airlines Flight IC 149 collision on 26 April 1993
Aircraft: Boeing 737, registration VT-EAH, 43,887 flight hours, 18 years in service
People: 141 on board including crew; 55 fatalities from the collision
Crew: Captain Satendra Kumar Singh, 51 years old, >15,000 flight hours; First Officer S.K. Mohan, 38 years old
Airport: Aurangabad Airport; gate removed in 1986 leaving road crossing aerodrome perimeter for 7 years

- The collision occurred on 26 April 1993 at Aurangabad Airport when a rolling Boeing 737 struck a truck loaded with cotton bales on a road crossing the aerodrome boundary.
- Fifty-five people were killed as a result of the impact that happened during takeoff seconds after the aircraft began its roll.
- First Officer S.K. Mohan later estimated the aircraft was overloaded by approximately 4.5 metric tons at departure.
- Investigators' independent calculation found the aircraft was overweight by approximately 118 kilograms when it left the gate.
- The aerodrome gate at the road crossing had been removed in 1986 and was not replaced for seven years, allowing vehicles to cross close to 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.]]>1129falsefullhttps://www.spreaker.com/episode/seventeen-feet-how-fedex-flight-14-turned-fatal-in-a-second--73096878
Fear of the last instant - at seventeen feet above Newark’s runway a well-known MD-11 freighter named Joshua was flying normally, and one second later it was inverted and burning on the grass. The aircraft had 13,034 flight hours, the left engine thrust reverser was inoperative, and 1,100 feet of runway separated the first touchdown from the point the airplane was no longer salvageable - so what single second changed everything?

In this episode, we tell the factual sequence of Flight 14’s final approach, the aircraft history and cockpit decisions that preceded the flare, and the investigation that followed; we close on the unresolved technical interaction that would only be clarified after a similar MD-11 accident twelve years later. How did crew planning and known equipment issues combine in that critical moment?

Aircraft: McDonnell Douglas MD-11 freighter
Registration: N611FE
Name: Joshua
Date: July 31, 1997
Flight hours: 13,034

- The airplane had accumulated 13,034 flight hours across 2,950 cycles at the time of the accident.
- The left engine thrust reverser was inoperative before the Newark landing.
- Captain Robert M. Freeman had 11,000+ total flight hours and 1,253 hours on the MD-11.
- First Officer Donald E. Goodin had 3,703 total hours and 95 hours on the MD-11.
- Eleven hundred feet of concrete separated the first touchdown from the moment the airplane became unsalvageable.

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/73096878Wed, 22 Jul 2026 01:11:43 +0000Creator at ObomediaSeventeen Feet: How FedEx Flight 14 Turned Fatal in a Second Fear of the last instant - at seventeen feet above Newark’s runway a well-known MD-11 freighter named Joshua was flying normally, and one second later it was inverted and burning on the...
Fear of the last instant - at seventeen feet above Newark’s runway a well-known MD-11 freighter named Joshua was flying normally, and one second later it was inverted and burning on the grass. The aircraft had 13,034 flight hours, the left engine thrust reverser was inoperative, and 1,100 feet of runway separated the first touchdown from the point the airplane was no longer salvageable - so what single second changed everything?

In this episode, we tell the factual sequence of Flight 14’s final approach, the aircraft history and cockpit decisions that preceded the flare, and the investigation that followed; we close on the unresolved technical interaction that would only be clarified after a similar MD-11 accident twelve years later. How did crew planning and known equipment issues combine in that critical moment?

Aircraft: McDonnell Douglas MD-11 freighter
Registration: N611FE
Name: Joshua
Date: July 31, 1997
Flight hours: 13,034

- The airplane had accumulated 13,034 flight hours across 2,950 cycles at the time of the accident.
- The left engine thrust reverser was inoperative before the Newark landing.
- Captain Robert M. Freeman had 11,000+ total flight hours and 1,253 hours on the MD-11.
- First Officer Donald E. Goodin had 3,703 total hours and 95 hours on the MD-11.
- Eleven hundred feet of concrete separated the first touchdown from the moment the airplane became unsalvageable.

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.]]>1108falsefullhttps://www.spreaker.com/episode/they-taxied-onto-the-dark-runway-49-dead-1-survivor--73096875
The most chilling fact: the crew noticed the runway was dark and still accelerated to 137 knots toward a strip 243 feet too short for liftoff. How did two experienced pilots, with decades of flying time between them, line up on an unlit, unauthorized runway and begin a takeoff that would kill 49 people before sunrise?

In this episode, we lay out the sequence of events from gate to impact, the recorded cockpit exchanges, and the investigation findings that measured the 243-foot shortfall - and ask what the crew, the controller, and the airport missed that morning.

Date: August 27, 2006
Aircraft: Bombardier CRJ100ER (serial number 7472)
Passengers: 47 (total aboard 50)
Captain Hours: 4,710 total, 3,082 on type
Takeoff Speed: 137 knots

- Runway available for commercial use (Runway 22) length: 7,003 feet
- Wrong runway used (Runway 26) length: 3,501 feet
- Calculated shortfall between required and available runway: 243 feet
- Fatalities: 49; Survivors: 1
- Captain age: 35; First Officer age: 44

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/73096875Wed, 22 Jul 2026 01:11:31 +0000Creator at ObomediaThey Taxied Onto the Dark Runway - 49 Dead, 1 Survivor The most chilling fact: the crew noticed the runway was dark and still accelerated to 137 knots toward a strip 243 feet too short for liftoff. How did two experienced pilots, with decades of...
The most chilling fact: the crew noticed the runway was dark and still accelerated to 137 knots toward a strip 243 feet too short for liftoff. How did two experienced pilots, with decades of flying time between them, line up on an unlit, unauthorized runway and begin a takeoff that would kill 49 people before sunrise?

In this episode, we lay out the sequence of events from gate to impact, the recorded cockpit exchanges, and the investigation findings that measured the 243-foot shortfall - and ask what the crew, the controller, and the airport missed that morning.

Date: August 27, 2006
Aircraft: Bombardier CRJ100ER (serial number 7472)
Passengers: 47 (total aboard 50)
Captain Hours: 4,710 total, 3,082 on type
Takeoff Speed: 137 knots

- Runway available for commercial use (Runway 22) length: 7,003 feet
- Wrong runway used (Runway 26) length: 3,501 feet
- Calculated shortfall between required and available runway: 243 feet
- Fatalities: 49; Survivors: 1
- Captain age: 35; First Officer age: 44

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.]]>1089falsefullhttps://www.spreaker.com/episode/the-word-they-never-said-how-avianca-052-ran-out-of-time--73096871
Panic and resignation hovered over Long Island that night as a four-engine Boeing 707 became a powerless glider twenty miles short of the runway after all four engines failed; the crew had loaded over 78,000 pounds of fuel yet fuel exhaustion still killed 73 passengers and 8 crew - what single word in the cockpit could have changed everything?

In this episode, you will hear the timeline of Avianca Flight 052 from departure in Medellín to the fatal descent over Cove Neck, the crew profiles, the aircraft details, the series of holding patterns and the unanswered radio question that sealed the outcome - how did fuel planning, holding delays and cockpit decisions converge to leave no time to save the flight?

Person: Captain Laureano Caviedes Hoyos, age 51, 27 years with Avianca, 16,000+ flight hours, 1,500+ hours in the 707
Person: First Officer Mauricio Klotz, age 28, 3 years with Avianca, 1,800 total hours, 64 hours in the 707 (13 at night)
Person: Flight Engineer Matías Moyano, age 45, 23 years with Avianca, 10,000+ hours, 3,000+ hours in the 707
Event: All four engines flamed out between 21:32 and 21:33 on January 25, 1990, 20 miles short of runway
Aircraft: Boeing 707-321B HK-2016, built June 1967, 61,000+ flight hours across 22 years

- Fuel loaded at departure: ordered 78,000+ pounds, with an added 2,000 pounds for a runway change
- Number on board: 158 people (149 passengers, 9 crew)
- Fatalities: 65 passengers and 8 crew (73 total passengers not surviving is stated; transcript also says 65 passengers died)
- Holding times: first hold 19 minutes (Norfolk), second hold 29 minutes (BOTON), third hold 29 minutes (CAMRN)
- Engine modifications and effects: hush kits increased fuel consumption by ~5%; aircraft age added an estimated additional ~5% burn rate

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/73096871Wed, 22 Jul 2026 01:11:19 +0000Creator at ObomediaThe Word They Never Said: How Avianca 052 Ran Out of Time Panic and resignation hovered over Long Island that night as a four-engine Boeing 707 became a powerless glider twenty miles short of the runway after all four engines failed; the crew had...
Panic and resignation hovered over Long Island that night as a four-engine Boeing 707 became a powerless glider twenty miles short of the runway after all four engines failed; the crew had loaded over 78,000 pounds of fuel yet fuel exhaustion still killed 73 passengers and 8 crew - what single word in the cockpit could have changed everything?

In this episode, you will hear the timeline of Avianca Flight 052 from departure in Medellín to the fatal descent over Cove Neck, the crew profiles, the aircraft details, the series of holding patterns and the unanswered radio question that sealed the outcome - how did fuel planning, holding delays and cockpit decisions converge to leave no time to save the flight?

Person: Captain Laureano Caviedes Hoyos, age 51, 27 years with Avianca, 16,000+ flight hours, 1,500+ hours in the 707
Person: First Officer Mauricio Klotz, age 28, 3 years with Avianca, 1,800 total hours, 64 hours in the 707 (13 at night)
Person: Flight Engineer Matías Moyano, age 45, 23 years with Avianca, 10,000+ hours, 3,000+ hours in the 707
Event: All four engines flamed out between 21:32 and 21:33 on January 25, 1990, 20 miles short of runway
Aircraft: Boeing 707-321B HK-2016, built June 1967, 61,000+ flight hours across 22 years

- Fuel loaded at departure: ordered 78,000+ pounds, with an added 2,000 pounds for a runway change
- Number on board: 158 people (149 passengers, 9 crew)
- Fatalities: 65 passengers and 8 crew (73 total passengers not surviving is stated; transcript also says 65 passengers died)
- Holding times: first hold 19 minutes (Norfolk), second hold 29 minutes (BOTON), third hold 29 minutes (CAMRN)
- Engine modifications and effects: hush kits increased fuel consumption by ~5%; aircraft age added an estimated additional ~5% burn rate

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.]]>1056falsefullhttps://www.spreaker.com/episode/silence-in-the-cockpit-how-pride-sent-airblue-202-into-hills--73096860
A commercial Airbus A321 flew as low as a four‑story building before disappearing into the Margalla Hills, killing 152 people; the aircraft was mechanically sound, other crews had turned away in the monsoon, and the first officer-an ex‑F‑16 pilot-said nothing while the captain steered a made‑up approach. What allowed a trained pilot to be silenced as the plane flew into terrain?

In this episode, we describe the flight, the cockpit dynamic, and the final minutes recorded on the cockpit voice recorder to understand how actions, not failures, led to the crash. How did a rigid hierarchy and a nonstandard flight path override safety procedures and end in disaster?

Date: July 28, 2010
Aircraft: Airbus A321, registration AP‑BJB
Flight: Airblue Flight 202
Fatalities: 152
Departure/Route: Karachi to Islamabad, two‑hour scheduled flight

- Aircraft age: built in 2000 with over 34,000 flight hours logged
- Occupants: 146 passengers and 6 crew, including five children and two infants
- Captain experience: Pervez‑Iqbal Chaudhry, 61 years old, 25,497 total flight hours
- First officer experience: Muntajib‑ud‑Din Ahmed, 34 years old, 1,837 total flight hours, 286 on A320 family
- Last contact/time: lost contact at 09:41, exactly two hours after takeoff

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/73096860Wed, 22 Jul 2026 01:11:07 +0000Creator at ObomediaSilence in the Cockpit: How Pride Sent Airblue 202 into Hills A commercial Airbus A321 flew as low as a four‑story building before disappearing into the Margalla Hills, killing 152 people; the aircraft was mechanically sound, other crews had turned...
A commercial Airbus A321 flew as low as a four‑story building before disappearing into the Margalla Hills, killing 152 people; the aircraft was mechanically sound, other crews had turned away in the monsoon, and the first officer-an ex‑F‑16 pilot-said nothing while the captain steered a made‑up approach. What allowed a trained pilot to be silenced as the plane flew into terrain?

In this episode, we describe the flight, the cockpit dynamic, and the final minutes recorded on the cockpit voice recorder to understand how actions, not failures, led to the crash. How did a rigid hierarchy and a nonstandard flight path override safety procedures and end in disaster?

Date: July 28, 2010
Aircraft: Airbus A321, registration AP‑BJB
Flight: Airblue Flight 202
Fatalities: 152
Departure/Route: Karachi to Islamabad, two‑hour scheduled flight

- Aircraft age: built in 2000 with over 34,000 flight hours logged
- Occupants: 146 passengers and 6 crew, including five children and two infants
- Captain experience: Pervez‑Iqbal Chaudhry, 61 years old, 25,497 total flight hours
- First officer experience: Muntajib‑ud‑Din Ahmed, 34 years old, 1,837 total flight hours, 286 on A320 family
- Last contact/time: lost contact at 09:41, exactly two hours after takeoff

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.]]>953falsefullhttps://www.spreaker.com/episode/when-a-missing-transponder-turned-daylight-into-disaster--73096857
The morning was clear and a private Piper without a Mode C transponder climbed into the same sky as a fully crewed Aeroméxico DC-9; eighty-two people would die when the two aircraft collided over Cerritos. How did a legal equipment gap and a distracted controller allow a blip with no altitude to vanish into a descent path and destroy four houses in seconds?

In this episode, we present the sequence of events, the aircraft and people involved, and the regulatory context that allowed an untransponded airplane to enter protected airspace - and we ask what that gap meant for the victims and the rules that followed.

Date: August 31, 1986
Event: Midair collision over Cerritos, California
Aircraft 1: Aeroméxico DC-9-32, registration XA-JED, 64 people on board (58 passengers, 6 crew)
Aircraft 2: Piper PA-28 Cherokee, registration N4891F, 3 people on board (William, Kathleen, Caroline Kramer)
Fatalities: 82

- 11:52 AM: swing sets at Cerritos Elementary were empty because 15 local residents had died in the crash.
- Aeroméxico Flight 498 had 10 children among its 58 passengers and had been in service since April 1969.
- The DC-9 (named Hermosillo) was 17 years in service and entered Aeroméxico fleet in November 1979.
- Private pilot William Kramer had 231 total flight hours and took off from Torrance Airport around 11:40 AM.
- The collision lasted less than one second and destroyed four houses and damaged seven more.

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/73096857Wed, 22 Jul 2026 01:10:54 +0000Creator at ObomediaWhen a Missing Transponder Turned Daylight Into Disaster The morning was clear and a private Piper without a Mode C transponder climbed into the same sky as a fully crewed Aeroméxico DC-9; eighty-two people would die when the two aircraft collided...
The morning was clear and a private Piper without a Mode C transponder climbed into the same sky as a fully crewed Aeroméxico DC-9; eighty-two people would die when the two aircraft collided over Cerritos. How did a legal equipment gap and a distracted controller allow a blip with no altitude to vanish into a descent path and destroy four houses in seconds?

In this episode, we present the sequence of events, the aircraft and people involved, and the regulatory context that allowed an untransponded airplane to enter protected airspace - and we ask what that gap meant for the victims and the rules that followed.

Date: August 31, 1986
Event: Midair collision over Cerritos, California
Aircraft 1: Aeroméxico DC-9-32, registration XA-JED, 64 people on board (58 passengers, 6 crew)
Aircraft 2: Piper PA-28 Cherokee, registration N4891F, 3 people on board (William, Kathleen, Caroline Kramer)
Fatalities: 82

- 11:52 AM: swing sets at Cerritos Elementary were empty because 15 local residents had died in the crash.
- Aeroméxico Flight 498 had 10 children among its 58 passengers and had been in service since April 1969.
- The DC-9 (named Hermosillo) was 17 years in service and entered Aeroméxico fleet in November 1979.
- Private pilot William Kramer had 231 total flight hours and took off from Torrance Airport around 11:40 AM.
- The collision lasted less than one second and destroyed four houses and damaged seven more.

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.]]>1052falsefullhttps://www.spreaker.com/episode/the-poet-who-flew-into-fog-xu-zhimo-s-fatal-jinan-flight--73096854
Fog hid a railway and a poet’s last minutes: Xu Zhimo, one of China’s most celebrated poets, boarded a mail plane without a ticket and died when the Stinson Detroiter Jinan flew into a mountain on November 19, 1931-why did a mail plane with a free passenger fly straight into a mountain in broad daylight?

In this episode, we tell the sequence of events that led to the crash, from Xu’s Cambridge-influenced fame and his decision to rearrange plans to hear Lin Huiyin speak, to the flight crew’s choices in thick Shandong fog; what drove Xu to accept that risky courtesy passage and what critical cockpit decision turned routine navigation into disaster?

Person: Xu Zhimo
Date: November 19, 1931
Aircraft: Stinson Detroiter SM-1F named Jinan
Crew: Captain Wang Guanyi (36) and First Officer Liang Bitang (36)
Cargo: 500 pounds of postal mail

- Xu Zhimo was 34 years old when he died on the flight.
- The flight departed Ming Gugong Airport in Nanjing at about 8:00 AM and stopped at Xu Zhimo at roughly 10:00 AM for a ten-minute refueling.
- The Jinan was a private aircraft of General Zhang Xueliang operated by China Airways Federal under contract with Chunghwa Post.
- After the railway landmark disappeared in fog, Captain Wang left the cockpit to sit beside Xu, leaving First Officer Liang alone at the controls.
- Xu Zhimo had no ticket and was riding as a free, courtesy passenger on a mail run carrying 500 pounds of postal cargo.

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/73096854Wed, 22 Jul 2026 01:10:43 +0000Creator at ObomediaThe Poet Who Flew Into Fog: Xu Zhimo's Fatal Jinan Flight Fog hid a railway and a poet’s last minutes: Xu Zhimo, one of China’s most celebrated poets, boarded a mail plane without a ticket and died when the Stinson Detroiter Jinan flew into a...
Fog hid a railway and a poet’s last minutes: Xu Zhimo, one of China’s most celebrated poets, boarded a mail plane without a ticket and died when the Stinson Detroiter Jinan flew into a mountain on November 19, 1931-why did a mail plane with a free passenger fly straight into a mountain in broad daylight?

In this episode, we tell the sequence of events that led to the crash, from Xu’s Cambridge-influenced fame and his decision to rearrange plans to hear Lin Huiyin speak, to the flight crew’s choices in thick Shandong fog; what drove Xu to accept that risky courtesy passage and what critical cockpit decision turned routine navigation into disaster?

Person: Xu Zhimo
Date: November 19, 1931
Aircraft: Stinson Detroiter SM-1F named Jinan
Crew: Captain Wang Guanyi (36) and First Officer Liang Bitang (36)
Cargo: 500 pounds of postal mail

- Xu Zhimo was 34 years old when he died on the flight.
- The flight departed Ming Gugong Airport in Nanjing at about 8:00 AM and stopped at Xu Zhimo at roughly 10:00 AM for a ten-minute refueling.
- The Jinan was a private aircraft of General Zhang Xueliang operated by China Airways Federal under contract with Chunghwa Post.
- After the railway landmark disappeared in fog, Captain Wang left the cockpit to sit beside Xu, leaving First Officer Liang alone at the controls.
- Xu Zhimo had no ticket and was riding as a free, courtesy passenger on a mail run carrying 500 pounds of postal cargo.

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.]]>1035falsefullhttps://www.spreaker.com/episode/the-nut-that-grounded-88-souls-alaska-flight-261-s-fatal-wear--73096853
A single metal nut wore down to almost nothing over years, and 88 people boarded a jet whose stabilizer thread had lost roughly 90% of its material. How did routine maintenance miss the Acme nut's catastrophic wear until it was too late?

In this episode, we tell the story of Alaska Flight Flight 261 from departure to disaster, following the pilots, crew, passengers, aircraft details, and the worn jackscrew component that failed-what decisions in maintenance logs and inspections allowed that thread to vanish?

Person: Captain Ted Thompson, age 53, 17,750 total flight hours, over 4,000 on MD-80
Person: First Officer William Tansky, age 57, 8,060 hours on MD-80
Event: Crash into Pacific Ocean 2.5 miles north of Anacapa Island on January 31, 2000
Aircraft: McDonnell Douglas MD-83, registration N963AS, entered service 1992
Status: 88 people on board, zero survivors

- Flight 261 struck the ocean at 4:21 PM on January 31, 2000, two and a half miles north of Anacapa Island.
- The aircraft had 26,584 flight hours and 14,315 pressurization cycles by the accident date.
- The jackscrew was 22 inches long and 1.5 inches across; its Acme nut had about 10% of its thread remaining.
- Over 35 passengers were employees or had connections to Alaska Flight, with 12 flying on employee discounts.
- In September 1999, four months before the crash, a San Francisco maintenance team lubricated the jackscrew assembly.

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/73096853Wed, 22 Jul 2026 01:10:31 +0000Creator at ObomediaThe Nut That Grounded 88 Souls: Alaska Flight 261's Fatal Wear A single metal nut wore down to almost nothing over years, and 88 people boarded a jet whose stabilizer thread had lost roughly 90% of its material. How did routine maintenance miss the...
A single metal nut wore down to almost nothing over years, and 88 people boarded a jet whose stabilizer thread had lost roughly 90% of its material. How did routine maintenance miss the Acme nut's catastrophic wear until it was too late?

In this episode, we tell the story of Alaska Flight Flight 261 from departure to disaster, following the pilots, crew, passengers, aircraft details, and the worn jackscrew component that failed-what decisions in maintenance logs and inspections allowed that thread to vanish?

Person: Captain Ted Thompson, age 53, 17,750 total flight hours, over 4,000 on MD-80
Person: First Officer William Tansky, age 57, 8,060 hours on MD-80
Event: Crash into Pacific Ocean 2.5 miles north of Anacapa Island on January 31, 2000
Aircraft: McDonnell Douglas MD-83, registration N963AS, entered service 1992
Status: 88 people on board, zero survivors

- Flight 261 struck the ocean at 4:21 PM on January 31, 2000, two and a half miles north of Anacapa Island.
- The aircraft had 26,584 flight hours and 14,315 pressurization cycles by the accident date.
- The jackscrew was 22 inches long and 1.5 inches across; its Acme nut had about 10% of its thread remaining.
- Over 35 passengers were employees or had connections to Alaska Flight, with 12 flying on employee discounts.
- In September 1999, four months before the crash, a San Francisco maintenance team lubricated the jackscrew assembly.

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.]]>1138falsefullhttps://www.spreaker.com/episode/the-heir-the-miss-universe-and-a-night-the-sky-collapsed--73096851
Fear of a private life that's never explained: a hotel heir who wrote a six-page pamphlet on communism, rose to national prominence at 25, and 43 years later died in a private plane crash near Burbank-how do those convulsive public moments connect to the silence he kept? What did G. David Schine know and why did he never answer?

In this episode, we tell the life events laid out in the record: his upbringing in a hotel empire, the 1952 pamphlet that led him to Roy Cohn and McCarthy's subcommittee, his 1957 marriage to Miss Universe Hillevi Rombin, and the 1996 crash that killed him, his wife, and their son. How do these episodes link into the unresolved question at the center of his life?

Person: Gerard David Schine
Date of birth: September 11, 1927
Event: Private plane crash near Burbank, California
Date of crash: June 19, 1996
Spouse: Hillevi Rombin (married October 22, 1957)

- The pamphlet "Definition of Communism" was six pages long and was distributed to every room in every Schine family hotel.
- Schine was 24 when he wrote the pamphlet in 1952 and 25 when he became chief consultant to Senator McCarthy's subcommittee.
- He graduated from Harvard in 1949 after attending in the mid-1940s and falsely described his role as a lieutenant on a readmission form.
- Hillevi Rombin was crowned Miss Universe in 1955 at age 21 and married Schine on October 22, 1957; they had six children and were married for nearly forty years.
- On June 19, 1996, a private plane carrying three people-Schine, his wife, and their son who was piloting-fell near Burbank, California; none aboard survived.

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/73096851Wed, 22 Jul 2026 01:10:19 +0000Creator at ObomediaThe Heir, The Miss Universe, and a Night the Sky Collapsed Fear of a private life that's never explained: a hotel heir who wrote a six-page pamphlet on communism, rose to national prominence at 25, and 43 years later died in a private plane crash...
Fear of a private life that's never explained: a hotel heir who wrote a six-page pamphlet on communism, rose to national prominence at 25, and 43 years later died in a private plane crash near Burbank-how do those convulsive public moments connect to the silence he kept? What did G. David Schine know and why did he never answer?

In this episode, we tell the life events laid out in the record: his upbringing in a hotel empire, the 1952 pamphlet that led him to Roy Cohn and McCarthy's subcommittee, his 1957 marriage to Miss Universe Hillevi Rombin, and the 1996 crash that killed him, his wife, and their son. How do these episodes link into the unresolved question at the center of his life?

Person: Gerard David Schine
Date of birth: September 11, 1927
Event: Private plane crash near Burbank, California
Date of crash: June 19, 1996
Spouse: Hillevi Rombin (married October 22, 1957)

- The pamphlet "Definition of Communism" was six pages long and was distributed to every room in every Schine family hotel.
- Schine was 24 when he wrote the pamphlet in 1952 and 25 when he became chief consultant to Senator McCarthy's subcommittee.
- He graduated from Harvard in 1949 after attending in the mid-1940s and falsely described his role as a lieutenant on a readmission form.
- Hillevi Rombin was crowned Miss Universe in 1955 at age 21 and married Schine on October 22, 1957; they had six children and were married for nearly forty years.
- On June 19, 1996, a private plane carrying three people-Schine, his wife, and their son who was piloting-fell near Burbank, California; none aboard survived.

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.]]>1121falsefullhttps://www.spreaker.com/episode/when-a-nut-fails-the-last-minutes-of-flight-261--73096847
A single failed nut the size of a coffee mug brought a packed airliner to catastrophic failure - 90% of its threads were gone before the flight even began. How did a copper alloy nut lose nearly all its threads across maintenance visits and inspections without anyone noticing, and what were the final minutes like when the pilots fought a machine gone deadly?

In this episode, we follow the timeline from Puerto Vallarta departure to the cockpit voice recorder pulled from the Pacific and describe the decisions, forces, and maintenance lapses that led to the crash. Listen to how a routine route, experienced crew, and a middle-aged MD-83 combined with a failing stabilizer and a single degraded nut to create an unfolding disaster.

Person: Captain Ted Thompson
Person: First Officer William Tansky
Aircraft: MD-83 registered N963AS
Date: January 31, 2000
Passengers and crew: 88 names on the memorial plaque

- The failed copper alloy nut at 17,800 feet had 90% of its threads already gone.
- The flight left Puerto Vallarta at 1:37 PM Pacific Standard Time.
- The aircraft had logged 26,500.84 flight hours and 14,315 pressurization cycles.
- Captain Thompson had 17,750 total flight hours; First Officer Tansky had 8,060 hours on the MD-80.
- The stabilizer jammed before 3:49 PM, later ran to full nose-down causing a descent from 31,000 to ~23,000-24,000 feet in about 80 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/73096847Wed, 22 Jul 2026 01:10:07 +0000Creator at ObomediaWhen a Nut Fails: The Last Minutes of Flight 261 A single failed nut the size of a coffee mug brought a packed airliner to catastrophic failure - 90% of its threads were gone before the flight even began. How did a copper alloy nut lose nearly all...
A single failed nut the size of a coffee mug brought a packed airliner to catastrophic failure - 90% of its threads were gone before the flight even began. How did a copper alloy nut lose nearly all its threads across maintenance visits and inspections without anyone noticing, and what were the final minutes like when the pilots fought a machine gone deadly?

In this episode, we follow the timeline from Puerto Vallarta departure to the cockpit voice recorder pulled from the Pacific and describe the decisions, forces, and maintenance lapses that led to the crash. Listen to how a routine route, experienced crew, and a middle-aged MD-83 combined with a failing stabilizer and a single degraded nut to create an unfolding disaster.

Person: Captain Ted Thompson
Person: First Officer William Tansky
Aircraft: MD-83 registered N963AS
Date: January 31, 2000
Passengers and crew: 88 names on the memorial plaque

- The failed copper alloy nut at 17,800 feet had 90% of its threads already gone.
- The flight left Puerto Vallarta at 1:37 PM Pacific Standard Time.
- The aircraft had logged 26,500.84 flight hours and 14,315 pressurization cycles.
- Captain Thompson had 17,750 total flight hours; First Officer Tansky had 8,060 hours on the MD-80.
- The stabilizer jammed before 3:49 PM, later ran to full nose-down causing a descent from 31,000 to ~23,000-24,000 feet in about 80 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.]]>1064falsefullhttps://www.spreaker.com/episode/six-rudder-kicks-sixty-seconds-how-flight-587-fell-apart--73096845
A single pilot input - six rapid rudder pedal movements in sixty seconds - preceded the loss of an airliner's entire vertical tail and the deaths of 260 people. The aircraft remained airborne for a minute after the first shove; what caused routine wake turbulence to become a catastrophe over Jamaica Bay and Belle Harbor, Queens?

In this episode, we tell what unfolded from takeoff at JFK through the exact sequence recorded by the flight data recorder, and why investigators eventually pointed to a training manual rather than terrorism as the critical factor. How did six rudder kicks turn a routine departure into the deadliest U.S. aviation accident since September 11?

Event: American Airlines Flight 587 crash
Date: November 12, 2001
Location: Over Jamaica Bay and Belle Harbor, Queens, New York
Aircraft: Airbus A300-600, tail number N14053
Fatalities: 260 people

- Takeoff clearance was at 09:13:28 from Runway 31L; a Japan Airlines 747 had departed 90 seconds earlier.
- Controller warned of possible wake turbulence at 09:11:36 before Flight 587 began its roll.
- First recorded bump from wake turbulence occurred at 09:15:36.
- At 09:15:52 the first officer began six rapid alternating rudder pedal inputs over sixty seconds.
- The aircraft's vertical tail separated from the airplane sixty seconds after the initial rudder input.

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/73096845Wed, 22 Jul 2026 01:09:55 +0000Creator at ObomediaSix Rudder Kicks, Sixty Seconds: How Flight 587 Fell Apart A single pilot input - six rapid rudder pedal movements in sixty seconds - preceded the loss of an airliner's entire vertical tail and the deaths of 260 people. The aircraft remained...
A single pilot input - six rapid rudder pedal movements in sixty seconds - preceded the loss of an airliner's entire vertical tail and the deaths of 260 people. The aircraft remained airborne for a minute after the first shove; what caused routine wake turbulence to become a catastrophe over Jamaica Bay and Belle Harbor, Queens?

In this episode, we tell what unfolded from takeoff at JFK through the exact sequence recorded by the flight data recorder, and why investigators eventually pointed to a training manual rather than terrorism as the critical factor. How did six rudder kicks turn a routine departure into the deadliest U.S. aviation accident since September 11?

Event: American Airlines Flight 587 crash
Date: November 12, 2001
Location: Over Jamaica Bay and Belle Harbor, Queens, New York
Aircraft: Airbus A300-600, tail number N14053
Fatalities: 260 people

- Takeoff clearance was at 09:13:28 from Runway 31L; a Japan Airlines 747 had departed 90 seconds earlier.
- Controller warned of possible wake turbulence at 09:11:36 before Flight 587 began its roll.
- First recorded bump from wake turbulence occurred at 09:15:36.
- At 09:15:52 the first officer began six rapid alternating rudder pedal inputs over sixty seconds.
- The aircraft's vertical tail separated from the airplane sixty seconds after the initial rudder input.

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.]]>1095falsefullhttps://www.spreaker.com/episode/when-two-planes-vanished-from-each-other-cerritos-collision-1986--73096844
Eighty-two people died in thirty seconds over Cerritos, California on August 31, 1986, when a DC-9 named Hermosillo and a Piper Archer collided in clear blue sky - neither pilot ever saw the other. What failures in rules and airspace control allowed a commercial jet and a small private plane to occupy the same six-thousand-foot corridor with no time to react?

In this episode, we tell the sequence of events that led to the midair collision and its human consequences, laying out who was aboard, where each aircraft came from, and how standard procedures at the time did not prevent disaster. How did routine flights and gaps in airspace rules converge into one of the deadliest U.S. aviation accidents of the era?

Event: Cerritos midair collision
Date: August 31, 1986
Aircraft 1: Aeromexico DC-9, registration XA-JED, name Hermosillo
Aircraft 2: Piper PA-28-181 Archer, registration N4891F
Fatalities: 82

- Collision occurred at 11:52 AM while both aircraft were in descent toward Los Angeles area airspace.
- Aeromexico Flight 498 had 64 people aboard: 58 passengers and 6 crew, including 10 children.
- Captain Arturo Valdes Prom had 10,641 total flight hours, 4,632 hours in the DC-9; First Officer Jose Hector Valencia had 1,463 total hours, 1,245 in type.
- Piper pilot William Kramer was 53 years old with 231 total flight hours; his wife Kathleen (51) and daughter Caroline (26) were aboard.
- The Piper departed Torrance Airport at approximately 11:40 AM en route to Big Bear City; Hermosillo began descent toward LAX at 11:46 AM.

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/73096844Wed, 22 Jul 2026 01:09:43 +0000Creator at ObomediaWhen Two Planes Vanished From Each Other: Cerritos Collision, 1986 Eighty-two people died in thirty seconds over Cerritos, California on August 31, 1986, when a DC-9 named Hermosillo and a Piper Archer collided in clear blue sky - neither pilot...
Eighty-two people died in thirty seconds over Cerritos, California on August 31, 1986, when a DC-9 named Hermosillo and a Piper Archer collided in clear blue sky - neither pilot ever saw the other. What failures in rules and airspace control allowed a commercial jet and a small private plane to occupy the same six-thousand-foot corridor with no time to react?

In this episode, we tell the sequence of events that led to the midair collision and its human consequences, laying out who was aboard, where each aircraft came from, and how standard procedures at the time did not prevent disaster. How did routine flights and gaps in airspace rules converge into one of the deadliest U.S. aviation accidents of the era?

Event: Cerritos midair collision
Date: August 31, 1986
Aircraft 1: Aeromexico DC-9, registration XA-JED, name Hermosillo
Aircraft 2: Piper PA-28-181 Archer, registration N4891F
Fatalities: 82

- Collision occurred at 11:52 AM while both aircraft were in descent toward Los Angeles area airspace.
- Aeromexico Flight 498 had 64 people aboard: 58 passengers and 6 crew, including 10 children.
- Captain Arturo Valdes Prom had 10,641 total flight hours, 4,632 hours in the DC-9; First Officer Jose Hector Valencia had 1,463 total hours, 1,245 in type.
- Piper pilot William Kramer was 53 years old with 231 total flight hours; his wife Kathleen (51) and daughter Caroline (26) were aboard.
- The Piper departed Torrance Airport at approximately 11:40 AM en route to Big Bear City; Hermosillo began descent toward LAX at 11:46 AM.

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.]]>1109falsefullhttps://www.spreaker.com/episode/a-two-year-old-girl-boarded-a-morning-flight-to-los-angeles-she-never-arrived--73096843
A routine family trip turned into one of the most shocking disruptions of a clear September morning: a two-and-a-half-year-old named Christine Hanson boarded United Airlines Flight 175 from Boston at 7:58 AM with her parents and never reached Los Angeles. How did five men pass through security with four-inch knives and take control of a less-than-one-third-full Boeing 767 while no distress call was made from the cockpit?

In this episode, we follow the timeline from boarding at Logan Airport through the final radio silence and the last cockpit words. You will hear how crew experience, CAPPS screening, passenger counts, and a single instruction from the captain fit into the unfolding events - but what critical moments before pushback might have changed everything?

Person: Christine Hanson
Date: September 11, 2001
Flight: United Airlines Flight 175
Aircraft: Boeing 767
Departure time: 7:58 AM

- Christine Hanson was two years and six months old, born February 22, 1999.
- Flight 175 pushed back from Gate 19 at Boston's Logan Airport at 7:58 AM on a clear Tuesday morning.
- The Boeing 767 carried 65 passengers, less than one-third of its capacity.
- Captain Victor Saracini was 51 years old and First Officer Michael Horrocks was 38 years old.
- At 8:42 AM Boston Center received no response after three radio calls; the captain's last recorded words were "everyone stay in your seats."

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/73096843Wed, 22 Jul 2026 01:09:30 +0000Creator at ObomediaA two-year-old girl boarded a morning flight to Los Angeles. She never arrived A routine family trip turned into one of the most shocking disruptions of a clear September morning: a two-and-a-half-year-old named Christine Hanson boarded United...
A routine family trip turned into one of the most shocking disruptions of a clear September morning: a two-and-a-half-year-old named Christine Hanson boarded United Airlines Flight 175 from Boston at 7:58 AM with her parents and never reached Los Angeles. How did five men pass through security with four-inch knives and take control of a less-than-one-third-full Boeing 767 while no distress call was made from the cockpit?

In this episode, we follow the timeline from boarding at Logan Airport through the final radio silence and the last cockpit words. You will hear how crew experience, CAPPS screening, passenger counts, and a single instruction from the captain fit into the unfolding events - but what critical moments before pushback might have changed everything?

Person: Christine Hanson
Date: September 11, 2001
Flight: United Airlines Flight 175
Aircraft: Boeing 767
Departure time: 7:58 AM

- Christine Hanson was two years and six months old, born February 22, 1999.
- Flight 175 pushed back from Gate 19 at Boston's Logan Airport at 7:58 AM on a clear Tuesday morning.
- The Boeing 767 carried 65 passengers, less than one-third of its capacity.
- Captain Victor Saracini was 51 years old and First Officer Michael Horrocks was 38 years old.
- At 8:42 AM Boston Center received no response after three radio calls; the captain's last recorded words were "everyone stay in your seats."

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.]]>988falsefullhttps://www.spreaker.com/episode/seven-year-old-at-the-controls-how-fame-pressured-a-fatal-flight--73096839
A seven-year-old girl with more than 33 hours of instruction sat in the left seat of a Cessna, on the cover of Time, and dead by the time the issue hit newsstands - and the media circus that chased her may have pushed adults past safety lines. How did publicity, parents and a paid instructor combine with a storm over Cheyenne to turn a coast-to-coast ambition into a fatal flight?

In this episode, we tell the sequence of events that led up to the April 1996 cross-country flight attempt, from Jessica Dubroff’s unconventional childhood and early training to the growing press attention and the weather briefing that warned of VFR-minimum-violating conditions. What choices did the adults make in those final hours that left a child at the controls?

Person: Jessica Whitney Dubroff
Date: April 1996 (eastbound leg arrived Cheyenne April 10, 1996)
Location: Cheyenne, Wyoming
Aircraft: 1975 Cessna 177B Cardinal, registration N35207
Flight instruction hours: more than 33 hours

- Jessica was seven years old and had logged more than 33 hours of flight instruction.
- The Cessna was a 1975 Cardinal, registration N35207, flown by instructor Joe Reid.
- The eastbound leg reached Cheyenne on the evening of April 10, 1996.
- Weather briefings indicated forecast conditions would fall below the VFR minimum visibility of three miles by morning.
- ABC News provided a video camera and blank cassettes to document the journey.

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/73096839Wed, 22 Jul 2026 01:09:19 +0000Creator at ObomediaSeven-Year-Old at the Controls: How Fame Pressured a Fatal Flight A seven-year-old girl with more than 33 hours of instruction sat in the left seat of a Cessna, on the cover of Time, and dead by the time the issue hit newsstands - and the media...
A seven-year-old girl with more than 33 hours of instruction sat in the left seat of a Cessna, on the cover of Time, and dead by the time the issue hit newsstands - and the media circus that chased her may have pushed adults past safety lines. How did publicity, parents and a paid instructor combine with a storm over Cheyenne to turn a coast-to-coast ambition into a fatal flight?

In this episode, we tell the sequence of events that led up to the April 1996 cross-country flight attempt, from Jessica Dubroff’s unconventional childhood and early training to the growing press attention and the weather briefing that warned of VFR-minimum-violating conditions. What choices did the adults make in those final hours that left a child at the controls?

Person: Jessica Whitney Dubroff
Date: April 1996 (eastbound leg arrived Cheyenne April 10, 1996)
Location: Cheyenne, Wyoming
Aircraft: 1975 Cessna 177B Cardinal, registration N35207
Flight instruction hours: more than 33 hours

- Jessica was seven years old and had logged more than 33 hours of flight instruction.
- The Cessna was a 1975 Cardinal, registration N35207, flown by instructor Joe Reid.
- The eastbound leg reached Cheyenne on the evening of April 10, 1996.
- Weather briefings indicated forecast conditions would fall below the VFR minimum visibility of three miles by morning.
- ABC News provided a video camera and blank cassettes to document the journey.

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.]]>1176falsefullhttps://www.spreaker.com/episode/the-engine-was-on-the-runway-the-plane-it-belonged-to-had-thirty-one-seconds-left--73096837
A single engine lay intact on O'Hare's concrete while the DC-10 it had just left climbed into the sky with 31 seconds of life remaining. This photograph would become the most studied image in American aviation history - how did a crack, growing silently for eight weeks, doom 273 people despite inspections and crews following procedure?

In this episode, we tell what happened on American Airlines Flight 191 and trace how routine maintenance choices and a hidden structural crack combined with normal operations to produce catastrophe. We follow the timeline from Tulsa maintenance practices to the moments after takeoff and ask: who - or what - actually failed?

Date: May 25, 1979
Event: American Airlines Flight 191 crash
Aircraft: McDonnell Douglas DC-10
Fatalities: 273
Passengers and crew: 258 passengers, 13 crew

- The left engine's forward pylon flange had a crack that had been growing for approximately eight weeks.
- The plane pushed back at 2:59 PM and taxied toward runway 32L, departing one minute ahead of schedule.
- Captain Walter Lux had more than 22,000 flight hours; First Officer James Dillard had more than 9,000 hours.
- There were 258 passengers aboard, including a group of travel and aviation enthusiasts and at least one novelist and one publisher.
- Tulsa maintenance crews had used a forklift method that saved roughly 200 working hours compared to the standard crane procedure.

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/73096837Wed, 22 Jul 2026 01:09:07 +0000Creator at ObomediaThe engine was on the runway. The plane it belonged to had thirty-one seconds left A single engine lay intact on O'Hare's concrete while the DC-10 it had just left climbed into the sky with 31 seconds of life remaining. This photograph would become...
A single engine lay intact on O'Hare's concrete while the DC-10 it had just left climbed into the sky with 31 seconds of life remaining. This photograph would become the most studied image in American aviation history - how did a crack, growing silently for eight weeks, doom 273 people despite inspections and crews following procedure?

In this episode, we tell what happened on American Airlines Flight 191 and trace how routine maintenance choices and a hidden structural crack combined with normal operations to produce catastrophe. We follow the timeline from Tulsa maintenance practices to the moments after takeoff and ask: who - or what - actually failed?

Date: May 25, 1979
Event: American Airlines Flight 191 crash
Aircraft: McDonnell Douglas DC-10
Fatalities: 273
Passengers and crew: 258 passengers, 13 crew

- The left engine's forward pylon flange had a crack that had been growing for approximately eight weeks.
- The plane pushed back at 2:59 PM and taxied toward runway 32L, departing one minute ahead of schedule.
- Captain Walter Lux had more than 22,000 flight hours; First Officer James Dillard had more than 9,000 hours.
- There were 258 passengers aboard, including a group of travel and aviation enthusiasts and at least one novelist and one publisher.
- Tulsa maintenance crews had used a forklift method that saved roughly 200 working hours compared to the standard crane procedure.

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.]]>1131falsefullhttps://www.spreaker.com/episode/fuel-gauges-empty-over-nebraska-the-brown-family-s-final-flight--73096835
A private plane's fuel gauges read empty over Nebraska, three people died and the pilot had not confirmed fuel before takeoff - what happened on July 24, 2019 that ended the Brown family's return from Oshkosh? How did one preflight check never made erase a life spent unearthing ancient worlds?

In this episode, we tell the story of the flight and the life it cut short. We cover the accident facts reported by the National Transportation Safety Board and trace Sarah Andrews Brown's career as a geologist, novelist, and researcher to show what was lost over Nebraska and why it matters.

Date: July 24, 2019
Event: Private plane crash returning from Oshkosh air show
People: Sarah Andrews Brown; Damon Brown; Duncan Brown
Cause noted: Pilot failed to confirm adequate fuel before departure
Survivors: 0

- Three people were on board and none survived.
- The flight was returning from an air show in Oshkosh, Wisconsin.
- The pilot had failed to confirm adequate fuel before leaving the ground, according to the NTSB.
- Sarah Andrews Brown was born in 1951 and was sixty-seven at the time of the crash.
- Sarah Andrews Brown published her first Em Hansen novel, Tensleep, in 1994 and wrote a total of ten novels.

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/73096835Wed, 22 Jul 2026 01:08:55 +0000Creator at ObomediaFuel Gauges Empty Over Nebraska: The Brown Family's Final Flight A private plane's fuel gauges read empty over Nebraska, three people died and the pilot had not confirmed fuel before takeoff - what happened on July 24, 2019 that ended the Brown...
A private plane's fuel gauges read empty over Nebraska, three people died and the pilot had not confirmed fuel before takeoff - what happened on July 24, 2019 that ended the Brown family's return from Oshkosh? How did one preflight check never made erase a life spent unearthing ancient worlds?

In this episode, we tell the story of the flight and the life it cut short. We cover the accident facts reported by the National Transportation Safety Board and trace Sarah Andrews Brown's career as a geologist, novelist, and researcher to show what was lost over Nebraska and why it matters.

Date: July 24, 2019
Event: Private plane crash returning from Oshkosh air show
People: Sarah Andrews Brown; Damon Brown; Duncan Brown
Cause noted: Pilot failed to confirm adequate fuel before departure
Survivors: 0

- Three people were on board and none survived.
- The flight was returning from an air show in Oshkosh, Wisconsin.
- The pilot had failed to confirm adequate fuel before leaving the ground, according to the NTSB.
- Sarah Andrews Brown was born in 1951 and was sixty-seven at the time of the crash.
- Sarah Andrews Brown published her first Em Hansen novel, Tensleep, in 1994 and wrote a total of ten novels.

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.]]>1062falsefullhttps://www.spreaker.com/episode/seventeen-minutes-over-manhattan-voices-from-flight-175-s-last-calls--73096833
Fear that someone you love is moments from death - and the desperate clarity in their last words. Seventeen minutes of United Airlines Flight 175 were tracked on radar and filmed from multiple angles, but no cockpit voice recorder was ever recovered; instead, the final record is a mosaic of phone calls and voicemails from thirty thousand feet. How did ordinary conversations, calm reports, and a child's last cries become the only testimony of what happened inside the plane?

In this episode, we present the people, timeline, and calls that make up Flight 175’s final minutes, and we follow the lines of connection from crew and passengers to controllers and family who received those last voices. What can those calls tell us about the passengers’ awareness, the crew’s last transmissions, and the unanswered moments when the plane turned toward the South Tower?

Person: Peter Hanson
Date: September 11, 2001
Location: Flight 175 (Boston to Los Angeles), crossed into New York Center at 8:42 AM
Event: Hijacking and impact at 8:46 AM
Aircraft: Boeing 767-200, registration N612UA, built 1983

- 8:52 AM: Lee Hanson answered Peter's call; Peter said the plane had been taken and that the pilots were dead.
- Peter called again eight minutes later; his final words were "Oh, my God" with a woman screaming in the background.
- Flight 175 departed Gate 19 at Logan at 7:58 AM and lifted off Runway 9 at 8:14 AM.
- The flight carried 51 passengers and 9 crew members, including Captain Victor Saracini (51) and First Officer Michael Horrocks (38).
- 8:46 AM: By this time the two pilots were dead and Marwan al-Shehhi had taken control, coinciding with the moment Flight 11 struck the North Tower.

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/73096833Wed, 22 Jul 2026 01:08:43 +0000Creator at ObomediaSeventeen Minutes Over Manhattan: Voices from Flight 175's Last Calls Fear that someone you love is moments from death - and the desperate clarity in their last words. Seventeen minutes of United Airlines Flight 175 were tracked on radar and filmed...
Fear that someone you love is moments from death - and the desperate clarity in their last words. Seventeen minutes of United Airlines Flight 175 were tracked on radar and filmed from multiple angles, but no cockpit voice recorder was ever recovered; instead, the final record is a mosaic of phone calls and voicemails from thirty thousand feet. How did ordinary conversations, calm reports, and a child's last cries become the only testimony of what happened inside the plane?

In this episode, we present the people, timeline, and calls that make up Flight 175’s final minutes, and we follow the lines of connection from crew and passengers to controllers and family who received those last voices. What can those calls tell us about the passengers’ awareness, the crew’s last transmissions, and the unanswered moments when the plane turned toward the South Tower?

Person: Peter Hanson
Date: September 11, 2001
Location: Flight 175 (Boston to Los Angeles), crossed into New York Center at 8:42 AM
Event: Hijacking and impact at 8:46 AM
Aircraft: Boeing 767-200, registration N612UA, built 1983

- 8:52 AM: Lee Hanson answered Peter's call; Peter said the plane had been taken and that the pilots were dead.
- Peter called again eight minutes later; his final words were "Oh, my God" with a woman screaming in the background.
- Flight 175 departed Gate 19 at Logan at 7:58 AM and lifted off Runway 9 at 8:14 AM.
- The flight carried 51 passengers and 9 crew members, including Captain Victor Saracini (51) and First Officer Michael Horrocks (38).
- 8:46 AM: By this time the two pilots were dead and Marwan al-Shehhi had taken control, coinciding with the moment Flight 11 struck the North Tower.

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.]]>1078falsefullhttps://www.spreaker.com/episode/wrong-number-wrong-order-how-a-single-radio-call-almost-killed-677--73096831
A drink cart hit the ceiling at thirty-seven thousand feet and two jets came within one hundred and thirty-five metres of each other - when every safety system was working. Six hundred and seventy-seven people were aboard two Japan Airlines flights that nearly occupied the same point in the sky; how did one wrong radio call create a near-catastrophe?

In this episode, we present the documented record of what unfolded above Suruga Bay on January 31, 2001, and the nine years of legal proceedings that followed. You will hear how controller errors, TCAS advisories, and misdirected instructions combined - could a single mistaken call sign have caused two fully loaded airliners to converge?

Date: January 31, 2001
Location: Suruga Bay airspace, Japan
Event: Near midair collision between JAL 907 (Boeing 747) and JAL 958 (DC-10)
Person: Hideki Hachitani, 26, air traffic control trainee
System: Both aircraft TCAS confirmed operational before departure

- JAL 907 was Boeing 747 registration JA8904 with 411 passengers and 16 crew.
- JAL 958 was McDonnell Douglas DC-10 registration JA8546 with 237 passengers and 13 crew.
- The horizontal separation reduced to 135 metres, where it should have been 2,000 feet.
- At 15:54 the 747’s TCAS issued a climb advisory to Captain Makoto Watanabe.
- Controller Hideki Hachitani mistakenly instructed JAL 907 to descend and supervisor Yasuko Momii later addressed a climb instruction to non-existent flight JAL 957.

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/73096831Wed, 22 Jul 2026 01:08:30 +0000Creator at ObomediaWrong Number, Wrong Order: How a Single Radio Call Almost Killed 677 A drink cart hit the ceiling at thirty-seven thousand feet and two jets came within one hundred and thirty-five metres of each other - when every safety system was working. Six...
A drink cart hit the ceiling at thirty-seven thousand feet and two jets came within one hundred and thirty-five metres of each other - when every safety system was working. Six hundred and seventy-seven people were aboard two Japan Airlines flights that nearly occupied the same point in the sky; how did one wrong radio call create a near-catastrophe?

In this episode, we present the documented record of what unfolded above Suruga Bay on January 31, 2001, and the nine years of legal proceedings that followed. You will hear how controller errors, TCAS advisories, and misdirected instructions combined - could a single mistaken call sign have caused two fully loaded airliners to converge?

Date: January 31, 2001
Location: Suruga Bay airspace, Japan
Event: Near midair collision between JAL 907 (Boeing 747) and JAL 958 (DC-10)
Person: Hideki Hachitani, 26, air traffic control trainee
System: Both aircraft TCAS confirmed operational before departure

- JAL 907 was Boeing 747 registration JA8904 with 411 passengers and 16 crew.
- JAL 958 was McDonnell Douglas DC-10 registration JA8546 with 237 passengers and 13 crew.
- The horizontal separation reduced to 135 metres, where it should have been 2,000 feet.
- At 15:54 the 747’s TCAS issued a climb advisory to Captain Makoto Watanabe.
- Controller Hideki Hachitani mistakenly instructed JAL 907 to descend and supervisor Yasuko Momii later addressed a climb instruction to non-existent flight JAL 957.

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.]]>1036falsefullhttps://www.spreaker.com/episode/seconds-of-silence-how-a-turbine-shredded-flight-007--73096830
A sudden, fatal chain began with a single turbine fragment that severed power and silenced the recorders twenty-six seconds before impact; the Il-62 hit an ice-covered moat less than one kilometre from the runway at 11:14:35 on March 14, 1980. How did engine repairs, extended overhaul intervals and routine acceptance of vibration leave a transatlantic airliner with a part that would shred its neighbour - and bury the crews' last moments in silence?

In this episode, we lay out the sequence of events on the aircraft and the maintenance history that preceded the crash, from the engine's earlier compressor damage and repeated repairs to airline policies that extended engine hours beyond manufacturer limits. What decisions on the ground allowed an engine fragment to cut the systems that would have recorded those final twenty-six seconds?

Person: Captain Paweł Lipowczan
Date: March 14, 1980
Location: Warsaw-Okęcie Airport vicinity (ice-covered fortress moat, ~1 km from runway threshold)
Aircraft: Ilyushin Il-62 "Mikołaj Kopernik" (built 1971, 9 years old)
Passengers: 87 aboard, 0 survivors

- Flight recorders went dark 26 seconds before impact due to a turbine fragment severing power cables.
- Engine number two had about 700 flight hours on the Kopernik after multiple installs and repairs.
- The Il-62 departed JFK at 21:18 local time on March 13 and had flown roughly nine hours without incident before approach.
- LOT claimed engines could be operated safely to 8,600 hours despite manufacturer warranty life of 5,000 hours and common failures between 2,000-3,000 hours.
- Fourteen amateur boxers, one 30-year-old singer with her 4-year-old daughter, and other passengers were among the 87 people on board.

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/73096830Wed, 22 Jul 2026 01:08:19 +0000Creator at ObomediaSeconds of Silence: How a Turbine Shredded Flight 007 A sudden, fatal chain began with a single turbine fragment that severed power and silenced the recorders twenty-six seconds before impact; the Il-62 hit an ice-covered moat less than one...
A sudden, fatal chain began with a single turbine fragment that severed power and silenced the recorders twenty-six seconds before impact; the Il-62 hit an ice-covered moat less than one kilometre from the runway at 11:14:35 on March 14, 1980. How did engine repairs, extended overhaul intervals and routine acceptance of vibration leave a transatlantic airliner with a part that would shred its neighbour - and bury the crews' last moments in silence?

In this episode, we lay out the sequence of events on the aircraft and the maintenance history that preceded the crash, from the engine's earlier compressor damage and repeated repairs to airline policies that extended engine hours beyond manufacturer limits. What decisions on the ground allowed an engine fragment to cut the systems that would have recorded those final twenty-six seconds?

Person: Captain Paweł Lipowczan
Date: March 14, 1980
Location: Warsaw-Okęcie Airport vicinity (ice-covered fortress moat, ~1 km from runway threshold)
Aircraft: Ilyushin Il-62 "Mikołaj Kopernik" (built 1971, 9 years old)
Passengers: 87 aboard, 0 survivors

- Flight recorders went dark 26 seconds before impact due to a turbine fragment severing power cables.
- Engine number two had about 700 flight hours on the Kopernik after multiple installs and repairs.
- The Il-62 departed JFK at 21:18 local time on March 13 and had flown roughly nine hours without incident before approach.
- LOT claimed engines could be operated safely to 8,600 hours despite manufacturer warranty life of 5,000 hours and common failures between 2,000-3,000 hours.
- Fourteen amateur boxers, one 30-year-old singer with her 4-year-old daughter, and other passengers were among the 87 people on board.

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.]]>1090falsefullhttps://www.spreaker.com/episode/one-second-from-landing-how-flight-834-fell-into-silence--73096829
A single second separated a routine farewell from annihilation: at 13:56:30 on April 4, 2011, Georgian Airways Flight 834 never landed and thirty-two people were dead before the minute ended. How did a Bombardier CRJ100ER on a familiar two-hour milk run, with an experienced-surface record on paper, collapse in roughly forty seconds into the deadliest aviation accident in United Nations history?

In this episode, we present the sequence of events, the people on board, and the institutional gaps that preceded the crash, and ask whether the disaster was driven by weather alone or by a failing system that left the crew exposed. What exactly hit Flight 834 in that final second, and why did oversight fail at every level?

Date: April 4, 2011
Aircraft: Bombardier CRJ100ER, registration 4L-GAE
Flight: Georgian Airways Flight 834 (callsign "UNO")
Fatalities: 32
Survivor: Francis Mwamba, Congolese journalist

- Departure time from Kisangani: 12:18 local
- Estimated arrival at Kinshasa N'djili Airport: 13:55 local
- Number of passengers representing UN agencies: 20 (including 14 for MONUSCO)
- Captain Alexei Hovhanesyan: 2,811 total flight hours, 1,622 on CRJ100, promoted to captain ~3 months before accident after 1 simulator session
- First Officer Suliko Tsutskiridze: 495 total flight hours, 344 on CRJ100

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/73096829Wed, 22 Jul 2026 01:08:06 +0000Creator at ObomediaOne Second From Landing: How Flight 834 Fell Into Silence A single second separated a routine farewell from annihilation: at 13:56:30 on April 4, 2011, Georgian Airways Flight 834 never landed and thirty-two people were dead before the minute...
A single second separated a routine farewell from annihilation: at 13:56:30 on April 4, 2011, Georgian Airways Flight 834 never landed and thirty-two people were dead before the minute ended. How did a Bombardier CRJ100ER on a familiar two-hour milk run, with an experienced-surface record on paper, collapse in roughly forty seconds into the deadliest aviation accident in United Nations history?

In this episode, we present the sequence of events, the people on board, and the institutional gaps that preceded the crash, and ask whether the disaster was driven by weather alone or by a failing system that left the crew exposed. What exactly hit Flight 834 in that final second, and why did oversight fail at every level?

Date: April 4, 2011
Aircraft: Bombardier CRJ100ER, registration 4L-GAE
Flight: Georgian Airways Flight 834 (callsign "UNO")
Fatalities: 32
Survivor: Francis Mwamba, Congolese journalist

- Departure time from Kisangani: 12:18 local
- Estimated arrival at Kinshasa N'djili Airport: 13:55 local
- Number of passengers representing UN agencies: 20 (including 14 for MONUSCO)
- Captain Alexei Hovhanesyan: 2,811 total flight hours, 1,622 on CRJ100, promoted to captain ~3 months before accident after 1 simulator session
- First Officer Suliko Tsutskiridze: 495 total flight hours, 344 on CRJ100

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.]]>1045falsefullhttps://www.spreaker.com/episode/the-night-ice-killed-flight-5017-how-instruments-lied-and-116-died--73096828
A chill of helplessness: invisible ice crystals silently fooled instruments and, according to investigators, triggered systems that slowly throttled a fully crewed MD-83 until it plunged nose-first into the Malian desert. How did ordinary sensors and an autothrottle become the mechanisms of a catastrophe that left 116 people dead?

In this episode, you will hear the timeline of Air Algérie Flight 5017 from takeoff to impact, the crew and aircraft details, and how weather and system logic combined to hide danger - could a single sensor error derail an otherwise routine flight?

Date: July 24, 2014
Aircraft: McDonnell Douglas MD-83 (registration EC-LTV)
Passengers on board: 116
Crew nationalities: Spanish pilots operating a Swiftair aircraft wet-leased to Air Algérie
Event: Autothrottle reduced thrust after EPR sensor icing leading to high-speed, nearly vertical descent

- Takeoff time: 01:15 (local)
- Level-off at FL310: 01:37, autopilot engaged
- Last known time before disappearance: 01:47
- Aircraft cycles: approximately 32,000 by July 2014
- Captain's total hours: 12,988; First Officer's total hours: 7,016

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/73096828Wed, 22 Jul 2026 01:07:54 +0000Creator at ObomediaThe Night Ice Killed Flight 5017: How Instruments Lied and 116 Died A chill of helplessness: invisible ice crystals silently fooled instruments and, according to investigators, triggered systems that slowly throttled a fully crewed MD-83 until it...
A chill of helplessness: invisible ice crystals silently fooled instruments and, according to investigators, triggered systems that slowly throttled a fully crewed MD-83 until it plunged nose-first into the Malian desert. How did ordinary sensors and an autothrottle become the mechanisms of a catastrophe that left 116 people dead?

In this episode, you will hear the timeline of Air Algérie Flight 5017 from takeoff to impact, the crew and aircraft details, and how weather and system logic combined to hide danger - could a single sensor error derail an otherwise routine flight?

Date: July 24, 2014
Aircraft: McDonnell Douglas MD-83 (registration EC-LTV)
Passengers on board: 116
Crew nationalities: Spanish pilots operating a Swiftair aircraft wet-leased to Air Algérie
Event: Autothrottle reduced thrust after EPR sensor icing leading to high-speed, nearly vertical descent

- Takeoff time: 01:15 (local)
- Level-off at FL310: 01:37, autopilot engaged
- Last known time before disappearance: 01:47
- Aircraft cycles: approximately 32,000 by July 2014
- Captain's total hours: 12,988; First Officer's total hours: 7,016

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.]]>1054falsefullhttps://www.spreaker.com/episode/the-night-the-constellation-flew-into-invisible-mountains--73096826
The idea of a decorated captain guiding a state-of-the-art airliner into invisible obstacles grabs the mind: fifteen thousand pounds of diamonds and sixteen thousand pounds of watches lay intact while forty people vanished; how could maps, weather and rules all fail at once? What single missing detail turned a routine approach into a catastrophe?

In this episode, we tell the story of KLM Flight PH-TEN and its captain Koene Dirk Parmentier, the flight’s planned route and the faulty maps and forecasts that shaped the final minutes - and ask how those institutional failures combined to make the crash inevitable.

Person: Koene Dirk Parmentier
Event: KLM Flight PH-TEN crash approach to Prestwick
Date: October 20, 1948
Location: Scottish hillside near Prestwick
Cargo: 15,000 pounds of uncut diamonds and 16,000 pounds of Swiss watches

- Forty people were on board the Lockheed L-049 Constellation PH-TEN.
- The aircraft departed Schiphol at 21:11 Central European Time after a late cargo addition.
- KLM charts marked inland terrain at 250 feet while actual elevation exceeded 400 feet.
- High-voltage power lines carrying 132,000 volts ran three miles inland but were not shown on KLM charts.
- Two Scandinavian Airlines flights had attempted Prestwick that evening and turned back due to deteriorating weather.

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/73096826Wed, 22 Jul 2026 01:07:42 +0000Creator at ObomediaThe Night the Constellation Flew Into Invisible Mountains The idea of a decorated captain guiding a state-of-the-art airliner into invisible obstacles grabs the mind: fifteen thousand pounds of diamonds and sixteen thousand pounds of watches lay...
The idea of a decorated captain guiding a state-of-the-art airliner into invisible obstacles grabs the mind: fifteen thousand pounds of diamonds and sixteen thousand pounds of watches lay intact while forty people vanished; how could maps, weather and rules all fail at once? What single missing detail turned a routine approach into a catastrophe?

In this episode, we tell the story of KLM Flight PH-TEN and its captain Koene Dirk Parmentier, the flight’s planned route and the faulty maps and forecasts that shaped the final minutes - and ask how those institutional failures combined to make the crash inevitable.

Person: Koene Dirk Parmentier
Event: KLM Flight PH-TEN crash approach to Prestwick
Date: October 20, 1948
Location: Scottish hillside near Prestwick
Cargo: 15,000 pounds of uncut diamonds and 16,000 pounds of Swiss watches

- Forty people were on board the Lockheed L-049 Constellation PH-TEN.
- The aircraft departed Schiphol at 21:11 Central European Time after a late cargo addition.
- KLM charts marked inland terrain at 250 feet while actual elevation exceeded 400 feet.
- High-voltage power lines carrying 132,000 volts ran three miles inland but were not shown on KLM charts.
- Two Scandinavian Airlines flights had attempted Prestwick that evening and turned back due to deteriorating weather.

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.]]>977falsefullhttps://www.spreaker.com/episode/a-two-hundred-pound-life-raft-flew-upward-and-dented-the-ceiling-gravity-had-stopped-working--73096824
Fear of sudden, violent danger: a 200-pound life raft launched off the floor and dented the ceiling inside NOAA 42 as gravity seemed to stop, while the crew unknowingly flew into a Category Five hurricane; how did five minutes of radar data and a failed instrument set the stage for 78 minutes of extreme turbulence and damage?

In this episode, we follow the flight of NOAA 42 on September 15, 1989, and describe the sequence of equipment failures, decision points, and storm behavior that led the crew into Hurricane Hugo’s eyewall - could a repaired radar and a five-minute data window have been enough to reveal the storm’s true intensity?

Date: September 15, 1989
Aircraft: Lockheed WP-3D Orion (NOAA 42, tail number N42RF)
Event: Flight into Hurricane Hugo during Hurricane Energetics experiment
People aboard: 16
Observed damage: ceiling dent from a two-hundred-pound life raft

- The life raft weighing 200 pounds launched from the floor and dented the aircraft ceiling during the flight.
- The crew believed they were penetrating a Category Three hurricane when, in fact, Hurricane Hugo was a Category Five.
- The belly radar failed shortly after takeoff, took twenty minutes to repair, leaving roughly five minutes to review its data before descent.
- The crew set a penetration altitude of 1,500 feet, 3,500 feet below the recommended minimum of 5,000 feet for Hugo’s true intensity.
- The violent sequence inside the eyewall lasted seventy-eight minutes and led to lasting changes in hurricane hunter procedures.

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/73096824Wed, 22 Jul 2026 01:07:31 +0000Creator at ObomediaA two-hundred-pound life raft flew upward and dented the ceiling - gravity had stopped working Fear of sudden, violent danger: a 200-pound life raft launched off the floor and dented the ceiling inside NOAA 42 as gravity seemed to stop, while the...
Fear of sudden, violent danger: a 200-pound life raft launched off the floor and dented the ceiling inside NOAA 42 as gravity seemed to stop, while the crew unknowingly flew into a Category Five hurricane; how did five minutes of radar data and a failed instrument set the stage for 78 minutes of extreme turbulence and damage?

In this episode, we follow the flight of NOAA 42 on September 15, 1989, and describe the sequence of equipment failures, decision points, and storm behavior that led the crew into Hurricane Hugo’s eyewall - could a repaired radar and a five-minute data window have been enough to reveal the storm’s true intensity?

Date: September 15, 1989
Aircraft: Lockheed WP-3D Orion (NOAA 42, tail number N42RF)
Event: Flight into Hurricane Hugo during Hurricane Energetics experiment
People aboard: 16
Observed damage: ceiling dent from a two-hundred-pound life raft

- The life raft weighing 200 pounds launched from the floor and dented the aircraft ceiling during the flight.
- The crew believed they were penetrating a Category Three hurricane when, in fact, Hurricane Hugo was a Category Five.
- The belly radar failed shortly after takeoff, took twenty minutes to repair, leaving roughly five minutes to review its data before descent.
- The crew set a penetration altitude of 1,500 feet, 3,500 feet below the recommended minimum of 5,000 feet for Hugo’s true intensity.
- The violent sequence inside the eyewall lasted seventy-eight minutes and led to lasting changes in hurricane hunter procedures.

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.]]>1174falsefullhttps://www.spreaker.com/episode/the-night-the-abel-tasman-vanished-fog-glass-bottle-no-answer--73096822
A perfectly airworthy Fokker Friendship vanished into a moonlit Coral Sea with twenty-nine people aboard and no distress call - and a small brown glass bottle pulled from forty feet of water would become one of the few physical mysteries left in the wreckage. What exactly drew the Abel Tasman straight into the sea on a night when fog, a full moon, and calm water seemed to offer nothing to fear?

In this episode, we tell the sequence of events from departure in Brisbane through the aborted approaches and the final unanswered transmission, laying out the known facts and the unanswered question that still haunts investigators: how did an experienced crew flying a new, well-regarded aircraft end up underwater with no warning?

Aircraft: Fokker Friendship VH-TFB
Date: June 10, 1960
Flight: Flight 538
Passengers: 29
Location: Coral Sea approach to Mackay

- Departure time from Brisbane: 5:00 PM
- Landing time at Rockhampton: 7:12 PM; departed Rockhampton: 7:52 PM
- Cruising altitude while circling: 13,000 feet
- Runway temperature read at 10:10 PM: 55.4°F (13°C)
- Wreckage recovered from: 40 feet of seawater, including a small brown glass bottle

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/73096822Wed, 22 Jul 2026 01:07:19 +0000Creator at ObomediaThe Night the Abel Tasman Vanished: Fog, Glass Bottle, No Answer A perfectly airworthy Fokker Friendship vanished into a moonlit Coral Sea with twenty-nine people aboard and no distress call - and a small brown glass bottle pulled from forty feet...
A perfectly airworthy Fokker Friendship vanished into a moonlit Coral Sea with twenty-nine people aboard and no distress call - and a small brown glass bottle pulled from forty feet of water would become one of the few physical mysteries left in the wreckage. What exactly drew the Abel Tasman straight into the sea on a night when fog, a full moon, and calm water seemed to offer nothing to fear?

In this episode, we tell the sequence of events from departure in Brisbane through the aborted approaches and the final unanswered transmission, laying out the known facts and the unanswered question that still haunts investigators: how did an experienced crew flying a new, well-regarded aircraft end up underwater with no warning?

Aircraft: Fokker Friendship VH-TFB
Date: June 10, 1960
Flight: Flight 538
Passengers: 29
Location: Coral Sea approach to Mackay

- Departure time from Brisbane: 5:00 PM
- Landing time at Rockhampton: 7:12 PM; departed Rockhampton: 7:52 PM
- Cruising altitude while circling: 13,000 feet
- Runway temperature read at 10:10 PM: 55.4°F (13°C)
- Wreckage recovered from: 40 feet of seawater, including a small brown glass bottle

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.]]>1082falsefullhttps://www.spreaker.com/episode/the-tailfin-on-chaperi-afghanistan-s-flight-that-vanished-without-a-voice--73096816
A single vertical stabilizer stood upright in the snow at 11,000 feet - the only recognizable fragment of an airplane carrying 105 people - and no one heard from the crew after contact was lost at 16:00 on February 3, 2005. What made a Boeing 737 on approach to Kabul end up striking a ridgeline on an eastward heading when it had been flying west, and why was so little of the aircraft ever found?

In this episode, we tell the story of Kam Air Flight 904 and the sparse, puzzling evidence left behind. You will hear how the flight departed Herat, how a 25-year-old Boeing 737-200 operated under multiple jurisdictions vanished in a storm, and why a lone tailfin became the central clue to a disaster that silenced 105 people.

Date: February 3, 2005
Event: Kam Air Flight 904 crash on Chaperi (Cheri Ghar) ridgeline
Aircraft: Boeing 737-200, registration EX-037, built 1980
Passengers and crew: 97 passengers, 8 crew, total 105 people
Wreckage location: ~20 miles east of Kabul, elevation ~11,000 feet, impact ~50 feet below summit

- Contact lost with air traffic controllers in Kabul at 16:00 local time while the flight was 12 minutes from landing.
- The airplane was operated by Phoenix Aviation and leased to Kam Air; registration was Kyrgyzstan EX-037.
- The vertical stabilizer was spotted four days later by Dutch Apache helicopters on February 7, 2005.
- The aircraft struck Cheri Ghar on an eastward heading though it had been approaching Kabul flying west.
- The forward fuselage was thrown over the crest into the valley; the tail remained upright on the uphill slope amid waist-deep snow.

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/73096816Wed, 22 Jul 2026 01:07:07 +0000Creator at ObomediaThe Tailfin on Chaperi: Afghanistan's Flight That Vanished Without a Voice A single vertical stabilizer stood upright in the snow at 11,000 feet - the only recognizable fragment of an airplane carrying 105 people - and no one heard from the crew...
A single vertical stabilizer stood upright in the snow at 11,000 feet - the only recognizable fragment of an airplane carrying 105 people - and no one heard from the crew after contact was lost at 16:00 on February 3, 2005. What made a Boeing 737 on approach to Kabul end up striking a ridgeline on an eastward heading when it had been flying west, and why was so little of the aircraft ever found?

In this episode, we tell the story of Kam Air Flight 904 and the sparse, puzzling evidence left behind. You will hear how the flight departed Herat, how a 25-year-old Boeing 737-200 operated under multiple jurisdictions vanished in a storm, and why a lone tailfin became the central clue to a disaster that silenced 105 people.

Date: February 3, 2005
Event: Kam Air Flight 904 crash on Chaperi (Cheri Ghar) ridgeline
Aircraft: Boeing 737-200, registration EX-037, built 1980
Passengers and crew: 97 passengers, 8 crew, total 105 people
Wreckage location: ~20 miles east of Kabul, elevation ~11,000 feet, impact ~50 feet below summit

- Contact lost with air traffic controllers in Kabul at 16:00 local time while the flight was 12 minutes from landing.
- The airplane was operated by Phoenix Aviation and leased to Kam Air; registration was Kyrgyzstan EX-037.
- The vertical stabilizer was spotted four days later by Dutch Apache helicopters on February 7, 2005.
- The aircraft struck Cheri Ghar on an eastward heading though it had been approaching Kabul flying west.
- The forward fuselage was thrown over the crest into the valley; the tail remained upright on the uphill slope amid waist-deep snow.

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.]]>1180falsefullhttps://www.spreaker.com/episode/the-night-samantha-smith-never-came-home-inside-flight-1808-s-fatal-approach--73096814
The night air over central Maine felt routine until a commuter plane descended through just 300 feet of cloud and never climbed again - the wreckage stopped exactly 4,007 feet from the end of Runway Four. Eight people aboard Bar Harbor Airlines Flight 1808 died, including thirteen-year-old Samantha Smith, once called "America's youngest ambassador"; why, when the crew needed to pull up, did no one do it?

In this episode, we tell the story of the flight, the decisions that added an unscheduled flag stop, and the weather and instrument conditions the crew faced on final approach. We trace Samantha's journey from international fame back to the last flight she ever boarded and ask the question that haunts the crash: what broke down in that cockpit at the critical moment?

Person: Samantha Smith
Event: Crash of Bar Harbor Airlines Flight 1808
Date: August 25, 1985
Location: Auburn/Lewiston Municipal Airport, central Maine
Distance from runway end to wreckage: 4,007 feet

- Eight people were aboard Flight 1808 and none survived.
- The aircraft descended through a cloud ceiling of 300 feet before impact.
- Visibility at Auburn was one mile in light drizzle, at the legal minimum for approach.
- Flight 1808 made Auburn a flag stop after a separate scheduled flight was canceled due to ATC delays.
- Samantha Smith was thirteen years old and had been returning from filming in London.

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/73096814Wed, 22 Jul 2026 01:06:55 +0000Creator at ObomediaThe Night Samantha Smith Never Came Home: Inside Flight 1808's Fatal Approach The night air over central Maine felt routine until a commuter plane descended through just 300 feet of cloud and never climbed again - the wreckage stopped exactly 4,007...
The night air over central Maine felt routine until a commuter plane descended through just 300 feet of cloud and never climbed again - the wreckage stopped exactly 4,007 feet from the end of Runway Four. Eight people aboard Bar Harbor Airlines Flight 1808 died, including thirteen-year-old Samantha Smith, once called "America's youngest ambassador"; why, when the crew needed to pull up, did no one do it?

In this episode, we tell the story of the flight, the decisions that added an unscheduled flag stop, and the weather and instrument conditions the crew faced on final approach. We trace Samantha's journey from international fame back to the last flight she ever boarded and ask the question that haunts the crash: what broke down in that cockpit at the critical moment?

Person: Samantha Smith
Event: Crash of Bar Harbor Airlines Flight 1808
Date: August 25, 1985
Location: Auburn/Lewiston Municipal Airport, central Maine
Distance from runway end to wreckage: 4,007 feet

- Eight people were aboard Flight 1808 and none survived.
- The aircraft descended through a cloud ceiling of 300 feet before impact.
- Visibility at Auburn was one mile in light drizzle, at the legal minimum for approach.
- Flight 1808 made Auburn a flag stop after a separate scheduled flight was canceled due to ATC delays.
- Samantha Smith was thirteen years old and had been returning from filming in London.

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.]]>1107falsefullhttps://www.spreaker.com/episode/a-twelve-year-old-girl-alone-in-the-indian-ocean-the-only-survivor-of-153-people--73096813
The ocean claimed 152 lives that night, yet one twelve-year-old clung to wreckage for twelve hours before rescue - how did she survive when an Airbus A310 carrying 153 people vanished without a distress call? What mixture of mechanical errors, human mistakes and ignored warnings turned a routine summer flight into a catastrophe?

In this episode, we tell the sequence of events from takeoff in Paris to the final minutes over Moroni, describing the flight, the weather, the cockpit actions and the unanswered questions that followed. What exactly happened in those twelve minutes between the crew noting the runway lights were off and the aircraft hitting the sea?

Event: Yemenia Airways Flight IY626
Date: June 30, 2009
Aircraft: Airbus A310, registration 7O-ADJ
Location: Indian Ocean, approach to Prince Said Ibrahim International Airport, Moroni, Comoros Islands
Survivor: Bahia Bakari, age 12

- 153 people were on board the flight that disappeared from radar and fell into the sea.
- Bahia Bakari clung to wreckage for 12 hours before being found as the sole survivor.
- The crew asked whether runway lights were illuminated and were told the lights were not on, then continued a circling approach at night over water.
- Winds were gusting above 60 kilometers per hour and visibility had dropped during the approach.
- Investigators found the altitude-select knob was set to zero feet, causing the autopilot to fly toward zero altitude.

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/73096813Wed, 22 Jul 2026 01:06:42 +0000Creator at ObomediaA twelve-year-old girl alone in the Indian Ocean - the only survivor of 153 people The ocean claimed 152 lives that night, yet one twelve-year-old clung to wreckage for twelve hours before rescue - how did she survive when an Airbus A310 carrying...
The ocean claimed 152 lives that night, yet one twelve-year-old clung to wreckage for twelve hours before rescue - how did she survive when an Airbus A310 carrying 153 people vanished without a distress call? What mixture of mechanical errors, human mistakes and ignored warnings turned a routine summer flight into a catastrophe?

In this episode, we tell the sequence of events from takeoff in Paris to the final minutes over Moroni, describing the flight, the weather, the cockpit actions and the unanswered questions that followed. What exactly happened in those twelve minutes between the crew noting the runway lights were off and the aircraft hitting the sea?

Event: Yemenia Airways Flight IY626
Date: June 30, 2009
Aircraft: Airbus A310, registration 7O-ADJ
Location: Indian Ocean, approach to Prince Said Ibrahim International Airport, Moroni, Comoros Islands
Survivor: Bahia Bakari, age 12

- 153 people were on board the flight that disappeared from radar and fell into the sea.
- Bahia Bakari clung to wreckage for 12 hours before being found as the sole survivor.
- The crew asked whether runway lights were illuminated and were told the lights were not on, then continued a circling approach at night over water.
- Winds were gusting above 60 kilometers per hour and visibility had dropped during the approach.
- Investigators found the altitude-select knob was set to zero feet, causing the autopilot to fly toward zero altitude.

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.]]>893falsefullhttps://www.spreaker.com/episode/stick-shaker-at-14-feet-how-a-faulty-sensor-burned-a-tristar--73096812
The moment the stick shaker screamed at fourteen feet, a 20‑year‑old TriStar had already left the runway at 181 knots and then come back - and two hundred and eighty people walked away from a burning wreck. How could an intermittent angle-of-attack sensor, flagged unserviceable nine times and cycled through a parts pool, create a false stall warning that almost killed everyone on board?

In this episode, we tell the story of TWA Flight 843 and the chain of events from pushback to crash, following the crew actions, aircraft history, and the maintenance system that placed a faulty sensor on that flight. What hidden failures in parts handling and testing allowed a benign takeoff to become a survivable catastrophe?

Event: TWA Flight 843
Date: July 30, 1992
Aircraft: Lockheed L-1011 TriStar
Location: John F. Kennedy International Airport, Runway 13R
Passengers: 280

- Takeoff speed reached 181 knots before the aircraft left the runway.
- Aircraft climbed to 14 feet above ground when the stick shaker activated.
- The airframe had 19,659 takeoff and landing cycles and 49,662 flight hours.
- The failed angle-of-attack sensor had been flagged unserviceable nine separate times before being fitted to this aircraft.
- Captain William Shelby Kinkead had 20,149 total hours and 2,397 hours on the L-1011.

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/73096812Wed, 22 Jul 2026 01:06:31 +0000Creator at ObomediaStick Shaker at 14 Feet: How a Faulty Sensor Burned a TriStar The moment the stick shaker screamed at fourteen feet, a 20‑year‑old TriStar had already left the runway at 181 knots and then come back - and two hundred and eighty people walked away...
The moment the stick shaker screamed at fourteen feet, a 20‑year‑old TriStar had already left the runway at 181 knots and then come back - and two hundred and eighty people walked away from a burning wreck. How could an intermittent angle-of-attack sensor, flagged unserviceable nine times and cycled through a parts pool, create a false stall warning that almost killed everyone on board?

In this episode, we tell the story of TWA Flight 843 and the chain of events from pushback to crash, following the crew actions, aircraft history, and the maintenance system that placed a faulty sensor on that flight. What hidden failures in parts handling and testing allowed a benign takeoff to become a survivable catastrophe?

Event: TWA Flight 843
Date: July 30, 1992
Aircraft: Lockheed L-1011 TriStar
Location: John F. Kennedy International Airport, Runway 13R
Passengers: 280

- Takeoff speed reached 181 knots before the aircraft left the runway.
- Aircraft climbed to 14 feet above ground when the stick shaker activated.
- The airframe had 19,659 takeoff and landing cycles and 49,662 flight hours.
- The failed angle-of-attack sensor had been flagged unserviceable nine separate times before being fitted to this aircraft.
- Captain William Shelby Kinkead had 20,149 total hours and 2,397 hours on the L-1011.

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.]]>1044falsefullhttps://www.spreaker.com/episode/one-hundred-hours-missing-how-rank-sent-119-into-cerro-bashun--73096806
The thought that rank could outweigh safety still chills: a Boeing 737 with registration HC-BIG carried exactly thirty hours on type in its captain’s log while the agreement required one hundred, and one hundred and nineteen people never reached Cuenca. How did a political deal, a dead president, and a military rank combine to put a general in the left seat minutes before impact?

In this episode, we present the facts of the accident and the training agreement behind the aircraft, the deviations from that agreement, and the final cockpit moments recorded before the crash - and ask how those gaps in procedure and protocol led to the deadliest aviation accident in Ecuador’s history.

Person: Captain Jorge Leonardo Peña Terán
Event: Crash into Cerro Bashún
Date: July 15, 1983
Aircraft: Boeing 737-2V2 Advanced, registration HC-BIG
Passengers and Crew: 119 people never reached Cuenca

- The aircraft arrived in Ecuador in October 1981 and had first flown on June 11, 1981 under temporary registration N8283V.
- The agreement required pilots to log 100 flight hours on the 737 before commanding the aircraft; Peña Terán had 30 hours on type.
- Peña Terán received three weeks of simulator training in Brazil in March 1983 instead of six weeks in Seattle and two months of supervised line flying specified by the agreement.
- President Jaime Roldós Aguilera negotiated the deal but died in an aircraft accident in May 1981 before the 737 entered service.
- The flight departed Quito for Cuenca on schedule; weather reports showed clear skies while fog in the approach valleys obscured visibility.

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/73096806Wed, 22 Jul 2026 01:06:19 +0000Creator at ObomediaOne Hundred Hours Missing: How Rank Sent 119 Into Cerro Bashún The thought that rank could outweigh safety still chills: a Boeing 737 with registration HC-BIG carried exactly thirty hours on type in its captain’s log while the agreement required...
The thought that rank could outweigh safety still chills: a Boeing 737 with registration HC-BIG carried exactly thirty hours on type in its captain’s log while the agreement required one hundred, and one hundred and nineteen people never reached Cuenca. How did a political deal, a dead president, and a military rank combine to put a general in the left seat minutes before impact?

In this episode, we present the facts of the accident and the training agreement behind the aircraft, the deviations from that agreement, and the final cockpit moments recorded before the crash - and ask how those gaps in procedure and protocol led to the deadliest aviation accident in Ecuador’s history.

Person: Captain Jorge Leonardo Peña Terán
Event: Crash into Cerro Bashún
Date: July 15, 1983
Aircraft: Boeing 737-2V2 Advanced, registration HC-BIG
Passengers and Crew: 119 people never reached Cuenca

- The aircraft arrived in Ecuador in October 1981 and had first flown on June 11, 1981 under temporary registration N8283V.
- The agreement required pilots to log 100 flight hours on the 737 before commanding the aircraft; Peña Terán had 30 hours on type.
- Peña Terán received three weeks of simulator training in Brazil in March 1983 instead of six weeks in Seattle and two months of supervised line flying specified by the agreement.
- President Jaime Roldós Aguilera negotiated the deal but died in an aircraft accident in May 1981 before the 737 entered service.
- The flight departed Quito for Cuenca on schedule; weather reports showed clear skies while fog in the approach valleys obscured visibility.

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.]]>1012falsefullhttps://www.spreaker.com/episode/lights-still-on-how-a-live-circuit-kept-21-alive-on-flight-217--73096803
The cabin lights were still burning inside a Twin Otter that had torn apart, lost both wings, and come to rest on its side at 10,530 feet in Colorado with the outside temperature at minus 50°F - a detail investigators said should not be possible. How did a single live electrical circuit inside a ruined fuselage keep 21 people alive through the night, while rescuers and search aircraft battled whiteout winds and eight feet of snow?

In this episode, we tell the story of Rocky Mountain Airways Flight 217 on December 4, 1978, from the delayed departure in Steamboat Springs through the sudden crash beyond Buffalo Pass, and the chain of decisions, physics, and luck that followed. Which moments and choices turned a catastrophe into a survival story?

Date: December 4, 1978
Aircraft: DHC-6 Twin Otter 300, registration N25RM
Crew: Captain Scott Alan Klopfenstein (29, 7,340 total hours), First Officer Gary Coleman (34, 3,816 total hours)
Passengers: 21 persons boarded (including an 8-month-old infant and three US Forest Service employees)
Location: Mountain in Colorado, came to rest at 10,530 feet; outside temperature -50°F

- The aircraft had 15,145 hours on its airframe and two Pratt & Whitney PT6A-27 engines.
- Ground time at Steamboat Springs was 34 minutes; departure at 18:55, about 2 hours behind schedule.
- Crewmembers manually removed 0.75 inches of ice from the airframe before departure.
- The aircraft stopped climbing at 13,000 feet instead of the planned 17,000 feet on the Victor 101 route.
- Rescuers crossed eight feet of snow with winds gusting to 40 mph; an Air Force C-130 searched the wrong area for 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/73096803Wed, 22 Jul 2026 01:06:07 +0000Creator at ObomediaLights Still On: How a Live Circuit Kept 21 Alive on Flight 217 The cabin lights were still burning inside a Twin Otter that had torn apart, lost both wings, and come to rest on its side at 10,530 feet in Colorado with the outside temperature at...
The cabin lights were still burning inside a Twin Otter that had torn apart, lost both wings, and come to rest on its side at 10,530 feet in Colorado with the outside temperature at minus 50°F - a detail investigators said should not be possible. How did a single live electrical circuit inside a ruined fuselage keep 21 people alive through the night, while rescuers and search aircraft battled whiteout winds and eight feet of snow?

In this episode, we tell the story of Rocky Mountain Airways Flight 217 on December 4, 1978, from the delayed departure in Steamboat Springs through the sudden crash beyond Buffalo Pass, and the chain of decisions, physics, and luck that followed. Which moments and choices turned a catastrophe into a survival story?

Date: December 4, 1978
Aircraft: DHC-6 Twin Otter 300, registration N25RM
Crew: Captain Scott Alan Klopfenstein (29, 7,340 total hours), First Officer Gary Coleman (34, 3,816 total hours)
Passengers: 21 persons boarded (including an 8-month-old infant and three US Forest Service employees)
Location: Mountain in Colorado, came to rest at 10,530 feet; outside temperature -50°F

- The aircraft had 15,145 hours on its airframe and two Pratt & Whitney PT6A-27 engines.
- Ground time at Steamboat Springs was 34 minutes; departure at 18:55, about 2 hours behind schedule.
- Crewmembers manually removed 0.75 inches of ice from the airframe before departure.
- The aircraft stopped climbing at 13,000 feet instead of the planned 17,000 feet on the Victor 101 route.
- Rescuers crossed eight feet of snow with winds gusting to 40 mph; an Air Force C-130 searched the wrong area for 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.]]>1053falsefullhttps://www.spreaker.com/episode/when-the-airliner-fell-through-their-roof-flight-307-s-last-approach--73096800
Cold, close, and eerily ordinary: a family watching the Minneapolis Lakers had no warning when a passenger airliner punched through their roof on March 7, 1950 - a storm with freezing rain, half-mile visibility, and 40-knot gusts was already closing in. Why did a seasoned captain continue an approach after being told of 900-foot ceilings, frequent power failures, and worsening winds?

In this episode, we tell the events of Northwest Orient Flight 307 from its departure in Washington, D.C. through the delays, the weather updates, and the final radio calls that led the aircraft toward Minneapolis. Listen for the decisions and conditions that culminated in a crash that struck a family home - and ask whether the final moments could have ended differently.

Date: March 7, 1950
Aircraft: Martin 202, registration N93050
Flight origin: Washington D.C. with stops including Detroit and Madison
Passengers onboard: 10
Impact point: left wing struck a 70-foot flagpole 4,180 feet short of runway, 650 feet west of centerline

- Temperature and conditions: freezing rain with visibility 0.5-0.75 miles and ceiling 900 feet
- Wind reported: north at 27 knots, gusting to 40 knots
- Aircraft fuel loaded in Madison: 1,010 gallons and 38 gallons of oil
- Crew rest prior to departure: 21 hours 52 minutes off duty for both pilots
- Captain total flight hours: 7,619 with 988 in the Martin 202

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/73096800Wed, 22 Jul 2026 01:05:54 +0000Creator at ObomediaWhen the Airliner Fell Through Their Roof: Flight 307's Last Approach Cold, close, and eerily ordinary: a family watching the Minneapolis Lakers had no warning when a passenger airliner punched through their roof on March 7, 1950 - a storm with...
Cold, close, and eerily ordinary: a family watching the Minneapolis Lakers had no warning when a passenger airliner punched through their roof on March 7, 1950 - a storm with freezing rain, half-mile visibility, and 40-knot gusts was already closing in. Why did a seasoned captain continue an approach after being told of 900-foot ceilings, frequent power failures, and worsening winds?

In this episode, we tell the events of Northwest Orient Flight 307 from its departure in Washington, D.C. through the delays, the weather updates, and the final radio calls that led the aircraft toward Minneapolis. Listen for the decisions and conditions that culminated in a crash that struck a family home - and ask whether the final moments could have ended differently.

Date: March 7, 1950
Aircraft: Martin 202, registration N93050
Flight origin: Washington D.C. with stops including Detroit and Madison
Passengers onboard: 10
Impact point: left wing struck a 70-foot flagpole 4,180 feet short of runway, 650 feet west of centerline

- Temperature and conditions: freezing rain with visibility 0.5-0.75 miles and ceiling 900 feet
- Wind reported: north at 27 knots, gusting to 40 knots
- Aircraft fuel loaded in Madison: 1,010 gallons and 38 gallons of oil
- Crew rest prior to departure: 21 hours 52 minutes off duty for both pilots
- Captain total flight hours: 7,619 with 988 in the Martin 202

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.]]>1056falsefullhttps://www.spreaker.com/episode/the-night-a-misplaced-beacon-turned-sweden-s-skies-deadly--73096798
A single misplaced light over southern Sweden lured a perfectly functioning Convair into a fatal descent on the night of 20 November 1964, killing 31 of 43 aboard - and the system that allowed it had no single person to blame. How did a strobe beacon that wasn’t on any chart, positioned 110 meters off the runway centerline and unknown to many pilots, become the difference between a safe approach and disaster?

In this episode, we tell the sequence of events on Linjeflyg Flight 267V from departure to impact, outline the navigation beacons and airport arrangements the crew were given, and follow the investigation that concluded the system failed incrementally - reshaping safety at joint military-civilian fields. What exactly about the beacon placement and documentation led several crews to almost make the same error, but only this crew did not recover?

Date: 20 November 1964
Aircraft: Convair CV-440 (registered SE-CCK)
Flight: Linjeflyg Flight 267V
Fatalities: 31 of 43 aboard
Route: Stockholm Bromma → (bypassed Hultsfred, Halmstad) → Ängelholm-Helsingborg

- The light first appeared at 21:13 and the crew began to descend toward it.
- The outer beacon LJ was located 10.4 km from the runway threshold instead of the civil standard 7 km.
- The inner beacon J was at 3,080 m from threshold versus the civil standard 1,200 m.
- The strobe beacon sat 2,250 m from the threshold and 110 m to the right of the runway centerline and was not on the crew’s approach chart.
- The aircraft had crossed three countries and four owners since manufacture on 23 June 1954 and was acquired by Aerotransport on 1 October 1964, seven weeks before the accident.

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/73096798Wed, 22 Jul 2026 01:05:42 +0000Creator at ObomediaThe Night a Misplaced Beacon Turned Sweden's Skies Deadly A single misplaced light over southern Sweden lured a perfectly functioning Convair into a fatal descent on the night of 20 November 1964, killing 31 of 43 aboard - and the system that...
A single misplaced light over southern Sweden lured a perfectly functioning Convair into a fatal descent on the night of 20 November 1964, killing 31 of 43 aboard - and the system that allowed it had no single person to blame. How did a strobe beacon that wasn’t on any chart, positioned 110 meters off the runway centerline and unknown to many pilots, become the difference between a safe approach and disaster?

In this episode, we tell the sequence of events on Linjeflyg Flight 267V from departure to impact, outline the navigation beacons and airport arrangements the crew were given, and follow the investigation that concluded the system failed incrementally - reshaping safety at joint military-civilian fields. What exactly about the beacon placement and documentation led several crews to almost make the same error, but only this crew did not recover?

Date: 20 November 1964
Aircraft: Convair CV-440 (registered SE-CCK)
Flight: Linjeflyg Flight 267V
Fatalities: 31 of 43 aboard
Route: Stockholm Bromma → (bypassed Hultsfred, Halmstad) → Ängelholm-Helsingborg

- The light first appeared at 21:13 and the crew began to descend toward it.
- The outer beacon LJ was located 10.4 km from the runway threshold instead of the civil standard 7 km.
- The inner beacon J was at 3,080 m from threshold versus the civil standard 1,200 m.
- The strobe beacon sat 2,250 m from the threshold and 110 m to the right of the runway centerline and was not on the crew’s approach chart.
- The aircraft had crossed three countries and four owners since manufacture on 23 June 1954 and was acquired by Aerotransport on 1 October 1964, seven weeks before the accident.

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.]]>990falsefullhttps://www.spreaker.com/episode/the-pilot-who-knew-the-hills-why-69-never-reached-imphal--73096796
Familiarity can be lethal: a captain who had flown into Imphal thirty-six times guided a fully serviceable Boeing 737 into the Thangjing range, striking the hillside at 6,700 feet and killing all 69 aboard. How could an experienced pilot on a known route, in daylight and with an airworthy aircraft, end up three hundred feet below the summit at full approach speed?

In this episode, we lay out the sequence of events from takeoff to impact, the airport procedures designed for a radar-less approach, and the human and procedural choices that diverged from them. What combination of decisions and environmental factors turned routine familiarity into fatal error?

Date: August 16, 1991
Aircraft: Boeing 737 registration VT-EFL
Person: Captain Sekhar Heldar (37 years old, 3,783 total hours; 2,369 on the 737)
Location: Thangjing range, near Imphal, Manipur
Casualties: 69 fatalities (68 adults, 1 infant)

- Takeoff time from Calcutta: 11:54 AM.
- Impact elevation: 6,700 feet, three hundred feet below the Thangjing summit.
- Total flight cycles on aircraft since 1977: more than 33,000 cycles.
- Captain Heldar had flown the Calcutta-Imphal route 36 times and had personally requested it.
- All 69 bodies were recovered within three days; 300 relatives flown in for identification.

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/73096796Wed, 22 Jul 2026 01:05:31 +0000Creator at ObomediaThe Pilot Who Knew the Hills - Why 69 Never Reached Imphal Familiarity can be lethal: a captain who had flown into Imphal thirty-six times guided a fully serviceable Boeing 737 into the Thangjing range, striking the hillside at 6,700 feet and...
Familiarity can be lethal: a captain who had flown into Imphal thirty-six times guided a fully serviceable Boeing 737 into the Thangjing range, striking the hillside at 6,700 feet and killing all 69 aboard. How could an experienced pilot on a known route, in daylight and with an airworthy aircraft, end up three hundred feet below the summit at full approach speed?

In this episode, we lay out the sequence of events from takeoff to impact, the airport procedures designed for a radar-less approach, and the human and procedural choices that diverged from them. What combination of decisions and environmental factors turned routine familiarity into fatal error?

Date: August 16, 1991
Aircraft: Boeing 737 registration VT-EFL
Person: Captain Sekhar Heldar (37 years old, 3,783 total hours; 2,369 on the 737)
Location: Thangjing range, near Imphal, Manipur
Casualties: 69 fatalities (68 adults, 1 infant)

- Takeoff time from Calcutta: 11:54 AM.
- Impact elevation: 6,700 feet, three hundred feet below the Thangjing summit.
- Total flight cycles on aircraft since 1977: more than 33,000 cycles.
- Captain Heldar had flown the Calcutta-Imphal route 36 times and had personally requested it.
- All 69 bodies were recovered within three days; 300 relatives flown in for identification.

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.]]>1114falsefullhttps://www.spreaker.com/episode/the-flight-that-vanished-without-a-trace-ob-1303-s-final-call--73096786
A sudden emergency call at 13:50 on September 11, 1990 reported fuel nearly gone and altitude dropping through 10,000 feet - then the frequency fell silent and nothing of the Boeing 727 was ever found. Sixteen people aboard, roughly 44,000 pounds of fuel loaded at Keflavik, and a last-known position hundreds of miles southeast of St. John’s - how did a fully fueled ferry flight disappear without a trace?

In this episode, we tell what the flight record and witness accounts record about OB-1303’s final hours, who was on board, the planned ferry route from Keflavik to Gander, and the puzzling navigation that placed the aircraft far off course - could the crew’s last call explain why no wreckage was ever recovered?

Date: September 11, 1990
Aircraft: Boeing 727, registration OB-1303
Passengers and crew: 16 Peruvian nationals
Fuel loaded: approximately 20 tons (about 44,000 pounds)
Last confirmed position: roughly 250 miles southeast of St. John’s, Newfoundland

- Emergency frequency transmission at 13:50 reported fuel almost gone and altitude dropping through 10,000 feet.
- Aircraft had departed Keflavik at 13:16 with an estimated flight time to Gander of 3 hours 38 minutes.
- The Boeing 727 was built in 1969 and was 21 years old at the time of disappearance.
- The aircraft had been leased to Air Malta for the summer and returned to Faucett Peru for a ferry flight home.
- Search teams found no fuselage fragments, life rafts, or any floating debris after the disappearance.

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/73096786Wed, 22 Jul 2026 01:05:19 +0000Creator at ObomediaThe Flight That Vanished Without a Trace: OB-1303's Final Call A sudden emergency call at 13:50 on September 11, 1990 reported fuel nearly gone and altitude dropping through 10,000 feet - then the frequency fell silent and nothing of the Boeing 727...
A sudden emergency call at 13:50 on September 11, 1990 reported fuel nearly gone and altitude dropping through 10,000 feet - then the frequency fell silent and nothing of the Boeing 727 was ever found. Sixteen people aboard, roughly 44,000 pounds of fuel loaded at Keflavik, and a last-known position hundreds of miles southeast of St. John’s - how did a fully fueled ferry flight disappear without a trace?

In this episode, we tell what the flight record and witness accounts record about OB-1303’s final hours, who was on board, the planned ferry route from Keflavik to Gander, and the puzzling navigation that placed the aircraft far off course - could the crew’s last call explain why no wreckage was ever recovered?

Date: September 11, 1990
Aircraft: Boeing 727, registration OB-1303
Passengers and crew: 16 Peruvian nationals
Fuel loaded: approximately 20 tons (about 44,000 pounds)
Last confirmed position: roughly 250 miles southeast of St. John’s, Newfoundland

- Emergency frequency transmission at 13:50 reported fuel almost gone and altitude dropping through 10,000 feet.
- Aircraft had departed Keflavik at 13:16 with an estimated flight time to Gander of 3 hours 38 minutes.
- The Boeing 727 was built in 1969 and was 21 years old at the time of disappearance.
- The aircraft had been leased to Air Malta for the summer and returned to Faucett Peru for a ferry flight home.
- Search teams found no fuselage fragments, life rafts, or any floating debris after the disappearance.

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.]]>1133falsefullhttps://www.spreaker.com/episode/the-pilot-who-pulled-back-inside-the-41-second-crash--73096782
Fear of a controlled disaster: a brand-new Bombardier Q400 vanished from radar four miles short of Buffalo Niagara Airport and fifty people were dead within sixty seconds - all because a pilot pulled back when the airplane needed forward input. How did routine procedure, two exhausted pilots, and one overridden automatic correction turn 41 seconds into a fatal descent?

In this episode, we tell what happened on the night of February 12, 2009, how the flight data recorder captured the critical actions in the cockpit, and why the investigation uncovered systemic failures beyond pilot error. What exactly changed in those final 41 seconds, and who had warned about it beforehand?

Person: Captain Marvin Renslow, age 47, total flight time 3,379 hours, 111 hours as Q400 captain
Person: First Officer Rebecca Lynne Shaw, age 24, total flight time 2,244 hours, 774 turbine hours
Event: Colgan Air Flight 3407 crash into a house on Long Street in Clarence Center
Date: February 12, 2009, last routine transmission at 10:17 PM, impact by 10:18 PM
Aircraft: Bombardier Q400, registration N200WQ, built April 2008, 1,819 airframe hours

- 50 people were dead before the clock reached 10:18 PM on February 12, 2009.
- The interval from last routine radio transmission to impact was 41 seconds.
- Flaps were at 5 degrees and airspeed 145 knots before crew called for flaps 15 and speed fell to 131 knots.
- The stick shaker activated at 131 knots, signaling an impending aerodynamic stall.
- The aircraft registration was N200WQ, a Q400 less than one year old with 1,819 airframe 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/73096782Wed, 22 Jul 2026 01:05:07 +0000Creator at ObomediaThe Pilot Who Pulled Back: Inside the 41-Second Crash Fear of a controlled disaster: a brand-new Bombardier Q400 vanished from radar four miles short of Buffalo Niagara Airport and fifty people were dead within sixty seconds - all because a pilot...
Fear of a controlled disaster: a brand-new Bombardier Q400 vanished from radar four miles short of Buffalo Niagara Airport and fifty people were dead within sixty seconds - all because a pilot pulled back when the airplane needed forward input. How did routine procedure, two exhausted pilots, and one overridden automatic correction turn 41 seconds into a fatal descent?

In this episode, we tell what happened on the night of February 12, 2009, how the flight data recorder captured the critical actions in the cockpit, and why the investigation uncovered systemic failures beyond pilot error. What exactly changed in those final 41 seconds, and who had warned about it beforehand?

Person: Captain Marvin Renslow, age 47, total flight time 3,379 hours, 111 hours as Q400 captain
Person: First Officer Rebecca Lynne Shaw, age 24, total flight time 2,244 hours, 774 turbine hours
Event: Colgan Air Flight 3407 crash into a house on Long Street in Clarence Center
Date: February 12, 2009, last routine transmission at 10:17 PM, impact by 10:18 PM
Aircraft: Bombardier Q400, registration N200WQ, built April 2008, 1,819 airframe hours

- 50 people were dead before the clock reached 10:18 PM on February 12, 2009.
- The interval from last routine radio transmission to impact was 41 seconds.
- Flaps were at 5 degrees and airspeed 145 knots before crew called for flaps 15 and speed fell to 131 knots.
- The stick shaker activated at 131 knots, signaling an impending aerodynamic stall.
- The aircraft registration was N200WQ, a Q400 less than one year old with 1,819 airframe 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.]]>1191falsefullhttps://www.spreaker.com/episode/they-trusted-the-instruments-181-dead-three-hills-one-mistake--73096780
Fear that expertise can blind you: a six-year-old Boeing 747 with no mechanical faults flew twelve kilometers off course and hit three hills in three minutes, killing 170 people. How did a cockpit with nearly a century of combined flight time and working instruments descend below safe altitude without a single distress call?

In this episode, we tell the facts of Avianca Flight 011's final hours, from its Frankfurt-Paris-Madrid routing and the crew's experience to the clear weather and working ILS at Madrid-Barajas, and ask how belief in what the instruments showed overrode reality.

Person: Captain Tulio Hernández, 58, 23,215 total flight hours
Person: First Officer Eduardo Ramírez, 36, 4,384 total flight hours
Person: Flight Engineer Juan Laverde, 57, 15,942 total flight hours
Date: November 27, 1983 (impact approx. 00:06)
Location: Three hills near Mejorada del Campo, ~12 kilometers southeast of Madrid-Barajas

- Aircraft: Boeing 747-200BM Combi, registration HK-2910X, six years old, nicknamed Olafo
- Onboard: 181 people (158 passengers, 23 crew); 11 survivors, 170 fatalities
- Departure: Left Paris Charles de Gaulle at 22:25 on November 26, delayed for connections
- Last ATC contact: Cleared to land runway 33 at approx. 00:03; first impact at approx. 00:06
- Conditions: Clear weather, visibility 8 km, calm wind, ILS and ground radar/communications operational

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/73096780Wed, 22 Jul 2026 01:04:55 +0000Creator at ObomediaThey Trusted the Instruments - 181 Dead, Three Hills, One Mistake Fear that expertise can blind you: a six-year-old Boeing 747 with no mechanical faults flew twelve kilometers off course and hit three hills in three minutes, killing 170 people. How...
Fear that expertise can blind you: a six-year-old Boeing 747 with no mechanical faults flew twelve kilometers off course and hit three hills in three minutes, killing 170 people. How did a cockpit with nearly a century of combined flight time and working instruments descend below safe altitude without a single distress call?

In this episode, we tell the facts of Avianca Flight 011's final hours, from its Frankfurt-Paris-Madrid routing and the crew's experience to the clear weather and working ILS at Madrid-Barajas, and ask how belief in what the instruments showed overrode reality.

Person: Captain Tulio Hernández, 58, 23,215 total flight hours
Person: First Officer Eduardo Ramírez, 36, 4,384 total flight hours
Person: Flight Engineer Juan Laverde, 57, 15,942 total flight hours
Date: November 27, 1983 (impact approx. 00:06)
Location: Three hills near Mejorada del Campo, ~12 kilometers southeast of Madrid-Barajas

- Aircraft: Boeing 747-200BM Combi, registration HK-2910X, six years old, nicknamed Olafo
- Onboard: 181 people (158 passengers, 23 crew); 11 survivors, 170 fatalities
- Departure: Left Paris Charles de Gaulle at 22:25 on November 26, delayed for connections
- Last ATC contact: Cleared to land runway 33 at approx. 00:03; first impact at approx. 00:06
- Conditions: Clear weather, visibility 8 km, calm wind, ILS and ground radar/communications operational

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.]]>1112falsefullhttps://www.spreaker.com/episode/when-a-dc-8-tried-to-kill-its-crew-twice-the-toledo-mystery--73096776
A four‑engine DC‑8 struck the frozen Ohio ground three miles short of the runway at 03:26, scattering parts with enough force to shake plaster from nearby houses; four men were aboard and none survived - so what happened in the final two minutes that turned a routine approach into catastrophe? The same aircraft had a cargo door failure at Toledo three months earlier, and investigators found a damaged latch among the wreckage that refused to fit a simple explanation.

In this episode, we walk through the flight, the crew, the aircraft history and the physical evidence recovered from the scene, following the questions that remained after official reports: did a cargo door issue recur, and why did a seasoned crew lose control on a clear approach?

Person: Harry Baker, 59 years old, 16,382 total hours, 2,382 on DC‑8
Person: Tim Hupp, 37 years old, 5,082 total hours, 3,135 on DC‑8; pilot flying
Person: Jose Montalbo, 57 years old, 21,697 total hours, 7,697 on DC‑8
Person: Raman Patel, non‑revenue pilot aboard (Buffalo Airways)
Date: February 15, 1992
Event: Aircraft impacted 3 miles short of runway at 03:26; four fatalities

- Aircraft registration N794AL: Douglas DC‑8‑63F, serial number 45923, first flew 1968
- Airframe totals before accident: 70,084 flight hours and 22,804 cycles
- Prior incident: November 13, 1991 cargo door opened in flight at Toledo; warning indicator failed due to damaged wiring
- Wreckage recovered included seven cargo door latches from the field; one latch had lost its locking pins
- Cockpit Voice Recorder survived impact and was listened to by investigators as part of the inquiry

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/73096776Wed, 22 Jul 2026 01:04:42 +0000Creator at ObomediaWhen a DC‑8 Tried to Kill Its Crew Twice: The Toledo Mystery A four‑engine DC‑8 struck the frozen Ohio ground three miles short of the runway at 03:26, scattering parts with enough force to shake plaster from nearby houses; four men were aboard and...
A four‑engine DC‑8 struck the frozen Ohio ground three miles short of the runway at 03:26, scattering parts with enough force to shake plaster from nearby houses; four men were aboard and none survived - so what happened in the final two minutes that turned a routine approach into catastrophe? The same aircraft had a cargo door failure at Toledo three months earlier, and investigators found a damaged latch among the wreckage that refused to fit a simple explanation.

In this episode, we walk through the flight, the crew, the aircraft history and the physical evidence recovered from the scene, following the questions that remained after official reports: did a cargo door issue recur, and why did a seasoned crew lose control on a clear approach?

Person: Harry Baker, 59 years old, 16,382 total hours, 2,382 on DC‑8
Person: Tim Hupp, 37 years old, 5,082 total hours, 3,135 on DC‑8; pilot flying
Person: Jose Montalbo, 57 years old, 21,697 total hours, 7,697 on DC‑8
Person: Raman Patel, non‑revenue pilot aboard (Buffalo Airways)
Date: February 15, 1992
Event: Aircraft impacted 3 miles short of runway at 03:26; four fatalities

- Aircraft registration N794AL: Douglas DC‑8‑63F, serial number 45923, first flew 1968
- Airframe totals before accident: 70,084 flight hours and 22,804 cycles
- Prior incident: November 13, 1991 cargo door opened in flight at Toledo; warning indicator failed due to damaged wiring
- Wreckage recovered included seven cargo door latches from the field; one latch had lost its locking pins
- Cockpit Voice Recorder survived impact and was listened to by investigators as part of the inquiry

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.]]>943falsefullhttps://www.spreaker.com/episode/the-plane-that-vanished-in-three-minutes-and-41-seconds--73096775
The idea that every person on a burning jet could walk away is both terrifying and impossible-103 people survived an aircraft that “no longer existed” three minutes and 41 seconds after liftoff. Recorded wind readings showed a 20-knot easterly headwind, yet a sudden microburst struck the runway area unseen; how did routine weather data fail the crew and controller at the worst possible moment?

In this episode, we tell the sequence of events on July 31, 2018, from the aircraft’s history and crew composition to the sudden storm that overtook the runway, and ask how communication and authority breakdowns shaped the final minutes.

Person: Carlos Galván Meyran, 38, captain
Person: José Ramón Vázquez, first officer (not type-certified)
Person: Daniel Dardon Chávez, 25, observer (qualified first officer)
Date: July 31, 2018
Event: Aeroméxico Connect Flight 2431 crash following microburst-induced loss of control

- 103 people evacuated and survived after the aircraft was already burning.
- Aircraft had accumulated 27,257 flight hours and 18,200 cycles by that date.
- Last tower wind report at 15:18 reported winds 090° at 20 knots.
- Flight was cleared for departure at 15:21 while trees near the threshold were already snapping.
- First officer in control had 3,296 total hours but 0 hours in the Embraer 190 actual aircraft (64 hours simulator).

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/73096775Wed, 22 Jul 2026 01:04:31 +0000Creator at ObomediaThe Plane That Vanished in Three Minutes and 41 Seconds The idea that every person on a burning jet could walk away is both terrifying and impossible-103 people survived an aircraft that “no longer existed” three minutes and 41 seconds after...
The idea that every person on a burning jet could walk away is both terrifying and impossible-103 people survived an aircraft that “no longer existed” three minutes and 41 seconds after liftoff. Recorded wind readings showed a 20-knot easterly headwind, yet a sudden microburst struck the runway area unseen; how did routine weather data fail the crew and controller at the worst possible moment?

In this episode, we tell the sequence of events on July 31, 2018, from the aircraft’s history and crew composition to the sudden storm that overtook the runway, and ask how communication and authority breakdowns shaped the final minutes.

Person: Carlos Galván Meyran, 38, captain
Person: José Ramón Vázquez, first officer (not type-certified)
Person: Daniel Dardon Chávez, 25, observer (qualified first officer)
Date: July 31, 2018
Event: Aeroméxico Connect Flight 2431 crash following microburst-induced loss of control

- 103 people evacuated and survived after the aircraft was already burning.
- Aircraft had accumulated 27,257 flight hours and 18,200 cycles by that date.
- Last tower wind report at 15:18 reported winds 090° at 20 knots.
- Flight was cleared for departure at 15:21 while trees near the threshold were already snapping.
- First officer in control had 3,296 total hours but 0 hours in the Embraer 190 actual aircraft (64 hours simulator).

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