Crew Resource Management in the Fire Service: Preventing Errors Under Pressure

In 1978, United Airlines Flight 173 circled above Portland, Oregon, while the captain focused on a landing gear problem. The crew knew they were running out of fuel. The flight engineer mentioned it multiple times. But the hierarchical culture of the cockpit at that time made it difficult for junior crew members to directly challenge the captain's decisions. The plane ran out of fuel and crashed six miles short of the runway. Ten people died. The captain survived, but 189 people on that aircraft came close to dying because a crew did not have the skills or the culture to effectively communicate critical safety information up the chain of command.

That crash, along with several other high-profile aviation accidents in the 1970s, led to the development of Crew Resource Management. CRM is a set of training principles designed to reduce human error in high-stakes environments by improving communication, situational awareness, decision-making, and teamwork. It revolutionized aviation safety. Fatal accidents dropped dramatically after airlines adopted CRM training.

The fire service operates in strikingly similar conditions. We work in high-stress, high-consequence environments where decisions have to be made quickly with incomplete information. We operate in hierarchical organizations where rank can sometimes inhibit the flow of critical safety information. We deal with fatigue, task overload, and communication breakdowns. The same types of human errors that kill people in aviation kill people on the fireground. CRM can help us reduce those errors.

The International Association of Fire Chiefs at iafc.org has published resources on officer development that include CRM concepts as part of effective fire service leadership. Their materials are worth reviewing if you are working to build stronger communication and decision-making practices in your department.

Understanding Human Error

CRM starts with a fundamental premise: humans make errors. Not because they are bad at their jobs, but because human cognitive systems have inherent limitations that become more pronounced under stress, fatigue, time pressure, and task overload, exactly the conditions we operate in during emergency responses.

There are several categories of human error that CRM addresses. Skill-based errors are mistakes in routine tasks that you normally perform correctly. You know how to do it, but in the moment, you make an error. Pulling the wrong lever, turning the wrong valve, going to the wrong floor. These errors increase dramatically under stress and fatigue.

Decision errors are mistakes in judgment. You have the information, but you reach the wrong conclusion or choose the wrong course of action. On the fireground, this might mean choosing an offensive attack on a building that is too far gone, or searching the wrong area first based on incorrect assumptions about where victims are located.

Perceptual errors occur when you misinterpret information or fail to perceive critical cues. You see smoke but do not register that its color and velocity indicate backdraft conditions. You hear a report from an interior crew but do not process that they are telling you conditions are deteriorating rapidly.

Communication errors are failures in transmitting or receiving information. You give an order that is misunderstood. A crew reports a hazard but the message does not reach the people who need it. Dispatch provides updated information but you are too task-saturated to absorb it.

CRM does not eliminate these errors. That is impossible. What it does is create systems and behaviors that catch errors before they lead to catastrophic outcomes.

Key CRM Principles for the Fireground

Assertive Communication

One of the most important CRM concepts for the fire service is assertive communication, specifically the idea that any member of the team has both the right and the responsibility to speak up when they perceive a safety concern, regardless of rank.

In the fire service, we have a strong tradition of following orders and respecting the chain of command. That tradition serves us well in many ways. But it can also create situations where a firefighter sees something dangerous, knows something is wrong, but hesitates to speak up because the officer has already made a decision. CRM teaches us that there is a difference between challenging authority and advocating for safety.

Assertive communication does not mean being insubordinate. It means clearly and directly stating your concern with the supporting information. Instead of hinting or hoping the officer notices, you say, "Captain, I am seeing heavy smoke pushing from the eaves on Side Charlie and I am concerned we may have extension into the attic that we have not addressed." That is not a challenge. That is critical information delivered in a way that supports better decision-making.

For this to work, officers have to create an environment where assertive communication is welcomed, not punished. If a firefighter speaks up about a concern and gets shut down or mocked, they will not speak up the next time. And the next time might be the time it matters most.

Situational Awareness

CRM defines situational awareness as knowing what is going on around you and understanding what it means for the near future. On the fireground, this means maintaining a mental picture of fire conditions, crew locations, resource status, elapsed time, and building conditions, and continuously updating that picture as new information comes in.

