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--7317291Mon, 26 Oct 2026 00:33:45 +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-beechcraft-s-engine-misfired-could-they-reach-clear-lake-in-time--74906033
The Beechcraft's Engine Misfired-Could They Reach Clear Lake in Time?

In this episode, we follow the twelve-hour chain of decisions that put Buddy Holly, Ritchie Valens, J.P. "Big Bopper" Richardson and pilot Roger Peterson on a single Beechcraft Bonanza. The narrative traces Holly's rise from Lubbock radio bands to national stardom and the fatal flight that left an envelope sealed for twenty-one years; what choices and mechanical warnings mattered most?

Person: Buddy Holly
Date: February 3, 1959
Location: Five miles northwest of Clear Lake, Iowa
Event: Beechcraft Bonanza crash after takeoff from Mason City Municipal Airport
Status: Personal effects sealed in courthouse envelope until March 1980

- Buddy Holly practiced piano, steel guitar and flat-top acoustic until his sound was fully formed, then teamed with local musicians into the Crickets.
- After a rejected Decca contract, Holly recorded "That'll Be the Day" at Norman Petty’s Clovis studio, which led to a number one hit and rapid touring success.
- On February 3, 1959, a Beechcraft Bonanza took off at 1:05 a.m. into freezing darkness from Mason City Municipal Airport with four people aboard.
- Eyewitness and administrative traces: an envelope dated April 7, 1959 held glasses, a wristwatch, a lighter, dice and watch parts and remained unopened for twenty-one years.
- In the preceding months Holly had recorded ambitious sessions, moved to Greenwich Village, married and faced complex label and royalty arrangements routed through Norman Petty.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906033Mon, 26 Oct 2026 09:00:21 +0000OBOMEDIA ENTERTAINMENTA Beechcraft with Buddy Holly aboard struggles north from Mason City toward Clear Lake after an engine misfire-can they make it to the field in time? The Beechcraft's Engine Misfired-Could They Reach Clear Lake in Time? In this episode, we...
The Beechcraft's Engine Misfired-Could They Reach Clear Lake in Time?

In this episode, we follow the twelve-hour chain of decisions that put Buddy Holly, Ritchie Valens, J.P. "Big Bopper" Richardson and pilot Roger Peterson on a single Beechcraft Bonanza. The narrative traces Holly's rise from Lubbock radio bands to national stardom and the fatal flight that left an envelope sealed for twenty-one years; what choices and mechanical warnings mattered most?

Person: Buddy Holly
Date: February 3, 1959
Location: Five miles northwest of Clear Lake, Iowa
Event: Beechcraft Bonanza crash after takeoff from Mason City Municipal Airport
Status: Personal effects sealed in courthouse envelope until March 1980

- Buddy Holly practiced piano, steel guitar and flat-top acoustic until his sound was fully formed, then teamed with local musicians into the Crickets.
- After a rejected Decca contract, Holly recorded "That'll Be the Day" at Norman Petty’s Clovis studio, which led to a number one hit and rapid touring success.
- On February 3, 1959, a Beechcraft Bonanza took off at 1:05 a.m. into freezing darkness from Mason City Municipal Airport with four people aboard.
- Eyewitness and administrative traces: an envelope dated April 7, 1959 held glasses, a wristwatch, a lighter, dice and watch parts and remained unopened for twenty-one years.
- In the preceding months Holly had recorded ambitious sessions, moved to Greenwich Village, married and faced complex label and royalty arrangements routed through Norman Petty.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1364falsefullhttps://www.spreaker.com/episode/the-nose-gear-light-failed-and-nine-minutes-ran-out--74906032
The nose-gear light failed and nine minutes ran out

In this episode, we follow the nine-minute sequence after a nose-gear indicator failed on Senator John Heinz’s Aerostar as it neared Philadelphia while children played outside at Merion Elementary. We track the decisions, improvised checks, and communications that unfolded and ask whether those actions could avert disaster.

Person: John Heinz
Date: April 4, 1991
Location: Lower Merion Township, Pennsylvania
Aircraft: Piper PA-60 Aerostar

- Pilot used propeller spinners as an improvised visual check and reported seeing the gear appear down.
- Philadelphia tower observers stated the nose gear “appeared” extended but could not verify gear was locked.
- The Aerostar’s warning horn would sound if throttles were reduced with gear unconfirmed, but investigators concluded the crew probably never tested it.
- No cockpit voice recorder existed on the Aerostar, leaving crew conversations and actions during the nine minutes undocumented.
- A Bell 412 SP helicopter crew heard the radio exchanges and offered to visually assist the Aerostar on 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/74906032Sun, 25 Oct 2026 09:00:16 +0000OBOMEDIA ENTERTAINMENTA senator’s Aerostar nears Philadelphia with a dark nose‑gear indicator; can on-scene helicopter checks stop the clock with nine minutes left? The nose-gear light failed and nine minutes ran out In this episode, we follow the nine-minute...
The nose-gear light failed and nine minutes ran out

In this episode, we follow the nine-minute sequence after a nose-gear indicator failed on Senator John Heinz’s Aerostar as it neared Philadelphia while children played outside at Merion Elementary. We track the decisions, improvised checks, and communications that unfolded and ask whether those actions could avert disaster.

Person: John Heinz
Date: April 4, 1991
Location: Lower Merion Township, Pennsylvania
Aircraft: Piper PA-60 Aerostar

- Pilot used propeller spinners as an improvised visual check and reported seeing the gear appear down.
- Philadelphia tower observers stated the nose gear “appeared” extended but could not verify gear was locked.
- The Aerostar’s warning horn would sound if throttles were reduced with gear unconfirmed, but investigators concluded the crew probably never tested it.
- No cockpit voice recorder existed on the Aerostar, leaving crew conversations and actions during the nine minutes undocumented.
- A Bell 412 SP helicopter crew heard the radio exchanges and offered to visually assist the Aerostar on 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.]]>1126falsefullhttps://www.spreaker.com/episode/the-trim-tank-transfer-memo-that-started-a-nineteen-minute-glide--74906029
The trim-tank transfer memo that started a nineteen-minute glide

In this episode, we follow the sequence of mechanical warnings, crew decisions, and unseen fuel loss that converted Air Transat Flight 236 into a glider sixty-five nautical miles from the nearest runway. We trace the instruments, the maintenance choices on the ground, and the nineteen minutes that determined the aircraft’s fate - could the pilots diagnose the invisible leak fast enough?

Date: August 24, 2001
Aircraft: Airbus A330-243, registration C-GITS
People: Captain Robert Piché; First Officer Dirk DeJager; 306 aboard
Event: Dual engine fuel loss leading to glide
Location: 65 nautical miles off course over the Atlantic

- At 05:11 UTC a TRIM TANK XFR memo began and ran for nineteen minutes, indicating an automatic fuel transfer nobody expected.
- Engine two showed low oil temperature and high oil pressure first; crew ran standard diagnostics and assumed noncritical anomalies.
- A fuel line fracture downstream of the fuel-oil heat exchanger leaked fuel at about 13 tonnes per hour, invisible to cockpit leak detection.
- Fuel quantity and estimated fuel-at-destination figures began a slow, puzzling decline that the crew interpreted as possible instrument error.
- The aircraft lost both engines and became a glider 65 nautical miles from the nearest runway, after maintenance decisions on the ground set the stage.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906029Sat, 24 Oct 2026 09:00:17 +0000OBOMEDIA ENTERTAINMENTA memo about a trim-tank transfer appears midflight, and an A330 with 306 aboard becomes a powerless glider - did they make it in time? The trim-tank transfer memo that started a nineteen-minute glide In this episode, we follow the sequence of...
The trim-tank transfer memo that started a nineteen-minute glide

In this episode, we follow the sequence of mechanical warnings, crew decisions, and unseen fuel loss that converted Air Transat Flight 236 into a glider sixty-five nautical miles from the nearest runway. We trace the instruments, the maintenance choices on the ground, and the nineteen minutes that determined the aircraft’s fate - could the pilots diagnose the invisible leak fast enough?

Date: August 24, 2001
Aircraft: Airbus A330-243, registration C-GITS
People: Captain Robert Piché; First Officer Dirk DeJager; 306 aboard
Event: Dual engine fuel loss leading to glide
Location: 65 nautical miles off course over the Atlantic

- At 05:11 UTC a TRIM TANK XFR memo began and ran for nineteen minutes, indicating an automatic fuel transfer nobody expected.
- Engine two showed low oil temperature and high oil pressure first; crew ran standard diagnostics and assumed noncritical anomalies.
- A fuel line fracture downstream of the fuel-oil heat exchanger leaked fuel at about 13 tonnes per hour, invisible to cockpit leak detection.
- Fuel quantity and estimated fuel-at-destination figures began a slow, puzzling decline that the crew interpreted as possible instrument error.
- The aircraft lost both engines and became a glider 65 nautical miles from the nearest runway, after maintenance decisions on the ground set the stage.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1249falsefullhttps://www.spreaker.com/episode/the-skipped-walk-around-left-the-wings-iced-did-they-lift-in-time--74906028
The skipped walk‑around left the wings iced - did they lift in time?

In this episode, we follow Bek Air Flight 2100 from gate to runway, detailing the decisions, procedures and conditions that led to a takeoff with unnoticed ice on the wings. How did routine shortcuts, sparse winter training and missing records align on one cold morning?

Date: December 27, 2019
Aircraft: Fokker 100 (UP‑F1007)
Location: Almaty International Airport, Kazakhstan
Passengers: 93 passengers, 5 children, 3 infants (98 people on board)
Temperature: -12°C on the ramp; inversion layer ~1,000 ft above runway

- Pushback at 07:22 after hours of freezing fog left ice building on the wings while no tactile walk-around was performed.
- Three hours earlier another pilot reported frost on slats and fuel tanks; the message was logged but not acted on by Flight 2100 crew.
- Bek Air mechanics were swapping engine components without data plates or Rolls‑Royce maintenance reports, leaving service histories unverifiable.
- Neither captain nor first officer had received specific winter-operations training; the operator’s program lacked cold-weather requirements.
- Ice accumulated unevenly on the wings causing asymmetric contamination that would affect lift during initial climb.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906028Fri, 23 Oct 2026 09:00:25 +0000OBOMEDIA ENTERTAINMENTA Fokker 100 at Almaty sits iced in freezing fog before a rushed takeoff; a missed walk-around and asymmetric ice leave lift in doubt. The skipped walk‑around left the wings iced - did they lift in time? In this episode, we follow Bek Air Flight...
The skipped walk‑around left the wings iced - did they lift in time?

In this episode, we follow Bek Air Flight 2100 from gate to runway, detailing the decisions, procedures and conditions that led to a takeoff with unnoticed ice on the wings. How did routine shortcuts, sparse winter training and missing records align on one cold morning?

Date: December 27, 2019
Aircraft: Fokker 100 (UP‑F1007)
Location: Almaty International Airport, Kazakhstan
Passengers: 93 passengers, 5 children, 3 infants (98 people on board)
Temperature: -12°C on the ramp; inversion layer ~1,000 ft above runway

- Pushback at 07:22 after hours of freezing fog left ice building on the wings while no tactile walk-around was performed.
- Three hours earlier another pilot reported frost on slats and fuel tanks; the message was logged but not acted on by Flight 2100 crew.
- Bek Air mechanics were swapping engine components without data plates or Rolls‑Royce maintenance reports, leaving service histories unverifiable.
- Neither captain nor first officer had received specific winter-operations training; the operator’s program lacked cold-weather requirements.
- Ice accumulated unevenly on the wings causing asymmetric contamination that would affect lift during initial climb.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1227falsefullhttps://www.spreaker.com/episode/last-transmission-at-10-48-how-flight-241-vanished-into-the-cardamoms--74906026
Last Transmission at 10:48: How Flight 241 Vanished into the Cardamoms

In this episode, we follow the timeline of PMTair Flight 241’s final minutes and the operational quirks around it. We lay out the decisions, the equipment gaps, and the human moments that led the aircraft toward a jungle ridge - what happened between 10:48 and 10:50 remains unanswered.

Date: June 25, 2007
Flight: PMTair Flight 241
Aircraft: Antonov An-24B, registration XU-U4A, manufactured 1969
Passengers: 22 (including 13 South Korean nationals and 3 Czech nationals)
Crew experience: Captain 10,345 hours; First Officer 3,500 hours; Flight Engineer present

- Departure from Siem Reap at 10:01 and normal climb; blip later drifted off planned route on Phnom Penh radar without controller query.
- Crew asked Sihanoukville about destination weather at 10:36 while still 60 nm out on a short hop that should have been near completion.
- Handed off to Sihanoukville at 10:42; contact described as normal before descent and loss from Phnom Penh radar at 10:46.
- Last transmission: pilot read back a descent clearance at 10:48 over the Cardamom Mountains; two minutes later the aircraft was gone.
- Investigators found wreckage with both flight recorders useless and a chain of small, individually explainable decisions converging on a 2,700 ft jungle ridge.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906026Thu, 22 Oct 2026 09:00:19 +0000OBOMEDIA ENTERTAINMENTA pilot reads a descent clearance over Cambodia's Cardamom Mountains; Flight 241 vanishes two minutes later - did they make it in time? Last Transmission at 10:48: How Flight 241 Vanished into the Cardamoms In this episode, we follow the...
Last Transmission at 10:48: How Flight 241 Vanished into the Cardamoms

In this episode, we follow the timeline of PMTair Flight 241’s final minutes and the operational quirks around it. We lay out the decisions, the equipment gaps, and the human moments that led the aircraft toward a jungle ridge - what happened between 10:48 and 10:50 remains unanswered.

Date: June 25, 2007
Flight: PMTair Flight 241
Aircraft: Antonov An-24B, registration XU-U4A, manufactured 1969
Passengers: 22 (including 13 South Korean nationals and 3 Czech nationals)
Crew experience: Captain 10,345 hours; First Officer 3,500 hours; Flight Engineer present

- Departure from Siem Reap at 10:01 and normal climb; blip later drifted off planned route on Phnom Penh radar without controller query.
- Crew asked Sihanoukville about destination weather at 10:36 while still 60 nm out on a short hop that should have been near completion.
- Handed off to Sihanoukville at 10:42; contact described as normal before descent and loss from Phnom Penh radar at 10:46.
- Last transmission: pilot read back a descent clearance at 10:48 over the Cardamom Mountains; two minutes later the aircraft was gone.
- Investigators found wreckage with both flight recorders useless and a chain of small, individually explainable decisions converging on a 2,700 ft jungle ridge.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1180falsefullhttps://www.spreaker.com/episode/the-vor-beacon-pulled-planes-a-mile-off-course-did-they-make-it--74906023
The VOR beacon pulled planes a mile off course - did they make it?

In this episode, we lay out the flight, the political stakes, and the pieces investigators had to assemble after a King Air A100 crashed two miles short of Eveleth’s runway. Who the passengers were, what the pilots’ records showed, and how a faulty VOR became central to the reconstruction drive the story - what crucial questions remain?

Person: Paul Wellstone
Date: October 25, 2002
Location: Eveleth, Minnesota
Event: Beechcraft King Air A100 crash
Status: No flight recorders aboard

- The King Air A100 departed for a roughly one-hour charter flight carrying eight people, including Senator Paul Wellstone, en route to Eveleth on the morning of October 25, 2002.
- The aircraft struck dense forest about two miles short of the Eveleth runway at 10:22 a.m.; there were no survivors and the plane had no black boxes.
- Technicians tested the local VOR beacon the next morning and found it pulled aircraft approximately one mile off course, aiming toward the eventual impact site.
- Investigators reconstructed the final minutes using radar returns, radio transcripts, the damaged VOR, and testimony from pilots who had flown with the two cockpit crew members.
- The NTSB cited crew error, the FBI investigated possible sabotage, and documents from that probe were sealed for eight years, leaving unanswered threads about the flight’s last decisions.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906023Wed, 21 Oct 2026 09:00:22 +0000OBOMEDIA ENTERTAINMENTA damaged VOR beacon led a charter plane a mile off course toward a Minnesota runway - did they make it in time? The VOR beacon pulled planes a mile off course - did they make it? In this episode, we lay out the flight, the political stakes, and...
The VOR beacon pulled planes a mile off course - did they make it?

In this episode, we lay out the flight, the political stakes, and the pieces investigators had to assemble after a King Air A100 crashed two miles short of Eveleth’s runway. Who the passengers were, what the pilots’ records showed, and how a faulty VOR became central to the reconstruction drive the story - what crucial questions remain?

Person: Paul Wellstone
Date: October 25, 2002
Location: Eveleth, Minnesota
Event: Beechcraft King Air A100 crash
Status: No flight recorders aboard

- The King Air A100 departed for a roughly one-hour charter flight carrying eight people, including Senator Paul Wellstone, en route to Eveleth on the morning of October 25, 2002.
- The aircraft struck dense forest about two miles short of the Eveleth runway at 10:22 a.m.; there were no survivors and the plane had no black boxes.
- Technicians tested the local VOR beacon the next morning and found it pulled aircraft approximately one mile off course, aiming toward the eventual impact site.
- Investigators reconstructed the final minutes using radar returns, radio transcripts, the damaged VOR, and testimony from pilots who had flown with the two cockpit crew members.
- The NTSB cited crew error, the FBI investigated possible sabotage, and documents from that probe were sealed for eight years, leaving unanswered threads about the flight’s last decisions.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1181falsefullhttps://www.spreaker.com/episode/the-drifting-heading-that-erased-their-minutes-and-doomed-the-flight--74906021
The drifting heading that erased their minutes and doomed the flight

