Runway state group in a METAR: deposit, extent, depth and friction

Tafrob editorial team · Updated · 8 min read

Short answer

The runway state group is an optional METAR group built from a runway designator and four coded values: deposit type, extent of contamination, depth of deposit and friction or braking action. SNOCLO replaces it when the aerodrome is closed by snow, and CLRD// says contamination has ceased. The Global Reporting Format has since moved this information to the runway condition report.

Key points

  • The group has the form RRRRERCReReRBRBR, added to the ICAO METAR code subject to regional air navigation agreement, and the airport authority supplies the data.
  • Four code tables give the meaning: deposit (0919), extent (0519), depth (1079) and friction or braking action (0366).
  • SNOCLO replaces the whole group when the aerodrome is closed due to extreme deposit of snow, and CLRD// replaces the last six characters when contamination has ceased.
  • The Global Reporting Format became mandatory on 4 November 2021 and moves runway reporting to the runway condition report, sent by SNOWTAM, ATIS or voice.
  • CAP 746 records the removal of the runway state requirement from UK METARs as a result of the Global Reporting Format.
Snow-covered runway at Schiphol airport
Photo: ♪Karthik♫ ♪Nadar♫, CC BY-SA 3.0, via Wikimedia Commons

What is the runway state group?

The runway state group was an optional element of the ICAO METAR that described what was lying on a runway: nothing, water, snow, ice, and so on. It sat at the very end of the body of the report, after the supplementary groups, and it packed everything into a fixed string of coded characters. Many readers meet it as a block of digits they cannot decode, or as the odd words SNOCLO and CLRD//.

Today it is largely a historical group in the documents cited here. The runway state information that pilots use now travels in the runway condition report of the Global Reporting Format. This page explains how the old group was built, so you can read archived reports, and how the new system relates to it. For the order of the other groups, see how to read a METAR.

Where the group comes from

The WMO text cited here is an amendment to the METAR and SPECI code forms (Annex 3 to Recommendation 3 of CBS-XII). It adds the runway state group after the supplementary wind shear and sea-surface groups. The code form reads:

WS ALL RWY (WTsTs/SS) (RRRRERCReReRBRBR)

The brackets mean the groups are optional. The amendment states that, subject to regional air navigation agreement, information on the state of the runway provided by the appropriate airport authority shall be included. Two points follow.

  • The data is not measured by the weather station. The airport authority provides it, which is why the group has always been tied to local arrangements.
  • The runway designator RRRR is reported in accordance with the relevant ICAO regional Air Navigation Plan, so its exact form is a regional matter. For that reason, no runway designator format is shown here.

The group follows the wind shear group, and the amendment also adds sea-surface temperature and state of the sea in the same position range, so a full tail of a report could hold recent weather, wind shear, sea state and runway state, in that order.

The four code tables

After the runway designator, the group carries four values, each looked up in a WMO code table. The amendment names the tables 0919 for deposits, 0519 for extent, 1079 for depth and 0366 for friction or braking action.

Deposit (ER, table 0919)

Code Runway deposit
0 Clear and dry
1 Damp
2 Wet and water patches
3 Rime and frost covered (depth normally less than 1 mm)
4 Dry snow
5 Wet snow
6 Slush
7 Ice
8 Compacted or rolled snow
9 Frozen ruts or ridges
/ Type of deposit not reported, for example because runway clearance is in progress

Extent of contamination (CR, table 0519)

Code Extent
1 Less than 10 per cent of the runway contaminated
2 11 per cent to 25 per cent
5 26 per cent to 50 per cent
9 51 per cent to 100 per cent
/ Not reported, for example because runway clearance is in progress

Codes 3, 4, 6, 7 and 8 are marked reserved in the table.

Depth of deposit (eReR, table 1079)

The depth is two characters. The table runs from 00 for less than 1 mm, through 01 for 1 mm and 02 for 2 mm, up to 89 for 89 mm and 90 for 90 mm. After that the codes jump: 92 is 10 cm, 93 is 15 cm, 94 is 20 cm, 95 is 25 cm, 96 is 30 cm, 97 is 35 cm and 98 is 40 cm or more. Code 91 is reserved. Code 99 means the runway or runways are non-operational due to snow, slush, ice, large drifts or runway clearance, but the depth is not reported. Two slashes mean the depth is operationally not significant or not measurable.

Friction coefficient or braking action (BRBR, table 0366)

Values 00 to 90 are a friction coefficient from 0.00 to 0.90. Then the table switches to words:

Code Meaning
91 Braking action poor
92 Braking action medium/poor
93 Braking action medium
94 Braking action medium/good
95 Braking action good
96 to 98 Reserved
99 Unreliable
// Braking conditions not reported and/or runway not operational

How to decode the values

The tables are enough to decode the six characters that follow the runway designator. Here is a constructed illustration, not a report from a source. Suppose the six characters were 4 5 12 93, read as ER, CR, eReR and BRBR:

  • ER 4 is dry snow.
  • CR 5 is 26 to 50 per cent of the runway covered.
  • eReR 12 is a depth of 12 mm, since the table is a direct mm value in this range.
  • BRBR 93 is medium braking action.

In a real report there are no spaces between these characters, and the runway designator comes first. Because the designator format depends on the regional plan, always check the local rules before decoding an archived report.

SNOCLO and CLRD//

The amendment gives two special forms.

