3 ms·
One could say that "the point" of MCAS was to be an implementation detail, something that you would often deliberately hide from software documentation so that
by cpgxiii 1y ago
One could say that "the point" of MCAS was to be an implementation detail, something that you would often deliberately hide from software documentation so that users don't design around internal details.
There's something of a history of aerospace vendors omitting "implementation details" that end up contributing to serious accidents (e.g. if you get an Airbus far enough out of the normal envelope protections, you lose stall warning), and an equally sordid history of flight and maintenance crews improvising procedures to the observed (rather than designed/specified) behavior of aircraft systems.
Arguably, the single biggest systematic risk in the current pilot training system is that crews overlearn to the implementation details of their training, rather than the actual principles and flight manuals (e.g. training inadvertently training for quick engine shutdowns, when the consequences of shutting down the wrong engine in reality are much more serious).
- sofixa 1y ago> There's something of a history of aerospace vendors omitting "implementation details" that end up contributing to serious accidents (e.g. if you get an Airbus far enough out of the normal envelope protections, you lose stall warning), And Airbus control laws and protections are well defined and studied by pilots training for them.
- cpgxiii 1y agoThey are now, just as MCAS behavior is well-defined and covered in conversion training now. They were not covered as well prior to AF447.