In this episode, we follow SATA Flight SP530M on a short inter-island run in the Azores that turns unexpected as instruments, weather, and routine decisions collide. We trace the chain of small navigational errors, crew calls, and shifting winds that set the plane toward a mountain and ask how those minutes vanished.

Date: December 11, 1999
Flight: SP530M
Aircraft: British Aerospace ATP, registration CS-TGM, named Graciosa
Crew: Captain Arnaldo Mesquita (55), First Officer António Magalhães (46)
Location: Azores, approaching Horta (São Jorge vicinity)

- Departure from Ponta Delgada at 09:37 for a short hop to Horta then Flores with 33 passengers aboard.
- Pilots requested a modified route threading between Pico and São Jorge and to intercept Horta VOR at 250°.
- Solid low cloud and winds shifting from southwest to strong northerlies produced 30-45 knot gusts that steadily pushed the aircraft off track.
- At 10:03 the crew reported passing waypoint LIMA-MIKE while the aircraft was already 14 nautical miles off course due to uncorrected dead reckoning.
- Seventeen seconds elapsed between the cockpit alarm at 10:17:17 and the collision with terrain; no distress call was transmitted.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906021Tue, 20 Oct 2026 09:00:19 +0000OBOMEDIA ENTERTAINMENTA regional turboprop drifts off course toward a fogged Azores mountain; an alarm gives the crew seconds to avoid impact - did they make it in time? The drifting heading that erased their minutes and doomed the flight In this episode, we follow...
The drifting heading that erased their minutes and doomed the flight

In this episode, we follow SATA Flight SP530M on a short inter-island run in the Azores that turns unexpected as instruments, weather, and routine decisions collide. We trace the chain of small navigational errors, crew calls, and shifting winds that set the plane toward a mountain and ask how those minutes vanished.

Date: December 11, 1999
Flight: SP530M
Aircraft: British Aerospace ATP, registration CS-TGM, named Graciosa
Crew: Captain Arnaldo Mesquita (55), First Officer António Magalhães (46)
Location: Azores, approaching Horta (São Jorge vicinity)

- Departure from Ponta Delgada at 09:37 for a short hop to Horta then Flores with 33 passengers aboard.
- Pilots requested a modified route threading between Pico and São Jorge and to intercept Horta VOR at 250°.
- Solid low cloud and winds shifting from southwest to strong northerlies produced 30-45 knot gusts that steadily pushed the aircraft off track.
- At 10:03 the crew reported passing waypoint LIMA-MIKE while the aircraft was already 14 nautical miles off course due to uncorrected dead reckoning.
- Seventeen seconds elapsed between the cockpit alarm at 10:17:17 and the collision with terrain; no distress call was transmitted.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1182falsefullhttps://www.spreaker.com/episode/the-landing-gear-extended-and-burned-sixteen-seconds-of-fuel--74906020
The landing gear extended and burned sixteen seconds of fuel

In this episode, we follow the flight path, crew and decisions aboard Kish Air flight 7170 that set the stage for a catastrophic sixteen-second window over Sharjah. The episode traces the routine route, the known technical vulnerability, and the crew actions that led up to those critical seconds - how many choices had to align wrong for them to become lethal?

Aircraft: Fokker 50, registration EP-LCA
Date: February 10, 2004
Flight: 7170
Passengers and crew: 42 passengers, 6 crew; at least twelve nationalities
Maintenance: anti-skid modification scheduled for May 2004; last Type A check December 24, 2003

- Landing gear extended while the aircraft was still four hundred feet in the air during approach to Sharjah.
- A dormant flaw in the anti-skid control unit sent a ground signal to the solenoids immediately after gear extension.
- The modification Fokker announced in 2003 had been scheduled but not installed on EP-LCA by February 2004.
- Captain Ahmed Hosseini and First Officer Nemat Panahian exchanged control mid-cruise without a formal transfer or completed brief.
- Every passenger was traveling to Kish Island to exit and re-enter the UAE to renew residency paperwork, making the flight mandatory for many.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906020Mon, 19 Oct 2026 09:00:16 +0000OBOMEDIA ENTERTAINMENTLanding gear extended as the Fokker 50 descended over Sharjah - sixteen seconds that may decide the passengers' fate. Did they make it in time? The landing gear extended and burned sixteen seconds of fuel In this episode, we follow the flight...
The landing gear extended and burned sixteen seconds of fuel

In this episode, we follow the flight path, crew and decisions aboard Kish Air flight 7170 that set the stage for a catastrophic sixteen-second window over Sharjah. The episode traces the routine route, the known technical vulnerability, and the crew actions that led up to those critical seconds - how many choices had to align wrong for them to become lethal?

Aircraft: Fokker 50, registration EP-LCA
Date: February 10, 2004
Flight: 7170
Passengers and crew: 42 passengers, 6 crew; at least twelve nationalities
Maintenance: anti-skid modification scheduled for May 2004; last Type A check December 24, 2003

- Landing gear extended while the aircraft was still four hundred feet in the air during approach to Sharjah.
- A dormant flaw in the anti-skid control unit sent a ground signal to the solenoids immediately after gear extension.
- The modification Fokker announced in 2003 had been scheduled but not installed on EP-LCA by February 2004.
- Captain Ahmed Hosseini and First Officer Nemat Panahian exchanged control mid-cruise without a formal transfer or completed brief.
- Every passenger was traveling to Kish Island to exit and re-enter the UAE to renew residency paperwork, making the flight mandatory for many.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1315falsefullhttps://www.spreaker.com/episode/the-rudder-pedals-slammed-could-crews-stop-a-falling-tail-fin-in-time--74906018
The rudder pedals slammed; could crews stop a falling tail fin in time?

In this episode, we present the sequence of events from takeoff to catastrophe on American Airlines Flight 587, showing the procedures, training, and forces at play as crews reacted in real time. What decisions and six seconds of training might explain how a routine departure became a deadly structural failure?

Person: Captain Edward States
Person: First Officer Sten Molin
Date: November 12, 2001
Aircraft: Airbus A300-600R, registration N14053
Location: Departure from John F. Kennedy International Airport over Belle Harbor, Queens

- At 09:15:36 the flight recorder logged an initial rolling jolt consistent with wake turbulence from a preceding Boeing 747.
- First Officer Sten Molin was the pilot flying and had completed American Airlines’ Advanced Aircraft Maneuvering Program training for wake turbulence encounters.
- A set of hard rudder pedal inputs applied forces of approximately 200 to 3,000 pounds to the fin's attachment bolts within seconds.
- The A300’s vertical tail is attached at six bolted points, each engineered to hold roughly 100,000 pounds of force, and the fin weighed about 2,000 pounds.
- The entire sequence from first pedal input to cockpit voice recorder silence lasted sixty-six seconds.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906018Sun, 18 Oct 2026 09:00:16 +0000OBOMEDIA ENTERTAINMENTA pilot trained to counter wake turbulence slammed the rudder pedals as an Airbus A300 climbed out of JFK-could crews stop a falling tail fin in time? The rudder pedals slammed; could crews stop a falling tail fin in time? In this episode, we...
The rudder pedals slammed; could crews stop a falling tail fin in time?

In this episode, we present the sequence of events from takeoff to catastrophe on American Airlines Flight 587, showing the procedures, training, and forces at play as crews reacted in real time. What decisions and six seconds of training might explain how a routine departure became a deadly structural failure?

Person: Captain Edward States
Person: First Officer Sten Molin
Date: November 12, 2001
Aircraft: Airbus A300-600R, registration N14053
Location: Departure from John F. Kennedy International Airport over Belle Harbor, Queens

- At 09:15:36 the flight recorder logged an initial rolling jolt consistent with wake turbulence from a preceding Boeing 747.
- First Officer Sten Molin was the pilot flying and had completed American Airlines’ Advanced Aircraft Maneuvering Program training for wake turbulence encounters.
- A set of hard rudder pedal inputs applied forces of approximately 200 to 3,000 pounds to the fin's attachment bolts within seconds.
- The A300’s vertical tail is attached at six bolted points, each engineered to hold roughly 100,000 pounds of force, and the fin weighed about 2,000 pounds.
- The entire sequence from first pedal input to cockpit voice recorder silence lasted sixty-six seconds.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1303falsefullhttps://www.spreaker.com/episode/black-sea-landing-gear-down-why-armavia-a320-dove-at-night--74906017
Black Sea Landing Gear Down: Why Armavia A320 Dove at Night

In this episode, we lay out the flight, the people, and the cockpit timeline that led to Armavia Flight 967 approaching Sochi. You’ll hear how decisions, fatigue, and automation interacted in the final minutes - and the question remains: did they make it in time?

Flight: Armavia Flight 967
Date: May 3, 2006 (early hours local)
Location: Off the coast of Sochi, Russia / en route Zvartnots Yerevan-Sochi
Aircraft: Airbus A320, msn 547, named Mesrop Mashtots
Passengers and crew: 113 on board (105 passengers, 8 crew)

- Captain Grigor Grigoryan (40) and First Officer Arman Davtyan (29) were both qualified on the A320 with documented type ratings.
- The aircraft had over 10,000 flight hours, was airworthy, and had served previous operators before joining Armavia in 2004.
- In cruise Davtyan told the captain he was fatigued; the exchange was captured on the cockpit voice recorder.
- During descent Grigoryan expressed frustration with the autopilot’s managed-descent mode and favored his own instincts.
- At high speed the aircraft struck the sea with its landing gear down, and the cockpit voice recorder captured conflicting control inputs in the final ninety seconds.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906017Sat, 17 Oct 2026 09:00:22 +0000OBOMEDIA ENTERTAINMENTA plane named Mesrop Mashtots descends toward Sochi at night - can two fatigued pilots stop a routine approach from becoming catastrophe? Black Sea Landing Gear Down: Why Armavia A320 Dove at Night In this episode, we lay out the flight, the...
Black Sea Landing Gear Down: Why Armavia A320 Dove at Night

In this episode, we lay out the flight, the people, and the cockpit timeline that led to Armavia Flight 967 approaching Sochi. You’ll hear how decisions, fatigue, and automation interacted in the final minutes - and the question remains: did they make it in time?

Flight: Armavia Flight 967
Date: May 3, 2006 (early hours local)
Location: Off the coast of Sochi, Russia / en route Zvartnots Yerevan-Sochi
Aircraft: Airbus A320, msn 547, named Mesrop Mashtots
Passengers and crew: 113 on board (105 passengers, 8 crew)

- Captain Grigor Grigoryan (40) and First Officer Arman Davtyan (29) were both qualified on the A320 with documented type ratings.
- The aircraft had over 10,000 flight hours, was airworthy, and had served previous operators before joining Armavia in 2004.
- In cruise Davtyan told the captain he was fatigued; the exchange was captured on the cockpit voice recorder.
- During descent Grigoryan expressed frustration with the autopilot’s managed-descent mode and favored his own instincts.
- At high speed the aircraft struck the sea with its landing gear down, and the cockpit voice recorder captured conflicting control inputs in the final ninety seconds.

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

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

In this episode, we present the documented sequence of maintenance decisions, damaged parts, and cockpit silence that preceded a catastrophic failure on May 25, 1979. What procedural shortcut and missed signals set up the crisis, and could anyone have known in time?

Date: May 25, 1979
Event: Engine separation during takeoff at O'Hare International Airport
Aircraft: McDonnell Douglas DC-10, registration N110AA
Maintenance: Engine and pylon removed together in Tulsa, March 29-30, 1979
Margin: Aircraft was six knots below stall with no cockpit warnings

- A $58 shortcut: Tulsa crew used a forklift to remove engine and pylon as one unit, cutting procedure steps from 79 to 27.
- A McDonnell Douglas representative warned that the combined removal method carried risk, but the procedure was used anyway.
- During the forklift operation a rear attachment fitting on the pylon was bent, damage invisible to naked-eye inspection.
- The aircraft flew for eight weeks and dozens of flights while a fatigue crack grew through the damaged fitting with each pressurization cycle.
- From engine separation to the aircraft rolling past the point of no return was 31 seconds, with no warning lights or alarms reaching the cockpit.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906015Fri, 16 Oct 2026 09:00:28 +0000OBOMEDIA ENTERTAINMENTA bent pylon fitting from a Tulsa shortcut cracks unseen as American Airlines Flight 191 climbs - did they make it in time? The bent pylon fitting failed six knots below stall - did they make it? In this episode, we present the documented...
The bent pylon fitting failed six knots below stall - did they make it?

In this episode, we present the documented sequence of maintenance decisions, damaged parts, and cockpit silence that preceded a catastrophic failure on May 25, 1979. What procedural shortcut and missed signals set up the crisis, and could anyone have known in time?

Date: May 25, 1979
Event: Engine separation during takeoff at O'Hare International Airport
Aircraft: McDonnell Douglas DC-10, registration N110AA
Maintenance: Engine and pylon removed together in Tulsa, March 29-30, 1979
Margin: Aircraft was six knots below stall with no cockpit warnings

- A $58 shortcut: Tulsa crew used a forklift to remove engine and pylon as one unit, cutting procedure steps from 79 to 27.
- A McDonnell Douglas representative warned that the combined removal method carried risk, but the procedure was used anyway.
- During the forklift operation a rear attachment fitting on the pylon was bent, damage invisible to naked-eye inspection.
- The aircraft flew for eight weeks and dozens of flights while a fatigue crack grew through the damaged fitting with each pressurization cycle.
- From engine separation to the aircraft rolling past the point of no return was 31 seconds, with no warning lights or alarms reaching the cockpit.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1321falsefullhttps://www.spreaker.com/episode/the-pylon-flange-cracked-during-removal-did-they-reach-safety--74906014
The pylon flange cracked during removal - did they reach safety?

In this episode, we follow the thirty-one seconds after American Airlines Flight 191 lost an engine at rotation and the maintenance decisions that preceded it. The episode traces the chain from a combined engine-pylon removal shortcut in Tulsa to the unnoticed crack that grew over weeks - but did anyone foresee the consequence?

Date: May 25, 1979
Flight: American Airlines Flight 191
Aircraft: McDonnell Douglas DC-10, N110AA
Maintenance event: Engine and pylon removed together March 29-30, 1979
Fatalities: 273

- The airline used a combined engine-and-pylon removal method in Tulsa to save roughly 200 labor hours per aircraft.
- The combined removal stressed the pylon aft bulkhead flange in ways the procedure wasn’t designed to handle.
- During the Tulsa work, a forklift-supported engine-pylon assembly shifted and produced an undetected crack in the flange.
- The cracked flange went unnoticed through inspections and the aircraft flew nearly two months afterward.
- The left engine and pylon separated at the exact instant of rotation at O'Hare, 15:59, sending the engine onto runway 32R while the airframe continued airborne.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906014Thu, 15 Oct 2026 09:00:25 +0000OBOMEDIA ENTERTAINMENTAn engine and pylon tore free the instant Flight 191 rotated at O'Hare-did the maintenance shortcut and a cracked pylon flange doom everyone aboard? The pylon flange cracked during removal - did they reach safety? In this episode, we follow the...
The pylon flange cracked during removal - did they reach safety?

In this episode, we follow the thirty-one seconds after American Airlines Flight 191 lost an engine at rotation and the maintenance decisions that preceded it. The episode traces the chain from a combined engine-pylon removal shortcut in Tulsa to the unnoticed crack that grew over weeks - but did anyone foresee the consequence?

Date: May 25, 1979
Flight: American Airlines Flight 191
Aircraft: McDonnell Douglas DC-10, N110AA
Maintenance event: Engine and pylon removed together March 29-30, 1979
Fatalities: 273

- The airline used a combined engine-and-pylon removal method in Tulsa to save roughly 200 labor hours per aircraft.
- The combined removal stressed the pylon aft bulkhead flange in ways the procedure wasn’t designed to handle.
- During the Tulsa work, a forklift-supported engine-pylon assembly shifted and produced an undetected crack in the flange.
- The cracked flange went unnoticed through inspections and the aircraft flew nearly two months afterward.
- The left engine and pylon separated at the exact instant of rotation at O'Hare, 15:59, sending the engine onto runway 32R while the airframe continued airborne.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1218falsefullhttps://www.spreaker.com/episode/the-night-an-md-82-stopped-flying-surviving-flight-255-s-silence--74906012
The Night an MD‑82 Stopped Flying: Surviving Flight 255's Silence

In this episode, we follow the moments before and after Northwest Airlines Flight 255’s fatal departure and the puzzling aftermath investigators faced. The episode traces the flight crew’s experience, the airplane’s configuration, and the single routine step that may have mattered most - but did it leave enough warning to stop the crash?

Person: Captain John R. Maus
Person: First Officer David J. Dodds
Date: August 16, 1987
Location: Detroit Metropolitan Airport, runway 3C
Aircraft: McDonnell Douglas MD-82, registration N312RC

