Runway Condition Code Replaces Friction Values Provided To Pilots Under The Takeoff And Landing Performance Assessment Initiative

On October 1, 2016 airports in the United States began using new reporting terminology to describe contaminated paved runways in both Field Condition Notices to Airmen (FICON NOTAMs) and on Automatic Terminal Information Service (ATIS) messages per the Takeoff and Landing Performance Assessment (TALPA) initiative.

Under TALPA, Mu (friction) values are no longer provided to pilots.  Instead, a three-digit Runway Condition Code (RwyCC) is assigned to paved runways whose surfaces are more than 25% covered by:  water, frost, snow, slush, and/or ice.   Similar to Mu values, a RwyCC is assigned to each third of a contaminated runway (i.e. touchdown, midpoint, and rollout).

The FAA notes that while participating airports are required to report contamination (including a runway condition of greater than 1/8” depth of water) the FAA only encourages airports to report a “wet” runway condition, defined as 1/8” depth or less of water.

If a RwyCC is used in conjunction with voluntarily-provided manufacturer-derived airplane-specific data, pilots will be able to more accurately determine the distance required to stop on a contaminated runway. If airplane-specific data is not available, pilots should consult their AFM and apply distance required adjustments, accordingly.

Nevertheless, TALPA will provide all pilots more descriptive information to reflect runway conditions.  To interpret RwyCC’s, a Runway Condition Assessment Matrix (RCAM) has been developed.

(Source: FAA news release)

FMI: www.faa.gov/about/initiatives/talpa/