4 ms·
If you look at plane crash reports, the disaster is almost always the result of a chain of events. Taken individually, each event is almost insignificant. It's
by GuB-42 8y ago
If you look at plane crash reports, the disaster is almost always the result of a chain of events. Taken individually, each event is almost insignificant. It's the combination that makes the disaster.
In the vase of the Boeing 737 Max the sequence would be something like:
- Boeing decided to fit an oversized engine on an older airframe, which can cause a dangerous stall in some unusual configurations. It is not that much of a problem, they just reduced the flight envelope to exclude these configurations. It is not an unusual thing at all.
- In order to make sure that dangerous situation is never encountered and to limit training expenses for the pilots, they used software. Then again, not unusual.
- In order to avoid writing entirely new software, they extended the functionality of existing software (MCAS). Again, fine.
- First problem: the MCAS, now a critical piece of software wasn't properly requalified.
- Second problem: The AoA sensor, now critical, isn't properly managed.
- Third problem: The pilots weren't properly trained on what to do when MCAS starts crapping out
- Fourth problem: The pilots didn't have enough skill to deal with the unexpected situation.
- Fifth problem: Maybe some pilots dealt with the problem correctly but the report wasn't properly made and accounted for.
Anyone of these steps done right would have averted a disaster. We can't really blame a single one.