- The MD-82 lifted off at 20:44 and was airborne for less than ninety seconds before control was lost.
- Flight crew together had nearly 29,000 hours of experience and conversed calmly on the cockpit voice recorder in the final minutes.
- Performance calculations were filed for runways 21L/21R, but the crew was cleared to depart from the shorter runway 3C that night.
- The aircraft’s takeoff weight of 144,046 pounds was within limits only if the airplane was configured correctly for takeoff.
- Investigators found the airplane rolled left immediately after liftoff and no obvious mechanical failure or lightning strike explained why it stopped flying.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906012Wed, 14 Oct 2026 09:00:20 +0000OBOMEDIA ENTERTAINMENTA routine MD-82 takes off from Detroit and, moments later, simply stops flying-could a single missed checklist item doom everyone on board? The Night an MD‑82 Stopped Flying: Surviving Flight 255's Silence In this episode, we follow the moments...
The Night an MD‑82 Stopped Flying: Surviving Flight 255's Silence

In this episode, we follow the moments before and after Northwest Airlines Flight 255’s fatal departure and the puzzling aftermath investigators faced. The episode traces the flight crew’s experience, the airplane’s configuration, and the single routine step that may have mattered most - but did it leave enough warning to stop the crash?

Person: Captain John R. Maus
Person: First Officer David J. Dodds
Date: August 16, 1987
Location: Detroit Metropolitan Airport, runway 3C
Aircraft: McDonnell Douglas MD-82, registration N312RC

- The MD-82 lifted off at 20:44 and was airborne for less than ninety seconds before control was lost.
- Flight crew together had nearly 29,000 hours of experience and conversed calmly on the cockpit voice recorder in the final minutes.
- Performance calculations were filed for runways 21L/21R, but the crew was cleared to depart from the shorter runway 3C that night.
- The aircraft’s takeoff weight of 144,046 pounds was within limits only if the airplane was configured correctly for takeoff.
- Investigators found the airplane rolled left immediately after liftoff and no obvious mechanical failure or lightning strike explained why it stopped flying.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1076falsefullhttps://www.spreaker.com/episode/the-transmitter-that-stayed-in-fairbanks-cost-them-thirty-nine-days--74906010
The transmitter that stayed in Fairbanks cost them thirty-nine days

In this episode, we lay out the sequence of events surrounding the October 16, 1972 disappearance of a twin-engine Cessna with four men aboard and the puzzling absence of its emergency locator transmitter. The episode traces who was on the flight, what was known about the device, and why the search never recorded a confirmed emergency signal.

Person: Thomas Hale Boggs
Date: October 16, 1972
Location: Alaska Range / flight from Anchorage to Juneau
Event: Disappearance of Cessna 310 with four aboard
Item: Emergency locator transmitter confirmed left airport in another aircraft

- The Cessna 310 departed Anchorage at 9:59 AM with pilot Don Jonz, Rep. Nick Begich, aide Russell Brown, and Hale Boggs aboard.
- No distress call, mayday, or position report was ever transmitted after contact was lost over the Alaska Range.
- The emergency locator transmitter that should have been on the plane remained in a Fairbanks hangar for thirty-nine days.
- Search efforts became one of the largest in Alaskan history, involving the U.S. Coast Guard, Navy, Army, and Air Force across mountains and water.
- Witness testimony noted an object in the pilot’s briefcase that “looked exactly like” the transmitter, raising questions about why no confirmed signal was received.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906010Tue, 13 Oct 2026 09:00:17 +0000OBOMEDIA ENTERTAINMENTA portable emergency locator transmitter sat in a Fairbanks hangar while the Alaskan wilderness swallowed a missing Cessna-did they make it in time? The transmitter that stayed in Fairbanks cost them thirty-nine days In this episode, we lay out...
The transmitter that stayed in Fairbanks cost them thirty-nine days

In this episode, we lay out the sequence of events surrounding the October 16, 1972 disappearance of a twin-engine Cessna with four men aboard and the puzzling absence of its emergency locator transmitter. The episode traces who was on the flight, what was known about the device, and why the search never recorded a confirmed emergency signal.

Person: Thomas Hale Boggs
Date: October 16, 1972
Location: Alaska Range / flight from Anchorage to Juneau
Event: Disappearance of Cessna 310 with four aboard
Item: Emergency locator transmitter confirmed left airport in another aircraft

- The Cessna 310 departed Anchorage at 9:59 AM with pilot Don Jonz, Rep. Nick Begich, aide Russell Brown, and Hale Boggs aboard.
- No distress call, mayday, or position report was ever transmitted after contact was lost over the Alaska Range.
- The emergency locator transmitter that should have been on the plane remained in a Fairbanks hangar for thirty-nine days.
- Search efforts became one of the largest in Alaskan history, involving the U.S. Coast Guard, Navy, Army, and Air Force across mountains and water.
- Witness testimony noted an object in the pilot’s briefcase that “looked exactly like” the transmitter, raising questions about why no confirmed signal was received.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1305falsefullhttps://www.spreaker.com/episode/nine-silent-seconds-how-flight-266-vanished-after-takeoff--74906007
Nine Silent Seconds: How Flight 266 Vanished After Takeoff

In this episode, we follow the departure and immediate aftermath of United Air Lines Flight 266 on the night of January 18-19, 1969. The story details the airplane, crew, known mechanical issues, and the nine seconds of cockpit audio that stopped mid-flight-what happened in those minutes?

Date: January 18-19, 1969
Flight: United Air Lines Flight 266
Aircraft: Boeing 727, registration N7434U
Crew hours on type: more than 4,300 combined hours
Known issue: Generator number three inoperative; control panel with history of malfunctions

- The airplane was four months old and had accumulated fewer than 1,100 flight hours when it departed Los Angeles.
- Captain Leonard Leverson, First Officer Walter Schlemmer, and Flight Engineer Keith Ostrander had logged thousands of hours between them, with Ostrander the least experienced.
- Generator number three had been out for days; the control panel with repeated failures had been moved between aircraft and was installed on N7434U a month earlier.
- Technicians applied an approved procedure: a replacement generator was fitted but failed, the faulty control panel repair was deferred, and switches/warning lights were masked with tape before flight.
- The cockpit voice recorder captured only nine seconds of audio-three pilots saying they could not see where the aircraft was going-before the recorders lost power.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906007Mon, 12 Oct 2026 09:00:30 +0000OBOMEDIA ENTERTAINMENTA nearly new Boeing 727 lifts from Los Angeles; two minutes later the cockpit goes dark-did the pilots make it back to instruments in time? Nine Silent Seconds: How Flight 266 Vanished After Takeoff In this episode, we follow the departure and...
Nine Silent Seconds: How Flight 266 Vanished After Takeoff

In this episode, we follow the departure and immediate aftermath of United Air Lines Flight 266 on the night of January 18-19, 1969. The story details the airplane, crew, known mechanical issues, and the nine seconds of cockpit audio that stopped mid-flight-what happened in those minutes?

Date: January 18-19, 1969
Flight: United Air Lines Flight 266
Aircraft: Boeing 727, registration N7434U
Crew hours on type: more than 4,300 combined hours
Known issue: Generator number three inoperative; control panel with history of malfunctions

- The airplane was four months old and had accumulated fewer than 1,100 flight hours when it departed Los Angeles.
- Captain Leonard Leverson, First Officer Walter Schlemmer, and Flight Engineer Keith Ostrander had logged thousands of hours between them, with Ostrander the least experienced.
- Generator number three had been out for days; the control panel with repeated failures had been moved between aircraft and was installed on N7434U a month earlier.
- Technicians applied an approved procedure: a replacement generator was fitted but failed, the faulty control panel repair was deferred, and switches/warning lights were masked with tape before flight.
- The cockpit voice recorder captured only nine seconds of audio-three pilots saying they could not see where the aircraft was going-before the recorders lost power.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1340falsefullhttps://www.spreaker.com/episode/the-snow-dune-that-stopped-the-fuselage-bought-them-twenty-seven-hours--74906005
The snow dune that stopped the fuselage bought them twenty-seven hours

In this episode, we follow the crash of Braathens SAFE Flight 253 and the first twenty-seven hours after impact when survivors waited in a blizzard. What decisions and conditions shaped their odds, and how did one passenger keep others alive amid the wreckage?

Date: 7 November 1956
Aircraft: De Havilland Heron (LN-SUR), Heron 114 Heron Two B
Route: Trondheim (Værnes) to Oslo (Fornebu)
Location: Hummelfjell, Røros highlands, 1,350 meters
Person: Rolf Kirkvaag

- Flight 253 departed Værnes at 08:30 and crossed Tolga beacon at 09:12 before conditions deteriorated.
- Icing accumulated on windshield, control surfaces and antenna until the crew were effectively blind and inaudible.
- Crew elected to turn back toward Trondheim; a sudden downdraft prevented completion of the turn.
- At 09:50 the aircraft struck the mountain at about 300 km/h, fuselage tore open and engines broke away.
- A compacted snow dune stopped the wreck on a slope, leaving ten survivors and one dead captain waiting in a storm 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/74906005Sun, 11 Oct 2026 09:00:25 +0000OBOMEDIA ENTERTAINMENTA De Havilland Heron slams into a Norwegian peak in a blizzard; a single snow dune may have bought the passengers a chance at survival. The snow dune that stopped the fuselage bought them twenty-seven hours In this episode, we follow the crash...
The snow dune that stopped the fuselage bought them twenty-seven hours

In this episode, we follow the crash of Braathens SAFE Flight 253 and the first twenty-seven hours after impact when survivors waited in a blizzard. What decisions and conditions shaped their odds, and how did one passenger keep others alive amid the wreckage?

Date: 7 November 1956
Aircraft: De Havilland Heron (LN-SUR), Heron 114 Heron Two B
Route: Trondheim (Værnes) to Oslo (Fornebu)
Location: Hummelfjell, Røros highlands, 1,350 meters
Person: Rolf Kirkvaag

- Flight 253 departed Værnes at 08:30 and crossed Tolga beacon at 09:12 before conditions deteriorated.
- Icing accumulated on windshield, control surfaces and antenna until the crew were effectively blind and inaudible.
- Crew elected to turn back toward Trondheim; a sudden downdraft prevented completion of the turn.
- At 09:50 the aircraft struck the mountain at about 300 km/h, fuselage tore open and engines broke away.
- A compacted snow dune stopped the wreck on a slope, leaving ten survivors and one dead captain waiting in a storm 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.]]>1127falsefullhttps://www.spreaker.com/episode/eighty-three-minutes-of-delay-forced-a-climb-that-met-medicine-bow-s-summit--74906003
Eighty‑three minutes of delay forced a climb that met Medicine Bow's summit

In this episode, we follow United Air Lines Flight 409 from its delayed departure in Denver through its assigned airway toward Salt Lake City and the moment investigators found only two oil stains on a cliff face. The narrative traces the flight plan, the mounting delay, and the gap between assigned altitude and the mountain it struck - what decisions and pressures led the crew into higher terrain?

Flight: United Air Lines Flight 409
Date: October 6, 1955
Aircraft: Douglas DC‑4 (registration N30062)
Location: Medicine Bow Peak, Wyoming
Passengers and crew: 66 aboard (63 passengers, 3 crew)

- The flight left Stapleton Airport in Denver already eighty‑three minutes behind schedule after earlier delays on the route.
- Assigned altitude was 10,000 feet on Victor airways that should have cleared Medicine Bow Peak by about 2,000 feet.
- Wyoming had no civil radar coverage in 1955; the last expected radio report over Rock River at 08:11 was never received.
- Search pilots first saw two oil stains fifty to seventy‑five feet below the 12,005‑foot summit, each marking where an engine struck granite.
- At impact the DC‑4’s nose was pointed upward and airspeed was unusually low, and wreckage spread down three hundred feet into two ravines.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906003Sat, 10 Oct 2026 09:00:31 +0000OBOMEDIA ENTERTAINMENTEighty‑three minutes late, a DC‑4 climbs toward Medicine Bow Peak - did the delay force a fatal shortcut across higher ground? Eighty‑three minutes of delay forced a climb that met Medicine Bow's summit In this episode, we follow United Air...
Eighty‑three minutes of delay forced a climb that met Medicine Bow's summit

In this episode, we follow United Air Lines Flight 409 from its delayed departure in Denver through its assigned airway toward Salt Lake City and the moment investigators found only two oil stains on a cliff face. The narrative traces the flight plan, the mounting delay, and the gap between assigned altitude and the mountain it struck - what decisions and pressures led the crew into higher terrain?

Flight: United Air Lines Flight 409
Date: October 6, 1955
Aircraft: Douglas DC‑4 (registration N30062)
Location: Medicine Bow Peak, Wyoming
Passengers and crew: 66 aboard (63 passengers, 3 crew)

- The flight left Stapleton Airport in Denver already eighty‑three minutes behind schedule after earlier delays on the route.
- Assigned altitude was 10,000 feet on Victor airways that should have cleared Medicine Bow Peak by about 2,000 feet.
- Wyoming had no civil radar coverage in 1955; the last expected radio report over Rock River at 08:11 was never received.
- Search pilots first saw two oil stains fifty to seventy‑five feet below the 12,005‑foot summit, each marking where an engine struck granite.
- At impact the DC‑4’s nose was pointed upward and airspeed was unusually low, and wreckage spread down three hundred feet into two ravines.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1185falsefullhttps://www.spreaker.com/episode/the-forward-baggage-hold-filled-itself-and-doomed-the-takeoff-time--74906000
The forward baggage hold filled itself and doomed the takeoff time

In this episode, we lay out the sequence of decisions, paperwork and human errors that preceded the crash of UTA Flight 141 without resolving the final outcome. The narrative follows the aircraft’s recent transfers, the cockpit crew’s roles, and the loading of the forward baggage hold to ask how those pieces aligned on that December day.

Aircraft: Boeing 727, first flown 1977, 40,452 cycles
Flight: UTA Flight 141, Conakry-Cotonou-Beirut route
Date: Christmas Day, 2003
Declared weight error: 78 tonnes declared; 7.5 tonnes underreported
Crew: Captain Najib al-Barouni (49), First Officer Ahmad al-Harizi (49), Flight Engineer Miftah (45)

- The aircraft had changed registrations across three continents within a year and carried a fragmented operational record.
- The owner, Imad Saba, leased the jet to carriers, creating a chain of custody investigators called hard to trace.
- The director general of UTA Guinea sat in the cockpit jump seat and earlier argued with the flying first officer about excess baggage.
- A ground handler at Cotonou with no formal training loaded the forward baggage hold until it was full and did not account for its effect on weight distribution.
- Departure paperwork listed a takeoff weight that investigators later found to be about 7.5 tonnes lower than the aircraft actually carried.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74906000Fri, 09 Oct 2026 09:00:27 +0000OBOMEDIA ENTERTAINMENTA forward baggage hold at Cotonou was packed until the last minute and a weight figure was wrong-did they make it in time? The forward baggage hold filled itself and doomed the takeoff time In this episode, we lay out the sequence of decisions,...
The forward baggage hold filled itself and doomed the takeoff time

In this episode, we lay out the sequence of decisions, paperwork and human errors that preceded the crash of UTA Flight 141 without resolving the final outcome. The narrative follows the aircraft’s recent transfers, the cockpit crew’s roles, and the loading of the forward baggage hold to ask how those pieces aligned on that December day.

Aircraft: Boeing 727, first flown 1977, 40,452 cycles
Flight: UTA Flight 141, Conakry-Cotonou-Beirut route
Date: Christmas Day, 2003
Declared weight error: 78 tonnes declared; 7.5 tonnes underreported
Crew: Captain Najib al-Barouni (49), First Officer Ahmad al-Harizi (49), Flight Engineer Miftah (45)

- The aircraft had changed registrations across three continents within a year and carried a fragmented operational record.
- The owner, Imad Saba, leased the jet to carriers, creating a chain of custody investigators called hard to trace.
- The director general of UTA Guinea sat in the cockpit jump seat and earlier argued with the flying first officer about excess baggage.
- A ground handler at Cotonou with no formal training loaded the forward baggage hold until it was full and did not account for its effect on weight distribution.
- Departure paperwork listed a takeoff weight that investigators later found to be about 7.5 tonnes lower than the aircraft actually carried.

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

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

In this episode, we follow the final minutes of Sriwijaya Air Flight 182 and the maintenance and crew history that led up to them. The episode lays out the sequence of events, personnel records, and maintenance entries that preceded the emergency and asks whether the crew could stop what was unfolding.

Person: Captain Afwan, 54, 17,904 total hours, 9,023 on the 737
Person: First Officer Diego Mamahit, 34, 5,107 total hours, 4,957 on the 737
Date: January 9, 2021
Aircraft: Boeing 737-500 registration PK-CLC ("Citra"), 26 years old, 62,983 flight hours
Event: Left thrust lever retracted by autothrottle during level-off at ~11,000 ft

- The aircraft had been grounded nine months during the COVID-19 pandemic and returned to service December 19, 2020.
- An autothrottle fault was logged on January 3 and 4; technicians cleaned connectors, replaced a Mach/airspeed indicator, and on January 5 marked the issue "Fixed."
- Flight 182 pushed back at 14:36, climbed normally, and was leveling off under ATC instruction when the left thrust lever moved without pilot input.
- The flight crew had extensive experience between them-over 23,000 combined hours-with both pilots holding large 737 time totals and recent training records.
- What followed after the autothrottle retraction unfolded in less than sixty seconds while controllers and crew were managing a routine short-haul leg across the Java Sea.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905998Thu, 08 Oct 2026 09:00:36 +0000OBOMEDIA ENTERTAINMENTA routine climb above Jakarta turns critical when the autothrottle retracts the left thrust lever midleveling - did they make it in time? The autothrottle retracted the left thrust lever-did they make it? In this episode, we follow the final...
The autothrottle retracted the left thrust lever-did they make it?

