Landing performance is one of the most critical preflight calculations a flight engineer performs on every trip segment. Unlike cruise or climb performance, landing performance has a hard, unforgiving endpoint: the end of the runway. Transport-category aircraft must meet strict regulatory requirements that ensure a safe margin between the actual stopping distance and the runway length available. Understanding how these requirements are calculated, what variables affect them, and where the regulatory limits are set is essential knowledge for any flight engineer applicant and for everyday line operations.
The Pilot's Handbook of Aeronautical Knowledge (FAA-H-8083-25C) provides foundational performance concepts that underpin the more specific transport-category requirements found in 14 CFR Part 25 and Part 121. While the handbook is not exclusively a transport-category reference, its treatment of landing distance, runway slope, wind, density altitude, and weight effects forms the conceptual backbone of the more detailed engineering analyses required for air carrier operations.
How Landing Distance Is Determined
Landing distance is broken into two phases: the air distance (from the screen height — typically 50 feet above the runway threshold — to touchdown) and the ground roll (from touchdown to a full stop). The sum of these two segments is the total landing distance. Manufacturers publish this distance in the Airplane Flight Manual (AFM) for specific conditions of weight, pressure altitude, temperature, flap setting, and wind. The flight engineer must use the AFM data — not generic charts — as the regulatory baseline.
Several physical factors increase or decrease landing distance in predictable ways:
- Gross weight: Heavier aircraft arrive at a higher approach speed (VREF is proportional to the square root of weight) and carry more kinetic energy that must be dissipated. Increased weight dramatically increases both air distance and ground roll. A 10% increase in landing weight can increase landing distance by roughly 21% because kinetic energy scales with the square of velocity, and velocity itself increases with weight.
- Density altitude: Higher pressure altitude or higher temperature reduces air density. This means the aircraft must fly a faster true airspeed for the same indicated airspeed (VREF is an IAS, but the actual speed over the ground is higher), and aerodynamic braking (spoilers, reversers drawing on aerodynamic drag) is less effective. Ground roll increases significantly at high-altitude or hot airports.
- Wind: A headwind reduces groundspeed at touchdown, directly shortening ground roll. A tailwind increases groundspeed and has a disproportionately large effect — a 10-knot tailwind can increase landing distance by roughly 20–25%. Crosswinds do not directly change stopping distance in the same way, but they limit the available braking if differential braking must be used to maintain directional control.
- Runway slope: An upsloping runway aids deceleration; a downsloping runway works against it. Even modest downslopes add meaningful distance on large, heavy aircraft.
- Runway surface condition: Dry, grooved pavement allows maximum braking. Wet, icy, or contaminated runways dramatically reduce the available coefficient of friction. Operations on wet or contaminated runways require the use of increased landing distance factors specified by the manufacturer and applicable regulations.
- Flap setting: Full flap configuration produces maximum lift and drag, resulting in the lowest VREF and shortest landing distance. Reduced-flap configurations increase both approach speed and stopping distance.
Regulatory Landing Distance Requirements for Transport-Category Aircraft
For air carrier operations under 14 CFR Part 121, the regulatory landing distance requirement does not simply ask whether the airplane can stop within the available runway length under ideal conditions. The regulations impose a safety factor that requires the unfactored demonstrated landing distance from the AFM to be no more than 60% of the available runway length. Stated the other way, the available runway must be at least 167% of the required landing distance (since 1 ÷ 0.60 ≈ 1.667). This safety margin accounts for normal variations in pilot technique, brake effectiveness, runway condition, and other operational variables not captured in idealized AFM testing.
The relevant regulations distinguish between dry and wet runway requirements. For wet runways, an additional factor is applied on top of the dry landing distance, increasing the required runway length further. Flight engineers and dispatchers must check forecasted and current runway conditions as part of release planning and must update calculations if conditions change prior to landing.
It is also important to distinguish the alternate airport planning requirement from the destination requirement. Part 121 allows a slightly relaxed factor for alternate airports in certain circumstances, but the destination requirement of 60% runway utilization applies at the planned landing airport.
Why Landing Performance Matters to the Flight Engineer
The flight engineer occupies a unique position in the three-person cockpit: while the captain and first officer focus on aircraft control and communications, the FE monitors systems and performance continuously throughout the flight. Before descent, the FE recalculates landing weight (accounting for fuel burned), determines the correct VREF for that weight and flap setting, and verifies that the destination runway meets the regulatory length requirements at the current forecast conditions.
If an en route diversion becomes necessary, the FE must rapidly compute landing weight, VREF, and runway adequacy for the alternate. This is not an academic exercise — air carrier accidents have resulted from landing on runways that appeared adequate but, after accounting for actual weight, tailwind, wet surface, and slope, were not.
Under 14 CFR § 121.387, a qualified flight engineer is required at the FE station for the entire flight whenever the airplane's type certificate requires one, and independently, for any airplane type certificated before January 2, 1964, with a maximum certificated takeoff weight of more than 80,000 pounds. This reflects the historical complexity of managing performance, systems, and fuel on large early-generation jet and piston transports — tasks that remain critical today on the platforms that still require a three-person crew.
Key Numbers and Rules
- 50-foot screen height: The standard obstacle clearance height at the runway threshold from which AFM landing distance is measured.
- 60% rule: Under Part 121, the AFM demonstrated landing distance must not exceed 60% of the available runway length (i.e., runway must be at least 167% of demonstrated distance).
- Weight-distance relationship: A 10% increase in landing weight typically increases landing distance by approximately 21% due to the squared relationship between weight and kinetic energy.
- Tailwind penalty: A 10-knot tailwind typically increases landing distance 20–25%; regulations limit the tailwind component used in planning (operators often limit to 10 knots maximum).
- Wet runway factor: Part 121 requires an additional factor for wet runways beyond the standard dry-runway demonstrated landing distance.
- VREF: The reference landing speed, typically 1.3 times the stalling speed in the landing configuration (VS0) at the actual landing weight, as specified in the AFM.
- AFM primacy: The AFM landing distance data is regulatory; performance charts in the POH or generic tables are informational only for transport operations.
Common Test Traps
- Confusing the 60% rule direction: Examinees sometimes state that the airplane needs 60% of the runway, when the rule means the demonstrated distance must fit within 60% of the available runway — a meaningful distinction on short fields.
- Ignoring the tailwind multiplier: Students often underestimate how much a tailwind increases landing distance. A small tailwind component (even 5–7 knots) can push a borderline calculation over the limit.
- Using sea-level AFM data at high-altitude airports: Failing to account for density altitude when applying performance charts is a classic error. Temperature and pressure altitude must both be entered correctly.
- Assuming wet-runway performance is just slightly worse: Braking coefficient on a wet grooved runway can be half or less that of a dry runway; the distance increase is substantial, not marginal.
- Mixing up FE certificate requirements with ATP requirements: On FE written-test questions about eligibility, there is no 1,500-hour total-time requirement for the flight engineer certificate. That figure applies to the ATP certificate under 14 CFR § 61.159. The FE certificate under Part 63 provides multiple alternative experience routes in § 63.37, none of which require 1,500 hours of flight time.