Hacker News new | past | comments | ask | show | jobs | submit login

This is an old system that works well and reliably for pretty much every incident. I’m not aware of another case of this sort of thing (relevant flight recorder data being overwritten) happening in recent years anyway. If you spend time constantly upgrading systems like this you’re asking for a higher failure rate, for very little gain.

That said, there’s a standard and reliable 25-hour flight voice recorder that solves this problem. But it’s only used outside the US. That’s a regulatory inertia situation and I suspect this incident will speed changes in this area.

However, finally, and particularly in relation to your proposal of streaming cockpit voice recordings to some cloud server. There is some resistance to this (and to longer recordings in general) from air crew on privacy grounds. The privacy issue is less about how much personal info is revealed in a crash situation and more about how easy it would be for a bad actor in management —or whatever operations group runs the audio storage—to listen in on conversations. And you can be sure this would happen if something like your system were implemented without the appropriate regulatory controls (and tbh even with them it would probably still happen).




> I’m not aware of another case of this sort of thing (relevant flight recorder data being overwritten) happening in recent years anyway.

Got me curious how often this happened.

Last example I can find of a CVR being overwritten and not just exploded/missing was in 2018 for an engine fire, similar to this where the flight had to emergency land shortly after take-off. Before that...well a lot of complete failures ("not operative at time of flight") but not many like this scenario.

https://en.wikipedia.org/wiki/List_of_unrecovered_and_unusab...


Here's one in 2017 that was recorded over because they didn't report until after another flight https://en.m.wikipedia.org/wiki/Air_Canada_Flight_759


In 2018 NTSB issued a report (https://www.ntsb.gov/investigations/AccidentReports/Reports/...) listing 17 incidents where CVR was lost due to the recording not being turned off after the incident.

And it also lists 17 more incidents where something happened in a flight and it took more than 2 hours to land so data from the incident was lost.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: