Every takeoff and landing you make depends on the assumption that your wheels will grip the pavement as your aircraft performance charts predict. When snow, ice, slush, or standing water changes that equation, the Runway Condition Assessment Matrix (RCAM) is the standardized tool airports use to translate ground observations into numbers pilots and dispatchers can act on. Understanding RCAM is essential for any pilot operating into airports where winter weather or contamination is a factor — and it shows up on FAA knowledge tests under airport operations.
Before RCAM was introduced into U.S. practice, runway condition reporting was fragmented. Different airports used different friction measurement devices and reported results inconsistently, making it nearly impossible for pilots to compare conditions across airports or apply them reliably to aircraft performance data. RCAM, now embedded in FAA and ICAO standards and described in the Aeronautical Information Manual (AIM), replaced those older methods with a single, consistent framework built around Runway Condition Codes (RwyCC).
How RCAM Works
The RCAM links observable runway surface conditions — what an airport inspector actually sees and feels when walking or driving the runway — to a numerical code on a scale of 0 through 6. A code of 6 represents a dry runway with full braking action, while a code of 0 represents the worst possible surface, equivalent to nil braking action. Every number between those extremes maps to a specific contamination type and depth, and to a corresponding expected braking action description.
A runway is divided into thirds — the touchdown zone, the mid-section, and the rollout zone — and each third receives its own RwyCC. This matters because conditions often vary along a runway's length; a plowed but still-slick touchdown zone may differ from a clear mid-section or a snow-covered far end. Pilots receive all three codes in sequence when a NOTAM or ATIS references runway conditions, formatted as a string such as 5/4/3 for a given runway.
The Code Scale in Detail
- 6 — Dry: Normal dry pavement. Full braking action. No performance penalty.
- 5 — Frost or wet: Frost covering the runway, or wet pavement. Braking action described as good.
- 4 — Wet (slippery wet) or dry snow/wet snow: Runway is slippery when wet, or covered with dry snow up to 25 mm, or wet snow up to 3 mm. Braking action good to medium.
- 3 — Compacted snow: Surface is compacted snow, providing reduced but predictable friction. Braking action medium.
- 2 — Wet snow over compacted snow, dry snow over compacted snow, or slush: Slush up to 3 mm, or layered snow combinations. Braking action medium to poor.
- 1 — Ice (not melting): Glare ice or hard, dry ice. Braking action poor.
- 0 — Wet ice, water on compacted snow, slush on ice, or dry/wet snow on ice: The most hazardous combinations. Braking action nil.
The braking action descriptions — good, good to medium, medium, medium to poor, poor, and nil — are qualitative terms that correspond to each code range and give pilots a plain-language handle on what to expect. When braking action reports of medium to poor or worse are in effect, many aircraft operators apply significant landing distance corrections from their performance supplements.
How Reports Reach Pilots
Airport Operations personnel conduct the surface assessment using direct observation and the RCAM lookup process. Their findings are disseminated to pilots through NOTAMs (specifically SNOWTAM or runway condition NOTAMs), through D-ATIS or ATIS broadcasts, and through ATC advisories. The standard reporting format is the RCR (Runway Condition Report), which uses the RCAM codes and also notes the contaminant type and, where relevant, the depth of accumulation.
Pilots should also be aware that ATC may relay pilot braking action reports (PIREPs). These reports use the qualitative terms (good, medium, poor, nil) directly from cockpit observations and serve as a real-time supplement to the official RCAM-based NOTAMs. A pilot who lands and experiences poor braking should proactively report that to the tower — those reports can trigger an airport re-inspection and updated NOTAM, protecting subsequent arrivals.
Why RCAM Matters for Safety and Performance Planning
Aircraft performance charts — specifically landing distance data — are almost universally published for a dry runway. Some manufacturers provide wet-runway corrections, and a growing number of aircraft Airplane Flight Manuals (AFMs) or performance supplements include landing distance factors keyed to specific RwyCC values (often labeled as mu values or braking action conditions). When you consult those charts, the RCAM code is the direct input.
Consider a practical example: a light single-engine trainer has a published dry landing distance of 1,500 feet over a 50-foot obstacle. If the runway reports a RwyCC of 1 (ice, poor braking), the actual stopping distance could be dramatically longer — potentially two to three times the dry distance or more, depending on the aircraft type. The RCAM and corresponding AFM corrections allow the pilot to compute whether the available runway length is adequate before committing to the approach.
Beyond stopping distance, contaminated runways affect directional control. On a surface coded 0 or 1, differential braking for steering becomes nearly useless. Pilots must plan on wider margins, anticipate longer rollout, and brief crosswind limits carefully — many operators apply reduced crosswind maximums on contaminated surfaces because side-force control also degrades.
Takeoff performance is equally affected. Slush and wet snow create drag on the wheels during the takeoff roll (called slush drag or contamination drag), extending the distance needed to accelerate to rotation speed. This can also reduce the aircraft's ability to reject a takeoff if an engine fails near V1 in transport category aircraft. While this primarily affects Part 121 and 135 operations, the principle applies to any aircraft.
Key Numbers and Rules
- RwyCC scale runs from 0 (nil braking) to 6 (dry/full braking). Only a code of 6 is truly free of a contamination-related performance penalty; a code of 5 (wet, frost, etc.) still reflects reduced braking action compared to dry pavement and should be factored into performance planning.
- Runways are assessed in thirds; pilots receive three codes, one for each third (e.g., 4/3/2).
- Codes of 0 or 1 correspond to poor or nil braking action — conditions where some operators prohibit operations entirely or require special crew training.
- RCR NOTAMs have an expiration; airports must re-inspect and update when conditions change. Reports are generally valid for a limited period and should be confirmed via current ATIS or ATC.
- Pilot braking action reports are described using the qualitative terms: good, good to medium, medium, medium to poor, poor, or nil — not numerical codes.
- A NOTAM reporting nil braking action does not legally prohibit a landing under 14 CFR Part 91, but it signals extreme hazard, and operator SOPs or Part 135/121 regulations may prohibit it.
- Slush depth matters: depths exceeding 3 mm of slush on the runway surface are associated with lower RwyCC values and greater performance penalties.
Common Test Traps
- Confusing the direction of the scale: Many students mistakenly think a higher number means worse conditions. Remember — 6 is best (dry), 0 is worst (nil). The FAA will test this directly.
- Assuming one code applies to the whole runway: The RCAM report gives three separate codes, one per third. A question may describe a condition in only one zone and ask you to identify the concern — read carefully.
- Mixing up qualitative and numerical systems: Pilot braking action PIREPs use words (good, medium, poor, nil). RwyCC NOTAMs use numbers (0–6). The FAA may present both in a scenario; don't conflate them.
- Thinking a nil braking action NOTAM is a legal prohibition under Part 91: It is not. Part 91 pilots have authority to make that go/no-go decision, but the hazard is extreme. Know that 121/135 regulations are more restrictive.
- Overlooking takeoff performance impacts: Test questions sometimes focus only on landing. Contaminated runways also affect takeoff roll distance and the ability to stop during an aborted takeoff — both are fair game.
Runway surface condition reporting exists because the FAA and the aviation community recognized that vague, inconsistent friction data was causing accidents. By learning to read and apply RCAM codes correctly, you demonstrate not just exam readiness but the kind of preflight diligence that makes you a competent, conservative pilot every time conditions are less than ideal.