What's New Since the Shutdown

The NTSB pulled its entire public docket system offline on May 22 after AI was used to reconstruct cockpit voice recordings from UPS Flight 2976, which crashed in Louisville killing all 15 people aboard including three pilots.

The agency still has NOT announced a timeline for restoring public access, according to NPR. That means thousands of aviation investigations — relied upon by airlines, manufacturers, and safety researchers — remain locked behind closed doors with no clarity on when they come back.

The Ten-Minute Problem

Mainstream coverage keeps framing this as a sophisticated AI breach. It wasn't.

John McElhone, who runs a small electrical turbine company, told NPR he had no audio background and cracked the spectrogram images in about ten minutes using publicly available AI tools. He regularly uses AI to write code for his business. This was not a state-sponsored attack. This was not a team of researchers.

One guy. Ten minutes. Off-the-shelf software.

Scott Manley — an astrophysicist and YouTuber — publicly posted on Twitter that he believed the spectrograms the NTSB had published to identify a mysterious high-pitched ringing sound (heard just after UPS 2976 rotated for takeoff) could be reverse-engineered into audio. His followers treated it as a challenge. They delivered.

The Scope Is Bigger Than One Crash

The NTSB realized that because it has included spectrogram imagery in dozens of historical investigations, the entire archive is now potentially vulnerable. Every past case where investigators published a visual sound map could now be reconstructed using the same technique, according to Simple Flying.

NTSB Chairwoman Jennifer Homendy called the AI-generated audio "deeply troubling," according to CNN as cited by Simple Flying. She noted the reconstructions were already circulating on X and Reddit, calling the posts "disgusting, manipulated" content that is "offensive to victims."

The agency created the vulnerability — unintentionally — by publishing the spectrograms in the first place.

What the Law Says

Federal law prohibits the public release of cockpit voice recordings. The NTSB posted a formal statement reiterating that position: "The NTSB does not release cockpit audio recordings. Federal law prohibits such public release due to the highly sensitive nature of verbal communications inside the cockpit."

The legal framework was built around a simple assumption: you can't release what you don't publish. AI just broke that assumption permanently.

Spectrograms were considered safe disclosures — technical images useful for safety analysis, stripped of the actual audio. Nobody at the NTSB anticipated that the images themselves were essentially the audio, just in a different format that AI could decode.

The Transparency Tradeoff

The NTSB's entire value to aviation safety is built on open data. Airlines, aircraft manufacturers, pilots' unions, and safety researchers use public investigation files to identify systemic problems before those problems kill more people. Restricted access doesn't just protect privacy — it slows down safety improvements across the entire industry.

As noted by nomadlawyer.com, industry experts warn that locking down investigation materials could delay identification of recurring hazards and complicate development of preventative measures across commercial aviation fleets.

But leaving spectrograms publicly accessible in their current form isn't viable either. Not when a turbine company owner can reconstruct protected audio in the time it takes to drink a cup of coffee.

What's Missing

The NTSB has been publishing spectrograms for years. How many investigations in the archive contain reconstructible audio? The agency hasn't published a number.

Also absent: a single concrete policy proposal from the NTSB on what comes next. Homendy has issued statements about how troubling this is. What she hasn't issued is a plan. "We aim to restore access soon" — published in the NTSB's official statement per Simple Flying — is not a plan. It's a press release.

The database went dark May 22. As of May 30, according to NPR, it remains offline.

What Happened

The NTSB didn't get hacked by nation-state actors using classified tools. It got outpaced by a technology that any hobbyist can access for free, doing something the agency never anticipated was possible. The fix isn't a statement — it requires rethinking how the agency publishes technical data across thousands of archived cases.

Every day the docket stays offline is a day aviation safety researchers work blind. And every day the NTSB stalls on a concrete policy is a day the agency proves it hasn't wrapped its head around what just happened.