Operating minima: where the numbers the crew applies actually come from

Pages d'un manuel d'exploitation étalées sous une lampe

Two aircraft arrive a minute apart on the same ILS, with the same reported visibility. The first lands; the second goes around at decision height. Neither crew made a mistake: the applicable minimum is not a property of the runway, it is the product of a chain that begins with the procedure designer and ends in a box of an operator’s approved manual. What remains is to know where each link sits, and which one moves on the day of the flight.

A minimum is not read, it is built

The question asked in the briefing room — “how much is it tonight?” — assumes there is a single figure sitting somewhere, ready to be copied down. There is not one, there is a series, and only the last value in the series is applicable. Each step takes the value handed down by the previous one and can do only two things with it: leave it unchanged, or raise it. None can lower it. That is the structuring property of the whole system, and it holds on both sides of the Atlantic regardless of the differences in form.

The starting point is a physical floor: the height below which the published flight path no longer guarantees obstacle clearance. Next comes the aircraft category, which decides which line of the table applies; the demonstrated capability of the aircraft and its automation; the approval held by the operator, which alone allows that capability to be used; the crew’s qualification and experience; and finally the actual state of the airfield at the time of arrival. Six filters, six opportunities to raise the number, none to lower it.

What this construction implies is easy to state and routinely forgotten: the figure printed on the approach chart is not necessarily yours. It describes what an operator holding every approval could do, with a fully serviceable aircraft, a seasoned crew and an airfield entirely in service. It applies to you only in proportion to the boxes you actually tick.

The chain of filters that raise an operating minimumA staircase rising from left to right. The first step, resting on the floor published by the State, corresponds to procedure design. The following steps — aircraft category, aircraft capability, operator approval, crew qualification, airfield status — stay at the same level or rise, never descend. The applicable decision height therefore always remains above or equal to the floor.applicable decision heightfloor published by the Statedesigncategoryaircraftapprovalcrewairfield
Each step can only leave the figure unchanged or raise it. The dashed line is the floor published by the State of the airfield; the value actually applicable is the last step of the staircase, never the first.

The operating minimum isn’t a fixed number on a chart. It’s built step by step, starting from a safety floor set by procedure designers. Each step (aircraft type, operator approvals, crew experience, etc.) can only keep the number the same or raise it. The final number is what the crew must use, not the one printed on the chart.

Three figures called by the same name

Before working back up the chain, three families that everyday usage lumps under the same word need to be separated. They share neither the same function, nor the same source, nor the same moment of application, and confusing them produces preparation errors far more often than piloting errors.

The three families of minima that everyday conversation confuses
Criterion Takeoff minimum Landing minimum Flight-planning minimum
What it guarantees seeing enough to hold the centreline and reject the takeoff seeing the required reference at the point where a go-around can no longer be flown without consequence that the chosen airfield will still be usable at the planned time, despite the uncertainty of the forecast
What mainly sets it runway lighting, the available measurement points, the approval to take off in low visibility the published procedure, the aircraft’s capability, the approval, the crew increments added to the landing minimum, which vary with the number and type of usable approaches
When it applies before beginning the takeoff roll at the approach gate and then at decision height at flight planning only
What makes it change in flight nothing: it is either met or it is not a failure carried under MEL tolerance, a runway facility out of service, a crew composition nothing on board: only a revised forecast changes the chosen airfield, and that choice can be remade for as long as the remaining fuel allows

The costliest confusion concerns the alternate. Flight-planning minima contain a margin meant to absorb the uncertainty of a forecast made several hours in advance: they serve to choose an airfield, not to land there. Once a diversion is under way, it is the ordinary landing minima that take over — an airfield ruled out at planning can perfectly well be usable on arrival. The reverse symmetry is more unpleasant: an airfield selected as an alternate guarantees nothing about its actual weather at the time you show up there.

An A320 is cleared to land at Paris CDG with a reported visibility of 400 meters. The flight-planning minimum for the alternate (Orly) was 800 meters, but at the time of diversion, Orly’s actual visibility is 500 meters. The crew can land because the landing minimum (not the flight-planning minimum) applies, and 500 meters meets it. However, if the crew had relied on the flight-planning minimum, they might have diverted unnecessarily.

The floor: what the procedure designer left

Every instrument procedure is built around protection areas that follow the nominal flight path, and within which obstacles are surveyed. The most penalising one dictates a clearance altitude, design margin included. That result is the absolute floor of the chain: no approval, no technique, no machine goes below it.

