https://www.spreaker.com/podcast/air-disasters-the-black-box-files--7317291
Each episode rebuilds one flight in full, cinematic detail: the crew and their decisions, the machine and its hidden flaw, the seconds where routine turned into emergency, and the investigation that pieced the truth together from wreckage and data. No host chatting between clips, no panel debating theories. Just one complete story, narrated start to finish, built from cockpit voice recorders, accident reports, and the testimony of investigators.

You will fly through air disasters caused by a single frozen instrument, collisions built from a chain of tiny coincidences, and impossible landings that saved hundreds when everything had already failed. Some episodes follow the final minutes second by second; others follow the years-long investigations that changed how the world flies. All of them treat air disasters as what they really are: lessons written at terrible cost, and the reason flying keeps getting safer.

If you are drawn to air disasters told with rigor and humanity, this is built for you. New episodes drop regularly, each one a self-contained investigation. Subscribe now so the next of these air disasters lands the moment it goes live.]]>enAviationCopyright OBOMEDIA ENTERTAINMENThttps://d3wo5wojvuv7l.cloudfront.net/t_rss_itunes_square_1400/images.spreaker.com/original/8997e89180c6b30bf27473a7fe9bfc14.jpghttps://www.spreaker.com/podcast/air-disasters-the-black-box-files--7317291Sat, 05 Sep 2026 09:18:05 +0000OBOMEDIA ENTERTAINMENTOBOMEDIA ENTERTAINMENTcreators@obomedia.comAir disasters begin quietly: a sensor reading nobody trusts, a bolt torqued wrong on a night shift, two words misheard between cockpit and tower. This show reconstructs true air disasters from the black box outward, one flight at a time. Each episode...
Each episode rebuilds one flight in full, cinematic detail: the crew and their decisions, the machine and its hidden flaw, the seconds where routine turned into emergency, and the investigation that pieced the truth together from wreckage and data. No host chatting between clips, no panel debating theories. Just one complete story, narrated start to finish, built from cockpit voice recorders, accident reports, and the testimony of investigators.

You will fly through air disasters caused by a single frozen instrument, collisions built from a chain of tiny coincidences, and impossible landings that saved hundreds when everything had already failed. Some episodes follow the final minutes second by second; others follow the years-long investigations that changed how the world flies. All of them treat air disasters as what they really are: lessons written at terrible cost, and the reason flying keeps getting safer.

If you are drawn to air disasters told with rigor and humanity, this is built for you. New episodes drop regularly, each one a self-contained investigation. Subscribe now so the next of these air disasters lands the moment it goes live.]]>false48f74366-df27-525e-b5de-ab2c2c98a582episodichttps://www.spreaker.com/episode/the-twelve-volt-battery-call-that-started-a-race-against-time--74905958
The twelve‑volt battery call that started a race against time

In this episode, we lay out how a single mistranscribed word in 1986 sent two men to life imprisonment and tied into the investigation of Air India Flight 182. We describe the meetings, the recordings, and the decisions that shaped the case - and ask what else went wrong along the way.

Person: Frank Miele (alias "George")
Person: Billy Joe (informant)
Event: Air India Flight 182 bombing, June 23, 1985
Date: May 19 and May 22, 1986
Location: Bugged hotel room, Montreal

- A recorded hotel-room sting in Montreal became the prosecution’s central evidence after an undercover FBI operative discussed bombing planes.
- An informant named Billy Joe brokered the introduction in exchange for dropped charges for an associate.
- One meeting focused on a supposedly routine hardware call about a twelve‑volt battery that was later mistranslated by government translators.
- Khelsa attended the meetings over a disputed stolen Cadillac payment; Dhillon came as a protector of that money.
- Years of undisclosed government material and courtroom battles followed, leaving convictions unable to withstand later judicial review.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905958Sun, 06 Sep 2026 09:01:44 +0000OBOMEDIA ENTERTAINMENTA mistranslated call about a twelve-volt battery turns into an alleged bomb order - did they stop the plot before the plane left New York? The twelve‑volt battery call that started a race against time In this episode, we lay out how a single...
The twelve‑volt battery call that started a race against time

In this episode, we lay out how a single mistranscribed word in 1986 sent two men to life imprisonment and tied into the investigation of Air India Flight 182. We describe the meetings, the recordings, and the decisions that shaped the case - and ask what else went wrong along the way.

Person: Frank Miele (alias "George")
Person: Billy Joe (informant)
Event: Air India Flight 182 bombing, June 23, 1985
Date: May 19 and May 22, 1986
Location: Bugged hotel room, Montreal

- A recorded hotel-room sting in Montreal became the prosecution’s central evidence after an undercover FBI operative discussed bombing planes.
- An informant named Billy Joe brokered the introduction in exchange for dropped charges for an associate.
- One meeting focused on a supposedly routine hardware call about a twelve‑volt battery that was later mistranslated by government translators.
- Khelsa attended the meetings over a disputed stolen Cadillac payment; Dhillon came as a protector of that money.
- Years of undisclosed government material and courtroom battles followed, leaving convictions unable to withstand later judicial review.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1269falsefullhttps://www.spreaker.com/episode/the-overloaded-fuel-tanks-that-kept-them-climbing-did-they-make-it--74905957
The overloaded fuel tanks that kept them climbing-did they make it?

In this episode, we follow the night a DC-7 freighter departed Isla Verde for Nicaragua carrying relief supplies and a celebrity passenger determined to ensure delivery. The episode traces the decisions, the people aboard, and the mechanical and weight problems that compounded in the minutes after takeoff-could anything have been done differently?

Person: Roberto Clemente
Date: December 31, 1972
Location: Isla Verde International Airport, San Juan, Puerto Rico
Event: DC-7 freighter N500AE took off overloaded with cargo and fuel
Weight: Aircraft was 4,193 pounds over certified maximum takeoff weight

- Clemente organized relief flights after the Managua earthquake and decided to accompany a cargo flight himself to prevent diversion of supplies.
- The DC-7 freighter N500AE was loaded with relief goods, crewed by pilot Jerry Hill, co-pilot Arthur S. Rivera, and flight engineer Francisco Matias.
- The aircraft departed at 9:20:30 PM, airborne less than three minutes before the last cockpit transmission, "Coming back around."
- Investigators later found an engine had been broken for 29 days and had not been closely inspected before the flight.
- To land safely after takeoff, the crew would have needed to dump roughly 32,000 pounds of fuel given the aircraft's overloaded condition.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905957Sat, 05 Sep 2026 09:01:57 +0000OBOMEDIA ENTERTAINMENTRoberto Clemente boards an overloaded DC-7 cargo flight out of San Juan with relief supplies for Managua - did they make it in time? The overloaded fuel tanks that kept them climbing-did they make it? In this episode, we follow the night a DC-7...
The overloaded fuel tanks that kept them climbing-did they make it?

In this episode, we follow the night a DC-7 freighter departed Isla Verde for Nicaragua carrying relief supplies and a celebrity passenger determined to ensure delivery. The episode traces the decisions, the people aboard, and the mechanical and weight problems that compounded in the minutes after takeoff-could anything have been done differently?

Person: Roberto Clemente
Date: December 31, 1972
Location: Isla Verde International Airport, San Juan, Puerto Rico
Event: DC-7 freighter N500AE took off overloaded with cargo and fuel
Weight: Aircraft was 4,193 pounds over certified maximum takeoff weight

- Clemente organized relief flights after the Managua earthquake and decided to accompany a cargo flight himself to prevent diversion of supplies.
- The DC-7 freighter N500AE was loaded with relief goods, crewed by pilot Jerry Hill, co-pilot Arthur S. Rivera, and flight engineer Francisco Matias.
- The aircraft departed at 9:20:30 PM, airborne less than three minutes before the last cockpit transmission, "Coming back around."
- Investigators later found an engine had been broken for 29 days and had not been closely inspected before the flight.
- To land safely after takeoff, the crew would have needed to dump roughly 32,000 pounds of fuel given the aircraft's overloaded condition.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1281falsefullhttps://www.spreaker.com/episode/the-outer-wing-section-lodged-in-shallows-stalled-the-search-clock--74905956
The outer wing section lodged in shallows stalled the search clock

In this episode, the story follows the disappearance of Ansett‑ANA Flight 325 on the night of 30 November 1961 and the early search that raced against time and weather. What the intact outer wing in shallow water and the pulverized main wreckage a mile away reveal about those final nine minutes becomes the central dilemma listeners must grapple with.

Event: Aircraft disappearance over Sydney night of 30 November 1961
Aircraft: Vickers Viscount, name John Oxley, 12,010 flights, 16,946 hours
People: 15 onboard - Captain Stan Lindsay, Co‑pilot Ben Costello, attendants Aileen Keldie and Elizabeth Hardy
Location: Botany Bay and Kurnell Beach area, 2.8 miles southeast of Sydney Airport
Status: No flight recorders; wreckage both intact and heavily fragmented

- The flight departed Sydney at 19:17 for Canberra with a routine eastward climb and a required crossing at 5,000 feet.
- At 19:22 the crew reported 6,000 feet, and three minutes later controllers received no further responses.
- Dawn searches initially scoured the Tasman Sea east of the airport, assuming the aircraft had stayed on its outbound track.
- Searchers then found cabin debris and an outer right wing section protruding from shallow water near Kurnell with registration still legible.
- The main wreckage lay 25 feet underwater and scattered across more than a mile of bay floor, presenting a stark contrast to the nearly undamaged wing.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905956Fri, 04 Sep 2026 18:43:03 +0000OBOMEDIA ENTERTAINMENTA wing section juts from Botany Bay while the rest lies underwater-did search crews reach the wreckage in time? The outer wing section lodged in shallows stalled the search clock In this episode, the story follows the disappearance of Ansett‑ANA...
The outer wing section lodged in shallows stalled the search clock

In this episode, the story follows the disappearance of Ansett‑ANA Flight 325 on the night of 30 November 1961 and the early search that raced against time and weather. What the intact outer wing in shallow water and the pulverized main wreckage a mile away reveal about those final nine minutes becomes the central dilemma listeners must grapple with.

Event: Aircraft disappearance over Sydney night of 30 November 1961
Aircraft: Vickers Viscount, name John Oxley, 12,010 flights, 16,946 hours
People: 15 onboard - Captain Stan Lindsay, Co‑pilot Ben Costello, attendants Aileen Keldie and Elizabeth Hardy
Location: Botany Bay and Kurnell Beach area, 2.8 miles southeast of Sydney Airport
Status: No flight recorders; wreckage both intact and heavily fragmented

- The flight departed Sydney at 19:17 for Canberra with a routine eastward climb and a required crossing at 5,000 feet.
- At 19:22 the crew reported 6,000 feet, and three minutes later controllers received no further responses.
- Dawn searches initially scoured the Tasman Sea east of the airport, assuming the aircraft had stayed on its outbound track.
- Searchers then found cabin debris and an outer right wing section protruding from shallow water near Kurnell with registration still legible.
- The main wreckage lay 25 feet underwater and scattered across more than a mile of bay floor, presenting a stark contrast to the nearly undamaged wing.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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/the-lone-walker-who-climbed-the-range-found-them-after-nine-days--74905955
The lone walker who climbed the range found them after nine days

In this episode, we follow the routine Sydney-Brisbane flight that vanished over the McPherson Range and the slow, misdirected official search that failed to find it. The story traces the aircraft, its crew and passengers, the lack of radio, and the lone man who set out on foot-what compelled him to walk into those mountains and what he discovered there?

Date: 19 February 1937
Aircraft: Stinson Model A trimotor VH-UHH (Brisbane)
Crew: Reginald Haslam “Rex” Boyden (pilot), Beverley Shepherd (first officer)
Passengers: Joseph Binstead; John Seymour Proud; James Westray; William Walden Fountain; James Westray Graham
Location: McPherson Range, border of Queensland and New South Wales

- The Brisbane departed Archerfield after 1pm on 19 February 1937 on the inland Sydney-Brisbane route and was due at 4:30pm.
- VH-UHH carried no radio; Boyden and Shepherd had only basic Morse proficiency and could not send a distress signal.
- Witnesses heard the aircraft circling near Lamington and Hill View around 1:40pm before it turned toward the McPherson Range and vanished.
- The Royal Australian Air Force flew four aircraft searching north along a coastal corridor while the McPherson Range was not thoroughly searched.
- On the tenth day after the crash one man walked into the mountains alone, reasoning his way to where the wreckage might be despite having no official backing.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905955Fri, 04 Sep 2026 18:42:58 +0000OBOMEDIA ENTERTAINMENTA lone walker climbs the McPherson Range searching for a missing Stinson trimotor and the two men he hopes to find-did he reach the wreck in time? The lone walker who climbed the range found them after nine days In this episode, we follow the...
The lone walker who climbed the range found them after nine days

In this episode, we follow the routine Sydney-Brisbane flight that vanished over the McPherson Range and the slow, misdirected official search that failed to find it. The story traces the aircraft, its crew and passengers, the lack of radio, and the lone man who set out on foot-what compelled him to walk into those mountains and what he discovered there?

Date: 19 February 1937
Aircraft: Stinson Model A trimotor VH-UHH (Brisbane)
Crew: Reginald Haslam “Rex” Boyden (pilot), Beverley Shepherd (first officer)
Passengers: Joseph Binstead; John Seymour Proud; James Westray; William Walden Fountain; James Westray Graham
Location: McPherson Range, border of Queensland and New South Wales

- The Brisbane departed Archerfield after 1pm on 19 February 1937 on the inland Sydney-Brisbane route and was due at 4:30pm.
- VH-UHH carried no radio; Boyden and Shepherd had only basic Morse proficiency and could not send a distress signal.
- Witnesses heard the aircraft circling near Lamington and Hill View around 1:40pm before it turned toward the McPherson Range and vanished.
- The Royal Australian Air Force flew four aircraft searching north along a coastal corridor while the McPherson Range was not thoroughly searched.
- On the tenth day after the crash one man walked into the mountains alone, reasoning his way to where the wreckage might be despite having no official backing.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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-non-precision-approach-he-chose-burned-ten-minutes-of-guided-descent--74905954
The non‑precision approach he chose burned ten minutes of guided descent

In this episode, we follow the flight into Durango on January 19, 1988, and the decisions and conditions that preceded the crash. The narrative lays out who was flying, what options were offered, and the gaps investigators had to work around - so what critical choices determined the final minutes?

Date: January 19, 1988
Location: Durango-La Plata County Airport, Colorado
Aircraft: Fairchild Metro III, N68TC
Persons: Captain Stephen S. Silver; First Officer Ralph D. Harvey
Weather: Ceiling 800 feet, light snow, fog

