17.3 Crew Resource Management, Dispatch Teamwork & Briefing Technique

17.3 Crew Resource Management, Dispatch Teamwork & Briefing Technique

Crew resource management, including crew communication and coordination, is knowledge area 13 of the 13 listed in 14 CFR § 65.55(a). It is also a training mandate, not merely a knowledge item: 14 CFR § 121.404 requires that no certificate holder use a person as an aircraft dispatcher unless that person has completed approved crew resource management (CRM) or dispatcher resource management (DRM) initial training, with recurrent CRM/DRM training thereafter. Part 65 Appendix A, section VIII.A.3 adds teamwork — communication, problem-solving, and resource management across ATC, flightcrew, maintenance, and operations control workloads — and section VIII.B.1 makes briefing techniques an explicit curriculum item.

CRM is often mis-taught as "being nice on the radio." It is not. CRM is the disciplined use of all available resources — people, equipment, and information — to achieve a safe and efficient operation. For a dispatcher, the most under-used resource is usually another human being: a relief dispatcher, a meteorologist, maintenance control, or the PIC.

---

Why CRM Exists: The Accident Record

CRM was not invented in a classroom. It came from accidents in which nothing mechanical failed that the crew could not have handled.

United 173 is the dispatcher's case. The failure was not fuel planning; it was that an accurate assessment held by someone other than the decision-maker never reached the decision-maker with enough force. That is precisely the failure mode a dispatcher must guard against when a flight's fuel state deteriorates and the dispatcher has the better picture.

---

The Core CRM Skill Set Applied to a Dispatch Desk

---

Closed-Loop Communication

A message is not communicated until it is confirmed received and understood. Closed-loop communication has three legs:

1. Send — the dispatcher transmits a specific, actionable message.
2. Read back — the receiver restates the substance in their own words or verbatim.
3. Confirm — the original sender verifies the read-back was correct, or corrects it.

OPEN LOOP (unsafe)                 CLOSED LOOP (correct)
-------------------                ---------------------
DX: ACARS uplink sent              DX: "KDEN now below alternate mins.
    -> no acknowledgement               New alternate KCOS. Divert fuel
    -> dispatcher assumes read          8,200 lbs. Confirm."
                                   PIC: "Copy, new alternate KCOS,
                                        divert fuel 8,200."
                                   DX: "That is correct. Release
                                        amendment number 2 sent."

[!WARNING] The silent ACARS trap. An uplinked message with no crew response is an open loop. The crew may be on an approach briefing, on a company frequency, or in a printer failure. A dispatcher who treats "sent" as "received" has not communicated. For any release amendment that changes fuel, alternate, destination, or a limitation, obtain an explicit acknowledgement.

Standard phraseology matters for the same reason. Numbers are spoken digit by digit, altitudes and fuel figures are stated with units, and the word "emergency" is never used casually or avoided when it applies — the Avianca 52 lesson.

---

Authority Gradient, Assertiveness, and the Two-Challenge Rule

The authority gradient is the perceived power difference between people in a coordination loop. Both extremes are dangerous:

• Too steep — a junior dispatcher will not challenge a 25-year captain, and a valid safety concern dies at the desk (Tenerife, Air Florida 90).
• Too flat — no one is clearly accountable, and in a time-critical event nobody acts.

Under 14 CFR § 121.533 the dispatcher is not a subordinate of the PIC; they are jointly responsible for preflight planning, delay, and dispatch release, and either may refuse. The dispatcher's leverage is procedural, not personal.

The Two-Challenge Rule

If a concern is voiced twice without a satisfactory response, the plan stops and is re-examined. Two challenges, not two arguments. This converts assertiveness from a personality trait into a procedure that works even for a new dispatcher.

The PACE Escalation Ladder

Advocacy and inquiry is the underlying technique: advocate your position with the reason attached ("I want a second alternate, because both the destination and the first alternate have sub-minimum conditional groups"), then inquire into the other view ("what are you seeing that I'm not?"). A position without a reason invites a rank contest; a position with a reason invites a data discussion.

---

Briefing Technique (Appendix A VIII.B.1)

A briefing is not a recitation of the release. It is a transfer of the decision-relevant picture, and Appendix A requires the course to teach it.

The Dispatcher–PIC Preflight Briefing

Brief in priority order, not document order:

1. The bottom line first. "This release is built around one problem: KBOS convective line arriving with your ETA."
2. Threats, with the numbers. Weather at destination and both alternates, RCAM runway condition codes, MEL/CDL penalties and their performance effect, ATC programs and EDCTs, crew duty limits.
3. The plan and its assumptions. Route, altitude, fuel breakdown, alternates and why those alternates.
4. The triggers and fallbacks. "Bingo is 9,100 lbs. If you are at 9,100 and still holding, go to KPVD — that is why the extra fuel is aboard."
5. The communication plan. How and when you will update — ACARS, the frequency, the position report schedule.
6. Invite challenge, then close the loop. End with a read-back of the critical numbers rather than "any questions?", which reliably produces silence.

The Desk Turnover Briefing

The highest-risk five minutes in an operations control center is a shift change during irregular operations. Section 4.1 covers the legal status of turnover time; the technique is:

• Written and verbal, both. The written log survives; the verbal briefing conveys intent and uncertainty.
• Priority-ordered. Flights in trouble first: low fuel states, holding, diversions in progress, aircraft with deferred items, redispatch flights approaching their decision fix.
• State the plan and the trigger, not just the status. "Flight 412 is holding at PVD, bingo 7,800, currently 9,200, my plan is divert to BDL if not cleared by 2145Z."
• Explicit transfer of operational control. Both dispatchers sign or electronically acknowledge the log. Until then, the outgoing dispatcher still holds it.

---

Coordinating the Wider Team

Appendix A VIII.A.3 names four external workloads. Each has a different failure mode:

A "we" problem, not a "they" problem. When a diversion is developing, the resources that shorten it — a meteorologist's read on the line's motion, maintenance control's judgment on a degraded system, a station's ground handling capability — are exactly the resources an overloaded dispatcher stops calling. Workload management is a CRM skill for that reason.

---

Common ADX Exam Traps

1. Treating CRM as a flightcrew-only requirement. Section 121.404 names aircraft dispatchers explicitly.
2. Calling a sent ACARS message "communicated." Without acknowledgement the loop is open.
3. Answering a dispatcher-PIC disagreement with deference. Under § 121.533 the correct answer is joint resolution on facts and regulation, with either party able to refuse.
4. Reversing PACE. Probe first, Emergency last. A dispatcher who opens with "I am not signing this" has skipped the steps that usually resolve the issue.
5. Confusing assertiveness with aggression. Assertiveness is advocacy plus a stated reason plus inquiry.