Every recording here is a real transmission or a documented cockpit recorder transcript from a real flight. Some are the last words ever spoken by a crew. Some are the calmest voices in aviation history, holding a crippled airplane together with nothing but procedure and nerve. Open a file. Press play. These are the tapes.
The most famous dramatic moments ever captured on an air traffic control frequency or a cockpit voice recorder — presented with the full story behind the tape.
Washington was buried under one of the heaviest snowstorms in years when Air Florida Flight 90 pushed back from National Airport, nearly two hours late. The 737 sat in a line of aircraft waiting for takeoff clearance for so long that snow and ice built back up on the wings after de-icing — and the crew, worried about missing their slot, chose not to return for a second treatment. On the cockpit voice recorder, the first officer can be heard repeatedly questioning the engine readings during the takeoff roll: "That don't seem right, does it?" The captain dismissed the concern each time.
Seconds after rotation, the jet failed to climb. Ice-contaminated wings and an artificially high engine-thrust reading — caused by blocked sensor probes — meant the aircraft never had enough power to fly. The 737 clipped the 14th Street Bridge, crushing several occupied vehicles, before plunging into the frozen Potomac River. The CVR's final seconds capture the first officer's last words: "Larry, we're going down, Larry." "I know it," the captain replies, an instant before impact.
Only five of the 79 people aboard survived, pulled from the ice by helicopter and by bystanders — most famously Lenny Skutnik, who dove into the freezing river to rescue a passenger who could no longer hold onto the helicopter's line. The NTSB's investigation led directly to new FAA rules on de-icing hold-over times and cockpit procedures for verifying engine instruments before takeoff in icing conditions.
Read Full Report → PDFGolfer Payne Stewart's chartered Learjet 35 departed Orlando climbing toward Dallas when, at around 23,000 feet, the crew stopped responding to air traffic control. Controllers watched the jet continue its climb on autopilot to 39,000 feet and then fly on, straight and level, in total radio silence — for hours, across half the country.
Air Force and Air National Guard F-16s were scrambled from four different bases to intercept the silent jet in relay as it crossed state after state. Fighter pilots who pulled alongside reported the cockpit windows were completely opaque, coated in condensation or frost from the inside — consistent with a total loss of cabin pressure that would have incapacitated everyone aboard within minutes through hypoxia. The intercept pilots' radio calls describing the frozen, unresponsive aircraft became the eeriest transmissions of the entire event.
With both engines eventually starved of fuel, the Learjet entered a steep spiral and crashed in a field near Mina, South Dakota, killing all six aboard instantly. The NTSB's investigation concluded a pressurization failure was the likely cause, though the exact mechanism was never definitively proven — leaving the "ghost flight" as one of the most haunting mysteries in modern aviation.
Read Full Report → PDFShortly after American Airlines Flight 11 stopped responding to Boston Center and turned off its assigned course, controllers began urgently trying to raise the crew. What they heard back was not the flight crew at all. A hijacker, apparently attempting to make an announcement to the passengers over the cabin PA, keyed the wrong switch — transmitting directly to air traffic control instead: "We have some planes. Just stay quiet and you'll be okay."
It was the first indication any controller in the country had that a hijacking — let alone one intending to use the aircraft itself as a weapon — was underway. Boston Center supervisors scrambled to alert other facilities as a second aircraft, United Airlines Flight 175, also went silent nearby. The recording captures air traffic control transitioning, almost in real time, from routine radio traffic to the opening minutes of a national crisis.
The tapes remained largely unheard by the public for years afterward, gradually released through FAA disclosures, a 2004 9/11 Commission report, and later journalist requests. They're now studied as one of the most significant primary-source recordings in American history — the moment the people whose job was to keep the skies orderly first understood that the rules had changed.
Read Full Report → PDFCruising toward Los Angeles, Alaska Airlines Flight 261's crew began fighting a jammed horizontal stabilizer — the surface that controls the aircraft's pitch trim. Years of inadequate lubrication had worn away the threads on the jackscrew mechanism that held the stabilizer in place. The crew calmly worked the problem for nearly an hour, radioing maintenance control and diverting toward Los Angeles as a precaution, unaware the assembly was seconds from complete failure.
The threads finally stripped entirely, and the stabilizer jammed into a severe nose-down position, sending the MD-83 into a violent dive. The captain and first officer fought to recover, at one point regaining a brief, terrifying level of control by flying the aircraft inverted — the CVR capturing the captain's urgent commands to "push and push and push" the controls as they tried to hold the nose up using pure aerodynamic force after the trim system failed completely.
The aircraft crashed into the Pacific Ocean, killing all 88 people aboard. The investigation into the jackscrew failure led to sweeping FAA airworthiness directives across the entire MD-80/DC-9 fleet worldwide, rewriting maintenance intervals for one of the most critical, and previously overlooked, mechanisms in the tail of a jet airliner.
Read Full Report → PDFRoughly an hour out of New York bound for Geneva, the crew of Swissair 111 smelled smoke in the cockpit. They radioed Moncton Center with a "Pan Pan Pan" — the internationally recognized urgency call one step below a full Mayday — and requested a diversion to Halifax, calmly beginning to dump fuel to get down to a safe landing weight.
What the crew didn't know was that a fire, sparked by arcing wiring above the cockpit ceiling, had ignited flammable insulation material and was spreading rapidly through the space behind their instrument panels. Within minutes, critical flight instruments and communication systems began failing one after another. The last transmissions from the aircraft show a crew still working the checklist, still calm, with no idea how little time remained.
Swissair 111 crashed into the Atlantic Ocean just minutes from the runway at Halifax, killing all 229 people aboard, in what became one of the longest and most expensive accident investigations in aviation history. The findings led directly to a worldwide ban on the flammable Mylar-type insulation blankets used in aircraft wiring bays.
Read full report →Actual pilot radio calls, caught live on frequency, reporting encounters with objects nobody could identify. Trained professionals, on an open channel, describing something that wasn't supposed to be there.
Cruising at 36,000 feet over the remote high desert of northeastern New Mexico, the crew of American Airlines Flight 2292 watched something pass directly over their aircraft, moving far faster than any traffic they'd expect to encounter at that altitude. About nine minutes later, the captain radioed Albuquerque Center — the call caught live by hobbyists monitoring the frequency on the ground.
"Did anyone report any traffic in the area at 37,000 feet or higher? ...We had something go right over the top of us," the pilot said. "I hate to say this, but it looked like a long cylindrical object that almost looked like a cruise missile type of thing, moving really fast right over the top of us." Albuquerque Center checked for any known traffic in the area and found nothing that matched.
American Airlines and the FAA both later confirmed the report was genuine. The recording spread widely online within days, becoming one of the most-cited modern UAP cases specifically because the audio itself — a professional pilot, mid-flight, visibly startled, on an open ATC channel — is the primary evidence. Full radar and communications records were released years later, but no explanation for the object has ever been confirmed.
Read full report →Captain Kenju Terauchi, an experienced ex-fighter pilot with more than 10,000 flight hours, was flying a JAL cargo 747 over eastern Alaska when he and his two crewmates reported unidentified lights pacing their aircraft. Terauchi described "two small ships" flying in formation ahead of the jet, followed by what he called a much larger object he referred to as a "mothership," which he said the smaller objects appeared to fly into.
The crew radioed Anchorage Center to report the objects and request confirmation. Both FAA ground radar and a nearby military radar installation reportedly showed an intermittent, unexplained return matching the reported position — though a United Airlines flight and an Air Force C-130 in the same airspace at the time saw and detected nothing at all.
The case triggered an unusually high-level review: the FAA, FBI and CIA all examined the radar and radio data, and investigators found Terauchi to be a credible, sober, professional witness. Skeptics have since suggested the crew may have misidentified the planets Jupiter and Mars low on the horizon. Case files remain among the most extensively documented UAP reports the FAA has ever produced.
Read Full Report → PDFFlying a midnight cargo run between Blenheim and Christchurch, pilots Vern Powell and Ian Pirie radioed Wellington air traffic control to report a series of bright, erratic lights pacing their aircraft around the Kaikōura mountain range. Wellington confirmed unexplained radar returns matching the lights' reported positions — a rare case of a live UAP report being corroborated by ground radar in real time.
Word of the sighting spread fast enough that, just over a week later, a television news crew boarded a follow-up Safe Air flight along the same route specifically hoping to film the phenomenon. They succeeded — capturing footage of glowing objects outside the aircraft that was broadcast around the world, while cockpit-to-tower radio traffic was again recorded as the lights appeared.
New Zealand's Defence Force and Air Force investigated extensively. Their report attributed some of the lights to Venus, squid-boat lights reflecting off cloud, and Japanese fishing fleets working the coast that night — but acknowledged that a portion of the radar-confirmed sightings were never conclusively explained. Nearly half a century later, it remains New Zealand's most famous UAP case.
Read full report →These are the actual radio calls and case records as documented by the pilots, controllers and agencies involved. We aren't claiming to know what any of these objects were — only that trained professionals, live on an open channel, reported seeing something they couldn't identify. Draw your own conclusions.
Not every black box tells a story of loss. These are the recordings where the voices stayed calm, the checklists got worked, and everyone walked away — caught live, on frequency, as it happened.
Ninety seconds after departing LaGuardia, US Airways Flight 1549 flew directly through a flock of Canada geese, disabling both engines at roughly 2,800 feet over the Bronx. On the recording, Captain Chesley "Sully" Sullenberger's voice is almost unnervingly level as he informs departure control: "We're gonna be in the Hudson."
Controller Patrick Harten, believing at first he'd misheard, scrambled to clear a runway back at LaGuardia and then at nearby Teterboro Airport — not yet realizing Sullenberger had already ruled out reaching any runway at all. The recording captures Harten's voice cracking slightly as he repeats "Cactus 1549, radar contact lost" into a silent frequency, genuinely unsure for a moment whether the aircraft had survived.
Sullenberger and First Officer Jeffrey Skiles ditched the powerless jet on the Hudson River in a controlled, wings-level landing. All 155 people aboard were rescued within minutes by nearby ferries, in a water landing so precisely executed it was immediately nicknamed the Miracle on the Hudson.
Read Full Report → PDFAn uncontained failure of the DC-10's tail-mounted engine sent shrapnel through all three of the aircraft's independent hydraulic systems simultaneously — a failure mode the aircraft's designers had considered virtually impossible. Captain Al Haynes and his crew were left with no conventional flight controls whatsoever, only the throttles of the two remaining wing engines.
An off-duty DC-10 training instructor, Denny Fitch, came forward from the cabin to help, kneeling between the pilots and working the throttles by hand to crudely steer the aircraft through differential thrust alone — a technique essentially invented in real time. Throughout, the crew's radio calls to Sioux City Approach remained methodical and calm, coordinating a landing attempt that, by any normal measure, shouldn't have been survivable at all.
The DC-10 crash-landed at Sioux Gateway Airport, breaking apart and catching fire on impact. Of 296 people aboard, 184 survived — a result so far beyond what investigators expected from a total hydraulic failure that it's still taught in cockpit resource management courses worldwide as the definitive example of a crew working a problem no training manual had ever covered.
Read Full Report → PDFA fueling error rooted in Air Canada's mid-conversion from imperial to metric units left Flight 143 with less than half the fuel its crew believed was aboard. At 41,000 feet over Manitoba, both engines flamed out one after the other, leaving Captain Bob Pearson and First Officer Maurice Quintal in command of a 132-ton glider with no power at all.
Pearson, who happened to be an experienced recreational glider pilot, calmly radioed Winnipeg Center to declare the emergency and begin working out where they might possibly reach. With no engines to generate hydraulic pressure for normal braking or flap control, and Winnipeg too far away to reach, Quintal suggested a decommissioned Royal Canadian Air Force base he'd once trained at — Gimli, since converted into a drag racing strip that, unknown to the crew, had spectators and cars on it that day.
Pearson executed a forward slip — a maneuver more familiar from gliders than airliners — to bleed off excess altitude on final approach, and put the powerless 767 down safely on the drag strip, stopping just short of the crowd. Only minor injuries were reported. The aircraft, repaired and returned to service, flew for Air Canada for another 25 years under a nickname that stuck for good: the Gimli Glider.
Read Full Report → PDFMinutes after departing Singapore, one of Qantas Flight 32's four engines suffered an uncontained failure, spraying turbine debris through the wing at high velocity. Unlike a typical single-engine failure, the shrapnel tore through wiring bundles, fuel lines and hydraulic systems across a huge section of the aircraft — knocking out or degrading more than twenty separate aircraft systems simultaneously.
With five qualified pilots aboard — including a check captain and a trainee, both riding along that day — the crew spent nearly two hours working through the A380's electronic checklists faster than the systems could even finish listing every fault, coordinating extensively and calmly with Singapore air traffic control while they worked out whether the aircraft could land safely at all.
Captain Richard de Crespigny brought the badly damaged superjumbo back to Singapore, landing with limited braking, no fuel jettison capability, and half the wing's systems offline — later calling it the most heavily damaged A380 ever to land safely. Nobody aboard or on the ground was injured, and the flight became a landmark case study in crew coordination under overwhelming technical failure.
Read full report →New to ATC and CVR recordings? Here's what you're actually hearing, where it comes from, and how to listen with the right context.
Air traffic control recordings capture the radio conversation between a flight crew and the ground controllers directing traffic — takeoff and landing clearances, altitude changes, and emergency declarations. In most countries, including the U.S., these are treated as public radio transmissions: aviation authorities and hobbyist networks like LiveATC.net routinely archive and release them, which is why so many of the tapes on this page are genuine, unedited recordings.
The cockpit voice recorder — one of two "black boxes," alongside the flight data recorder — continuously records the last two hours of cockpit audio: crew conversation, switch clicks, alarms and ambient sound. It's built to survive a crash so investigators can reconstruct exactly what happened and why.
In the United States, federal law (49 U.S.C. § 1114) protects the actual CVR tape from public release — investigators use it, but the raw audio itself is not handed out. What the public gets is an official written transcript. Most "CVR recordings" online for U.S. accidents, including several on this page, are voice reconstructions of that transcript, not the original tape. Some countries, like Canada in the Swissair 111 case, have released real CVR or cockpit-to-ATC audio directly — we've labeled every recording's evidence type so you know exactly what you're hearing.
Every tragedy on this page happened to real crews, real passengers and real families. These recordings are studied by investigators, pilots and researchers specifically because they save lives — the lessons learned from them have reshaped checklists, maintenance rules and cockpit training industry-wide. We present them here in that same spirit: as history and education, not spectacle.
Flight Crew Files compiles publicly documented recordings and case files as reported by investigating authorities, news archives and the aviation community. Video embeds link to third-party YouTube uploads; we don't own or control that footage and can't guarantee any individual upload's permanence or exact fidelity to the original tape. Where a recording isn't a verified original — such as a dramatized CVR reconstruction — we've labeled it as such in the case file.