Winter operations present unique challenges for pilots. A runway that looks clear from the air might be covered with black ice, while heavy snow can make braking nearly impossible. The FAA's TALPA ARC program standardized how airports report runway conditions, giving pilots objective data to make safe go/no-go decisions.
Understanding the RCAM
The Runway Condition Assessment Matrix (RCAM) is the standardized tool airports use to determine Runway Condition Codes (RwyCC). It correlates contamination type and depth to a numerical braking action code from 0 to 6.
| Code | Braking Action | Surface Conditions |
|---|---|---|
| 6 | Dry | Dry runway surface |
| 5 | Good | Wet, frost, <1/8" dry snow/sand |
| 4 | Good to Medium | Compacted snow at -15°C or colder |
| 3 | Medium | Wet snow, dry snow >1/8", compacted snow |
| 2 | Medium to Poor | Standing water, slush <3mm |
| 1 | Poor | Ice, wet compacted snow |
| 0 | Nil | Wet ice, water over compacted snow, slush >3mm |
Critical: RwyCC 0 (Nil Braking)
A runway condition code of 0 means braking action is NIL—directional control may be impossible. Operations should not be attempted unless your aircraft has performance data specifically addressing nil braking conditions, which most do not.
Reading FICON NOTAMs
Field Condition (FICON) NOTAMs report runway surface conditions in a standardized format. Understanding this format is essential for flight planning in winter weather.
# Example FICON NOTAM
!ORD 01/234 ORD FICON RWY 10L 5/5/4
100 PCT COMPACTED SNOW
OBSERVED AT 1523Z
FICON Format Breakdown
- RWY 10L: The runway designation
- 5/5/4: Condition codes for touchdown/midpoint/rollout zones
- 100 PCT: Percentage of runway affected
- COMPACTED SNOW: Type of contamination
- OBSERVED AT 1523Z: Time of observation
Common Contamination Types
Frozen Contaminants
- ICE - Frozen water
- COMPACTED SNOW - Dense, packed snow
- DRY SNOW - Loose, powder snow
- WET SNOW - Snow with high moisture
- FROST - Thin ice crystals
Liquid Contaminants
- WET - Water layer on surface
- STANDING WATER - Puddles >3mm
- SLUSH - Water-saturated snow
- TREATED - Chemical treatment applied
Depth Reporting
Contamination depth is reported in inches (US) or millimeters (ICAO). Depth significantly affects braking performance and must be considered in landing distance calculations:
# Depth examples
1/4 IN DRY SNOW - Quarter inch of dry snow
2 IN WET SNOW - Two inches of wet snow
3MM STANDING WATER - Three millimeters of water
Using RwyCC for Performance Calculations
The primary purpose of runway condition codes is to enable accurate landing distance calculations. Your aircraft's AFM or performance manual should include contaminated runway landing data indexed to these codes.
Performance Impact Example
A Boeing 737 requiring 5,000 feet on a dry runway (Code 6) may need:
- • Code 5 (Wet): ~5,750 feet (+15%)
- • Code 3 (Medium): ~7,500 feet (+50%)
- • Code 1 (Poor): ~10,000+ feet (+100%)
Three-Zone Consideration
Runways are divided into thirds for condition reporting. The rollout zone (final third) is typically most critical for landing, as this is where maximum braking occurs:
Practical Application
For RWY 27R with codes 5/4/3: Use Code 3 for your landing distance calculation since you need adequate braking throughout, including the rollout zone. The lowest code in your expected stopping zone determines your required runway length.
Operational Considerations
Before Departure
- • Check destination FICON NOTAMs
- • Calculate contaminated runway landing distance
- • Verify runway length is adequate
- • Check alternate airport conditions
- • Review crosswind limits for contaminated runways
During Approach
- • Request updated runway conditions from ATC
- • Listen to pilot braking action reports
- • Be prepared to divert if conditions worsen
- • Brief go-around criteria
- • Review rejected landing procedure
Crosswind Limits on Contaminated Runways
Most aircraft have reduced crosswind limits on contaminated runways. A runway that's acceptable in calm winds may be unusable with a 10-knot crosswind:
| Condition | Typical Max Crosswind |
|---|---|
| Dry (Code 6) | Published max (e.g., 33 kts) |
| Wet (Code 5) | Published max or 25 kts |
| Compacted Snow (Code 3-4) | 10-15 kts |
| Ice (Code 1) | 5-10 kts |
*Always refer to your specific aircraft's AFM for actual limits
Pilot Braking Action Reports
In addition to official FICON reports, ATC may relay pilot braking action reports. These subjective reports use the traditional terminology:
Traditional Terms
- GOOD: Correlates to Code 5
- GOOD TO MEDIUM: Correlates to Code 4
- MEDIUM: Correlates to Code 3
- MEDIUM TO POOR: Correlates to Code 2
- POOR: Correlates to Code 1
- NIL: Correlates to Code 0
Important Notes
- • Reports are subjective
- • Aircraft type matters
- • Conditions can change rapidly
- • Consider aircraft weight differences
Report Your Experience
After landing on a contaminated runway, report your braking action to ATC. This helps following aircraft make informed decisions. Include your aircraft type, as a heavy jet's experience differs significantly from a light single.
Frequently Asked Questions
What is a Runway Condition Code (RwyCC)?
A Runway Condition Code is a number from 0 to 6 that describes the braking effectiveness on a runway surface. Code 6 means dry conditions with maximum braking, while Code 0 indicates nil braking action where directional control may be impossible.
How do I read a FICON NOTAM?
A FICON NOTAM reports runway conditions in a standardized format including runway designation, condition codes for each third (touchdown/midpoint/rollout), contamination type, depth, and coverage percentage.
What is the TALPA ARC?
TALPA ARC standardized runway condition reporting using numerical codes instead of subjective terms. It provides pilots with objective data to calculate actual landing performance on contaminated runways.
How often are runway condition reports updated?
Reports must be updated whenever conditions change significantly. During active precipitation, updates may occur every 15-30 minutes. After conditions stabilize, updates are typically hourly.