NTSB pulls docket after AI reconstructs cockpit audio from spectrogram
TECH

NTSB pulls docket after AI reconstructs cockpit audio from spectrogram

33+
Signals

Strategic Overview

  • 01.
    The NTSB temporarily suspended public access to its entire online docket system on May 21, 2026, after internet users used AI to reconstruct cockpit voice recorder audio from a spectrogram image released in the UPS Flight 2976 investigation.
  • 02.
    Federal law bars the NTSB from releasing cockpit voice recorder audio, but the agency did release a spectrogram (a visual frequency/time image) of the recording, which contained enough encoded data to allow reconstruction.
  • 03.
    Reconstruction used the Griffin-Lim phase-recovery algorithm (originally published in 1984) combined with modern AI tools such as OpenAI's Codex, with the publicly available transcript serving as a prior to constrain the audio approximation.
  • 04.
    The NTSB restored public access to most of the docket system on Friday but kept 42 investigations closed pending review, including the UPS Flight 2976 docket.

A spectrogram is not a picture of sound — it is the sound, serialized

The central misconception driving this incident is that a spectrogram is a visual aid. It isn't. A spectrogram is the magnitude of the Short-Time Fourier Transform of an audio signal, rendered as pixels: each column encodes the frequency content of a small slice of audio, and each row encodes a frequency bin. The amplitude at every (time, frequency) point is the pixel intensity. That means a high-resolution spectrogram PDF is, mathematically, the magnitude half of the audio's spectral representation — the only thing missing is the phase. Griffin-Lim, the 1984 algorithm at the heart of this leak, was designed specifically to recover that missing phase by iterating between time and frequency domains until the reconstructed waveform's STFT matches the given magnitude [3]. Audio engineers in the Reddit threads treated this as Audio 101: modern text-to-speech systems use exactly this pipeline in reverse, generating a spectrogram and then inverting it to waveform via a neural vocoder. NTSB Chairwoman Jennifer Homendy called it 'deeply troubling that emerging technology can be used to extract [CVR] audio from visualized data,' [2]but The Register's coverage pushed back that 'emerging mischaracterizes four-decade-old technology' [3]. The leak isn't novel signal processing. It's a policy that assumed images couldn't be inverted.

Why a 1984 algorithm broke a 40-year privacy regime in 2026

If Griffin-Lim is 42 years old, why didn't this happen to the NTSB in 1990, or 2010? Three accelerants converged this month. First, OpenAI's Codex and similar coding agents collapsed the build time: assembling a Griffin-Lim + neural-vocoder pipeline that once took a graduate student weeks now takes a curious hobbyist a few hours of prompting [1]. Second, and more importantly, the NTSB also publishes the cockpit voice transcript — and a transcript is a powerful text prior. With known words and timestamps, reconstruction stops being a blind audio-recovery problem and becomes a constrained optimization: any audio output is rejected if it doesn't roughly produce the published transcript when transcribed back [1]. That collapses a fuzzy, unintelligible Griffin-Lim output into something a human can recognize. Third, distribution. Scott Manley flagged the vulnerability on X on May 20; by May 21 reconstructed final-30-seconds clips were circulating on Reddit and X faster than the NTSB could respond, forcing a wholesale docket pull [4]. None of these three ingredients existed in their current potency before 2024 — which is why a 1984 attack is breaking a 1980s privacy statute in 2026.

The 42-docket problem — retroactive leakage across decades of investigations

The most overlooked detail in the NTSB statement is the number 42. When the agency restored partial access, it kept 42 historical investigations sealed pending review [1]. That implies the staff is now auditing past dockets for the same vulnerability — spectrograms, frequency plots, animations with audio-derived waveforms — released over years of accident reports. The retroactive surface is the real story: every NTSB docket from the past decade that included a spectrogram exhibit is potentially a privacy leak waiting for someone with a free Codex account to find. The same logic generalizes beyond aviation. Anywhere a regulator believed an image was a sanitized derivative of sensitive audio, this incident invalidates that assumption. The technical community discussions captured it precisely: the math isn't new, but the ability to execute it cheaply with no specialized knowledge is. That is the threshold change every agency releasing visual exhibits now has to internalize.

The contrarian read — CVR privacy as legal artifact, not principle

Underneath the privacy outrage sits an awkward question that surfaced in the community discussions: why is cockpit audio statutorily shielded when most workers' communications aren't? The NTSB has long described the federal protection as essential to keeping pilots candid during emergencies — and that candor is what produces better accident analysis. The leak threatens that bargain. A contrarian voice in the r/aviation thread pushed the point further by noting that other workers, including commercial truck drivers with mandatory cab cameras, get no equivalent shield — framing CVR privacy more as a professional carve-out than a principled stance. Meanwhile the NTSB has labeled the circulating reconstructions 'fabricated' [5]— technically accurate, since Griffin-Lim outputs are approximations rather than the true CVR, but a framing that could backfire if litigants or journalists treat any reconstructed audio as evidence. The next 12 months of NTSB policy — what gets published, what gets redacted, whether transcripts and spectrograms can coexist in the same docket — will set the template every regulator with a publication mandate eventually has to copy.