In this episode, we follow the final minutes of Sriwijaya Air Flight 182 and the maintenance and crew history that led up to them. The episode lays out the sequence of events, personnel records, and maintenance entries that preceded the emergency and asks whether the crew could stop what was unfolding.

Person: Captain Afwan, 54, 17,904 total hours, 9,023 on the 737
Person: First Officer Diego Mamahit, 34, 5,107 total hours, 4,957 on the 737
Date: January 9, 2021
Aircraft: Boeing 737-500 registration PK-CLC ("Citra"), 26 years old, 62,983 flight hours
Event: Left thrust lever retracted by autothrottle during level-off at ~11,000 ft

- The aircraft had been grounded nine months during the COVID-19 pandemic and returned to service December 19, 2020.
- An autothrottle fault was logged on January 3 and 4; technicians cleaned connectors, replaced a Mach/airspeed indicator, and on January 5 marked the issue "Fixed."
- Flight 182 pushed back at 14:36, climbed normally, and was leveling off under ATC instruction when the left thrust lever moved without pilot input.
- The flight crew had extensive experience between them-over 23,000 combined hours-with both pilots holding large 737 time totals and recent training records.
- What followed after the autothrottle retraction unfolded in less than sixty seconds while controllers and crew were managing a routine short-haul leg across the Java Sea.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1159falsefullhttps://www.spreaker.com/episode/the-circuit-breaker-that-tripped-on-the-floor-stalled-the-landing-gear-clock--74905996
The circuit breaker that tripped on the floor stalled the landing gear clock

In this episode, the story follows LOT Polish Airlines Flight 16 from Newark to Warsaw when a center-hydraulic failure leaves the main landing gear without primary power. We trace the crew’s decisions, the hidden breaker on the cockpit floor, and the race against time that investigators later tried to reconstruct. What choices and oversights set the clock ticking toward a belly landing?

Date: 1 November 2011
Aircraft: Boeing 767, registration SP-LPC
People: Captain Tadeusz Wrona; First Officer Jerzy Szwarc
Passengers and crew: 231 aboard (220 passengers, 11 crew)
Flight phase: Transatlantic cruise then approach to Warsaw Chopin Airport

- A flexible hose in the center hydraulic system was excessively bent during gear retraction shortly after takeoff, causing a slow fluid leak.
- The crew received ECAM indications and logged the anomaly, then made a deliberate decision to continue to Warsaw where maintenance was based.
- Over eight hours of flight the center hydraulic lines feeding the primary landing gear drained, leaving the gear without its main deployment system.
- During approach the crew announced the landing gear would not extend, triggering airport-wide emergency preparations and a series of procedural attempts.
- A small circuit breaker labeled C829 sat low on the first officer’s side, tripped and invisible during the emergency, and it locked out the sole backup system capable of lowering the gear.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905996Wed, 07 Oct 2026 09:00:30 +0000OBOMEDIA ENTERTAINMENTA finger-sized circuit breaker sits tripped on the cockpit floor as LOT Flight 16 approaches Warsaw-did they make it in time? The circuit breaker that tripped on the floor stalled the landing gear clock In this episode, the story follows LOT...
The circuit breaker that tripped on the floor stalled the landing gear clock

In this episode, the story follows LOT Polish Airlines Flight 16 from Newark to Warsaw when a center-hydraulic failure leaves the main landing gear without primary power. We trace the crew’s decisions, the hidden breaker on the cockpit floor, and the race against time that investigators later tried to reconstruct. What choices and oversights set the clock ticking toward a belly landing?

Date: 1 November 2011
Aircraft: Boeing 767, registration SP-LPC
People: Captain Tadeusz Wrona; First Officer Jerzy Szwarc
Passengers and crew: 231 aboard (220 passengers, 11 crew)
Flight phase: Transatlantic cruise then approach to Warsaw Chopin Airport

- A flexible hose in the center hydraulic system was excessively bent during gear retraction shortly after takeoff, causing a slow fluid leak.
- The crew received ECAM indications and logged the anomaly, then made a deliberate decision to continue to Warsaw where maintenance was based.
- Over eight hours of flight the center hydraulic lines feeding the primary landing gear drained, leaving the gear without its main deployment system.
- During approach the crew announced the landing gear would not extend, triggering airport-wide emergency preparations and a series of procedural attempts.
- A small circuit breaker labeled C829 sat low on the first officer’s side, tripped and invisible during the emergency, and it locked out the sole backup system capable of lowering the gear.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1213falsefullhttps://www.spreaker.com/episode/the-late-flare-that-ate-the-runway-seconds-before-touchdown--74905995
The late flare that ate the runway seconds before touchdown

In this episode, we follow the last minutes of a cargo flight into Narita where two experienced pilots, both short on sleep, manage an unstable final approach amid gusty winds and a wind shear advisory. The episode covers cockpit audio, crew roles, aircraft history, and the chain of events that turned a routine overnight run into an urgent investigative puzzle-did they make it in time?

Person: Kevin Kyle Kyle
Person: Anthony Stephen Pino
Date: March 23, 2009
Location: Narita International International, Runway 34L
Aircraft: McDonnell Douglas MD-11F N526FE

- Both pilots had military backgrounds and thousands of flight hours, but neither had more than four consecutive hours of sleep before departure.
- Pino, the relief pilot who usually rests on long-haul legs, was the pilot flying during the approach.
- The flight originated in Guangzhou at 02:02 CST and was expected at Narita at 06:53 JST after a routine overnight cargo run.
- Weather at Narita included winds 320° at 26 knots gusting to 40, and a preceding 747 reported +/-15 kt shear below 2,000 ft.
- At 06:43:57 JST air traffic control issued a wind shear advisory; the cockpit remained calm while the aircraft descended with a high rate of descent and an autothrottle compensating for gusts.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905995Tue, 06 Oct 2026 09:00:27 +0000OBOMEDIA ENTERTAINMENTA fatigued flight crew approaches Narita in gusting wind and wind shear on final-will a late flare on an MD-11 be caught before touchdown? The late flare that ate the runway seconds before touchdown In this episode, we follow the last minutes of...
The late flare that ate the runway seconds before touchdown

In this episode, we follow the last minutes of a cargo flight into Narita where two experienced pilots, both short on sleep, manage an unstable final approach amid gusty winds and a wind shear advisory. The episode covers cockpit audio, crew roles, aircraft history, and the chain of events that turned a routine overnight run into an urgent investigative puzzle-did they make it in time?

Person: Kevin Kyle Kyle
Person: Anthony Stephen Pino
Date: March 23, 2009
Location: Narita International International, Runway 34L
Aircraft: McDonnell Douglas MD-11F N526FE

- Both pilots had military backgrounds and thousands of flight hours, but neither had more than four consecutive hours of sleep before departure.
- Pino, the relief pilot who usually rests on long-haul legs, was the pilot flying during the approach.
- The flight originated in Guangzhou at 02:02 CST and was expected at Narita at 06:53 JST after a routine overnight cargo run.
- Weather at Narita included winds 320° at 26 knots gusting to 40, and a preceding 747 reported +/-15 kt shear below 2,000 ft.
- At 06:43:57 JST air traffic control issued a wind shear advisory; the cockpit remained calm while the aircraft descended with a high rate of descent and an autothrottle compensating for gusts.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1300falsefullhttps://www.spreaker.com/episode/eight-minutes-that-killed-the-survivors-strapped-inside-aviogenex-130--74905994
Eight Minutes That Killed: The Survivors Strapped Inside Aviogenex 130

In this episode, we follow Aviogenex Flight 130 from Gatwick to Rijeka and trace the decisions, weather and cockpit dynamics that set the scene for the eight minutes after touchdown. What happened in that window that turned a survivable accident into a catastrophic post-crash failure?

Date: May 23, 1971
Flight: Aviogenex Flight 130 / Tupolev Tu-134A YU-AHZ
Location: Rijeka Airport, Yugoslavia
Passengers: 76 passengers (72 British passports, 4 Yugoslav)
Crew: Captain Miloš Markićević; Copilot Stevan Mandić; Flight engineer Ivan Čavajda; trainee Viktor Tomić; three flight attendants

- The Tu-134A YU-AHZ had only 111 flight hours and was delivered 30 days before the accident.
- Captain Markićević had 9,230 total hours but only 138 hours on the Tu-134A; copilot Mandić had 899 hours on type.
- During the second approach heavy cumulonimbus and torrential rain turned the windscreen into a mirror, obscuring the runway.
- At 3.2 km out a turbulence spike rolled the aircraft right; correction brought the jet below glideslope and speed was slightly high.
- Thirty percent of passengers were found still buckled and upside down after the fuselage inverted during the slide down the runway.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905994Mon, 05 Oct 2026 09:00:28 +0000OBOMEDIA ENTERTAINMENTA passenger jet lands hard at Rijeka in torrential rain - but in eight minutes something else collapses. Did they make it in time? Eight Minutes That Killed: The Survivors Strapped Inside Aviogenex 130 In this episode, we follow Aviogenex Flight...
Eight Minutes That Killed: The Survivors Strapped Inside Aviogenex 130

In this episode, we follow Aviogenex Flight 130 from Gatwick to Rijeka and trace the decisions, weather and cockpit dynamics that set the scene for the eight minutes after touchdown. What happened in that window that turned a survivable accident into a catastrophic post-crash failure?

Date: May 23, 1971
Flight: Aviogenex Flight 130 / Tupolev Tu-134A YU-AHZ
Location: Rijeka Airport, Yugoslavia
Passengers: 76 passengers (72 British passports, 4 Yugoslav)
Crew: Captain Miloš Markićević; Copilot Stevan Mandić; Flight engineer Ivan Čavajda; trainee Viktor Tomić; three flight attendants

- The Tu-134A YU-AHZ had only 111 flight hours and was delivered 30 days before the accident.
- Captain Markićević had 9,230 total hours but only 138 hours on the Tu-134A; copilot Mandić had 899 hours on type.
- During the second approach heavy cumulonimbus and torrential rain turned the windscreen into a mirror, obscuring the runway.
- At 3.2 km out a turbulence spike rolled the aircraft right; correction brought the jet below glideslope and speed was slightly high.
- Thirty percent of passengers were found still buckled and upside down after the fuselage inverted during the slide down the runway.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1326falsefullhttps://www.spreaker.com/episode/a-twelve-second-blind-spot-erased-the-warning-and-nearly-killed-140--74905993
A twelve‑second blind spot erased the warning and nearly killed 140

In this episode, we follow the final minute of Air Canada Flight 759’s approach into San Francisco on July 7, 2017, when the crew aligned with taxiway lights instead of the intended runway. The episode covers the pilots’ fatigue, the closed runway’s darkened lights, and the seconds of unfolding confusion that put four queued jets directly below them - but what happened in those critical twelve seconds?

Aircraft: Airbus A320-200 C-FKCK
Date: July 7, 2017
Location: San Francisco International Airport
Passengers and crew: 135 passengers, 5 crew
Nearby aircraft: Four commercial jets on Taxiway Charlie with engines running

- The crew believed they were lined up on Runway 28R during final approach under night visual conditions.
- Runway 28L had been closed; its edge lights were extinguished and marked by a single flashing X at the eastern threshold.
- The captain had been awake ~19 hours and was near his circadian low; the first officer had roughly 12 hours awake.
- At 23:55:46 the captain asked “Clear to land 28R?” while the aircraft was approximately 0.7 miles from the threshold they were actually approaching.
- For a twelve‑second window the safety system monitoring Flight 759 went blind while four fully fueled jets waited on Taxiway Charlie less than 500 feet south.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905993Sun, 04 Oct 2026 09:00:38 +0000OBOMEDIA ENTERTAINMENTAn Air Canada A320 descends into San Francisco at night and a twelve‑second blind spot erases its warning - did they make it in time? A twelve‑second blind spot erased the warning and nearly killed 140 In this episode, we follow the final minute...
A twelve‑second blind spot erased the warning and nearly killed 140

In this episode, we follow the final minute of Air Canada Flight 759’s approach into San Francisco on July 7, 2017, when the crew aligned with taxiway lights instead of the intended runway. The episode covers the pilots’ fatigue, the closed runway’s darkened lights, and the seconds of unfolding confusion that put four queued jets directly below them - but what happened in those critical twelve seconds?

Aircraft: Airbus A320-200 C-FKCK
Date: July 7, 2017
Location: San Francisco International Airport
Passengers and crew: 135 passengers, 5 crew
Nearby aircraft: Four commercial jets on Taxiway Charlie with engines running

- The crew believed they were lined up on Runway 28R during final approach under night visual conditions.
- Runway 28L had been closed; its edge lights were extinguished and marked by a single flashing X at the eastern threshold.
- The captain had been awake ~19 hours and was near his circadian low; the first officer had roughly 12 hours awake.
- At 23:55:46 the captain asked “Clear to land 28R?” while the aircraft was approximately 0.7 miles from the threshold they were actually approaching.
- For a twelve‑second window the safety system monitoring Flight 759 went blind while four fully fueled jets waited on Taxiway Charlie less than 500 feet south.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1414falsefullhttps://www.spreaker.com/episode/the-shoebox-sized-component-stalled-the-engines-and-cost-twenty-three-lives--74905991
The shoebox-sized component stalled the engines and cost twenty-three lives

In this episode, we tell the story of Atlantic Southeast Airlines Flight 2311 and the mechanical failure that brought it down on April 5, 1991. The episode follows the flight, the passengers on board, and the investigative trail that traced the catastrophe to a single failed component - but what questions about those last seconds remain?

Event: Atlantic Southeast Airlines Flight 2311
Date: April 5, 1991
Location: Approach to Brunswick, Georgia
Fatalities: Twenty-three
Notable passenger: John Goodwin Tower

- The failure began with a component no larger than a shoebox that stalled the aircraft's engines during final approach.
- Among the dead were a former United States senator, his thirty-five-year-old daughter, and an astronaut who had orbited the Earth.
- Investigators documented the mechanical failure and eventually identified the exact part that failed.
- John Tower had a long political career: elected to the Senate in 1961, chaired the Armed Services Committee from 1981-1984, and served as chief negotiator at START talks after leaving the Senate.
- The episode traces Tower’s life from his 1925 birth in Houston through military service, academia, and decades in public office up to the flight that ended his story.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905991Sat, 03 Oct 2026 09:00:35 +0000OBOMEDIA ENTERTAINMENTA shoebox-sized component stalls the engines of Atlantic Southeast Airlines Flight 2311 as it approaches Brunswick - did they make it in time? The shoebox-sized component stalled the engines and cost twenty-three lives In this episode, we tell...
The shoebox-sized component stalled the engines and cost twenty-three lives

In this episode, we tell the story of Atlantic Southeast Airlines Flight 2311 and the mechanical failure that brought it down on April 5, 1991. The episode follows the flight, the passengers on board, and the investigative trail that traced the catastrophe to a single failed component - but what questions about those last seconds remain?

Event: Atlantic Southeast Airlines Flight 2311
Date: April 5, 1991
Location: Approach to Brunswick, Georgia
Fatalities: Twenty-three
Notable passenger: John Goodwin Tower

- The failure began with a component no larger than a shoebox that stalled the aircraft's engines during final approach.
- Among the dead were a former United States senator, his thirty-five-year-old daughter, and an astronaut who had orbited the Earth.
- Investigators documented the mechanical failure and eventually identified the exact part that failed.
- John Tower had a long political career: elected to the Senate in 1961, chaired the Armed Services Committee from 1981-1984, and served as chief negotiator at START talks after leaving the Senate.
- The episode traces Tower’s life from his 1925 birth in Houston through military service, academia, and decades in public office up to the flight that ended his story.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1158falsefullhttps://www.spreaker.com/episode/the-rv-s-only-door-jammed-shut-did-anyone-reach-him-in-time--74905989
The RV's only door jammed shut - did anyone reach him in time?

In this episode, we follow the moments around December 6, 2024 when a Vans RV-12IS came to rest inverted on a road in Homosassa, Florida, with the president and general manager of Tyler Perry Studios inside. The story traces his role running a 330‑acre studio compound in Atlanta and the unanswered questions about why he was three hundred miles away in a Gulf Coast town. What was he doing there, and who found him first?

Person: Steve Mensch
Date: December 6, 2024
Location: Homosassa, Florida
Event: Vans RV‑12IS inverted on road
Position: President and general manager of Tyler Perry Studios

- The vehicle was a Vans RV‑12IS found inverted with wheels pointed at the sky on a Homosassa road.
- The person inside was Steve Mensch, who ran daily operations at Tyler Perry Studios in southwest Atlanta.
- Tyler Perry Studios occupied 330 acres of the former Fort McPherson and included twelve soundstages and permanent sets.
- Months earlier the studio paused an $800 million expansion, citing advances in artificial intelligence, while a Netflix first‑look deal was active.
- Homosassa is a Gulf Coast town about ninety miles north of Tampa with no known connection to the Atlanta studio.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905989Fri, 02 Oct 2026 09:00:38 +0000OBOMEDIA ENTERTAINMENTA Vans RV lies inverted on a Homosassa road with its only door jammed; the studio manager is inside - did anyone reach him in time? The RV's only door jammed shut - did anyone reach him in time? In this episode, we follow the moments around...
The RV's only door jammed shut - did anyone reach him in time?

