History of CRM: 1979 to Today

How three accidents changed the way we think about the flight deck — and why that change has saved more lives than any other safety intervention in aviation history.

Three Accidents That Built a Discipline

On 27 March 1977, the deadliest accident in aviation history occurred on a fog-bound runway in Tenerife. The captain of KLM 4805 began his takeoff roll without clearance. His co-pilot and flight engineer had the information that would have prevented the accident. Neither could deliver it in a form that the captain was required to act upon. Five hundred and eighty-three people died.

Two years earlier, the crew of Eastern Air Lines Flight 401 had collectively focused their attention on a burned-out landing gear indicator bulb while their state-of-the-art L-1011 flew, unmonitored, into the Florida Everglades. Four qualified crew members. Zero people monitoring the aircraft. One hundred and one fatalities.

And in December 1978, United Air Lines Flight 173 ran out of fuel over Portland, Oregon, while the captain troubleshot a landing gear anomaly. The first officer and flight engineer mentioned the fuel state. Repeatedly. In language that was correct, factual, and insufficient to compel action. Ten people died.

Three accidents. Three different failure modes. One common thread: the flight deck was not functioning as a team. The captain was the sole decision-maker. Junior crew members who possessed safety-critical information lacked the cultural authority to act on it. The hierarchy of the cockpit was killing people.

Tenerife, Eastern 401, and United 173 are not three separate accidents. They are three expressions of the same systemic failure: a flight deck culture that had no architecture for translating junior crew knowledge into captain action.

The 1979 NASA Workshop and the Birth of CRM

In June 1979, NASA convened a workshop at Ames Research Center titled ‘Resource Management on the Flightdeck.’ It was, in retrospect, one of the most consequential aviation safety events in history. The workshop brought together researchers, airline representatives, and regulators to address the problem that Tenerife and the accidents that preceded it had defined: the cockpit’s human performance system was broken.

The workshop produced a framework — initially called Cockpit Resource Management, later broadened to Crew Resource Management — that reframed the flight deck as a team system. It identified the key competencies: leadership and authority management, situational awareness, decision-making, communication, and workload management. It argued that these were not soft skills peripheral to technical flying — they were hard safety requirements that could be identified, trained, and assessed.

United Airlines, working with the NASA researcher Robert Helmreich and motivated directly by the UAL 173 accident, developed the first formal CRM training programme in 1981. It was the first systematic attempt to change the authority architecture of the commercial flight deck.

Six Generations of CRM

CRM has evolved significantly since 1981. Aviation safety researchers typically describe its development in generations. First-generation CRM (early 1980s) focused on changing the captain’s interpersonal style — making captains less authoritarian. This was limited; it addressed the symptom without the system.

Second-generation CRM expanded to address specific cockpit skills — decision-making frameworks, briefing structures, situational awareness models. Third-generation CRM integrated CRM into recurrent training and simulator checks, moving it from a one-off course to an ongoing practice.

Fourth-generation CRM introduced the LOSA (Line Operations Safety Audit) concept — directly observing CRM behaviour on real line operations to assess whether training was producing operational change. Fifth-generation CRM brought in Threat and Error Management (TEM) as the organising framework.

Today’s sixth-generation CRM is evidence-based, culturally adapted, and integrated across all aviation specialisms — cabin crew, maintenance, dispatch, and ATC. It is no longer a course that pilots attend. It is the operational philosophy of the flight deck.

CRM did not reach its current form in 1981. It evolved through six generations of research, accident investigation, and operational feedback. The version being trained today is not the version that responded to Tenerife — it is the version that responded to everything since.

What CRM Has Achieved

The impact of CRM on aviation safety is difficult to isolate precisely — aviation safety improvement is the product of many concurrent initiatives. But the NTSB, EASA, and academic researchers consistently identify CRM as among the most significant single contributions to the reduction in aviation fatalities since the 1980s.

US Airways 1549 — in which Captain Sullenberger and First Officer Skiles managed a dual engine failure over New York City through textbook CRM — is the most public demonstration of what the framework achieves at its best. United 232 in 1989, where four crew members and a deadheading instructor improvised an impossible recovery through explicit team coordination, is the earlier landmark.

The flight deck in 2025 is a fundamentally different authority system from the flight deck of 1977. The captain is still in command. But every crew member now has not just the right but the trained professional obligation to speak up, assert, escalate, and if necessary physically intervene when safety is at risk. That change did not happen by accident. It happened because three accidents made the cost of the old system unmistakably visible — and because the aviation community built a new one.

 

Key Takeaway

CRM was not invented to make pilots nicer. It was invented to save lives by redesigning the authority architecture of the flight deck. It has been the most important safety training development in aviation history — and its ongoing evolution reflects the fact that the problem it addresses never fully disappears.

 

Related Content on Aviation Risk Lab

Human Factors Pillar Page: https://aviationrisklab.com/human-factors/

Case Study: Tenerife 1977: https://aviationrisklab.com/case-studies/tenerife-1977/

Case Study: United 173: https://aviationrisklab.com/case-studies/united-173/

Case Study: United 232: https://aviationrisklab.com/case-studies/united-232/

Crew Resource Management: https://aviationrisklab.com/crew-resource-management/