SNOCLO. The runway state group is replaced by the abbreviation SNOCLO when the aerodrome is closed due to extreme deposit of snow. It stands in place of the whole group, so there is no runway designator and no digit string.

CLRD//. If contaminations on a single runway or on all runways at an aerodrome have ceased to exist, this is reported by replacing the last six characters of the group with CLRD//. The runway designator remains, which tells the reader which runway has cleared.

These two forms are easy to misread. SNOCLO is about the aerodrome, not about snow depth. CLRD// is the end of a contamination episode and tells you nothing about how the runway behaved while it was contaminated.

The Global Reporting Format replaces it

The ACI guidance on the Global Reporting Format (GRF) says the format became mandatory on 4 November 2021 under ICAO requirements. It adds that states applying EASA regulation, and Canada, transitioned on 12 August 2021. The GRF applies to all airports regardless of their location, local weather and operating conditions.

The method differs from the old group in several ways.

  • The aerodrome operator assesses the runway by visual observation, noting the percentage of each runway third covered by contaminant, the depth, and the surface condition and type of contaminant.
  • The operator uses the Runway Condition Assessment Matrix to determine a Runway Condition Code, abbreviated RWYCC, and reports it in a Runway Condition Report, abbreviated RCR.
  • The RCR goes to air traffic control, which passes it to crews through a SNOWTAM, through the ATIS, or by voice on the radio frequency.
  • The FAQ says the process of reporting starts when the runway is wet or has a contaminant, and a report is generated when there is 10 per cent or more coverage of a contaminant in any third of the runway.
  • A new RCR is generated whenever there is a significant change. A SNOWTAM is valid for eight hours, according to the same FAQ.
  • If there is no contaminant on the runway, there is no need to generate a report.

The FAQ also covers unlisted contaminants such as hail, mud and sand. They have no associated RWYCC, but a runway assessment must still be conducted and the presence of the contaminant is mentioned in the situational awareness section of the RCR. For the report itself, see the SNOWTAM and Global Reporting Format page, and for the broadcast channel see the ATIS page.

What happened to the METAR group?

CAP 746 is the cited document that states the change plainly. Its revision history for Issue 6, August 2023, lists the removal of the requirement to provide runway state details in METARs as a result of the implementation of the Global Reporting Format. The same history shows that earlier editions had guidance on the runway state message format and, in Issue 3 of 2014, clarification of two runway state codes. Those codes are not defined in the cited text, so they are not decoded here.

What the sources do not confirm:

  • Whether other states still include the group in their METARs.
  • Whether ICAO or EASA texts formally remove the group from the METAR code form. The cited sources give the UK statement and the GRF dates, nothing more.

In the United States, neither FMH-1 nor FAA JO 7900.5E mentions the runway state group or SNOCLO. FMH-1 does allow, in the plain-language remarks, other significant information such as runway conditions, which agencies may add for their operations. That is a free-text remark and not the coded group. The METAR remarks page covers the section, and the US versus ICAO page covers the wider gap between the two systems.

Common mistakes

  • Reading the digit string as a weather element. It describes the runway surface and comes from the airport authority.
  • Treating SNOCLO as a snow depth. It means the aerodrome is closed due to extreme deposit of snow.
  • Assuming CLRD// means the whole aerodrome is clear. It names the runway whose contamination has ceased, or all runways if so reported.
  • Expecting the group in modern reports. Runway condition now travels in the RCR, the SNOWTAM and the ATIS.
  • Mixing up the friction coefficient values 00 to 90 with the braking action words 91 to 95.

This page is educational and is not a source for operational runway conditions. For where the codes come from, see where METAR and TAF rules come from.

Training and reference only. For flight planning, always use official briefing sources (your national weather service, AIS or approved provider).

Frequently asked questions

What is the runway state group in a METAR?

It is an optional group that reported the state of a runway after the sea-surface group. The WMO amendment text writes it RRRRERCReReRBRBR, with a runway designator followed by deposit, extent, depth and friction values. It applies only subject to regional air navigation agreement.

What does SNOCLO mean in a METAR?

SNOCLO replaces the runway state group when the aerodrome is closed due to extreme deposit of snow. The WMO amendment text uses exactly this wording. It is not a weather phenomenon and it does not describe the snow on a particular runway, only that the aerodrome is closed.

What does CLRD// mean at the end of a runway state group?

CLRD// replaces the last six characters of the group when contamination on a single runway, or on all runways, has ceased to exist. The runway designator stays in place. It tells the reader that the earlier deposit values no longer apply.

Do METARs still carry the runway state group?

Not in the United Kingdom. CAP 746 records the removal of the requirement to provide runway state details in METARs because of the Global Reporting Format. The group does not appear in the US handbooks FMH-1 and JO 7900.5E, and the practice of other states is not covered by the sources cited here.

Sources

  1. World Meteorological Organization. Annex 3 to Recommendation 3 (CBS-XII), Modifications to Code Forms FM 15-X Ext. METAR and FM 16-X Ext. SPECI
  2. Airports Council International World (2021). Global Reporting Format, Frequently Asked Questions, Guidance for Airport Operators
  3. UK Civil Aviation Authority (2023). CAP 746, Requirements for Meteorological Observations at Aerodromes
  4. Office of the Federal Coordinator for Meteorology (2019). Federal Meteorological Handbook No. 1 (FCM-H1-2019)