Operational calm.
On December 28, 1978, United Airlines Flight 173 circled Portland for over an hour while the crew tried to diagnose a landing-gear indicator light. They were so absorbed in the gear problem, no one monitored the fuel gauges, and the aircraft ran out of fuel and crashed short of the airport. The lesson emerging from this accident, and from a string of similar ones through the 1970s, became Crew Resource Management (CRM): the discipline of making sure the WHOLE flight deck stays aware of the whole situation, instead of everyone tunnel-visioning on the one problem feeling most urgent in the moment.
This single accident rewired an entire industry’s approach to teamwork under pressure, and the fix was almost entirely procedural, not technological. Junior crew members were trained and explicitly empowered to speak up when something looked wrong, even to a senior captain. Checklists were restructured to force a deliberate pause and cross-check rather than letting one fixation consume the whole crew’s attention. None of it required new instruments. It required a system assuming people would panic and fixate under pressure, and built the process to catch this specific failure mode.
“Aviate, navigate, communicate” is the standard priority order pilots are trained to fall back on in any emergency: first fly the aircraft, then figure out where it needs to go, then tell someone what is happening. Applied outside a cockpit, the same order works for any crisis: keep the operation running first, decide direction second, update stakeholders third. Panic reorders this sequence, usually starting with communication, which is exactly backwards when the operation itself still needs someone’s full attention.
This exact framework, cockpit discipline ported into the boardroom and the build pipeline, already runs in full on the Piloting Mindsets page.