https://www.spreaker.com/podcast/plane-crash-stories--7307849
From mechanical failures to pilot errors, each episode of Plane Crash Stories explores the chilling details of these incidents, focusing on the human element amidst the chaos. We examine the 'how' and 'why' of survival, offering a unique perspective on the aftermath of these catastrophic events. This podcast is a deep dive into the psychology of survival and the extraordinary circumstances that defy the odds.

New episodes are published daily, Monday through Sunday, at 4:00 AM EST, ensuring a fresh story to captivate you every morning. Each episode is a standalone narrative, thoroughly researched to bring you compelling and accurate accounts.

This podcast is for anyone fascinated by true survival stories, aviation history, and the indomitable human spirit. If you're drawn to narratives where one person miraculously escapes the impossible, Plane Crash Stories is your next listen.

Subscribe now and uncover the untold tales of those who defied fate.]]>enHistoryCopyright OBOMEDIA ENTERTAINMENThttps://d3wo5wojvuv7l.cloudfront.net/t_rss_itunes_square_1400/images.spreaker.com/original/24772eed60e914a7431aa1628c801364.jpghttps://www.spreaker.com/podcast/plane-crash-stories--7307849Thu, 15 Oct 2026 08:03:04 +0000OBOMEDIA ENTERTAINMENTOBOMEDIA ENTERTAINMENTcreators@obomedia.comEvery plane crash leaves a story, but some leave a mystery: how did someone survive when no one else did? Plane Crash Stories delves into the incredible true accounts of the sole survivors of aviation disasters. We meticulously reconstruct the events,...
From mechanical failures to pilot errors, each episode of Plane Crash Stories explores the chilling details of these incidents, focusing on the human element amidst the chaos. We examine the 'how' and 'why' of survival, offering a unique perspective on the aftermath of these catastrophic events. This podcast is a deep dive into the psychology of survival and the extraordinary circumstances that defy the odds.

New episodes are published daily, Monday through Sunday, at 4:00 AM EST, ensuring a fresh story to captivate you every morning. Each episode is a standalone narrative, thoroughly researched to bring you compelling and accurate accounts.

This podcast is for anyone fascinated by true survival stories, aviation history, and the indomitable human spirit. If you're drawn to narratives where one person miraculously escapes the impossible, Plane Crash Stories is your next listen.

Subscribe now and uncover the untold tales of those who defied fate.]]>falsebf410af4-7107-5e33-8333-cf5beebd2b5depisodichttps://www.spreaker.com/episode/a-contact-lens-bottle-that-held-nitroglycerin--74832979
A contact lens bottle that held nitroglycerin

This episode recounts the harrowing events aboard Philippine Airlines Flight 434, where a seemingly ordinary item concealed a deadly device. It explores the incredible resilience of the flight crew and the terrifying realization that this incident was merely a prelude to a much larger plot.

Person: Ramzi Yousef
Date: December 11, 1994
Location: Philippine Airlines Flight 434
Aircraft: Boeing 747
Route: Manila to Tokyo

- A man boarded the Manila-to-Cebu leg of the flight under the alias "Armaldo Forlani."
- He assembled a bomb in the lavatory, using components hidden in his shoes and a modified Casio Databank watch.
- The explosive was liquid nitroglycerin, carried in a contact lens fluid bottle, indistinguishable from a toiletry item.
- He set the timer for four hours and placed the device in the life vest pocket under seat 26K.
- After landing in Cebu, he disembarked with domestic passengers, leaving the bomb behind for the international flight to Tokyo.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832979Fri, 16 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA contact lens bottle containing liquid nitroglycerin passes airport security, but the real danger isn't the bomb itself. It's the chilling discovery that this flight is just a rehearsal. A contact lens bottle that held nitroglycerin This...
A contact lens bottle that held nitroglycerin

This episode recounts the harrowing events aboard Philippine Airlines Flight 434, where a seemingly ordinary item concealed a deadly device. It explores the incredible resilience of the flight crew and the terrifying realization that this incident was merely a prelude to a much larger plot.

Person: Ramzi Yousef
Date: December 11, 1994
Location: Philippine Airlines Flight 434
Aircraft: Boeing 747
Route: Manila to Tokyo

- A man boarded the Manila-to-Cebu leg of the flight under the alias "Armaldo Forlani."
- He assembled a bomb in the lavatory, using components hidden in his shoes and a modified Casio Databank watch.
- The explosive was liquid nitroglycerin, carried in a contact lens fluid bottle, indistinguishable from a toiletry item.
- He set the timer for four hours and placed the device in the life vest pocket under seat 26K.
- After landing in Cebu, he disembarked with domestic passengers, leaving the bomb behind for the international flight to Tokyo.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1329falsefullhttps://www.spreaker.com/episode/the-twin-empty-seats-that-arrived-at-his-daughter-s-party--74832977
An eighty-year-old man waits for two sons who boarded a small plane to fly to their sister's fortieth birthday party. Behind that afternoon lies a life that had already survived a cockpit shot down over Tobruk, a fence at Stalag Luft III, and the floor of the House of Commons — but nothing in eighty years had prepared him for what didn't arrive. What does a man do with a life this full when the people who gave it meaning are taken from him one by one?

In this episode, we trace Aidan Crawley's path from a record-breaking cricket career at Oxford and Lord's through wartime intelligence work, imprisonment, Parliament, and British television, asking how one man's extraordinary public life sat alongside private losses almost too heavy to name.

Person: Aidan Merivale Crawley
Location: Buckinghamshire and the skies over Tobruk, Silesia, and Britain
Date: summer 1988
Case: the small plane carrying his two sons that never landed
Status: both sons died; Crawley died in 1993, described as virtually penniless

- In the 1926 Eton v Harrow match at Lord's, an 18-year-old Crawley scored 87 runs, which Wisden called the best innings in the match for many years
- Shot down near Tobruk in July 1941, he was held at Stalag Luft III in Silesia and was inside the camp during the March 1944 mass escape, in which 50 of the 76 escapees were shot on Hitler's orders
- He won Buckingham for Labour in the 1945 election, serving as Under-Secretary of State for Air, later crossed to the Conservatives and won West Derbyshire in a 1962 by-election
- He became the first editor-in-chief of Independent Television News in 1955, introducing the American-style newscaster format to British screens
- In summer 1988, his sons Andrew (41) and Randall (38) died when their small plane failed to arrive at sister Harriet's 40th birthday party; both men's wives were seven months pregnant at the time

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832977Thu, 15 Oct 2026 08:00:02 +0000OBOMEDIA ENTERTAINMENTThe twin empty seats that arrived at his daughter's party An eighty-year-old man waits for two sons who boarded a small plane to fly to their sister's fortieth birthday party. Behind that afternoon lies a life that had already survived a cockpit...
An eighty-year-old man waits for two sons who boarded a small plane to fly to their sister's fortieth birthday party. Behind that afternoon lies a life that had already survived a cockpit shot down over Tobruk, a fence at Stalag Luft III, and the floor of the House of Commons — but nothing in eighty years had prepared him for what didn't arrive. What does a man do with a life this full when the people who gave it meaning are taken from him one by one?

