NTSB recommends FAA update Runway Condition Assessment Matrix (RCAM). The recommendations follow NTSB investigations of 11 runway overrun accidents and incidents.

The National Transportation Safety Board has formally recommended that the Federal Aviation Administration update the Runway Condition Assessment Matrix, the standardized framework airports use to evaluate and communicate contaminated runway surface conditions to flight crews. The recommendation stems from NTSB investigations into eleven separate runway overrun accidents and incidents, a pattern significant enough that the Board concluded systemic deficiencies in the current RCAM methodology contribute to continued risk across commercial and business aviation operations. The RCAM, introduced as part of the FAA's Takeoff and Landing Performance Assessment initiative and implemented industry-wide around 2016, replaced the older friction-based Mu reporting system with a 0-to-6 Runway Condition Code scale intended to give crews and dispatchers a more standardized basis for landing performance calculations.

The core concern driving the NTSB's recommendations is the reliability of the correlation between reported surface descriptions and actual aircraft braking performance. Airport personnel conduct RCAM assessments visually and by vehicle, then assign condition codes that feed directly into the landing distance tables and performance charts used by flight crews. When those assessments are inaccurate — whether due to surface changes after reporting, subjective interpretation of conditions like compacted snow, wet ice, or mixed contamination, or delays between assessment and arrival — the landing performance data available to the crew overstates available stopping capability. For Part 121 carriers and Part 135 operators with regulatory landing performance requirements, an inflated RwyCC effectively masks an unsafe situation behind a compliant-looking number, narrowing or eliminating the margin that performance standards are designed to protect.

For professional pilots, the practical implication is that RCAM-based landing performance data cannot always be treated as a precise engineering guarantee. Experienced crews operating in winter conditions have long understood that reported braking action and actual deceleration can diverge substantially, and that factors like runway surface temperature, the presence of frost under snow, or rapidly changing precipitation can outpace even well-intentioned airport reporting. The NTSB's finding across eleven investigations reinforces that this gap is not merely anecdotal — it is a recurring systemic contributor to overrun events. Until the FAA acts on the recommendations, operators should apply conservative margins when RwyCC codes fall in the mid-range (3-4), treat crew pireps and real-time observations as higher-fidelity data than ground-based assessments when discrepancies exist, and revisit their go-around criteria for contaminated conditions.

The broader significance lies in the accumulation of post-TALPA evidence. The RCAM system was itself a response to earlier NTSB findings, most notably following the 2005 Southwest Airlines overrun at Chicago Midway that killed a child on the ground. The fact that eleven more overrun investigations have identified continued RCAM-related deficiencies in the decade since implementation signals that the 2016 reform, while an improvement over Mu reporting, did not fully solve the underlying data quality problem. Aviation regulators and operators worldwide have adopted RCAM-compatible reporting frameworks, meaning any FAA update to the matrix would likely cascade through ICAO-aligned procedures, airline operations specifications, and manufacturer landing performance documentation globally. Business aviation operators flying into smaller airports with less frequent surface assessments face compounding risk, as reporting intervals at non-towered or low-traffic fields can significantly lag behind changing conditions.

The NTSB's action reflects a continuing regulatory focus on what the safety community calls the runway safety triad — accurate information, appropriate crew decision-making, and adequate runway distance. Runway overruns remain one of the most consequential accident categories in commercial and business aviation, and technology solutions such as onboard performance monitoring systems and real-time ATIS/datalink condition updates are increasingly cited as complements to ground-based assessment. Whether the FAA opts to revise the assessment criteria, shorten mandatory reassessment intervals, incorporate sensor-based friction measurement requirements, or mandate tighter performance margins for specific condition codes, the NTSB's eleven-investigation foundation gives the recommendations substantial weight. Operators and flight departments should monitor the FAA's response closely, as any regulatory action will directly affect landing performance methodology, operations specifications, and crew training requirements across all certificate categories.