How to read a METAR, one group at a time

Tafrob editorial team · Updated · 6 min read

Short answer

A METAR is read left to right in a fixed order: report type, station, day and UTC time, AUTO or COR, wind, visibility, runway visual range, present weather, cloud, temperature and dew point, pressure, then trend or remarks. ICAO reports use meters and hectopascals; US reports use statute miles, inches of mercury and a remarks section.

Key points

  • The order of groups is fixed, so a missing group is simply skipped rather than replaced by a placeholder, except in automated reports that use slashes.
  • Times are always UTC, written as day of month plus hours and minutes followed by Z.
  • ICAO reports give visibility in meters and pressure as Q in hectopascals; US reports use SM and A in inches of mercury.
  • US METARs end with an RMK section that carries station type, sea level pressure and precise temperatures.
  • A METAR describes observed conditions at one point in time and is not a forecast.
Automated Surface Observing System sensors on a grass field at Trenton-Mercer Airport in New Jersey
Photo: Famartin, CC BY-SA 4.0, via Wikimedia Commons

The order of a METAR never changes

A METAR is a coded surface observation whose groups always appear in the same sequence, so reading one is mostly a matter of knowing what comes next. The FAA Aeronautical Information Manual (paragraph 7-1-29) lists the ICAO order, and the Federal Meteorological Handbook (FMH-1) lists the same skeleton for the United States. If an element is not observed or not required, its group is left out and the next one follows.

Position Group ICAO example US example
1 Type of report METAR or SPECI METAR or SPECI
2 Station identifier EGLL KOKC
3 Day and time (UTC) 281050Z 011955Z
4 Report modifier AUTO, COR, NIL AUTO, COR
5 Wind 24012G25KT 200V280 22015G25KT 180V250
6 Visibility 4000 1400SW 3/4SM
7 Runway visual range R24/P2000 R17L/2600FT
8 Present weather +SHRA +TSRA BR
9 Sky condition FEW005 BKN025 OVC010CB
10 Temperature and dew point 10/03 18/16
11 Pressure Q0995 A2992
12 Supplementary information RERA WS R24 (not used)
13 Trend or remarks NOSIG or BECMG RMK AO2 SLP132

FMH-1 caps the US body at 11 groups before the remarks, while CAP 746 describes a UK report of up to 18 groups. In practice you will rarely see every group in one report.

A full ICAO example, decoded

The WMO guide to aerodrome reports (WMO-No. 782) uses this special report as its worked example:

SPECI LUDO 211025Z 31015G27KT 280V350 4000 1400SW R24/P2000 +SHRA FEW005 FEW010CB SCT018 BKN025 10/03 Q0995 RERA WS R24
  • SPECI LUDO: a special report from the station LUDO (a fictitious indicator used in WMO training material).
  • 211025Z: the 21st day of the month at 10:25 UTC. See station identifier and time group.
  • 31015G27KT 280V350: wind from 310 degrees true at 15 knots, gusting 27, direction varying between 280 and 350 degrees. See wind group.
  • 4000 1400SW: prevailing visibility 4,000 m, with a minimum of 1,400 m toward the southwest.
  • R24/P2000: runway visual range on runway 24 above 2,000 m, the top of the reportable scale.
  • +SHRA: heavy showers of rain.
  • FEW005 FEW010CB SCT018 BKN025: cloud layers in hundreds of feet, including cumulonimbus at 1,000 ft. See cloud cover codes.
  • 10/03: temperature 10 °C, dew point 3 °C.
  • Q0995: QNH 995 hPa.
  • RERA WS R24: recent rain, and wind shear reported on runway 24.

A full US example, decoded

The FAA Aviation Weather Handbook (FAA-H-8083-28A, section 24.4) decodes this example report:

METAR KOKC 011955Z AUTO 22015G25KT 180V250 3/4SM R17L/2600FT +TSRA BR OVC010CB 18/16 A2992 RMK AO2 TSB25 TS OHD MOV E SLP132
  • 011955Z AUTO: issued on the 1st at 19:55 UTC by an automated station with no human augmentation. The handbook treats it as the 2000 UTC routine report.
  • 22015G25KT 180V250: wind 220 degrees at 15 knots, gusts 25, direction variable between 180 and 250.
  • 3/4SM: prevailing visibility three quarters of a statute mile.
  • R17L/2600FT: RVR on runway 17 left of 2,600 ft.
  • +TSRA BR: thunderstorm with heavy rain, plus mist.
  • OVC010CB: overcast at 1,000 ft with cumulonimbus.
  • 18/16 A2992: 18 °C over 16 °C, altimeter 29.92 inHg.
  • RMK AO2 TSB25 TS OHD MOV E SLP132: automated station with a precipitation discriminator, thunderstorm began at 25 minutes past the hour, overhead and moving east, sea level pressure 1013.2 hPa.

