The Smart Marty Sky Dispatch
Runway Condition Codes Explained
Runway condition codes run from 6 to 0 and replaced Mu friction readings in 2016. How the RCAM works, what each code means, and the accident behind it.
Runway condition codes (RC) are a standardized scale used to evaluate and communicate the safety of runway surfaces. According to the material from MiGFlug, the RC system runs from 6 down to 0, providing a graded assessment that replaces the older Mu friction readings. This transition to a standardized coding scheme occurred in 2016, establishing a common framework for assessing surface safety and the potential impact on braking performance.
The MiGFlug report explains the mechanism of the RCAM system, detailing how runway condition codes are derived and what each code signifies for surface conditions. The article outlines that RCAM encompasses an interpretation of braking action and related factors, integrating them into a coherent assessment of runway surface safety. The emphasis is on how pilots and ground personnel use these codes to gauge landing and rolling performance under varying surface conditions.
A central theme in the MiGFlug material is the historical shift from Mu friction readings to the current RCAM approach. The piece highlights the rationale behind the change in 2016, noting that the new scheme was implemented to standardize the assessment of runway surfaces and improve communication of braking action and surface safety across different regions and operators.
Within the discussion of RCAM, TALPA and braking action are identified as components of the system used for evaluating runway surface conditions. The material describes these elements as integral to how RCAM codes are applied in practice, linking the code values to practical implications for aircraft braking performance and operational decision-making during takeoff and landing.
The report acknowledges an accident associated with runway condition assessment as a point of historical context behind the development of RCAM. However, the supplied material does not provide any specific details about that event, such as the date, location, aircraft involved, injuries or fatalities, or the outcomes. The narrative uses the accident to illustrate why RCAM and vocabulary around runway condition assessment matter in safety discussions.
Across the supplied material, there is an emphasis on the practical purpose of RCAM: to convey, in a standardized form, the current state of a runway surface to flight crews and ground responders. The codes are described as a tool for assessing safety margins related to braking action, with 6 representing the best conditions and 0 representing the most degraded surface, as part of the standardized scale introduced in 2016.
The materials repeatedly link RCAM to a broader context of runway condition assessment, including how the codes influence operational decisions. While the discussion confirms that RCAM replaced Mu friction readings and that 2016 marked the transition, it does not provide operational data such as specific code values observed on particular runways or the outcomes of incidents tied to RCAM readings.
In sum, the MiGFlug materials present RCAM as a 2016-established, 6-to-0 coding system that superseded Mu friction measurements, with TALPA and braking action as part of the assessment framework. They reference an accident as part of a historical context but do not include concrete details about the event, and the overall focus remains on the purpose, structure, and rationale behind the RCAM-based runway condition assessment.