The METAR station identifier and date-time group

Tafrob editorial team · Updated · 5 min read

Short answer

After METAR or SPECI comes the station's four-letter ICAO location indicator, such as KSEA or EGLL, then a six-digit group with the day of the month, hours and minutes in UTC, ending in Z. In 011955Z, the report is from the 1st at 19:55 UTC. Month and year are never coded, so you infer them from context.

Key points

  • Station identifiers are four-letter ICAO location indicators, not the three-letter IATA codes printed on luggage tags.
  • In the contiguous United States the ICAO code is K plus the three-letter domestic identifier, so SEA becomes KSEA.
  • The time group is DDHHMMZ in UTC; the month and year are not part of the report.
  • US routine reports are often stamped a few minutes before the hour, and FAA material treats 1955Z as the 2000 report.
  • A corrected report keeps the date and time of the report it corrects.
Automated Surface Observing System mast and sensors beside the airfield at Northeast Philadelphia Airport
Photo: Famartin, CC BY-SA 4.0, via Wikimedia Commons

Where the identification groups sit

The first three items of every METAR identify the report: its type, the reporting station and the time it applies to. WMO-No. 782 calls these the identification groups and shows them as METAR CCCC YYGGggZ, where CCCC is the location indicator, YY the day, GG the hour and gg the minutes. Optional modifiers such as AUTO, COR or NIL follow immediately after; they are covered on the AUTO, COR and NIL page.

Part Code Meaning Example
Report type METAR or SPECI Routine or special report METAR
Station CCCC ICAO four-letter location indicator KDCA
Day YY Day of the month, two digits 21
Hour and minute GGgg UTC time, 24-hour clock 0855
Time zone letter Z UTC (Zulu) Z

How ICAO station identifiers are built

ICAO location indicators are four letters with a regional structure, which is why they differ from the three-letter IATA codes used for tickets. The FAA Aviation Weather Handbook and AIM paragraph 7-1-29 describe the pattern for North America:

Region Prefix Example
Contiguous United States K plus the domestic three-letter code SEA becomes KSEA
Alaska PA PAxx
Hawaii PH PHxx
Guam PG PGxx
Puerto Rico TJ SJU becomes TJSJ
Canada CU, CW, CY, CZ CYXE (Saskatoon)
Mexico MM MMxx
Cuba, Dominican Republic, Bahamas MU, MD, MY MUxx, MDxx, MYxx

The AIM points to ICAO Document 7910, Location Indicators, for the full worldwide list. FMH-1 adds that a US identifier sent long-line must be four alphabetic characters. You can look up codes on the ICAO airport codes page.

A practical trap: the K-plus-three rule only holds in the lower 48 states. Outside them, there is no reliable way to guess an ICAO code from an IATA code, so look it up.

Decoding the date and time group

The date and time group is six digits followed by Z: two for the day of the month, two for the hour and two for the minutes, all in UTC. FMH-1 requires 24-hour UTC times in every disseminated report and notes that 0000 and 2359 mark the beginning and end of the day.

US example from the FAA Aviation Weather Handbook:

METAR KOKC 011955Z AUTO 22015G25KT 180V250 3/4SM R17L/2600FT +TSRA BR OVC010CB 18/16 A2992
  • KOKC: the station identifier used in the handbook example, a K-prefixed code from the contiguous US.
  • 011955Z: 1st day of the month, 19:55 UTC. The handbook reads it as the 2000 UTC routine report.

ICAO example from WMO-No. 782:

SPECI LUDO 211025Z 31015G27KT 280V350 4000 1400SW R24/P2000 +SHRA
  • LUDO: the location indicator WMO uses in its examples.
  • 211025Z: the 21st at 10:25 UTC. Because this is a SPECI, the time is when the special criterion was met, not a scheduled slot.

Canadian example from the NAV CANADA guide:

METAR CYXE 292000Z CCA 30015G25KT 3/4SM R33/4000FT/D -RA BR BKN008 OVC040 21/19 A2992
  • CYXE: Saskatoon. 292000Z: the 29th at 20:00 UTC. NAV CANADA states that routine observations are taken on the hour.

