Earlier quoted context omitted.
There's actually a tendency to reduce the number of different alarms and use screen information to indicate the problem Yes, that'd be good UX. There should be only one actionable task presented at any time to correct errors. In any case, user testing is more important than guidelines. I wonder if grouped alarms make any sense. For instance you can group all alarms related to stalling together, and present the one th…
With the Qantas incident, they had something like 146 msgs appear on the screen spread over about 5 or 6 pages. So they were forcibly distracted from solving the problem from a top-down approach to having to investigate and cancel each of the 146 msgs, and that was why the two extra pilots were such a godsend, they were able to help out.
There are lots of messages because lots of things can go wrong with an aircraft. They aren't all critical "land now" messages, but may be relevant.