How does slush on the runway affect takeoff distance for a Part 121 aircraft?

Slush increases both fluid displacement drag and impingement drag on engines and airframe, which slows acceleration and extends the runway needed to reach rotation speed. At the same time, slush dramatically degrades braking effectiveness, extending the accelerate-stop distance. Dispatchers must apply AFM-approved contaminated-runway tables that account for both effects, which often require a significant reduction in allowable takeoff weight.

What is the minimum V1 a dispatcher can authorize on a contaminated runway?

V1 can never be reduced below VMCG, the minimum control speed on the ground, regardless of contamination corrections. VMCG is the lowest speed at which directional control can be maintained with an engine failure using only rudder input. If contamination requires an ASD correction that would push V1 below VMCG, the flight cannot be dispatched at that weight from that runway.

What is a Runway Condition Code and how does it affect dispatcher performance calculations?

A Runway Condition Code (RwyCC) is a number from 0 to 6 that standardizes runway surface reporting under the FAA's Global Reporting Format. A code of 0 represents the worst braking condition, while a code of 6 indicates a dry runway; codes of 3 and below (covering compacted snow, slush, and ice) trigger the most significant AFM performance corrections. Dispatchers use the reported RwyCC to select the appropriate contaminated-runway performance table, ensuring that accelerate-stop and takeoff distances reflect actual surface conditions.

Computing Takeoff Performance for Contaminated and Slush-Covered Runways

Few performance challenges are more consequential for an aircraft dispatcher than computing takeoff data for a runway covered with snow, slush, or standing water. Unlike a dry or wet runway where published performance tables apply directly, a contaminated surface introduces fluid drag, braking degradation, and potential for asymmetric thrust loss that can push a flight beyond its legal or physical performance envelope. Under 14 CFR Part 121, the dispatcher shares legal responsibility with the pilot-in-command for every dispatch release, and that responsibility extends to verifying that the aircraft can meet all applicable performance standards before the wheels ever begin to roll.

This article walks through the regulatory framework, the physics of contaminated-runway performance, the specific corrections dispatchers must apply, and the practical decision-making process that separates a safe authorization from an accident waiting to happen.

Regulatory Foundation

The governing regulations for Part 121 takeoff performance are found in 14 CFR 121.189 through 121.197. Section 121.189 establishes the basic requirement: no person may take off a turbine-engine-powered transport airplane at a weight that exceeds the limitations in the Airplane Flight Manual (AFM) for the airport altitude, ambient temperature, and runway length available. Section 121.195 extends this concept to landing performance. Critically, these sections require that the aircraft meet gradient and distance requirements with one engine inoperative, reflecting the fundamental reality that a contaminated runway emergency is often compounded by engine failure.

The AFM itself is the primary performance authority. Under 14 CFR 121.189(d), the certificated takeoff field length must account for the full accelerate-stop distance — the distance required to accelerate to V1, experience a failure, and stop — as well as the all-engines-operating and one-engine-inoperative takeoff distances. On a contaminated runway, the AFM-approved data or an approved performance engineering analysis must be used; extrapolating dry-runway charts to contaminated conditions without authorization is not permissible.

How Contamination Degrades Performance

Contamination affects takeoff in two interrelated ways: it increases drag during the ground roll, and it degrades braking effectiveness if the takeoff must be rejected. Understanding each mechanism is essential for interpreting the corrections the AFM or performance software applies.

Fluid Drag (Impingement and Displacement)

When an aircraft rolls through standing water, slush, or wet snow, the tires must continuously displace the fluid ahead of them. This creates two forms of aerodynamic and mechanical resistance. Displacement drag acts on the landing gear and lower fuselage as the fluid is physically pushed aside. Impingement drag occurs when fluid thrown up by the main wheels strikes the engine nacelles and airframe, effectively reducing net thrust. Slush is particularly destructive because its density — approximately 50–80% that of water — allows large quantities to be lofted at high velocity. At speeds above roughly 60–80 knots, impingement drag can be severe enough to measurably reduce acceleration rate. Some AFMs provide specific corrections for slush depth in tenths of an inch (e.g., 0.25 inch, 0.50 inch, 1.0 inch), and the dispatcher must use the table that most closely matches current ATIS or PIREP reports of contamination depth.

Braking Degradation

Contamination also reduces the friction coefficient between tire and pavement. On a dry runway, friction coefficients (mu) may reach 0.5 or higher. Packed snow reduces this to approximately 0.2, and wet ice can fall to 0.05 or lower. A lower friction coefficient means that if V1 is reached and a rejected takeoff (RTO) initiated, the aircraft requires significantly more runway to stop. This is why the accelerate-stop distance (ASD) is the critical constraint on contaminated runways — the stopping side of the performance equation expands dramatically even as the acceleration side is slowed by fluid drag. Many operators find that slush-covered runways effectively reduce the allowable takeoff weight not because the aircraft cannot get airborne, but because the airplane cannot stop in the available distance if a failure occurs near V1.

Performance Corrections Dispatchers Must Apply

The correction process typically follows this sequence, using AFM data or an FAA-approved performance engineering program:

