Free Daily Podcast Summary
Air Disasters - The Black Box Files: Daily Summaries Delivered
by OBOMEDIA ENTERTAINMENT
Air disasters begin quietly: a sensor reading nobody trusts, a bolt torqued wrong on a night shift, two words misheard between cockpit and tower. This show reconstructs true air disasters from the black box outward, one flight at a time. Each episode rebuilds one flight in full, cinematic detail: the crew and their decisions, the machine and its hidden flaw, the seconds where routine turned into emergency, and the investigation that pieced the truth together from wreckage and data. No host chatting between clips, no panel debating theories. Just one complete story, narrated start to finish, built from cockpit voice recorders, accident reports, and the testimony of investigators. You will fly through air disasters caused by a single frozen instrument, collisions built from a chain of tiny coincidences, and impossible landings that saved hundreds when everything had already failed. Some episodes follow the final minutes second by second; others follow the years-long investigations that changed how the world flies. All of them treat air disasters as what they really are: lessons written at terrible cost, and the reason flying keeps getting safer. If you are drawn to air disasters told with rigor and humanity, this is built for you.
Latest Episodes
The most recent episodes — sign up to get AI-powered summaries of each one.
- Yesterday22 min
The six‑page pamphlet that forced the Army's clock to run out
A six-page anti-Communist pamphlet by a 24-year-old hotel heir lands him in McCarthy’s circle - can his pamphlet and a drafted soldier force the Army to act?The six‑page pamphlet that forced the Army's clock to run outIn this episode, we follow the paper trail, testimony, and televised footage that surround G. David Schine’s rise from hotel heir to unpaid chief consultant in McCarthy’s investigations. The episode traces how a flawed six-page pamphlet, an unlikely friendship with Roy Cohn, and a fabricated rank propelled Schine into the center of a national controversy - and asks how that controversy reached the Army’s doorstep.Person: Gerard David SchineDate: June 19, 1996 (plane crash)Date: September 11, 1927 (birth)Event: Publication of Definition of Communism (1952)Person: Roy Cohn- A six-page pamphlet titled Definition of Communism, written in 1952 by a 24-year-old Schine, contained factual errors yet was widely distributed in his hotel chain.- Schine misrepresented himself as a lieutenant on his Harvard application, but was later drafted as a private in 1953.- Columnist George Sokolsky introduced Schine to Roy Cohn, leading to Schine’s unpaid role as chief consultant to McCarthy’s Permanent Subcommittee on Investigations.- In spring 1953 Cohn and Schine toured USIA libraries across seven countries in 18 days, openly removing books and prompting international media critique.- Theodore Kaghan publicly criticized their actions and was subsequently investigated by the subcommittee, illustrating the personal and professional costs of the campaign.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.
- 2 days ago20 min
The Christmas mailload jammed the Uiver's controls and cost them the runway
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 runwayIn 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 BeekmanPerson: Jan van SteenbergenEvent: Christmas mail flight from Amsterdam to BataviaDate: 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.
- 3 days ago19 min
The glide-slope absence that left descent on a clock
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 clockIn 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, 1970Aircraft: Southern Airways DC‑9‑30, N97SPerson: Captain Frank Abbott; First Officer Jerry SmithEvent: Crash during approach to Tri‑State AirportTopic: 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.
- 4 days ago19 min
The radio compass needles both pointed at PR - did they turn in time?
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 PopovDate: October 30, 1975Aircraft: Douglas DC‑9 series 32, registration YU‑AJOLocation: Prague Ruzyně approach, fog over Runway 25Event: 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.
- 5 days ago20 min
The landing system sat in a warehouse - did they reach the runway in time?
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 1963Flight: Aero O/Y Flight 217Aircraft: Douglas DC-3Location: Mariehamn, Åland Islands, FinlandSurvivors: 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.To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.© 2026 OBOMEDIA. All rights reserved.This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
- 6 days ago21 min
Thirty-One Meters: Why Widerøe Flight 744 Vanished Below the Radar
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 RadarIn 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 1993Flight: Widerøe Flight 744 (Twin Otter LN-BNM)Location: Namsos approach, NorwayPassengers: 17Survivors: 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.To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.© 2026 OBOMEDIA. All rights reserved.This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
- 1 weeks ago20 min
The automated weather loop omitted one runway and turned night into a countdown
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 countdownIn 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, 1994Location: St. Louis Lambert International AirportAircraft (1): McDonnell Douglas MD-82, N954UAircraft (2): Cessna 441 Conquest II, N441KMFlight 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.To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.© 2026 OBOMEDIA. All rights reserved.This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
- 1 weeks ago21 min
The ungrooved runway sent the jet onto the road - did they make it?
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 2008Location: Toncontín International Airport, Tegucigalpa, HondurasAircraft: Airbus A320, registration EI-TAFPeople: 135 on board (124 passengers, 11 crew); notable passengers named in recordCondition: 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.To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.© 2026 OBOMEDIA. All rights reserved.This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.
About Air Disasters - The Black Box Files
Air disasters begin quietly: a sensor reading nobody trusts, a bolt torqued wrong on a night shift, two words misheard between cockpit and tower. This show reconstructs true air disasters from the black box outward, one flight at a time. Each episode rebuilds one flight in full, cinematic detail: the crew and their decisions, the machine and its hidden flaw, the seconds where routine turned into emergency, and the investigation that pieced the truth together from wreckage and data. No host chatting between clips, no panel debating theories. Just one complete story, narrated start to finish, built from cockpit voice recorders, accident reports, and the testimony of investigators. You will fly through air disasters caused by a single frozen instrument, collisions built from a chain of tiny coincidences, and impossible landings that saved hundreds when everything had already failed. Some episodes follow the final minutes second by second; others follow the years-long investigations that changed how the world flies. All of them treat air disasters as what they really are: lessons written at terrible cost, and the reason flying keeps getting safer. If you are drawn to air disasters told with rigor and humanity, this is built for you.
Customized Recaps
AI-powered recaps with compact key takeaways, quotes, and insights.
Straight to Your Inbox
Get key takeaways from Air Disasters - The Black Box Files in a 5-minute read.
Save Hours Every Week
Stay current on your favorite podcasts without falling behind.
Frequently Asked Questions
What is Podzilla's Air Disasters - The Black Box Files daily summary?
It's a free AI-powered email that summarizes new episodes of Air Disasters - The Black Box Files as soon as they're published. You get the key takeaways, notable quotes, and links & mentions — all in a quick read.
How does the Air Disasters - The Black Box Files podcast summary work?
When a new episode drops, our AI transcribes and analyzes it, then generates a personalized summary tailored to your interests and profession. It's delivered to your inbox every morning.
Is this an official Air Disasters - The Black Box Files product?
No. Podzilla is an independent service that summarizes publicly available podcast content. We're not affiliated with or endorsed by OBOMEDIA ENTERTAINMENT.
Can I get summaries of other podcasts too?
Absolutely! The free plan covers up to 3 podcasts, any in the catalog. Basic raises that to 15, Pro to 40 and Max to 100. Browse our full catalog at /podcasts.
How often does Air Disasters - The Black Box Files release new episodes?
Air Disasters - The Black Box Files publishes daily. Our AI generates a summary within hours of each new episode.
What topics does Air Disasters - The Black Box Files cover?
Our AI identifies the specific themes in each episode and highlights what matters most to you.
Start getting Air Disasters - The Black Box Files summaries tomorrow morning.
Free forever for up to 3 podcasts. No credit card required.
Free forever for up to 3 podcasts. No credit card required.