In this episode, we trace Aidan Crawley's path from a record-breaking cricket career at Oxford and Lord's through wartime intelligence work, imprisonment, Parliament, and British television, asking how one man's extraordinary public life sat alongside private losses almost too heavy to name.

Person: Aidan Merivale Crawley
Location: Buckinghamshire and the skies over Tobruk, Silesia, and Britain
Date: summer 1988
Case: the small plane carrying his two sons that never landed
Status: both sons died; Crawley died in 1993, described as virtually penniless

- In the 1926 Eton v Harrow match at Lord's, an 18-year-old Crawley scored 87 runs, which Wisden called the best innings in the match for many years
- Shot down near Tobruk in July 1941, he was held at Stalag Luft III in Silesia and was inside the camp during the March 1944 mass escape, in which 50 of the 76 escapees were shot on Hitler's orders
- He won Buckingham for Labour in the 1945 election, serving as Under-Secretary of State for Air, later crossed to the Conservatives and won West Derbyshire in a 1962 by-election
- He became the first editor-in-chief of Independent Television News in 1955, introducing the American-style newscaster format to British screens
- In summer 1988, his sons Andrew (41) and Randall (38) died when their small plane failed to arrive at sister Harriet's 40th birthday party; both men's wives were seven months pregnant at the time

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>977falsefullhttps://www.spreaker.com/episode/the-ruptured-fuel-line-that-forced-him-down-and-lost-his-reconnaissance--74832973
The ruptured fuel line that forced him down and lost his reconnaissance

This episode explores the story of Frederick Joseph Rutland, a pioneering naval aviator whose early reconnaissance efforts and innovations in carrier aviation were unprecedented. It delves into the extraordinary events of his career and the mysterious circumstances that led to his later imprisonment without charge.

Person: Frederick Joseph Rutland
Date: May 30, 1916
Location: North Sea
Aircraft: Short Type 184
Event: Battle of Jutland

- Frederick Joseph Rutland joined the Royal Navy as a boy seaman at age fourteen in 1901.
- At Jutland, he conducted the first heavier-than-air aircraft reconnaissance of an enemy fleet during active battle.
- After his fuel line ruptured, Rutland repaired it himself in the North Sea and signaled he was ready to re-launch.
- The day after Jutland, Rutland went against orders to rescue a man who fell between two ships, earning him the Albert Medal in Gold.
- In 1917, Rutland performed the first successful aircraft launch from a flying-off platform mounted on a gun turret.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832973Wed, 14 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA naval aviator makes history with the first reconnaissance flight in a fleet engagement, but his reports never reach admirals. His country later locks him away. The ruptured fuel line that forced him down and lost his reconnaissance This...
The ruptured fuel line that forced him down and lost his reconnaissance

This episode explores the story of Frederick Joseph Rutland, a pioneering naval aviator whose early reconnaissance efforts and innovations in carrier aviation were unprecedented. It delves into the extraordinary events of his career and the mysterious circumstances that led to his later imprisonment without charge.

Person: Frederick Joseph Rutland
Date: May 30, 1916
Location: North Sea
Aircraft: Short Type 184
Event: Battle of Jutland

