Explore every episode of the podcast Air Disasters - The Black Box Files

A celebrated Dutch airliner flies a Christmas mailload into a storm over the desert; did the crew make it to Baghdad in time?

The Christmas mailload jammed the Uiver's controls and cost them the runway

In this episode, we follow the Uiver’s final hours between Cairo and Baghdad: a high-profile KLM Christmas mail flight crewed by experienced pilots and pressured by management, into unexpectedly severe weather. What decisions were made on board and by the airline as the situation deteriorated?

Person: Captain Wim Beekman
Person: Jan van Steenbergen
Event: Christmas mail flight from Amsterdam to Batavia
Date: 22 December 1934 (last contact 21-22 December)
Location: Desert south of Rutbah Wells, Iraq

- The Uiver was a newly famous KLM Douglas DC-2 carrying 5,225 Christmas cards and high-profile passengers.
- Captain Beekman had 40 hours on the Uiver and had previously reported loss-of-control in heavy weather; he initially refused the flight.
- A suppressed 1935 report says KLM ordered Beekman to fly the leg under threat of dismissal.
- The crew included a co-pilot with only 10 hours on the Uiver, a chief engineer, and a telegraphist who was a prior crash survivor.
- The Uiver departed Cairo for Baghdad into “very bad” weather and made final radio contact just after midnight.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC‑9 carrying a college football team begins descending into ragged weather without a glide slope - did they make it to the runway in time?

The glide-slope absence that left descent on a clock

In this episode, we reconstruct the final hours before Southern Airways Flight 932's approach to Tri‑State Airport and the decisions, equipment limits, and timing that shaped the descent. The narrative follows the crew, the charter logistics, and the narrow window of cockpit audio that leaves the central question unresolved: why did the aircraft keep descending?

Date: November 14, 1970
Aircraft: Southern Airways DC‑9‑30, N97S
Person: Captain Frank Abbott; First Officer Jerry Smith
Event: Crash during approach to Tri‑State Airport
Topic: Missing glide slope and incomplete cockpit voice recording

- The charter carried 75 people: 37 players, 5 coaches, 7 staff, 21 supporters, and local officials on a single return flight.
- The aircraft lacked a glide slope at Tri‑State; controllers reported rain, fog, smoke, and a ragged ceiling during approach.
- The cockpit voice recorder preserved only 30 seconds of audio between a routine approach call and silence.
- Two Marshall staffers survived by not boarding: one had driven away, another gave up his seat to make a recruiting stop where they learned the news on a transistor radio.
- The charter was renegotiated beforehand to meet weight limits after an initial proposal exceeded allowable takeoff weight.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC‑9 descends into dense fog at Prague with both radio compass needles set to the same beacon-did they correct course before impact?

The radio compass needles both pointed at PR - did they turn in time?

In this episode, we lay out the final minutes of Inex-Adria Flight JP 450 as it approached Prague Ruzyně in heavy fog and with key landing systems down. You’ll hear what instruments, procedures, and decisions shaped the crew’s approach-and why critical records remain sealed-raising the question: what happened in the cockpit before impact?

Person: Commander Miodrag Marović and First Officer Rade Popov
Date: October 30, 1975
Aircraft: Douglas DC‑9 series 32, registration YU‑AJO
Location: Prague Ruzyně approach, fog over Runway 25
Event: Both radio compass needles set to PR while ILS and PAR were inoperative

- The altimeter recovered from the wreckage was set correctly to 981 hPa, indicating the instrument worked.
- Two critical approach aids, the Instrument Landing System and Precision Approach Radar, were both inoperative that morning.
- Standard procedure required radio compass needles on two beacons (PR and L); both needles were found set to PR.
- The crew requested a holding pattern after learning the systems were down, then elected to continue the approach.
- Flight path reconstruction shows the DC‑9 missed the required right turn and drifted 1.3 km south of the runway centerline before descent.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC-3 approaches Mariehamn in thick November fog with an instrument landing system sitting unused in a warehouse-did they reach the runway in time?

The landing system sat in a warehouse - did they reach the runway in time?

In this episode, we follow a short domestic flight from Turku to Mariehamn on 8 November 1963 and the immediate aftermath of a crash in dense fog. The episode traces the decisions, equipment gaps, and on-board people that shaped the final minutes and asks what went wrong during that descent.