- At 19:14 the Metro descended toward Durango at 3,000 fpm while the published procedure called for 900 fpm, and no one in the cockpit corrected the rate.
- Air traffic offered two approaches: a precision ILS that added about ten minutes of guided vertical guidance, or a direct non‑precision approach to Runway 20; Silver chose the non‑precision.
- Silver handed controls to First Officer Harvey after choosing Runway 20, removing continuous electronic vertical guidance and replacing it with altitude checks at waypoints.
- No cockpit voice recorder or flight data recorder was on board, so investigators relied on radar returns, radio transcripts, wreckage distribution, and toxicology.
- Toxicology showed cocaine and metabolites in Captain Silver consistent with use 12-18 hours before impact, and a woman who might explain that timing was never located or interviewed.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905954Fri, 04 Sep 2026 18:42:55 +0000OBOMEDIA ENTERTAINMENTA captain with cocaine chooses a risky approach into mountainous Durango on a foggy night-did they make it in time? The non‑precision approach he chose burned ten minutes of guided descent In this episode, we follow the flight into Durango on...
The non‑precision approach he chose burned ten minutes of guided descent

In this episode, we follow the flight into Durango on January 19, 1988, and the decisions and conditions that preceded the crash. The narrative lays out who was flying, what options were offered, and the gaps investigators had to work around - so what critical choices determined the final minutes?

Date: January 19, 1988
Location: Durango-La Plata County Airport, Colorado
Aircraft: Fairchild Metro III, N68TC
Persons: Captain Stephen S. Silver; First Officer Ralph D. Harvey
Weather: Ceiling 800 feet, light snow, fog

- At 19:14 the Metro descended toward Durango at 3,000 fpm while the published procedure called for 900 fpm, and no one in the cockpit corrected the rate.
- Air traffic offered two approaches: a precision ILS that added about ten minutes of guided vertical guidance, or a direct non‑precision approach to Runway 20; Silver chose the non‑precision.
- Silver handed controls to First Officer Harvey after choosing Runway 20, removing continuous electronic vertical guidance and replacing it with altitude checks at waypoints.
- No cockpit voice recorder or flight data recorder was on board, so investigators relied on radar returns, radio transcripts, wreckage distribution, and toxicology.
- Toxicology showed cocaine and metabolites in Captain Silver consistent with use 12-18 hours before impact, and a woman who might explain that timing was never located or interviewed.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1204falsefullhttps://www.spreaker.com/episode/the-arthur-unit-failed-and-controls-went-light-did-they-reach-the-runway--74905952
The ARTHUR unit failed and controls went light - did they reach the runway?

In this episode, we follow the flight that landed at Bucharest while seven people inside died under unexplained forces. The episode lays out the sequence of events, the broken cockpit voice recorder, and the technical failures that turned a routine approach into a catastrophe-what exactly happened in those twenty-four seconds?

Date: September 14, 1999
Aircraft: Dassault Falcon
Location: Bucharest airport, runway 08
Event: Severe cabin forces during final approach
System: ARTHUR control-feel unit malfunctioning prior to flight

- Passengers aboard included Greece’s Deputy Minister of Foreign Affairs Giannos Kranidiotis and his son, ERT journalists, security, and an aircraft engineer.
- During the descent the fasten-seat-belt sign was not activated and many occupants were unbuckled as the aircraft began oscillating.
- In twenty-four seconds the aircraft experienced ten pitch oscillations that produced forces near twice design limits, ripping seats and panels.
- The cockpit voice recorder was broken before departure, limiting investigators’ ability to know pilot communications during the event.
- The flight data showed the controls became almost weightless without ARTHUR, and the unit had been malfunctioning for some time before the Bucharest 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/74905952Fri, 04 Sep 2026 18:42:50 +0000OBOMEDIA ENTERTAINMENTA Dassault Falcon descends toward Bucharest with a failed ARTHUR system and unbuckled passengers-did they reach the runway in time? The ARTHUR unit failed and controls went light - did they reach the runway? In this episode, we follow the flight...
The ARTHUR unit failed and controls went light - did they reach the runway?

In this episode, we follow the flight that landed at Bucharest while seven people inside died under unexplained forces. The episode lays out the sequence of events, the broken cockpit voice recorder, and the technical failures that turned a routine approach into a catastrophe-what exactly happened in those twenty-four seconds?

Date: September 14, 1999
Aircraft: Dassault Falcon
Location: Bucharest airport, runway 08
Event: Severe cabin forces during final approach
System: ARTHUR control-feel unit malfunctioning prior to flight

- Passengers aboard included Greece’s Deputy Minister of Foreign Affairs Giannos Kranidiotis and his son, ERT journalists, security, and an aircraft engineer.
- During the descent the fasten-seat-belt sign was not activated and many occupants were unbuckled as the aircraft began oscillating.
- In twenty-four seconds the aircraft experienced ten pitch oscillations that produced forces near twice design limits, ripping seats and panels.
- The cockpit voice recorder was broken before departure, limiting investigators’ ability to know pilot communications during the event.
- The flight data showed the controls became almost weightless without ARTHUR, and the unit had been malfunctioning for some time before the Bucharest 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.]]>1118falsefullhttps://www.spreaker.com/episode/the-loose-lock-nut-that-let-the-bolt-rotate-cost-them-their-return-fuel--74905951
The loose lock nut that let the bolt rotate cost them their return fuel

In this episode, we follow the flight crew of Hapag-Lloyd Flight D‑AHLB from Chania as a maintenance error turns routine summer rotations into an escalating crisis. We trace the technical faults, cockpit choices, and communication gaps that turned ten millimeters of rotation into a life‑threatening fuel problem and ask what decisions could have changed the course of the flight.

Aircraft: Airbus A310-300 D-AHLB
Date: July 12, 2000
People: Captain Wolfgang Arminger; First Officer Thorsten Rökrath; 151 on board
Event: Landing gear failed to retract after takeoff
Location: Chania (Crete) to Hannover, over Adriatic and Austrian airspace

- A single lock nut left improperly secured during maintenance allowed a bolt to rotate ten millimeters, preventing the right landing gear from retracting.
- The crew attempted gear retraction four times; cockpit indicated "gear unsafe" and "door open" each time while drag increased fuel burn.
- The Flight Management System was not updated for extended-gear drag and calculated fuel as if the aircraft were clean, producing reassuring but inaccurate numbers.
- The airline's HF link to operations was unavailable, forcing the crew to rely on slower ATC relays for coordination and advice during the unfolding problem.
- At 12:34 the FMS showed 1.9 tonnes of fuel remaining at Vienna and company rules mandated diversion below the threshold; an alternate like Zagreb was ten minutes away.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905951Fri, 04 Sep 2026 18:42:47 +0000OBOMEDIA ENTERTAINMENTA loose lock nut left the A310's left gear stuck after takeoff from Crete - the crew raced a hidden fuel countdown toward Hannover; did they make it? The loose lock nut that let the bolt rotate cost them their return fuel In this episode, we...
The loose lock nut that let the bolt rotate cost them their return fuel

In this episode, we follow the flight crew of Hapag-Lloyd Flight D‑AHLB from Chania as a maintenance error turns routine summer rotations into an escalating crisis. We trace the technical faults, cockpit choices, and communication gaps that turned ten millimeters of rotation into a life‑threatening fuel problem and ask what decisions could have changed the course of the flight.

Aircraft: Airbus A310-300 D-AHLB
Date: July 12, 2000
People: Captain Wolfgang Arminger; First Officer Thorsten Rökrath; 151 on board
Event: Landing gear failed to retract after takeoff
Location: Chania (Crete) to Hannover, over Adriatic and Austrian airspace

- A single lock nut left improperly secured during maintenance allowed a bolt to rotate ten millimeters, preventing the right landing gear from retracting.
- The crew attempted gear retraction four times; cockpit indicated "gear unsafe" and "door open" each time while drag increased fuel burn.
- The Flight Management System was not updated for extended-gear drag and calculated fuel as if the aircraft were clean, producing reassuring but inaccurate numbers.
- The airline's HF link to operations was unavailable, forcing the crew to rely on slower ATC relays for coordination and advice during the unfolding problem.
- At 12:34 the FMS showed 1.9 tonnes of fuel remaining at Vienna and company rules mandated diversion below the threshold; an alternate like Zagreb was ten minutes away.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1398falsefullhttps://www.spreaker.com/episode/the-stopped-wristwatches-that-locked-the-clock-at-3-15-did-they-make-it--74905950
The stopped wristwatches that locked the clock at 3:15 - did they make it?

In this episode, we lay out the flight, the crew and the unexplained fifty-five-minute gap between a routine radio call and the moment every recovered wristwatch stopped at 3:15. What happened in those missing minutes over Parley’s Canyon that left investigators without a definitive answer?

Date: February 23, 1934
Aircraft: Boeing 247 registration NC13357
Person: Lloyd Anderson (captain), Eric Danielson (co-pilot), Miss Carter (stewardess), John J. Sterling (passenger mayor)
Location: Parley's Canyon, Utah

- The flight departed Salt Lake City at 2:00 PM bound for Cheyenne amid falling snow and sleet.
- At 2:20 PM the captain radioed a single professional message: "All okay."
- Seventy-five minutes after takeoff the aircraft struck the canyon three-quarters of a mile past the summit in a near-vertical, nose-first impact.
- Eight wristwatches recovered from the wreckage were all stopped at exactly 3:15 PM, synchronized to the minute.
- Two official investigations examined the crash and returned without a single definitive explanation.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905950Fri, 04 Sep 2026 18:42:43 +0000OBOMEDIA ENTERTAINMENTA Boeing 247 climbs into a snowbound Utah canyon and stops transmitting; eight wristwatches all stop at 3:15 - did they make it in time? The stopped wristwatches that locked the clock at 3:15 - did they make it? In this episode, we lay out the...
The stopped wristwatches that locked the clock at 3:15 - did they make it?

In this episode, we lay out the flight, the crew and the unexplained fifty-five-minute gap between a routine radio call and the moment every recovered wristwatch stopped at 3:15. What happened in those missing minutes over Parley’s Canyon that left investigators without a definitive answer?

Date: February 23, 1934
Aircraft: Boeing 247 registration NC13357
Person: Lloyd Anderson (captain), Eric Danielson (co-pilot), Miss Carter (stewardess), John J. Sterling (passenger mayor)
Location: Parley's Canyon, Utah

- The flight departed Salt Lake City at 2:00 PM bound for Cheyenne amid falling snow and sleet.
- At 2:20 PM the captain radioed a single professional message: "All okay."
- Seventy-five minutes after takeoff the aircraft struck the canyon three-quarters of a mile past the summit in a near-vertical, nose-first impact.
- Eight wristwatches recovered from the wreckage were all stopped at exactly 3:15 PM, synchronized to the minute.
- Two official investigations examined the crash and returned without a single definitive explanation.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1265falsefullhttps://www.spreaker.com/episode/the-autothrottle-that-slammed-to-idle-did-they-regain-the-climb--74905949
The autothrottle that slammed to idle - did they regain the climb?

In this episode, we follow a TAROM A310 that lifted off Otopeni on March 31, 1995, and the unfolding minutes when a known autothrottle fault, a pilot suddenly feeling ill, and a change of control collide. Who will hold the throttles, and what happens in the seconds nobody is flying the plane?

Date: March 31, 1995
Location: Bucharest Otopeni Airport
Aircraft: Airbus A310-300, registration YR-LCC
Event: Autothrottle retracted to idle on engine one during climb
Person: Capt. Liviu Bătănoiu (pilot monitoring), First Officer Ionel Stoi (pilot flying)

- Takeoff occurred at 09:06:44 with Stoi as pilot flying and Bătănoiu monitoring the throttles.
- A known fault allowed excessive friction in the autothrottle kinematic linkage to pull engine one to idle during climb.
- Bătănoiu had briefed he would personally guard the throttles; his plan lasted ninety-four seconds.
- During flap retraction, Bătănoiu reported feeling sick and groaned as control actions unfolded in the cockpit.
- For twenty-seven seconds after takeoff, cockpit recordings show no one actively flying 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/74905949Fri, 04 Sep 2026 18:42:40 +0000OBOMEDIA ENTERTAINMENTAn autothrottle in a climb slams to idle sixty seconds after takeoff from Bucharest - can the two-man cockpit regain control before it's too late? The autothrottle that slammed to idle - did they regain the climb? In this episode, we follow a...
The autothrottle that slammed to idle - did they regain the climb?

In this episode, we follow a TAROM A310 that lifted off Otopeni on March 31, 1995, and the unfolding minutes when a known autothrottle fault, a pilot suddenly feeling ill, and a change of control collide. Who will hold the throttles, and what happens in the seconds nobody is flying the plane?

Date: March 31, 1995
Location: Bucharest Otopeni Airport
Aircraft: Airbus A310-300, registration YR-LCC
Event: Autothrottle retracted to idle on engine one during climb
Person: Capt. Liviu Bătănoiu (pilot monitoring), First Officer Ionel Stoi (pilot flying)

- Takeoff occurred at 09:06:44 with Stoi as pilot flying and Bătănoiu monitoring the throttles.
- A known fault allowed excessive friction in the autothrottle kinematic linkage to pull engine one to idle during climb.
- Bătănoiu had briefed he would personally guard the throttles; his plan lasted ninety-four seconds.
- During flap retraction, Bătănoiu reported feeling sick and groaned as control actions unfolded in the cockpit.
- For twenty-seven seconds after takeoff, cockpit recordings show no one actively flying 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.]]>1295falsefullhttps://www.spreaker.com/episode/the-ahrs-went-dead-twenty-eight-seconds-to-the-mountain--74905948
The AHRS went dead - twenty‑eight seconds to the mountain

In this episode, you hear how a routine evening flight became a race against one instrument and one ticking countdown. We trace the crew's decisions, the skipped steps, and the moment the aircraft climbed into cloud toward the Andes - what happened next hangs on twenty‑eight seconds.

Date: February 21, 2008
Aircraft: ATR 42, registration YV‑1449
Person: Captain Aldino Garanito Gómez, 36, >5,000 flight hours
Person: First Officer Denis Ferreira Quintal, 29, >2,000 flight hours
Event: AHRS failure during departure from Alberto Carnevalli Airport

- Crew delayed boarding while still in the terminal, taking time for coffee before reaching the cockpit.
- The flight was the last scheduled departure of the day from Mérida to Caracas, a night departure prohibited by regulation.
- The AHRS (Attitude and Heading Reference System) stopped providing attitude and heading during climb in cloud at dusk.
- The captain was an experienced flight instructor familiar with the airport’s surrounding peaks and steep terrain.
- The aircraft impacted La Cara del Indio approximately ten kilometers from the runway at 4,000 meters 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/74905948Fri, 04 Sep 2026 18:42:36 +0000OBOMEDIA ENTERTAINMENTA senior captain ignores a failing AHRS during a dusk mountain departure from Mérida with forty‑six lives on board - did they make it in time? The AHRS went dead - twenty‑eight seconds to the mountain In this episode, you hear how a routine...
The AHRS went dead - twenty‑eight seconds to the mountain

In this episode, you hear how a routine evening flight became a race against one instrument and one ticking countdown. We trace the crew's decisions, the skipped steps, and the moment the aircraft climbed into cloud toward the Andes - what happened next hangs on twenty‑eight seconds.

Date: February 21, 2008
Aircraft: ATR 42, registration YV‑1449
Person: Captain Aldino Garanito Gómez, 36, >5,000 flight hours
Person: First Officer Denis Ferreira Quintal, 29, >2,000 flight hours
Event: AHRS failure during departure from Alberto Carnevalli Airport

