AUTO, COR and NIL: the METAR report modifiers

Tafrob editorial team · Updated · 6 min read

Short answer

AUTO marks a report produced entirely by an automated system with no human input. COR marks a corrected report that replaces an earlier one with an error. NIL means the report is missing. ICAO puts COR before the station code, the US puts COR where AUTO would be, and Canada uses CCA, CCB and so on.

Key points

  • AUTO means no human observer touched the report; when an observer signs on or augments, AUTO disappears.
  • COR flags a corrected report, and US rules never show AUTO and COR in the same observation.
  • NIL replaces the weather groups when the report itself is missing.
  • ICAO places COR after METAR and before the station code; the US and Canada place their correction words after the time group.
  • An AUTO report can only contain what its sensors can measure, so cloud types, thunderstorms and some weather types may be absent or coded with slashes.
Automated Weather Observation System sensor mast at Pennridge Airport in Bucks County, Pennsylvania
Photo: Famartin, CC BY-SA 4.0, via Wikimedia Commons

What the three modifiers do

AUTO, COR and NIL are report modifiers: short code words placed near the start of a METAR or SPECI that describe the report itself, not the weather. WMO-No. 782 treats them as part of the identification groups, right after the report type, station and time covered in the station identifier and time group.

Modifier Meaning Source
AUTO Fully automated observation, without human intervention WMO-No. 782, FMH-1, JO 7900.5E
COR Corrected report that replaces an earlier one WMO-No. 782, FMH-1, CAP 746
NIL Missing report WMO-No. 782
CCA, CCB... Canadian corrected report, first and second correction NAV CANADA guide

None of them changes how the rest of the report is decoded. They tell you how much to trust the coverage of the groups that follow.

AUTO: a report with no human in the loop

AUTO identifies a METAR or SPECI as a fully automated report. WMO-No. 782 says the word is inserted when the report contains a fully automated observation without human intervention. FMH-1 describes it the same way, as a report with no human intervention or oversight.

The US rule has a practical consequence. FAA Order JO 7900.5E says the absence of AUTO means the report is either manual or an automated report with an observer logged on to the system. When an observer signs on, the AUTO tag at the start of the observation is dropped. The Aviation Weather Handbook calls these augmented observations: a human adds weather beyond the automated system's capability or deemed operationally significant, and AUTO is not used.

In the US, an AUTO report also names its equipment. The AIM states that when AUTO appears in the body, the type of sensor equipment is coded in the remarks. That is why you see RMK AO1 or RMK AO2 after it; see AO1 and AO2 for the difference.

Canada uses AUTO the same way. The NAV CANADA guide says AUTO indicates that the observation was taken by an AWOS, and the same word appears on reports from its more basic limited weather information system, which measures only wind, altimeter setting, temperature and dew point.

COR and the Canadian CCA: corrections

COR marks a corrected report. WMO-No. 782 inserts COR, or NIL, as appropriate for corrected or missing reports. The position depends on the system you are reading.

System Where the correction goes Example
ICAO (WMO, UK) Between the report type and the station METAR COR EGZZ 301150Z 18025G35KT 8000 ...
US In the modifier slot after the time group, in place of AUTO METAR KXXX 011955Z COR ...
Canada After the time group; CCA first, CCB second correction METAR CYXE 292000Z CCA 30015G25KT ...

The ICAO placement comes from the WMO code form METAR COR CCCC YYGGggZ, and CAP 746 repeats it: a correction is indicated by METAR COR before the ICAO location indicator. FMH-1 says that in a corrected US report the modifier COR is substituted in place of AUTO. NAV CANADA explains that CCA indicates the first correction and CCB the second.

The example lines above show the placement only; the weather groups are illustrative. The NAV CANADA line is taken directly from its guide.

Two more rules matter for correction handling:

  • Time stays the same. FMH-1 and CAP 746 both say a corrected report keeps the time of the report it corrects. CAP 746 adds that the time is changed only if the time of the observation itself was wrong.
  • US exclusivity. JO 7900.5E states that AUTO and COR are never seen in the same observation: if COR is used, the observation cannot be AUTO, because an observer is correcting it. The order also says COR on an augmented station is the way a corrected report is marked.

NIL: a report that does not exist

NIL is the code word for a missing report. In WMO-No. 782 the format is METAR CCCC YYGGggZ NIL, and the same word appears in TAF messages when the forecast is missing. The message identifies which report is absent, the station and the time slot, and then stops. There are no wind, visibility or weather groups to decode.

NIL is easy to confuse with other uses of the word. In the UK, CAP 746 uses NIL in reports to air traffic services when there is no weather significant to aviation. That is a different message type from the METAR. In a Canadian pilot report, the free-text remark NIL TURB means no turbulence. In a METAR, the code word NIL always refers to the report as a whole.

