4 ms·
Pure handwaving speculation here, but this incident is feeling like a result of the limitations of fly-by-cable - specifically taking the tried and true design
by mindslight 8y ago
Pure handwaving speculation here, but this incident is feeling like a result of the limitations of fly-by-cable - specifically taking the tried and true design of fly-by-cable, but augmenting it with motors in parallel to human control.
System integration is a known common source of errors, and what is less formally specified than the effective limits of a human being? If the human(s) are fully in the loop, then the buck stops with them and we know how to socially characterize and educate about failure modes. A pure-computer portion of the loop is characterizable by straight engineering.
But rather, we've got human pilots physically fighting against electrical motors. Either the pilot is right and the computer is wrong (in which case any physical effort expended is a further detriment), or the computer is right and the pilot is wrong (in which case letting the pilot effectively sabotage the computer is wrong). There is no middle ground between these two - weighing the input of a human versus the input of a computer based on them physically fighting is not a sound methodology.
Either powered drive of the trim is necessary or it is not. As it seems to be necessary due to the forces involved, the sensible design is to declare the actuator a critical part of the plane, and make the human input go through the actuator rather than around it.