Date: 8 November 1963
Flight: Aero O/Y Flight 217
Aircraft: Douglas DC-3
Location: Mariehamn, Åland Islands, Finland
Survivors: 3

- The DC-3 departed Turku after a short scheduled leg, carrying 25 aboard and 789 kg of freight, with tanks holding 1,100 liters of fuel.
- Visibility at Turku was at Aero O/Y planning minimums and slightly worse at Mariehamn; the crew continued with Stockholm Arlanda listed as the alternate.
- The airport lacked an installed instrument landing system that had been purchased two years earlier but remained in a warehouse due to a land dispute.
- The crew had the MAR beacon and Locator S for lateral guidance and were aligned on the runway centerline when they crossed the coastline at about 2,000 feet.
- The aircraft struck trees 1,480 meters before the runway threshold, impacting trees about 18 meters tall, inverted and burning within seconds, with no distress call transmitted.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Twin Otter on a routine coastal hop into Namsos loses thirty-one meters of clearance as instruments read green - did they make it in time?

Thirty-One Meters: Why Widerøe Flight 744 Vanished Below the Radar

In this episode, we walk through the final hour before Widerøe Flight 744 struck terrain, piecing together cockpit voice recorder excerpts, crew actions, and operational details to understand the build-up to impact. What decisions, small errors, and conditions combined in those last ninety seconds?

Date: 27 October 1993
Flight: Widerøe Flight 744 (Twin Otter LN-BNM)
Location: Namsos approach, Norway
Passengers: 17
Survivors: 13 injured; 6 fatalities

- Both pilots were experienced on the route: Captain Jan Bjørstad had landed at Namsos 13 times in the prior year; First Officer Trond Hamre had 27 recent Namsos landings.
- The aircraft, LN-BNM, had 40,453 flight hours and maintenance records showed no discrepancies; engines and instruments reported normal before impact.
- A ground handler miscalculated center-of-gravity; the captain checked and recalculated by hand and accepted passenger seating without moving anyone.
- The crew turned onto base leg earlier than planned, placing the aircraft 14 nautical miles out instead of the expected position and compressing time and altitude margins.
- The cockpit voice recorder captured the last ninety seconds almost verbatim, but obtaining it from the airline took nearly two years and three court rulings.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A pilot cleared to back‑taxi moves toward a different runway at St. Louis after an automated weather loop omitted one runway-did they make it in time?

The automated weather loop omitted one runway and turned night into a countdown

In this episode, the story follows an MD-82 and a Cessna crossing paths at Lambert Airport on the night of November 22, 1994, after an automated weather broadcast left out a runway and a required readback was never made. The episode traces radio calls, crew experience, and how expectation shaped what pilots heard-could the silence be the clue that matters?

Date: November 22, 1994
Location: St. Louis Lambert International Airport
Aircraft (1): McDonnell Douglas MD-82, N954U
Aircraft (2): Cessna 441 Conquest II, N441KM
Flight crew (MD-82): Captain Rick Carr (57), First Officer Randy Speed (38)
System failure: Automated Terminal Information Service omitted Runway 31

- ATIS loop listed only Runways 30L and 30R; Runway 31 was omitted from the automated weather broadcast.
- Ground control cleared the Cessna to back-taxi and hold on Runway 31 and the controller spoke the number aloud.
- The Cessna pilot did not read back "thirty-one"; the controller did not catch the missing readback and issued no correction.
- The Cessna had landed earlier that evening on Runway 30R and the crew’s recent experience likely shaped their taxi expectations.
- The NTSB identified preconception-expectation-driven perception-as a mechanism that may explain how the crew moved toward the wrong runway.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A commercial jet lands at Tegucigalpa-did the crew make it off the pavement before traffic and the valley caught up?

The ungrooved runway sent the jet onto the road - did they make it?

In this episode, we walk through the landing at Toncontín where a TACA Airbus A320 ran out of runway, struck vehicles and broke apart amid documented runway deficiencies and pilot decisions. What choices and failures in the final 300 meters set the stage for disaster?

Date: 30 May 2008
Location: Toncontín International Airport, Tegucigalpa, Honduras
Aircraft: Airbus A320, registration EI-TAF
People: 135 on board (124 passengers, 11 crew); notable passengers named in record
Condition: Runway ungrooved, friction not measured in five years; light rain and tailwind