- Crew delayed boarding while still in the terminal, taking time for coffee before reaching the cockpit.
- The flight was the last scheduled departure of the day from Mérida to Caracas, a night departure prohibited by regulation.
- The AHRS (Attitude and Heading Reference System) stopped providing attitude and heading during climb in cloud at dusk.
- The captain was an experienced flight instructor familiar with the airport’s surrounding peaks and steep terrain.
- The aircraft impacted La Cara del Indio approximately ten kilometers from the runway at 4,000 meters 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.]]>1378falsefullhttps://www.spreaker.com/episode/the-missing-backup-battery-died-with-the-instruments-did-they-land--74905942
The missing backup battery died with the instruments - did they land?

In this episode, we follow a routine Hannover-Düsseldorf morning flight where every procedural check looked normal until the aircraft entered a storm and the instruments lost power. The story tracks the crew, the aircraft's equipment, the weather briefing gaps, and the seconds that led from stability to catastrophe - could the pilots regain control?

Person: Captain Ralf Borsdorf
Person: First Officer Sibylle Heilmann
Aircraft: D‑CABB, Swearingen Fairchild Metroliner III
Date: February 8, 1988
Route: Hannover to Düsseldorf

- Captain Borsdorf had ~2,500 total hours and 277 on the Metroliner III, with recent simulator training covering electrical emergencies.
- First Officer Heilmann had ~2,500 total hours and over 1,300 hours on type, giving her deeper hands‑on experience with the Metroliner III.
- The aircraft had all required instruments, autopilot, weather radar and a third artificial horizon, but no emergency electrical backup battery or generator.
- Forecasts noted a 10% chance of heavy thunderstorms and moderate‑to‑severe turbulence below 5,000 ft; Hannover’s overnight weather station had been unstaffed during critical development of the front.
- After takeoff the crew flew with ATIS wind reports from Hannover; witnesses later saw the aircraft enter a steep bank, level, climb into the storm three times, then suffer structural failure.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905942Fri, 04 Sep 2026 18:42:30 +0000OBOMEDIA ENTERTAINMENTA regional Metroliner enters a brewing thunderstorm with all instruments alive-two minutes later, every instrument dies; did they land? The missing backup battery died with the instruments - did they land? In this episode, we follow a routine...
The missing backup battery died with the instruments - did they land?

In this episode, we follow a routine Hannover-Düsseldorf morning flight where every procedural check looked normal until the aircraft entered a storm and the instruments lost power. The story tracks the crew, the aircraft's equipment, the weather briefing gaps, and the seconds that led from stability to catastrophe - could the pilots regain control?

Person: Captain Ralf Borsdorf
Person: First Officer Sibylle Heilmann
Aircraft: D‑CABB, Swearingen Fairchild Metroliner III
Date: February 8, 1988
Route: Hannover to Düsseldorf

- Captain Borsdorf had ~2,500 total hours and 277 on the Metroliner III, with recent simulator training covering electrical emergencies.
- First Officer Heilmann had ~2,500 total hours and over 1,300 hours on type, giving her deeper hands‑on experience with the Metroliner III.
- The aircraft had all required instruments, autopilot, weather radar and a third artificial horizon, but no emergency electrical backup battery or generator.
- Forecasts noted a 10% chance of heavy thunderstorms and moderate‑to‑severe turbulence below 5,000 ft; Hannover’s overnight weather station had been unstaffed during critical development of the front.
- After takeoff the crew flew with ATIS wind reports from Hannover; witnesses later saw the aircraft enter a steep bank, level, climb into the storm three times, then suffer structural failure.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1263falsefullhttps://www.spreaker.com/episode/the-brake-mark-that-held-the-yak-42-to-the-runway-did-they-get-airborne--74905941
The brake mark that held the Yak‑42 to the runway - did they get airborne?

In this episode, we follow the takeoff roll, the crew, and the moments on Tunoshna’s runway that preceded a flight that should have climbed but didn't. We trace the aircraft, its passengers, and the puzzling brake mark that suggested deliberate braking-did anyone act in time?

Date: September 7, 2011
Aircraft: Yakovlev Yak-42 RA-42434
Location: Tunoshna Airport, Yaroslavl
People on board: 26 players, 2 coaches, 4 crew/passengers
Runway length: 2,700 meters

- The Yak-42 used the entire 2,700 m runway, reached 230 km/h and still crossed the pavement before lifting off.
- The aircraft finally left the ground 400 meters beyond the runway end and climbed only 5-6 meters at a 20° nose angle.
- Wreckage and flight recorders were recovered; the debris field stretched nearly two kilometers along the Tunoshonka riverbank.
- A 100-meter brake mark in the takeoff zone suggested deliberate braking force applied during the roll.
- The crew included Captain Andrei Solomentsev (6,900 hours), First Officer Igor Zhevelov (13,500 hours), and Flight Engineer Sergei Zhuravlev.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905941Fri, 04 Sep 2026 18:42:26 +0000OBOMEDIA ENTERTAINMENTA Yak-42 thunders down Tunoshna’s runway - something held its wheels to the ground; did they make it airborne? The brake mark that held the Yak‑42 to the runway - did they get airborne? In this episode, we follow the takeoff roll, the crew, and...
The brake mark that held the Yak‑42 to the runway - did they get airborne?

In this episode, we follow the takeoff roll, the crew, and the moments on Tunoshna’s runway that preceded a flight that should have climbed but didn't. We trace the aircraft, its passengers, and the puzzling brake mark that suggested deliberate braking-did anyone act in time?

Date: September 7, 2011
Aircraft: Yakovlev Yak-42 RA-42434
Location: Tunoshna Airport, Yaroslavl
People on board: 26 players, 2 coaches, 4 crew/passengers
Runway length: 2,700 meters

- The Yak-42 used the entire 2,700 m runway, reached 230 km/h and still crossed the pavement before lifting off.
- The aircraft finally left the ground 400 meters beyond the runway end and climbed only 5-6 meters at a 20° nose angle.
- Wreckage and flight recorders were recovered; the debris field stretched nearly two kilometers along the Tunoshonka riverbank.
- A 100-meter brake mark in the takeoff zone suggested deliberate braking force applied during the roll.
- The crew included Captain Andrei Solomentsev (6,900 hours), First Officer Igor Zhevelov (13,500 hours), and Flight Engineer Sergei Zhuravlev.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1267falsefullhttps://www.spreaker.com/episode/the-vertical-speed-knob-pulled-the-a320-off-glidepath-would-they-make-it--74905939
The vertical-speed knob pulled the A320 off glidepath-would they make it?

In this episode, we follow Indian Airlines Flight 605’s final minutes as crew choices, cockpit layout and unfamiliarity with the A320’s fly-by-wire logic interact during a clear, visual approach into Bangalore. The episode tracks the sequence of decisions and actions that put the aircraft below the intended path and asks whether the pilots’ responses were enough to save the landing.

Date: February 14, 1990
Aircraft: Airbus A320 VT-EPN
Person: Captain Cyril Fernandez (46), First Officer Satish Gopujkar (44)
Event: Visual approach to Bangalore Runway 09
Passengers on board: 146

- The aircraft was five months old with about 370 flight hours and fully functional systems at departure.
- Fernandez was undergoing his first required A320 route check with just 68 hours on type; Gopujkar acted as both co-pilot and check pilot.
- On final approach the crew were high; Fernandez requested a go-around but chose vertical speed mode instead, calling for 1,000 fpm.
- The A320’s fly-by-wire system mediates pilot inputs and enforces flight-envelope logic, requiring different handling than conventional jets.
- Two nearly identical knobs sit side-by-side on the Flight Control Unit; one selected by hand set the aircraft on a wrong trajectory during those critical 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/74905939Fri, 04 Sep 2026 18:42:22 +0000OBOMEDIA ENTERTAINMENTA five-month-old A320 drifts off glidepath after a pilot twists a cockpit knob during a Bangalore visual approach - did they make it in time? The vertical-speed knob pulled the A320 off glidepath-would they make it? In this episode, we follow...
The vertical-speed knob pulled the A320 off glidepath-would they make it?

In this episode, we follow Indian Airlines Flight 605’s final minutes as crew choices, cockpit layout and unfamiliarity with the A320’s fly-by-wire logic interact during a clear, visual approach into Bangalore. The episode tracks the sequence of decisions and actions that put the aircraft below the intended path and asks whether the pilots’ responses were enough to save the landing.

Date: February 14, 1990
Aircraft: Airbus A320 VT-EPN
Person: Captain Cyril Fernandez (46), First Officer Satish Gopujkar (44)
Event: Visual approach to Bangalore Runway 09
Passengers on board: 146

- The aircraft was five months old with about 370 flight hours and fully functional systems at departure.
- Fernandez was undergoing his first required A320 route check with just 68 hours on type; Gopujkar acted as both co-pilot and check pilot.
- On final approach the crew were high; Fernandez requested a go-around but chose vertical speed mode instead, calling for 1,000 fpm.
- The A320’s fly-by-wire system mediates pilot inputs and enforces flight-envelope logic, requiring different handling than conventional jets.
- Two nearly identical knobs sit side-by-side on the Flight Control Unit; one selected by hand set the aircraft on a wrong trajectory during those critical 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.]]>1254falsefullhttps://www.spreaker.com/episode/the-seventeen-foot-flare-that-left-them-racing-the-runway--74905938
The seventeen-foot flare that left them racing the runway

In this episode, we reconstruct the final seconds of FedEx flight N611FE's landing at Newark on July 31, 1997, tracking the decisions, mechanical issues, and timing that led from flare to disaster. What choices in those last moments changed everything?

Person: Captain Robert Freeman
Person: First Officer Donald Goodin
Date: July 31, 1997
Aircraft: McDonnell Douglas MD‑11, registration N611FE
Event: Landing flare at 17 feet with three preexisting mechanical issues

- The jet, nicknamed Joshua, had 13,034 flight hours and 2,950 pressurization cycles and had prior hard‑landing and tail‑strike repairs.
- Three mechanical problems were documented before dispatch: left thrust reverser inoperative, recurring autobrake failures, and a misread runway distance calculation.
- Captain Freeman, a 46‑year‑old FedEx pilot with 11,000 total hours and 1,253 on the MD‑11, aimed to touchdown early because he believed stopping distance was limited.
- First Officer Goodin, a 39‑year‑old USAF veteran with 95 hours on the MD‑11, was in the right seat during the transpacific flight that had come via Singapore, Penang, Taipei, and Anchorage.
- At 17 feet above the runway the flare began; four seconds later the aircraft hit the ground, twelve seconds after that it flipped and caught fire.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905938Fri, 04 Sep 2026 18:42:18 +0000OBOMEDIA ENTERTAINMENTA cargo MD‑11 named Joshua flares at seventeen feet above Newark with known mechanical faults and a crew racing the runway - did they make it in time? The seventeen-foot flare that left them racing the runway In this episode, we reconstruct the...
The seventeen-foot flare that left them racing the runway

In this episode, we reconstruct the final seconds of FedEx flight N611FE's landing at Newark on July 31, 1997, tracking the decisions, mechanical issues, and timing that led from flare to disaster. What choices in those last moments changed everything?

Person: Captain Robert Freeman
Person: First Officer Donald Goodin
Date: July 31, 1997
Aircraft: McDonnell Douglas MD‑11, registration N611FE
Event: Landing flare at 17 feet with three preexisting mechanical issues

- The jet, nicknamed Joshua, had 13,034 flight hours and 2,950 pressurization cycles and had prior hard‑landing and tail‑strike repairs.
- Three mechanical problems were documented before dispatch: left thrust reverser inoperative, recurring autobrake failures, and a misread runway distance calculation.
- Captain Freeman, a 46‑year‑old FedEx pilot with 11,000 total hours and 1,253 on the MD‑11, aimed to touchdown early because he believed stopping distance was limited.
- First Officer Goodin, a 39‑year‑old USAF veteran with 95 hours on the MD‑11, was in the right seat during the transpacific flight that had come via Singapore, Penang, Taipei, and Anchorage.
- At 17 feet above the runway the flare began; four seconds later the aircraft hit the ground, twelve seconds after that it flipped and caught fire.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1247falsefullhttps://www.spreaker.com/episode/the-approach-lights-clipped-the-plane-did-they-make-it--74905937
The approach lights clipped the plane - did they make it?

In this episode, we follow Commonwealth Commuter Flight 317 from its January 6, 1974 departure in Pittsburgh through the final minutes before impact, focusing on the crew, the approach, and the unanswered questions that led to a crash short of the runway. What choices, procedures, and mechanical factors set the flight on that descent toward the embankment?

Date: January 6, 1974
Aircraft: Beechcraft Model 99A, N125AE
Flight: Commonwealth Commuter Flight 317
Person: Captain Daniel Brannon; First Officer Gerald Knouff
Location: Ten miles short of Johnstown, Pennsylvania (approach to Runway 33)

- Flight departed Pittsburgh around 6:30 PM on a short commuter hop to Johnstown with 15 people aboard.
- Captain Brannon logged 6,331 flight hours and was described as meticulous; his co-pilot later reported a habit of flying slower than published approach speeds.
- Conditions were instrument-rated, the approach lighting system was operating, and runway 33 was the intended landing.
- The aircraft first struck elevated approach lights, crossed U.S. Route 219 beneath the approach corridor, then impacted the top of a steep embankment nose-up.
- The impact tore the nose from the fuselage, ejected parts of the aircraft up to 75 yards, destroyed floor anchor points while seatbelts remained fastened.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905937Fri, 04 Sep 2026 18:42:14 +0000OBOMEDIA ENTERTAINMENTA commuter plane clipped Johnstown’s approach lights and plunged into a winter embankment ten miles out - did they make it in time? The approach lights clipped the plane - did they make it? In this episode, we follow Commonwealth Commuter Flight...
The approach lights clipped the plane - did they make it?

In this episode, we follow Commonwealth Commuter Flight 317 from its January 6, 1974 departure in Pittsburgh through the final minutes before impact, focusing on the crew, the approach, and the unanswered questions that led to a crash short of the runway. What choices, procedures, and mechanical factors set the flight on that descent toward the embankment?

Date: January 6, 1974
Aircraft: Beechcraft Model 99A, N125AE
Flight: Commonwealth Commuter Flight 317
Person: Captain Daniel Brannon; First Officer Gerald Knouff
Location: Ten miles short of Johnstown, Pennsylvania (approach to Runway 33)

- Flight departed Pittsburgh around 6:30 PM on a short commuter hop to Johnstown with 15 people aboard.
- Captain Brannon logged 6,331 flight hours and was described as meticulous; his co-pilot later reported a habit of flying slower than published approach speeds.
- Conditions were instrument-rated, the approach lighting system was operating, and runway 33 was the intended landing.
- The aircraft first struck elevated approach lights, crossed U.S. Route 219 beneath the approach corridor, then impacted the top of a steep embankment nose-up.
- The impact tore the nose from the fuselage, ejected parts of the aircraft up to 75 yards, destroyed floor anchor points while seatbelts remained fastened.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1150falsefullhttps://www.spreaker.com/episode/the-clearance-to-5-000-feet-met-the-mountain-and-left-no-time-to-turn--74905935
The clearance to 5,000 feet met the mountain and left no time to turn