The two design schools — the international procedure criteria and the US federal criteria — do not always arrive at the same number for the same runway. They do not model the flight path the same way, do not size their protection areas by the same rules, and do not treat the go-around identically. The practitioner does not have to arbitrate between them, but should know that comparing, figure for figure, an approach seen through both bodies of criteria makes no sense: these are not two measurements of the same object.

Two floor parameters deserve particular attention because they keep coming up in everyday operations. The first is aircraft category, determined by its threshold speed at maximum landing mass. It is not a property of the type but of the mass and configuration adopted: an operator that has standardised a reduced landing configuration may find itself reading a more restrictive line of the table than the one it is used to. The second is the assumed go-around gradient. When a procedure requires a gradient steeper than the standard one, the published minimum assumes the aircraft can hold it in the conditions of the day, mass and temperature included: that becomes a performance condition to be checked, not a footnote.

From obstacle clearance to decision heightVertical cross-section of a final approach. A straight line descends from left toward the runway threshold. Two horizontal lines cross it: the lower one, dashed, marks the obstacle clearance altitude, set above the top of the most penalising obstacle; the higher one, solid, marks the applied decision height. From that point, a dashed go-around path dips slightly before climbing again, never reaching the clearance line.continuous descentdecision heightclearance altitudemarginobstaclego-aroundthresholdrunway
The obstacle clearance margin is not the decision height. It protects a go-around path that first loses altitude before climbing again: it is that dip, as much as the position of the obstacle, that explains the gap between the two lines.

The aircraft: what the flight manual demonstrates

The aircraft’s capability is a ceiling, never an entitlement. It is established at certification, described in the approved flight manual, and comes with conditions that are quickly forgotten: wind limits, runway slope, terrain profile ahead of the threshold for the radio altimeter, configuration, status of the redundant chains.

The structuring distinction is not the presence of an autopilot, but its behaviour after a failure. A fail-passive system stops guiding without an abrupt deviation: the crew must be able to take over, which presupposes seeing. A fail-operational system continues the manoeuvre despite the failure, and it is precisely that redundancy which opens up the lowest decision heights, down to no decision height at all. Between the two, the head-up display and enhanced vision systems occupy a place of their own: they do not lower the obstacle floor, they allow it to be reached with lower visibility by providing a usable reference earlier.

The minimum equipment list is where this capability degrades day to day. An automation channel, an air data unit, a landing light, a sensor: each can slide the aircraft from one category of operation to another. The MEL deferral is rarely read with that question in mind, even though it determines the figure that will be announced at the approach briefing three hours later.

The approval: where the figure becomes binding

This is where the two systems diverge most visibly, and where transatlantic misunderstandings thrive.

In the European system, the operator sets its own minima. It applies the method prescribed by the regulation, never goes below what the State of the airfield publishes, and records the result in its operations manual, under the oversight of its authority. What authorises low visibility operations does not appear in that manual but in the specific approvals annexed to the air operator certificate: without the corresponding entry, the machine’s capability remains theoretical and the manual cannot describe it.

In the US system, the published procedure carries its own minima, directly usable by a private operator. The airline, however, does not read that figure in isolation: its operations specifications, an individual document issued by the administration, can lower it once a particular approval has been processed, or raise it when oversight has judged it necessary. The reasoning is the same; the location of the figure is not.

The consequence is methodological. In Europe, one looks for the value in the operator’s manual and traces it back to the regulation to understand how it was derived. In the United States, one reads the chart and checks what the operations specifications do to it. Asking an American operator “where is your minima table” makes no more sense than asking a European operator “which paragraph of your specifications authorises this approach”.

Where each link of the chain resides in each system
Link European system US system
Obstacle floor clearance altitude or height established under the international design criteria, published by the State of the airfield minima published with the instrument procedure by the federal administration
Figure the crew applies value derived by the operator and entered in the operations manual value shown on the chart, corrected by the operations specifications
Approval to go lower specific approval annexed to the air operator certificate paragraph of the operations specifications issued to the operator
Runway equipment unavailable downgrade table kept in the operations manual inoperative components table published with the procedures
Conversion of a reported visibility converted meteorological visibility, factors depending on lighting and time of day, use excluded wherever a measured value is required published equivalence table, use bounded by the same exclusions
Continuation of the approach gate placed at a height of one thousand feet above the airfield gate placed at the final approach fix
Criterion at decision height availability of the required visual reference required visual reference and in-flight visibility assessed by the crew
Recently qualified captain increment prescribed by the rule, values in the operations manual increment prescribed by the scheduled-operations rule, until a threshold of hours in command on type is reached