- The runway sits inside a mountain-cut valley with a steep, curved final approach and public roads at both ends.
- Pilots had filed braking and wet-season complaints about the surface since 2003; friction measurements were not taken.
- A repaving contract from 2003 was not completed, and inspectors found structural deficiencies affecting ~30% of runway area.
- The crew was told an alternate airport was available with fuel calculated for diversion, but they elected to land.
- Captain D'Antonio (40, 11,899 flight hours, 52 prior Toncontín landings) flew the approach in low ceilings and light rain.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A controller told them "final approach path is clear" as an ATR-72 descended over the Zagros - did they make it in time?

The controller's "final approach path is clear" bought them seconds

In this episode, we follow the flight, the crew, and the decisions that led an ATR-72 to descend below safe altitude toward the Zagros Mountains. We lay out the weather, the cockpit dynamics, and the sequence of actions that pulled the aircraft closer to terrain - could a single radio call have steered the course?

Date: 18 February 2018
Aircraft: ATR 72-212, registration EP-ATS
Route: Tehran (Mehrabad) to Yasuj
Crew: Captain Hojatollah Foolad (17,000+ hrs); First Officer Kaveh Khalili (~1,800 hrs)
Weather: Ceiling 9,000 ft (minimum required 11,000 ft); cumulonimbus, thunderstorm risk

- Departure crossed company minima: flight dispatched despite METARs and forecast below required ceiling.
- Controller at Yasuj tower radioed "the final approach path was clear" at 05:49 UTC, which the crew accepted.
- Aircraft descended from 16,975 ft into the Zagros and was 500 ft below the minimum safe altitude for the corridor.
- Ground proximity alarm activated and sounded continuously in the final moments recorded by the flight data recorder.
- Investigators reaching the remote crash site on foot recovered data showing a chain of plausible decisions and cockpit dynamics rather than a single catastrophic mechanical failure.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC‑9 skims Boston outer marker in dense fog with seconds to spare - did the crew bring it back on glideslope before it was too late?

The Outer Marker Crossed High That Left One Runway and Seconds to Spare

In this episode, we follow Delta Air Lines Flight 723’s final approach into Boston Logan on July 31, 1973, reconstructing the sequence of decisions, timing pressures, and shifting weather that led to the aircraft crossing the outer marker improperly. What choices and distractions stacked in those last minutes, and could the crew still correct course in time?

Date: July 31, 1973
Aircraft: DC‑9‑31 (N975NE)
Flight: Delta Air Lines Flight 723
Location: Boston Logan International Airport (approach over Boston Harbor)
Weather: Fog, ceiling 400 ft, visibility 0.5 mile, variable RVR

- The flight departed Burlington, Vermont, route included stops at Manchester, then inbound to Boston on a routine northeast corridor hop.
- Captain John N. Streil (49) had 14,840 total hours and 1,457 on the DC‑9; First Officer Sidney W. Burrill (31) had 6,994 hours with 217 on type.
- Clearance for the approach was delayed by just over one minute while ATC handled a traffic conflict, leaving the crew waiting during a critical phase.
- The aircraft crossed the outer marker already above the glideslope and faster than stabilized approach criteria required, with changing runway visual range between 1,400 and 6,000 feet.
- At decision height the crew failed to make the required visual/no‑visual choice as multiple small errors and distractions accumulated.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Boeing 737 begins its Buenos Aires takeoff with flaps never extended - can the crew stop disaster as runway and lives run out?

The untouched flap handle doomed the takeoff - did they make it?

In this episode, we follow the minute-by-minute lead-up to the LAPA Flight 3142 accident, tracing crew actions, aircraft status, and procedural breakdowns that preceded the runway overrun. The episode asks how checklists, warnings, and certification failures intersected - and whether timely action could have changed the outcome.

Event: LAPA Flight 3142
Date: August 31, 1999
Location: Aeroparque Jorge Newbery, Buenos Aires
Aircraft: Boeing 737-200, registration LV-WRZ
People on board: 100 (95 passengers, 5 crew)