In this episode, we reconstruct the moments before Aviateca Flight 901 reached the San Vicente volcano after a descent clearance to 5,000 feet. We follow the decisions in the cockpit, the controller’s perspective, and the gap that shaped the disaster-what happened next?

Person: Captain Axel Byron Miranda Herrera
Person: First Officer Víctor Francisco Sandoval Salguero
Date: August 9, 1995
Location: San Vicente volcano / Comalapa approach
Aircraft: Boeing 737, registration N125GU

- At 19:30 local time controller José Alberto Chávez cleared Aviateca Flight 901 to descend to 5,000 feet on approach to Comalapa.
- The mountain directly ahead stood at 7,159 feet above sea level, leaving a 2,159-foot difference from the cleared altitude.
- Captain Miranda chose the Runway 07 approach over the standard Runway 25 procedure but did not inform the controller of the change.
- Flight 901 had departed Guatemala City two hours late; the aircraft had 16,645 flight hours and 20,323 cycles and had joined Aviateca in March 1995.
- Sixty-five passengers and crew were aboard, including diplomats and two retired U.S. FAA inspectors, on a short Guatemala City-San Salvador leg.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905935Fri, 04 Sep 2026 18:42:10 +0000OBOMEDIA ENTERTAINMENTA crew cleared to descend to 5,000 feet aimed at Comalapa while the mountain ahead rose to 7,159 feet - did they make it in time? The clearance to 5,000 feet met the mountain and left no time to turn In this episode, we reconstruct the moments...
The clearance to 5,000 feet met the mountain and left no time to turn

In this episode, we reconstruct the moments before Aviateca Flight 901 reached the San Vicente volcano after a descent clearance to 5,000 feet. We follow the decisions in the cockpit, the controller’s perspective, and the gap that shaped the disaster-what happened next?

Person: Captain Axel Byron Miranda Herrera
Person: First Officer Víctor Francisco Sandoval Salguero
Date: August 9, 1995
Location: San Vicente volcano / Comalapa approach
Aircraft: Boeing 737, registration N125GU

- At 19:30 local time controller José Alberto Chávez cleared Aviateca Flight 901 to descend to 5,000 feet on approach to Comalapa.
- The mountain directly ahead stood at 7,159 feet above sea level, leaving a 2,159-foot difference from the cleared altitude.
- Captain Miranda chose the Runway 07 approach over the standard Runway 25 procedure but did not inform the controller of the change.
- Flight 901 had departed Guatemala City two hours late; the aircraft had 16,645 flight hours and 20,323 cycles and had joined Aviateca in March 1995.
- Sixty-five passengers and crew were aboard, including diplomats and two retired U.S. FAA inspectors, on a short Guatemala City-San Salvador leg.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1293falsefullhttps://www.spreaker.com/episode/the-stick-shaker-stayed-silent-and-robbed-them-of-ninety-seconds--74905934
The stick shaker stayed silent and robbed them of ninety seconds

In this episode, we follow Flight Eight Twenty-Seven’s post‑overhaul functional evaluation flight and the chain of routine decisions, tests, and absences that set the stage for disaster. The episode explores the people, procedures, and aircraft details that mattered - and asks whether ordinary assumptions cost six lives.

Date: December 22, 1996
Aircraft: Douglas DC‑8, tail number N827AX
Event: two‑hour functional evaluation flight after overhaul
Location: departed Greensboro, route over Pulaski County, Virginia
Personnel: six aboard including three cockpit crew (Avery, Leming, Waelti) and three maintenance observers

- Stick shaker tested and signed off as functional during ground runs on December 15, seven days before the flight.
- Crew included two Airborne Express flight‑standards managers and an FAA‑designated examiner with extensive DC‑8 experience.
- TIMCO completed an extensive overhaul at Piedmont Triad; two engines rebuilt, two replaced, hush kits and new EFIS installed.
- This was the first time Avery or Leming had conducted a post‑overhaul functional evaluation flight on the DC‑8; the company simulator could not accurately reproduce the type’s stall behavior.
- The flight departed at 17:40 for a planned IFR two‑hour route between 9,000 and 14,000 ft, with the stick shaker silent as the aircraft climbed into winter darkness.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905934Fri, 04 Sep 2026 18:42:06 +0000OBOMEDIA ENTERTAINMENTA DC‑8 freighter climbs into a winter night with a tested stick shaker - the stall warning is silent as a mountain looms. Did they make it in time? The stick shaker stayed silent and robbed them of ninety seconds In this episode, we follow...
The stick shaker stayed silent and robbed them of ninety seconds

In this episode, we follow Flight Eight Twenty-Seven’s post‑overhaul functional evaluation flight and the chain of routine decisions, tests, and absences that set the stage for disaster. The episode explores the people, procedures, and aircraft details that mattered - and asks whether ordinary assumptions cost six lives.

Date: December 22, 1996
Aircraft: Douglas DC‑8, tail number N827AX
Event: two‑hour functional evaluation flight after overhaul
Location: departed Greensboro, route over Pulaski County, Virginia
Personnel: six aboard including three cockpit crew (Avery, Leming, Waelti) and three maintenance observers

- Stick shaker tested and signed off as functional during ground runs on December 15, seven days before the flight.
- Crew included two Airborne Express flight‑standards managers and an FAA‑designated examiner with extensive DC‑8 experience.
- TIMCO completed an extensive overhaul at Piedmont Triad; two engines rebuilt, two replaced, hush kits and new EFIS installed.
- This was the first time Avery or Leming had conducted a post‑overhaul functional evaluation flight on the DC‑8; the company simulator could not accurately reproduce the type’s stall behavior.
- The flight departed at 17:40 for a planned IFR two‑hour route between 9,000 and 14,000 ft, with the stick shaker silent as the aircraft climbed into winter darkness.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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-captain-s-vor-failed-and-they-raced-a-mountain-for-thirty-nine-minutes--74905933
The captain's VOR failed and they raced a mountain for thirty-nine minutes

In this episode, we follow Aerosvit Flight 241’s final hours from Odesa to Thessaloniki, focusing on the failed navigation equipment, the crew actions, and how a radar-less airport and a sequence of decisions set the flight on a collision course. The episode asks what went wrong in the cockpit, on the ground, and during the approach.

Aircraft: Yakovlev Yak-42 UR-42334
Date: December 17, 1997
Location: Thessaloniki / Pieria Mountains
Passengers: 70 aboard
Crew experience: Captain 9,850 hours; instructor pilot 16,210 hours

- The number-one VOR receiver on the captain’s side malfunctioned during an earlier approach into Odesa and was not declared an emergency.
- The crew departed Odesa with the captain’s primary navigation instrument inoperative and made no formal report to ground authorities.
- Makedonia Airport in Thessaloniki had no radar to track the jet when its radio went silent during descent.
- Controllers cleared the flight toward the Thessaloniki VOR and issued descent instructions while the crew referenced a failing beacon.
- The aircraft vanished into the mountains thirty-nine minutes after last transmission, leaving no ELT signal and no immediate location for rescuers.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905933Fri, 04 Sep 2026 18:42:02 +0000OBOMEDIA ENTERTAINMENTA Ukrainian jet with a failed VOR races a mountain near Thessaloniki as controllers lose sight - did they make it in time? The captain's VOR failed and they raced a mountain for thirty-nine minutes In this episode, we follow Aerosvit Flight...
The captain's VOR failed and they raced a mountain for thirty-nine minutes

In this episode, we follow Aerosvit Flight 241’s final hours from Odesa to Thessaloniki, focusing on the failed navigation equipment, the crew actions, and how a radar-less airport and a sequence of decisions set the flight on a collision course. The episode asks what went wrong in the cockpit, on the ground, and during the approach.

Aircraft: Yakovlev Yak-42 UR-42334
Date: December 17, 1997
Location: Thessaloniki / Pieria Mountains
Passengers: 70 aboard
Crew experience: Captain 9,850 hours; instructor pilot 16,210 hours

- The number-one VOR receiver on the captain’s side malfunctioned during an earlier approach into Odesa and was not declared an emergency.
- The crew departed Odesa with the captain’s primary navigation instrument inoperative and made no formal report to ground authorities.
- Makedonia Airport in Thessaloniki had no radar to track the jet when its radio went silent during descent.
- Controllers cleared the flight toward the Thessaloniki VOR and issued descent instructions while the crew referenced a failing beacon.
- The aircraft vanished into the mountains thirty-nine minutes after last transmission, leaving no ELT signal and no immediate location for rescuers.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1179falsefullhttps://www.spreaker.com/episode/the-hill-s-charted-beacon-hid-the-approach-an-hour-of-fuel-needed--74905932
The hill's charted beacon hid the approach an hour of fuel needed

In this episode, we follow a Dutch‑government press tour of thirteen American journalists returning from the Dutch East Indies and the flight that never filed the dispatches home. What decisions, altered logs, and controller clearances left a Constellation headed toward a hill the crew could not see?

Person: Captain Arnoldus Marcelis van der Vaart
Date: July 12, 1949
Aircraft: Lockheed Constellation PH‑TDF "Franeker"
Location: Santa Cruz approach, Bombay (near Ghatkopar)
Passengers: Thirteen American journalists

- The group were established correspondents invited on a Dutch‑government tour through the Indonesian conflict who had secured an interview with Sukarno.
- The Franeker departed Batavia July 10, made a routine flight to New Delhi, then began the final leg to Bombay amid a building monsoon.
- Air traffic control cleared the crew on an approach path later described as terrain‑obstructed, with a charted hill directly in the descent corridor.
- The hill was shown on approach charts; in the downpour it was invisible and the instruments were relied upon as visibility collapsed.
- Investigators cited pilot error and criticized ATC; flight log entries were found altered or incomplete and later allegations about intercepted communications remained unconfirmed.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905932Fri, 04 Sep 2026 18:41:58 +0000OBOMEDIA ENTERTAINMENTA chartered Lockheed Constellation descends toward Santa Cruz in blinding monsoon rain with press credentials still wet - did they make it in time? The hill's charted beacon hid the approach an hour of fuel needed In this episode, we follow a...
The hill's charted beacon hid the approach an hour of fuel needed

In this episode, we follow a Dutch‑government press tour of thirteen American journalists returning from the Dutch East Indies and the flight that never filed the dispatches home. What decisions, altered logs, and controller clearances left a Constellation headed toward a hill the crew could not see?

Person: Captain Arnoldus Marcelis van der Vaart
Date: July 12, 1949
Aircraft: Lockheed Constellation PH‑TDF "Franeker"
Location: Santa Cruz approach, Bombay (near Ghatkopar)
Passengers: Thirteen American journalists

- The group were established correspondents invited on a Dutch‑government tour through the Indonesian conflict who had secured an interview with Sukarno.
- The Franeker departed Batavia July 10, made a routine flight to New Delhi, then began the final leg to Bombay amid a building monsoon.
- Air traffic control cleared the crew on an approach path later described as terrain‑obstructed, with a charted hill directly in the descent corridor.
- The hill was shown on approach charts; in the downpour it was invisible and the instruments were relied upon as visibility collapsed.
- Investigators cited pilot error and criticized ATC; flight log entries were found altered or incomplete and later allegations about intercepted communications remained unconfirmed.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1225falsefullhttps://www.spreaker.com/episode/the-acme-nut-stripped-itself-free-could-they-land-in-time--74905930
The Acme nut stripped itself free - could they land in time?

In this episode, we follow the flight crew, mechanics, and passengers aboard Alaska Airlines Flight 261 as a hidden failure in the tail turns routine into a fight for control. The episode traces the slow degradation of a crucial Acme nut, the crew’s efforts in flight, and the maintenance decisions that set the scene - could they land before the stabilizer failed completely?

Date: January 31, 2000
Flight: Alaska Airlines Flight 261
Aircraft: McDonnell Douglas MD-83, N963AS
Person: Captain Ted Thompson; First Officer Bill Tansky
Event: Horizontal stabilizer jam due to worn Acme nut

- Ninety percent of the Acme nut’s threading had been ground away over years before the flight, unseen inside the tail.
- The jackscrew system controlled the horizontal stabilizer with a 22-inch screw and a copper-alloy Acme nut that rides the threads.
- The MD-83 had passed inspections and logged 26,584 flight hours and 14,315 flight cycles, masking the internal wear.
- At 15:49 PST, the crew reported the stabilizer was jammed and maintained level by holding about ten pounds of constant forward force on the controls.
- Maintenance history included missed maintenance, bad tools, and paperwork claiming work had been completed when it had not.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905930Fri, 04 Sep 2026 18:41:54 +0000OBOMEDIA ENTERTAINMENTA critical Acme nut had almost vanished in the tail-can the pilots wrestle a jammed stabilizer and land Alaska Airlines Flight 261 in time? The Acme nut stripped itself free - could they land in time? In this episode, we follow the flight crew,...
The Acme nut stripped itself free - could they land in time?

In this episode, we follow the flight crew, mechanics, and passengers aboard Alaska Airlines Flight 261 as a hidden failure in the tail turns routine into a fight for control. The episode traces the slow degradation of a crucial Acme nut, the crew’s efforts in flight, and the maintenance decisions that set the scene - could they land before the stabilizer failed completely?

Date: January 31, 2000
Flight: Alaska Airlines Flight 261
Aircraft: McDonnell Douglas MD-83, N963AS
Person: Captain Ted Thompson; First Officer Bill Tansky
Event: Horizontal stabilizer jam due to worn Acme nut

- Ninety percent of the Acme nut’s threading had been ground away over years before the flight, unseen inside the tail.
- The jackscrew system controlled the horizontal stabilizer with a 22-inch screw and a copper-alloy Acme nut that rides the threads.
- The MD-83 had passed inspections and logged 26,584 flight hours and 14,315 flight cycles, masking the internal wear.
- At 15:49 PST, the crew reported the stabilizer was jammed and maintained level by holding about ten pounds of constant forward force on the controls.
- Maintenance history included missed maintenance, bad tools, and paperwork claiming work had been completed when it had not.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1250falsefullhttps://www.spreaker.com/episode/the-rudderless-recorder-failed-to-warn-them-in-time--74905929
The rudderless recorder failed to warn them in time

In this episode, we tell how United Flight 585 descended into a residential neighborhood on a clear March morning and why investigators struggled for years to find a cause. The focus is on the flight, the crew, the aircraft, and a surprising gap in what the cockpit voice and flight data recorders captured - could the missing parameter hold the key?

Date: March 3, 1991
Location: Widefield Park, Colorado Springs
Aircraft: Boeing 737-291, registration N999UA
Crew: Captain Harold Green and First Officer Patricia Eidson
Investigation: NTSB opened probe same day; initial report declared probable cause: unknown

