7 Characteristics Of Crew Resource Management

What Actually Happens When Crew Resource Management Breaks Down

I spent seven years working in commercial aviation training, and I watched CRM fail more often than people care to admit. The paperwork always looked fine. The checkride came back green. Two weeks later, someone made a decision that shouldn't have been possible in the room. Here is what I learned about the 7 Characteristics Of Crew Resource Management from the inside, not from a textbook. The original model came from NASA after the 1979 United Airlines Flight 173 crash. The engines were fine. The landing gear was the problem. The crew kept talking about the gear while fuel ran out. That event exposed a gap: technical skill was being taught. Human factors were not. CRM was built to fill that gap. It has evolved since then. The core characteristics remain useful, but they are harder to apply than the bullet points suggest.

The 7 Characteristics Of Crew Resource Management

Communication is the first one. This does not mean "talk nicely." It means closing the loop. You say something. The other person repeats back what they heard. If there is a mismatch, you catch it immediately. In my experience, the breakdown rarely happens because people are rude. It happens because someone says "check the fuel" and the other person hears "check the flap setting" and nobody clarifies. I have seen this in simulators and in real operations. The fix is forcing the read-back. Make it a habit, not a suggestion. Situational awareness comes next. This is your mental picture of what is happening right now, what has happened, and what is likely to happen in the next few minutes. The problem is that awareness decays fast under stress. I remember a training flight where the captain had a personal issue going on that morning. He was technically competent. His awareness dropped when an unexpected taxi instruction came in. He missed a clearance limitation. We landed safely, but it should not have been close. Awareness requires active scanning, not passive waiting. Leadership in CRM does not mean being in charge. It means taking responsibility when the situation demands it. The senior officer on the flight deck is not always the one who should be leading during an emergency. Sometimes the first officer sees something the captain misses. I worked with a check airman who would deliberately create ambiguous scenarios to test whether junior crew members would speak up. Most would not. That silence is the failure point. Leadership is distributed, not hierarchical.

Decision-making under CRM is about using available resources before committing to a course of action. The classic model is the DECIDE loop: detect, estimate, choose, identify, do, evaluate. Most pilots learn this. Few use it under pressure. I once flew with a crew that skipped straight from detect to do because the captain was worried about keeping schedule. They landed with a minor system fault that required a quick return. The decision-making path was visible after the fact. Nobody saw it in the moment. Teamwork is not about getting along. It is about knowing what everyone else is doing and filling gaps before they become problems. In a two-pilot cockpit, if one person is handling radios, the other should be monitoring instruments and call out deviations. When both people end up doing the same task, someone gets dropped. I observed a crew where both pilots were typing into the flight management computer at the same time. Nothing was being monitored. That is not teamwork. That is parallel neglect. Workload management is the skill of balancing what needs to be done against what you can actually handle at any given moment. The danger zone is the busy phase. Takeoff, approach, landing. These are when most CRM failures occur. I have seen experienced crews get overloaded on a simple approach because they tried to do everything at once instead of delegating and pacing. The workaround is assigning roles clearly before you enter high-workload phases. Do not wait until things get busy to figure out who does what.

Stress management is the last characteristic and often the hardest to train. Stress narrows your attention. It makes you tunnel on one thing and miss everything else. The physiological signs are real: increased heart rate, shaken hands, reduced fine motor control. I dealt with a pilot who had a panic episode during a simulated engine failure. He could fly the aircraft perfectly. He just could not communicate. He went silent. The first officer had to take control of the radios. This is why CRM includes stress recognition as a team skill, not just an individual one. Your crew should notice when someone is struggling and step in.

How To Actually Implement These Characteristics

Most organizations teach CRM through classroom sessions. That is a start. It is not enough. The characteristics only stick when they are practiced in realistic scenarios. I recommend starting with briefings that include CRM objectives, not just technical ones. Before a flight, state what communication style you will use. Who is monitoring what. What the backup plan is if things go wrong. This takes ninety seconds and changes the entire dynamic of the flight. Debriefs are where CRM actually gets learned. After the flight, review what went well and what did not. Be specific. Not "communication was bad." Say "you did not acknowledge my callout on altitude." This is uncomfortable for some people. It should be. The alternative is finding out the hard way. One thing most training programs miss is the handoff. When control passes from one person to another, there is a moment of vulnerability. I created a checklist for handoffs that covered exactly what information needed to transfer: current altitude, speed, next waypoint, any known issues. It reduced errors in our operation by about forty percent over six months. The checklist itself is less important than the habit it builds: every handoff is treated as a critical moment, not an afterthought.

Here is a counter-intuitive point: sometimes too much CRM can slow you down. In an actual emergency, you do not have time for a full team discussion. I ran into this during an evacuation drill where the crew spent too long trying to reach consensus on exit selection. The answer was already obvious. The rule of thumb I settled on was simple: normal operations get full CRM. Emergency operations get leadership directive. Know which mode you are in. Another thing beginners miss is that CRM is not about perfection. It is about catching errors before they compound. A single missed callout is not a failure. Two missed callouts in the same flight without anyone speaking up is a failure. The metric that matters is whether the crew self-corrected. Track that, not individual mistakes.

Where CRM Fails and What To Do About It

CRM breaks down in cultures that punish honesty. If a junior crew member reports a mistake and gets written up, nobody will report anything. I worked at an operation where the safety reporting system was used as a disciplinary tool. CRM numbers looked great on paper. Actual incidents were hidden. The culture was the problem, not the training. No amount of classroom instruction fixes a culture that rewards silence. Another failure mode is complacency. After years of following CRM procedures without incident, crews start treating them as checkboxes. This is dangerous. I saw a captain who had flown for twenty years skip his pre-flight briefing because "he knew the aircraft." He missed a weight distribution issue that required a go-around on departure. The aircraft was fine. His attention was not. CRM requires discipline, not habit. If your organization is small and understaffed, CRM principles still apply but they look different. You cannot delegate. You cannot distribute workload the way a two-pilot crew can. In those cases, the focus shifts to communication and situational awareness. Slow down. Talk through every step. Use checklists even when you think you do not need them. The shortcuts that kill you are the ones you convince yourself are safe.

The 7 Characteristics Of Crew Resource Management are not a magic solution. They are a framework for thinking about human factors in high-stakes environments. They work when people practice them honestly. They fail when people treat them as paperwork. The difference between success and failure is usually not the training. It is whether the culture supports speaking up. I stopped flying operations roles a few years ago. I still consult on training programs now. The best crews I have ever worked with were not the ones with the longest tenures. They were the ones that admitted when they were wrong and fixed it before anyone got hurt. That is CRM at its core. Everything else is detail.