- Captain Gustavo Weigel boarded and interacted with dispatch; his pilot license had expired and personnel files logged repeated checklist and command weaknesses.
- First officer Luis Etcheverry, the junior pilot, arrived separately and ordered 8,500 kg of fuel before boarding procedures proceeded.
- The aircraft was airworthy with functioning engines, hydraulics, brakes, and thrust reversers; the airframe had logged 64,564 flight hours and 38,680 cycles.
- The takeoff checklist card was found intact and unworn in its holder, and cockpit recorders captured a timeline showing flaps were never extended.
- Investigators documented a paper trail of warnings, a cockpit warning light that activated and was ignored, and repeated certifications that overlooked documented procedural struggles.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A nine-month-old DC‑10 descends low toward Miami's runway, its crew unaware that approach lights and unseen wind shear have stolen their seconds.

The approach lights masked the wind shear and stole their seconds

In this episode, we follow the final minutes of a brand‑new Douglas DC‑10 on approach to Miami International and the sequence of decisions and missing information that shaped the descent. The story focuses on what the crew knew (and what they were never told) as the aircraft crossed the approach lights and encountered a sudden atmospheric instability - and asks whether systems or experience failed to buy them enough time.

Aircraft: Douglas DC‑10 (N310EA)
Date: December 20, 1972
Location: Miami International Airport, Runway 27 left approach
People: Captain James Sutor and three‑man cockpit crew (combined ~85,000 flight hours)
Passengers on board: 168

- The plane had been delivered in March 1972 and had accumulated 2,016 flight hours by December.
- Approach lights were mounted on 32‑foot concrete and steel piers extending into shallow water just short of the runway threshold.
- Instrument landing system and radio communications were functioning, but crews lacked accurate information about low‑level wind shear.
- The descent rate increased through an invisible instability that the pilots did not recognize in time given available information.
- Investigators concluded the trap was systemic - experienced crew competence could not compensate for critical information that was never provided.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Boeing 737 climbing out of Beirut makes a sudden left turn at 9,000 feet with 90 people aboard - did they make it in time?

The left turn at nine thousand feet cost them the chance to survive

In this episode, we reconstruct the first chaotic minutes after Ethiopian Airlines Flight 409 took off from Beirut, piecing together radar tracks, shoreline witness accounts, and the cockpit crew profiles to show how the flight deteriorated. What happened in those four minutes and forty-one seconds, and how did crew dynamics and weather shape the choices made in the cockpit?

Date: January 25, 2010
Flight: Ethiopian Airlines Flight 409
Aircraft: Boeing 737, registration ET-ANB
Time: 02:41 local
Location: Off the coast near Na'ameh, Mediterranean Sea

- Four minutes and forty-one seconds after takeoff the radar return vanished while the jet was still climbing and in sight of runway lights.
- The aircraft had climbed to about 9,000 feet and then executed a left-hand turn recorded by instruments.
- Captain Habtamu Benti Negasa had 10,233 total flight hours and 2,488 on the 737; First Officer Aluna Tamerat Beyene had 673 hours total and 350 on the 737.
- Weather that night featured variable winds at eight knots and thunderstorms rolling through the eastern Mediterranean, with shifting wind directions near the coast.
- Wreckage was later located about 45 meters beneath the Mediterranean near the village of Na'ameh, while shore witnesses and radar data presented conflicting accounts.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Beechcraft with Buddy Holly aboard struggles north from Mason City toward Clear Lake after an engine misfire-can they make it to the field in time?

The Beechcraft's Engine Misfired-Could They Reach Clear Lake in Time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A senator’s Aerostar nears Philadelphia with a dark nose‑gear indicator; can on-scene helicopter checks stop the clock with nine minutes left?

The nose-gear light failed and nine minutes ran out

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

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

- Pilot used propeller spinners as an improvised visual check and reported seeing the gear appear down.
- Philadelphia tower observers stated the nose gear “appeared” extended but could not verify gear was locked.
- The Aerostar’s warning horn would sound if throttles were reduced with gear unconfirmed, but investigators concluded the crew probably never tested it.
- No cockpit voice recorder existed on the Aerostar, leaving crew conversations and actions during the nine minutes undocumented.
- A Bell 412 SP helicopter crew heard the radio exchanges and offered to visually assist the Aerostar on approach.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A memo about a trim-tank transfer appears midflight, and an A330 with 306 aboard becomes a powerless glider - did they make it in time?

