Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Ah...because HN famously never has any interest in tech litigation and definitely won't have anything to say if a court finds in Boeing's failure in several years time!

The parallels are fairly obvious: AoA sensors malfunctioned, the situation was recoverable but the pilots were confused by conflicting and absent cockpit feedback and lack of relevant training, the OEM initially placed the blame entirely on the pilot but the problem was resolved with a tech remedy. Plus a whole lot of scope for speculation about Airbus regulatory capture of EASA and whether a first incident should have lead to grounding etc. Sure, with AF447 the issue was sensors having a (known) proneness to systematic failure rather than lack of redundancy and the plane plummeted because a stabilisation system disengaged at the worst possible time. They're obviously also not exactly the same, and the Qantas Flight 72 (different software subsystem input conflict automatically pitches nose down) near miss was a closer analogue, but they're all related to critical software handling edge cases and how guidance and UX might have mitigated issues. But as I said, you won't get much of a picture of the aviation industry from HN.



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

Search: