Landing Distance: From the Certification Demonstration to the Number You Compute on the Day

A test pilot executing a precise, minimal-flare landing on a dry runway at dusk, demonstrating certified landing distance.

Four different numbers travel under the name « landing distance », and they are not versions of each other. One comes from a test pilot who knew exactly where he was going to put the wheels. One comes from a rule written to protect a decision taken hours before anybody knew the weather. One models what line crews actually do. One is computed in the cruise, on the conditions of the day, and it is the only one that answers the question the aeroplane is about to ask. Knowing which margin pays for which uncertainty is what separates a briefed number from a copied one.

Inside the certification demonstration

The scheduled landing distance in an aeroplane flight manual is the reduced product of flight test. The measured quantity runs from fifty feet above the landing surface to a full stop, on a dry, level, hard-surfaced runway, at the weight under test, with a stabilised approach flown at the reference speed and maximum manual braking applied without delay. For transport aeroplanes, reverse thrust earns no credit on a dry runway: the certified figure is what the wheel brakes and aerodynamic drag alone will do.

The technique behind that figure deserves to be pictured. The test pilot is flying to a target touchdown point he has practised, in an aeroplane instrumented to tell him exactly what happened, on a runway he does not need to share. The flare is minimal, the float is nearly nothing, the brakes go on at once and stay on. Nobody is managing passengers, a late runway change, a gusting crosswind or a first officer’s first landing on type.

None of that is a criticism of the method: a certification number has to be attributable to the aeroplane rather than to the crew, and the only way to get that is to remove the crew as a variable. But it means the flight manual distance is a floor, not an expectation, and every factor applied downstream exists to buy back something the demonstration deliberately excluded.

The certification landing distance is a test result under perfect conditions. Real landings are messier, so extra margins are added later.

An Airbus A320’s certified landing distance might be 1,500 m, but a real landing with a 10 kt tailwind on a wet runway could require well over 2,000 m.

The dispatch factor pays for a decision taken hours early

The rule most crews can quote is the dispatch requirement: for a turbojet operated commercially under the European air operations rules, the aeroplane must be able to stop within sixty per cent of the landing distance available at the destination, on the forecast conditions for the estimated time of arrival. If the runway is expected to be wet, the required dry distance is increased by fifteen per cent. Turboprops are given a less demanding percentage. The American equivalent in 14 CFR Part 121 works the same way and uses the same sixty per cent and the same wet increment.

What is easy to lose is what that factor is buying. It is not a margin against the landing you are about to fly. It is a margin against a planning act performed before departure, on a forecast, for a runway that may not be the one in use, at a weight that will not be exactly the weight, flown by a crew that has not yet been assigned. It also absorbs the enormous gap between test-pilot technique and normal line technique. Three fifths of the runway required at dispatch is the aeroplane’s own stopping distance; the remaining two fifths is everything nobody could know at the time.

The consequence follows immediately. Satisfying the dispatch rule tells you that the flight was legal to plan. It tells you nothing whatever about whether the aeroplane will stop today, because every input that made the dispatch calculation valid is now three hours old.

Advisory data is a different baseline, not a softer one

Alongside the flight manual, manufacturers publish operational landing distances built to model what a line crew actually does. The air distance from fifty feet is longer and more realistic than the flight-test value. Speed additives for wind and gust are included. Each autobrake setting has its own table, because an autobrake schedules a target deceleration rather than the maximum the brakes can produce — which on a dry runway frequently gives a longer stop than maximum manual braking, in exchange for consistency and passenger comfort. Reverse thrust appears, and so do models for contaminated surfaces that the certification basis never had to cover.

The trap is arithmetic. Because advisory distances are longer than flight manual distances for the same conditions, it is tempting to treat them as a conservative version of the same quantity and apply the dispatch factor to them as a belt-and-braces exercise. They are not the same quantity. They already contain a realistic technique allowance, so factoring them by 1.67 double-pays for the same uncertainty and produces a number that no longer corresponds to any question. Conversely, applying a fifteen per cent margin to a flight manual distance and calling the result an arrival assessment under-pays, because the flight manual distance never contained a technique allowance at all. The margin is only meaningful against the baseline it was written for.

The trap. Two aeroplanes, two figures, same runway, same day — and one crew has factored certified data while the other has factored advisory data. Both did arithmetic they can defend and the answers are hundreds of metres apart. Before applying any factor, establish which table you are on: certified flight manual data, or manufacturer advisory data with technique already inside it.

The arrival assessment asks a different question

The in-flight landing distance assessment exists because a series of overruns showed that a dispatch calculation performed hours earlier, on a forecast, was not protecting arrivals onto degraded surfaces. The FAA’s response after the Chicago Midway overrun of December 2005 was a safety alert recommending an assessment at the time of arrival with at least a fifteen per cent margin over the distance computed for the actual conditions. Europe subsequently built the same requirement into the air operations rules as a landing performance assessment before commencing the approach, with the same minimum factor where the data does not already contain it.

Two properties make it a genuinely different exercise rather than a repeat. First, its inputs are real rather than forecast: reported runway condition, measured wind, actual landing weight, the configuration and autobrake actually selected, the reverse actually available. Second, the fifteen per cent covers a much narrower set of unknowns — the residual scatter around a technique that is otherwise specified. Where the aeroplane touches down, how quickly the brakes come on and what speed is carried over the threshold are no longer buried inside a blanket factor; they are the crew’s to control, and the margin no longer pays for gross departures from them.

That is the pivot of the whole chain. The dispatch factor is generous because it must cover ignorance. The arrival factor is thin because ignorance has been replaced by information — and it only stays adequate if the landing is flown the way the data assumed.

