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

You 100% certain your system won't false? Playing a loud horn/sound on final is a good way to overload the crew and needlessly cause a crash.



If thee crew is this easily rattled, how come we trust their communication skills so much?

I see your point, but I think that the rate of false positives can be tuned to be very low, with a good design of the system.

In the rare event of a false positive, it’s still extremely unlikely that this will cause any more disruption than the co-pilot pushing a button and double checking with the tower.


I never said the crews were easily rattled. I can see you're more interested in argument than discussion so I'll leave you with this thought: software engineers can throw features into a product and A/B test it. When aviation engineers throw features into a cockpit without thinking through EVERY side, accidents happen. You're technically correct that, when skies are clear and the crew is idle, adding sounds and buttons is no big deal. But that's obvious, and not the scenario you need to be thinking about.

EDIT: I thought it was obvious from context but maybe not... Imagine I said "overload an already heavily loaded crew." An unloaded crew isn't normally worth worrying about.


I'm not sure a properly-designed warning would add much load to the flight crew.

They're already listening for "go around" commands from ATC. This would just be an automated "go around" based on runway sensor data.




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

Search: