Study guide

17.3 Crew Resource Management, Dispatch Teamwork & Briefing Technique

FAA ADX Aircraft Dispatcher Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Regulations & Dispatcher Certification (14 CFR Part 65)

1.1 14 CFR Part 65 Eligibility, Privileges, Limitations & Retesting 1.2 Operational Control & Shared Dispatcher-PIC Responsibility 1.3 Dispatch Release Requirements, Amendments & Records

2 Chapter 2: Part 121 Domestic, Flag & Supplemental Operating Rules

2.1 Domestic vs. Flag vs. Supplemental Operational Rules 2.2 Dispatch Weather Minimums & Departure Rules 2.3 Takeoff Alternates & Clean Aircraft Concept

3 Chapter 3: Destination Alternates, Alternate Minimums & Redispatch

3.1 Destination Alternate Requirements (1-2-3 Rule & Flag/Supplemental) 3.2 Alternate Airport Weather Minimums (OpSpecs Table C055) 3.3 Marginal Weather Rule & Second Alternate Selection 3.4 En Route Redispatch & Reclearance Procedures

4 Chapter 4: Dispatcher & Flightcrew Duty Limitations and Rest (14 CFR § 121.465 & Part 117)

4.1 Dispatcher Duty Time Limitations & Rest Requirements 4.2 Flightcrew Duty & Rest Requirements (14 CFR Part 117) 4.3 Dispatcher Qualifications, Recurrent Training & Operating Familiarization

5 Chapter 5: Minimum Equipment Lists (MEL), CDL & Maintenance Dispatch

5.1 Master Minimum Equipment List (MMEL) & Operator MEL 5.2 Configuration Deviation List (CDL) & Missing Secondary Airframe Parts 5.3 Dispatch with Inoperative Equipment, Logbooks & Special Flight Permits

6 Chapter 6: Aviation Meteorology — Atmosphere, Pressure Systems & Fronts

6.1 Atmospheric Structure, Pressure Systems & Altimetry 6.2 Air Masses & Frontal Systems 6.3 Clouds, Atmospheric Stability & Fog 6.4 Earth Motion, Global Circulation & Regional/Local Weather Regimes

7 Chapter 7: Hazardous Aviation Weather — Convection, Icing & Turbulence

7.1 Thunderstorms & Severe Convection 7.2 Structural & Induction Icing 7.3 Turbulence, Jet Streams & Clear Air Turbulence (CAT) 7.4 Low-Level Windshear & Microburst Detection Systems

8 Chapter 8: Aviation Weather Products, Observations & Forecasts

8.1 Surface Weather Observations (METAR & SPECI) 8.2 Terminal Aerodrome Forecasts (TAF) 8.3 In-Flight Weather Advisories (PIREPs, AIRMETs, SIGMETs) 8.4 Upper-Air Analysis & Prognostic Weather Charts

9 Chapter 9: Airspace Structure, Air Traffic Control & Traffic Management

9.1 Airspace Classes & Operating Rules 9.2 Special Use Airspace & Temporary Flight Restrictions 9.3 Air Traffic Control Flow Management & Initiatives 9.4 NOTAM System & Airport Field Condition Reporting 9.5 Flight Plan Filing: Domestic and International (ICAO) Flight Plans

10 Chapter 10: IFR Navigation, Airway Structure & Charting

10.1 Ground-Based Navigation Facilities (VOR, TACAN, DME, ILS) 10.2 RNAV, RNP & Performance-Based Navigation (PBN) 10.3 En Route IFR Charts & High/Low Airway Navigation 10.4 Earth Reference, Time Standards, Chart Projections & Great-Circle Navigation

11 Chapter 11: Terminal Instrument Procedures — SIDs, STARs & Approaches

11.1 Standard Instrument Departures (SIDs) & Obstacle Departure Procedures (ODPs) 11.2 Standard Terminal Arrival Routes (STARs) & En Route Transitions 11.3 Instrument Approach Procedures & Minimums 11.4 Holding Procedures & Holding Pattern Calculations

12 Chapter 12: High-Altitude Transonic Aerodynamics & Jet Characteristics

12.1 Transonic Flow, Mach Number & Compressibility 12.2 Shock Waves, Mach Tuck & Shock Stall 12.3 Coffin Corner, Buffet Boundaries & Swept-Wing Aerodynamics

13 Chapter 13: Transport Category Turbine Aircraft Systems

13.1 Turbine Powerplants & Auxiliary Power Units 13.2 Electrical, Hydraulic & Pneumatic Systems 13.3 Pressurization, Environmental Control & Oxygen Systems 13.4 Flight Management Systems (FMS), Autoflight & Avionics

14 Chapter 14: Aircraft Weight, Balance & Loading

14.1 Weight Definitions & Structural Limitations 14.2 Center of Gravity (CG) Principles & Computations 14.3 Cargo Loading, Floor Load Limits & Load Manifests

15 Chapter 15: Transport Category Aircraft Performance & Limitations

15.1 Takeoff Performance & V-Speeds 15.2 Climb Gradients, Obstacle Clearance & Runway Limitations 15.3 En Route Engine Inoperative Performance & Drift-Down 15.4 Landing Performance & Runway Condition Assessment

16 Chapter 16: Practical Dispatch Flight Planning, Fuel Strategy & Emergencies

16.1 Domestic, Flag & Supplemental Fuel Requirements 16.2 Flight Planning, Route Selection & Equal Time Point (ETP) / PNR 16.3 Emergency Procedures, In-Flight Diversions & Security Threats 16.4 NTSB Part 830 Incident & Accident Notification Procedures 16.5 Flight Following, Overdue Aircraft & Post-Flight Duties

