17.1 Dispatch Resource Management, Human Error, and Risk Decisions

Make Decisions with the Whole Operational Team

The official knowledge requirements and PTS explicitly cover human factors, aeronautical decision-making (ADM), and dispatch resource management (DRM). These are operational skills, not a final chapter of motivational advice. A dispatcher must assess the situation, generate alternatives, prioritize risks, use support tools, detect errors, and communicate decisions with the PIC and other participants.

Assess the situation before choosing a solution

State the flight's actual position or phase, aircraft capability, fuel and time constraints, weather, available airports, and the decision deadline. Distinguish confirmed facts from assumptions and missing information. A forecast at the original ETA may not apply after a delay; a runway listed in a database may be closed by NOTAM; and a remaining fuel prediction may use an outdated altitude or wind.

Develop a concise problem statement. For example: “The original alternate is now below its required planning minima during the possible diversion window; a replacement must be reachable with the actual fuel and aircraft limitations.” That statement identifies the safety question more usefully than “the weather is bad.” It also prevents the team from solving a different, easier problem while leaving the original constraint unresolved.

Generate and compare alternatives

Options can include rerouting, changing altitude, delaying departure, choosing another destination or alternate, reducing weight, changing aircraft or crew, or cancelling. An emergency may make prompt diversion the appropriate option, while a preflight problem can allow time for repair or a later weather window. The decision depends on the actual phase and urgency.

Safety and applicable legal limits are constraints, not quantities to offset with ticket revenue. Within the safe, authorized options, economics and schedule can help choose among alternatives. Do not claim that the cheapest option is automatically the safest or that every delay is inherently preferable to a valid reroute.

Individual and organizational error

Attention overload, fatigue, expectation, incomplete knowledge, and memory failures can create individual errors. Confirmation bias favors information supporting the desired departure; plan-continuation bias favors the original destination despite worsening conditions. Detect these by seeking disconfirming evidence, checking thresholds explicitly, and inviting a colleague or the PIC to challenge the assumptions.

Organizational factors include workload, unclear responsibility, poor handover, inadequate training, conflicting procedures, and pressure to maintain schedule. A personal reminder cannot fully fix a staffing or process problem. Use the carrier's reporting, supervision, and safety-management arrangements to resolve recurring hazards rather than hiding them behind repeated discretionary workarounds.

Technology-induced error

Automation can calculate accurately from wrong inputs. A stale aircraft configuration, wrong runway condition, unit mismatch, copied alternate, or outdated route can produce a polished but invalid release. Automation bias makes people accept an output because it appears authoritative. An alert can also be missed among numerous low-priority messages.

Crosscheck key inputs and operational plausibility. Confirm the aircraft/engine variant, weight, weather time, runway and declared distances, MEL effects, route, and actual reserve basis. Independently estimate an order of magnitude: a two-hour flight at a supplied 5,000 lb/hour rate should not show a 1,000-pound trip burn. The independent check need not reproduce the entire software algorithm to catch a consequential input or scale error.

Prevention, detection, and recovery

Prevent errors using clear procedures, verified data, role assignment, and manageable workload. Detect them with crosschecks, peer review, discrepancies between planned and observed conditions, and feedback from the crew or other departments. Recover by identifying the affected flights and documents, communicating the correction, recalculating dependent results, and recording the final decision.

A corrected fuel number does not automatically correct takeoff weight, landing weight, performance, alternate reachability, and flight-plan filing. Follow the error through every dependent output. Preserve a clear audit trail and distinguish the obsolete release from the amended one. If the error is discovered airborne, assess urgency and the remaining safe choices before sending a long administrative explanation.

Teamwork and distributed problem solving

ATC manages traffic and clearances, maintenance controls aircraft discrepancies, the flightcrew assesses and operates the airplane, crew scheduling manages assigned personnel eligibility and limits, and operations-control staff coordinate the broader operation. The dispatcher integrates relevant information and maintains the applicable operational-control responsibilities. Delegating a task does not mean assuming someone else owns the decision.

Assign named responsibilities and deadlines. Ask maintenance for the verified restriction, not a vague assurance that the aircraft is “fine.” Ask ATC about the relevant route/delay options without treating a clearance as fuel approval. Brief the PIC on the proposed plan and obtain required concurrence. Use closed-loop communication for critical updates and handovers.

Workload and contingency planning

Prioritize immediate threats and upcoming decision points. A flight with a smoke emergency takes precedence over routine forecast delivery; a flight nearing a re-release point has a time-sensitive requirement. Request support and distribute tasks so each person knows the operational priority and reporting path.

Create contingencies before options disappear: identify an alternate, a fuel/decision threshold, and the trigger for reassessment. In a fictional destination-fog scenario, document when updated weather or fuel trends will prompt diversion, who tracks those triggers, and what airport remains reachable. A contingency is a verified option, not a promise that weather will improve. The PTS expects the applicant to explain these choices and demonstrate effective DRM throughout the practical exercise.

Official References

Source check: 2026-10-12. FAA dispatcher PTS; Part 65 Appendix A syllabus; Part 121 operational rules and records. For operational use, apply current issued authorizations and the assigned aircraft’s approved data.