The airfield, and what actually works there tonight

The airfield comes into play twice. Statically, through its permanent equipment: the type and length of the approach lighting system, centreline and touchdown-zone lights, markings, the number and location of the RVR measurement points, protection of the localiser’s sensitive areas. That inventory decides which line of the table you are on: the same approach does not give the same value depending on whether the runway has a full lighting system or minimal markings, and it is the lighting, far more than the airfield’s stated category, that governs.

RVR measurement points required by category of operationThree stacked rows, one per category of operation, against three measurement locations spread along a runway: touchdown zone, midpoint, far end. In Category I, only the touchdown-zone location carries a filled circle, the other two just a dash. In Category II, the touchdown zone and the midpoint carry a circle. In Category III, all three locations carry one. The number of required points increases as the decision height decreases.required measurement pointsCAT ICAT IICAT IIItouchdown zonemidpointfar end
The lower the decision height, the more the airfield must measure. The touchdown-zone point governs in every case; the following ones typically become required as you go lower, depending on the text the State of the airfield applies, which is enough on its own to close down a low operation on a runway that nonetheless has an ILS.

Dynamically, through what is actually in service. An approach lighting system partially unlit, a transmissometer unavailable, a low visibility procedure not armed at the required moment: each of these events raises the applicable minimum. The correction mechanism exists in both systems but does not live in the same place. American documentation publishes an inoperative components table with the procedures; European documentation places it in the operations manual. In both cases, the failure notice announces the fault, not its numerical consequence: the translation remains the crew’s responsibility.

The trap. The chart knows nothing about your evening. A downgraded centreline light, a measurement point out of service, or a low visibility procedure the airfield has not yet armed all change the applicable figure without any published document changing appearance. A crew that replays yesterday’s briefing on the same runway applies a value that no longer exists, and nothing on board will tell them so.

The crew: three requirements that stack

The last link is human, and it subdivides further. Qualification first: low visibility operations require dedicated training, recorded in the file, and both pilots must hold it. Currency next: those qualifications must be maintained, and their expiry does not ground the flight, it raises the applicable minimum. The difference matters, because a crew that is no longer current can still depart — just not with the figure it is used to.

Experience, finally. Both systems impose an increment on a recently qualified captain, for as long as they have not accumulated a certain number of hours in command on type. That increment adds to the decision height and to the required visibility; the order of magnitude is a hundred-odd feet and a fraction of a mile, but the exact value, like the hours threshold, is to be read in the operator’s documentation, not from a memory of ground school. The rule has a crewing consequence that scheduling often misses: a captain under increment cannot be freely paired with a freshly released first officer, and the network’s lowest approaches are not open to every pairing.

On the day of the flight: convert, continue, see

Three mechanisms close the chain, and these are the ones that play out in flight.

Conversion first. An airfield that does not report runway visual range reports meteorological visibility instead, which is not the same quantity: the first tells you what you will make out of the centreline lights, the second what you can make out of a dark object on the horizon. The European system provides for an explicit conversion, affected by a factor that depends on the lighting and the time of day, more favourable at night with high-intensity lighting. The US system publishes an equivalence table. In both cases the use of the converted value is bounded, and excluded exactly where precision matters most.

The second trap. Converting where it is forbidden produces a figure that does not exist. Reported visibility is not runway visual range, and conversion is ruled out for takeoff as much as for Category II and III approaches, where only a value measured on the runway concerned is authoritative. The calculation remains easy to do in your head, and its result looks reasonable: that is exactly what makes it dangerous.

Continuation of the approach next. Both bodies of rules forbid continuing once the reported value drops below the minimum, but they do not place the gate in the same spot. The European system places it at one thousand feet above the airfield: above it, a reported deterioration requires the approach to be discontinued; below it, the approach continues down to decision height. The US system places it at the final approach fix, with the same freezing logic: a message received after passing the fix does not require discontinuing. The practical outcome is close, the geometry is not, and a crew used to one gets the timing wrong when operating under the other.