17 Chapter 17: Human Factors, ADM, CRM & Dispatch Communications

17.1 Human Factors & Human Error in Airline Dispatch 17.2 Aeronautical Decision Making, Judgment & Risk Management 17.3 Crew Resource Management, Dispatch Teamwork & Briefing Technique 17.4 Dispatch Communications, Data Link & Aeronautical Publications

17.3 Crew Resource Management, Dispatch Teamwork & Briefing Technique

Key Takeaways Explain This Topic AI

Crew resource management including crew communication and coordination is knowledge area 13 of the 13 listed in 14 CFR § 65.55(a), and 14 CFR § 121.404 requires every Part 121 aircraft dispatcher to complete approved CRM or dispatcher resource management training.

CRM exists because of accidents caused by coordination failure rather than technical failure; United 173 in 1978 is the canonical fuel-exhaustion case and directly shaped both CRM and modern dispatcher fuel monitoring.

Closed-loop communication requires three legs — the sender transmits, the receiver reads back, and the sender confirms — and an ACARS uplink with no crew acknowledgement is an open loop, not a completed message.

The two-challenge rule and the PACE escalation ladder (Probe, Alert, Challenge, Emergency) give a dispatcher a procedural path to stop a flight without needing to win an argument, backed by the § 121.533 principle that either the dispatcher or the PIC may refuse.

Part 65 Appendix A VIII.B.1 makes briefing technique a required curriculum item: an effective dispatcher-PIC briefing leads with the decision-relevant threats, names the triggers and fallbacks, and ends with a read-back rather than a question.

Last updated: September 2026

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.

Event Coordination failure What it changed

Tenerife, 1977 Ambiguous phraseology and an extreme authority gradient; the flight engineer's concern about the other aircraft's position was not pressed Standardized phraseology; explicit takeoff clearance discipline; the entire premise of CRM

United 173, Portland, 1978 A DC-8 held near the airport troubleshooting a landing gear indication until it exhausted its fuel and crashed; crew members recognized the fuel state but did not communicate it forcefully enough to the captain The first formal CRM programs; directly shaped modern fuel-state monitoring and assertiveness training , the case every dispatcher should know

Air Florida 90, 1982 The first officer voiced doubt about engine instrument readings during a contaminated takeoff four times, indirectly, and was not heeded Assertiveness technique; the two-challenge rule; ground deicing and the clean aircraft concept

Avianca 52, 1990 A crew low on fuel used non-standard phrasing ("we're running out of fuel") rather than declaring an emergency; ATC did not interpret it as a distress condition Standard fuel terminology: minimum fuel is an advisory, emergency/mayday fuel is a declaration (see Section 16.1)

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

CRM skill What it means at the desk

Communication Unambiguous, closed-loop, standard-phraseology exchanges with the PIC, ATC, maintenance, and the relief dispatcher

Situational awareness An accurate, current model of every flight's fuel, weather exposure, equipment status, and crew legality — and knowing when that model has gone stale

Workload management Prioritizing, load-shedding to a relief dispatcher, and refusing to run 50 flights solo through a severe weather event

Leadership and followership Directing an emergency response, and equally, supporting a decision you did not make once it is legally sound

  • Decision making The DECIDE loop of Section 17.2, run as a team rather than alone
  • Conflict resolution Resolving a dispatcher-PIC disagreement on facts and regulation, not on rank
  • Closed-Loop Communication

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

Send — the dispatcher transmits a specific, actionable message.

Read back — the receiver restates the substance in their own words or verbatim.

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

Step Form Dispatcher example

P — Probe Ask a question that surfaces the gap "Captain, do you have the amended KORD TAF with the TEMPO quarter-mile at ETA?"

A — Alert State the consequence plainly "With that TEMPO, our filed alternate no longer meets the C055 derived minimums."

C — Challenge Require a decision, offer the fix "I am not able to release this as filed. I can add KMKE as a second alternate with 3,400 lbs more fuel, or we delay 90 minutes."

E — Emergency Exercise authority "I am not signing this release." (§ 121.533 — two to go, one to say no )

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:

The bottom line first. "This release is built around one problem: KBOS convective line arriving with your ETA."

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.

The plan and its assumptions. Route, altitude, fuel breakdown, alternates and why those alternates.

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."

The communication plan. How and when you will update — ACARS, the frequency, the position report schedule.

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:

  • Resource What the dispatcher needs Failure mode to guard against
  • Flightcrew Fuel state, ride reports, intentions, PIREPs Assuming a silent crew is a content crew

Air traffic control Flow programs, EDCTs, reroutes, holding expectations Accepting a reroute without recomputing fuel and Part 117 crew legality

Maintenance control MEL/CDL status, deferral effects, ETOPS serviceability Taking "it is deferred" as the end of the conversation rather than asking for the operational penalty

Station and operations Deicing queues, gate and ramp constraints, ARFF index, customs and curfew limits Discovering a curfew or a customs limitation only after selecting a diversion field

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

Treating CRM as a flightcrew-only requirement. Section 121.404 names aircraft dispatchers explicitly.

Calling a sent ACARS message "communicated." Without acknowledgement the loop is open.

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.

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.

Confusing assertiveness with aggression. Assertiveness is advocacy plus a stated reason plus inquiry.

Loading diagram... Closed-Loop Communication and the PACE Escalation Ladder