Introduction to Runway Condition Assessment Matrix (RCAM) and Field Condition Reporting Presented to: By: Date: Advanced ASOS Steven Oetzell October 18, 2016
Takeoff And Landing Performance Assessment (TALPA) Background: Catalyst was a fatal excursion at Midway Airport - Dec 2005. Need to develop adequate guidance for addressing operation on contaminated runways with dissemination of real time runway condition information in a less subjective format. Runway Condition Assessment Matrix (RCAM) is the result RCAM ties type of contaminants to specific aircraft manufacturers braking performance data. Standardizes method for determining and reporting surface conditions and harmonizes with ICAO standards, Annex 14.
FAA Advisory Circular 150/5200-30D, Airport Field Condition Assessments and Winter Operations Safety Effective Date: July 29, 2016 Replaces: AC 150/5200-30C, Airport Winter Safety and Operations Purpose:Provides guidance to assist airport operators in revising a snow and ice control plan (due September 1, 2016) and assessing and reporting airport conditions through the utilization of the Runway Condition Assessment Matrix (RCAM) (beginning October 1, 2016). 3
Principal Changes Introduces RCAM and procedures for its use and application. Defines vehicle and pilot reported braking action and updates terminology: Good, Good-to-Medium, Medium (previously known as Fair), Medium-to-Poor, Poor, and Nil. Adds conditions not monitored information for airport operators to use when the airport is not monitored due to operations hours or staffing. Adds new acronym RwyCC for Runway Condition Code. Removes the capability to report friction (Mu) values (replaced by RwyCCs). Introduces percentage based contaminant reporting by runway thirds. A runway is considered contaminated when more than 25% of the overall runway length and width is covered by frost, ice, snow, slush or water. Adds definitions of contaminants. 4
Guidance Information: Snow & Ice Control Plans (SICP) SICP revisions can follow change template released by Office of Airports with AC150/5200-30D Current way airport operators accomplish assessment has not changed. Decelerometer and CFME data should only be used under certain contaminate conditions (see 5.1.4 of AC 150/5200-30D) SICP surface snow clearing procedures have not changed Reporting DOES change Reporting RwyCCs replaces reporting Mu numbers Mu still useable for actions associated with trends on taxiway(s), aprons, holding bays, etc. Mu remains a tool in the tool box for upgrading/downgrading RwyCCs DO NOT attempt to correlate Mu readings with Good/Medium, Poor or Nil terms. Primary changes are on reporting contaminant information through the Federal NOTAM System - Via NOTAM Manager, ENII, and Flight Service Stations
Reporting Airport Condition Information Runway Condition Codes are disseminated via one or more of the following methods: Federal NOTAM System (FNS), preferably through NOTAM Manager (direct-entry system) or ENII (direct-entry but lacks some inputs that NOTAM Manager has). Airport Traffic Control Facility (corresponding Tower, Center, Tracon, etc.); Flight Service Station (FSS) (as applicable); and Directly from airport operator via Common Traffic Advisory Frequency (as applicable).
Runway Condition Assessment Matrix 7
Example NOTAMs Old Format:!MCI MCI RWY 9/27 PATCHY THIN SLUSH New format:!mci MCI RWY 9 20% 1/8 INCH SLUSH Translation: MCI Runway 9 is 20% covered with 1/8 inch of slush Old Format:!MKC MKC RWY 1/19 ½ INCH WET SNOW New format:!mkc MKC RWY 19 5/5/3 70% 1/8 INCH WET SNOW, 70% 1/8 INCH WET SNOW, 90% ½ INCH WET SNOW Translation: MKC Runway 19 runway condition code of 5/5/3, Touchdown and Midpoint runway thirds are 70% covered with 1/8 inch of wet snow; the Rollout third is 90% covered with ½ inch wet snow. 8
Slippery When Wet 9
Downgrading Downgrading a RwyCC allowable by using Mu readings from friction measuring equipment Use criteria in grey columns of RCAM Upgrading Upgrading a RwyCC allowable but no higher than 3 for each 1/3 of the runway if the Mu value for that 1/3 is 40 or greater. This ability to raise the reported RwyCC to a code 1, 2, or 3 can only be applied to those runway conditions listed under codes 0 and 1 in the matrix. Do not upgrade on Mu readings alone. Use all other observations (vehicle deceleration/control and pilot BA reports) and judgment to support upgrade in RwyCC.. Airport must continuously monitor an upgraded RwyCC to ensure that it has not deteriorated below the assigned code. 10
Conditions Not Monitored NOTAMS When it is determined that no surface condition reports will be taken for longer then a 24-hour period, issue a single NOTAM (Keyword AD) for the entire time-period. Use the phrase SFC CONDITIONS NOT REPORTED, as this differs from Conditions Not Monitored. 11
Misc. A RwyCC of 0 denotes minimal or non-existent braking deceleration, which the FAA has determined to be an unsafe condition. The NOTAM system does not accept 0 for RwyCC and, if attempted, prompts the airport operator to close the surface and perform mitigating actions until the unsafe condition no longer exists. RwyCCs will not be generated if less than 25% of runway is not contaminated Ash, oil, sand, and rubber do not generate a RwyCC. A measured depth of mud must be reported. 12
Related Guidance CertAlert No. 16-06 Issued September 30, 2016 Applicable to all Title 14 CFR Part 139 Airport Operators Guidance Change: The FAA will change Advisory Circular 150/5200-30D, Airport Field Condition Assessments and Winter Operations Safety, to remove the current requirement to report runway wet conditions (1/8th inch or less of water) when it is the only contaminant present. Instead, because of the impact on performance of some aircraft, the FAA will highly encourage airports to report wet conditions (1/8th inch or less of water) when it is the only condition present on the runway. AC 150/5200-28E, Notices to Airmen (NOTAMS) for Airport Operators 13
Questions? 14