- Frederick Joseph Rutland joined the Royal Navy as a boy seaman at age fourteen in 1901.
- At Jutland, he conducted the first heavier-than-air aircraft reconnaissance of an enemy fleet during active battle.
- After his fuel line ruptured, Rutland repaired it himself in the North Sea and signaled he was ready to re-launch.
- The day after Jutland, Rutland went against orders to rescue a man who fell between two ships, earning him the Albert Medal in Gold.
- In 1917, Rutland performed the first successful aircraft launch from a flying-off platform mounted on a gun turret.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1055falsefullhttps://www.spreaker.com/episode/a-rain-dampened-stall-speed-rose-fast-enough-to-strangle-takeoff--74832970
A Rain-Dampened Stall Speed Rose Fast Enough to Strangle Takeoff

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832970Tue, 13 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA seven-year-old pilots a Cessna into a rain-soaked takeoff at Cheyenne-will the pilot’s plan survive worsening weather and rising stall speed? A Rain-Dampened Stall Speed Rose Fast Enough to Strangle Takeoff In this episode, we follow the...
A Rain-Dampened Stall Speed Rose Fast Enough to Strangle Takeoff

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>837falsefullhttps://www.spreaker.com/episode/the-flaps-stayed-up-the-clock-ran-out-before-they-could-stop-the-roll--74832968
The flaps stayed up - the clock ran out before they could stop the roll

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832968Mon, 12 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA heavily loaded MD‑82 lifts off Detroit with its flaps still retracted - the pilots have seconds to stop a roll. Who lives? The flaps stayed up - the clock ran out before they could stop the roll In this episode, we follow the final minutes...
The flaps stayed up - the clock ran out before they could stop the roll

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1129falsefullhttps://www.spreaker.com/episode/the-elt-sat-in-fairbanks-and-kept-rescuers-from-him--74832965
The ELT sat in Fairbanks and kept rescuers from him

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832965Sun, 11 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA congressman flies to a Juneau fundraiser - did rescuers miss them because the emergency transmitter wasn’t aboard? The ELT sat in Fairbanks and kept rescuers from him In this episode, we follow the October 16, 1972 flight from Anchorage toward...
The ELT sat in Fairbanks and kept rescuers from him

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>909falsefullhttps://www.spreaker.com/episode/the-forty-two-minute-delay-that-let-the-hijackers-strike-in-time--74832964
The forty‑two‑minute delay that let the hijackers strike in time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832964Sat, 10 Oct 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA Newark-San Francisco flight is hijacked midair with minutes to spare - did the passengers make it in time? The forty‑two‑minute delay that let the hijackers strike in time In this episode, we trace United Airlines Flight 93 from its delayed...
The forty‑two‑minute delay that let the hijackers strike in time

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832962Fri, 09 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Tu-154 closes on Omsk runway as two fuel trucks sit dark below and a 23-year-old ground controller sleeps - did they wake in time? The runway lights flickered on - did the sleeping controller wake in time? In this episode, we follow the...
The runway lights flickered on - did the sleeping controller wake in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1446falsefullhttps://www.spreaker.com/episode/the-500-hour-deadline-lapsed-did-2-000-extra-flight-hours-cost-them--74832960
The 500‑hour deadline lapsed - did 2,000 extra flight hours cost them?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832960Thu, 08 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Boeing 767 with a known thrust‑reverser fault flew past its safety deadline - can investigators piece together what happened six minutes after takeoff? The 500‑hour deadline lapsed - did 2,000 extra flight hours cost them? In this episode, the...
The 500‑hour deadline lapsed - did 2,000 extra flight hours cost them?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>871falsefullhttps://www.spreaker.com/episode/the-controller-s-severe-wind-shift-warning-came-six-minutes-too-late--74832959
The controller's "Severe wind shift" warning came six minutes too late

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832959Wed, 07 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Boeing 727 on final to JFK hears a controller warn of a "severe wind shift" six minutes before impact - what happens next? The controller's "Severe wind shift" warning came six minutes too late In this episode, we follow the final minutes of...
The controller's "Severe wind shift" warning came six minutes too late

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832958Tue, 06 Oct 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA thin dusting of snow coats a Fokker F28 wing as the APU fails and the left engine runs-did they make it in time to deice before takeoff? The dead auxiliary power unit kept the left engine running - did they make it? In this episode, we...
The dead auxiliary power unit kept the left engine running - did they make it?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>856falsefullhttps://www.spreaker.com/episode/the-port-engine-gauge-wavered-and-cost-the-team-their-takeoff-time--74832954
The port engine gauge wavered and cost the team their takeoff time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832954Mon, 05 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA British airliner pauses on a Munich runway as the port engine gauge wavers during takeoff-did the crew fix the engine problem in time? The port engine gauge wavered and cost the team their takeoff time In this episode, we follow the minutes...
The port engine gauge wavered and cost the team their takeoff time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1312falsefullhttps://www.spreaker.com/episode/the-wooden-planks-dropped-onto-the-peat-formed-a-raft-that-carried-survivors-out--74832952
The wooden planks dropped onto the peat formed a raft that carried survivors out

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832952Sun, 04 Oct 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA burned DC-4 lies in a Newfoundland bog at dawn; rescuers improvise a seaplane rescue - did they make it in time? The wooden planks dropped onto the peat formed a raft that carried survivors out In this episode, we follow the moments after a...
The wooden planks dropped onto the peat formed a raft that carried survivors out

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832950Sat, 03 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Turkish prime minister’s Vickers Viscount vanishes from radar three miles out during a routine instrument approach - did they make it in time? The three miles of final approach that swallowed their last two minutes In this episode, we...
The three miles of final approach that swallowed their last two minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1081falsefullhttps://www.spreaker.com/episode/the-midnight-coordinate-change-shifted-their-course-did-they-escape--74832946
The midnight coordinate change shifted their course - did they escape?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832946Fri, 02 Oct 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA sightseeing DC-10 over Antarctica had its flight plan silently changed overnight - did the crew make it in time? The midnight coordinate change shifted their course - did they escape? In this episode, we follow the flight from Auckland to...
The midnight coordinate change shifted their course - did they escape?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>959falsefullhttps://www.spreaker.com/episode/millibar-how-a-tiny-pressure-error-killed-98-at-ljubljana--74832943
Millibar: How a Tiny Pressure Error Killed 98 at Ljubljana

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832943Thu, 01 Oct 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Bristol Britannia descends toward Ljubljana on a clear night with two pressure settings in the cockpit - did a 43 millibar error doom the approach? Millibar: How a Tiny Pressure Error Killed 98 at Ljubljana In this episode we follow the final...
Millibar: How a Tiny Pressure Error Killed 98 at Ljubljana

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832941Wed, 30 Sep 2026 08:00:05 +0000OBOMEDIA ENTERTAINMENTA flight bound for Moroni circles at night over a black Indian Ocean as the altitude selector is set to zero feet - did they make it in time? The altitude selector set to zero feet - did they make it in time? In this episode, we follow the final...
The altitude selector set to zero feet - did they make it in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>793falsefullhttps://www.spreaker.com/episode/the-phrase-cleared-for-the-approach-let-them-descend-into-the-mountain--74832939
The phrase "Cleared for the approach" let them descend into the mountain

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832939Tue, 29 Sep 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA routine "Cleared for the approach" sends a Boeing 727 toward Mount Weather-did they make it in time? The phrase "Cleared for the approach" let them descend into the mountain In this episode, we lay out the flight, the crew, the weather, and...
The phrase "Cleared for the approach" let them descend into the mountain

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

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

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

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

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

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

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

- Runway 35L measured 1,940 meters with no runway-end safety area and a four-story warehouse and gas station beyond the far end.
- Resurfacing finished June 29 but the standard transverse grooves to channel water were not cut; Infraero said 30 more days were needed.
- Pilots had reported poor braking on July 16; one TAM stopped meters from the end and a Pantanal ATR hydroplaned and was written off.
- The A320 had one thrust reverser deactivated per a maintenance note but was released for flight and departed Porto Alegre at 17:17 BRT.
- The approach began at 18:48 BRT into wet conditions with 26 seconds between threshold crossing and the point the pilots would need to stop.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832938Mon, 28 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTAn A320 fights to stop on a short, ungrooved São Paulo runway in a downpour as the city looms; did they make it in time? The ungrooved runway sent the A320 hydroplaning - did they stop in time? In this episode, listeners follow the minutes and...
The ungrooved runway sent the A320 hydroplaning - did they stop in time?

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

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

- Runway 35L measured 1,940 meters with no runway-end safety area and a four-story warehouse and gas station beyond the far end.
- Resurfacing finished June 29 but the standard transverse grooves to channel water were not cut; Infraero said 30 more days were needed.
- Pilots had reported poor braking on July 16; one TAM stopped meters from the end and a Pantanal ATR hydroplaned and was written off.
- The A320 had one thrust reverser deactivated per a maintenance note but was released for flight and departed Porto Alegre at 17:17 BRT.
- The approach began at 18:48 BRT into wet conditions with 26 seconds between threshold crossing and the point the pilots would need to stop.

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832936Sun, 27 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Tupolev touches down at Vnukovo and one right main strut sends no compression signal-did the silent strut stop the reversers in time? The silent right strut stopped the reversers - did they stop in time? In this episode, we follow a...
The silent right strut stopped the reversers - did they stop in time?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832935Sat, 26 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA four-year-old clung to a flipped seat on Middlebelt Road - did the retracted slats cost them their seconds? The slats stayed retracted and stole their climb seconds In this episode, we follow the minutes from gate to impact as crew,...
The slats stayed retracted and stole their climb seconds

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1155falsefullhttps://www.spreaker.com/episode/the-disabled-runway-alarms-kept-warning-silent-did-they-make-it--74832931
The Disabled Runway Alarms Kept Warning Silent - Did They Make It?

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

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