Situational awareness degrades under task overload. When you are focused on one task, your awareness of everything else shrinks. This is why the incident commander who gets sucked into a tactical task loses the big picture. It is why the nozzle firefighter who is locked into the fire in front of them may not notice that conditions behind them have changed. It is why the driver who is focused on pump operations may not see that the supply line is compromised.

CRM teaches strategies for maintaining situational awareness, including regular communication among team members, structured check-ins, and deliberate scanning of the environment. On the fireground, this translates to practices like regular personnel accountability reports, officer check-ins with interior crews on a timed cycle, and the habit of periodically stepping back from your immediate task to reassess the overall situation.

Workload Management

CRM recognizes that people have a finite capacity for managing tasks and information. When workload exceeds that capacity, performance degrades and errors increase. This is directly applicable to the fireground, where the first-arriving company officer can find themselves simultaneously managing tactical operations, command communications, crew tracking, and decision-making.

The CRM solution is to distribute workload across the team rather than concentrating it on one person. On the fireground, this means delegating tasks, using tactical worksheets or aides to reduce the cognitive burden on the commander, and recognizing when an individual is becoming task-saturated so that responsibilities can be redistributed.

A practical example: the first-arriving officer who is trying to run command while also managing their crew's tactical assignment is splitting their cognitive resources between two demanding tasks. CRM would say that as soon as possible, one of those tasks needs to be handed off. Either transfer command to the next arriving officer, or assign the crew's tactical task to an experienced firefighter and focus on command.

Structured Decision-Making

Under pressure, people tend to default to the first option that seems reasonable rather than systematically evaluating alternatives. CRM teaches structured approaches to decision-making that help counteract this tendency.

One practical tool is the PACE model: Primary plan, Alternate plan, Contingency plan, Emergency plan. Before committing to a course of action, quickly consider what happens if your primary plan does not work. What is your backup? If that fails, what is your contingency? And if everything goes wrong, what is your emergency plan?

On the fireground, this might look like: Primary plan is offensive fire attack through the front door. Alternate plan is a transitional attack from the exterior if interior conditions are too severe. Contingency is to go defensive and set up master streams. Emergency plan is an immediate withdrawal and accountability check if structural collapse or rapid fire progression is observed.

You do not need to write this down during a fire. But if you train yourself to think through alternatives before committing to a plan, you make better decisions and you recover faster when conditions change.

Error Trapping and Cross-Checking

In aviation, CRM encourages crew members to actively cross-check each other's actions. The co-pilot verifies the captain's settings. The flight engineer confirms fuel calculations independently. This redundancy catches errors before they cascade into accidents.

On the fireground, error trapping might look like the backup firefighter confirming that the nozzle team is on the correct hoseline before they advance. It might look like the driver confirming the pump pressure with the officer before charging the line. It might look like a crew member double-checking the floor number before committing to a search.

Building these cross-checking behaviors into your standard operations takes practice, but it creates a safety net that catches the small errors before they become big problems.

Implementing CRM in Your Department

CRM is not a one-time class. It is a culture change. You can teach the principles in a classroom, but they only stick if they are reinforced in daily operations and training.

Start by introducing the concepts during company-level training. Discuss real incidents where communication failures, loss of situational awareness, or decision errors contributed to poor outcomes. Use NIOSH LODD reports and near-miss reports as case studies.

Practice assertive communication during drills. Create scenarios where a crew member has information that the officer does not, and practice how that information gets communicated up. Debrief every drill with CRM principles in mind. Did everyone maintain situational awareness? Were there communication breakdowns? Did anyone feel unable to speak up about a concern?

The departments that have successfully implemented CRM see measurable improvements in communication, fewer near-miss events, and a culture where safety concerns are raised early rather than after something goes wrong. It takes time and commitment, but the payoff is real.

StruckBox was built on the belief that better training produces better decisions under pressure. Our scenario-based tools help you practice the situational awareness and decision-making skills that CRM principles demand. Start training at struckbox.com.