The remarks section is where most US-only content lives; the METAR remarks guide covers it in full.

Where ICAO and US reports differ

The main US and ICAO differences are units, the remarks section and a handful of coding rules. AIM 7-1-29 and FMH-1 describe the US side; WMO-No. 782 and CAP 746 describe the ICAO side.

Element ICAO practice United States practice
Visibility Meters, 9999 for 10 km or more Statute miles with SM, fractions allowed
RVR Meters, touchdown zone, up to 4 runways Feet with FT suffix
Pressure Q and hectopascals A and inches of mercury
Mean wind 10-minute average 2-minute average
Remarks RMK not used at many aerodromes (for example UK civil) RMK carries AO1/AO2, SLP, T group and more
Trend NOSIG, BECMG, TEMPO at many stations No trend forecast in NWS METARs
Directional visibility Minimum visibility with a direction when required Prevailing visibility; sector values go in remarks

Canada follows a hybrid: statute miles, feet and inches of mercury like the US, with ICAO-style wind shear groups and Canadian remarks. A full comparison is on the US vs ICAO METAR differences page.

Reading strategy for beginners

Breaking the report into blocks makes it faster to read than trying to decode every character in one pass.

  1. Identity block: type, station, time and modifier. Check the time first, because an old report can look perfectly reasonable.
  2. Wind block: direction in degrees true, speed, gust, variability. Compare it with your runway heading.
  3. Visibility block: prevailing visibility, any minimum or sector value, and RVR if present.
  4. Weather and sky block: what is falling or obscuring, then cloud layers from lowest to highest.
  5. Thermo block: temperature and dew point, then pressure.
  6. Tail: trend forecast in ICAO reports, remarks in US and Canadian reports.

When a block is missing in a manual report, the element simply was not reported. In an automated report, slashes often stand in for values the sensors could not determine; CAP 746 shows //// for missing visibility and // when present weather is unavailable.

Common mistakes when reading a METAR

Most decoding errors come from a few recurring traps.

  • Reading wind direction as magnetic. METAR wind is referenced to true north. The AIM notes that ATIS and ASOS or AWOS voice broadcasts give wind relative to magnetic north, so the two can differ by the local magnetic variation. See ATIS.
  • Confusing 9999 with unlimited visibility. It means 10 km or more, nothing more precise.
  • Assuming AUTO means low quality. It means no observer was involved in that report; the content depends on the sensors fitted.
  • Ignoring the minus sign in temperatures. M05 is minus 5 °C.
  • Reading a TAF group in a METAR. BECMG and TEMPO after the main body of an ICAO METAR are a two-hour trend, not a TAF. The trend and NOSIG page explains the difference.

What a METAR is not

A METAR is an observation of conditions at and around one aerodrome at the time of the report. It does not forecast, and it does not describe conditions a few miles away except through vicinity (VC) codes and remarks. For forecast information you need the TAF. For operational use, pilots must rely on official briefings, not on decoders or explainers such as this site.

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 difference between METAR and SPECI?

METAR is the routine report issued at fixed times, hourly in the US and hourly or half-hourly elsewhere. SPECI is an unscheduled special report issued when conditions change past set thresholds, such as a ceiling or visibility crossing a limit, a thunderstorm starting or a wind shift.

Why does a US METAR at 1955Z count as the 2000 report?

US routine observations are taken in the minutes before the hour. FAA guidance shows a report stamped 1955Z as the 2000 UTC observation, and the Federal Meteorological Handbook gives a similar example with 0855Z standing for the 0900 report.

Do all countries use the same METAR format?

The structure comes from WMO and ICAO, but states file differences. The United States uses statute miles, feet for RVR, inches of mercury and a remarks section. Canada also uses statute miles and inches. Most other states use meters, hectopascals and no remarks.

Can I use a METAR decoded on a website for flight planning?

Use official briefing sources for any operational decision. A website decoder, including this one, is a learning aid. Always confirm current reports and forecasts through an approved weather provider or flight service before flying.

Sources

  1. Federal Aviation Administration. Aeronautical Information Manual, Chapter 7 Section 1, Meteorology
  2. Office of the Federal Coordinator for Meteorology (2019). Federal Meteorological Handbook No. 1, Surface Weather Observations and Reports (FCM-H1-2019)
  3. World Meteorological Organization (2025). Manual on Codes, Volume I.1 (WMO-No. 306), FM 15 METAR, as summarized in Aerodrome Reports and Forecasts (WMO-No. 782)
  4. UK Civil Aviation Authority (2023). CAP 746, Requirements for Meteorological Observations at Aerodromes, Issue 6
  5. Federal Aviation Administration (2024). Aviation Weather Handbook (FAA-H-8083-28A)
  6. NAV CANADA. Aviation Weather Services Guide