- Witnesses described a massive blast wave and a 39 by 24 by 15-foot crater where the 737 struck at 245 mph
- Captain Green had 9,902 flight hours (1,732 on the 737) and was known for conservative, procedure-driven decisions
- First Officer Eidson had 3,903 total hours (1,077 on the 737) and handled radio communications during the approach
- Weather reports showed rotor conditions, gusting northwest winds to 40 knots, and wind shear advisories the crew received
- The flight data recorder was designed to record five parameters - notably omitting rudder position, a gap investigators flagged during the decade-long 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/74905929Fri, 04 Sep 2026 18:41:50 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 on approach to Colorado Springs fights severe rotor winds - did they make it in time? The rudderless recorder failed to warn them in time In this episode, we tell how United Flight 585 descended into a residential neighborhood on a...
The rudderless recorder failed to warn them in time

In this episode, we tell how United Flight 585 descended into a residential neighborhood on a clear March morning and why investigators struggled for years to find a cause. The focus is on the flight, the crew, the aircraft, and a surprising gap in what the cockpit voice and flight data recorders captured - could the missing parameter hold the key?

Date: March 3, 1991
Location: Widefield Park, Colorado Springs
Aircraft: Boeing 737-291, registration N999UA
Crew: Captain Harold Green and First Officer Patricia Eidson
Investigation: NTSB opened probe same day; initial report declared probable cause: unknown

- Witnesses described a massive blast wave and a 39 by 24 by 15-foot crater where the 737 struck at 245 mph
- Captain Green had 9,902 flight hours (1,732 on the 737) and was known for conservative, procedure-driven decisions
- First Officer Eidson had 3,903 total hours (1,077 on the 737) and handled radio communications during the approach
- Weather reports showed rotor conditions, gusting northwest winds to 40 knots, and wind shear advisories the crew received
- The flight data recorder was designed to record five parameters - notably omitting rudder position, a gap investigators flagged during the decade-long 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.]]>1244falsefullhttps://www.spreaker.com/episode/the-fresh-air-that-flashed-the-cabin-fire-ninety-seconds-to-live--74905928
The fresh air that flashed the cabin fire - ninety seconds to live

In this episode, we follow the final minutes aboard Air Canada Flight 797 and the aftermath that turned a real death into a national story. We trace the known timeline, the uncertainties investigators faced, and the questions that still hang over what happened in those ninety seconds.

Event: Air Canada Flight 797 cabin fire
Date: June 2, 1983
Person: Stan Rogers
Location: Greater Cincinnati Airport (Kentucky)
Outcome: Source of fire never conclusively established

- Smoke began in an aft washroom area-investigators debated whether behind the vanity or beneath the toilet shroud.
- Crew detected smoke at altitude, diverted the DC-9 to Greater Cincinnati and initiated descent with passengers told to brace.
- The cabin gradually filled with smoke; at altitude many passengers lost consciousness from inhalation before landing.
- When the doors opened on the ground, the influx of fresh air created a flash fire that spread within approximately ninety seconds.
- Nineteen of the forty-one aboard did not walk off the runway, and the narrative around one passenger grew into a widely repeated national legend.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905928Fri, 04 Sep 2026 18:41:46 +0000OBOMEDIA ENTERTAINMENTA flight diverted to Cincinnati; fresh air hits a smoke-filled cabin and a flash fire erupts - ninety seconds between open doors and survival closing. The fresh air that flashed the cabin fire - ninety seconds to live In this episode, we follow...
The fresh air that flashed the cabin fire - ninety seconds to live

In this episode, we follow the final minutes aboard Air Canada Flight 797 and the aftermath that turned a real death into a national story. We trace the known timeline, the uncertainties investigators faced, and the questions that still hang over what happened in those ninety seconds.

Event: Air Canada Flight 797 cabin fire
Date: June 2, 1983
Person: Stan Rogers
Location: Greater Cincinnati Airport (Kentucky)
Outcome: Source of fire never conclusively established

- Smoke began in an aft washroom area-investigators debated whether behind the vanity or beneath the toilet shroud.
- Crew detected smoke at altitude, diverted the DC-9 to Greater Cincinnati and initiated descent with passengers told to brace.
- The cabin gradually filled with smoke; at altitude many passengers lost consciousness from inhalation before landing.
- When the doors opened on the ground, the influx of fresh air created a flash fire that spread within approximately ninety seconds.
- Nineteen of the forty-one aboard did not walk off the runway, and the narrative around one passenger grew into a widely repeated national legend.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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-beechcraft-s-seat-cushion-kept-ben-cauley-afloat-did-they-make-it--74905927
The Beechcraft's seat cushion kept Ben Cauley afloat - did they make it?

In this episode, we follow the final hours leading up to a December 10, 1967 flight from Cleveland to Madison and the moments after the plane struck Lake Monona. It covers Otis Redding's career arc, the flight's passengers, and the unanswered questions about why the plane crashed, asking whether anyone could have been saved.

Person: Otis Redding
Person: Ben Cauley
Date: December 10, 1967
Location: Lake Monona / Truax Field, Madison, Wisconsin
Event: Beechcraft H18 crash

- Otis Redding had recorded a new song three days before the flight and was returning from performances when the plane descended toward Truax Field.
- The Beechcraft H18 carried eight people; the pilot had radioed for landing permission with the airfield about four miles away.
- Ben Cauley surfaced after the crash clutching a seat cushion from the plane and was the only passenger who came out of the lake alive.
- No official mechanical fault, weather cause, or documented pilot error was established in the crash investigation.
- The episode traces Redding’s rise from Macon, Georgia-leaving school at fifteen, his Stax breakthrough, and his mounting success in the years before December 1967.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905927Fri, 04 Sep 2026 18:41:42 +0000OBOMEDIA ENTERTAINMENTOtis Redding’s Beechcraft descends toward Truax Field; a passenger clings to a seat cushion in Lake Monona - did they make it in time? The Beechcraft's seat cushion kept Ben Cauley afloat - did they make it? In this episode, we follow the final...
The Beechcraft's seat cushion kept Ben Cauley afloat - did they make it?

In this episode, we follow the final hours leading up to a December 10, 1967 flight from Cleveland to Madison and the moments after the plane struck Lake Monona. It covers Otis Redding's career arc, the flight's passengers, and the unanswered questions about why the plane crashed, asking whether anyone could have been saved.

Person: Otis Redding
Person: Ben Cauley
Date: December 10, 1967
Location: Lake Monona / Truax Field, Madison, Wisconsin
Event: Beechcraft H18 crash

- Otis Redding had recorded a new song three days before the flight and was returning from performances when the plane descended toward Truax Field.
- The Beechcraft H18 carried eight people; the pilot had radioed for landing permission with the airfield about four miles away.
- Ben Cauley surfaced after the crash clutching a seat cushion from the plane and was the only passenger who came out of the lake alive.
- No official mechanical fault, weather cause, or documented pilot error was established in the crash investigation.
- The episode traces Redding’s rise from Macon, Georgia-leaving school at fifteen, his Stax breakthrough, and his mounting success in the years before December 1967.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1246falsefullhttps://www.spreaker.com/episode/the-unlipped-anti-ice-switch-left-the-engines-to-freeze-midflight--74905925
The unlipped anti‑ice switch left the engines to freeze midflight

In this episode, we follow the flight that carried NASCAR champion Alan Kulwicki on a short trip from Knoxville to Bristol the week after his championship win. We trace the plane, the mistaken registration, the missed switch, and the choices that defined Kulwicki-so what decision cost him that night?

Person: Alan Kulwicki
Event: Swearingen Merlin III crash near Blountville
Date: April 1, 1993
Location: Interstate 81 area near Blountville
Cause cited by NTSB: anti-ice system not activated; ice blocked engine air inlets

- The tail bore registration N300AK while records showed N300EF and corporate names Eastern Foods and Hooters beneath the paint.
- Kulwicki was flying a borrowed corporate aircraft four months after winning the NASCAR Winston Cup championship.
- The NTSB concluded the pilot did not activate the aircraft’s anti-ice system, allowing ice to block engine air inlets.
- The flight was a short hop from Knoxville to Bristol during a week when Kulwicki was expected at a race he had helped build toward.
- Kulwicki’s career is framed by hands-on engineering, refusal of large offers, and the “underdog” choice to retain ownership and control.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905925Fri, 04 Sep 2026 18:41:38 +0000OBOMEDIA ENTERTAINMENTA corporate Swearingen Merlin III departs for Bristol with the pilot skipping anti-ice-did they make it in time? The unlipped anti‑ice switch left the engines to freeze midflight In this episode, we follow the flight that carried NASCAR champion...
The unlipped anti‑ice switch left the engines to freeze midflight

In this episode, we follow the flight that carried NASCAR champion Alan Kulwicki on a short trip from Knoxville to Bristol the week after his championship win. We trace the plane, the mistaken registration, the missed switch, and the choices that defined Kulwicki-so what decision cost him that night?

Person: Alan Kulwicki
Event: Swearingen Merlin III crash near Blountville
Date: April 1, 1993
Location: Interstate 81 area near Blountville
Cause cited by NTSB: anti-ice system not activated; ice blocked engine air inlets

- The tail bore registration N300AK while records showed N300EF and corporate names Eastern Foods and Hooters beneath the paint.
- Kulwicki was flying a borrowed corporate aircraft four months after winning the NASCAR Winston Cup championship.
- The NTSB concluded the pilot did not activate the aircraft’s anti-ice system, allowing ice to block engine air inlets.
- The flight was a short hop from Knoxville to Bristol during a week when Kulwicki was expected at a race he had helped build toward.
- Kulwicki’s career is framed by hands-on engineering, refusal of large offers, and the “underdog” choice to retain ownership and control.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1275falsefullhttps://www.spreaker.com/episode/the-program-note-that-scheduled-the-funeral-march-and-left-them-seven-days-short--74905924
The program note that scheduled the Funeral March and left them seven days short

In this episode, we follow the last weeks of William Kapell’s life, tracing his rapid rise, relentless schedule, and the medical notes and diary entries that complicate the timeline. The narrative asks whether the clues in his program and private papers hint at what he knew about his own condition and whether that knowledge shaped his final decisions.

Person: William Kapell
Date: October 29, 1953
Event: BCPA Flight 304 descended into fog and struck trees at Kings Mountain
Location: San Francisco / Kings Mountain
Program detail: Performed Chopin Sonata in B‑flat minor, the "Funeral March," on October 22, 1953

- A prodigy from Yorkville who won the Philadelphia Orchestra youth competition and the Naumburg Award by age eighteen.
- Signed an exclusive RCA Victor contract before turning twenty and earned the nickname "Khachaturian Kapell" after a hit recording.
- Kept a rigorous practice routine with a notebook and stopwatch and sought lessons from leading musicians of his era.
- In April 1952 was diagnosed with bronchitis and kept touring despite diary notes about a pulmonary condition needing immediate attention.
- Allegation by one dinner companion that Kapell said he had cancer and two years to live, an unconfirmed account dated May 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/74905924Fri, 04 Sep 2026 18:41:34 +0000OBOMEDIA ENTERTAINMENTA celebrated American pianist boards a fogbound flight home - did he know something about his health the program notes quietly record? The program note that scheduled the Funeral March and left them seven days short In this episode, we follow...
The program note that scheduled the Funeral March and left them seven days short

In this episode, we follow the last weeks of William Kapell’s life, tracing his rapid rise, relentless schedule, and the medical notes and diary entries that complicate the timeline. The narrative asks whether the clues in his program and private papers hint at what he knew about his own condition and whether that knowledge shaped his final decisions.

Person: William Kapell
Date: October 29, 1953
Event: BCPA Flight 304 descended into fog and struck trees at Kings Mountain
Location: San Francisco / Kings Mountain
Program detail: Performed Chopin Sonata in B‑flat minor, the "Funeral March," on October 22, 1953

- A prodigy from Yorkville who won the Philadelphia Orchestra youth competition and the Naumburg Award by age eighteen.
- Signed an exclusive RCA Victor contract before turning twenty and earned the nickname "Khachaturian Kapell" after a hit recording.
- Kept a rigorous practice routine with a notebook and stopwatch and sought lessons from leading musicians of his era.
- In April 1952 was diagnosed with bronchitis and kept touring despite diary notes about a pulmonary condition needing immediate attention.
- Allegation by one dinner companion that Kapell said he had cancer and two years to live, an unconfirmed account dated May 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.]]>1261falsefullhttps://www.spreaker.com/episode/the-flight-manifest-that-scheduled-his-lecture-did-it-arrive-in-time--74905922
The flight manifest that scheduled his lecture - did it arrive in time?

In this episode, we follow the life and work of Walter Franz Heiligenberg from postwar Germany to San Diego, tracing how his experiments on fish reshaped neuroscience and culminated in a single lecture he was scheduled to give. What happens when decades of a mind’s work travel on one plane?

Person: Walter Franz Heiligenberg
Date: September 8, 1994
Location: Pittsburgh (flight bound for)
Event: USAir Flight 427 crash
Topic: complete map of a vertebrate nervous system

- Born in Berlin (1938) and raised in Münster, he entered research after encountering Konrad Lorenz at age 15.
- He studied botany, zoology, physics and mathematics, earning a doctorate on cichlid fish behavior in 1963.
- He used quantitative experiments to refute Lorenz’s psychohydraulic model and proposed the law of heterogeneous summation.
- He moved to Scripps Institution of Oceanography, became a professor, and declined the Max Planck directorship to continue his research in San Diego.
- He researched Eigenmannia, an electric fish, tracing sensory input to motor output to build a decades-long neural map carried with him onto Flight 427.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905922Fri, 04 Sep 2026 18:41:30 +0000OBOMEDIA ENTERTAINMENTA scientist boards a doomed flight to Pittsburgh carrying the only complete map of a vertebrate nervous system - did the lecture make it in time? The flight manifest that scheduled his lecture - did it arrive in time? In this episode, we follow...
The flight manifest that scheduled his lecture - did it arrive in time?

In this episode, we follow the life and work of Walter Franz Heiligenberg from postwar Germany to San Diego, tracing how his experiments on fish reshaped neuroscience and culminated in a single lecture he was scheduled to give. What happens when decades of a mind’s work travel on one plane?

Person: Walter Franz Heiligenberg
Date: September 8, 1994
Location: Pittsburgh (flight bound for)
Event: USAir Flight 427 crash
Topic: complete map of a vertebrate nervous system

- Born in Berlin (1938) and raised in Münster, he entered research after encountering Konrad Lorenz at age 15.
- He studied botany, zoology, physics and mathematics, earning a doctorate on cichlid fish behavior in 1963.
- He used quantitative experiments to refute Lorenz’s psychohydraulic model and proposed the law of heterogeneous summation.
- He moved to Scripps Institution of Oceanography, became a professor, and declined the Max Planck directorship to continue his research in San Diego.
- He researched Eigenmannia, an electric fish, tracing sensory input to motor output to build a decades-long neural map carried with him onto Flight 427.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1262falsefullhttps://www.spreaker.com/episode/the-five-channel-recorder-missed-the-rudder-did-they-get-answers-in-time--74905920
The five‑channel recorder missed the rudder - did they get answers in time?