- At 08:10 the tower received a radio call reporting position "S four," a taxiway designation that did not exist on the controller’s map.
- Linate was enveloped in dense fog with visibility around 100 meters while flights continued under low-visibility procedures.
- The ground radar decommissioned in November 1999 had not been replaced despite approval for a new system in 1995, leaving controllers blind on the ground for six years.
- The airport's runway incursion warning alarms were intentionally switched off because recurring false alerts from vehicles and animals made them a nuisance.
- Multiple authorities - the airport operator, the national air navigation service and the civil aviation directorate - shared responsibility for infrastructure decisions and budget handoffs leading up to that morning.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832931Fri, 25 Sep 2026 08:00:05 +0000OBOMEDIA ENTERTAINMENTA foggy October morning at Milan Linate: controllers are blind on the ground, runway alarms deliberately silenced - did they make it in time? The Disabled Runway Alarms Kept Warning Silent - Did They Make It? In this episode, we reconstruct the...
The Disabled Runway Alarms Kept Warning Silent - Did They Make It?

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

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

- At 08:10 the tower received a radio call reporting position "S four," a taxiway designation that did not exist on the controller’s map.
- Linate was enveloped in dense fog with visibility around 100 meters while flights continued under low-visibility procedures.
- The ground radar decommissioned in November 1999 had not been replaced despite approval for a new system in 1995, leaving controllers blind on the ground for six years.
- The airport's runway incursion warning alarms were intentionally switched off because recurring false alerts from vehicles and animals made them a nuisance.
- Multiple authorities - the airport operator, the national air navigation service and the civil aviation directorate - shared responsibility for infrastructure decisions and budget handoffs leading up to that morning.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>840falsefullhttps://www.spreaker.com/episode/the-pressure-setting-spoken-over-the-radio-pushed-them-below-safety-in-time--74832929
The pressure setting spoken over the radio pushed them below safety in time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832929Thu, 24 Sep 2026 08:00:06 +0000OBOMEDIA ENTERTAINMENTA trainee controller read the wrong pressure over radio, placing the jet low over Pico Alto - did they make it in time? The pressure setting spoken over the radio pushed them below safety in time In this episode, we lay out the sequence of...
The pressure setting spoken over the radio pushed them below safety in time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1023falsefullhttps://www.spreaker.com/episode/the-cargo-door-began-to-open-thirty-three-seconds-after-takeoff-enough-time--74832926
The cargo door began to open thirty‑three seconds after takeoff - enough time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832926Wed, 23 Sep 2026 08:00:05 +0000OBOMEDIA ENTERTAINMENTThirty-three seconds after takeoff a DC‑9’s cargo door began to peel open over Fort Worth - did they make it in time? The cargo door began to open thirty‑three seconds after takeoff - enough time? In this episode, we follow the minutes after a...
The cargo door began to open thirty‑three seconds after takeoff - enough time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>930falsefullhttps://www.spreaker.com/episode/a-ten-month-old-q400-stalled-its-landing-and-cost-fifty-lives--74832923
A ten‑month‑old Q400 stalled its landing and cost fifty lives

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832923Tue, 22 Sep 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA ten-month-old Q400 vanishes from radar five miles short of Buffalo. Did they make it in time? A ten‑month‑old Q400 stalled its landing and cost fifty lives In this episode we follow the flight from Newark to Buffalo and the fifty-nine minutes...
A ten‑month‑old Q400 stalled its landing and cost fifty lives

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>900falsefullhttps://www.spreaker.com/episode/the-word-emergency-never-came-and-the-fuel-ran-out-sixteen-miles-short--74832921
The word "emergency" never came - and the fuel ran out sixteen miles short

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832921Mon, 21 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Bogotá-New York Boeing 707 runs low on fuel and falls silent sixteen miles from Kennedy as controllers wait - did they declare an emergency in time? The word "emergency" never came - and the fuel ran out sixteen miles short In this episode, we...
The word "emergency" never came - and the fuel ran out sixteen miles short

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>998falsefullhttps://www.spreaker.com/episode/the-temperature-column-that-cut-nine-knots-and-stole-time--74832920
The temperature column that cut nine knots and stole time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832920Sun, 20 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Kansas City flight crew misreads a performance chart and sets takeoff speed nine knots too low - did they make it in time? The temperature column that cut nine knots and stole time In this episode, we follow the moments leading up to a...
The temperature column that cut nine knots and stole time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>758falsefullhttps://www.spreaker.com/episode/the-piper-s-missing-clearance-ran-into-the-dc-9-did-anyone-make-it-out--74832916
The Piper's missing clearance ran into the DC‑9 - did anyone make it out?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832916Sat, 19 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA small Piper without clearance crossed into LAX terminal airspace and struck a DC‑9 over Cerritos - did anyone make it in time? The Piper's missing clearance ran into the DC‑9 - did anyone make it out? In this episode, we follow the minutes...
The Piper's missing clearance ran into the DC‑9 - did anyone make it out?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832915Fri, 18 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Delta DC‑3 and a Vultee trainer converge over Muscogee County Airport-ten feet separates life from catastrophe, and no tower to stop it? The missing control tower left them ten feet to decide In this episode, we follow the flight that brought...
The missing control tower left them ten feet to decide

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>868falsefullhttps://www.spreaker.com/episode/the-last-end-play-check-missed-did-the-dry-jackscrew-run-out-of-minutes--74832911
The last end-play check missed-did the dry jackscrew run out of minutes?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832911Thu, 17 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA worn jackscrew and overdue checks leave an MD-83 climbing out of Puerto Vallarta - did the maintenance math run out? The last end-play check missed-did the dry jackscrew run out of minutes? In this episode, we follow the flight, the plane, and...
The last end-play check missed-did the dry jackscrew run out of minutes?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832907Wed, 16 Sep 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA commuter turboprop is overloaded and its elevator jammed-can the pilots overcome and make it to level flight? The turnbuckles jammed the elevator - did they make it to level flight? In this episode, we follow the moments before Air Midwest...
The turnbuckles jammed the elevator - did they make it to level flight?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832904Tue, 15 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA routine northbound flight faces a hidden crisis when an Acme nut controlling pitch has stripped most threads - did they land in time? The stripped Acme nut sheared at cruise speed - did they land in time? In this episode, we follow the final...
The stripped Acme nut sheared at cruise speed - did they land in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1232falsefullhttps://www.spreaker.com/episode/they-never-said-emergency-the-night-flight-052-ran-out-of-fuel--74832901
They Never Said "Emergency": The Night Flight 052 Ran Out of Fuel

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832901Mon, 14 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Boeing 707 circles over New York with engines and radios working but no one ever declares "emergency" - did they make it in time? They Never Said "Emergency": The Night Flight 052 Ran Out of Fuel In this episode, we follow the nine-hour flight...
They Never Said "Emergency": The Night Flight 052 Ran Out of Fuel

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>929falsefullhttps://www.spreaker.com/episode/the-eighteen-foot-roof-tore-away-did-anyone-reach-the-exit-in-time--74832899
The eighteen‑foot roof tore away - did anyone reach the exit in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832899Sun, 13 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA flight attendant walks the aisle when an eighteen‑foot section of fuselage peels away midflight - did anyone reach the exit in time? The eighteen‑foot roof tore away - did anyone reach the exit in time? In this episode, we follow the sequence...
The eighteen‑foot roof tore away - did anyone reach the exit in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>954falsefullhttps://www.spreaker.com/episode/the-radio-died-he-kept-broadcasting-the-pilot-s-location-and-burned-up--74832897
The radio died - he kept broadcasting the pilot's location and burned up

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832897Sat, 12 Sep 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA Skyraider pilot’s cockpit fills with smoke over karst limestone as he keeps broadcasting a downed F-4 pilot’s location - did they make it in time? The radio died - he kept broadcasting the pilot's location and burned up In this episode, we...
The radio died - he kept broadcasting the pilot's location and burned up

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1020falsefullhttps://www.spreaker.com/episode/the-single-word-they-never-spoke-ran-the-engines-dead--74832894
The single word they never spoke ran the engines dead

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832894Fri, 11 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Boeing 707 circles over New York with fuel running low while its crew never says the word that would trigger an emergency-did they make it in time? The single word they never spoke ran the engines dead In this episode, we follow the final...
The single word they never spoke ran the engines dead

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1033falsefullhttps://www.spreaker.com/episode/the-delayed-clearance-that-let-the-dc-9-meet-the-seawall--74832892
The delayed clearance that let the DC‑9 meet the seawall

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832892Thu, 10 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA DC‑9 on ILS into fog at Logan races a delayed clearance toward a seawall as instruments and cockpit silence conspire - did they make it in time? The delayed clearance that let the DC‑9 meet the seawall In this episode, we follow the final...
The delayed clearance that let the DC‑9 meet the seawall

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>989falsefullhttps://www.spreaker.com/episode/they-never-walked-away-the-big-bopper-s-final-100-feet--74832889
They Never Walked Away: The Big Bopper's Final 100 Feet

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832889Wed, 09 Sep 2026 08:00:02 +0000OBOMEDIA ENTERTAINMENTA grieving band faces a desperate flight from a freezing Iowa night when rock star The Big Bopper boards a small plane - did they make it in time? They Never Walked Away: The Big Bopper's Final 100 Feet In this episode, we trace the last hours...
They Never Walked Away: The Big Bopper's Final 100 Feet

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>889falsefullhttps://www.spreaker.com/episode/the-phone-calls-that-bought-eight-minutes-did-anyone-reach-safety--74832886
The Phone Calls That Bought Eight Minutes - Did Anyone Reach Safety?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832886Tue, 08 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA Boeing 767 is hijacked en route to California; frantic phone calls buy eight minutes as passengers try to reach safety-did anyone make it out? The Phone Calls That Bought Eight Minutes - Did Anyone Reach Safety? In this episode, we follow...
The Phone Calls That Bought Eight Minutes - Did Anyone Reach Safety?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1038falsefullhttps://www.spreaker.com/episode/the-0-05-mhz-readback-that-silenced-the-piper-did-they-make-it--74832883
The 0.05 MHz readback that silenced the Piper - did they make it?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832883Mon, 07 Sep 2026 08:00:04 +0000OBOMEDIA ENTERTAINMENTA pilot misreads a handoff and vanishes from the only voice channel over the Hudson River as another helicopter approaches - did they make it in time? The 0.05 MHz readback that silenced the Piper - did they make it? In this episode, we follow...
The 0.05 MHz readback that silenced the Piper - did they make it?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>896falsefullhttps://www.spreaker.com/episode/the-yellow-rotor-blade-flew-four-hundred-meters-could-they-stop-the-crash--74832881
The yellow rotor blade flew four hundred meters - could they stop the crash?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832881Sun, 06 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA yellow rotor blade flew 400 meters from the wreckage as a prototype Sikorsky S-61L broke apart over Compton - could they stop the crash? The yellow rotor blade flew four hundred meters - could they stop the crash? In this episode, we follow...
The yellow rotor blade flew four hundred meters - could they stop the crash?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>975falsefullhttps://www.spreaker.com/episode/the-darkened-navigational-beacons-hid-the-mountains-and-cost-them-their-lives--74832877
The darkened navigational beacons hid the mountains and cost them their lives

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832877Sat, 05 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTCarole Lombard boards a night flight from Las Vegas with navigational beacons switched off; the mountains ahead are invisible and time is running out. The darkened navigational beacons hid the mountains and cost them their lives In this episode,...
The darkened navigational beacons hid the mountains and cost them their lives

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

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

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

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

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

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

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