To convert to local time, subtract or add the UTC offset for the station's time zone and season. For instance, Oklahoma City is on Central Time: in winter (UTC-6) the KOKC report stamped 1955Z was observed at 1:55 p.m. local time, while in summer (UTC-5) the same stamp means 2:55 p.m. The Zulu time converter does this for you.

Scheduled time versus actual time

US rules separate the scheduled time of a report from the actual time printed in it. FMH-1 defines the scheduled time as the UTC time a METAR must be available for transmission, and the actual time as when the last element was observed. For a SPECI, the time is when the criterion was met or noted.

FMH-1 gives a clear example: METAR KDCA 210855Z is the 0900 scheduled report from station KDCA, taken at 0855 UTC on the 21st. FAA Order JO 7900.5E says routine METARs are prepared for transmission between H+55 and H+00, and that observations may not start more than 15 minutes before the scheduled time. That is why US hourly reports so often carry minutes in the 50s.

Other states run different clocks:

Source Routine schedule described
WMO-No. 782 METAR issued hourly or half-hourly
FMH-1 and JO 7900.5E (US) Hourly, prepared between H+55 and H+00
CAP 746 (UK) Every half hour, typically observed at H+20 and H+50, sent within 5 minutes
NAV CANADA guide Routine observations taken on the hour

Do not assume that every ICAO station reports at exactly H+00 and H+30. The UK, for example, uses H+20 and H+50.

Edge cases worth knowing

A few situations break the simple reading of the time group.

  • Corrections. FMH-1 and CAP 746 both say a corrected report keeps the time of the report being corrected. A COR stamped 0855Z replaces the 0855Z report, even if it was sent later.
  • Month boundaries. Only the day is coded. When you read archived data around the turn of a month, check the source's date field rather than trusting the day number alone.
  • Day rollover. A report at 2350Z on the 31st and one at 0050Z on the 1st are one hour apart, not thirty days.
  • Special reports. A SPECI can carry any minute value, because it is tied to an event. See SPECI special report.
  • Delayed reports. JO 7900.5E says delayed and corrected reports are sent as soon as possible after H+00, so the transmission time and the report time can differ.

Common mistakes

Most errors with these groups come from reading local time into a UTC report or mixing up code systems.

  • Treating 1955Z as late. In the US it is usually the on-time 2000 report.
  • Converting with the wrong daylight saving offset.
  • Typing an IATA code into a METAR request outside the contiguous US.
  • Reading the first two digits as the hour. They are the day.

These groups are the frame for everything that follows in the report; the rest is explained in how to read a METAR. This page is educational and is not a source for operational weather.

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

Frequently asked questions

Why are METAR times in Zulu?

Zulu is the aviation name for UTC. Using one time reference avoids confusion across time zones and daylight saving changes. FMH-1 requires all disseminated times to use the 24-hour UTC clock, and ICAO and WMO formats end the group with the letter Z.

Is the METAR identifier the same as the airport code on my ticket?

Not usually. Tickets use three-letter IATA codes. METARs use four-letter ICAO location indicators. In the contiguous US the two line up with a K prefix, but elsewhere, for example in Europe, the ICAO code is often unrelated to the IATA letters.

How do I know which month a METAR is from?

The report itself only gives the day of the month. Current reports are almost always from the present month, but archived reports need their month and year from the data source or file name. Near month end, check that day 31 is not from the previous month.

Why does a UK METAR say 20 or 50 minutes past the hour?

CAP 746 states that UK METARs are sent every half hour and that observations are typically made at 20 minutes past the hour and 10 minutes to the hour, then transmitted within 5 minutes. Other states use different schedules.

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 (FCM-H1-2019)
  3. Federal Aviation Administration (2024). Aviation Weather Handbook (FAA-H-8083-28A)
  4. Federal Aviation Administration (2020). Order JO 7900.5E, Surface Weather Observing
  5. World Meteorological Organization (2025). Aerodrome Reports and Forecasts, A Users' Handbook to the Codes (WMO-No. 782)
  6. UK Civil Aviation Authority (2023). CAP 746, Requirements for Meteorological Observations at Aerodromes
  7. NAV CANADA. Aviation Weather Services Guide