A re-dispatch does not find fuel in the tanks. It rewrites the question the fuel plan is answering, and the answer comes out smaller. The whole gain sits on one line of the plan — contingency — and it is bought by moving a decision out of the operations centre, where it would have been made before departure, onto the flight deck several hours into the flight. The saving is real; what it costs is that a question an ordinary flight plan settles on the ground stays open until a commander closes it.
Two flight plans, one aeroplane
An ordinary flight plan is a single computation. Departure aerodrome, destination, one alternate or two, one trip fuel figure, one contingency figure derived from it. The aeroplane is fuelled for that computation and the crew flies it.
A decision point procedure replaces the single computation with two, and loads the aeroplane with the greater of the two requirements. The first plan runs from the departure aerodrome to a nearer aerodrome — call it the intermediate destination — with its own alternate and its own reserves. The second runs from the departure aerodrome, through a nominated point on the route, onward to the destination the operator actually wants, with its own alternate and its own reserves, but with contingency computed only on the segment beyond that point.
Two constructions circulate under closely related names, and they are not interchangeable. In one, the two plans end at different aerodromes: the fallback is a genuine commercial destination, and if the arithmetic fails the flight lands there — a re-dispatch, a re-release, or a reduced contingency fuel procedure, depending on the system. In the other, a single destination throughout, with a suitably located en-route alternate as the fallback. Which of the two an operator holds is settled by its manual and its approval, not by the vocabulary.
The essential move is the same in both. Contingency absorbs the difference between planned and actual consumption. On a long sector the planner has to carry that absorption from the moment the doors close, although most of the uncertainty will have resolved itself long before the top of descent. The procedure says: carry it whole until we can measure what actually happened, then carry it only for what is left.
This procedure delays deciding how much fuel to carry until partway through the flight. Instead of guessing the whole trip’s fuel needs upfront, it splits the flight into two parts and only commits to the second part’s fuel after checking the first part’s actual consumption. This saves fuel by avoiding overestimating early in the flight.
Where the saving is actually taken
The commonest misreading is that a re-dispatch removes fuel. It removes nothing. It changes the base on which one line is calculated, and the loaded figure is then the higher of the two plans, not the lower.
Take a twelve-hour sector with the decision point placed eight hours out. Under the default construction, contingency is a percentage of the trip fuel for twelve hours of flying. Under the second plan it is that same percentage applied to the trip fuel of the four hours remaining beyond the point. The percentage has not changed. The exposure it covers has shrunk, because eight hours of deviation are no longer hypothetical when the check is made — they are on the fuel gauges.
That is also where the procedure stops being free. The first plan carries a full set of reserves to the intermediate destination and its alternate. If that aerodrome sits early on the route, or its alternate is distant, or its weather forces a second alternate, the first plan becomes the binding one and the saving evaporates. Choosing the intermediate destination is a fuel decision, not a commercial one.
On a Boeing 777 flying from London to Singapore (12 hours, around 84 t of trip fuel), with a decision point at 8 hours, the standard contingency might be 5% of the whole trip fuel (about 4,200 kg). Using the procedure, it is based on the last 4 hours only (about 1,400 kg). This saves roughly 2,800 kg of fuel, but only if the intermediate aerodrome (e.g., Dubai) is a suitable place to land and its weather remains usable.
| Construction | What is computed | Contingency applies to | What must exist besides the destination | What is decided in flight |
|---|---|---|---|---|
| Ordinary plan | One computation, departure to destination | The trip fuel of the whole sector | Destination alternate or alternates | Nothing not already decided at dispatch |
| Decision point procedure | One destination, contingency split at a nominated point | The trip fuel from the decision point onward | An en-route alternate placed to suit the point | Continue, or divert to the en-route alternate |
| Reduced contingency fuel, or re-dispatch | Two plans, to an intermediate and to a final destination | The trip fuel from the point to the final destination | An intermediate destination with its own alternate and reserves | Continue, or land at the intermediate destination |
The decision point is a calculation before it is a waypoint
Crews meet the decision point as a name on a plan, often an oceanic entry fix with a time beside it. That presentation hides what it is: the place where two opposing pressures balance.
Pushing the point later increases the saving, because the residual trip fuel keeps shrinking. Pushing it later also erodes the fallback, because the aeroplane must still be able to reach the intermediate destination, or the en-route alternate, with everything a landing there requires. Past a certain distance downtrack the fallback stops being reachable and the flight is committed whether anyone writes it down or not.
Three further constraints bear on the placement:
- Information. The check needs current actual and forecast weather for the final destination and its alternate, and the status of both aerodromes. A point where that data cannot be obtained reliably is a decision point in name only.
- Time to act. The computation must be made early enough for a turn towards the fallback to remain a normal manoeuvre flown on the fuel the plan assumed.
- Sequence with other gates. On a sector with an extended-range segment, the decision point and the entry into that segment are two gates with two arithmetics, and the crossing order matters.
What has to be true at the point to continue
At the decision point the crew compares fuel that exists with fuel that is required. On one side, the usable fuel actually on board, read from the aircraft rather than from the plan. On the other, everything the remainder of the flight will demand: trip fuel from here to the final destination, contingency for that segment, alternate fuel, final reserve, and any additional or extra fuel carried for a specific identified reason.

