Landing a transport-category aircraft on a contaminated runway demands precise, consistent information about how that surface will affect stopping distance. For decades, pilots and dispatchers relied on subjective braking action reports — terms like "good," "medium," or "poor" — that meant different things to different crews and could not be reliably mapped to performance charts. The FAA's Takeoff and Landing Performance Assessment (TALPA) initiative, formalized through AC 150/5200-30 for airports and operationalized for aircraft manufacturers through AC 25-32, replaced that imprecise language with a structured, numerical system: the Runway Condition Assessment Matrix (RCAM) and the associated Runway Condition Codes (RwyCCs).
This article explains the RCAM framework from the ground up, details how braking action reports are generated and published, and describes exactly how flight crews and dispatchers are expected to use this information for departure and arrival performance planning under 14 CFR Parts 91, 121, and 135.
The Problem TALPA Solved
Before TALPA, a first officer might report "fair" braking action after landing, and the next crew might interpret that word very differently when planning their own stopping distance. There was no standardized mathematical link between the reported condition and the aircraft's actual deceleration data. Accident investigations — including runway overruns in winter operations — repeatedly identified this gap as a contributing factor. TALPA created a closed loop: airport personnel assess the surface, assign a numerical code, that code drives the pilot's performance lookup, and pilots cross-check by reporting actual deceleration after landing.
Runway Condition Codes (RwyCC): The Six-Point Scale
The RCAM defines six Runway Condition Codes, numbered 0 through 6, where 6 represents a fully dry runway, 5 represents a good/nearly ideal contaminated-surface braking condition, and 0 represents a surface with essentially no meaningful braking. Each code corresponds to a described surface condition and, critically, to a defined range of aircraft deceleration performance. The codes are:
- RwyCC 6 — Dry: A fully dry runway. No contamination. Maximum braking performance expected.
- RwyCC 5 — Good: Corresponds to a wet runway or very light contamination. Braking is slightly diminished but still excellent. Deceleration is near the dry performance level.
- RwyCC 4 — Good to Medium: Compacted snow, slush, or wet snow at very low depths. A noticeable but moderate reduction in braking.
- RwyCC 3 — Medium: Deeper slush, dry snow, or wet compact snow. Pilots should expect a meaningful increase in landing distance compared to dry values.
- RwyCC 2 — Medium to Poor: Ice under snow, wet ice, or a mix of conditions where braking is substantially degraded. Landing distance increases are significant.
- RwyCC 1 — Poor: Wet ice or treated ice where friction is very low. Stopping distances can be dramatically longer than the dry-runway chart value.
- RwyCC 0 — Nil: No meaningful braking available. A condition of RwyCC 0 can require prohibiting operations entirely; it essentially means the aircraft cannot reliably stop on the available runway.
Each aircraft manufacturer, using the methodology prescribed in AC 25-32, must provide performance data keyed to these RwyCC values. The result is a flight-manual table or chart — often called a Runway Condition Assessment table in the AFM — that tells the crew exactly how much landing (or stopping) distance is required for each code.
The RCAM Table: How Airport Personnel Assess the Surface
The RCAM is a look-up matrix used by qualified airport personnel — typically airfield operations staff or ARFF — to translate a physical surface observation into a numerical RwyCC. The matrix considers two primary inputs: contaminant type (dry snow, wet snow, slush, standing water, ice, frost, etc.) and contaminant depth or coverage. By cross-referencing type and depth, the assessor arrives at the appropriate RwyCC for each third of the runway. Crucially, the RCAM assessment is done in thirds — touchdown zone, mid-field, and rollout end — because contamination is rarely uniform across the full runway length.
The lowest (worst) code of the three thirds generally governs the most conservative planning, although AC 25-32 and airline operations specifications define exactly how crews must handle split-condition runways. When the three thirds differ, the NOTAM will report all three codes in order (e.g., "5/3/3"), and the crew uses whichever AFM methodology applies — typically the most limiting section — or a weighted average method if the manufacturer provides one.
Braking Action Reports from Pilots
After landing, flight crews are expected to provide an actual braking action (BA) report to ATC. Under TALPA, the verbal terminology was also standardized. Crews now report using the same six qualitative terms, each of which maps back to a numerical RwyCC range:
- Good corresponds to RwyCC 5
- Good to Medium corresponds to RwyCC 4
- Medium corresponds to RwyCC 3
- Medium to Poor corresponds to RwyCC 2
- Poor corresponds to RwyCC 1
- Nil corresponds to RwyCC 0
The old terms "fair" and "medium-good" were eliminated precisely because they did not map cleanly to numerical codes. ATC broadcasts pilot braking action reports as received, and these are included in ATIS when available. Pilots must understand that a braking action report reflects the conditions at the time the reporting aircraft landed — conditions can change rapidly with precipitation, temperature shifts, or runway treatment.
NOTAMs and the RCR Format
Airport operators issue Runway Condition Reports (RCRs) in NOTAM format using a standardized coding structure. The SNOWTAM or domestic NOTAM will include the three-digit RwyCC string (one digit per third of the runway) along with the contaminant type, depth, and coverage percentage for each third. For example, a NOTAM might read: "RWY 28L CONDITION: 4/3/3 — WET SN 1/2 IN TD ZONE, COMPACT SN MID, COMPACT SN ROLLOUT." The crew uses the worst applicable code — or follows the manufacturer's specific split-condition methodology — to determine landing distance required.
It is important to note that these NOTAMs have a limited validity period. Airports are required to reassess and update the NOTAM when conditions change, and the RCR expires after a set interval (typically not more than 24 hours, or sooner if precipitation or other factors require it). Pilots must verify they are using a current RCR before committing to performance planning.
How AC 25-32 Connects to Transport-Category Performance
AC 25-32, titled Flight Standardization Board Procedures and AFM Approval of TALPA/GRF Landing Performance Data, provides the FAA's policy for how aircraft manufacturers demonstrate and document landing performance on contaminated runways. Under the AC, manufacturers must either conduct actual contaminated-runway flight tests or use an FAA-accepted analytical method to derive deceleration data for each RwyCC level. The resulting data is incorporated into the Airplane Flight Manual (AFM), making it legally operative performance data — not advisory-only information.
This is a critical point for ATP candidates: the landing distance from the AFM contaminated-runway tables is required performance data, not a conservative rule of thumb. Dispatchers and flight crews must use these tables when planning arrivals on contaminated runways and must verify that the required landing distance does not exceed the runway's available landing distance (with applicable regulatory factors applied). Under 14 CFR Part 121, for example, dispatch rules require that the expected landing distance at the destination not exceed 60% of the available runway (i.e., a 1.67 landing distance factor on a dry runway), and similar principles extend to contaminated-surface operations using the AFM data.
Operational Considerations and Edge Cases
Several practical scenarios test a crew's mastery of TALPA concepts:
- Rapidly changing conditions: If a storm is actively depositing snow, the RwyCC reported in the NOTAM may be stale by the time the aircraft lands. Crews should obtain the most recent pilot report and, if in doubt, add margin or divert.
- Split runway codes: A 5/3/1 code means the touchdown zone is good, mid-field is medium, and the rollout end is poor. If the aircraft has not stopped by the worst-condition section, that worst code may govern. Many AFMs have specific guidance for this scenario.
- Crosswind and contamination interaction: Contaminated runways reduce directional control in addition to braking. Crosswind limits on contaminated surfaces may be lower than those published for dry conditions — some manufacturers publish separate crosswind limits by RwyCC.
- Autobrake selection: The AFM will specify which autobrake setting, combined with spoiler and thrust reverser use, was used to derive the chart distances. Crews must use at least the specified configuration to achieve the charted performance.
- Nil braking action: A RwyCC of 0 or a pilot report of Nil braking action triggers a NOTAM advisory that should cause crews to seriously reconsider the operation. Many airline operations specifications require crew notification and possibly operational control approval before landing on a runway with Nil braking action reported.
Key Numbers and Rules
- RwyCC scale: 0 (Nil) to 6 (Dry), with 5 representing Good on a contaminated but reported surface.
- Runway assessed in three equal thirds; all three codes published in order (TD zone / mid / rollout).
- TALPA pilot reports use six standardized terms replacing the old good/fair/poor language.
- AFM contaminated-runway data under AC 25-32 is required, regulatory performance data.
- Part 121 dispatch requires landing distance not exceed 60% of available runway (dry), with contaminated adjustments from AFM tables.
- RCRs in NOTAMs have a limited validity; always verify currency before use.
Common Test Traps
- Confusing old and new terminology: "Fair" braking action no longer exists in the TALPA system. Any question referencing "fair" is testing whether you know it has been replaced. The six TALPA terms are Good, Good to Medium, Medium, Medium to Poor, Poor, and Nil.
- Treating AFM contaminated-runway data as advisory: Under AC 25-32, this data is AFM-approved and legally required — not a conservative suggestion. Examiners may frame a question as if it's optional.
- Assuming the lowest RwyCC always governs uniformly: The correct approach depends on your specific AFM methodology for split-code runways. Do not simply apply the worst code to the entire runway without checking the AFM procedure.
- Ignoring NOTAM expiration: A braking action NOTAM that was issued hours ago during a snowstorm may not reflect current conditions. Currency of the RCR matters operationally and is tested conceptually.
- Forgetting thrust reversers and autobrakes in the distance calculation: TALPA tables assume a specific configuration. Using less than the assumed stopping devices means the published distance is NOT achievable — a common practical and exam oversight.