The trim-tank transfer memo that started a nineteen-minute glide

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Fokker 100 at Almaty sits iced in freezing fog before a rushed takeoff; a missed walk-around and asymmetric ice leave lift in doubt.

The skipped walk‑around left the wings iced - did they lift in time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A pilot reads a descent clearance over Cambodia's Cardamom Mountains; Flight 241 vanishes two minutes later - did they make it in time?

Last Transmission at 10:48: How Flight 241 Vanished into the Cardamoms

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A damaged VOR beacon led a charter plane a mile off course toward a Minnesota runway - did they make it in time?

The VOR beacon pulled planes a mile off course - did they make it?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A regional turboprop drifts off course toward a fogged Azores mountain; an alarm gives the crew seconds to avoid impact - did they make it in time?

The drifting heading that erased their minutes and doomed the flight

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

Landing gear extended as the Fokker 50 descended over Sharjah - sixteen seconds that may decide the passengers' fate. Did they make it in time?

The landing gear extended and burned sixteen seconds of fuel

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A pilot trained to counter wake turbulence slammed the rudder pedals as an Airbus A300 climbed out of JFK-could crews stop a falling tail fin in time?

The rudder pedals slammed; could crews stop a falling tail fin in time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A plane named Mesrop Mashtots descends toward Sochi at night - can two fatigued pilots stop a routine approach from becoming catastrophe?

Black Sea Landing Gear Down: Why Armavia A320 Dove at Night

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A bent pylon fitting from a Tulsa shortcut cracks unseen as American Airlines Flight 191 climbs - did they make it in time?

The bent pylon fitting failed six knots below stall - did they make it?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

An engine and pylon tore free the instant Flight 191 rotated at O'Hare-did the maintenance shortcut and a cracked pylon flange doom everyone aboard?

The pylon flange cracked during removal - did they reach safety?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A routine MD-82 takes off from Detroit and, moments later, simply stops flying-could a single missed checklist item doom everyone on board?

The Night an MD‑82 Stopped Flying: Surviving Flight 255's Silence

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A portable emergency locator transmitter sat in a Fairbanks hangar while the Alaskan wilderness swallowed a missing Cessna-did they make it in time?

The transmitter that stayed in Fairbanks cost them thirty-nine days

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A nearly new Boeing 727 lifts from Los Angeles; two minutes later the cockpit goes dark-did the pilots make it back to instruments in time?

Nine Silent Seconds: How Flight 266 Vanished After Takeoff

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A De Havilland Heron slams into a Norwegian peak in a blizzard; a single snow dune may have bought the passengers a chance at survival.

The snow dune that stopped the fuselage bought them twenty-seven hours

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

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

- Flight 253 departed Værnes at 08:30 and crossed Tolga beacon at 09:12 before conditions deteriorated.
- Icing accumulated on windshield, control surfaces and antenna until the crew were effectively blind and inaudible.
- Crew elected to turn back toward Trondheim; a sudden downdraft prevented completion of the turn.
- At 09:50 the aircraft struck the mountain at about 300 km/h, fuselage tore open and engines broke away.
- A compacted snow dune stopped the wreck on a slope, leaving ten survivors and one dead captain waiting in a storm for rescuers.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

Eighty‑three minutes late, a DC‑4 climbs toward Medicine Bow Peak - did the delay force a fatal shortcut across higher ground?

Eighty‑three minutes of delay forced a climb that met Medicine Bow's summit

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A forward baggage hold at Cotonou was packed until the last minute and a weight figure was wrong-did they make it in time?

The forward baggage hold filled itself and doomed the takeoff time

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A routine climb above Jakarta turns critical when the autothrottle retracts the left thrust lever midleveling - did they make it in time?

The autothrottle retracted the left thrust lever-did they make it?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A finger-sized circuit breaker sits tripped on the cockpit floor as LOT Flight 16 approaches Warsaw-did they make it in time?

The circuit breaker that tripped on the floor stalled the landing gear clock

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A fatigued flight crew approaches Narita in gusting wind and wind shear on final-will a late flare on an MD-11 be caught before touchdown?

The late flare that ate the runway seconds before touchdown

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A passenger jet lands hard at Rijeka in torrential rain - but in eight minutes something else collapses. Did they make it in time?