Identify contamination type and depth. Obtain current METAR, ATIS, SIGMET, PIREP, or NOTAM data specifying runway condition codes (RwyCC), braking action reports, or explicit depth measurements in inches or millimeters. The Global Reporting Format (GRF) now standardizes this information into RwyCC values from 0 (worst braking condition) to 6 (dry).
Select the correct AFM performance table. Most transport-category AFMs provide separate tables for dry, wet, and contaminated conditions. Contaminated tables are further subdivided by fluid type (standing water, slush, compacted snow, ice) and depth. Always use the most conservative applicable table; if reported depth falls between table values, interpolate or use the next higher depth.
Apply drag corrections to accelerate-go distances. Fluid drag slows acceleration, increasing the distance required to reach VR and V2. The corrected takeoff distance accounts for this through longer field-length requirements or reduced allowable weights at a given field length.
Apply braking corrections to accelerate-stop distances. The ASD on contaminated runways can be two to three times the dry-runway value. The corrected ASD must not exceed the accelerate-stop distance available (ASDA), which equals the runway length plus any stopway.
Verify V-speed validity. On contaminated runways, some operators lower V1 to reduce the ASD, accepting a slightly longer airborne segment. However, V1 cannot be reduced below VMCG (minimum control speed on the ground) or the airplane will be uncontrollable with an engine failure before rotation. Dispatchers must confirm that the V-speeds selected by performance software remain within these limits.
Check obstacle clearance. The one-engine-inoperative net climb gradient must meet Part 121 requirements in each takeoff segment: 0.5% positive gradient in the first segment (gear retraction), 3.0% in the second segment (flaps retracted), and 1.2% in the final segment (net gradient above 1,500 feet AGL). Contamination does not directly affect climb performance once airborne, but if contamination forces a weight reduction, the crew and dispatcher must verify the new weight still supports the required gradients.
Apply MEL or configuration deductions if applicable. If an anti-skid system is inoperative, braking effectiveness is further reduced, and AFM or MEL may require additional runway corrections or may prohibit operations on contaminated runways altogether.

Why It Matters: Safety and Legal Exposure

Contaminated-runway accidents and incidents consistently appear in NTSB data as a category where decisions made on the ground — dispatch authorization, captain's acceptance, airport reporting quality — determine outcome. When an aircraft overruns a runway following an RTO in slush, the investigation almost always reveals that the actual stopping distance exceeded what was assumed. The assumptions were wrong either because the contamination was deeper than reported, the braking action was worse than expected, or corrections were not applied at all.

For the dispatcher, the legal stakes are explicit. Under 14 CFR 121.533, the dispatcher and the PIC jointly bear responsibility for the safety of the flight from the time the dispatch release is signed. If a dispatcher authorizes a flight with a takeoff weight that exceeds the contaminated-runway limit and an accident results, the dispatcher's certificate — and potentially criminal liability — is at risk. The standard of care is to apply all required corrections and to refuse to release the flight if the corrections produce a weight below what is needed for the planned payload.

Key Numbers and Rules

Slush density: approximately 50–80% of water; water density used in some AFM tables is 8.35 lb/gallon — slush can be heavier per foot of depth than commonly assumed.
Maximum slush depth for many transport aircraft: 0.5 inch (12.7 mm) per many AFMs; operations above this limit may be prohibited or require special approval.
Runway Condition Codes: 0 = worst braking condition (e.g., ice at or above 0°C), up to 6 = dry; RwyCC 3 or below (compacted snow, slush) triggers the most significant performance corrections.
Friction coefficient (mu) ranges: dry ~0.5, wet ~0.4, compacted snow ~0.2, ice ~0.05.
Climb gradient requirements (Part 121 transport): first segment ≥0.5% (positive), second segment ≥3.0%, final segment ≥1.2% (net).
V1 floor: V1 ≥ VMCG in all cases, regardless of contamination corrections.
Anti-skid inoperative: braking effectiveness can be reduced by 60% or more; many AFMs prohibit takeoff on contaminated runways with anti-skid MEL'd.

Common Test Traps

Confusing wet and contaminated. A wet runway uses specific wet-runway tables; contaminated (slush, snow, ice) uses separate, more conservative contaminated tables. The two are not interchangeable on the exam or in practice.
Ignoring the ASD constraint. Students often focus on getting the aircraft airborne and forget that the accelerate-stop distance may be the limiting factor on a contaminated runway, not the takeoff distance itself.
Assuming V-speeds stay constant. Weight reductions or runway corrections may require recalculation of V1, VR, and V2. The dispatcher cannot simply use the V-speeds from the dry-runway analysis.
Overlooking VMCG as a V1 floor. Lowering V1 to meet ASD requirements is valid only until V1 = VMCG. Below that speed, directional control with an engine failure cannot be maintained; the flight must not be dispatched if this limit is reached before the required ASD is met.
Not accounting for contamination reporting accuracy. Braking action reports from PIREPs represent conditions at the time of the previous landing. Conditions can change rapidly. Dispatchers are expected to build conservatism into the authorization when reports are old or conditions are deteriorating.