Crew Resource Management for Drone Teams
Many commercial sUAS missions are not flown solo — a visual observer scans for hazards while the remote PIC focuses on the aircraft, a payload operator runs the camera or sensor independently, or a ground crew member manages site access. Crew Resource Management, or CRM, is the set of communication and coordination principles that make a multi-person drone team safer than the same people working in isolation. This lesson explains the core CRM principles and how they apply specifically to sUAS crews built around a remote PIC, visual observer, and payload operator.
What CRM is and where it came from
CRM originated in commercial airline aviation after accident investigators found that many crashes involving fully functional aircraft and qualified crews traced back to breakdowns in communication and coordination between crew members — a co-pilot who noticed a problem but didn't speak up forcefully enough, or a captain who dismissed input from the rest of the crew. CRM training was developed to fix exactly that failure pattern by teaching structured communication, shared situational awareness, and a culture where any crew member is expected to speak up about a safety concern regardless of seniority.
sUAS operations increasingly involve a small crew rather than a single solo pilot — a visual observer, a dedicated payload or camera operator, or ground personnel managing site logistics and public safety. CRM principles transfer directly: a drone crew that communicates poorly is vulnerable to the same kind of preventable accident a poorly coordinated airline crew is, just at a smaller scale.
Defined roles and clear authority
Effective CRM starts with every crew member knowing exactly what their role is and who has final authority. On a Part 107 crew, the remote pilot in command holds final authority and legal responsibility under 14 CFR 107.19, regardless of how many other people are involved in the operation. A visual observer's role, defined under 14 CFR 107.33, is to maintain visual contact with the aircraft, scan for other aircraft and hazards, and communicate that information effectively to the remote PIC — not to make independent flight decisions. Ambiguity about who is responsible for what, or who has final say in a disagreement, is one of the fastest ways to undermine an otherwise capable crew.
Structured communication
CRM emphasizes clear, unambiguous communication rather than assuming information has been understood just because it was said. A visual observer calling out "aircraft approaching from the east, altitude looks similar to ours" is far more useful than a vague "watch out." Structured communication also means confirming receipt — the remote PIC acknowledging "copied, aircraft east, turning to maintain separation" — so the crew has shared confirmation the information landed correctly, not just an assumption that it did.
Assertiveness: the obligation to speak up
A defining feature of CRM culture is that every crew member, regardless of experience level or job title, is expected to voice a safety concern immediately, and the remote PIC is expected to take that input seriously rather than dismiss it because of the crew member's relative inexperience. A visual observer who notices the aircraft drifting toward a person on the ground has both the authority and the obligation to call it out immediately, not to assume the remote PIC has already seen it.
A typical three-person drone crew: defined roles, bidirectional communication, and the remote PIC holding final authority.
View LargerThe required preflight crew briefing
14 CFR 107.49(a) requires the remote PIC to brief every person directly participating in the operation on operating conditions, emergency procedures, contingency procedures, roles and responsibilities, and potential hazards, before the flight begins. This is CRM in its most literal, regulatory form — it's not optional, and it exists specifically to prevent the kind of ambiguity that leads to a coordination failure once the aircraft is in the air. A rushed or skipped briefing removes the shared understanding the rest of CRM depends on.
Worked scenario: a visual observer catches what the PIC missed
You're flying a construction-site progress mapping mission with a visual observer positioned to watch a blind corner of the site the remote PIC can't see directly. The visual observer notices a pickup truck backing into the site's access road, on a path that will bring it under the aircraft's flight line within about 30 seconds. Good CRM means the visual observer calls this out immediately and specifically ("vehicle entering from the access road, will be under our flight path shortly") rather than waiting to see if it becomes a bigger problem, and the remote PIC treats that call as actionable information requiring an immediate response, not a suggestion to be evaluated at leisure.
CRM failures look different in a small crew than an airline cockpit
A common misconception is that CRM only matters for large flight crews with formal cockpit hierarchies. In a two- or three-person drone crew, CRM failures often look smaller and more mundane — a visual observer who assumes the remote PIC already saw something, a payload operator who doesn't mention a camera malfunction because it seems unrelated to flight safety, or a remote PIC who doesn't clearly delegate "watch that side of the site" and assumes it's covered. These failures are just as capable of contributing to an accident as a dramatic cockpit miscommunication, just quieter.
Debriefing after the flight
CRM doesn't end when the aircraft lands. A short debrief — what went well, what communication broke down, what would be handled differently next time — turns each mission into a chance to improve crew coordination for the next one. Skipping the debrief because the flight "went fine" wastes a low-cost opportunity to catch a near-miss or communication gap before it becomes a real problem on a future flight.
| Role | Primary responsibility | Authority | Governing regulation |
|---|---|---|---|
| Remote pilot in command | Overall safety and legal compliance of the operation | Final decision-making authority | 14 CFR 107.19 |
| Visual observer | Maintain visual contact with the aircraft; scan for hazards and other aircraft | Communicates hazards; does not make independent flight decisions | 14 CFR 107.33 |
| Payload/camera operator | Operate the camera or sensor payload independently of flight control | Reports payload issues that could affect the mission or aircraft | No standalone Part 107 section; role defined by the crew briefing |
| Ground crew / site liaison | Manage site access, bystanders, and coordination with site personnel | Reports ground-level hazards to the remote PIC | No standalone Part 107 section; role defined by the crew briefing |
Running the Required Preflight Crew Briefing
Complete this briefing with every crew member before every flight, per 14 CFR 107.49(a).
Confirm operating conditions
Cover current weather, airspace status, and any authorization required for the specific site and time.
Assign and confirm each crew member's role
State explicitly who is watching which part of the operating area, and confirm the visual observer's field of view actually covers it.
Establish communication protocol
Agree on how hazard calls will be phrased and confirmed (e.g. direction, description, PIC acknowledgment) before launch, not improvised mid-flight.
Cover emergency and contingency procedures
Brief what each crew member should do if the aircraft loses link, experiences a fly-away, or an emergency landing becomes necessary.
Invite questions and confirm understanding
Explicitly ask if anyone has questions or concerns before launch — a briefing that's rushed through without checking for understanding doesn't accomplish its purpose.
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Believing CRM only matters for large airline flight crews | CRM's origin in commercial aviation makes it sound scale-dependent | CRM applies to any multi-person operation, including a two- or three-person drone crew. | FAA Risk Management Handbook |
| Assuming a visual observer can make independent flight decisions | A VO is actively watching the aircraft and may seem equally "in control" | The remote PIC holds final decision-making authority under 107.19; the VO's role is to observe and communicate, not to independently decide. | 14 CFR 107.19, 14 CFR 107.33 |
| Treating the preflight crew briefing as optional or a formality | A familiar crew that has flown together before may feel briefings are unnecessary | 14 CFR 107.49(a) requires this briefing before every flight, and it establishes the shared understanding the rest of CRM depends on. | 14 CFR 107.49(a) |
| A junior crew member staying quiet about a concern out of deference | Hesitation to challenge a more experienced remote PIC | CRM culture requires every crew member to voice a safety concern immediately, regardless of experience or seniority. | FAA Risk Management Handbook |
Is a preflight crew briefing legally required, or just good practice?
It's legally required. 14 CFR 107.49(a) requires the remote PIC to brief everyone directly participating in the operation on operating conditions, emergency and contingency procedures, roles and responsibilities, and potential hazards, before the flight.
Can a visual observer overrule the remote PIC's decision?
No. A visual observer's role under 14 CFR 107.33 is to maintain visual contact and communicate hazards effectively; the remote PIC retains final decision-making authority under 107.19. Good CRM means that authority is exercised by taking the VO's input seriously, not by the VO having independent control.
Does CRM apply if I only ever fly solo?
CRM specifically addresses multi-person coordination, so it applies when a crew is involved. A solo pilot's equivalent discipline is Single-Pilot Resource Management, covered in the previous lesson.
What's the point of debriefing after a flight that went fine?
A flight that "went fine" can still contain a near-miss or a communication gap that didn't happen to cause a problem this time. A short debrief captures those lessons while they're fresh, improving coordination on future missions.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.