Take-off performance: cross-checks that catch the wrong answer

The UK CAA continues to receive reports of take-offs attempted with incorrect performance data, an incorrect thrust setting, or the wrong runway or intersection. Although its safety notice addresses learning across the industry, the underlying discipline is valuable anywhere performance calculation matters.

Calculation is only one layer

A polished output is not evidence that the inputs were right. A robust process confirms aircraft mass and configuration, runway and intersection, declared distances, surface state, wind, temperature, pressure altitude, obstacles and any applicable corrections or limitations.

A practical error trap

• State the runway and departure point aloud before accepting the result.
• Check that live conditions still match the calculation.
• Use the approved aircraft method and current aerodrome information.
• Ask whether the expected acceleration and available stopping options make sense.
• Recalculate after a material change instead of mentally adjusting an old result.

Performance margins should not be used to excuse uncertain inputs. If the result cannot be supported by approved data and current conditions, pause the departure.

What this means in practice

Performance software can calculate precisely from incorrect inputs. A credible result therefore needs two checks: trace each input to approved and current evidence, then ask whether the output is physically plausible for the aircraft and runway. Neither check replaces the other.

Runway selection errors are particularly deceptive because the calculation may still produce a complete set of numbers. State the airport, runway, intersection and declared distance aloud or in a challenge-and-response before accepting the result. Confirm that the aircraft is actually at that departure point before power is applied.

A verification workflow

• Use current aircraft mass, configuration and approved performance data for the exact model and any relevant modification.
• Verify runway, intersection, declared distances, slope, surface condition, wind, temperature, pressure altitude and obstacle assumptions.
• Apply corrections and limitations using the approved method rather than an informal percentage remembered from another type.
• Independently sense-check acceleration, margin and stopping options, and brief a point or cue for rejecting an abnormal takeoff where applicable.
• Recalculate after a runway, intersection, wind, temperature, loading or surface change instead of mentally adjusting an old result.

Scenario to rehearse

Taxi instructions change the departure from the full length to an intersection. The electronic result on the kneeboard still carries the original distance and looks comfortably within limits. The cross-check is procedural rather than mathematical: state the new departure point, verify the available distance from current information and rerun the approved calculation before accepting the change.

Limits of this briefing

This article does not provide takeoff distances, margins or rejection technique. Those depend on approved aircraft data, regulation, runway and operating procedure. A legal calculation can still be operationally unwise when inputs are uncertain or the available margin does not tolerate the real threats.

Debrief questions

• Can every input be traced to an approved or current source?
• Does the result belong to the runway and intersection beneath the aircraft?
• What change would invalidate the calculation?
• Which cue will trigger a stop if acceleration is not as expected?

A source-reading exercise