BizJet Brief
Thursday, November 19, 2026
BizJet Brief

Thursday, November 19, 2026

Education

Reading the Runway in Winter: How Business Jet Crews Should Use Runway Condition Codes and FICON NOTAMs

What the FAA's runway condition codes in FICON NOTAMs mean, how to read 5/3/3, and how AC 91-79B says to turn a code into a safe landing distance.

Reading the Runway in Winter: How Business Jet Crews Should Use Runway Condition Codes and FICON NOTAMs
File photo: Cory W. Watts / Wikimedia Commons (Flickr), CC BY-SA 2.0 — a Bombardier Challenger 300 taxis on a snow-covered ramp at La Crosse Regional Airport, Wis., in February 2007

Winter brings FICON NOTAMs full of numbers like "5/3/3." Those three digits describe how slippery each third of the runway is. Misread them, and a routine winter landing can turn into an overrun.

Here is a plain-language guide to the FAA's system and how to turn those codes into a landing decision. It pairs well with our de-icing refresher, "Holdover Time, Explained."

Where the system came from

The FAA calls it TALPA, short for Takeoff and Landing Performance Assessment. According to the agency's Safety Alert for Operators (SAFO) 16009, the FAA and industry built it after a Boeing 737 overran the runway at Chicago Midway in December 2005.

It took effect Oct. 1, 2016. The FAA's TALPA page says federally obligated airports and many others now use these procedures and publish the results in Field Condition, or FICON, NOTAMs.

The codes, from 6 to 0

At its center is the Runway Condition Assessment Matrix, or RCAM. The airport assesses the type and depth of contamination and assigns a Runway Condition Code, or RwyCC. Higher is better. Here is the pilot's version, as published in SAFO 16009 and FAA Advisory Circular 91-79B:

  • 6: Dry.
  • 5 (braking "good"): Frost; a wet runway, including damp or up to 1/8 inch of water; or up to 1/8 inch of slush, dry snow or wet snow.
  • 4 (good to medium): Compacted snow when the outside air temperature is -15°C or colder.
  • 3 (medium): A runway reported "slippery when wet"; dry or wet snow over compacted snow; more than 1/8 inch of dry or wet snow; or compacted snow warmer than -15°C.
  • 2 (medium to poor): More than 1/8 inch of water or slush.
  • 1 (poor): Ice.
  • 0 (nil): Wet ice, slush over ice, water over compacted snow, or snow over ice.

You will not see a 0 in a FICON NOTAM. The Aeronautical Information Manual says a code of 0 marks a "nil" braking report and is prohibited from FICON NOTAMs. Under SAFO 16009, a federally obligated airport facing nil conditions must close that surface until the condition is gone.

Reading the three numbers

A FICON NOTAM gives one code for each third of the runway: touchdown, midpoint and rollout. A report of 5/3/3 means the touchdown zone is better than the rest of the runway.

SAFO 16009 says the codes and contaminant coverage, given as a percentage for each third, are reported starting from the runway end the airport assessed. That is usually the end mainly in use. So check which direction the report describes before you apply it to your landing runway.

Two more points from the SAFO: codes appear only when more than 25% of the runway is contaminated; below that, the FAA says performance impacts are less likely. And the old friction readings, known as Mu, are no longer published in the NOTAM system.

Airport operators may upgrade or downgrade a code based on their overall assessment, so it can differ from the contaminant listed, the SAFO notes. Airplane operators cannot adjust it.

Braking action reports still matter

Pilots describe braking with six terms: good, good to medium, medium, medium to poor, poor and nil. When towers receive reports of medium, poor or nil, or when weather could make braking worse quickly, ATIS will say "braking action advisories are in effect," according to the AIM. Controllers then give each arriving and departing aircraft the latest report for the runway in use.

AC 91-79B says a recent report from an aircraft similar to yours is more likely to be useful.

Turning a code into a landing distance

A code is not a landing distance. The FAA's answer is a time of arrival assessment, done with the weather and field conditions in hand, usually before top of descent, according to AC 91-79B.

The AC says crews should use the most adverse reliable braking report or the worst expected conditions. Then add a safety margin of at least 15%. Except in an emergency, the FAA says crews should not try to land on a runway that does not meet that standard.

Use your manufacturer's or performance provider's advisory data if you have it. If you do not, AC 91-79B offers landing distance factors that already include the 15% margin. You multiply the unfactored, dry landing distance from the airplane flight manual by the factor for the reported code.

For a turbojet with thrust reversers, the factors run from 1.67 for a dry runway to 2.5 for code 3 and 3.4 for code 1. Without reversers, code 1 climbs to 5.1. As a simple illustration, a jet with a 3,000-foot unfactored landing distance would need about 7,500 feet on a code 3 runway using the with-reverser factor.

The AC notes the FAA has no plans to give Part 23 manufacturers guidance like AC 25-32, the standard behind that advisory data, so check what your manufacturer provides.

Rain counts too

AC 91-79B also warns that wet-runway stopping in moderate or heavy rain has been worse than predicted in several overruns, even on grooved runways. If you expect more than 1/8 inch of water, the AC recommends using the code 2 factor for your assessment.

A checklist for this winter

  • Note the time. AC 91-79B says several overruns happened when crews relied on a runway report that weather had already made obsolete. Compare the report time with what has fallen since.
  • Plan your bottom line early. Decide before descent how much worse conditions can get before you divert, as the AC recommends.
  • Use the worst credible number. Base the assessment on the lowest reliable code or braking report for the part of the runway you will use.
  • Give a report. Your braking report after landing helps the next crew.

The National Business Aviation Association offers a free TALPA video series and pilot quick reference card, built by its Access Committee.

Sources

  1. FAA: Takeoff and Landing Performance Assessment (TALPA)
  2. FAA SAFO 16009: Runway Assessment and Condition Reporting, Effective October 1, 2016
  3. FAA Advisory Circular 91-79B: Aircraft Landing Performance and Runway Excursion Mitigation (Aug. 28, 2023)
  4. FAA Aeronautical Information Manual, Chapter 4, Section 3 (4-3-8 Braking Action Reports and Advisories; 4-3-9 Runway Condition Reports)
  5. NBAA: Takeoff and Landing Performance Assessment (TALPA) resources
  6. NBAA: Pilot's Runway Condition Assessment Matrix quick reference card (Rev. 2, March 2019)