THL,
more knowledge wouldn't have helped the crew solve their particular complex behavior issue?
Knowledge always is necessary. But remember the crews that faced and unsolved "different behavior" (i replaced complex by different) were trained in SIM, by all the required Standards and they failed.
I don´t think what happened in many cases was just an issue related to complex systems they piloted. It involved much more, like issues later improved by software updates, hardware improvements, etc.
Even in a perfect complex System the "real world" presents new situations.
And our capabilities are much more dependable on what we learned before a "completely unusual situation". When they arise in complex Systems our capability to solve it (with the several steps since the start of the issue to the adequate solution) IN TIME as you know, is LIMITED.
As a Designer i am not contrary to new solutions, automation, etc.
But i understand the limitations of Systems in the hands of "normal professionals" in "real world environment".
And i respect the K.I.S.S. design approach and threat´s of Murphy´s law.
The crew never of Northwest Airlines 727-25 N26 4US near Thiells Dec 1, 1974 never understood in time what happened to their "simple" a/c in the ferry flight.
Where a simple interlock could have prevented the unreliable air speed that triggered the accident.