If the fuel on board covers that sum, the flight continues and the second plan becomes the operative one. If it does not, the flight lands at the intermediate destination or diverts to the en-route alternate — and that is not a failure of the procedure, it is the procedure working. The option to continue was always conditional; the decision point fixes the moment the condition is tested.
Fuel is not the only gate. The weather and aerodrome status that justified the second plan at dispatch must still justify it now, against the applicable planning minima for the expected arrival time. And the flight duty period has to accommodate the longer leg: a continuation that only fits inside a commander’s discretion provision has to be recognised as such and handled under the operator’s scheme, not absorbed silently.
| Element | Continuing requires | Taking the fallback requires |
|---|---|---|
| Trip fuel | Point to final destination, recomputed on the level and wind being flown | Point to the fallback aerodrome |
| Contingency | Applied to the remaining segment only | As the first plan computed it |
| Alternate fuel | For the final destination’s alternate | For the fallback’s alternate |
| Final reserve | Unchanged, and untouchable | Unchanged, and untouchable |
| Weather | Final destination and alternate at or above planning minima for the arrival time | Fallback usable, hence monitored the whole way |
| Crew duty | The longer leg has to fit the duty period actually available | Usually the less constraining of the two |
The right habit. Run the decision point computation on the fuel indicated by the aircraft and on the conditions being flown — actual level, actual temperature, actual wind — never on the planned figures reprinted in the flight plan. The value of the procedure comes from measuring what happened instead of predicting it; recomputing with planned numbers throws that value away and keeps the risk.
What the procedure moves onto the flight deck
Every fuel construction distributes responsibility between those who plan and those who fly. The default puts almost all of it before departure, and the crew’s in-flight fuel checks are a monitoring activity whose normal outcome is that nothing changes. A decision point procedure keeps those checks and adds one that is load-bearing.
Monitoring becomes predictive rather than descriptive
Comparing fuel remaining against plan tells you where you stand. Here you also need to know where you will stand at the decision point, early enough to see a shortfall coming while options are still cheap. A crew that discovers at the point itself that the figure will not work has been overtaken by the aeroplane.
Two aerodromes stay in the picture
The intermediate destination is not a curiosity on the plan. Its weather, runway state and services have to be tracked from departure, because it is where the flight goes if the arithmetic fails. One that has quietly gone below minima while everyone watched the final destination removes the fallback altogether.
The decision has a deadline, and the commander’s authority does not change
Unlike most in-flight decisions this one expires: deferring it does not preserve options, it consumes them, because the fuel needed to reach the fallback is burning while the deferral lasts. What does not change is what attaches to a commander who finds the calculated usable fuel on landing falling below the final reserve, and the declarations that go with it. The procedure narrows what is planned, not what has to be announced.
The trap. Treating the final destination as the flight’s real destination and the intermediate one as a formality. Connecting passengers, positioning crew and the next rotation all push in one direction at exactly the moment the arithmetic may be pushing the other way. A continuation decided without the required figure does not save the rotation; it converts an approved procedure into an unplanned reduction of reserves, and it is visible in the fuel record afterwards.
Where it meets extended-range operations
On sectors flown with extended diversion times, the decision point procedure and the extended-range fuel requirement sit side by side without merging, and they are routinely confused.
The critical fuel scenario computed for an extended-range segment answers a different question. It asks what the aeroplane needs to divert to an adequate en-route alternate from the most demanding point of the segment, in a defined failure case, with the drift-down, icing and performance penalties that case implies. It is not a percentage of anything, and a re-dispatch does not reduce it. At the entry into the segment the aeroplane must hold at least what that scenario demands, whatever the decision point arithmetic said minutes earlier.
Two consequences follow. The decision point is usually placed so the crew resolves it before the entry gate, keeping the two checks in a readable order. And on many long oceanic sectors the extended-range requirement, not the re-dispatch, is the binding constraint on the fuel load, so the saving the commercial department expected never appears. That is a route-study finding, not a crew finding. The en-route alternates supporting the segment keep their own weather requirements and validity windows; the procedure does not shorten that list.
What the operator has to have in place first
None of this is a technique a thoughtful captain can adopt. It has to exist in the operations manual before it exists in the aeroplane, and the European framework now organises fuel and energy planning into schemes — a basic one, a basic one with variations, and an individual one — with anything beyond the basic scheme being a matter for the competent authority.
What a line pilot can reasonably expect to find in the manual before flying the procedure is a coherent set:
- The criteria for selecting the fallback aerodrome and for placing the decision point.
- The computation to be performed at the point, written as an arithmetic executable without interpretation.
- The weather and aerodrome-status requirements at each stage, and how the crew obtains that information en route.
- The flight-following support: who monitors the fallback, who transmits an update, what happens if the link is lost.
- Training for crews and flight operations officers, and the recording that lets the operator see how often the fallback is actually used.
That last item is the one operators skip and authorities ask about. A procedure whose fallback is never used across thousands of sectors is either well planned or never honestly evaluated, and only the records tell them apart. Recurrent training on the fuel scheme, in house or through a provider such as FL330 training, is what keeps the arithmetic executable under time pressure rather than merely documented.
The same idea under three names
Terminology travels badly between systems. The mechanism survives translation; the numbers and surrounding conditions do not.
| System | Usual label | What the reduction rests on | What to check before assuming equivalence |
|---|---|---|---|
| ICAO framework | Fuel planning with a decision point, in Annex 6 Part I and its guidance material | Contingency computed from the decision point onward | Annex 6 sets the framework; the binding detail is the State’s implementation |
| European rules | Reduced contingency fuel procedure, decision point procedure | Contingency applied to the remaining segment, inside an approved fuel scheme | Whether the operator holds a scheme beyond the basic one, and what its variations authorise |
| United States | Re-dispatch, re-release, for flag operations | The reserve expressed as a proportion of total time en route, recomputed from the release point | The reserve is built differently, so the check is not the same arithmetic |
The differences between operators’ manuals are usually less about the mechanism than about what the manual authorises when the figure is marginal — worth discussing with people who fly both systems, which is what the FL330 forums exist for.
What the procedure is worth, honestly stated
A decision point procedure is a good trade when three conditions hold together: the sector is long enough that contingency on the full trip fuel is a meaningful weight, a fallback exists that is genuinely usable and genuinely monitored, and the crew has the information and the time to make the check properly. Remove any one and the procedure keeps its paperwork and loses its value.
It is a poor trade when the fallback is chosen to make the numbers work rather than because the flight could land there, or when the culture makes the fallback outcome feel like a defeat. In that case the procedure has not reduced fuel; it has relocated a decision to the worst possible place — a tired flight deck, hours into a duty, with an aeroplane pointed the wrong way for the answer the arithmetic is about to give.

Leave a Reply
You must be logged in to post a comment.