The arrival assessment uses real-time data and a smaller margin because the crew knows more when they land than when they took off.

An A380 landing at 380 t with a 10 kt tailwind might need 2,800 m at dispatch, but only 2,400 m at arrival with the actual conditions.

Which margin pays for which uncertainty

What each factor buys, and what it explicitly does not
Margin Pays for Does not pay for
Sixty per cent dispatch factor (jet) Forecast error, weight change, unknown crew and technique, runway change, normal deceleration devices not credited A surface condition worse than forecast, or a landing distance available reduced after planning
Wet increment at dispatch The friction penalty of a wet, non-contaminated surface Standing water, slush, snow, ice, or a rubber-contaminated touchdown zone
Fifteen per cent arrival margin Residual scatter around a specified technique and reported condition A long flare, a late brake application, an unfactored tailwind, or a condition report that has aged
Wind factoring rule Wind variability, by crediting at most half the headwind and charging at least one and a half times the tailwind A wind that changes between the report and the flare

Set out that way, the redundancy becomes visible. Dispatch and arrival both pay for technique — the first with a third of a runway, the second with fifteen per cent — so a crew who computes an arrival distance and then congratulates itself on also meeting the sixty per cent rule has counted the same protection twice and learned nothing new.

The hole is more important than the overlap. The dispatch rule was satisfied against a forecast of a wet runway. The aeroplane arrives onto compacted snow with a downgraded condition code and a tailwind component. Nothing in the dispatch calculation extends to that case, and it is entirely possible to have been comfortably legal at departure and to have no viable landing distance at arrival. The dispatch rule cannot fail in flight, because it is not evaluated in flight. Only the arrival assessment can.

Runway condition codes and the chain that feeds them

Since the Global Reporting Format became applicable in November 2021, the aerodrome describes each third of the runway with a condition code and a description of contaminant type, depth and coverage, and the crew converts that code into a landing distance through the manufacturer’s table. The code is the hinge between two organisations that never speak directly, and it carries the weaknesses of any hinge: it is an assessment, made at a moment, over a surface that changes.

Runway condition codes and what they hand the crew
Code Braking action equivalent What it means for the arrival computation
6 Dry The certified baseline; the only case where reverse earns nothing
5 Good A surface that behaves close to dry; distances grow modestly
4 Good to medium Distances lengthen materially; wind and touchdown accuracy begin to dominate the result
3 Medium Reverse becomes a significant contributor; crosswind limits usually tighten
2 Medium to poor Distances climb steeply; directional control, not stopping, often becomes the limit
1 Poor The lowest code for which manufacturers normally publish data; many operators restrict it further
0 Less than poor, or unreliable No landing distance data is published; the landing cannot be assessed

Two habits make the code usable. The first is treating the time of the report as part of the report: a code assessed before the last snow shower, or before four aeroplanes have landed and polished the touchdown zone, is a historical statement. The second is the special air-report of braking action — a crew observation that can downgrade the code for everybody behind. It is the only feedback path in the system, and it is the one that goes unused most often, usually because the aeroplane that could have filed it was busy vacating.

The inputs that move the number most

Sensitivity is worth carrying as physics rather than as a memorised list. On a friction-limited surface the stop is essentially kinetic energy divided by braking force: distance grows with the square of the speed at touchdown. Reference speed grows with the square root of weight, so to a first approximation the ground roll grows roughly in proportion to weight on a dry runway — but any excess speed carried over the threshold is charged at the square.

Air distance is the other half, and it is pure arithmetic. At a groundspeed of one hundred and thirty knots the aeroplane covers something on the order of two hundred and twenty feet every second. A three-second float and a two-second delay before the brakes bite are not sloppiness on a long dry runway; on a code 3 surface at a heavy weight they can consume the whole of the fifteen per cent margin before deceleration begins.

Wind is charged asymmetrically for the same reason: the rules require that no more than half a reported headwind be credited and no less than one and a half times a reported tailwind be charged. Slope acts on the same energy balance. And on a flooded surface the risk is not gradual degradation but a threshold — the classical estimate for a rotating tyre ties the onset of dynamic hydroplaning to the square root of tyre inflation pressure, which is why the useful question on a wet runway is not « how much longer » but « at what speed do the brakes stop mattering ».

The right reflex. Brief the assumption, not just the answer. « Two thousand one hundred metres required against two thousand six hundred available, code 4, autobrake 3, both reversers, touchdown in the zone, no float » is a briefing a first officer can call you on. A number alone cannot be challenged, because nobody else knows what went into it.

Briefing a number instead of reading one

Runway excursions remain one of the most frequent accident categories in commercial operations, and the recurring pattern is rarely a computation error. It is a computed distance that assumed a technique nobody then flew: an assessment done for the reported code and the planned autobrake, followed by a long flare, a late reverse selection or an acceptance of a tailwind that arrived after the figure was fixed.

Two pilots in a cockpit reviewing a document with performance data.
Performance data is critical for accurate landing distance calculations.
  • Always brief the assumptions behind your landing distance calculation
  • Include touchdown point, autobrake setting, reverse thrust availability, and any wind factors
  • Establish “gates” that trigger a recalculation (e.g., condition code downgrade, weight change)
  • Keep the go-around decision tied to assumptions, not just the distance number

The practical defence is to make the assumptions audible and revocable. State the touchdown point and the deceleration configuration as part of the number, so that a change to either is recognised as invalidating it. Fix a gate — condition code downgraded, tailwind increased, weight or configuration changed — at which the assessment is redone rather than remembered. And keep the go-around attached to the assumptions rather than to the distance: a float that has already eaten the margin is a fact available at fifty feet, not a discovery to be made at the far end. Performance modules on FL330 training work through the same chain type by type.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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