The visual reference, finally. Both systems list what must be seen to continue below the minimum, and the lists are very similar: approach lighting, the threshold and its markings, threshold lights, touchdown zone, runway centreline. They differ on a point that is not minor. The US body of rules adds an in-flight visibility condition, assessed by the crew, which must not be less than that prescribed: the pilot is explicitly the judge of what they see, in addition to what has been reported. The European body of rules bases the decision on the sole availability of the required visual reference, the reported value having already played its part upstream, at the earlier gates. Same action on the controls, different foundation — and it shows in mixed debriefings.

The right reflex. Walk back through the chain, in three questions, before the approach briefing. What does the operator’s documentation authorise for this procedure and this category? What can the aircraft do tonight, MEL tolerances included? What does the airfield allow, lighting and measurement points included? The figure to announce is the highest of the three answers, never the chart’s by default.

What to go and check at home

Three checks pay off immediately. The first concerns the category adopted for your aircraft: it is written down somewhere, it was calculated at a given mass and configuration, and everyday practice sometimes drifts away from it without anyone redoing the calculation. An operator that has standardised a reduced landing configuration must make sure the table it reads still matches what it flies.

Two pilots in a cockpit at night review flight charts and checklists on clipboards.
Operating minima are carefully calculated and verified before each flight.

The second concerns the match between capability and approval. List the lowest minima your procedures describe, then find, for each one, the entry that authorises it: a specific approval on one side, a paragraph of the operations specifications on the other. Any mismatch signals a procedure written for a capability that nothing covers, and it is the first place an auditor looks.

The third concerns the translation of failures. Take three ordinary notices — a partial approach lighting failure, a touchdown-zone measurement point out of service, a downgraded centreline light — and ask a crew to produce the applicable figure. If the exercise takes more than two minutes or produces two different answers, the downgrade table is badly placed in the documentation, not badly written. It is also a good indicator during type-rating preparation: the chain is often known by heart and never walked backwards.

A grey area remains that no one ever quite closes off. That of airfields whose equipment is nominally compliant but whose actual maintenance is hard to gauge from the flight deck. And that of procedures designed under one set of criteria, flown by crews trained under the other, on aircraft certified under a third. It is precisely there that exchanges between practitioners of both systems teach more than a cross-reading of the texts.

This article describes a mechanism, not a table of figures. The applicable texts in their current version, the aircraft’s approved flight manual, the operator’s approved documentation, and the approvals actually entered in its operations specifications prevail in every circumstance over what is written here.

Questions fréquentes

Why is the minimum printed on the approach chart not always the one an operator applies?

Because the published value describes the most favourable case: every approval held, a fully serviceable aircraft, a seasoned crew, an airfield entirely in service. Every departure from that case raises the figure, never lowers it. The applicable value is the one that comes out of the full chain — that is, your operator documentation checked against the conditions of the day.

What is the difference between alternate minima and landing minima?

Alternate minima are used to choose an airfield during flight planning, with increments designed to absorb the uncertainty of a forecast made several hours in advance. They do not apply on arrival: once a diversion is under way, it is the ordinary landing minima that govern. An airfield ruled out at planning can therefore be perfectly usable by the time you show up there.

Can a reported visibility always be converted into runway visual range?

No. The conversion exists in both systems, with a factor that depends on the lighting and the time of day, but its use is ruled out wherever precision is decisive: takeoff and Category II and III approaches require a value measured on the runway concerned. Using a converted value in those cases amounts to applying a minimum that does not exist.

At what point must the approach be discontinued if the reported value drops below the minimum?

The European system places the gate at one thousand feet above the airfield: above it, a report below the minimum requires the approach to be discontinued; below it, the approach continues down to decision height. The US system places the same gate at the final approach fix, with the same logic: a message received after passing the fix does not require discontinuing. The logic is identical, the geometry is not.

Can a failure deferred under MEL tolerance change the applicable minimum?

Yes, and it is one of the most frequent effects. An unavailable automation channel, air data unit, sensor or landing light can slide the aircraft from one category of operation to another. The minimum equipment list says so explicitly, but the deferral is rarely read with that question in mind: it needs to be revisited when preparing the approach, not only at departure.

What difference does a recently type-qualified captain make?

Both systems impose an increment on them, added to the decision height and the required visibility, for as long as they have not accumulated a certain number of hours in command on type. The order of magnitude is a hundred-odd feet and a fraction of a mile, with the exact value found in the operator’s documentation. The practical consequence also concerns crew pairing and the assignment of the most demanding rotations.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

FL330, c’est toute l’aviation professionnelle — explorez nos autres espaces.