The balanced field length is taught as the answer and is, most of the time, only the default. It equalises two distances — the one needed to stop and the one needed to go — and that equality is optimal in exactly one case: when the runway offers the same length for both. Add a clearway, add a stopway, put an obstacle in the departure sector, and the decision speed that maximises the weight moves away from the balanced value, sometimes by a great deal. Knowing which way it moves, and why, is the difference between reading a performance figure and understanding what it cost.
What « balanced » actually equalises
V1 is not a single idea wearing one name. It is simultaneously the highest speed at which the first stopping action may still be taken and the take-off abandoned within the distance available, and the lowest speed from which, after an engine failure, the take-off may still be continued to the screen height within the distance available. Those two definitions constrain the same number from opposite directions, which is why the number sits in a range rather than at a point.
A take-off is called balanced when the accelerate-stop distance required and the accelerate-go distance required come out equal. That equality is a property of the chosen V1, not of the runway: raise V1 and the stop distance grows while the go distance shrinks, because the engine now fails later, with more energy to dissipate and less remaining to be recovered. Lower V1 and the reverse happens. Somewhere in between the two distances cross, and that crossing is what the balanced field length names.
The certified distances behind those curves are not naive. On a dry runway the accelerate-stop distance takes no credit for reverse thrust, and modern certification adds a distance equivalent to two seconds at V1 to the demonstrated stopping distance — an allowance for the fact that a real crew does not transition instantaneously from a take-off configuration to a full stopping configuration. Wet data may be built differently, and older certification bases may not carry the same allowance. The accelerate-go distance is measured to a screen height of 35 ft on a dry runway; on a wet one the operational rules allow the screen to be lowered to 15 ft, with the conditions attached to that relief.
A balanced V1 is the speed at which the distance to stop and the distance to go are equal. If the runway has extra space (like a clearway), V1 can shift to let the plane carry more weight by trading stop margin for climb performance.
The two curves, and why the crossing is usually the answer
Turn the two distances into weights and the picture becomes the one the performance software actually solves. For a given V1, one weight is the maximum that can still be stopped inside the accelerate-stop distance available, and it falls as V1 rises. A second weight is the maximum that can still be flown to the screen height inside the take-off distance available, and it rises as V1 rises. The allowable weight at any V1 is the lower of the two, so the best available weight sits at the crossing of a falling line and a rising one.
That construction explains the popularity of the balanced solution and also its limit. The crossing maximises the field-length-limited weight — but only when the two distances available are themselves equal, because it is the vertical position of each curve that decides where they meet. Change one distance available without changing the other and the whole geometry shifts.
On a runway with 2,000m TORA and 2,500m TODA (due to a 500m clearway), the balanced V1 might be 120 knots. But with the clearway, the optimum V1 drops to 110 knots, allowing 5 tonnes more payload by trading stop margin for extra climb performance.
What a clearway does to the optimum
A clearway lengthens TODA and leaves ASDA alone. In the two-curve picture the go-limited weight curve lifts — every V1 now permits more weight in the continued case — while the stop-limited curve stays exactly where it was. The two lines cross further to the left and higher up. The optimum V1 falls below the balanced value and the allowable weight rises. This is the unbalanced, or offset, V1, and it is not a refinement: where the clearway is substantial, the weight it recovers is large enough to change what the aeroplane can carry.
The mechanism is worth stating in plain terms, because it is counter-intuitive on first reading. Lowering V1 means committing to stop from a lower speed, which is cheap in distance, and paying for it by having to accelerate to the screen height on one engine from further back, which is expensive in distance — but expensive in a distance you have just been given for free beyond the runway end. The clearway is bought with stop margin, and stop margin is the one currency the crew is not short of when the stopping distance is not the binding constraint.
The trap. A clearway does not extend the take-off run available. The certified take-off run required is measured to a point midway between lift-off and the 35 ft screen, and it must still fit inside TORA. On runways with a long clearway the calculation therefore stops being clearway-limited at some point and becomes run-limited instead, and further reductions in V1 buy nothing. Software applies that cap silently; a hand-built optimisation does not.
What a stopway does, and why it is rarer
A stopway lengthens ASDA and leaves TODA untouched, so it lifts the stop-limited curve and pushes the crossing to the right: a higher optimum V1 and, again, a higher allowable weight. Structurally it is the more demanding of the two, because it has to carry the aeroplane rather than merely be free of obstacles, and that is why clearways are common and stopways are not.
The two are not interchangeable and cannot be traded. Counting a stopway in the go case, or a clearway in the stop case, is a straightforward error that produces an aeroplane that either cannot stop on the surface it planned to use or cannot reach the screen height where it planned to reach it. The declared distances exist precisely to keep the two accounts separate, and the aerodrome’s published set is the only authority on them — not the paved surface visible from the flight deck, which frequently includes areas that count for neither.
| Configuration | Which curve moves | Optimum V1 | Effect on allowable weight |
|---|---|---|---|
| ASDA equal to TODA, no clearway or stopway | Neither | The balanced value | Maximum available from field length alone |
| Clearway present (TODA greater than ASDA) | Go-limited curve rises | Below balanced | Higher, until the take-off run cap binds |
| Stopway present (ASDA greater than TODA) | Stop-limited curve rises | Above balanced | Higher, until VR or brake energy binds |
| Wet or contaminated surface | Stop-limited curve falls sharply | Below balanced, often at the VMCG floor | Lower; the stop case dominates |
| Climb or obstacle limited, field length surplus | Neither is binding | Indeterminate over a range | Unchanged by V1 — the constraint is elsewhere |
When the decision speed buys nothing at all
The most common misreading of the whole subject is to treat V1 as a weight lever in all circumstances. It is a lever only while field length is the binding limit. A performance calculation delivers several candidate weights — field length, climb gradient, obstacles in the departure sector, tyre speed, brake energy, structural limits, sometimes runway or aerodrome restrictions — and the take-off weight is the lowest of them. If the lowest is the second-segment climb limit, then moving V1 anywhere within its legal range changes the field figure and changes nothing about the answer.
That climb limit is a certification floor, applied one engine inoperative with the gear retracted at V2: the certified steady gradient must reach 2.4 per cent for a two-engined aeroplane, 2.7 per cent for three and 3.0 per cent for four. Obstacle work then uses the net flight path, which is the gross path reduced by 0.8, 0.9 and 1.0 percentage points respectively, and that net path must clear obstacles in the departure sector by 35 ft vertically. Those reductions are not conservatism added by the operator; they are the built-in margin, and they are consumed whether or not anyone looks at them.
Improved climb: paying runway for gradient
The reverse trade is the one that turns surplus field length into climb performance. When the runway is long and the limit is climb or obstacle, the take-off can be flown at increased V2 — and therefore increased VR and V1 — which raises the speed at the screen height and buys a steeper one-engine-inoperative gradient, at the cost of a longer ground run and a longer accelerate-go distance. The aeroplane is then no longer field-limited but it is no longer wasting the field either.
This is the honest statement of the arbitrage in the title. Stop margin, go distance and climb gradient are three claims on the same runway, and only one of them can be maximised at a time. The balanced solution maximises neither the weight nor the gradient; it maximises nothing except the symmetry of two distances that the aerodrome had no reason to make symmetric.
The right reflex. Before assuming a take-off is field-limited, read which limit the calculation actually returned. If the answer is climb or obstacle, the V1 conversation is over and the useful levers are flap setting, improved climb and thrust. If the answer is field length, then ask whether the runway has a clearway or a stopway — because that single fact tells you which side of balanced the best decision speed lies on.
The floors and ceilings that overrule the optimum
The optimisation lives inside a box. V1 may not exceed VR, because a decision speed above the rotation speed is meaningless. It may not exceed the maximum brake energy speed, which falls with altitude, temperature, tailwind and downslope and is the constraint most often forgotten on a hot high aerodrome. And it may not fall below VMCG, the minimum control speed on the ground, because below that speed the aeroplane cannot be kept on the runway with an engine failed and the concept of continuing does not exist.
On a wet or contaminated runway the box tightens from both sides at once: the stop distance grows, pushing the optimum down, while VMCG does not move. It is entirely normal on a short wet runway for V1 to sit on its floor, for the take-off to be stop-limited, and for the theoretical optimum to be unreachable. That is not a defect in the calculation; it is the calculation telling the crew that the margin it has been asked to find does not exist.
Reading the output on the day
What all of this changes in practice is the interpretation of a number the crew did not compute. A take-off performance output carries more than a weight and three speeds: it carries which limit produced them, what surface state and wind were assumed, what flap and thrust setting the speeds belong to, and — where the software offers it — whether the V1 is balanced or offset. A V1 noticeably below the balanced value on a long dry runway often means a clearway is being counted; one noticeably above often means a stopway is — though a brake-energy cap, a contaminated-runway case or an improved-climb solution can produce the same signature, and only the limit returned with the figures settles it. Either way the offset tells the crew where the margin has been placed.

The operational consequence is narrow but real. On an offset-low V1 the aeroplane is committed to continue earlier than instinct suggests, and the stop case has been deliberately made comfortable in exchange. On an offset-high V1 the reverse holds and the brake energy question is closer to the surface. In both cases the calculated number is not a compromise between two philosophies; it is the exact point at which the aerodrome’s asymmetry has been converted into payload. Performance discussions of this kind, and the worked examples behind them, run regularly on the FL330 forums.
The last thing worth keeping is the caution. Every figure in the output rests on assumptions — a briefed wind, a declared surface state, a serviceable aeroplane, a specific runway entry point — and an intersection take-off, a wind change or an unswept contaminant invalidates the optimisation without changing a single figure on the printout. The optimum V1 is only optimal for the runway that was actually described to the computer.

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