In this episode, we follow the moments around December 6, 2024 when a Vans RV-12IS came to rest inverted on a road in Homosassa, Florida, with the president and general manager of Tyler Perry Studios inside. The story traces his role running a 330‑acre studio compound in Atlanta and the unanswered questions about why he was three hundred miles away in a Gulf Coast town. What was he doing there, and who found him first?

Person: Steve Mensch
Date: December 6, 2024
Location: Homosassa, Florida
Event: Vans RV‑12IS inverted on road
Position: President and general manager of Tyler Perry Studios

- The vehicle was a Vans RV‑12IS found inverted with wheels pointed at the sky on a Homosassa road.
- The person inside was Steve Mensch, who ran daily operations at Tyler Perry Studios in southwest Atlanta.
- Tyler Perry Studios occupied 330 acres of the former Fort McPherson and included twelve soundstages and permanent sets.
- Months earlier the studio paused an $800 million expansion, citing advances in artificial intelligence, while a Netflix first‑look deal was active.
- Homosassa is a Gulf Coast town about ninety miles north of Tampa with no known connection to the Atlanta studio.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1073falsefullhttps://www.spreaker.com/episode/the-stick-shaker-jolted-at-fourteen-feet-did-they-stop-the-fire--74905988
The stick shaker jolted at fourteen feet - did they stop the fire?

In this episode, we follow the moments on board TWA Flight 843 as a seasoned crew confronts a sudden instrument failure seconds after takeoff and the maintenance trail behind it. What decisions did the pilots and maintenance system make in those first frantic minutes, and could the hidden fault have been caught sooner?

Person: Captain William Shelby Kinkead
Person: First Officer Dennis William Hergert
Person: Flight Engineer Charles Edward Long
Event: Stick shaker activation at 14 feet after takeoff
Date: July 30, 1992

- Takeoff began from Runway 13R at John F. Kennedy International Airport with 280 people on board.
- The aircraft, a Lockheed L-1011 first flown in 1972, had nearly 49,662 flight hours and 19,659 cycles.
- A single small sensor, previously documented as faulty nine separate times, was in the parts pool and returned to service.
- The stick shaker activated eight seconds after liftoff, warning of an impending aerodynamic stall while the jet was climbing.
- Two prior L-1011 engine fires occurred within two years, including one at JFK three months earlier.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905988Thu, 01 Oct 2026 09:00:36 +0000OBOMEDIA ENTERTAINMENTA stick shaker jolts at fourteen feet during takeoff from JFK, a sensor with nine prior faults triggers an emergency - did they stop the fire? The stick shaker jolted at fourteen feet - did they stop the fire? In this episode, we follow the...
The stick shaker jolted at fourteen feet - did they stop the fire?

In this episode, we follow the moments on board TWA Flight 843 as a seasoned crew confronts a sudden instrument failure seconds after takeoff and the maintenance trail behind it. What decisions did the pilots and maintenance system make in those first frantic minutes, and could the hidden fault have been caught sooner?

Person: Captain William Shelby Kinkead
Person: First Officer Dennis William Hergert
Person: Flight Engineer Charles Edward Long
Event: Stick shaker activation at 14 feet after takeoff
Date: July 30, 1992

- Takeoff began from Runway 13R at John F. Kennedy International Airport with 280 people on board.
- The aircraft, a Lockheed L-1011 first flown in 1972, had nearly 49,662 flight hours and 19,659 cycles.
- A single small sensor, previously documented as faulty nine separate times, was in the parts pool and returned to service.
- The stick shaker activated eight seconds after liftoff, warning of an impending aerodynamic stall while the jet was climbing.
- Two prior L-1011 engine fires occurred within two years, including one at JFK three months earlier.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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-flight-strip-that-never-moved-cost-thirty-five-people-their-lives--74905987
The flight strip that never moved cost thirty‑five people their lives

In this episode, we follow the sequence of decisions, equipment failures, and human oversights on the evening of February 1, 1991 that set two aircraft on a collision course at Los Angeles International Airport. The narrative traces the roles of controllers, the missing flight strip, and the degraded ground radar; could routine gaps have doomed everyone involved?

Date: February 1, 1991
Location: Los Angeles International Airport
Event: Runway collision between USAir Flight 1493 and SkyWest Flight 5569
Person: Robin Lee Wascher
Person: Captain Colin Franklin Shaw

- A flight progress strip that should have moved from clearance delivery to local control never arrived, leaving the tower without its paper backup.
- Local control at LAX required continuous attention; controller Robin Lee Wascher had prior performance records noting loss of situational awareness and aircraft misidentification.
- Ground radar at LAX had been intermittent and unreliable, creating reliance on physical strips and visual observation at dusk with glare.
- SkyWest Metroliner was cleared to hold on Runway 24L at a taxiway intersection and remained there awaiting release that never came.
- USAir Flight 1493, on approach and touching down on Runway 24L, was flown by experienced pilots who were unaware the runway was occupied.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905987Wed, 30 Sep 2026 09:01:07 +0000OBOMEDIA ENTERTAINMENTA missing flight progress strip leaves an LAX controller blind as a 737 nears a runway occupied by a commuter plane-did they make it in time? The flight strip that never moved cost thirty‑five people their lives In this episode, we follow the...
The flight strip that never moved cost thirty‑five people their lives

In this episode, we follow the sequence of decisions, equipment failures, and human oversights on the evening of February 1, 1991 that set two aircraft on a collision course at Los Angeles International Airport. The narrative traces the roles of controllers, the missing flight strip, and the degraded ground radar; could routine gaps have doomed everyone involved?

Date: February 1, 1991
Location: Los Angeles International Airport
Event: Runway collision between USAir Flight 1493 and SkyWest Flight 5569
Person: Robin Lee Wascher
Person: Captain Colin Franklin Shaw

- A flight progress strip that should have moved from clearance delivery to local control never arrived, leaving the tower without its paper backup.
- Local control at LAX required continuous attention; controller Robin Lee Wascher had prior performance records noting loss of situational awareness and aircraft misidentification.
- Ground radar at LAX had been intermittent and unreliable, creating reliance on physical strips and visual observation at dusk with glare.
- SkyWest Metroliner was cleared to hold on Runway 24L at a taxiway intersection and remained there awaiting release that never came.
- USAir Flight 1493, on approach and touching down on Runway 24L, was flown by experienced pilots who were unaware the runway was occupied.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1397falsefullhttps://www.spreaker.com/episode/the-cabin-lights-burned-for-hours-and-kept-twenty-two-people-alive--74905986
The cabin lights burned for hours and kept twenty-two people alive

In this episode, we follow Rocky Mountain Airways Flight 217 from its delayed evening departure in a blizzard to the moment the aircraft stops climbing over the Park Range. The episode traces the crew’s decisions, the missing weather details in the briefing, and the search that began miles from the wreck - could those cabin lights be the difference between life and death?

Person: Captain Scott Alan Klopfenstein
Person: First Officer Gary Coleman
Date: December 4, 1982
Aircraft: de Havilland Canada DHC-6 Twin Otter (N25RM)
Event: Mountain wave encounter, in-flight loss of climb and impact

- The flight departed Steamboat Springs at 18:55 after a two-hour delay that followed earlier aborted and iced flights that day.
- Pre-flight inspection found no mechanical defects; the Twin Otter had 15,145 hours and two reliable Pratt & Whitney engines.
- The crew filed an IFR climb to 17,000 ft then visual to Gill VOR; the aircraft stalled at about 13,000 ft and could not climb further.
- The NTSB identified a mountain wave producing downdrafts over 500 ft/min as the external force preventing climb.
- The emergency locator signal placed the wreckage 12 miles from the actual site, sending search teams into a Rocky Mountain blizzard in the wrong area.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905986Tue, 29 Sep 2026 09:00:57 +0000OBOMEDIA ENTERTAINMENTA Twin Otter stalls in a mountain wave above the Park Range with a cracked fuselage - did rescuers find the 22 survivors in time? The cabin lights burned for hours and kept twenty-two people alive In this episode, we follow Rocky Mountain...
The cabin lights burned for hours and kept twenty-two people alive

In this episode, we follow Rocky Mountain Airways Flight 217 from its delayed evening departure in a blizzard to the moment the aircraft stops climbing over the Park Range. The episode traces the crew’s decisions, the missing weather details in the briefing, and the search that began miles from the wreck - could those cabin lights be the difference between life and death?

Person: Captain Scott Alan Klopfenstein
Person: First Officer Gary Coleman
Date: December 4, 1982
Aircraft: de Havilland Canada DHC-6 Twin Otter (N25RM)
Event: Mountain wave encounter, in-flight loss of climb and impact

- The flight departed Steamboat Springs at 18:55 after a two-hour delay that followed earlier aborted and iced flights that day.
- Pre-flight inspection found no mechanical defects; the Twin Otter had 15,145 hours and two reliable Pratt & Whitney engines.
- The crew filed an IFR climb to 17,000 ft then visual to Gill VOR; the aircraft stalled at about 13,000 ft and could not climb further.
- The NTSB identified a mountain wave producing downdrafts over 500 ft/min as the external force preventing climb.
- The emergency locator signal placed the wreckage 12 miles from the actual site, sending search teams into a Rocky Mountain blizzard in the wrong area.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1353falsefullhttps://www.spreaker.com/episode/the-elevator-cable-turnbuckle-limited-pitch-could-they-lift-in-time--74905985
The elevator cable turnbuckle limited pitch - could they lift in time?

In this episode, we follow Air Midwest Flight 5481’s ordinary morning flight that lasted only thirty-five seconds and the chain of small errors that left two pilots fighting for control. Listen to how weight calculations from 1936 and a misadjusted elevator turnbuckle set up a race against time and altitude. What choices and checks mattered in those seconds?

Flight: Air Midwest Flight 5481
Date: January 8, 2003
Aircraft: Beechcraft 1900D, N233YV
People: Captain Catherine “Katie” Leslie; First Officer Jonathan Gibbs
Weight: 580 pounds over maximum takeoff weight

- Two nights before the flight, a Vertex Aerospace technician adjusted the elevator control cables on N233YV and had never worked on a Beechcraft 1900D before.
- The turnbuckles were set incorrectly, restricting elevator range of motion and limiting the aircraft’s pitch authority.
- Air Midwest used weight-estimation tables last updated in 1936; crew calculations used those dated inputs and were arithmetically correct.
- Nineteen passengers and two crew boarded; twenty-three bags were loaded, with two bags later described as unusually heavy.
- The aircraft had accumulated 15,003 flight hours and had flown earlier that morning; during the thirty-five-second climb the pilots pushed controls fully but the airplane did not respond.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905985Mon, 28 Sep 2026 09:00:47 +0000OBOMEDIA ENTERTAINMENTA commuter turboprop lifts overweight and with limited elevator travel-can the crew gain pitch control and climb before thirty-five seconds run out? The elevator cable turnbuckle limited pitch - could they lift in time? In this episode, we...
The elevator cable turnbuckle limited pitch - could they lift in time?

In this episode, we follow Air Midwest Flight 5481’s ordinary morning flight that lasted only thirty-five seconds and the chain of small errors that left two pilots fighting for control. Listen to how weight calculations from 1936 and a misadjusted elevator turnbuckle set up a race against time and altitude. What choices and checks mattered in those seconds?

Flight: Air Midwest Flight 5481
Date: January 8, 2003
Aircraft: Beechcraft 1900D, N233YV
People: Captain Catherine “Katie” Leslie; First Officer Jonathan Gibbs
Weight: 580 pounds over maximum takeoff weight

- Two nights before the flight, a Vertex Aerospace technician adjusted the elevator control cables on N233YV and had never worked on a Beechcraft 1900D before.
- The turnbuckles were set incorrectly, restricting elevator range of motion and limiting the aircraft’s pitch authority.
- Air Midwest used weight-estimation tables last updated in 1936; crew calculations used those dated inputs and were arithmetically correct.
- Nineteen passengers and two crew boarded; twenty-three bags were loaded, with two bags later described as unusually heavy.
- The aircraft had accumulated 15,003 flight hours and had flown earlier that morning; during the thirty-five-second climb the pilots pushed controls fully but the airplane did not respond.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1191falsefullhttps://www.spreaker.com/episode/the-jammed-dc-9-exit-refused-to-open-two-passengers-lost-five-seconds--74905984
The jammed DC‑9 exit refused to open - two passengers lost five seconds

In this episode, we follow the moments before and after a high‑speed collision on December 3, 1990, focusing on the failed emergency exit, crew actions in low visibility, and the chain of system failures that followed. How did a mechanical fault on a revenue flight survive inspection and contribute to lives lost?

Event: Collision between Northwest Airlines Flight 1482 (DC‑9) and Northwest Flight 299 (Boeing 727)
Date: December 3, 1990
Location: Detroit Metro Wayne County Airport
Aircraft: McDonnell Douglas DC‑9 N3313L; Boeing 727 N278US
Crew: Captain William Lovelace (DC‑9), First Officer James Schifferns; Captain Robert Ouellette, First Officer William Hagedorn, Flight Engineer Darren Owen (727)

- Dense fog reduced visibility to a quarter mile or less and forced taxiing by instruments and radio at Detroit Metro.
- The DC‑9 (N3313L), built in 1966 and acquired by Northwest in 1986, had accumulated 62,253 flight hours across multiple carriers.
- Investigators found airport signage, markings, and lighting at Detroit Metro did not meet standards and hindered safe ground navigation.
- The DC‑9 flight crew exhibited a "virtual reversal of crew roles," with command assertiveness and cross‑checking degraded during taxi.
- In the burning DC‑9, two people reached an emergency exit that failed to open due to a preexisting mechanical fault on an aircraft already owned by the airline.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905984Sun, 27 Sep 2026 09:01:29 +0000OBOMEDIA ENTERTAINMENTA jammed DC‑9 exit won’t open as fog blankets Detroit Metro and a 727 accelerates for takeoff - did they make it in time? The jammed DC‑9 exit refused to open - two passengers lost five seconds In this episode, we follow the moments before and...
The jammed DC‑9 exit refused to open - two passengers lost five seconds

In this episode, we follow the moments before and after a high‑speed collision on December 3, 1990, focusing on the failed emergency exit, crew actions in low visibility, and the chain of system failures that followed. How did a mechanical fault on a revenue flight survive inspection and contribute to lives lost?

Event: Collision between Northwest Airlines Flight 1482 (DC‑9) and Northwest Flight 299 (Boeing 727)
Date: December 3, 1990
Location: Detroit Metro Wayne County Airport
Aircraft: McDonnell Douglas DC‑9 N3313L; Boeing 727 N278US
Crew: Captain William Lovelace (DC‑9), First Officer James Schifferns; Captain Robert Ouellette, First Officer William Hagedorn, Flight Engineer Darren Owen (727)

- Dense fog reduced visibility to a quarter mile or less and forced taxiing by instruments and radio at Detroit Metro.
- The DC‑9 (N3313L), built in 1966 and acquired by Northwest in 1986, had accumulated 62,253 flight hours across multiple carriers.
- Investigators found airport signage, markings, and lighting at Detroit Metro did not meet standards and hindered safe ground navigation.
- The DC‑9 flight crew exhibited a "virtual reversal of crew roles," with command assertiveness and cross‑checking degraded during taxi.
- In the burning DC‑9, two people reached an emergency exit that failed to open due to a preexisting mechanical fault on an aircraft already owned by the airline.

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

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

In this episode, we follow the final minutes of Indian Airlines Flight 557 as investigators piece together conflicting position reports, cockpit audio, and flight tracking to understand what happened during the descent toward Imphal. What decisions and assumptions in the cockpit and on the ground set the stage for the crisis?

Event: Indian Airlines Flight 557
Date: 14 October 1988
Location: Imphal approach, Manipur, India
Aircraft: Airbus A300B2
People aboard: 69

- Captain Bhupinder Singh Sodhi had flown the Calcutta-Imphal route at least thirty-six times and spoke confidently about the terrain during descent.
- The crew reported passing Agartala to air traffic control while the Agartala VOR showed no crossing.
- Cockpit voice recorder timestamps differ from the captain’s claim by twenty-five seconds during the critical final minutes.
- Flight track shifted to heading 053, a direct shortcut that bypassed the filed Agartala waypoint and was not cleared or reported.
- The first officer was largely silent on the CVR during the approach, providing little challenge to the captain’s position calls.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905983Sat, 26 Sep 2026 09:01:34 +0000OBOMEDIA ENTERTAINMENTA seasoned captain reports passing Agartala while the cockpit voice recorder shows they were still minutes away-did they make it in time? The crew reported Agartala early - did they make it in time? In this episode, we follow the final minutes...
The crew reported Agartala early - did they make it in time?

In this episode, we follow the final minutes of Indian Airlines Flight 557 as investigators piece together conflicting position reports, cockpit audio, and flight tracking to understand what happened during the descent toward Imphal. What decisions and assumptions in the cockpit and on the ground set the stage for the crisis?

Event: Indian Airlines Flight 557
Date: 14 October 1988
Location: Imphal approach, Manipur, India
Aircraft: Airbus A300B2
People aboard: 69

