Before a U.S. airline flight pushes back, a dispatcher builds a dispatch release — a signed legal document that fixes the route, the fuel load, and the alternate airport.
The captain must countersign it, and under 14 CFR 121.533 both share responsibility for what it says. Fuel breaks into four mandatory parts: trip, contingency, alternate, and final reserve. The dispatcher works that load two to four hours out, often while tracking 10 to 25 aircraft.
Ask a passenger who plans a flight and you’ll usually get one answer: the captain. In the U.S. regulatory system, that answer is incomplete. Before a Part 121 flight is authorized to leave, two people sign the same document — and the passenger has almost certainly never met one of them.
That document is the dispatch release, and it locks in the route, the fuel load, and the alternate airport. The dispatcher starts building it two to four hours before departure, pulling weather, performance data, airspace restrictions, and airport status into a single plan. Often that same dispatcher is working it for 10 to 25 flights at once.
The release is best understood not by the clock but by its decision points: what gets certified when two signatures land on the page, why the fuel load has four mandatory parts, how an alternate earns its place, and what happens when the weather tools start to argue.
What two signatures actually certify
Under 14 CFR 121.533, operational control over a U.S. Part 121 flight rests jointly with the pilot in command and the aircraft dispatcher. Before departure, both must sign the dispatch release — the formal legal instrument that authorizes the flight to operate.
The captain’s signature records agreement to fly under the plan the dispatcher built. It does not transfer the dispatcher’s responsibility to the flight deck.
The joint model is not a global standard. Under the retrieved ICAO working paper, Annex 6, Part I, paragraph 4.6 assigns flight dispatchers a support role; by the same paper’s account, EASA gives the pilot in command primary operational-control responsibility. The U.S. arrangement is exactly that — a U.S. arrangement.
The four parts of a fuel load
Fuel planning starts with the four mandatory components of the release. Trip fuel covers the planned route. Contingency fuel covers the unexpected changes — a reroute, a stronger headwind, a longer hold.
Alternate fuel is what the aircraft carries to reach the backup airport. Final reserve is the fuel that must still be in the tanks after landing, no matter what happened on the way.
What this article cannot tell you is the number. None of the retrieved primary-source material established a reserve percentage or a time-equivalent figure, and inventing one would be worse than leaving the box empty. The actual figures shift with the operation, the aircraft, the route, and the governing regulation.
The route itself is a fuel input before it becomes a flight path. On international legs, overflight permissions, restrictions, and charges shape which routing the dispatcher can even plan. That much is clear in principle; this research turned up no verifiable current fee figure or official restriction document for any named route, so those numbers stay open.
Flight deals
most people never see
Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.
Each deal saves 40–80% vs. regular fares:
Choosing the alternate
The alternate airport is not an afterthought. A safe destination must exist if the primary airport becomes unusable, and choosing one is a mandatory part of the dispatch release. That choice matters before a single passenger boards — the alternate is selected and fueled for while the aircraft is still at the gate.
What looks like an unplanned diversion to the passengers in row 22 was almost always planned hours earlier, with fuel already accounted for. The weather at that backup field, the runway available, and the approach available all shape whether it can serve. If none of them work, the dispatcher’s job is to find that out before release, not after a missed approach.
When the weather tools disagree
A terminal aerodrome forecast and a convective forecast product can disagree about the same arrival window, and no fixed rule settles which one wins. The dispatcher settles it by comparing the latest observations with short-range convective guidance for the estimated arrival time, then choosing between three options: fly the route as planned, add safeguards such as extra fuel, or avoid the weather altogether.
That three-response framework comes from a documented dispatcher presentation in a Transportation Research Board circular. Its worked example shows the third option in action. The storm’s intensity and track pushed the dispatcher to scrap the routing the software preferred and build an avoidance route by hand — even after a second forecast product put the worst of the weather somewhere else.
The dispatcher also works from a floor of required information: reports and forecasts for every airport and route the flight will use, covering hazards such as low-level wind shear, thunderstorms, and clear-air turbulence. The call is not made from a tool list; it is made when two or more of those inputs refuse to agree.
Low-cost versus legacy: same rules, different priorities
The same Part 121 rules apply whether the aircraft is a regional jet or a widebody, but whether low-cost and legacy carriers actually prioritize those rules differently is an open question. One NTSB-hosted excerpt from American Airlines’ dispatch manual lists fuel, routing, alternates, weather avoidance, aircraft performance, regulations, company policy, and business objectives among the planning considerations. That is one airline’s list, not a cross-carrier comparison.
What is missing is the other side of the ledger. None of the retrieved material put a named low-cost carrier’s pre-flight priorities on the same footing. The comparison remains unverified, which means the honest section is this: the regulatory framework is identical, and any claim about cost structure changing dispatch judgment needs primary-source proof that does not yet exist here.
Who can ground a flight
Weather, fuel margins, or mechanical limitations can make a flight unsafe, and when they do, the dispatcher does not need the captain’s permission to act. The dispatcher is legally empowered to delay, divert, or cancel it. That authority is built into the same operational-control framework that requires the co-signature in the first place.
An NTSB-hosted excerpt from American Airlines’ dispatch manual shows the authority in writing: a dispatcher can cancel, delay, amend, or redispatch a flight on safety grounds. It’s a procedures document, not a dated record of a single dramatic case — no named flight, date, and outcome turned up in the retrieved NTSB, court, or regulatory material. The power is documented; the stories are not.
None of this is visible from the gate. The next time a flight is held for ‘operational reasons,’ the person who made that call may not be in the airplane — and may be doing the same math for two dozen other flights.
How the release gets built and shipped
The dispatcher builds the operational picture from weather, aircraft performance, the routes and alternates on offer, airport and facility status, and the fuel the flight needs. A computerized planner will suggest routings — it weighs real-time meteorological data, wind-optimal algorithms, and current airspace restrictions or notices to air missions to generate candidates.
The planner proposes; the dispatcher weighs. If the hazards on the candidate route are unacceptable, the release can override the software. Once the dispatcher signs off on the plan, it goes out through the operator’s own dispatch system or a datalink such as ACARS, and the captain countersigns it on the flight deck.
That signature does not close the file. Release amendments and rolling updates keep both parties involved after the aircraft is airborne, which is why a plan can change in mid-air without a single gate-announcement clue.
What a dispatcher’s decision looks like from the gate
The dispatcher never hands you a boarding pass, but the release’s fingerprints are on several things you do see. A delay attributed to ‘operational reasons’ may be a fuel-margin or weather judgment made hours earlier, at a desk the passenger never sees.
FAA guidance on hazardous weather spells out the options: change the route or altitude, delay the takeoff or landing, hold, or divert to an alternate. Any of those can turn into a mystery delay at the gate, even when the forecast at your departure point looks fine.
The block-time clue is subtler. The same city pair can show different scheduled block times on different days, because the routing the dispatcher picks shifts with real-time weather and airspace restrictions. And a delay is not necessarily the airline falling apart — it can be one dispatcher working through a queue of safety margins.
Key terms
- Operational control
- Operational control is the shared responsibility for how a flight is planned and conducted. In U.S. Part 121 operations, 14 CFR 121.533 — the section titled ‘Responsibility for operational control’ — assigns it jointly to the pilot in command and the aircraft dispatcher, with sections 121.535 and 121.537 sitting in the same framework. The practical effect is that two people, in two different places, answer for a single flight, and either can hold it on the ground when the margins do not add up.
- Part 121
- Part 121 is the set of U.S. federal aviation regulations that covers the airline operations described in this article. Its operational-control rules — 121.533 first among them — are the source of the joint pilot-and-dispatcher responsibility at the center of the release. The label matters to a traveler because it draws a line: under these rules, the plan for the flight carries a signature from someone who is not on board.
- Terminal aerodrome forecast
- A terminal aerodrome forecast is a forecast for conditions at one specific airport over a set window. Dispatchers are required to have current reports and forecasts covering every airport and route a Part 121 flight will use, so the forecast for the destination — and for each alternate — is part of the paperwork behind a release. Because it speaks for a single field rather than for the weather system moving toward it, it is only one of the inputs a dispatcher has to reconcile before signing.
- ACARS
- ACARS is a datalink system for exchanging messages between an aircraft and the ground. A dispatcher can use it, or the operator’s own dispatch system, to deliver a release to the flight deck. Its role is easy to overlook until a plan changes: the same channel that carried the release can carry the revision.
Questions? Answers.
Does the joint pilot-and-dispatcher responsibility model apply outside the United States?
No. The joint model comes from U.S. 14 CFR 121.533. Outside the U.S., ICAO Annex 6, Part I, paragraph 4.6 assigns flight dispatchers a supporting role for preparation and in-flight phases, and under EASA rules the pilot in command holds primary operational-control responsibility.
What weather information must a dispatcher provide before a Part 121 flight departs?
The dispatcher must provide reports and forecasts for every route and airport the flight will use, covering hazards such as low-level wind shear, thunderstorms, and clear-air turbulence.
How can a dispatcher’s decision show up in a passenger’s experience?
Before departure, the dispatcher supplies the weather and hazard information that frames the flight, and the choices made from it can reach a passenger as an unexplained delay or a diversion. A hold, a different altitude, or a different airport is a call made against a safety margin, not a sign that the airline has lost track of the schedule.