- Departed Ouagadougou at 01:15 local time en route to Algiers, scheduled arrival 05:10.
- Flight data recorder stopped transmitting at 01:47; the final 32 minutes became the focus of reconstruction.
- Maintenance history shows four interventions on EPR/autothrottle systems within 13 months, plus an engine replacement after a June rejected takeoff.
- The cockpit voice recorder’s magnetic tracks were unreadable, leaving crew dialogue and warnings undocumented.
- The autothrottle relied on EPR transmitters that had been replaced or repaired multiple times before this night flight.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832875Fri, 04 Sep 2026 08:00:03 +0000OBOMEDIA ENTERTAINMENTA night flight over the Sahara loses its autothrottle signals and the cockpit falls silent - did they land in time? The EPR reading that fooled the autothrottle - did they land in time? In this episode, we follow the final thirty-two minutes of...
The EPR reading that fooled the autothrottle - did they land in time?

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

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

- Departed Ouagadougou at 01:15 local time en route to Algiers, scheduled arrival 05:10.
- Flight data recorder stopped transmitting at 01:47; the final 32 minutes became the focus of reconstruction.
- Maintenance history shows four interventions on EPR/autothrottle systems within 13 months, plus an engine replacement after a June rejected takeoff.
- The cockpit voice recorder’s magnetic tracks were unreadable, leaving crew dialogue and warnings undocumented.
- The autothrottle relied on EPR transmitters that had been replaced or repaired multiple times before this night flight.

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>967falsefullhttps://www.spreaker.com/episode/the-chart-that-showed-forty-five-feet-forced-the-plane-to-hit-the-wires--74832871
The chart that showed forty‑five feet forced the plane to hit the wires

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>832falsefullhttps://www.spreaker.com/episode/the-radar-scale-maxed-out-and-they-had-five-minutes-to-live--74832868
The radar scale maxed out - and they had five minutes to live

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832868Wed, 02 Sep 2026 21:44:58 +0000OBOMEDIA ENTERTAINMENTA NOAA Hurricane Hunter plane dives toward the ocean into Hurricane Hugo with the radar scale maxed out and only five minutes to read what’s inside. The radar scale maxed out - and they had five minutes to live In this episode, we follow a NOAA...
The radar scale maxed out - and they had five minutes to live

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>942falsefullhttps://www.spreaker.com/episode/the-empty-flight-recorder-box-that-erased-whether-they-made-it-in-time--74832866
The empty flight‑recorder box that erased whether they made it in time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832866Wed, 02 Sep 2026 21:44:54 +0000OBOMEDIA ENTERTAINMENTA United flight over Lake Michigan suddenly dives and the flight recorder is missing-did the crew realize what was happening? The empty flight‑recorder box that erased whether they made it in time In this episode we lay out the sequence of...
The empty flight‑recorder box that erased whether they made it in time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>937falsefullhttps://www.spreaker.com/episode/the-blizzard-that-grounded-search-helicopters-and-cost-four-days-to-reach-them--74832864
The blizzard that grounded search helicopters-and cost four days to reach them

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832864Wed, 02 Sep 2026 21:44:50 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 vanishes in a February blizzard east of Kabul as helicopters turn back-did rescuers reach the wreckage in time? The blizzard that grounded search helicopters-and cost four days to reach them In this episode, we narrate the...
The blizzard that grounded search helicopters-and cost four days to reach them

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>855falsefullhttps://www.spreaker.com/episode/the-three-handed-altimeter-misread-cost-them-ten-thousand-feet-and-nine-lives--74832861
The three‑handed altimeter misread cost them ten thousand feet and nine lives

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832861Wed, 02 Sep 2026 21:44:46 +0000OBOMEDIA ENTERTAINMENTA test flight crew trusts a three‑handed altimeter as dense fog hides the ground - did their instrument misread cost them ten thousand feet? The three‑handed altimeter misread cost them ten thousand feet and nine lives In this episode, we follow...
The three‑handed altimeter misread cost them ten thousand feet and nine lives

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>841falsefullhttps://www.spreaker.com/episode/the-failed-right-engine-turbine-blades-bled-thrust-and-left-them-two-miles-short--74832859
The failed right-engine turbine blades bled thrust and left them two miles short

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832859Wed, 02 Sep 2026 21:44:42 +0000OBOMEDIA ENTERTAINMENTA right-engine turbine bled thrust after takeoff from Honolulu, leaving two pilots racing back to the runway. Did they make it in time? The failed right-engine turbine blades bled thrust and left them two miles short In this episode, we follow...
The failed right-engine turbine blades bled thrust and left them two miles short

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832857Wed, 02 Sep 2026 21:44:38 +0000OBOMEDIA ENTERTAINMENTA dark landing-gear light strands a fully fueled DC‑8 over Portland as crew debate fuel levels - did they make it back before the tanks ran dry? The dark landing-gear light that hid how fast fuel leaked In this episode, we follow United Airlines...
The dark landing-gear light that hid how fast fuel leaked

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832853Wed, 02 Sep 2026 21:44:34 +0000OBOMEDIA ENTERTAINMENTA captain with far too few jet hours pilots a Boeing 737 toward Cuenca in fog, one mile short of Mariscal Lamar - did they make it in time? The one missed seat that cost them one mile from the runway In this episode, we follow the flight, the...
The one missed seat that cost them one mile from the runway

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>839falsefullhttps://www.spreaker.com/episode/the-wing-frost-that-formed-on-the-ramp-did-they-deice-in-time--74832851
The wing frost that formed on the ramp - did they deice in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832851Wed, 02 Sep 2026 21:44:30 +0000OBOMEDIA ENTERTAINMENTA frost‑sensitive DC‑9 sits engines‑running on a snowy Cleveland ramp as two pilots prepare to take off - did they deice in time? The wing frost that formed on the ramp - did they deice in time? In this episode, we follow the events and...
The wing frost that formed on the ramp - did they deice in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>935falsefullhttps://www.spreaker.com/episode/the-flagpole-sheared-the-wing-and-left-them-four-thousand-feet-short--74832848
The flagpole sheared the wing and left them four thousand feet short

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832848Wed, 02 Sep 2026 21:44:26 +0000OBOMEDIA ENTERTAINMENTA flagpole shears a wing at night over Minneapolis as Northwest Orient Flight 307 struggles toward Runway 35 - did they make it in time? The flagpole sheared the wing and left them four thousand feet short In this episode, we follow the flight,...
The flagpole sheared the wing and left them four thousand feet short

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832845Wed, 02 Sep 2026 21:44:22 +0000OBOMEDIA ENTERTAINMENTA pulsing strobe appears in the fog by the runway as a Convair descends - did they make it to the runway in time? The strobe beacon lit off-course - would they reach the runway? In this episode, we follow the final minutes of Linjeflyg Flight...
The strobe beacon lit off-course - would they reach the runway?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832843Wed, 02 Sep 2026 21:44:18 +0000OBOMEDIA ENTERTAINMENTA cracked solder joint tripped an amber rudder limiter warning on an Airbus over the Java Sea - did they fix it in time? The cracked solder joint flashed amber - did they fix it in time? In this episode, we follow a routine flight that departed...
The cracked solder joint flashed amber - did they fix it in time?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832840Wed, 02 Sep 2026 21:44:14 +0000OBOMEDIA ENTERTAINMENTA ferry flight over the North Atlantic reports fuel critical and imminent ditching - did they make it in time? The fuel gauge warned of ditching - did they make it in time? In this episode, we follow the last hours of OB-1303, a Boeing 727 ferry...
The fuel gauge warned of ditching - did they make it in time?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832838Wed, 02 Sep 2026 21:44:10 +0000OBOMEDIA ENTERTAINMENTA regional jet lines up on an unlit runway that is 243 feet too short for takeoff - did the pilots recognize the danger in time? (aviation) The unlit runway fooled them - did they stop in time? In this episode, we follow the morning of August...
The unlit runway fooled them - did they stop in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>870falsefullhttps://www.spreaker.com/episode/the-c-46-climbed-into-darkness-and-missed-the-qingdao-approach-in-fog--74832835
The C‑46 climbed into darkness and missed the Qingdao approach in fog

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832835Wed, 02 Sep 2026 21:44:06 +0000OBOMEDIA ENTERTAINMENTA Curtiss C-46 climbs into dense fog off Shanghai bound for Qingdao - did they make the approach in time? The C‑46 climbed into darkness and missed the Qingdao approach in fog In this episode, we follow the flight that left Longhua Airport at...
The C‑46 climbed into darkness and missed the Qingdao approach in fog

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>918falsefullhttps://www.spreaker.com/episode/the-captain-s-relentless-insults-froze-the-co-pilot-and-lost-them-minutes--74832832
The captain's relentless insults froze the co‑pilot and lost them minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832832Wed, 02 Sep 2026 21:44:02 +0000OBOMEDIA ENTERTAINMENTA captain's insults silence his co‑pilot during an Islamabad approach as a charted hill fills the windscreen - did they make it in time? The captain's relentless insults froze the co‑pilot and lost them minutes In this episode, we follow the...
The captain's relentless insults froze the co‑pilot and lost them minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>983falsefullhttps://www.spreaker.com/episode/the-off-duty-pilot-grabbed-the-controls-as-the-wind-shifted-did-they-lift--74832831
The off‑duty pilot grabbed the controls as the wind shifted - did they lift?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832831Wed, 02 Sep 2026 21:43:59 +0000OBOMEDIA ENTERTAINMENTAn off‑duty pilot with simulator hours-listed as a passenger-takes the controls during takeoff at Durango as the wind shifts; did they lift? The off‑duty pilot grabbed the controls as the wind shifted - did they lift? In this episode, we present...
The off‑duty pilot grabbed the controls as the wind shifted - did they lift?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1027falsefullhttps://www.spreaker.com/episode/the-rear-pressure-bulkhead-detonated-and-stole-the-crew-s-last-twelve-minutes--74832829
The rear pressure bulkhead detonated and stole the crew's last twelve minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832829Wed, 02 Sep 2026 21:43:54 +0000OBOMEDIA ENTERTAINMENTA routine flight from Haneda becomes a race when a repaired bulkhead may blow apart the plane-did they make it in time? The rear pressure bulkhead detonated and stole the crew's last twelve minutes In this episode, we follow Japan Airlines...
The rear pressure bulkhead detonated and stole the crew's last twelve minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1306falsefullhttps://www.spreaker.com/episode/the-travel-rule-that-kept-his-assistants-home-and-who-made-the-flight--74832828
The travel rule that kept his assistants home - and who made the flight?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832828Wed, 02 Sep 2026 21:43:52 +0000OBOMEDIA ENTERTAINMENTA head coach boards a charter from a small Indiana airport because his travel rule forces practice on the opponent’s court - did they make it in time? The travel rule that kept his assistants home - and who made the flight? In this episode, we...
The travel rule that kept his assistants home - and who made the flight?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>847falsefullhttps://www.spreaker.com/episode/the-de-icer-flowed-at-18-fouled-the-engines-and-cost-them-minutes--74832826
The de-icer flowed at 18% - fouled the engines and cost them minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832826Wed, 02 Sep 2026 21:43:48 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 at a snowy Seattle gate with de-icer flowing-minutes tick toward a doomed takeoff: did they make it in time? The de-icer flowed at 18% - fouled the engines and cost them minutes In this episode, we lay out the hour before Air...
The de-icer flowed at 18% - fouled the engines and cost them minutes

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1302falsefullhttps://www.spreaker.com/episode/the-jackscrew-s-last-threads-stripped-as-fuel-ran-low-did-they-land--74832823
The jackscrew's last threads stripped as fuel ran low-did they land?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832823Wed, 02 Sep 2026 21:43:42 +0000OBOMEDIA ENTERTAINMENTA worn jackscrew in an MD-83 stripped almost all its threads midflight above the Pacific as fuel ran low-did they land in time? The jackscrew's last threads stripped as fuel ran low-did they land? In this episode, we follow the timeline from...
The jackscrew's last threads stripped as fuel ran low-did they land?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832820Wed, 02 Sep 2026 21:43:38 +0000OBOMEDIA ENTERTAINMENTA twin‑engine Cessna climbs beyond its ceiling with a college football coach aboard - did they make it in time? The Cessna climbed past its ceiling and burned its fuel-clock dry In this episode, you’ll hear the known facts of a routine...
The Cessna climbed past its ceiling and burned its fuel-clock dry

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>886falsefullhttps://www.spreaker.com/episode/the-mode-c-transponder-missing-the-piper-and-the-playground-that-waited--74832816
The Mode C transponder missing the Piper - and the playground that waited

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832816Wed, 02 Sep 2026 21:43:34 +0000OBOMEDIA ENTERTAINMENTA private Piper without a Mode C transponder climbs toward LA airspace while an Aeromexico DC-9 descends-did anyone see the altitude in time? The Mode C transponder missing the Piper - and the playground that waited In this episode, we present...
The Mode C transponder missing the Piper - and the playground that waited

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>911falsefullhttps://www.spreaker.com/episode/the-helicopter-that-climbed-for-a-gear-check-collided-before-they-could-land--74832814
The helicopter that climbed for a gear check collided before they could land

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832814Wed, 02 Sep 2026 21:43:30 +0000OBOMEDIA ENTERTAINMENTA helicopter climbs close to check a Piper Aerostar's balky landing gear over a schoolyard - did they make it in time? The helicopter that climbed for a gear check collided before they could land In this episode, we lay out the sequence of...
The helicopter that climbed for a gear check collided before they could land

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832812Wed, 02 Sep 2026 21:43:26 +0000OBOMEDIA ENTERTAINMENTA seasoned TriStar on final approach into a storm at Dallas/Fort Worth encounters an invisible explosive downdraft - did they make it in time? The microburst struck the approach - did they make it? In this episode, we follow Flight 191’s final...
The microburst struck the approach - did they make it?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832810Wed, 02 Sep 2026 21:43:22 +0000OBOMEDIA ENTERTAINMENTA DC‑10 with a hidden maintenance crack taxis at O'Hare for takeoff with 273 souls aboard - did they make it off the runway? The forklift shifted and cracked the pylon - did they make it off the runway? In this episode, we follow the chain of...
The forklift shifted and cracked the pylon - did they make it off the runway?

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832809Wed, 02 Sep 2026 21:43:18 +0000OBOMEDIA ENTERTAINMENTA United crew battles a turbulent approach as a Boeing 737 rolls hard - did their go‑around command reach the flaps in time? The flaps command that started the go‑around - did they make it? In this episode, we follow the final minutes of United...
The flaps command that started the go‑around - did they make it?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>993falsefullhttps://www.spreaker.com/episode/the-cloud-top-upslope-erased-a-thousand-feet-did-they-get-out--74832805
The cloud‑top upslope erased a thousand feet - did they get out?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832805Wed, 02 Sep 2026 21:43:14 +0000OBOMEDIA ENTERTAINMENTA thousand feet of mandated separation vanishes when a rising cloud-top makes a Boeing look level with a Constellation - did they make it out in time? The cloud‑top upslope erased a thousand feet - did they get out? In this episode, we follow...
The cloud‑top upslope erased a thousand feet - did they get out?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1323falsefullhttps://www.spreaker.com/episode/the-thirty-five-thousand-foot-altitude-put-them-on-a-collision-clock--74832802
The thirty‑five‑thousand‑foot altitude put them on a collision clock

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832802Wed, 02 Sep 2026 21:43:10 +0000OBOMEDIA ENTERTAINMENTA humanitarian C-141 and a German Tu-154 converged at 35,000 ft over the South Atlantic with no traffic warnings-did anyone make it in time? The thirty‑five‑thousand‑foot altitude put them on a collision clock In this episode, we lay out the...
The thirty‑five‑thousand‑foot altitude put them on a collision clock

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>962falsefullhttps://www.spreaker.com/episode/the-ninety-degree-shaft-step-in-engine-two-fractured-before-they-reached-runway--74832801
The ninety‑degree shaft step in engine two fractured before they reached runway

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832801Wed, 02 Sep 2026 21:43:06 +0000OBOMEDIA ENTERTAINMENTA Transatlantic Il‑62 is seconds from the runway with landing gear down when a hidden engine defect fractures-did they make it in time? The ninety‑degree shaft step in engine two fractured before they reached runway In this episode we lay out...
The ninety‑degree shaft step in engine two fractured before they reached runway

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832798Wed, 02 Sep 2026 21:43:02 +0000OBOMEDIA ENTERTAINMENTA seasoned Pan Am crew climbs out of New Orleans into gusty skies unaware a wind shear bulletin never reached them - did they make it in time? The weather bulletin that never reached them: did they climb out in time? In this episode, we follow...
The weather bulletin that never reached them: did they climb out in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>888falsefullhttps://www.spreaker.com/episode/the-two-percent-ice-ridge-broke-the-atr-s-lift-did-they-make-it--74832797
The two-percent ice ridge broke the ATR's lift - did they make it?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832797Wed, 02 Sep 2026 21:42:58 +0000OBOMEDIA ENTERTAINMENTAn ATR on approach to Indiana accumulates unexpected ice-can the crew regain control before the stall takes them? The two-percent ice ridge broke the ATR's lift - did they make it? In this episode, we follow the last fifteen critical seconds...
The two-percent ice ridge broke the ATR's lift - did they make it?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1350falsefullhttps://www.spreaker.com/episode/when-sky-turned-silent-the-dual-engine-disaster-over-georgia--74832794
When Sky Turned Silent: The Dual-Engine Disaster Over Georgia

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832794Wed, 02 Sep 2026 21:42:54 +0000OBOMEDIA ENTERTAINMENTA seasoned DC-9 crew flies toward a radar corridor over Georgia and, trusting the storm radar, suddenly lose both engines - did they make it in time? When Sky Turned Silent: The Dual-Engine Disaster Over Georgia In this episode, we lay out the...
When Sky Turned Silent: The Dual-Engine Disaster Over Georgia

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>919falsefullhttps://www.spreaker.com/episode/the-refusal-of-ils-at-22-28-doomed-their-descent-on-mount-somma--74832792
The refusal of ILS at 22:28 doomed their descent on Mount Somma

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832792Wed, 02 Sep 2026 21:42:52 +0000OBOMEDIA ENTERTAINMENTA veteran captain refuses the ILS as his Viscount descends toward Naples at night; can visual confidence beat the unseen ridge of Mount Somma? The refusal of ILS at 22:28 doomed their descent on Mount Somma In this episode, we follow Alitalia...
The refusal of ILS at 22:28 doomed their descent on Mount Somma

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>1029falsefullhttps://www.spreaker.com/episode/they-had-eight-seconds-why-the-737-s-rudder-turned-against-its-pilots--74832790
They Had Eight Seconds: Why the 737's Rudder Turned Against Its Pilots

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832790Wed, 02 Sep 2026 21:42:45 +0000OBOMEDIA ENTERTAINMENTA United Airlines 737 on final approach to Colorado Springs suddenly rolls hard right and crashes in eight seconds - did the rudder betray its pilots? They Had Eight Seconds: Why the 737's Rudder Turned Against Its Pilots In this episode, we...
They Had Eight Seconds: Why the 737's Rudder Turned Against Its Pilots

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>897falsefullhttps://www.spreaker.com/episode/the-twenty-one-degree-turn-that-outpaced-their-descent-time--74832786
The twenty‑one‑degree turn that outpaced their descent time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832786Wed, 02 Sep 2026 21:42:41 +0000OBOMEDIA ENTERTAINMENTA routine regional flight over West Java turns twenty-one degrees off course into worsening weather-did the crew see the mountain in time? The twenty‑one‑degree turn that outpaced their descent time In this episode, we follow the final sixteen...
The twenty‑one‑degree turn that outpaced their descent time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>729falsefullhttps://www.spreaker.com/episode/the-ils-course-correction-that-drew-them-below-the-runway-just-before-midnight--74832785
The ILS course correction that drew them below the runway just before midnight

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832785Wed, 02 Sep 2026 21:42:38 +0000OBOMEDIA ENTERTAINMENTA turboprop drifts off the ILS on a foggy Maine night; can the crew correct course and make the runway before they sink into the trees? The ILS course correction that drew them below the runway just before midnight In this episode, we follow...
The ILS course correction that drew them below the runway just before midnight

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>861falsefullhttps://www.spreaker.com/episode/concrete-death-how-muan-s-barrier-turned-a-bird-strike-fatal--74832783
Concrete Death: How Muan's Barrier Turned a Bird Strike Fatal

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832783Wed, 02 Sep 2026 21:42:34 +0000OBOMEDIA ENTERTAINMENTA Boeing 737 approaches Muan International amid known bird strike risk and a concrete barrier too close to the runway - did they make it in time? Concrete Death: How Muan's Barrier Turned a Bird Strike Fatal In this episode, we lay out the...
Concrete Death: How Muan's Barrier Turned a Bird Strike Fatal

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832780Wed, 02 Sep 2026 21:42:30 +0000OBOMEDIA ENTERTAINMENTA United Airlines Boeing 737 approaches Midway with a failed flight recorder and 45 lives at stake - did they make it in time? The broken flight recorder cost them the final seconds to save 45 lives In this episode, we follow the routine...
The broken flight recorder cost them the final seconds to save 45 lives

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

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

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

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

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

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832779Wed, 02 Sep 2026 21:42:26 +0000OBOMEDIA ENTERTAINMENTA captain hesitates at Pokhara with TAWS inhibited and clouds closing on the Kali Gandaki gorge - did they make it to Jomsom in time? The TAWS switch silenced the cockpit and cost them the runway-time In this episode, we follow Tara Air Flight...
The TAWS switch silenced the cockpit and cost them the runway-time

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>924falsefullhttps://www.spreaker.com/episode/the-throttle-coupling-slipped-the-left-engine-surged-did-they-stop-in-time--74832778
The throttle coupling slipped, the left engine surged - did they stop in time?

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

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

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

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

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.]]>https://api.spreaker.com/episode/74832778Wed, 02 Sep 2026 21:42:22 +0000OBOMEDIA ENTERTAINMENTA landing at Irkutsk goes from routine to critical when a worn throttle coupling lets the left engine surge - did they stop in time? The throttle coupling slipped, the left engine surged - did they stop in time? In this episode, we follow the...
The throttle coupling slipped, the left engine surged - did they stop in time?

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

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

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

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

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