Two standard phrases sit at the far end of a deteriorating fuel situation, and they are not two intensities of the same message. One announces that the aircraft has run out of room to absorb delay; the other announces that the arithmetic has already failed. Only the second is an emergency, and it is the only one of the two built on a prediction rather than on a gauge. What each phrase commits the controller to, what it commits the crew to, and the reasoning that has to be finished before the second one is transmitted.
Two phrases, two different objects
The confusion between the two announcements is not a vocabulary problem. It comes from reading both as descriptions of the same thing — a quantity of fuel in the tanks, differing only in how alarming it is. Neither of them describes the fuel in the tanks.
The minimum fuel announcement describes a state of commitment. It says: this aircraft is now going to a named aerodrome, the option of going somewhere else has been spent, and the flight can no longer absorb an unplanned change to its clearance without eating into the last protected quantity of fuel. It is a statement about degrees of freedom, not about litres.
The fuel distress announcement describes a predicted quantity at a future moment: if this aircraft flies to the nearest aerodrome at which a safe landing can be made, the usable fuel remaining on touchdown will be below final reserve. It is a forecast, and like every forecast it must be produced before the event it forecasts.
That is why the two calls behave so differently in the system. A statement about lost options is information. A statement that the protected reserve is going to be broken is a distress condition, because it says the flight has already left the envelope the entire fuel policy exists to defend.
| Minimum fuel | Fuel distress (Mayday fuel) | |
|---|---|---|
| What it asserts | Committed to a specific aerodrome; any change to the existing clearance may result in landing below final reserve | Calculated usable fuel on landing at the nearest aerodrome where a safe landing is possible would be less than final reserve |
| Nature of the claim | A statement about remaining options | A statement about a predicted landing quantity |
| Requires a calculation first | A coarse one: does any change to my clearance break the reserve? | An explicit one: fuel on landing at the nearest suitable field, against final reserve |
| Status | Advisory; not an emergency, not a priority request | Distress. Full emergency handling |
| What the controller owes you | Information on expected delay, or that none is expected | Priority, and whatever assistance the situation needs |
| Reversible | In practice, the situation can improve | Rarely; downgrading it is a decision in its own right |
| Common misuse | Used as a request for priority | Delayed until the tanks, not the prediction, look empty |
Final reserve fuel, the number both phrases point at
Neither announcement makes sense without the quantity they both reference. Final reserve is the quantity that must still be in the tanks when the wheels touch; every other fuel figure exists to protect it. For turbine-engined aeroplanes it is conventionally expressed as thirty minutes of holding at fifteen hundred feet above aerodrome elevation in standard conditions, computed at the estimated mass on arrival; for piston-engined aeroplanes the classic figure is forty-five minutes. The exact expression, and the mass and conditions used to derive it, come from the operator’s approved fuel policy and from the State of the Operator, not from a universal constant.
Two properties of that number are routinely forgotten in the cruise. It is a mass, computed once at planning at an assumed arrival weight, not a duration you still have: heavier than planned, the same mass buys fewer minutes. And it is not consumable — planning to land with exactly final reserve is planning to land with no margin for whatever goes wrong on short final.
Both announcements are comparisons against a reference the crew must be able to state in minutes, at the present weight, without opening a manual. A crew that cannot answer « how many minutes is our final reserve right now » cannot make either call at the right moment.
The trap. Final reserve is not the fuel remaining when the low level alert illuminates, and it is not what the fuel prediction shows. Onboard predictions are computed against the flight plan currently entered, not against a diversion nobody has entered. A comparison with final reserve that was not made deliberately, for the aerodrome you are actually going to, has not been made.
Final reserve is the fuel you must have left when landing. It’s not a fixed time, but a mass that changes with your weight. You must always know how many minutes of flight it represents at your current weight to make the right calls.
Minimum fuel is a statement about commitment
The condition for the first announcement is not a fuel quantity, it is the loss of alternatives. It arrives at the moment the flight is committed to a specific aerodrome and can no longer accept an unplanned change of clearance, a re-sequence, a longer routing or a hold, without that change taking it below final reserve on landing.
Operationally, that trigger is usually crossed a long way out and passes unnoticed, because nothing on the flight deck changes when it happens. There is no alert, no amber caption, no callout. It occurs when fuel state, distance to the alternate and distance to destination line up in a particular way, and the only thing that detects it is a crew who computed the point in advance.
The announcement itself does not buy anything. It is not a request, it does not confer priority and it does not, on its own, place the flight ahead of anybody. What it buys is information: on receiving it the controller is expected to say whether a delay is anticipated, and how long. That answer is what turns a commitment into a decision. If the answer is « no delay expected », the situation is stable. If the answer is a number, the crew now has the input to their next comparison, which may well be the second announcement.
Crews who expect the advisory to produce a queue jump come away believing the phrase does not work. It works exactly as designed; it was never designed to produce priority. The danger is what follows: having been disappointed once, a crew is tempted to skip it next time and use informal language instead, which produces nothing at all.
Fuel distress is a statement about a landing quantity
The distress announcement uses standard distress phraseology followed by the word identifying the nature of the emergency, and it is a declaration of an emergency in the full sense, with all that implies for handling, for reporting and for the paperwork that follows. Its trigger is a prediction: the calculated usable fuel on landing at the nearest aerodrome where a safe landing can be made is below final reserve.
Three words do the work. Calculated: someone has done the sum, using track miles, level, configuration and approach. Nearest: not the destination, not the planned alternate, not the field the company would prefer, but the nearest one where the aeroplane can actually land — often one nobody has looked at. Landing: the comparison is made at touchdown, not now.
The consequence is that the declaration becomes correct while the tanks still hold a comfortable-looking quantity. A crew whose fuel state will put them below final reserve on the ground at the nearest suitable field is in a distress condition even though nothing is flashing. Waiting for a state that looks like distress means waiting past the moment when the call could still change the outcome.
An A320 is at 20,000 feet, 150 NM from destination, with 3,000 kg of fuel remaining. The nearest suitable airport is 100 NM away with a 1,500-meter runway. The crew calculates that after descent and approach, they will land with only 200 kg (5 minutes) of fuel. This triggers a “Mayday fuel” call, even though the fuel quantity looks high.
The prediction that has to precede the call
The second announcement is only as good as the arithmetic that produces it, and that arithmetic has to be maintainable in the cruise by two people who also have an aeroplane to fly. It is not a spreadsheet. It is a short, repeatable comparison, and its inputs are known in advance.
| Input | Where it comes from | The usual error |
|---|---|---|
| Fuel on board now | Totaliser, cross-checked against flight plan burn | Single source, no cross-check: a leak reads as normal |
| Track miles to the candidate aerodrome | The routing you will actually be given, plus the approach | Direct distance used, understating the requirement by the whole arrival |
| Descent and approach allowance | Operator tables or a rule of thumb for the type | Omitted, because the cruise figure was used all the way to the threshold |
| Level and configuration | Levels available rather than planned; gear or flap already out changes everything | Cruise level assumed after a descent has been imposed |
| Final reserve in today’s terms | Approved fuel policy, converted to present mass | Remembered as a duration from another weight |
| Contingency for one more change | One re-sequence, one go-around, one runway change | Assumed to be zero, so the first surprise eats the reserve |
The practical form is a running comparison with two answers rather than one number: what do I land with here, and what do I land with at the nearest alternative. When the second answer falls below final reserve, the distress call is due. When only the first does, the correct action is not a call at all — it is a diversion.
The right reflex. Fix the point at which you will decide, not the quantity at which you will worry. Before top of descent, name the aerodrome you would go to, the track miles to it and the figure below which you leave. A number written down before the pressure starts is worth more than any reasoning done while being vectored.
What the controller does with each, and what they cannot do
Controllers work from published procedures, and those procedures separate the two announcements sharply. On the advisory, the expected action is to inform the aircraft of any anticipated delay, or that none is expected. On the distress declaration, the flight receives priority and full emergency handling.
What a controller cannot do is interpret. « We are getting a bit tight on fuel », « we would like to be reasonably quick », « we cannot take much more holding » have no defined status. They may be understood by an experienced controller on a quiet frequency, and they may vanish entirely on a busy one, across a language boundary, or on handover to the next sector — because there is no defined phrase to hand over. The standard phrases survive relay; informal ones do not.
The harmonised wording in use today emerged in the early 2010s precisely because incompatible local usages coexisted, and because accidents had shown what happens when a crew believes it has communicated urgency and the system has recorded none. Avianca 052 in 1990 remains the reference case: a crew that repeatedly said it was running out of fuel, in terms that were true and produced no defined action. The lesson is uncomfortable — the crew’s private understanding of its own situation changes nothing. Only the transmitted phrase does.
Where ICAO and the FAA part company
The structure above is the ICAO one, adopted in the European rules; it is not universal in its wording. United States practice keeps the advisory notion — a minimum fuel advisory, indicating that the flight cannot accept undue delay on reaching the destination — but does not use a distress phrase built around the word fuel. Where the ICAO scheme expects a specific distress call, the American construction expects a plain declaration of an emergency together with a report of fuel remaining in minutes. The underlying idea is identical: an advisory that conveys lost options, a declaration that conveys a broken margin. The words differ, and so does what a controller expects to hear next.
For a crew operating both sides of the Atlantic, the rule is not to memorise both scripts and hope to select the right one under pressure. A declared emergency works everywhere. A pilot who declares an emergency and states fuel remaining in minutes has communicated unambiguously in any airspace; one who has picked the wrong regional phrase has communicated nothing.
How this goes wrong
The failure patterns are stable enough to list, and none is a knowledge failure: everyone involved knew the definitions.
| Pattern | What it looks like from inside | What it costs |
|---|---|---|
| Waiting for the gauges | The prediction says the margin is gone, but the quantity displayed still looks liveable, so the call is postponed | The declaration arrives when it can no longer change the routing that caused the problem |
| Informal language | Urgency communicated in ordinary words, believed to have been received | No defined action, nothing recorded, nothing handed over to the next sector |
| The advisory used as a request | Minimum fuel transmitted in the expectation of priority, and disappointment when none arrives | Loss of confidence in the phrase, and a temptation to skip it entirely next time |
| Reversed order | Distress declared first, then downgraded, or the advisory made after the margin is already broken | Either an unnecessary emergency, or a real one announced too late to matter |
| The nearest field never identified | Only destination and planned alternate exist in the crew’s mental picture | The comparison that triggers the distress call has no subject |
| Configuration ignored | Consumption still assumed nominal after an abnormal configuration or a low level | The prediction is wrong in the direction that hurts |
Making the thresholds computable before you need them
Both announcements are outputs of a calculation, and a calculation cannot be started at the moment its answer is needed. The work belongs earlier.

Three habits carry most of the weight. Convert final reserve into minutes at today’s weight, out loud, during descent preparation, so every later comparison is against a live figure rather than a remembered one. Name, before top of descent, the nearest aerodrome at which the aeroplane could actually land — length, approach aid, hours of operation — because that is the field the distress trigger refers to, and it is frequently not the planned alternate. Fix a decision fuel and a decision time in advance, and treat them as commitments rather than as prompts to reconsider.
Done this way, the two phrases stop being escalation steps and behave like what they are: two answers to two different questions, each correct at a particular moment. The advisory is correct when the options are gone and the delay is unknown. The distress declaration is correct when the prediction, honestly made, says the reserve will be broken. Neither is a confession of poor planning, and both are late once the arithmetic has failed on its own. The in-flight fuel management behind these calls is worked through in the operations modules at FL330 training.

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