Policy · 22 May 2026 · 2 min read

NTSB Pulls Accident Database After AI Voice Recreation

The US transport safety board pulled its public database after users recreated pilot voices, a sharp reminder that public data is not always fair game.

Pen-and-ink illustration: a large, intricate keyhole being sealed. For the story "NTSB Pulls Accident Database After AI Voice Recreation".
— Pen-and-ink illustration: a large, intricate keyhole being sealed. For the story "NTSB Pulls Accident Database After AI Voice Recreation". —

What happened

The US National Transportation Safety Board (NTSB) has temporarily shut down its public database of accident investigations. The move, reported by Ars Technica, came after internet users re-created the final cockpit audio of a fatal plane crash. They used AI tools on a spectrogram — a visual representation of sound — that the agency had published in its report on UPS flight 2976. A 1990 federal law explicitly prohibits the NTSB from releasing cockpit audio recordings to protect the privacy of air crews.

How the room's reading it

The reaction from aviation safety experts is one of shock. Former NTSB investigators told Ars Technica they were horrified, explaining that the law exists to protect the privacy of pilots in their final moments — a pact that has stood for decades. On social media, however, the tone is different. Users on X and Reddit shared the reconstructed audio, with some noting how quickly it could be done with modern tools. One developer claimed it took just ten minutes with an AI model to generate a rough version from the NTSB's own spectrogram, highlighting a new reality where data workarounds can bypass long-standing legal protections.

Sailfish's take

This isn't a clever technical hack. It's a failure of imagination and respect. We see this as a clear line for builders — public data does not equal ethical clearance. The NTSB's spectrogram was released for accident analysis, not for generating deepfakes of a person's last words. The useful work here isn't building another tool to scrape and reconstruct. It's building guardrails that prevent this kind of misuse by default. If your product touches personal or sensitive information, the core question is not 'what does the law permit?' but 'what does respect demand?'. This incident proves that policy will always lag behind ingenuity.

Our take — your read?

Be the first to weigh in.

Sources
— END OF DISPATCH — Policy