5.1 Crew Resource Management (CRM)

Crew Resource Management for Small UAS

Crew Resource Management (CRM) is the effective use of all available resources — human, hardware, and information — to achieve a safe and efficient flight. The Federal Aviation Administration (FAA) borrowed CRM from airline cockpits, but it maps cleanly onto a Part 107 operation that often pairs a Remote Pilot in Command (Remote PIC) with one or more visual observers (VOs) and ground support personnel. On the exam, CRM questions are almost always scenarios: you are asked what the crew should do, and the credited answer involves communicating, sharing workload, and prioritizing safety over the mission.

The Four Pillars

• Communication — Use standardized, unambiguous phrasing. The Remote PIC briefs every crew member before launch and establishes a backup channel (hand signals, radio, agreed verbal calls) in case the primary fails. CRM expects a challenge-and-response culture: any crew member who sees a hazard must speak up, and the PIC must invite it.
• Situational awareness (SA) — Knowing what is happening, what it means, and what will happen next.
• Task and workload management — Distributing duties so no one person saturates.
• Decision making — Applying a structured model (covered in 5.2) rather than reacting.

The Three Levels of Situational Awareness

Most SA breakdowns are Level 1 failures — the cue was simply never detected because the crew was heads-down on a payload screen.

Aviate, Navigate, Communicate

The single most-tested CRM rule is the priority order. Aviate (keep positive control of the aircraft) always comes first; Navigate (keep it clear of obstacles, airspace, and people) second; Communicate (talk to crew or, rarely, Air Traffic Control) last. A classic trap answer reverses this — for example, telling you to radio Air Traffic Control before stabilizing a drifting aircraft.

Common CRM Failures

A steep authority gradient is worth understanding: when the PIC projects an intimidating, unquestionable demeanor, crew members suppress safety concerns. Good CRM deliberately flattens that gradient by inviting input.

The Pre-Flight Crew Briefing

Every commercial sortie should open with a briefing covering, at minimum:

1. Mission objectives — what are we accomplishing and what are the deliverables?
2. Roles — who is Remote PIC, who is VO, who handles ground security?
3. Airspace and authorizations — airspace class, any Temporary Flight Restrictions (TFRs), Low Altitude Authorization and Notification Capability (LAANC) status.
4. Weather — current and forecast, with the day's wind/visibility limits stated aloud.
5. Emergency procedures — lost link, low battery, manned-aircraft incursion, person entering the area.
6. Communication plan — primary and backup channels.
7. Go/no-go criteria — the specific conditions that will abort the flight.

Notice that the Remote PIC may delegate manipulation of the controls to another person, but the Remote PIC remains responsible for the operation at all times — a frequently tested point that CRM reinforces: resources are shared, accountability is not.

Resources Beyond the Crew

CRM is not only about people. The "all available resources" definition deliberately includes hardware and information. Hardware resources include the aircraft's telemetry display, the geofence and Return-to-Home settings, obstacle-avoidance sensors, and the controller's battery and signal-strength readouts. Information resources include the sectional chart, the latest METAR and TAF, NOTAMs, the B4UFLY result, and the manufacturer's flight manual. A pilot who ignores a clear low-battery telemetry warning, or who launches without pulling current weather, has failed at CRM just as surely as one who silences a crew member.

On the exam, an answer that says "use the available information" or "consult the data before deciding" is usually the credited choice.

Workload Management in Practice

Workload spikes during launch, recovery, and any abnormal event — exactly when a saturated pilot makes mistakes. Good CRM front-loads the easy work: program the mission, confirm the geofence, and brief contingencies on the ground, while you have spare mental capacity. During the flight, the Remote PIC should stay focused on flying and traffic-watching while delegating secondary duties — logging, photography review, client interaction — to other crew. When workload suddenly rises, shed the non-essential tasks first: a CRM-sound pilot stops narrating to the client and resumes flying the aircraft.

The Visual Observer's Role

The visual observer (VO) is the most-tested CRM resource for small UAS. A VO is used to help maintain visual line of sight (VLOS) and scan for other aircraft and hazards. Three rules appear often on the exam: (1) the Remote PIC, the person manipulating the controls, and any VO must be able to communicate throughout the operation; (2) the VO and Remote PIC coordinate so that together they meet the see-and-avoid duty, but the VO does not transfer legal responsibility away from the Remote PIC; and (3) the VO supplements VLOS — it does not replace the requirement that the aircraft remain capable of being seen.

Sterile-Cockpit Discipline

Borrowed from airline CRM, the sterile-cockpit concept means no non-essential conversation or distraction during critical phases — for a drone that is launch, recovery, and any abnormal event. A client asking questions or a phone call during recovery is a classic distraction the exam expects you to defer. The CRM-correct response is to finish the safety-critical task first, then handle the interruption.

For the Exam: When a CRM scenario offers a tempting "complete the job" answer and a "stop, communicate, reassess" answer, the safety-first choice is correct. The PIC who uses the VO, consults available data, and protects the priority order is always the credited response.