3 ms·
sure it was an hardware fault that started the event, but now blaming the whole thing on a system that has a warning system, duplicate readings to check faults
by LoSboccacc 7y ago
sure it was an hardware fault that started the event, but now blaming the whole thing on a system that has a warning system, duplicate readings to check faults and bypasses to work around the issue is deeply misguided and ignores simple facts about how safety is attained in aircrafts: trough redundancy and training.
this is completely different from the mcas where the default configuration lacked redundancy, the pilot lacked training and the bypass procedure ineffective unless executed at low speed and high altitude before the dive would lock the trims
- deleted 7y ago[deleted]
- blub 7y agoBoeing's cost-cutting design and their culture of covering their own ass and blaming the pilot seem particularly relevant and relatable.
- LoSboccacc 7y agono, it's not relevant unless you can substantiate how the cost cutting was related to the crash and it'd be an hard case to make, since the faulty system were redundant and the warning themselves were redundant with lights, audibles and whatnot. the hardware did all it could to get the pilot to go around and reassess the situation.