- Captain Bhupinder Singh Sodhi had flown the Calcutta-Imphal route at least thirty-six times and spoke confidently about the terrain during descent.
- The crew reported passing Agartala to air traffic control while the Agartala VOR showed no crossing.
- Cockpit voice recorder timestamps differ from the captain’s claim by twenty-five seconds during the critical final minutes.
- Flight track shifted to heading 053, a direct shortcut that bypassed the filed Agartala waypoint and was not cleared or reported.
- The first officer was largely silent on the CVR during the approach, providing little challenge to the captain’s position calls.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1115falsefullhttps://www.spreaker.com/episode/one-wrong-prop-how-a-8-blade-sent-mainliner-idaho-plummeting--74905981
One Wrong Prop: How a -8° Blade Sent Mainliner Idaho Plummeting

In this episode we follow the final half‑minute of United Air Lines Mainliner Idaho’s April 4, 1955 takeoff, and the technical trail investigators uncovered. What sequence of mechanical settings and safety logic left an experienced crew unaware of the danger they faced?

Date: April 4, 1955
Aircraft: Douglas DC‑6 (N37512) Mainliner Idaho
Location: Long Island MacArthur Airport, Ronkonkoma
Flight type: Recurrent instrument training flight
Engines/Propellers: Four Pratt & Whitney R‑2800 engines with Hamilton Standard propellers

- Three experienced pilots aboard: check captain Stanley C. Hoyt plus Henry M. Dozier and Vernis H. Webb on a routine recurrent training flight.
- Takeoff sequence lasted less than thirty seconds from lift‑off at 150 feet to impact on a clear, gusty afternoon.
- Wreckage propeller measurements: three blades at +34° pitch, the outboard right engine blade at -8° pitch.
- DC‑6 thrust reversal safety used a landing‑gear‑activated switch and a cockpit red flag to allow reverse only when weight was on wheels.
- The reversal‑prevention device that might have stopped the event arrived at the hangar one week too late.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905981Fri, 25 Sep 2026 09:00:53 +0000OBOMEDIA ENTERTAINMENTA DC‑6 taking off from Long Island rolls and dives after one prop blade reads -8°-did the pilots have any warning before the wing went down? One Wrong Prop: How a -8° Blade Sent Mainliner Idaho Plummeting In this episode we follow the final...
One Wrong Prop: How a -8° Blade Sent Mainliner Idaho Plummeting

In this episode we follow the final half‑minute of United Air Lines Mainliner Idaho’s April 4, 1955 takeoff, and the technical trail investigators uncovered. What sequence of mechanical settings and safety logic left an experienced crew unaware of the danger they faced?

Date: April 4, 1955
Aircraft: Douglas DC‑6 (N37512) Mainliner Idaho
Location: Long Island MacArthur Airport, Ronkonkoma
Flight type: Recurrent instrument training flight
Engines/Propellers: Four Pratt & Whitney R‑2800 engines with Hamilton Standard propellers

- Three experienced pilots aboard: check captain Stanley C. Hoyt plus Henry M. Dozier and Vernis H. Webb on a routine recurrent training flight.
- Takeoff sequence lasted less than thirty seconds from lift‑off at 150 feet to impact on a clear, gusty afternoon.
- Wreckage propeller measurements: three blades at +34° pitch, the outboard right engine blade at -8° pitch.
- DC‑6 thrust reversal safety used a landing‑gear‑activated switch and a cockpit red flag to allow reverse only when weight was on wheels.
- The reversal‑prevention device that might have stopped the event arrived at the hangar one week too late.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1151falsefullhttps://www.spreaker.com/episode/the-autopilot-switched-to-control-wheel-steering-did-they-disable-it-in-time--74905980
The autopilot switched to control-wheel steering - did they disable it in time?

In this episode, we follow the first three minutes after Flash Airlines Flight 604 departed Sharm El Sheikh and the rapid cockpit actions that followed. The episode covers the crew makeup, the autopilot's unexpected mode change, and the sequence of manual inputs that preceded the aircraft's sharp right roll - what happened in those compressed seconds?

Date: January 3, 2004
Aircraft: Boeing 737-300 (737 Classic, -300 series, -3Q8)
Location: Red Sea, after departure from Sharm El Sheikh (Charles de Gaulle-bound charter)
Passengers: 148 people aboard
Crew: Captain Khedr Abdullah (53, ~7,500 hours), First Officer Amr al-Shaafei (25,

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905980Thu, 24 Sep 2026 09:00:55 +0000OBOMEDIA ENTERTAINMENTA captain fights controls over the Red Sea as autopilot shifts into control-wheel steering - did they disable it in time? The autopilot switched to control-wheel steering - did they disable it in time? In this episode, we follow the first three...
The autopilot switched to control-wheel steering - did they disable it in time?

In this episode, we follow the first three minutes after Flash Airlines Flight 604 departed Sharm El Sheikh and the rapid cockpit actions that followed. The episode covers the crew makeup, the autopilot's unexpected mode change, and the sequence of manual inputs that preceded the aircraft's sharp right roll - what happened in those compressed seconds?

Date: January 3, 2004
Aircraft: Boeing 737-300 (737 Classic, -300 series, -3Q8)
Location: Red Sea, after departure from Sharm El Sheikh (Charles de Gaulle-bound charter)
Passengers: 148 people aboard
Crew: Captain Khedr Abdullah (53, ~7,500 hours), First Officer Amr al-Shaafei (25,

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

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

In this episode, we present the final minutes and physical evidence surrounding British Commonwealth Pacific Airlines Flight 304 as it descended toward San Francisco. We lay out the crew’s experience, the flight’s routing, and the artifacts found on King's Mountain to ask the central question listeners must confront.

Date: October 29, 1953
Aircraft: Douglas DC‑6 (VH‑BPE, named Resolution)
Location: King's Mountain slope, El Corte de Madera Creek Open Space Preserve, southwest of San Francisco
People: Captain Bruce N. Dickson; First Officer Frank A. Campbell; 11 passengers and 8 crew (including pianist William Kapell and Purser Knight)
Status: Aircraft found intact with landing gear down and locked; 19 fatalities

- The landing gear was found hanging in an oak tree in dense marine fog, configured "down and locked" as for a normal landing approach.
- The flight had crossed the Pacific with stops at Sydney, Fiji, Canton Island, and Honolulu and began descent toward San Francisco after nine hours and twenty‑five minutes over ocean.
- Captain Dickson (34) and First Officer Campbell (28) each logged more than 100 instrument approaches into San Francisco and had flown this approach repeatedly.
- Witness George Bordi heard a single violent impact in the fog; no aircraft wreckage was visible from his vantage point until later searchers found the gear.
- The Civil Aeronautics Board found the aircraft was fully functioning with no mechanical failure noted, leaving investigators to piece together the flight path and cockpit decisions in the final three 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/74905979Wed, 23 Sep 2026 09:00:56 +0000OBOMEDIA ENTERTAINMENTA DC‑6 with gear down vanishes into San Francisco fog near King's Mountain-did the crew reach the runway in time? The landing gear dropped and locked-did they reach the runway in time? In this episode, we present the final minutes and physical...
The landing gear dropped and locked-did they reach the runway in time?

In this episode, we present the final minutes and physical evidence surrounding British Commonwealth Pacific Airlines Flight 304 as it descended toward San Francisco. We lay out the crew’s experience, the flight’s routing, and the artifacts found on King's Mountain to ask the central question listeners must confront.

Date: October 29, 1953
Aircraft: Douglas DC‑6 (VH‑BPE, named Resolution)
Location: King's Mountain slope, El Corte de Madera Creek Open Space Preserve, southwest of San Francisco
People: Captain Bruce N. Dickson; First Officer Frank A. Campbell; 11 passengers and 8 crew (including pianist William Kapell and Purser Knight)
Status: Aircraft found intact with landing gear down and locked; 19 fatalities

- The landing gear was found hanging in an oak tree in dense marine fog, configured "down and locked" as for a normal landing approach.
- The flight had crossed the Pacific with stops at Sydney, Fiji, Canton Island, and Honolulu and began descent toward San Francisco after nine hours and twenty‑five minutes over ocean.
- Captain Dickson (34) and First Officer Campbell (28) each logged more than 100 instrument approaches into San Francisco and had flown this approach repeatedly.
- Witness George Bordi heard a single violent impact in the fog; no aircraft wreckage was visible from his vantage point until later searchers found the gear.
- The Civil Aeronautics Board found the aircraft was fully functioning with no mechanical failure noted, leaving investigators to piece together the flight path and cockpit decisions in the final three 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.]]>1316falsefullhttps://www.spreaker.com/episode/the-cargo-door-indicator-that-went-dark-cost-them-the-runway-in-twenty-minutes--74905978
The cargo door indicator that went dark cost them the runway in twenty minutes

In this episode, we follow the last twenty‑four minutes of a routine cargo flight that ended with wreckage in a backyard and four men dead. We trace the crew actions, two go‑arounds, and a single destroyed instrument that investigators hoped would explain those final minutes - but did it survive long enough to tell the story?

Person: Captain Harry Baker
Person: First Officer Tim Hupp
Person: Flight Engineer Jose Montalbo
Aircraft: Douglas DC‑8, registration N794AL
Event: Cargo door opening on 13 November 1991 prior to crash on 15 February 1992

- Flight originated Seattle 21:45 the night before, destined for Toledo Express as a routine cargo run.
- Aircraft had 72,084 flight hours and 22,804 cycles, in service since 1968 and converted to a freighter.
- Seventy‑two days earlier at Toledo, the same DC‑8 had an in‑flight cargo door opening due to incorrectly installed locking pins and an extinguished indicator light.
- Approach began just after 03:00; first approach at ~03:13 failed and crew executed an unremarkable go‑around on heading 100°.
- Second approach cleared ~03:21 with multiple GPWS warnings for glideslope deviation and excessive descent rate 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/74905978Tue, 22 Sep 2026 09:00:54 +0000OBOMEDIA ENTERTAINMENTA DC‑8 on final to Toledo, a cargo door indicator that had gone dark weeks earlier, two failed approaches and twenty minutes to get it right. The cargo door indicator that went dark cost them the runway in twenty minutes In this episode, we...
The cargo door indicator that went dark cost them the runway in twenty minutes

In this episode, we follow the last twenty‑four minutes of a routine cargo flight that ended with wreckage in a backyard and four men dead. We trace the crew actions, two go‑arounds, and a single destroyed instrument that investigators hoped would explain those final minutes - but did it survive long enough to tell the story?

Person: Captain Harry Baker
Person: First Officer Tim Hupp
Person: Flight Engineer Jose Montalbo
Aircraft: Douglas DC‑8, registration N794AL
Event: Cargo door opening on 13 November 1991 prior to crash on 15 February 1992

- Flight originated Seattle 21:45 the night before, destined for Toledo Express as a routine cargo run.
- Aircraft had 72,084 flight hours and 22,804 cycles, in service since 1968 and converted to a freighter.
- Seventy‑two days earlier at Toledo, the same DC‑8 had an in‑flight cargo door opening due to incorrectly installed locking pins and an extinguished indicator light.
- Approach began just after 03:00; first approach at ~03:13 failed and crew executed an unremarkable go‑around on heading 100°.
- Second approach cleared ~03:21 with multiple GPWS warnings for glideslope deviation and excessive descent rate 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.]]>1282falsefullhttps://www.spreaker.com/episode/the-graduation-she-flew-to-see-fifty-one-minutes-to-reach-houston--74905977
The Graduation She Flew to See-Fifty-One Minutes to Reach Houston

In this episode, we trace the life and work of Guillermina Valdes Villalva and the fifty-one-minute flight that ended her journey to a graduation. We outline how she built support for maquiladora workers and the unanswered questions that followed the plane’s disappearance.

Person: Guillermina Valdes Villalva
Event: Continental Express Flight 2574 explosion over south Texas
Date: September 11, 1991
Topic: Centro de Orientación para la Mujer Obrera (COMO) and maquiladora labor advocacy

- Guillermina, born December 15, 1939 in El Paso, became an advocate for maquiladora women after earning a BA from UTEP and a doctorate from the University of Michigan.
- She founded COMO in Ciudad Juárez, securing a public building from President Luis Echeverría to house classes and services for factory workers.
- COMO’s model required participants to volunteer and teach others, serving roughly 300 women per year in its early years.
- The center offered practical classes-English, nutrition, sewing-while resisting employer limits on training about contracts, safety, and labor rights.
- On September 11, 1991 Guillermina boarded Continental Express Flight 2574 from Laredo to Houston to see her daughter graduate; the plane exploded and no public cause has been confirmed.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905977Mon, 21 Sep 2026 09:00:38 +0000OBOMEDIA ENTERTAINMENTA mother boards a flight from Laredo to Houston to watch her daughter graduate-what happened? The Graduation She Flew to See-Fifty-One Minutes to Reach Houston In this episode, we trace the life and work of Guillermina Valdes Villalva and the...
The Graduation She Flew to See-Fifty-One Minutes to Reach Houston

In this episode, we trace the life and work of Guillermina Valdes Villalva and the fifty-one-minute flight that ended her journey to a graduation. We outline how she built support for maquiladora workers and the unanswered questions that followed the plane’s disappearance.

Person: Guillermina Valdes Villalva
Event: Continental Express Flight 2574 explosion over south Texas
Date: September 11, 1991
Topic: Centro de Orientación para la Mujer Obrera (COMO) and maquiladora labor advocacy

- Guillermina, born December 15, 1939 in El Paso, became an advocate for maquiladora women after earning a BA from UTEP and a doctorate from the University of Michigan.
- She founded COMO in Ciudad Juárez, securing a public building from President Luis Echeverría to house classes and services for factory workers.
- COMO’s model required participants to volunteer and teach others, serving roughly 300 women per year in its early years.
- The center offered practical classes-English, nutrition, sewing-while resisting employer limits on training about contracts, safety, and labor rights.
- On September 11, 1991 Guillermina boarded Continental Express Flight 2574 from Laredo to Houston to see her daughter graduate; the plane exploded and no public cause has been confirmed.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1335falsefullhttps://www.spreaker.com/episode/the-single-flight-plan-that-left-five-seats-and-no-explanation--74905976
The single flight plan that left five seats and no explanation

In this episode, we trace the life and last known journey of Kenneth Baillieu Myer and the five-person flight that ended in wreckage in Alaska. The episode covers his wartime service, decades of cultural leadership in Australia, and the unanswered questions surrounding the trip that preceded the crash.

Person: Kenneth Baillieu Myer
Date: July 30, 1992
Location: Alaska
Event: Light aircraft crash with five occupants
Period: 1921-1992

- Born March 1, 1921 in San Francisco as a legal measure to secure his status under Australian law.
- Awarded the Distinguished Service Cross for action near Port Moresby on August 15, 1944 while serving in the Royal Australian Navy.
- Joined Myer Emporium as a director in 1948 and later served as Chairman and a director through the Coles Myer merger until 1989.
- Decades-long cultural roles: Honorary Secretary of the National Gallery Society of Victoria (from 1948), co-founder of the Myer Foundation (1959), chairman of the Victorian Arts Centre Trust (until 1989), and chairman of the National Library council (1974-1982).
- Married Yasuko Hiraoka in 1979; both died on the same day in the same aircraft that crashed in Alaska, a trip whose purpose was never publicly documented.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905976Sun, 20 Sep 2026 09:01:23 +0000OBOMEDIA ENTERTAINMENTA cultural patron boards a light aircraft in Alaska on July 30, 1992 - one unexplained flight plan. Did they make it in time? The single flight plan that left five seats and no explanation In this episode, we trace the life and last known...
The single flight plan that left five seats and no explanation

In this episode, we trace the life and last known journey of Kenneth Baillieu Myer and the five-person flight that ended in wreckage in Alaska. The episode covers his wartime service, decades of cultural leadership in Australia, and the unanswered questions surrounding the trip that preceded the crash.

Person: Kenneth Baillieu Myer
Date: July 30, 1992
Location: Alaska
Event: Light aircraft crash with five occupants
Period: 1921-1992

- Born March 1, 1921 in San Francisco as a legal measure to secure his status under Australian law.
- Awarded the Distinguished Service Cross for action near Port Moresby on August 15, 1944 while serving in the Royal Australian Navy.
- Joined Myer Emporium as a director in 1948 and later served as Chairman and a director through the Coles Myer merger until 1989.
- Decades-long cultural roles: Honorary Secretary of the National Gallery Society of Victoria (from 1948), co-founder of the Myer Foundation (1959), chairman of the Victorian Arts Centre Trust (until 1989), and chairman of the National Library council (1974-1982).
- Married Yasuko Hiraoka in 1979; both died on the same day in the same aircraft that crashed in Alaska, a trip whose purpose was never publicly documented.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or 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-convair-that-ran-out-of-fuel-did-they-make-it--74905975
The Convair that ran out of fuel - did they make it?

In this episode, we follow the days and decisions leading up to a Convair CV-240 losing power over Mississippi and the life of Ronnie Van Zant as it approached his vowed thirtieth year. We trace his upbringing, the band's rise, and the eerie repetitions - the nickname, the number, the location - that framed the night everyone remembers. What do these details mean for the moments before the crash?

