Air Disasters – The Black Box Files
NuevoEight Seconds of Warning: Why Flight TK634 Vanished in Fog
- Episodios
- 111
- Se publica
- a diario
- Último episodio
- 14 Nov 2026
Sobre el podcast
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. New episodes drop regularly, each one a self-contained investigation. Subscribe now so the next of these air disasters lands the moment it goes live.
Episodios 111
Eight Seconds of Warning: Why Flight TK634 Vanished in Fog
A captain and first officer descend through Diyarbakır fog on a VOR approach - did they climb before the runway vanished from sight?Eight Seconds of Warning: Why Flight TK634 Vanished in FogIn this episode, we …
Notas del episodio
A captain and first officer descend through Diyarbakır fog on a VOR approach - did they climb before the runway vanished from sight?
Eight Seconds of Warning: Why Flight TK634 Vanished in Fog
In this episode, we follow the final minutes of Turkish Airlines Flight 634 as the crew carries out a routine domestic approach into Diyarbakır amid conflicting visibility reports and missing landing aids. We trace the decisions, instruments, and weather that shaped those eight critical seconds and the unanswered question they leave: what did the pilots see and decide in the fog?
Date: January 8, 2003
Flight: Turkish Airlines Flight 634
Aircraft: British Aerospace Avro RJ100, registration TC-THG
Location: Diyarbakır Airport, Turkey
Approach: Non-precision VOR approach (no ILS)
- Crew composition: Captain Alaaddin Yunak (34, ex-military, 6,309 hours) and First Officer Ismail Altug Ulusu (33, 2,052 hours) were rested, current, and tested negative for drugs and alcohol.
- Weather reports conflicted: ATC reported visibility at 3,500 metres while rescue teams measured under one metre minutes after impact.
- Airport equipment gap: Diyarbakır had no Instrument Landing System (ILS); pilots flew a VOR approach offering horizontal guidance but no electronic vertical glidepath.
- Descent profile: Flight entered approach at 9,000 feet, descended to the published minimum descent altitude of 2,800 feet and continued with no runway in sight.
- Warning timeline: Cockpit alarm sounded and screamed for eight seconds before the aircraft struck terrain roughly 900 metres short of 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: [email protected].The empty CRJ climbed past its ceiling - did they make it?
An empty CRJ climbs past its ceiling on a ferry flight to Minneapolis-two pilots pushing limits; did they make it in time?The empty CRJ climbed past its ceiling - did they make it?In this episode, we follow a …
Notas del episodio
An empty CRJ climbs past its ceiling on a ferry flight to Minneapolis-two pilots pushing limits; did they make it in time?
The empty CRJ climbed past its ceiling - did they make it?
In this episode, we follow a repositioning ferry flight where two Pinnacle Airlines pilots pushed a Bombardier CRJ-200 beyond its certified ceiling and into a chain of escalating errors. The episode traces the decisions, the silence, and the missing oversight that turned routine choices into catastrophe - what went wrong in those fifty-three minutes?
Date: October 14, 2004
Aircraft: Bombardier CRJ-200 (N8396A)
Operator: Pinnacle Airlines / Northwest Airlink
Flight type: Ferry flight (no passengers, no cabin crew)
Duration of recorded incident: 53 minutes
- Two pilots, Jesse Rhodes (captain, 31) and Peter Cesarz (first officer, 23), deadheaded to Little Rock then were reassigned to the empty ferry run.
- The CRJ’s certified ceiling was 41,000 feet; pilots in Pinnacle’s community informally attempted that altitude on empty repositioning flights.
- Rhodes had 6,900 total flight hours and 973 on the CRJ-200; training records noted deficiencies in decision-making and judgment.
- The flight data and cockpit voice recorders capture a sequence: climb past ceiling, a violent stall and dual engine flameout, then fourteen minutes where both engines were out but ATC was told only one had failed.
- At the moment of upset six airports were within gliding range; five slipped out of reach during the fourteen minutes of silence.
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: [email protected].The VOR hold that looped them into the mountain - did they make it?
A VOR hold over Ajaccio turns into a deadly course into mountains: a crew, a controller and nine seconds to change everything.The VOR hold that looped them into the mountain - did they make it?In this episode …
Notas del episodio
A VOR hold over Ajaccio turns into a deadly course into mountains: a crew, a controller and nine seconds to change everything.
The VOR hold that looped them into the mountain - did they make it?
In this episode, we follow the final flight of Inex‑Adria MD‑82 YU‑ANA on 1 December 1981 and the sequence of decisions that placed crew and controller on different realities. What went wrong during the VOR hold and the nine seconds before impact?
Date: 1 December 1981
Aircraft: MD-82, registration YU-ANA
Flight: Inex-Adria JP-308
Location: Mont San-Pietro, Corsica / Ajaccio VOR
Crew: Captain Ivan Kunović; First Officer Franc Terglav
- The flight was a one-hour charter from Ljubljana to Ajaccio with 180 people aboard, the airline's first ever Ajaccio service.
- The MD-82 had 683 flight hours, was delivered in August 1981, and showed no mechanical defects on investigation.
- Captain Kunović had 12,000+ total hours but only 188 on MD‑80 series after converting in August 1981.
- First Officer Terglav had just received his commercial licence 20 days earlier and sat with his son in the cockpit jump seat during descent.
- Ajaccio approach ordered a hold over the VOR; the crew followed published Jeppesen holding guidance while the controller sequenced traffic and changed active 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: [email protected].Six Missing Words: How a Phrase Sent a Jet Into a Man's Path
A jet at Luton and a light twin converge on the same runway - six words never spoken leave one moment: will they clear each other?Six Missing Words: How a Phrase Sent a Jet Into a Man's PathIn this episode, we …
Notas del episodio
A jet at Luton and a light twin converge on the same runway - six words never spoken leave one moment: will they clear each other?
Six Missing Words: How a Phrase Sent a Jet Into a Man's Path
In this episode, we reconstruct the eighteen seconds at Luton Airport on April 18, 1974, when a BAC One-Eleven and a Piper Aztec converged on Runway 08/26. What did a three-word omission in radio phraseology mean for two crews and the controller trying to keep them apart?
Date: April 18, 1974
Location: Luton Airport
Aircraft 1: BAC One-Eleven G-AXMJ
Aircraft 2: Piper PA-23 Aztec G-AYDE
Controller action: Transmission "Cleared to Alpha Two Six" (abbreviated)
- The One-Eleven, a 107-ton charter jet, commenced its takeoff roll at 15:27:31, accelerating past 100 knots.
- The Aztec, a light twin with a qualified pilot seated in the right seat, taxied toward the runway threshold after hearing an abbreviated clearance.
- Standard phraseology would have been "Cleared to holding point Alpha, Runway Two Six," but the controller used a shorter form that named a destination, not a limit.
- Both aircraft were on the same radio frequency with the same controller, yet neither crew was informed the runway was occupied by the other.
- Eighteen seconds elapsed between the Aztec entering the runway and the One-Eleven already committed to takeoff speed, while the Aztec right-seat passenger asked over the intercom whether they had clearance and received no response.
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: [email protected].The squall-line briefing he shrugged off - and they ran out of runway
A veteran captain shrugs off a squall-line briefing and takes off toward Islamabad with a storm crossing the approach - did they make it in time?The squall-line briefing he shrugged off - and they ran out of …
Notas del episodio
A veteran captain shrugs off a squall-line briefing and takes off toward Islamabad with a storm crossing the approach - did they make it in time?
The squall-line briefing he shrugged off - and they ran out of runway
In this episode, we follow the flight, the crew and the institutional records behind a Boeing 737 approach into a squall line. We trace warnings in training files, weather briefings and operational choices to ask how decisions over months put one crew on that corridor that night.
Person: Captain Noorullah Afridi
Person: First Officer Javaid Malik
Date: April 20, 2012
Aircraft: Boeing 737-236A, registration AP-BKC
Event: Karachi to Islamabad approach with squall line and high surface winds
- Captain Afridi had over ten thousand flight hours but only eighty-two hours on the exact Boeing 737-236A type and had received a South African simulator report recommending additional automation training.
- First Officer Malik also had eighty-two hours on the same type, had delayed recurrent simulator training that was later signed off by the Civil Aviation Authority.
- Bhoja Air had recently relaunched and the flight was the airline’s first inaugural night service on the Karachi-Islamabad schedule, a subtle source of pressure documented by investigators.
- Meteorological briefing recorded a squall line crossing the approach and surface winds of 24-36 knots; Afridi’s verbal response to the briefing was captured on the cockpit voice recorder.
- Flight data shows the aircraft accelerated to 280 knots during descent toward the weather system and impacted terrain four miles short of the runway at 215 knots.
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: [email protected].The valve that stayed half‑closed stalled the de‑icer - did they make it?
An Antonov An‑12 battles heavy icing after the crew switch on de‑icing-did a half‑closed valve doom them before they reached Surgut?The valve that stayed half‑closed stalled the de‑icer - did they make it?In …
Notas del episodio
An Antonov An‑12 battles heavy icing after the crew switch on de‑icing-did a half‑closed valve doom them before they reached Surgut?
The valve that stayed half‑closed stalled the de‑icer - did they make it?
In this episode, we follow a routine January cargo flight from Tyumen to Surgut that encountered severe icing during descent and activated its de-icing system. The story focuses on the crew actions, aircraft systems, and a silent mechanical fault that may have stalled the aircraft-could a small valve have decided their fate?
Person: Captain Konstantin Ivanovich Adamovich
Aircraft: Antonov An-12, registration CCCP-12996
Date: 31 January 1971
Location: Approach to Surgut airport, West Siberian Plain
Event: Severe airframe icing after de-icing system activation
- Departure at 01:25 Moscow time on a night cargo run carrying twelve metric tons of boxed Pacific herring.
- Crew of seven (six named crew members plus a loadmaster whose name is absent from records) followed standard procedures and reported very strong icing.
- Flight Mechanic Yuri Isakov switched the engine bleed‑air de-icing system on; cockpit gauges indicated the system was operating.
- The AN-12 used bleed air routed through valves to heat wing leading edges, with wing tips dependent on full valve travel for adequate heat.
- Valves on CCCP-12996 failed to reach full travel, reducing hot-air delivery to the wing tips despite the system appearing functional.
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: [email protected].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 …
Notas del episodio
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 out
In 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 Schine
Date: 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: [email protected].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 …
Notas del episodio
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: [email protected].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 …
Notas del episodio
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: [email protected].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 …
Notas del episodio
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: [email protected].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 …
Notas del episodio
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: [email protected].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 …
Notas del episodio
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: [email protected].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 …
Notas del episodio
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: [email protected].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 …
Notas del episodio
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: [email protected].The controller's "final approach path is clear" bought them seconds
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 secondsIn this episode, we …
Notas del episodio
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: [email protected].The Outer Marker Crossed High That Left One Runway and Seconds to Spare
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 SpareIn …
Notas del episodio
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: [email protected].The untouched flap handle doomed the takeoff - did they make it?
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 …
Notas del episodio
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: [email protected].The approach lights masked the wind shear and stole their seconds
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 …
Notas del episodio
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: [email protected].The left turn at nine thousand feet cost them the chance to survive
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 surviveIn this episode, we …
Notas del episodio
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: [email protected].The Beechcraft's Engine Misfired-Could They Reach Clear Lake in Time?
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 …
Notas del episodio
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: [email protected].The nose-gear light failed and nine minutes ran out
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 outIn this episode …
Notas del episodio
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: [email protected].The trim-tank transfer memo that started a nineteen-minute glide
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 glideIn this …
Notas del episodio
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: [email protected].The skipped walk‑around left the wings iced - did they lift in time?
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 …
Notas del episodio
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: [email protected].Last Transmission at 10:48: How Flight 241 Vanished into the Cardamoms
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 CardamomsIn …
Notas del episodio
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: [email protected].The VOR beacon pulled planes a mile off course - did they make it?
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 …
Notas del episodio
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: [email protected].The drifting heading that erased their minutes and doomed the flight
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 …
Notas del episodio
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: [email protected].The landing gear extended and burned sixteen seconds of fuel
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 fuelIn this …
Notas del episodio
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: [email protected].The rudder pedals slammed; could crews stop a falling tail fin in time?
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 …
Notas del episodio
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: [email protected].Black Sea Landing Gear Down: Why Armavia A320 Dove at Night
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 NightIn this …
Notas del episodio
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: [email protected].The bent pylon fitting failed six knots below stall - did they make it?
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 …
Notas del episodio
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: [email protected].
Aquí están los 40 episodios más recientes de 111. Los anteriores están en el feed del podcast.
Podcasts similares
Más podcasts de Ocio
¿Es tu podcast?
Confírmalo con una entrada en tu feed: aquí recibes un código, lo añades como podcast:txt en el canal de tu feed y nosotros lo comprobamos. Después tu podcast aparecerá como «verificado» en SoundNode.