In this episode, we walk through the final minutes of United Flight 585, the limits of its five‑parameter flight data recorder, and the investigative road that started with a thirty‑nine foot crater. What did the missing rudder data mean for finding out why the controls betrayed the crew?

Date: March 3, 1991
Aircraft: Boeing 737 (N999UA)
Crew: Captain Harold Green; First Officer Patricia Eidson
Event: Rudder deflection and crash into Widefield Park
Recorder: Five‑parameter FDR (no rudder, aileron, or spoiler channels)

- Eight seconds elapsed between initial roll to the right and impact at 245 mph.
- Two prior uncommanded rudder deflections were logged on Feb 25 and Feb 27 and archived without grounding the airplane.
- Weather reports showed gusting northwest winds, wind shear advisories, and rapid airspeed swings; ATIS information was 40 minutes old.
- Flight data recorder channels were limited to heading, altitude, airspeed, normal acceleration, and microphone keying.
- Investigators recovered an intact tape inside a crushed FDR case but lacked direct rudder position data to explain the sudden 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/74905920Fri, 04 Sep 2026 18:41:26 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 drops into a Colorado park in eight seconds after the rudder moves the wrong way - did investigators get answers before another crash? The five‑channel recorder missed the rudder - did they get answers in time? In this episode, we...
The five‑channel recorder missed the rudder - did they get answers in time?

In this episode, we walk through the final minutes of United Flight 585, the limits of its five‑parameter flight data recorder, and the investigative road that started with a thirty‑nine foot crater. What did the missing rudder data mean for finding out why the controls betrayed the crew?

Date: March 3, 1991
Aircraft: Boeing 737 (N999UA)
Crew: Captain Harold Green; First Officer Patricia Eidson
Event: Rudder deflection and crash into Widefield Park
Recorder: Five‑parameter FDR (no rudder, aileron, or spoiler channels)

- Eight seconds elapsed between initial roll to the right and impact at 245 mph.
- Two prior uncommanded rudder deflections were logged on Feb 25 and Feb 27 and archived without grounding the airplane.
- Weather reports showed gusting northwest winds, wind shear advisories, and rapid airspeed swings; ATIS information was 40 minutes old.
- Flight data recorder channels were limited to heading, altitude, airspeed, normal acceleration, and microphone keying.
- Investigators recovered an intact tape inside a crushed FDR case but lacked direct rudder position data to explain the sudden 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.]]>1272falsefullhttps://www.spreaker.com/episode/the-dark-hazy-night-erased-the-horizon-and-ate-their-flight--74905919
The dark, hazy night erased the horizon and ate their flight

In this episode, we trace the final flight that left Essex County Airport on July 16, 1999, the people on board, and the moments leading up to the plane’s disappearance, posing the question at the center of the story. We present who Carolyn Bessette was, her life before the trip, and the flight’s timeline to Martha’s Vineyard.

Person: Carolyn Bessette-Kennedy
Person: John F. Kennedy Jr.
Person: Lauren Bessette
Date: July 16, 1999
Location: Essex County Airport to Martha's Vineyard (Atlantic Ocean)

- A single-engine Piper Saratoga took off at 8:38 p.m. heading east toward Martha's Vineyard.
- John F. Kennedy Jr. filed no flight plan and was piloting the aircraft.
- Carolyn Bessette-Kennedy, age thirty-three, and her sister Lauren were seated behind him; Lauren was to be dropped off first.
- The sky was described as dark and hazy, erasing the horizon where water and sky blend.
- The plane disappeared from radar at 9:41 p.m., sixty-three minutes after takeoff, with no distress call or radio 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/74905919Fri, 04 Sep 2026 18:41:22 +0000OBOMEDIA ENTERTAINMENTJohn Kennedy Jr. pilots a small plane into a dark, hazy night toward Martha's Vineyard with Carolyn Bessette and her sister aboard-did they make it? The dark, hazy night erased the horizon and ate their flight In this episode, we trace the final...
The dark, hazy night erased the horizon and ate their flight

In this episode, we trace the final flight that left Essex County Airport on July 16, 1999, the people on board, and the moments leading up to the plane’s disappearance, posing the question at the center of the story. We present who Carolyn Bessette was, her life before the trip, and the flight’s timeline to Martha’s Vineyard.

Person: Carolyn Bessette-Kennedy
Person: John F. Kennedy Jr.
Person: Lauren Bessette
Date: July 16, 1999
Location: Essex County Airport to Martha's Vineyard (Atlantic Ocean)

- A single-engine Piper Saratoga took off at 8:38 p.m. heading east toward Martha's Vineyard.
- John F. Kennedy Jr. filed no flight plan and was piloting the aircraft.
- Carolyn Bessette-Kennedy, age thirty-three, and her sister Lauren were seated behind him; Lauren was to be dropped off first.
- The sky was described as dark and hazy, erasing the horizon where water and sky blend.
- The plane disappeared from radar at 9:41 p.m., sixty-three minutes after takeoff, with no distress call or radio 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.]]>1281falsefullhttps://www.spreaker.com/episode/the-window-post-hid-the-otter-for-eleven-seconds-did-they-make-it--74905918
The window post hid the Otter for eleven seconds - did they make it?

In this episode, we follow the final minutes before two de Havilland floatplanes converged over George Inlet and the chain of methodical electronic and human factors that left both cockpits without alert. What happened in those eleven seconds, and how did systems designed to warn pilots remain silent?

Date: May 13, 2019
Location: George Inlet, near Ketchikan Harbor Seaplane Base, Alaska
Event: Midair collision between two floatplanes
Person: Randy Sullivan (Mountain Air Service) - pilot of DHC-2 Beaver
Person: Lou Beck (Taquan Air) - pilot of DHC-3 Turbine Otter

- Both aircraft were airworthy with recent inspections: Beaver inspected April 16, 2019; Otter inspected April 30, 2019.
- Sullivan flew a DHC-2 Beaver (N952DB) with ~16,452 airframe hours and reported ~11,000 pilot hours; single-operator Mountain Air Service.
- Beck commanded a DHC-3 Otter (N959PA) with ~30,297 airframe hours and ~25,000 pilot hours, operating for Taquan Air with nine passengers aboard.
- At 12:21 PM both planes were at about 3,350 ft: Beaver level, 107 knots heading 255°; Otter descending, 126 knots approaching from the right.
- Both cockpits had electronic collision-warning equipment installed, yet neither system produced any alert during the critical fourteen days and the final 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/74905918Fri, 04 Sep 2026 18:41:19 +0000OBOMEDIA ENTERTAINMENTA sixty-eight-year-old Otter disappears behind a window post over George Inlet-two floatplanes close; did they make it? The window post hid the Otter for eleven seconds - did they make it? In this episode, we follow the final minutes before two...
The window post hid the Otter for eleven seconds - did they make it?

In this episode, we follow the final minutes before two de Havilland floatplanes converged over George Inlet and the chain of methodical electronic and human factors that left both cockpits without alert. What happened in those eleven seconds, and how did systems designed to warn pilots remain silent?

Date: May 13, 2019
Location: George Inlet, near Ketchikan Harbor Seaplane Base, Alaska
Event: Midair collision between two floatplanes
Person: Randy Sullivan (Mountain Air Service) - pilot of DHC-2 Beaver
Person: Lou Beck (Taquan Air) - pilot of DHC-3 Turbine Otter

- Both aircraft were airworthy with recent inspections: Beaver inspected April 16, 2019; Otter inspected April 30, 2019.
- Sullivan flew a DHC-2 Beaver (N952DB) with ~16,452 airframe hours and reported ~11,000 pilot hours; single-operator Mountain Air Service.
- Beck commanded a DHC-3 Otter (N959PA) with ~30,297 airframe hours and ~25,000 pilot hours, operating for Taquan Air with nine passengers aboard.
- At 12:21 PM both planes were at about 3,350 ft: Beaver level, 107 knots heading 255°; Otter descending, 126 knots approaching from the right.
- Both cockpits had electronic collision-warning equipment installed, yet neither system produced any alert during the critical fourteen days and the final 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.]]>1257falsefullhttps://www.spreaker.com/episode/the-missing-chart-denied-them-altitude-did-they-climb-in-time--74905916
The missing chart denied them altitude - did they climb in time?

In this episode, we hear how a routine Cold Response leg aboard C-130J "Siv" became a fatal navigation moment when the crew lacked a chart showing Sweden's highest summit, and how records and delayed evidence raised questions about institutional oversights. What sequence of small failures led a veteran crew into a fifty-foot margin with a mountain?

Person: Ståle Garberg
Person: Truls Audun Ørpen
Aircraft: C-130J Super Hercules (military serial 5630), call sign HAZE one
Date: 15 March 2012
Location: Kebnekaise massif, Sweden

- Five experienced Royal Norwegian Air Force officers flew a routine 50-minute transit from Evenes to Kiruna during Cold Response.
- The planned route took the aircraft directly over Kebnekaise, whose western summit is 6,950 ft above sea level.
- Kiruna air traffic control cleared descent to 7,000 ft, leaving roughly a 20-meter (≈50 ft) margin to the summit.
- The crew did not possess an aeronautical chart showing the mountain’s altitude; that absence remained undisclosed for seven years.
- Radar showed steady, level flight with last returns around 7,200-7,600 ft before an impact that triggered an avalanche and buried the 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/74905916Fri, 04 Sep 2026 18:41:14 +0000OBOMEDIA ENTERTAINMENTFive Norwegian Air Force officers cross into the Kebnekaise massif without a chart showing the peak ahead - did they climb in time? The missing chart denied them altitude - did they climb in time? In this episode, we hear how a routine Cold...
The missing chart denied them altitude - did they climb in time?

In this episode, we hear how a routine Cold Response leg aboard C-130J "Siv" became a fatal navigation moment when the crew lacked a chart showing Sweden's highest summit, and how records and delayed evidence raised questions about institutional oversights. What sequence of small failures led a veteran crew into a fifty-foot margin with a mountain?

Person: Ståle Garberg
Person: Truls Audun Ørpen
Aircraft: C-130J Super Hercules (military serial 5630), call sign HAZE one
Date: 15 March 2012
Location: Kebnekaise massif, Sweden

- Five experienced Royal Norwegian Air Force officers flew a routine 50-minute transit from Evenes to Kiruna during Cold Response.
- The planned route took the aircraft directly over Kebnekaise, whose western summit is 6,950 ft above sea level.
- Kiruna air traffic control cleared descent to 7,000 ft, leaving roughly a 20-meter (≈50 ft) margin to the summit.
- The crew did not possess an aeronautical chart showing the mountain’s altitude; that absence remained undisclosed for seven years.
- Radar showed steady, level flight with last returns around 7,200-7,600 ft before an impact that triggered an avalanche and buried the 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.]]>1217falsefullhttps://www.spreaker.com/episode/thirteen-missing-rollers-overheated-and-tore-the-plane-apart-midflight--74905915
Thirteen missing rollers overheated and tore the plane apart midflight

In this episode, we follow the fifty-four minutes after LOT Polish Airlines Flight 5055 departed Warsaw and a catastrophic bearing failure set off a cascading emergency. We describe the crew, the aircraft layout, the mechanical failure, and the moments the pilots and flight crew faced-what did those minutes look like and how did they respond?

Date: May 9, 1987
Aircraft: Ilyushin Il-62M SP-LBG
Event: Engine number two catastrophic bearing failure
Person: Captain Zygmunt Pawlaczyk (59), 19,745 flight hours
Passengers: 182 on board

- Engine number two’s bearing assembly ran at roughly 1,000°C nine minutes after takeoff, causing the turbine disc to disintegrate.
- The Il-62’s four tail-mounted engines are grouped in two adjacent pairs; debris from one engine traveled directly into the neighbouring engine cluster.
- Shrapnel severed electrical cables and flight control linkages in the tail, puncturing the fuselage and cutting systems as the crew worked.
- The flight crew included a highly experienced captain, first officer, flight engineer and trainer, navigator, and radio operator managing systems amid cascading failures.
- A flight attendant had been assigned to the technical cabin bay between the rear engine clusters, a detail investigators later noted during reconstruction.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905915Fri, 04 Sep 2026 18:41:10 +0000OBOMEDIA ENTERTAINMENTA flight out of Warsaw loses half an engine midair, shredding the tail - did they make it in time? Thirteen missing rollers overheated and tore the plane apart midflight In this episode, we follow the fifty-four minutes after LOT Polish Airlines...
Thirteen missing rollers overheated and tore the plane apart midflight

In this episode, we follow the fifty-four minutes after LOT Polish Airlines Flight 5055 departed Warsaw and a catastrophic bearing failure set off a cascading emergency. We describe the crew, the aircraft layout, the mechanical failure, and the moments the pilots and flight crew faced-what did those minutes look like and how did they respond?

Date: May 9, 1987
Aircraft: Ilyushin Il-62M SP-LBG
Event: Engine number two catastrophic bearing failure
Person: Captain Zygmunt Pawlaczyk (59), 19,745 flight hours
Passengers: 182 on board

- Engine number two’s bearing assembly ran at roughly 1,000°C nine minutes after takeoff, causing the turbine disc to disintegrate.
- The Il-62’s four tail-mounted engines are grouped in two adjacent pairs; debris from one engine traveled directly into the neighbouring engine cluster.
- Shrapnel severed electrical cables and flight control linkages in the tail, puncturing the fuselage and cutting systems as the crew worked.
- The flight crew included a highly experienced captain, first officer, flight engineer and trainer, navigator, and radio operator managing systems amid cascading failures.
- A flight attendant had been assigned to the technical cabin bay between the rear engine clusters, a detail investigators later noted during reconstruction.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1168falsefullhttps://www.spreaker.com/episode/the-drainage-ditch-that-saved-two-lives-when-the-jet-struck-short--74905912
The drainage ditch that saved two lives when the jet struck short

In this episode, we follow Sosoliso Airlines Flight 1145’s final minutes as weather, routine omissions, and a chain of small decisions converge on approach to Port Harcourt. The story traces who was aboard, what the crew knew, and the procedural gaps that mattered - and asks whether those choices made the difference in the moment of impact.

Date: 10 December 2005
Flight: Sosoliso Airlines Flight 1145
Aircraft: McDonnell Douglas DC-9-32 (built 1972)
Person: Captain Benjamin Adebayo, 48; First Officer Gerald Andan, 33
Passengers: 103 (+7 crew), ~60 secondary school students

- Flight departed Abuja at 12:25 for a scheduled 12:39 arrival at Port Harcourt after families chose air travel over dangerous road routes.
- Captain Adebayo had ~10,050 hours total; First Officer Andan had ~920 hours and both had recent satisfactory simulator checks.
- A sea‑breeze front near Port Harcourt produced rapid visibility changes and the specific atmospheric phenomenon later identified as central to the accident.
- Port Harcourt approach controller reported scattered cumulonimbus and no precipitation, omitting wind speed and thunderstorm possibility from the radio call.
- The aircraft struck ground short of the runway at approximately 13:04; a concrete drainage ditch at the runway edge played a critical role in who 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/74905912Fri, 04 Sep 2026 18:41:06 +0000OBOMEDIA ENTERTAINMENTA pilot descends into Port Harcourt in poor visibility as a sea‑breeze front rolls in; did the crew make it to the runway in time? The drainage ditch that saved two lives when the jet struck short In this episode, we follow Sosoliso Airlines...
The drainage ditch that saved two lives when the jet struck short

In this episode, we follow Sosoliso Airlines Flight 1145’s final minutes as weather, routine omissions, and a chain of small decisions converge on approach to Port Harcourt. The story traces who was aboard, what the crew knew, and the procedural gaps that mattered - and asks whether those choices made the difference in the moment of impact.

Date: 10 December 2005
Flight: Sosoliso Airlines Flight 1145
Aircraft: McDonnell Douglas DC-9-32 (built 1972)
Person: Captain Benjamin Adebayo, 48; First Officer Gerald Andan, 33
Passengers: 103 (+7 crew), ~60 secondary school students

- Flight departed Abuja at 12:25 for a scheduled 12:39 arrival at Port Harcourt after families chose air travel over dangerous road routes.
- Captain Adebayo had ~10,050 hours total; First Officer Andan had ~920 hours and both had recent satisfactory simulator checks.
- A sea‑breeze front near Port Harcourt produced rapid visibility changes and the specific atmospheric phenomenon later identified as central to the accident.
- Port Harcourt approach controller reported scattered cumulonimbus and no precipitation, omitting wind speed and thunderstorm possibility from the radio call.
- The aircraft struck ground short of the runway at approximately 13:04; a concrete drainage ditch at the runway edge played a critical role in who 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.]]>1316falsefullhttps://www.spreaker.com/episode/the-de-ice-that-never-happened-stole-their-fifty-one-seconds--74905911
The de-ice that never happened stole their fifty-one seconds

In this episode, we follow Arrow Air Flight 1285 on the morning it left Gander and trace the decisions, conditions, and people that led to its fifty-one-second takeoff roll. We lay out the sequence on the ground and in the cockpit and ask how one omitted procedure shaped every line of inquiry that followed. What happened during those fifty-one seconds?

Date: December 12, 1985
Location: Gander, Newfoundland
Aircraft: Douglas DC-8-63, registration N950JW
People: 248 passengers (236 from 101st Airborne Division’s 3rd Battalion, 502nd Infantry), 8 crew
Condition: Freezing precipitation; no de-icing before departure

- Soldiers had spent six months on a peacekeeping mission in the Sinai and were reboarding at Gander for the final leg home.
- The DC-8 had landed from Cologne, refueled, and sat on the ramp in conditions favorable to ice formation while passengers stretched in the terminal.
- The three officers on the flight deck (Captain John Griffin, First Officer Joseph Connelly, Flight Engineer Michael Fowler) joined the aircraft after it completed multiple sectors overnight.
- The aircraft was sixteen years old, operated by Arrow Air under a lease, and its data recorders and age later became focal points in reconstruction efforts.
- Investigators produced three competing official conclusions after months of work, each tracing chains of evidence back to the aircraft’s condition during those final minutes.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905911Fri, 04 Sep 2026 18:41:02 +0000OBOMEDIA ENTERTAINMENTA fully loaded DC-8 begins a takeoff from Gander in freezing precipitation without being de-iced - did they make it in time? The de-ice that never happened stole their fifty-one seconds In this episode, we follow Arrow Air Flight 1285 on the...
The de-ice that never happened stole their fifty-one seconds

In this episode, we follow Arrow Air Flight 1285 on the morning it left Gander and trace the decisions, conditions, and people that led to its fifty-one-second takeoff roll. We lay out the sequence on the ground and in the cockpit and ask how one omitted procedure shaped every line of inquiry that followed. What happened during those fifty-one seconds?

Date: December 12, 1985
Location: Gander, Newfoundland
Aircraft: Douglas DC-8-63, registration N950JW
People: 248 passengers (236 from 101st Airborne Division’s 3rd Battalion, 502nd Infantry), 8 crew
Condition: Freezing precipitation; no de-icing before departure

- Soldiers had spent six months on a peacekeeping mission in the Sinai and were reboarding at Gander for the final leg home.
- The DC-8 had landed from Cologne, refueled, and sat on the ramp in conditions favorable to ice formation while passengers stretched in the terminal.
- The three officers on the flight deck (Captain John Griffin, First Officer Joseph Connelly, Flight Engineer Michael Fowler) joined the aircraft after it completed multiple sectors overnight.
- The aircraft was sixteen years old, operated by Arrow Air under a lease, and its data recorders and age later became focal points in reconstruction efforts.
- Investigators produced three competing official conclusions after months of work, each tracing chains of evidence back to the aircraft’s condition during those final minutes.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1228falsefullhttps://www.spreaker.com/episode/the-thrust-reversers-that-waited-18-seconds-to-stop-a-landing--74905909
The thrust reversers that waited 18 seconds to stop a landing

In this episode, we follow the final minutes of Southwest Airlines Flight 1248’s approach and landing at Chicago Midway on a snowy December night, focusing on the decisions, systems, and environmental factors that shaped the outcome. What did the crew see, what did the airplane’s computers hide, and how did eighteen seconds become critical?

Person: Captain Bruce Sutherland
Person: First Officer Steven Oliver
Date: December 8, 2005
Location: Chicago Midway Airport, Runway 31C
Event: Landing with tailwind; thrust reverser delay

- The crew elected Runway 31C in a winter storm despite an eight‑knot tailwind, above Southwest’s five‑knot limit.
- The aircraft’s onboard performance computer returned a “safe” landing distance without displaying two hidden assumptions about wind and reverser deployment.
- The Boeing 737 (N471WN) was barely a year old with autobrake and newly introduced systems; it needed 5,300 feet to stop but had 4,500 feet available.
- Captain Sutherland, with about 15,000 flight hours, and First Officer Oliver, with 8,500 hours, touched down with the main gear contacting the runway around 7:15 PM in low visibility and heavy snow.
- The crew moved for thrust reversers immediately at touchdown; the investigation centered on what happened in the eighteen seconds after the wheels met pavement.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905909Fri, 04 Sep 2026 18:40:58 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 lands at Chicago’s Midway; eighteen seconds stand between a routine touchdown and catastrophe - can they stop it? The thrust reversers that waited 18 seconds to stop a landing In this episode, we follow the final minutes of...
The thrust reversers that waited 18 seconds to stop a landing

In this episode, we follow the final minutes of Southwest Airlines Flight 1248’s approach and landing at Chicago Midway on a snowy December night, focusing on the decisions, systems, and environmental factors that shaped the outcome. What did the crew see, what did the airplane’s computers hide, and how did eighteen seconds become critical?

Person: Captain Bruce Sutherland
Person: First Officer Steven Oliver
Date: December 8, 2005
Location: Chicago Midway Airport, Runway 31C
Event: Landing with tailwind; thrust reverser delay

- The crew elected Runway 31C in a winter storm despite an eight‑knot tailwind, above Southwest’s five‑knot limit.
- The aircraft’s onboard performance computer returned a “safe” landing distance without displaying two hidden assumptions about wind and reverser deployment.
- The Boeing 737 (N471WN) was barely a year old with autobrake and newly introduced systems; it needed 5,300 feet to stop but had 4,500 feet available.
- Captain Sutherland, with about 15,000 flight hours, and First Officer Oliver, with 8,500 hours, touched down with the main gear contacting the runway around 7:15 PM in low visibility and heavy snow.
- The crew moved for thrust reversers immediately at touchdown; the investigation centered on what happened in the eighteen seconds after the wheels met pavement.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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/the-touchdown-four-thousand-one-hundred-feet-in-that-left-them-racing-the-sea--74905908
The touchdown four thousand one hundred feet in that left them racing the sea

In this episode, we follow the final hours of American Airlines Flight 331 on December 22, 2009, tracing the crew decisions, weather and airport information that converged on one critical landing. What combination of choices and missing warnings turned a routine approach into a race against the sea?

Date: December 22, 2009
Flight: American Airlines Flight 331
Aircraft: Boeing 737-800, tail N977AN
Location: Norman Manley International Airport, Kingston, Jamaica
Passengers and Crew: 154 on board

- Touchdown occurred 4,100 feet from runway threshold on runway 12, leaving fewer than 5,000 feet to stop.
- Runway length was 8,910 feet and had no drainage grooves; heavy rain produced standing water.
- Crew decisions included not selecting maximum autobrake and not deploying maximum flaps on final approach.
- The crew was not informed of a standing water advisory; they were told only about some non-functional approach lights.
- Combined pilot experience totaled about 17,000 hours, and the aircraft had been in service since 2001 and was technically airworthy.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905908Fri, 04 Sep 2026 18:40:55 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 touches down 4,100 feet into an 8,910-foot runway in Kingston amid heavy rain and missing warnings - did they make it to shore? The touchdown four thousand one hundred feet in that left them racing the sea In this episode, we follow...
The touchdown four thousand one hundred feet in that left them racing the sea

In this episode, we follow the final hours of American Airlines Flight 331 on December 22, 2009, tracing the crew decisions, weather and airport information that converged on one critical landing. What combination of choices and missing warnings turned a routine approach into a race against the sea?

Date: December 22, 2009
Flight: American Airlines Flight 331
Aircraft: Boeing 737-800, tail N977AN
Location: Norman Manley International Airport, Kingston, Jamaica
Passengers and Crew: 154 on board

- Touchdown occurred 4,100 feet from runway threshold on runway 12, leaving fewer than 5,000 feet to stop.
- Runway length was 8,910 feet and had no drainage grooves; heavy rain produced standing water.
- Crew decisions included not selecting maximum autobrake and not deploying maximum flaps on final approach.
- The crew was not informed of a standing water advisory; they were told only about some non-functional approach lights.
- Combined pilot experience totaled about 17,000 hours, and the aircraft had been in service since 2001 and was technically airworthy.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1244falsefullhttps://www.spreaker.com/episode/meters-from-safety-tony-lema-s-fatal-fuel-gauge-failure--74905907
Meters From Safety: Tony Lema's Fatal Fuel Gauge Failure

In this episode, we follow the late career and final flight of Tony Lema, tracing his rise from childhood hardship to golf stardom and the mechanical failure that ended a Sunday approach. How did a single number on a fuel gauge intersect with a champion’s trajectory and four lives on board?

Person: Tony Lema
Event: Aircraft crash on approach to Lansing Municipal Airport
Date: July 24, 1966
Location: Lansing Municipal Airport / golf course water hazard
Topic: Fuel gauge reading empty during final approach

- Tony Lema grew up in Oakland after his father died when he was three, raised on public assistance and introduced to golf at Lake Chabot.
- He served in the United States Marine Corps, returned in 1955, and worked as an assistant professional before rising on tour.
- Eddie Lowery financed Lema early on with $200 weekly for a 33% share, a debt that exceeded $11,000 by 1963 and helped stabilize his career.
- Nicknamed "Champagne Tony" after buying champagne for the press in 1962, Lema amassed twelve wins and a Ryder Cup record that still stands.
- On July 24, 1966, a Beechcraft Bonanza came down in a golf course water hazard eight hundred meters short of Lansing runway after the fuel gauge read empty.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905907Fri, 04 Sep 2026 18:40:51 +0000OBOMEDIA ENTERTAINMENTAn Open Champion flies a short hop toward Lansing and the fuel gauge reads empty-800 meters from the runway, and four lives hang in the balance. Meters From Safety: Tony Lema's Fatal Fuel Gauge Failure In this episode, we follow the late career...
Meters From Safety: Tony Lema's Fatal Fuel Gauge Failure

In this episode, we follow the late career and final flight of Tony Lema, tracing his rise from childhood hardship to golf stardom and the mechanical failure that ended a Sunday approach. How did a single number on a fuel gauge intersect with a champion’s trajectory and four lives on board?

Person: Tony Lema
Event: Aircraft crash on approach to Lansing Municipal Airport
Date: July 24, 1966
Location: Lansing Municipal Airport / golf course water hazard
Topic: Fuel gauge reading empty during final approach

- Tony Lema grew up in Oakland after his father died when he was three, raised on public assistance and introduced to golf at Lake Chabot.
- He served in the United States Marine Corps, returned in 1955, and worked as an assistant professional before rising on tour.
- Eddie Lowery financed Lema early on with $200 weekly for a 33% share, a debt that exceeded $11,000 by 1963 and helped stabilize his career.
- Nicknamed "Champagne Tony" after buying champagne for the press in 1962, Lema amassed twelve wins and a Ryder Cup record that still stands.
- On July 24, 1966, a Beechcraft Bonanza came down in a golf course water hazard eight hundred meters short of Lansing runway after the fuel gauge read empty.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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-bomber-s-wing-rock-went-unanswered-did-they-make-it-in-time--74905906
The bomber's wing rock went unanswered - did they make it in time?

In this episode, we follow the final hour of American Airlines Flight 28 and the Lockheed Ventura B-34 that converged over Southern California in October 1942. The episode lays out the people, decisions and six suspenseful sixty seconds that preceded the crash and asks how a pilot’s maneuver became the central fact investigators had to reckon with.

Date: October 23, 1942
Aircraft: Douglas DC-3 (NC16017) and Lockheed Ventura B-34
Location: Chino Canyon, at roughly 9,000 feet
People: Captain Charles Fred Pedley; First Officer Louis Frederick Reppert Jr.; Lieutenant William Norman Wilson; Sergeant Robert Reed Leicht; passenger Ralph Rainger
Status: Collision; three crew and nine passengers on DC-3, bomber landed in Palm Springs

- Flight 28 departed Burbank at 4:36 p.m. with 12 people aboard and cruised through San Gorgonio Pass toward Indio at 9,000 feet.
- Ten minutes earlier a B-34 had taken off from Long Beach; its pilot circled near March Field before positioning to intercept the airliner.
- Wilson and Reppert had met the night before; testimony later focused on Wilson’s intent to signal Reppert in the air.
- At about 5:15 p.m. the bomber rolled its wings alongside the DC-3 - a deliberate greeting that went unanswered.
- Sixty seconds elapsed from the first wing rock to the moment the DC-3 struck the canyon wall, triggering three investigations and conflicting conclusions.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905906Fri, 04 Sep 2026 18:40:47 +0000OBOMEDIA ENTERTAINMENTA military bomber rolls its wings beside a DC-3 over Chino Canyon and the airliner does not respond - did they make it in time? The bomber's wing rock went unanswered - did they make it in time? In this episode, we follow the final hour of...
The bomber's wing rock went unanswered - did they make it in time?

In this episode, we follow the final hour of American Airlines Flight 28 and the Lockheed Ventura B-34 that converged over Southern California in October 1942. The episode lays out the people, decisions and six suspenseful sixty seconds that preceded the crash and asks how a pilot’s maneuver became the central fact investigators had to reckon with.

Date: October 23, 1942
Aircraft: Douglas DC-3 (NC16017) and Lockheed Ventura B-34
Location: Chino Canyon, at roughly 9,000 feet
People: Captain Charles Fred Pedley; First Officer Louis Frederick Reppert Jr.; Lieutenant William Norman Wilson; Sergeant Robert Reed Leicht; passenger Ralph Rainger
Status: Collision; three crew and nine passengers on DC-3, bomber landed in Palm Springs

