CRM — Crew Resource Management

2 contributors Last edited: Anonym Updated: 14. 6. 2026 Revision history

CRM — Crew Resource Management

CRM (Crew Resource Management) is a training concept introduced after accidents caused by human factors (the turning point: Tenerife 1977). It improves communication, situational awareness and team decision-making — and applies to a single-pilot cockpit too (single-pilot CRM).

📷 Image placeholder: a crew in the cockpit / a briefing
We will add a real photo / screenshot.

The pillars of CRM

  • Communication — clear, standardised, assertive (a junior crew member must also speak up).
  • Situational awareness — a shared picture of the situation (shared mental model).
  • Decision-making — structured (the FORDEC model).
  • Workload management — the division of tasks between PF/PM.
  • Error management — errors happen; it is about catching them in time.

FORDEC

Facts → Options → Risks → Decision → Execution → Check. A structured procedure for decision-making under pressure.

Why CRM was created — history

CRM was not born at a desk but from the lessons of accidents. In the 1970s, investigators found that the cause was often not a machine failure but a failure of people and their cooperation — poor communication, loss of awareness, a junior crew member's reluctance to speak up. In 1979 NASA held a workshop on “resource management on the flight deck", from which CRM emerged (originally “Cockpit", later “Crew" Resource Management). The aim is to teach the crew to use all available resources — people, information, technology — for a safe flight.

The triggers: Tenerife and United 173

Two accidents became symbols. At Tenerife (1977) two Boeing 747s collided on the ground — the KLM captain began the takeoff without clearance and a less experienced colleague did not dare intervene firmly enough; 583 people died, to this day the deadliest air accident. United 173 (1978) ended near Portland after running out of fuel — the crew was so focused on a landing gear problem that they overlooked the dwindling fuel, and the captain did not respond to his colleagues' hints. Both tragedies showed that the technology failed only as a consequence of the people failing — and gave rise to CRM.

Communication in the crew

The foundation of CRM is clear, closed-loop communication. Important elements are the readback and confirmation that an instruction has been understood, standard callouts in the phases of flight, a briefing before takeoff and approach, and sharing intentions (“what I am doing now and why"). When everyone knows what is happening and what will follow, the risk of misunderstanding drops considerably. Communication is not meant to be polite padding — it should convey precise information at the right time (see radiotelephony).

Situational awareness

Situational awareness (SA) is a correct and current picture of what is happening — position, altitude, fuel, weather, system status and what comes next. Accidents are often accompanied by a loss of SA: the crew “fixates" on one problem (as with United 173) and loses track of everything else. CRM teaches crews to actively maintain and share awareness, divide attention, use checklists and “check" each other. The key is to recognise the warning signs that the picture does not match reality.

Decision-making under pressure

CRM provides tools for structured decision-making — which is why models such as FORDEC (discussed above) or DECIDE exist. Under time pressure they help you avoid a hasty or, conversely, a delayed step: gather the facts, weigh the options, decide, act and evaluate whether the solution is working. It is important not to forget the automation — who is flying, who is monitoring it and who is “flying the aircraft". A crew always has someone who is primarily flying the aircraft while the other solves the problem.

The sterile cockpit

The sterile cockpit rule prohibits any non-essential activities and conversation in critical phases of flight (typically below 10,000 feet, i.e. takeoff, climb, descent, approach). It was introduced after accidents in which a conversation distracted the crew at the most sensitive moment. The point is full concentration where there is the least time to correct a mistake. It is a simple but very effective rule — and shows nicely how CRM changes behaviour, not just technology.

📷 Image placeholder: a crew during the pre-approach briefing — teamwork

Authority vs. assertiveness

A sensitive topic is the authority gradient — the difference in status between the captain and the first officer. A gradient that is too steep is dangerous: the junior crew member is afraid to speak up (Tenerife). One that is too flat creates confusion about who is in command. CRM seeks a healthy balance: the captain decides but listens, and the first officer knows how to speak up assertively. The two-challenge rule helps — if there is no response to repeated warnings, the colleague may take the initiative. Safety takes precedence over hierarchy.

NOTECHS — non-technical skills

The European NOTECHS framework names the non-technical skills that can be assessed and trained. It divides them into four areas: cooperation, leadership and managerial skills, situation awareness and decision making. Thanks to NOTECHS, CRM can be assessed objectively during training and checks — it is not just about “soft skills" but a measurable part of pilot competence.

Threat and Error Management (TEM)

The modern view of CRM builds on TEM (Threat and Error Management). It starts from the premise that threats (weather, traffic, fatigue, technology) and human errors are inevitable — the aim is not to deny them but to recognise and manage them before they develop into an undesired aircraft state and then an incident. The crew works as the last line of defence that breaks the chain. TEM is today the backbone of CRM training:

Threat & Error Management (TEM) THREATS weather, traffic, fatigue, technology ERRORS wrong action, oversight UNDESIRED STATE deviation from normal CRM breaks the chain at every step — it recognises, shares and corrects.

CRM today and in the simulator

CRM is today a mandatory part of training for airline crews (required by both EASA and the FAA) and is also practised in LOFT (Line Oriented Flight Training) — realistic scenarios in the simulator. The principles also apply to a single-pilot crew (single-pilot CRM) and can be applied in the sim too: clear communication on VATSIM/IVAO, a briefing before the flight, sharing tasks when flying as a pair (e.g. pilot + navigator) and calm, structured problem-solving. Thanks to CRM, even a virtual pilot becomes more disciplined and safer.

Practical steps — simulator

Even solo, practise callouts (“1000 to go", “approaching minimums", “going around"). In multi-crew modules (the DCS F-14 with JESTER, cooperative multiplayer), practise dividing roles and communicating.

FAQ

Does CRM apply to a single pilot too? Yes — single-pilot resource management (using the autopilot, ATC, checklists).

Why was it created? After Tenerife 1977 and other accidents where communication/decision-making failed, not technology.

Related links


Sources (verified 06/2026): ICAO Doc 9683 (Human Factors), EASA CRM training; human performance textbooks. An educational summary.