Re: Hey software, get the fuck out of the way!
“Sounds like that angle of attack sensor should be triplicated. How else can the software decide which sensor is bad, if both produce plausible values (one being wrong, but not impossibly so).
- And the same for goes for all other safety-critical sensors.”
Yes, I’m somewhat perplexed by the lack of a “tie breaker”.
Again, comparing with the Airbus implementation:
The Airbus aircraft generally have 3 ADIRUs (Air Data and Inertial Referencing Units), each with its own AoA sensor. And yes, there is a voting system so that a rogue sensor will merely cause a DISAGREE state and is disregarded, rather than something potentially rather more catastrophic.