- Flight 28 departed Burbank at 4:36 p.m. with 12 people aboard and cruised through San Gorgonio Pass toward Indio at 9,000 feet.
- Ten minutes earlier a B-34 had taken off from Long Beach; its pilot circled near March Field before positioning to intercept the airliner.
- Wilson and Reppert had met the night before; testimony later focused on Wilson’s intent to signal Reppert in the air.
- At about 5:15 p.m. the bomber rolled its wings alongside the DC-3 - a deliberate greeting that went unanswered.
- Sixty seconds elapsed from the first wing rock to the moment the DC-3 struck the canyon wall, triggering three investigations and conflicting conclusions.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1357falsefullhttps://www.spreaker.com/episode/the-invisible-crack-in-the-rudder-locked-it-and-robbed-them-of-radio-time--74905904
The invisible crack in the rudder locked it and robbed them of radio time

In this episode, we hear how a transpacific flight turned into three hours of improvised flying when an invisible fracture locked the rudder and cut reliable radio contact over the Bering Sea. The episode follows the crew’s decisions, the aircraft’s history, and the gaps in procedures that forced four pilots to keep 239 people alive by feel and calculation alone. What choices did they make as isolation and an unknown mechanical failure closed in?

Aircraft: Boeing 747-400 (first 747-400 built, N661US)
Flight: Northwest Airlines Flight 85
Date: October 9, 2002
Location: Bering Sea corridor (communications dead zone)
Crew: Capt. John Hanson; Capt. Frank Geib; FOs David Smith and Mike Fagan

- The aircraft was the prototype 747-400 (registration N661US), delivered to Northwest on December 8, 1989, after serving as Boeing’s testbed.
- At 17:40 Alaska Daylight Time the jet at FL350 began an uncommanded 30-40° roll to the left with no pilot input.
- Geib and Fagan were at the controls while Hanson and Smith were resting; the crew immediately ruled out asymmetric thrust as the cause.
- The rudder had locked at full deflection due to a fracture invisible to naked-eye inspection and undetectable by routine preflight checks.
- The Bering Sea transit placed the aircraft in a communications dead zone relying on HF radio and position reports, complicating contact with ground controllers and the airline’s engineers.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905904Fri, 04 Sep 2026 18:40:42 +0000OBOMEDIA ENTERTAINMENTA prototype 747-400 rolls hard left at 35,000 ft over the Bering Sea - can the crew fight a locked rudder and make radio contact in time? The invisible crack in the rudder locked it and robbed them of radio time In this episode, we hear how a...
The invisible crack in the rudder locked it and robbed them of radio time

In this episode, we hear how a transpacific flight turned into three hours of improvised flying when an invisible fracture locked the rudder and cut reliable radio contact over the Bering Sea. The episode follows the crew’s decisions, the aircraft’s history, and the gaps in procedures that forced four pilots to keep 239 people alive by feel and calculation alone. What choices did they make as isolation and an unknown mechanical failure closed in?

Aircraft: Boeing 747-400 (first 747-400 built, N661US)
Flight: Northwest Airlines Flight 85
Date: October 9, 2002
Location: Bering Sea corridor (communications dead zone)
Crew: Capt. John Hanson; Capt. Frank Geib; FOs David Smith and Mike Fagan

- The aircraft was the prototype 747-400 (registration N661US), delivered to Northwest on December 8, 1989, after serving as Boeing’s testbed.
- At 17:40 Alaska Daylight Time the jet at FL350 began an uncommanded 30-40° roll to the left with no pilot input.
- Geib and Fagan were at the controls while Hanson and Smith were resting; the crew immediately ruled out asymmetric thrust as the cause.
- The rudder had locked at full deflection due to a fracture invisible to naked-eye inspection and undetectable by routine preflight checks.
- The Bering Sea transit placed the aircraft in a communications dead zone relying on HF radio and position reports, complicating contact with ground controllers and the airline’s engineers.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1244falsefullhttps://www.spreaker.com/episode/the-warning-system-screamed-they-switched-it-off-two-seconds-too-late--74905902
The warning system screamed - they switched it off, two seconds too late

In this episode, we follow the short, recorded minutes on board Sukhoi Superjet 97004 after Jakarta cleared it to six thousand feet and the mountain loomed unseen in cloud. We outline the crew, the flight's purpose, and the decisions in the cockpit that preceded impact - what happened in those five minutes?

Person: Captain Alexander Yablontsev
Person: First Officer Alexander Kotchetkov
Person: Flight Navigator Oleg Shvetsov
Date: 9 May 2012
Location: Mount Salak, West Java

- Departure: Halim Perdanakusuma Airport at 14:00 for a short demonstration route over West Java
- Purpose: "Welcome Asia!" demo flight carrying 42 passengers including airline representatives and journalists
- Aircraft: Sukhoi Superjet 100, registration 97004, built in 2009 with ~800 flight hours
- Clearance: Jakarta ATC cleared descent to 6,000 feet, 1,254 feet below Mount Salak's summit at 7,254 feet
- Recorders: Flight data and cockpit voice recorders recovered within 200 meters of the tail, capturing the five-minute sequence and the crew discussion before the warning was silenced

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905902Fri, 04 Sep 2026 18:40:38 +0000OBOMEDIA ENTERTAINMENTA Sukhoi Superjet demo flight over West Java hears the terrain-warning; the crew mutes it - did they realize Mount Salak was rising beneath them? The warning system screamed - they switched it off, two seconds too late In this episode, we follow...
The warning system screamed - they switched it off, two seconds too late

In this episode, we follow the short, recorded minutes on board Sukhoi Superjet 97004 after Jakarta cleared it to six thousand feet and the mountain loomed unseen in cloud. We outline the crew, the flight's purpose, and the decisions in the cockpit that preceded impact - what happened in those five minutes?

Person: Captain Alexander Yablontsev
Person: First Officer Alexander Kotchetkov
Person: Flight Navigator Oleg Shvetsov
Date: 9 May 2012
Location: Mount Salak, West Java

- Departure: Halim Perdanakusuma Airport at 14:00 for a short demonstration route over West Java
- Purpose: "Welcome Asia!" demo flight carrying 42 passengers including airline representatives and journalists
- Aircraft: Sukhoi Superjet 100, registration 97004, built in 2009 with ~800 flight hours
- Clearance: Jakarta ATC cleared descent to 6,000 feet, 1,254 feet below Mount Salak's summit at 7,254 feet
- Recorders: Flight data and cockpit voice recorders recovered within 200 meters of the tail, capturing the five-minute sequence and the crew discussion before the warning was silenced

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1280falsefullhttps://www.spreaker.com/episode/crew-never-knew-where-they-were-the-avianca-011-crash--74905901
Imagine a Boeing 747, flown by an elite crew, crashing into three hills 12 kilometers short of its destination on a clear night, with all systems functioning perfectly. This aviation catastrophe, which killed 181 people, defies mechanical explanation. How could an experienced crew, in a fully operational aircraft, not know their location?

In this episode, we delve into the baffling crash of Avianca Flight 011 near Madrid in 1983. We explore the circumstances leading to the disaster, the state of the aircraft, and the highly qualified crew, ultimately asking what truly went wrong when everything seemed right.

Aircraft: Boeing 747-200BM Combi
Date: November 27, 1983
Location: Mejorada del Campo, Spain
Fatalities: 181
Investigation Body: Spain's CIAIAC

- The wreckage of Avianca Flight 011 was spread across three separate ridges.
- The aircraft, registered HK-2910X and nicknamed Olafo, had no mechanical failures.
- Captain Tulio Hernández had 23,215 total flight hours, with 2,432 on the 747.
- The flight was carrying notable Latin American literary and cultural figures to a conference in Bogotá.
- The ground proximity warning system (GPWS) activated before impact, but the crew did not respond correctly.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905901Fri, 04 Sep 2026 18:40:35 +0000OBOMEDIA ENTERTAINMENTCrew Never Knew Where They Were: The Avianca 011 Crash Imagine a Boeing 747, flown by an elite crew, crashing into three hills 12 kilometers short of its destination on a clear night, with all systems functioning perfectly. This aviation...
Imagine a Boeing 747, flown by an elite crew, crashing into three hills 12 kilometers short of its destination on a clear night, with all systems functioning perfectly. This aviation catastrophe, which killed 181 people, defies mechanical explanation. How could an experienced crew, in a fully operational aircraft, not know their location?

In this episode, we delve into the baffling crash of Avianca Flight 011 near Madrid in 1983. We explore the circumstances leading to the disaster, the state of the aircraft, and the highly qualified crew, ultimately asking what truly went wrong when everything seemed right.

Aircraft: Boeing 747-200BM Combi
Date: November 27, 1983
Location: Mejorada del Campo, Spain
Fatalities: 181
Investigation Body: Spain's CIAIAC

- The wreckage of Avianca Flight 011 was spread across three separate ridges.
- The aircraft, registered HK-2910X and nicknamed Olafo, had no mechanical failures.
- Captain Tulio Hernández had 23,215 total flight hours, with 2,432 on the 747.
- The flight was carrying notable Latin American literary and cultural figures to a conference in Bogotá.
- The ground proximity warning system (GPWS) activated before impact, but the crew did not respond correctly.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1324falsefullhttps://www.spreaker.com/episode/debris-falls-into-a-backyard-at-3-am-air-transport-international-flight-805--74905900
Imagine waking at 3:26 AM to the sound of walls shaking and plaster falling, only to discover aircraft wreckage in your backyard, three miles short of the runway. This chilling scene marked the beginning of a disaster that claimed four lives, but what caused an experienced crew to lose control of a Douglas DC-8 on a routine cargo flight?

In this episode, we delve into the perplexing crash of Air Transport International Flight 805, an aviation catastrophe that defied easy explanation. We explore the aircraft's history, the crew's extensive experience, and the critical evidence from the cockpit voice recorder and flight data recorder that revealed a slow accumulation of pressure, not a sudden crisis.

Date: February 15, 1992
Aircraft: Douglas DC-8-63
Location: Toledo Express Airport, Ohio
Flight: Seattle to Toledo
Crew: Captain Harry Baker, First Officer Tim Hupp, Flight Engineer Jose Montalbo, Raman Patel (non-revenue pilot)

- Wreckage fell into a residential backyard three miles short of runway zero seven at Toledo Express Airport.
- The aircraft, N794AL, was a Douglas DC-8-63 with 22,804 takeoff and landing cycles and 70,000 flight hours.
- Captain Harry Baker had 16,382 total flight hours, 2,382 on the DC-8.
- Flight Engineer Jose Montalbo had 21,697 total hours, nearly 8,000 on the DC-8 type.
- A previous incident on November 13, 1991, involved the same aircraft experiencing an in-flight cargo door opening after departing Toledo.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905900Fri, 04 Sep 2026 18:40:31 +0000OBOMEDIA ENTERTAINMENTDebris Falls Into a Backyard at 3 AM: Air Transport International Flight 805 Imagine waking at 3:26 AM to the sound of walls shaking and plaster falling, only to discover aircraft wreckage in your backyard, three miles short of the runway. This...
Imagine waking at 3:26 AM to the sound of walls shaking and plaster falling, only to discover aircraft wreckage in your backyard, three miles short of the runway. This chilling scene marked the beginning of a disaster that claimed four lives, but what caused an experienced crew to lose control of a Douglas DC-8 on a routine cargo flight?

In this episode, we delve into the perplexing crash of Air Transport International Flight 805, an aviation catastrophe that defied easy explanation. We explore the aircraft's history, the crew's extensive experience, and the critical evidence from the cockpit voice recorder and flight data recorder that revealed a slow accumulation of pressure, not a sudden crisis.

Date: February 15, 1992
Aircraft: Douglas DC-8-63
Location: Toledo Express Airport, Ohio
Flight: Seattle to Toledo
Crew: Captain Harry Baker, First Officer Tim Hupp, Flight Engineer Jose Montalbo, Raman Patel (non-revenue pilot)

- Wreckage fell into a residential backyard three miles short of runway zero seven at Toledo Express Airport.
- The aircraft, N794AL, was a Douglas DC-8-63 with 22,804 takeoff and landing cycles and 70,000 flight hours.
- Captain Harry Baker had 16,382 total flight hours, 2,382 on the DC-8.
- Flight Engineer Jose Montalbo had 21,697 total hours, nearly 8,000 on the DC-8 type.
- A previous incident on November 13, 1991, involved the same aircraft experiencing an in-flight cargo door opening after departing Toledo.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1259falsefullhttps://www.spreaker.com/episode/engines-on-the-ground-the-aeromexico-connect-2431-crash--74905899
Two jet engines lay in the dirt, 300 feet from their burning aircraft, yet every person aboard stood in a field. How did Aeromexico Connect flight 2431 produce survivors and a coherent wreckage trail when it shouldn't have?

In this episode, we cover the Aeromexico Connect 2431 crash in Durango, Mexico, revealing a critical detail buried in the official report about who was in the cockpit and what they were legally permitted to do. This detail changes everything about the aviation catastrophe.

Aircraft: Embraer 190, XA-GAL
Date: July 31, 2018
Location: Durango, Mexico
Flight Hours: 27,257
Takeoff-and-Landing Cycles: 18,200

- The Embraer 190 was built in 2008 and acquired by Aeromexico Connect in 2014.
- Captain Carlos Galván Meyran had 3,700 total flight hours, with 1,064 on the E-190.
- First Officer Daniel Dardon Chávez had 460 hours on the Embraer 190 type.
- A third pilot, José Ramón Vázquez, had zero actual flight hours on the Embraer 190.
- The aircraft reached a maximum altitude of approximately two feet above the runway surface during 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/74905899Fri, 04 Sep 2026 18:40:27 +0000OBOMEDIA ENTERTAINMENTEngines on the Ground: The Aeromexico Connect 2431 Crash Two jet engines lay in the dirt, 300 feet from their burning aircraft, yet every person aboard stood in a field. How did Aeromexico Connect flight 2431 produce survivors and a coherent...
Two jet engines lay in the dirt, 300 feet from their burning aircraft, yet every person aboard stood in a field. How did Aeromexico Connect flight 2431 produce survivors and a coherent wreckage trail when it shouldn't have?

In this episode, we cover the Aeromexico Connect 2431 crash in Durango, Mexico, revealing a critical detail buried in the official report about who was in the cockpit and what they were legally permitted to do. This detail changes everything about the aviation catastrophe.

Aircraft: Embraer 190, XA-GAL
Date: July 31, 2018
Location: Durango, Mexico
Flight Hours: 27,257
Takeoff-and-Landing Cycles: 18,200

- The Embraer 190 was built in 2008 and acquired by Aeromexico Connect in 2014.
- Captain Carlos Galván Meyran had 3,700 total flight hours, with 1,064 on the E-190.
- First Officer Daniel Dardon Chávez had 460 hours on the Embraer 190 type.
- A third pilot, José Ramón Vázquez, had zero actual flight hours on the Embraer 190.
- The aircraft reached a maximum altitude of approximately two feet above the runway surface during 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.]]>1276falsefull