Person: Ronald Wayne Van Zant
Date: October 20, 1977
Event: Convair CV-240 ran out of fuel over Mississippi
Album cover: Street Survivors (release October 20, 1977)
Nickname: "The Mississippi Kid"

- Ronnie Van Zant repeatedly told friends and family he would never reach thirty, saying the number aloud to his father, bandmates, and on the road.
- Four months before his thirtieth birthday, Lynyrd Skynyrd completed Street Survivors and posed Van Zant on the cover wearing a Neil Young T-shirt.
- The band formed in Jacksonville in 1964 from classmates and long-time collaborators, evolving from backyard gigs to headlining stages by 1977.
- On the night of October 20, 1977, the group's charter plane, a Convair CV-240 twin-engine aircraft, ran out of fuel over Mississippi.
- Band members and associates had begun hearing Ronnie call himself "The Mississippi Kid" with no explained connection to the state.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905975Sat, 19 Sep 2026 09:01:23 +0000OBOMEDIA ENTERTAINMENTA Convair runs out of fuel over Mississippi while Lynyrd Skynyrd's frontman nears his self‑predicted thirtieth birthday - did they make it in time? The Convair that ran out of fuel - did they make it? In this episode, we follow the days and...
The Convair that ran out of fuel - did they make it?

In this episode, we follow the days and decisions leading up to a Convair CV-240 losing power over Mississippi and the life of Ronnie Van Zant as it approached his vowed thirtieth year. We trace his upbringing, the band's rise, and the eerie repetitions - the nickname, the number, the location - that framed the night everyone remembers. What do these details mean for the moments before the crash?

Person: Ronald Wayne Van Zant
Date: October 20, 1977
Event: Convair CV-240 ran out of fuel over Mississippi
Album cover: Street Survivors (release October 20, 1977)
Nickname: "The Mississippi Kid"

- Ronnie Van Zant repeatedly told friends and family he would never reach thirty, saying the number aloud to his father, bandmates, and on the road.
- Four months before his thirtieth birthday, Lynyrd Skynyrd completed Street Survivors and posed Van Zant on the cover wearing a Neil Young T-shirt.
- The band formed in Jacksonville in 1964 from classmates and long-time collaborators, evolving from backyard gigs to headlining stages by 1977.
- On the night of October 20, 1977, the group's charter plane, a Convair CV-240 twin-engine aircraft, ran out of fuel over Mississippi.
- Band members and associates had begun hearing Ronnie call himself "The Mississippi Kid" with no explained connection to the state.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1367falsefullhttps://www.spreaker.com/episode/the-controller-s-ten-second-radio-order-overrode-the-tcas-seconds-left--74905973
The Controller's Ten-Second Radio Order Overrode the TCAS Seconds Left

In this episode, we follow two commercial flights converging over southern Germany with less than seventy seconds separating them. The episode covers the chain of human decisions, degraded systems, and the critical radio instruction that arrived just after a TCAS advisory - who acted and what mattered most in those final seconds?

Date: July 1, 2002
Location: Brachenreute, southern Germany
Event: Midair conflict between Bashkirian Tupolev and DHL Boeing
Person: Peter Nielsen
Aircraft: Bashkirian Tupolev Tupolev 154 (RA-85816) and DHL Boeing 757 (Flight 611)

- Two aircraft occupied the same altitude at 34,890 feet and were closing at a combined speed near 1,800 km/h with about 68 seconds to impact.
- The Bashkirian flight carried a UNESCO-sponsored group of children from Ufa bound for Barcelona; many passengers were twelve and thirteen years old.
- Skyguide controller Peter Nielsen was working alone on two workstations while primary radar, telephone links, and a visual collision warning were under maintenance.
- With 60 seconds remaining Nielsen diverted attention to a delayed Aero Lloyd flight, turning away from his radar as the two aircraft converged.
- At 23:34:49 TCAS issued a climb to the Tupolev and a descend to the Boeing; eleven seconds later Nielsen instructed the Tupolev to descend to FL350.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905973Fri, 18 Sep 2026 09:00:42 +0000OBOMEDIA ENTERTAINMENTA traffic-collision warning orders climb while a controller over southern Germany radios descent - did the pilots follow TCAS or the controller? The Controller's Ten-Second Radio Order Overrode the TCAS Seconds Left In this episode, we follow...
The Controller's Ten-Second Radio Order Overrode the TCAS Seconds Left

In this episode, we follow two commercial flights converging over southern Germany with less than seventy seconds separating them. The episode covers the chain of human decisions, degraded systems, and the critical radio instruction that arrived just after a TCAS advisory - who acted and what mattered most in those final seconds?

Date: July 1, 2002
Location: Brachenreute, southern Germany
Event: Midair conflict between Bashkirian Tupolev and DHL Boeing
Person: Peter Nielsen
Aircraft: Bashkirian Tupolev Tupolev 154 (RA-85816) and DHL Boeing 757 (Flight 611)

- Two aircraft occupied the same altitude at 34,890 feet and were closing at a combined speed near 1,800 km/h with about 68 seconds to impact.
- The Bashkirian flight carried a UNESCO-sponsored group of children from Ufa bound for Barcelona; many passengers were twelve and thirteen years old.
- Skyguide controller Peter Nielsen was working alone on two workstations while primary radar, telephone links, and a visual collision warning were under maintenance.
- With 60 seconds remaining Nielsen diverted attention to a delayed Aero Lloyd flight, turning away from his radar as the two aircraft converged.
- At 23:34:49 TCAS issued a climb to the Tupolev and a descend to the Boeing; eleven seconds later Nielsen instructed the Tupolev to descend to FL350.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1307falsefullhttps://www.spreaker.com/episode/the-loose-ski-boot-jammed-the-gear-and-stole-their-last-minutes--74905972
The loose ski boot jammed the gear and stole their last minutes

In this episode, we follow the final hours before a small plane’s fatal takeoff from Unalakleet, Alaska, tracing the decisions, technical failures and personal moments that led up to the crash. What tiny choices and mechanical details turned a routine departure into a catastrophe?

Person: Félix Samuel Rodríguez de la Fuente
Date: March 14, 1980
Location: Unalakleet airstrip, near Shaktoolik, Alaska
Event: Aircraft took off with a loose ski boot on the landing gear
Topic: Final minutes, mechanical failure and pre-flight decisions

- Félix celebrated his fifty-second birthday the morning he boarded the flight after arriving to cover the Iditarod.
- He had a documented fear of flying but traveled because his documentary plans demanded it.
- The plane climbed only a few dozen meters and then suddenly stopped climbing during takeoff.
- A loose ski boot on the landing gear and a tiny latch or pin failure are cited as critical mechanical factors.
- Ten days earlier Félix presented a Global Strategy for the Protection of Biodiversity before the Spanish king and queen, then departed for Alaska with a full filming schedule.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905972Thu, 17 Sep 2026 09:00:58 +0000OBOMEDIA ENTERTAINMENTA loose ski boot jammed the landing gear of a small plane on a frozen Alaskan airstrip, delaying a naturalist's birthday flight. Did they make it in time? The loose ski boot jammed the gear and stole their last minutes In this episode, we follow...
The loose ski boot jammed the gear and stole their last minutes

In this episode, we follow the final hours before a small plane’s fatal takeoff from Unalakleet, Alaska, tracing the decisions, technical failures and personal moments that led up to the crash. What tiny choices and mechanical details turned a routine departure into a catastrophe?

Person: Félix Samuel Rodríguez de la Fuente
Date: March 14, 1980
Location: Unalakleet airstrip, near Shaktoolik, Alaska
Event: Aircraft took off with a loose ski boot on the landing gear
Topic: Final minutes, mechanical failure and pre-flight decisions

- Félix celebrated his fifty-second birthday the morning he boarded the flight after arriving to cover the Iditarod.
- He had a documented fear of flying but traveled because his documentary plans demanded it.
- The plane climbed only a few dozen meters and then suddenly stopped climbing during takeoff.
- A loose ski boot on the landing gear and a tiny latch or pin failure are cited as critical mechanical factors.
- Ten days earlier Félix presented a Global Strategy for the Protection of Biodiversity before the Spanish king and queen, then departed for Alaska with a full filming schedule.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1016falsefullhttps://www.spreaker.com/episode/the-notebook-that-counted-down-metres-and-ran-out-of-altitude--74905970
The notebook that counted down metres - and ran out of altitude

In this episode, we follow the thirty-four-minute Milan-Frankfurt flight of KLM's DC-2 PH-AKG, piecing together radio transmissions and five notebook pages to see what unfolded inside the cabin. The episode lays out the flight, the crew, and the escalating conditions, and asks what the altitude entries really meant for the people aboard.

Date: 20 July 1935
Aircraft: Douglas DC-2 PH-AKG
Flight time: 34 minutes
Passengers aboard: 13
Notebook last entry: 2100 metres

- Departure from Milan at 11:56 local for a routine Alpine crossing via the San Bernardino pass.
- Captain Johannes van der Feijst with 3,200 flight hours, plus flight engineer Vocke and radio operator Aafjes in the cockpit.
- Passenger Jos van Langen, a 25-year-old foreign editor, kept a running notebook and began recording altitudes fifteen minutes after takeoff.
- The Gaai climbed through 4,000, 4,500 and then into 5,000 metres before entering dense cloud and heavy-sounding precipitation.
- Radio transmissions reached the ground while five notebook pages grew progressively harder to read, ending with “2100” metres and the pen falling silent.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905970Wed, 16 Sep 2026 09:00:59 +0000OBOMEDIA ENTERTAINMENTA passenger's notebook tracks a Douglas DC-2's frantic descent through cloud and ice over the Alps - did the crew reach safety before the pen stopped? The notebook that counted down metres - and ran out of altitude In this episode, we follow the...
The notebook that counted down metres - and ran out of altitude

In this episode, we follow the thirty-four-minute Milan-Frankfurt flight of KLM's DC-2 PH-AKG, piecing together radio transmissions and five notebook pages to see what unfolded inside the cabin. The episode lays out the flight, the crew, and the escalating conditions, and asks what the altitude entries really meant for the people aboard.

Date: 20 July 1935
Aircraft: Douglas DC-2 PH-AKG
Flight time: 34 minutes
Passengers aboard: 13
Notebook last entry: 2100 metres

- Departure from Milan at 11:56 local for a routine Alpine crossing via the San Bernardino pass.
- Captain Johannes van der Feijst with 3,200 flight hours, plus flight engineer Vocke and radio operator Aafjes in the cockpit.
- Passenger Jos van Langen, a 25-year-old foreign editor, kept a running notebook and began recording altitudes fifteen minutes after takeoff.
- The Gaai climbed through 4,000, 4,500 and then into 5,000 metres before entering dense cloud and heavy-sounding precipitation.
- Radio transmissions reached the ground while five notebook pages grew progressively harder to read, ending with “2100” metres and the pen falling silent.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1403falsefullhttps://www.spreaker.com/episode/210-metres-from-the-runway-and-64-people-did-not-survive--74905968
210 metres from the runway - and 64 people did not survive

In this episode, we follow the flight from Moscow through Omsk to Alma-Ata and the sequence of decisions, broken procedures, and missing weather reports that shaped the final approach. What combinations of errors and choices put the aircraft two hundred and ten metres short of the runway?

Date: 4 January 1965
Aircraft: Ilyushin Il-18B, registration CCCP-75685
Route: Domodedovo - Omsk - Alma-Ata
Crew: Captain Konstantin Artamonov; co-pilot Nikolai Slamikhin; flight engineer Anatoliy Shakirov; navigator Vladimir Pristavka; radio operator Nikolay Safonov
Passengers: 103 on board

- Departure from Domodedovo was delayed by nearly three hours after an engine repair, compressing the day’s schedule.
- Rishat Azakov, head of the Kazakh Civil Aviation Directorate, boarded as check captain with supervisory authority despite lacking a current medical certificate and having already worked about fifteen hours.
- The meteorological service stopped issuing weather updates during the critical period; scheduled reports at 20:00, 20:15 and 20:30 were not sent.
- Another Il-18 had returned after two attempts and informed operations that no Il-18 could safely land in the conditions, yet Flight 20 was cleared to descend five minutes later.
- The aircraft struck frozen ground 210 metres right of runway 23, flying ten metres below the altitude where the crew should have seen the runway.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905968Tue, 15 Sep 2026 09:00:51 +0000OBOMEDIA ENTERTAINMENTAn Aeroflot Il-18 descends toward Alma-Ata while a senior check captain with a lapsed medical certificate holds authority - did they make it in time? 210 metres from the runway - and 64 people did not survive In this episode, we follow the...
210 metres from the runway - and 64 people did not survive

In this episode, we follow the flight from Moscow through Omsk to Alma-Ata and the sequence of decisions, broken procedures, and missing weather reports that shaped the final approach. What combinations of errors and choices put the aircraft two hundred and ten metres short of the runway?

Date: 4 January 1965
Aircraft: Ilyushin Il-18B, registration CCCP-75685
Route: Domodedovo - Omsk - Alma-Ata
Crew: Captain Konstantin Artamonov; co-pilot Nikolai Slamikhin; flight engineer Anatoliy Shakirov; navigator Vladimir Pristavka; radio operator Nikolay Safonov
Passengers: 103 on board

- Departure from Domodedovo was delayed by nearly three hours after an engine repair, compressing the day’s schedule.
- Rishat Azakov, head of the Kazakh Civil Aviation Directorate, boarded as check captain with supervisory authority despite lacking a current medical certificate and having already worked about fifteen hours.
- The meteorological service stopped issuing weather updates during the critical period; scheduled reports at 20:00, 20:15 and 20:30 were not sent.
- Another Il-18 had returned after two attempts and informed operations that no Il-18 could safely land in the conditions, yet Flight 20 was cleared to descend five minutes later.
- The aircraft struck frozen ground 210 metres right of runway 23, flying ten metres below the altitude where the crew should have seen the runway.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1095falsefullhttps://www.spreaker.com/episode/the-free-upgrade-that-moved-him-off-flight-800-did-he-make-it--74905967
The free upgrade that moved him off Flight 800 - did he make it?

In this episode, we follow the life moments that led Jed Johnson to accept a free first-class seat the night TWA Flight 800 disintegrated, tracing his path from Midwestern roots to Andy Warhol’s inner circle and a career in high‑end interior design. What does one small, ordinary decision reveal about how his life was lived - and what happened that night?

Person: Jed Johnson
Date: July 17, 1996
Location: Atlantic off the coast of Long Island
Event: TWA Flight 800 disintegration
Birth Date: December 30, 1948

- He accepted an airline upgrade that moved his departure up by one day and placed him on Flight 800.
- Born in Alexandria, Minnesota, he was a twin and the fourth of six children, later living in Scottsdale and Fair Oaks.
- At nineteen he arrived in New York, was hired at Andy Warhol’s Factory, and became Warhol’s close companion after the 1968 shooting.
- He taught himself spatial design while organizing Warhol’s townhouse and later designed Warhol’s East Sixty‑sixth Street home over four years.
- His design work, featured in Vogue, led to commissions from Mick Jagger, Bianca Jagger, Barbra Streisand, and others.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905967Mon, 14 Sep 2026 09:00:48 +0000OBOMEDIA ENTERTAINMENTA free upgrade on July 16, 1996 moved Jed Johnson onto TWA Flight 800 - a single choice that put him on a doomed plane. Did he make it in time? The free upgrade that moved him off Flight 800 - did he make it? In this episode, we follow the life...
The free upgrade that moved him off Flight 800 - did he make it?

In this episode, we follow the life moments that led Jed Johnson to accept a free first-class seat the night TWA Flight 800 disintegrated, tracing his path from Midwestern roots to Andy Warhol’s inner circle and a career in high‑end interior design. What does one small, ordinary decision reveal about how his life was lived - and what happened that night?

Person: Jed Johnson
Date: July 17, 1996
Location: Atlantic off the coast of Long Island
Event: TWA Flight 800 disintegration
Birth Date: December 30, 1948

- He accepted an airline upgrade that moved his departure up by one day and placed him on Flight 800.
- Born in Alexandria, Minnesota, he was a twin and the fourth of six children, later living in Scottsdale and Fair Oaks.
- At nineteen he arrived in New York, was hired at Andy Warhol’s Factory, and became Warhol’s close companion after the 1968 shooting.
- He taught himself spatial design while organizing Warhol’s townhouse and later designed Warhol’s East Sixty‑sixth Street home over four years.
- His design work, featured in Vogue, led to commissions from Mick Jagger, Bianca Jagger, Barbra Streisand, and others.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1180falsefullhttps://www.spreaker.com/episode/the-transponder-that-began-cycling-saved-no-seconds-did-they-make-it--74905966
The Transponder That Began Cycling Saved No Seconds, Did They Make It?

In this episode, we follow the twenty-one minutes before United Airlines Flight 175 vanished from recorded flight data and trace the calls, choices, and movements aboard the Boeing 767. What do the phone calls, seating moves, and a cycling transponder reveal about those final minutes?

Flight: United Airlines Flight 175
Date: September 11, 2001
Aircraft: Boeing 767, registration N612UA
Captain: Victor Saracini; First Officer: Michael Horrocks
Passengers aboard: 51

