5.1 Crew Resource Management (CRM)
Key Takeaways
- CRM uses all available resources (human, hardware, information) for safe operations.
- Situational awareness has three levels: Perception → Comprehension → Projection.
- Priority order: Aviate → Navigate → Communicate — always fly the aircraft first.
- "Get-there-itis" (pressure to complete missions in unsafe conditions) is a leading cause of accidents.
- Pre-flight briefings should cover mission, roles, airspace, weather, emergencies, and go/no-go criteria.
5.1 Crew Resource Management (CRM)
Crew Resource Management (CRM) is the effective use of all available resources — human, hardware, and information — to achieve safe and efficient flight operations. Originally developed for multi-crew airline operations, CRM principles apply directly to drone operations where teams often include a Remote PIC, visual observer(s), and ground support personnel.
CRM Principles for UAS Operations
1. Communication
- Clear, concise communication between all crew members
- Use standardized terminology — avoid ambiguity
- The Remote PIC should brief all crew members before the flight
- Establish a communication plan (hand signals, radio protocols, verbal calls)
- Challenge and response — crew members should speak up when they see a hazard
2. Situational Awareness (SA)
- Knowing what is happening around you, what it means, and what will happen next
- Three levels of SA:
- Level 1 — Perception: Detecting relevant information (seeing other aircraft, noticing wind changes)
- Level 2 — Comprehension: Understanding what the information means (that aircraft is heading toward us)
- Level 3 — Projection: Predicting what will happen next (we need to descend now to avoid conflict)
3. Task Management
- Prioritize tasks: Aviate → Navigate → Communicate
- Never let secondary tasks (photography, data collection) compromise flight safety
- Delegate tasks appropriately — the Remote PIC should focus on safety, not camera settings
4. Decision Making
- Use structured decision-making processes (see Aeronautical Decision Making below)
- Avoid get-there-itis — the pressure to complete a mission despite deteriorating conditions
- Set personal minimums BEFORE the flight (e.g., "I will not fly if winds exceed 20 knots")
5. Workload Management
- Distribute tasks among crew members to avoid overloading any one person
- During critical phases (takeoff, landing, emergency), minimize non-essential tasks
- Plan for contingencies before they happen, not during the crisis
Common CRM Failures in UAS Operations
| Failure | Example | Consequence |
|---|---|---|
| Poor communication | VO doesn't report approaching helicopter | Near-miss or collision |
| Fixation | PIC focused on camera shot, ignores battery level | Forced landing or crash |
| Get-there-itis | Flying in marginal weather to meet a deadline | Accident or regulation violation |
| Authority gradient | Junior crew afraid to speak up to senior PIC | Missed hazard identification |
| Complacency | Skipping preflight because "I fly here all the time" | Equipment failure or airspace violation |
Pre-Flight Briefing
An effective crew briefing before each operation should cover:
- Mission objectives — what are we trying to accomplish?
- Roles and responsibilities — who is the PIC, VO, ground support?
- Airspace and restrictions — what class, any TFRs, authorizations needed?
- Weather — current and forecast conditions
- Emergency procedures — what to do if [battery fails / control link lost / aircraft enters controlled airspace / person enters flight area]
- Communication plan — how will the team communicate?
- Go/no-go criteria — what conditions will cause us to abort?
For the Exam: CRM questions often present a scenario and ask what the PIC should do. The correct answer almost always involves communication, prioritizing safety over mission completion, and using all available resources.
The primary goal of Crew Resource Management (CRM) is to:
Which of the following is an example of "get-there-itis" in drone operations?
The priority order for a Remote PIC during flight should be: