Glossary
Crew Resource Management (CRM)
Crew resource management is a set of team practices, born in aviation after a string of 1970s crashes, that uses every crew member's knowledge to prevent error. Its central idea is flattening the authority gradient: making it safe and expected for a junior person to challenge a senior one when they see something wrong.
Crew resource management (CRM) is a body of team-coordination practices that originated in commercial aviation to stop avoidable accidents. It was developed after investigators found that several crashes of mechanically sound aircraft — notably the 1977 Tenerife runway collision and the 1978 United Airlines Flight 173 fuel-exhaustion crash — were caused not by failing machinery but by failing communication. A 1979 NASA workshop named the discipline, and airlines built it into mandatory training over the following decade.12
The information needed to prevent a disaster is often already in the room — held by a co-pilot, an engineer, or a junior officer — but never reaches the person making the decision. CRM exists to close that gap.
The authority gradient
The central idea in CRM is the authority gradient: the perceived power distance between a senior and a junior team member. When the gradient is too steep, the junior person who notices a problem stays silent rather than challenge the captain, and the error proceeds unopposed. CRM training deliberately flattens that gradient so the most junior person present feels safe and obliged to speak up — using techniques such as standardised assertive phrasing ("Captain, I am concerned…"), explicit callouts, and a shared expectation that any crew member can and must flag a deviation. The captain keeps the decision rights; CRM ensures they decide with the full picture.
Why it matters
CRM matters because the same dynamic that downs aeroplanes quietly degrades ordinary organisations: the person closest to the problem is often the most junior, and a steep hierarchy keeps them quiet. Flattening the gradient is what turns scattered knowledge into a working safety net. It is the operational twin of a just culture — the latter makes it safe to report a mistake after the fact, while CRM makes it safe to challenge one as it is happening. A useful after-action review often reveals that someone saw the problem coming but did not feel able to say so; that is an authority-gradient failure, and it is exactly what CRM is built to prevent.
-
SKYbrary, Crew Resource Management (CRM) — skybrary.aero. ↩
-
US Federal Aviation Administration, Advisory Circular 120-51E, Crew Resource Management Training — faa.gov. ↩
Frequently asked
What does CRM stand for in aviation?
What is the authority gradient?
Why was CRM created?
Does CRM apply outside aviation?
Related
Just Culture
A just culture is an organisational approach to error that holds people accountable for reckless choices while treating honest mistakes as a signal to fix the system, not the person. Popularised by Sidney Dekker and David Marx, it replaces "who messed up?" with "what let this happen?" — so people report problems instead of hiding them.
TermAfter-Action Review (AAR)
An after-action review is a short, structured debrief that asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will we change? Originally a US Army practice, it turns experience into improvement — and works best when it's blameless but accountable.
TermDecision Rights
Decision rights define who gets to make which decisions, and at what level, without needing sign-off from above. Setting them clearly is how a team stops routing every choice through one person: cheap, reversible decisions are pushed down with guardrails, while the rare, hard-to-reverse ones are deliberately kept for a more senior call.