A computerized flight plan is far more than a printout from an automated system. It is the product of deliberate, informed decisions made by a certificated aircraft dispatcher who understands how each input variable shapes the output. The Flight Management System (FMS) data loader, airline operational control software, and performance computing tools accept the dispatcher's choices and translate them into fuel burn projections, weight limits, takeoff performance data, and routing. Every number entered has a real-world consequence for fuel reserves, alternate selection, and en route safety.
This article examines the specific inputs that a dispatcher controls when constructing a computerized flight plan, explains the underlying principles that govern each input, and connects those principles to the legal framework under 14 CFR Part 121 and the procedural guidance found in the FAA Instrument Procedures Handbook (FAA-H-8083-16) and the Aeronautical Information Manual (AIM) Chapter 5.
The Core Dispatcher-Controlled Inputs
Modern airline dispatching software accepts a structured set of inputs that drive every downstream calculation. Understanding each category is essential for the aircraft dispatcher written examination and, more importantly, for safe operational control.
Route of Flight
The dispatcher selects the specific airways, waypoints, direct segments, and special-use airspace avoidances that define the route. The AIM Chapter 5 explains how flight plans are filed, and a dispatched Part 121 operation must file an IFR flight plan that reflects the actual intended route. The dispatcher chooses between:
- Published airways (Victor routes for low altitude, Jet Routes for high altitude): These follow VOR radials or RNAV corridors defined in the Chart Supplement and encoded in the navigation database.
- RNAV/GPS direct routing: Where ATC allows, the dispatcher may specify direct waypoint-to-waypoint routing to reduce flight time and fuel burn.
- Oceanic and MNPS/RVSM tracks: For transatlantic or transpacific operations, the dispatcher selects from published Organized Track Systems (OTS) or files random routes within approved airspace, accounting for NAT HLA restrictions.
- Special-use airspace avoidance: MOAs, Restricted Areas, and TFRs must be checked and routed around unless prior coordination ensures access.
The route choice directly drives the Great Circle Distance (GCD) or actual route distance the planning system uses to compute fuel burn. A longer but more favorable wind route often consumes less fuel than a shorter route with strong headwinds, so the dispatcher must evaluate both geometry and meteorology simultaneously.
Cruise Altitude and Step Climbs
Altitude selection is one of the highest-leverage dispatcher decisions. Aircraft fuel efficiency (expressed as specific range—nautical miles per pound of fuel) varies with altitude and aircraft weight. The dispatcher inputs an Initial Cruise Altitude and, for long flights, one or more step-climb altitudes at which the aircraft should request a higher flight level as fuel burn reduces weight.
RVSM airspace (FL290–FL410 in domestic U.S. and most international airspace) allows 1,000-foot separation between flights, enabling the dispatcher to select optimal altitudes in 1,000-foot increments. Without RVSM approval, separation minima revert to 2,000 feet above FL290. The planning system applies the appropriate restriction automatically once the dispatcher confirms the aircraft's RVSM status.
Semi-circular (hemispheric) altitude rules also apply: IFR flights on magnetic courses 000°–179° use odd thousands of feet, and courses 180°–359° use even thousands—though within RVSM these are still in the odd/even pattern at each 1,000-foot interval. The dispatcher's software enforces these constraints, but the dispatcher must still confirm that the selected altitude is appropriate for the direction of flight.
Aircraft Performance Data and Weight Inputs
Computerized planning systems require accurate weight inputs to generate valid fuel burn projections. The dispatcher must enter or verify:
- Operating Empty Weight (OEW): The baseline weight of the configured aircraft, drawn from the current Weight and Balance manifest or electronic aircraft record.
- Zero Fuel Weight (ZFW): OEW plus payload (passengers, bags, and cargo). ZFW must not exceed the Maximum Zero Fuel Weight (MZFW) structural limit.
- Planned Takeoff Weight (TOW): ZFW plus all fuel loaded. TOW drives takeoff performance calculations and must stay within Maximum Takeoff Weight (MTOW).
- Landing Weight: The system calculates projected landing weight by subtracting expected fuel burn from TOW. This must not exceed Maximum Landing Weight (MLW).
The dispatcher commonly uses a payload-range philosophy: maximize revenue payload within structural and performance limits while carrying the minimum legal fuel. Every extra pound of fuel beyond regulatory minimums reduces payload capacity or increases fuel burn, so precision matters.
Fuel Load Inputs
14 CFR §121.639 through §121.647 specify the fuel requirements for Part 121 domestic, flag, and supplemental operations. The dispatcher must compute and enter separate fuel components, which the planning system sums into a total fuel requirement:
- Trip fuel: Computed fuel from departure to destination under planned route, altitude, and forecast winds.
- Alternate fuel: Fuel from destination missed approach to the alternate airport, computed using forecast conditions.
- Reserve fuel: For domestic operations under 14 CFR §121.639, this is fuel to fly, after completing the flight to the destination and then to the most distant alternate, for 45 minutes at normal cruise fuel consumption—it is not a separate cruise leg flown after arriving at the alternate, but the fuel that must remain onboard once the aircraft reaches the alternate. Flag operations use different standards.
- Additional / contingency fuel: The dispatcher may add discretionary fuel for known factors such as ATC delay, convective weather deviation, airport congestion, or unusually strong headwinds beyond the nominal forecast.
- Taxi fuel: Ground burn from engine start to takeoff roll, based on planned routing and airport congestion history.
The computerized system sums these components and alerts the dispatcher if the total fuel load would exceed MTOW or the fuel tank capacity. The dispatcher then resolves the conflict by adjusting payload, selecting a closer alternate, or modifying the route.
Alternate Airport Selection
The dispatcher selects the alternate airport(s) and inputs them into the system, which then calculates alternate fuel. The AIM Chapter 5 and 14 CFR §121.619 govern when an alternate is required. The FAA's 1-2-3 rule (a simplified guidance concept) describes conditions under which an IFR alternate might not be required for general aviation, but Part 121 dispatchers must apply the more stringent airline standard: an alternate is almost always planned, and weather at the alternate must meet prescribed minima at the estimated time of arrival (ETA ± 1 hour for planning purposes under Part 121 alternate weather standards).
The dispatcher evaluates alternate airports for instrument approach availability, navaid reliability, airport facilities (fuel, maintenance, gates), and forecast weather using Terminal Aerodrome Forecasts (TAFs) and Area Forecasts. The computerized system calculates additional fuel based on the routing from destination to alternate but relies entirely on the dispatcher's judgment to select an appropriate airport.
Weather Data Integration
Computerized planning systems pull forecast upper-wind data (typically from NOAA/NWS Global Forecast System or equivalent) to compute winds-aloft corrections at each waypoint and altitude. The dispatcher controls which forecast cycle to use and must verify that the data is current and applicable to the planned departure time. For long-haul flights, the dispatcher may apply a wind bias factor to account for forecast uncertainty, effectively treating winds as slightly less favorable than the forecast to protect against a fuel shortfall.
Significant weather (SIGMETs, AIRMETs, PIREPs, and convective outlooks) is not automatically routed around by the planning system in most configurations—the dispatcher must assess that information and manually modify the route or add contingency fuel accordingly.
Why Dispatcher Control of These Inputs Matters
Under 14 CFR §121.533, the aircraft dispatcher shares operational control with the pilot-in-command. This joint responsibility makes dispatcher accuracy in flight plan inputs a direct safety factor. An under-fueled flight plan or an improperly selected alternate can create a life-safety emergency. Conversely, excessive conservatism on every flight compounds into millions of dollars in unnecessary fuel costs and emissions. The dispatcher's professional judgment in calibrating each input is therefore both a legal obligation and an economic responsibility.
FAA-H-8083-16 (Instrument Procedures Handbook) reinforces that understanding of procedures, airspace, and routing constraints is inseparable from safe IFR operations. The dispatcher's role is to translate that procedural knowledge into flight plan inputs that the crew can execute safely and efficiently.
Key Numbers and Rules
- RVSM airspace: FL290–FL410; 1,000-foot vertical separation (requires RVSM equipment and approval).
- Hemispheric rule: Odd thousands (FL270, FL290, etc.) for courses 000°–179°; even thousands for 180°–359°.
- Domestic fuel reserve (14 CFR §121.639): Fuel to fly to the destination, then to the most distant alternate, plus 45 minutes at normal cruise consumption remaining after reaching the alternate.
- Flag fuel reserve (14 CFR §121.645): Fuel to fly to and land at the most distant alternate, plus fly thereafter for 30 minutes at holding speed; a separate additional-fuel provision under §121.645(b) applies to certain flag operations without an available alternate.
- MZFW limit: ZFW must not exceed the manufacturer-specified Maximum Zero Fuel Weight.
- Alternate weather timing: TAF must cover the period from 1 hour before to 1 hour after planned ETA at the alternate.
Common Test Traps
- Confusing trip fuel with total fuel: Trip fuel is only the destination leg. Total fuel adds alternate, reserve, contingency, and taxi components. The exam distinguishes these sharply.
- Applying GA alternate rules to Part 121: The 1-2-3 concept applies to general aviation; Part 121 dispatchers operate under the stricter requirements of 14 CFR §121.619.
- Ignoring MZFW as a limit: Candidates sometimes focus only on MTOW and MLW. An overloaded zero-fuel condition can violate structural limits even when total weight is technically under MTOW.
- Treating the computerized plan as authoritative without verification: The system is only as good as its inputs. The dispatcher is responsible for the accuracy of entered data—garbage in, garbage out is a safety issue in aviation.
- Forgetting step-climb fuel accounting: Each step climb re-initializes the fuel burn model at a new altitude and weight. Failing to plan step climbs on long flights means the plan may overstate fuel burn (conservative) or, if altitudes are mismatched, understate it (dangerous).