- Passengers included Peter, Sue, and two-year-old Christine Hanson seated in row 19 C, D, E and several crew of six flight attendants with Purser Kathryn Laborie.
- Five men boarded at Gate 19, Terminal C between 7:23 and 7:28 a.m.; their leader was Marwan al-Shehhi, a trained pilot who practiced in simulators.
- At 8:42 a.m. Captain Saracini made the last transmission, reporting someone keyed the mic and saying, "Everyone stay in your seats."
- Four minutes later the aircraft was off course and the transponder began cycling through codes: 1470 then 3020 before communications ceased.
- Two phone calls from a passenger in seat 30E to his father documented weapons, injuries, and intentions in real time while no cockpit voice or data recorders were ever recovered.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905966Sun, 13 Sep 2026 09:01:15 +0000OBOMEDIA ENTERTAINMENTA passenger on a transcontinental flight calls his father as the Boeing’s transponder cycles through codes; did they make it in time? The Transponder That Began Cycling Saved No Seconds, Did They Make It? In this episode, we follow the...
The Transponder That Began Cycling Saved No Seconds, Did They Make It?

In this episode, we follow the twenty-one minutes before United Airlines Flight 175 vanished from recorded flight data and trace the calls, choices, and movements aboard the Boeing 767. What do the phone calls, seating moves, and a cycling transponder reveal about those final minutes?

Flight: United Airlines Flight 175
Date: September 11, 2001
Aircraft: Boeing 767, registration N612UA
Captain: Victor Saracini; First Officer: Michael Horrocks
Passengers aboard: 51

- Passengers included Peter, Sue, and two-year-old Christine Hanson seated in row 19 C, D, E and several crew of six flight attendants with Purser Kathryn Laborie.
- Five men boarded at Gate 19, Terminal C between 7:23 and 7:28 a.m.; their leader was Marwan al-Shehhi, a trained pilot who practiced in simulators.
- At 8:42 a.m. Captain Saracini made the last transmission, reporting someone keyed the mic and saying, "Everyone stay in your seats."
- Four minutes later the aircraft was off course and the transponder began cycling through codes: 1470 then 3020 before communications ceased.
- Two phone calls from a passenger in seat 30E to his father documented weapons, injuries, and intentions in real time while no cockpit voice or data recorders were ever recovered.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1344falsefullhttps://www.spreaker.com/episode/the-flaps-set-at-five-degrees-left-them-racing-the-runway-clock--74905965
The flaps set at five degrees left them racing the runway clock

In this episode, we follow the final minutes of Garuda Indonesia Flight GA 200 as recorded by the flight and cockpit voice recorders. The episode lays out the sequence of speeds, flap settings, alarms and cockpit exchanges that led up to the runway crossing and asks what decisions sealed the aircraft's fate.

Date: March 7, 2007
Flight: Garuda Indonesia Flight GA 200
Aircraft: Boeing 737‑497, registration PK‑GZC
Person: Captain Muhammad Marwoto Komar (44), First Officer Gagam Saman Rohmana (30)
Passengers: 133 aboard, including 21 foreign nationals

- At 07:07 the aircraft touched down 860 meters past the runway threshold; normal touchdown is roughly 300 meters.
- The plane crossed the outer approach at 241 knots when the standard speed should have been 141 knots.
- First Officer Rohmana set flaps to 5 degrees-the maximum safe at that speed-while Captain Komar requested 15 degrees.
- Every alarm in the cockpit was sounding and the cockpit voice recorder captured repeated, unanswered prompts and silences.
- Six days earlier Garuda introduced a fuel‑saving bonus for crews who arrived under expected fuel, a detail Komar later denied influenced his actions.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905965Sat, 12 Sep 2026 09:01:24 +0000OBOMEDIA ENTERTAINMENTA captain and first officer race a Boeing 737 toward Yogyakarta with flaps at five degrees and alarms screaming-did they make it in time? The flaps set at five degrees left them racing the runway clock In this episode, we follow the final...
The flaps set at five degrees left them racing the runway clock

In this episode, we follow the final minutes of Garuda Indonesia Flight GA 200 as recorded by the flight and cockpit voice recorders. The episode lays out the sequence of speeds, flap settings, alarms and cockpit exchanges that led up to the runway crossing and asks what decisions sealed the aircraft's fate.

Date: March 7, 2007
Flight: Garuda Indonesia Flight GA 200
Aircraft: Boeing 737‑497, registration PK‑GZC
Person: Captain Muhammad Marwoto Komar (44), First Officer Gagam Saman Rohmana (30)
Passengers: 133 aboard, including 21 foreign nationals

- At 07:07 the aircraft touched down 860 meters past the runway threshold; normal touchdown is roughly 300 meters.
- The plane crossed the outer approach at 241 knots when the standard speed should have been 141 knots.
- First Officer Rohmana set flaps to 5 degrees-the maximum safe at that speed-while Captain Komar requested 15 degrees.
- Every alarm in the cockpit was sounding and the cockpit voice recorder captured repeated, unanswered prompts and silences.
- Six days earlier Garuda introduced a fuel‑saving bonus for crews who arrived under expected fuel, a detail Komar later denied influenced his actions.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1350falsefullhttps://www.spreaker.com/episode/the-maintenance-shortcut-that-cracked-the-flange-and-doomed-flight-191--74905964
The maintenance shortcut that cracked the flange and doomed Flight 191

In this episode, we follow the documented sequence of events that began in a Tulsa hangar and culminated thirty-one seconds after takeoff at O'Hare. The episode traces the people aboard, the decisions in maintenance, and the metal evidence that held a warning - but did anyone see it before it was too late?

Date: May 25, 1979
Flight: American Airlines Flight 191
Aircraft: McDonnell Douglas DC-10, tail N110AA
Location: O'Hare runway 32R
Event: Engine separation after takeoff

- The number one engine tore away from the left wing during the takeoff roll and fell onto the runway as the aircraft continued climbing.
- The crack in a metal flange had been growing for fifty-nine days, cycle by cycle, before the failure.
- Fifty-nine days earlier, the aircraft underwent an engine change in Tulsa where American Airlines used a 27-step shortcut instead of the manufacturer's 79-step procedure.
- The cockpit crew held the prescribed attitude and airspeed exactly as the manual required in the seconds after separation.
- Investigators found the fracture in the wreckage and read its history in the metal, linking the failure to the maintenance change.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905964Fri, 11 Sep 2026 09:00:54 +0000OBOMEDIA ENTERTAINMENTA cracked flange at O'Hare and a DC-10 climbing away with an engine on the runway - did they make it in time? The maintenance shortcut that cracked the flange and doomed Flight 191 In this episode, we follow the documented sequence of events...
The maintenance shortcut that cracked the flange and doomed Flight 191

In this episode, we follow the documented sequence of events that began in a Tulsa hangar and culminated thirty-one seconds after takeoff at O'Hare. The episode traces the people aboard, the decisions in maintenance, and the metal evidence that held a warning - but did anyone see it before it was too late?

Date: May 25, 1979
Flight: American Airlines Flight 191
Aircraft: McDonnell Douglas DC-10, tail N110AA
Location: O'Hare runway 32R
Event: Engine separation after takeoff

- The number one engine tore away from the left wing during the takeoff roll and fell onto the runway as the aircraft continued climbing.
- The crack in a metal flange had been growing for fifty-nine days, cycle by cycle, before the failure.
- Fifty-nine days earlier, the aircraft underwent an engine change in Tulsa where American Airlines used a 27-step shortcut instead of the manufacturer's 79-step procedure.
- The cockpit crew held the prescribed attitude and airspeed exactly as the manual required in the seconds after separation.
- Investigators found the fracture in the wreckage and read its history in the metal, linking the failure to the maintenance change.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1291falsefullhttps://www.spreaker.com/episode/the-flight-idle-gate-that-spencer-breached-and-whether-four-minutes-was-enough--74905963
The flight idle gate that Spencer breached - and whether four minutes was enough

In this episode we follow the final minutes of Airlines PNG Flight 1600, the thirty-minute hop from Lae to Madang that became a disaster in four minutes and eighteen seconds. We lay out the timeline, the crew actions and the missing safety component that investigators would focus on - what questions remain about responsibility and system design?

Date: 13 October 2011
Flight: Airlines PNG Flight 1600
Aircraft: DHC-8-100, registration P2-MCJ
Person: Captain William Spencer; First Officer Campbell Wagstaff
Passengers: 32 aboard, 4 walked away

- Flight 1600 departed Lae Nadzab at 16:47 local time bound for Madang with a scheduled 30-minute flight.
- The aircraft climbed to 16,000 ft, diverted around thunderstorms, then entered a steeper descent that built high airspeed.
- An overspeed warning sounded; Spencer called for higher propeller RPM while managing the descent.
- Spencer pulled the power levers past the physical flight idle gate into the ground beta range while still airborne.
- Investigators spent nearly three years focused not on a deep mechanical flaw but on why a working safety device was not installed on this airplane.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905963Thu, 10 Sep 2026 09:00:56 +0000OBOMEDIA ENTERTAINMENTA turboprop dives toward Madang with a safety device missing - can the crew stop the plane in four minutes and change the outcome? The flight idle gate that Spencer breached - and whether four minutes was enough In this episode we follow the...
The flight idle gate that Spencer breached - and whether four minutes was enough

In this episode we follow the final minutes of Airlines PNG Flight 1600, the thirty-minute hop from Lae to Madang that became a disaster in four minutes and eighteen seconds. We lay out the timeline, the crew actions and the missing safety component that investigators would focus on - what questions remain about responsibility and system design?

Date: 13 October 2011
Flight: Airlines PNG Flight 1600
Aircraft: DHC-8-100, registration P2-MCJ
Person: Captain William Spencer; First Officer Campbell Wagstaff
Passengers: 32 aboard, 4 walked away

- Flight 1600 departed Lae Nadzab at 16:47 local time bound for Madang with a scheduled 30-minute flight.
- The aircraft climbed to 16,000 ft, diverted around thunderstorms, then entered a steeper descent that built high airspeed.
- An overspeed warning sounded; Spencer called for higher propeller RPM while managing the descent.
- Spencer pulled the power levers past the physical flight idle gate into the ground beta range while still airborne.
- Investigators spent nearly three years focused not on a deep mechanical flaw but on why a working safety device was not installed on this airplane.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1114falsefullhttps://www.spreaker.com/episode/the-controller-said-the-wrong-flight-number-did-they-make-it--74905962
The Controller Said the Wrong Flight Number - Did They Make It?

In this episode, we follow the minutes on January 31, 2001 when two Japan Airlines aircraft converged over Suruga Bay and the human and technical decisions that intersected beneath their wings. The narrative lays out who was in the room, what systems acted, and the moment a single spoken error changed everything - could the responses prevent disaster?

Person: Controller Hideki Hachitani
Date: January 31, 2001
Location: Suruga Bay / Tokyo Area Control Center
Event: Near mid-air collision involving JAL flights 907 and 958
System: TCAS issued a climb Resolution Advisory to JAL 907

- JAL 907 (Boeing 747, JA8904) departed Haneda with 411 passengers and 16 crew, bound for Naha.
- JAL 958 (DC-10, JA8546) was inbound to Narita with 237 passengers and 13 crew, converging on the same sector.
- Trainee controller Hachitani was managing twelve radar targets-ten other aircraft at the same time as the two JAL flights.
- The planned vertical separation was 2,000 feet; when the incident unfolded the planes were separated by roughly 135 meters.
- The aircraft’s TCAS detected the closure rate and issued a climb advisory before the controller’s spoken clearance reached the crews.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905962Wed, 09 Sep 2026 09:01:20 +0000OBOMEDIA ENTERTAINMENTA trainee Tokyo controller misheard flight numbers as two JAL airliners closed to 135 meters over Suruga Bay-did they make it in time? The Controller Said the Wrong Flight Number - Did They Make It? In this episode, we follow the minutes on...
The Controller Said the Wrong Flight Number - Did They Make It?

In this episode, we follow the minutes on January 31, 2001 when two Japan Airlines aircraft converged over Suruga Bay and the human and technical decisions that intersected beneath their wings. The narrative lays out who was in the room, what systems acted, and the moment a single spoken error changed everything - could the responses prevent disaster?

Person: Controller Hideki Hachitani
Date: January 31, 2001
Location: Suruga Bay / Tokyo Area Control Center
Event: Near mid-air collision involving JAL flights 907 and 958
System: TCAS issued a climb Resolution Advisory to JAL 907

- JAL 907 (Boeing 747, JA8904) departed Haneda with 411 passengers and 16 crew, bound for Naha.
- JAL 958 (DC-10, JA8546) was inbound to Narita with 237 passengers and 13 crew, converging on the same sector.
- Trainee controller Hachitani was managing twelve radar targets-ten other aircraft at the same time as the two JAL flights.
- The planned vertical separation was 2,000 feet; when the incident unfolded the planes were separated by roughly 135 meters.
- The aircraft’s TCAS detected the closure rate and issued a climb advisory before the controller’s spoken clearance reached the crews.

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

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

In this episode, the story follows the moments before the Learjet crash that killed Walter Reuther and the life that led him there. We trace the damaged instrument, the pilots’ descent through night weather, and Reuther’s rise from factory tool-and-die maker to UAW leader - what led him to be on that flight and what questions the wreckage left unanswered.

Person: Walter Philip Reuther
Date: May 9, 1970
Event: Learjet twenty-three crash
Location: night approach to runway in rain and fog
Injury: altimeter missing parts and one piece installed backward

- Three parts were missing from the instrument recovered from the wreckage.
- One component of the altimeter was installed completely upside down.
- Pilots were descending through rain and fog toward a runway they could not see.
- Walter Reuther survived a 1948 assassination attempt that shattered his arm into roughly 150 pieces.
- Reuther rose from tool-and-die maker to lead the UAW and helped organize the 1936-37 sit-down strikes.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905961Tue, 08 Sep 2026 09:01:31 +0000OBOMEDIA ENTERTAINMENTA broken altimeter, rain and fog, and a Learjet careening toward a runway the pilots cannot see - did they make it in time? The broken altimeter failed to warn them before impact In this episode, the story follows the moments before the Learjet...
The broken altimeter failed to warn them before impact

In this episode, the story follows the moments before the Learjet crash that killed Walter Reuther and the life that led him there. We trace the damaged instrument, the pilots’ descent through night weather, and Reuther’s rise from factory tool-and-die maker to UAW leader - what led him to be on that flight and what questions the wreckage left unanswered.

Person: Walter Philip Reuther
Date: May 9, 1970
Event: Learjet twenty-three crash
Location: night approach to runway in rain and fog
Injury: altimeter missing parts and one piece installed backward

- Three parts were missing from the instrument recovered from the wreckage.
- One component of the altimeter was installed completely upside down.
- Pilots were descending through rain and fog toward a runway they could not see.
- Walter Reuther survived a 1948 assassination attempt that shattered his arm into roughly 150 pieces.
- Reuther rose from tool-and-die maker to lead the UAW and helped organize the 1936-37 sit-down strikes.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1219falsefullhttps://www.spreaker.com/episode/the-handbag-s-ten-thousand-dollars-burned-as-the-plane-lost-its-only-exit--74905960
The handbag's ten-thousand dollars burned as the plane lost its only exit

In this episode, we lay out who Dorothy Hunt was, where she was traveling, and the tangled Washington network connected to the cash found in her handbag. The episode follows the flight, the investigations, and the unanswered questions that kept the money's purpose a mystery.

Person: Dorothy Hunt
Event: United Airlines Flight 553 crash
Date: December 8, 1972
Location: Chicago Midlothian neighborhood
Topic: Unexplained cash linked to Watergate network

- Dorothy Hunt boarded Flight 553 in Washington bound for Chicago carrying a handbag with over ten thousand dollars in cash.
- She was the wife of E. Howard Hunt, a former CIA officer turned Watergate operative who worked with the White House Plumbers.
- First responders found her handbag in the wreckage within hours after the plane struck houses in Chicago.
- The NTSB, the FBI, and Congress all investigated the crash while separately grappling with the unexplained cash.
- Members of a Washington hush-money network, including lawyers and White House aides, were moving funds to burglars and families in December 1972.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74905960Mon, 07 Sep 2026 09:01:38 +0000OBOMEDIA ENTERTAINMENTA woman carrying over ten thousand dollars on a flight to Chicago dies in a crash-did the hush-money make it out before the plane lost its only exit? The handbag's ten-thousand dollars burned as the plane lost its only exit In this episode, we...
The handbag's ten-thousand dollars burned as the plane lost its only exit

In this episode, we lay out who Dorothy Hunt was, where she was traveling, and the tangled Washington network connected to the cash found in her handbag. The episode follows the flight, the investigations, and the unanswered questions that kept the money's purpose a mystery.

Person: Dorothy Hunt
Event: United Airlines Flight 553 crash
Date: December 8, 1972
Location: Chicago Midlothian neighborhood
Topic: Unexplained cash linked to Watergate network

- Dorothy Hunt boarded Flight 553 in Washington bound for Chicago carrying a handbag with over ten thousand dollars in cash.
- She was the wife of E. Howard Hunt, a former CIA officer turned Watergate operative who worked with the White House Plumbers.
- First responders found her handbag in the wreckage within hours after the plane struck houses in Chicago.
- The NTSB, the FBI, and Congress all investigated the crash while separately grappling with the unexplained cash.
- Members of a Washington hush-money network, including lawyers and White House aides, were moving funds to burglars and families in December 1972.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1283falsefullhttps://www.spreaker.com/episode/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