Eight Minutes That Killed: The Survivors Strapped Inside Aviogenex 130

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

An Air Canada A320 descends into San Francisco at night and a twelve‑second blind spot erases its warning - did they make it in time?

A twelve‑second blind spot erased the warning and nearly killed 140

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A shoebox-sized component stalls the engines of Atlantic Southeast Airlines Flight 2311 as it approaches Brunswick - did they make it in time?

The shoebox-sized component stalled the engines and cost twenty-three lives

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Vans RV lies inverted on a Homosassa road with its only door jammed; the studio manager is inside - did anyone reach him in time?

The RV's only door jammed shut - did anyone reach him in time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A stick shaker jolts at fourteen feet during takeoff from JFK, a sensor with nine prior faults triggers an emergency - did they stop the fire?

The stick shaker jolted at fourteen feet - did they stop the fire?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A missing flight progress strip leaves an LAX controller blind as a 737 nears a runway occupied by a commuter plane-did they make it in time?

The flight strip that never moved cost thirty‑five people their lives

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Twin Otter stalls in a mountain wave above the Park Range with a cracked fuselage - did rescuers find the 22 survivors in time?

The cabin lights burned for hours and kept twenty-two people alive

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A commuter turboprop lifts overweight and with limited elevator travel-can the crew gain pitch control and climb before thirty-five seconds run out?

The elevator cable turnbuckle limited pitch - could they lift in time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A jammed DC‑9 exit won’t open as fog blankets Detroit Metro and a 727 accelerates for takeoff - did they make it in time?

The jammed DC‑9 exit refused to open - two passengers lost five seconds

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A seasoned captain reports passing Agartala while the cockpit voice recorder shows they were still minutes away-did they make it in time?

The crew reported Agartala early - did they make it in time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC‑6 taking off from Long Island rolls and dives after one prop blade reads -8°-did the pilots have any warning before the wing went down?

One Wrong Prop: How a -8° Blade Sent Mainliner Idaho Plummeting

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A captain fights controls over the Red Sea as autopilot shifts into control-wheel steering - did they disable it in time?

The autopilot switched to control-wheel steering - did they disable it in time?

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC‑6 with gear down vanishes into San Francisco fog near King's Mountain-did the crew reach the runway in time?

The landing gear dropped and locked-did they reach the runway in time?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A DC‑8 on final to Toledo, a cargo door indicator that had gone dark weeks earlier, two failed approaches and twenty minutes to get it right.

The cargo door indicator that went dark cost them the runway in twenty minutes

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

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

- Flight originated Seattle 21:45 the night before, destined for Toledo Express as a routine cargo run.
- Aircraft had 72,084 flight hours and 22,804 cycles, in service since 1968 and converted to a freighter.
- Seventy‑two days earlier at Toledo, the same DC‑8 had an in‑flight cargo door opening due to incorrectly installed locking pins and an extinguished indicator light.
- Approach began just after 03:00; first approach at ~03:13 failed and crew executed an unremarkable go‑around on heading 100°.
- Second approach cleared ~03:21 with multiple GPWS warnings for glideslope deviation and excessive descent rate before impact.

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A mother boards a flight from Laredo to Houston to watch her daughter graduate-what happened?

The Graduation She Flew to See-Fifty-One Minutes to Reach Houston

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A cultural patron boards a light aircraft in Alaska on July 30, 1992 - one unexplained flight plan. Did they make it in time?

The single flight plan that left five seats and no explanation

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

A Convair runs out of fuel over Mississippi while Lynyrd Skynyrd's frontman nears his self‑predicted thirtieth birthday - did they make it in time?

The Convair that ran out of fuel - did they make it?

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

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

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

Tired of ads? Listen to this podcast and 200+ more ad-free on OBOMEDIA.
Try it free for 7 days, cancel anytime: https://obomedia.com/en/gratis?ref=desc-7317291

© 2026 Created by an independent creator of the OBOMEDIA Network. All rights reserved.
This episode and its content (audio, text, and related materials) are the property of their respective creator, who is solely responsible for them, and are distributed by the OBOMEDIA Network on platforms such as Apple Podcasts, Spotify, Amazon Music, and Pocket Casts. Reproduction, distribution, editing, or commercial use, in whole or in part, without the creator's prior written permission is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.