What an AUTO report cannot tell you

An automated report contains only data its sensors can measure. The practical limits differ by country, and the sources describe them in detail.

United States

  • JO 7900.5E says cloud layers above 12,000 feet are not reported by automated sky condition sensors, and that sensors may truncate the sky condition group to three layers. This is why an automated site can report clear below 12,000 feet; see SKC, CLR, NSC and NCD.
  • The same order notes that the automated systems do not accept the SH entry, so shower descriptors are an area where an observer's augmentation matters.
  • The Aviation Weather Handbook notes that automated stations substitute time averaging for the spatial averaging a human does. Sky condition is evaluated from sensor data gathered over the 30 minutes before the observation, and other elements use data from the last 10 minutes or less.

United Kingdom

  • CAP 746 requires AUTO METARs to carry wind, visibility, cloud, temperature, dew point, pressure and present weather, with RVR, thunderstorm, cumulonimbus and towering cumulus provided when the aerodrome is operational and when required.
  • Missing data is coded with slashes: six slashes for cloud when the system is not operating, //// for visibility, // for present weather when the sensor is unserviceable. Cloud groups from a system that cannot detect cloud type end in ///.
  • NCD means the system has determined that there are no clouds below 5000 feet. CAP 746 gives //////CB and //////TCU for convective cloud detected without height or amount.
  • If the sensor cannot tell the form of precipitation, UP or FZUP is used. See UP, unknown precipitation.

Canada

  • NAV CANADA notes that AWOS systems outside the Canadian Lightning Detection Network coverage area do not receive lightning data, so they cannot report thunderstorm or lightning activity.

Read an AUTO report as a measurement from a machine with a known range. A missing cloud type or a lack of TS does not prove the sky is free of convection; it may only mean the system cannot see it. When a station's sensors fail, a maintenance indicator or sensor status remark may be added; see maintenance indicator and sensor status. For the equipment itself, see ASOS and AWOS stations.

Decoded examples

ICAO automated report from CAP 746:

METAR EGZZ 290450Z AUTO VRB02KT 3000 BR NCD 10/09 Q1002=

AUTO sits between the time group and the wind group. NCD says the system detected no cloud below 5000 feet.

US automated report from the Aviation Weather Handbook:

METAR KOKC 011955Z AUTO 22015G25KT 180V250 3/4SM R17L/2600FT +TSRA BR OVC010CB

If an observer had signed on, the same report would carry no AUTO. If it were a correction, COR would take the place of AUTO.

Canadian corrected report from the NAV CANADA guide:

METAR CYXE 292000Z CCA 30015G25KT 3/4SM R33/4000FT/D -RA BR BKN008 OVC040 21/19 A2992

Common mistakes

  • Assuming that AUTO means the data is worse. It means the data comes from sensors only.
  • Looking for COR next to the station code in a US report. In the US it sits in the AUTO slot.
  • Reading NIL in a METAR as "no weather". It means the report is missing.
  • Treating the absence of CB or TS in an AUTO report as proof that none exists.

The rest of the report is read as usual; the full walk-through is 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

Does AUTO mean a METAR is less reliable?

Not by itself. AUTO only states that no human was involved. The report is limited to what the sensors can measure, so cloud above the sensor range, cloud type or some weather types may be missing or coded with slashes. Check the remarks and treat gaps as unknown, not as absence.

Why is there no AUTO in some reports from automated stations?

US rules drop the AUTO tag when an observer signs on to the system, because the report then has human augmentation or backup. The absence of AUTO therefore means either a manual report or an automated one with an observer logged on.

What does COR change in a METAR?

COR marks the report as a correction that replaces an earlier one containing an error. FMH-1 and CAP 746 both keep the time of the original observation, so a COR stamped 0855Z replaces the 0855Z report rather than creating a new observation.

What does NIL mean in a METAR?

WMO-No. 782 gives NIL as the code word for a missing report. The message carries the report type, the station and the time group, then NIL, with no wind, visibility or weather groups after it.

Sources

  1. World Meteorological Organization (2025). Aerodrome Reports and Forecasts, A Users' Handbook to the Codes (WMO-No. 782)
  2. UK Civil Aviation Authority (2023). CAP 746, Requirements for Meteorological Observations at Aerodromes
  3. Office of the Federal Coordinator for Meteorology (2019). Federal Meteorological Handbook No. 1 (FCM-H1-2019)
  4. Federal Aviation Administration (2020). Order JO 7900.5E, Surface Weather Observing
  5. Federal Aviation Administration (2024). Aviation Weather Handbook (FAA-H-8083-28A)
  6. Federal Aviation Administration. Aeronautical Information Manual, Chapter 7 Section 1, Meteorology
  7. NAV CANADA. Aviation Weather Services Guide