Historical Context

1984
Published the foundational phase-recovery algorithm in IEEE Transactions on Acoustics, Speech, and Signal Processing that 40+ years later enabled the cockpit-audio reconstruction.
2025-11-04
MD-11F freighter bound for Honolulu lost its left engine and pylon during takeoff rotation from Louisville Muhammad Ali International, caught fire, and crashed into nearby buildings, killing 3 crew and at least 11 on the ground.
2026-05-19
Opened a two-day investigative hearing for UPS Flight 2976 and released the docket containing the now-controversial spectrogram PDF.
2026-05-20
Posted on X warning that the released spectrogram could be reverse-engineered into audio, prompting hobbyists to attempt it.
2026-05-21
Temporarily pulled the entire public docket system after reconstructed audio began circulating on X and Reddit.
2026-05-22
Restored most docket access but kept 42 investigations including UPS 2976 sealed pending privacy review.

Power Map

Key Players
Subject

NTSB pulls docket after AI reconstructs cockpit audio from spectrogram

NA

National Transportation Safety Board (NTSB)

Federal investigator that released the spectrogram in the docket and then suspended public access to all dockets; controls future disclosure policy and is pursuing platform takedowns.

JE

Jennifer Homendy

NTSB Chairwoman who publicly condemned the audio reconstructions and ordered the docket pull.

SC

Scott Manley

Aerospace and physics YouTuber who first flagged on X on May 20, 2026 that the spectrogram was reconstructable, sparking attention.

OP

OpenAI

Provider of the Codex coding assistant that internet users invoked to assemble the audio reconstruction pipeline in hours rather than weeks.

UP

UPS Flight 2976 crew families

Families of the three pilots killed; primary privacy interest the federal CVR statute was written to protect.

X

X and Reddit

Platforms hosting the reconstructed audio that the NTSB is pressing to remove.

Fact Check

5 cited
  1. [1] AI is being used to resurrect the voices of dead pilots
  2. [2] AI is being used to recreate the cockpit voices of pilots killed in a plane crash
  3. [3] Feds unwittingly leak pilots' pre-crash conversation
  4. [4] NTSB Wants PDF Removed After It Exposed Final Cockpit Audio From UPS Crash
  5. [5] NTSB Says UPS Cockpit Voice Recordings Were Fabricated With AI

Source Articles

Top 4

THE SIGNAL.

Analysts

"Framed the use of AI to extract CVR audio from released visual data as a serious privacy violation that undermines the agency's transparency mission. Quoted: "It's deeply troubling that emerging technology can be used to extract [cockpit voice recorder] audio from visualized data we share to help the public understand the circumstances of an accident.""

Jennifer Homendy
Chairwoman, NTSB

"Warned within a day of the docket release that the spectrogram image contained enough information to recover the underlying audio. Quoted: "I'm not sure that's a good idea since you can probably reconstruct a lot of audio from the megabytes of data encoded in this image.""

Scott Manley
Aerospace and physics YouTuber

"Acknowledged the agency had not anticipated that publishing a spectrogram could leak the underlying audio. Quoted: "Nobody was aware that you can recreate audio from a picture.""

NTSB spokesperson
NTSB

"Pushed back on the 'emerging technology' framing, noting Griffin-Lim phase reconstruction has existed since 1984 and machine learning only lowered the barrier to implementing it."

The Register (editorial)
Technology publication
The Crowd

"The NTSB is aware that advances in image recognition and computational methods have enabled individuals to reconstruct approximations of cockpit voice recorder audio from sound spectrum imagery released as part of NTSB investigations, including the ongoing investigation of the UPS Flight 2976 crash."

@@NTSB_Newsroom1726

"Cockpit audio reconstructions of the Nov. 2025 UPS MD-11 crash have surfaced on sites like Reddit after a spectrogram file of the voice recorder was included in the accident docket this week"

@@willguisbond198

"The NTSB normally does not release cockpit voice recorder audio from accidents. In this case, however, they published a spectrogram image, and people were able to reconstruct portions of the audio from it. It appears the NTSB later realized the issue and temporarily shut down the docket system."

@@airmainengineer133

"NTSB removes UPS Flight 2976 Spectrogram"

@u/Yosh145921
Broadcast
Why The NTSB Shut Down Their Plane Crash Report Archive

Why The NTSB Shut Down Their Plane Crash Report Archive

UPS Flight 2976 Crash: New Footage and Transcripts Released

UPS Flight 2976 Crash: New Footage and Transcripts Released

[CVR] UPS flight 2976 leaked CVR (Maybe) (4th, November, 2025)

[CVR] UPS flight 2976 leaked CVR (Maybe) (4th, November, 2025)