Remarks shall be included in all METAR and SPECI, if appropriate.

Note: The United States does not report remarks in the same manner as the WMO standard.

Remarks shall be separated from the body of the report by a space and the contraction RMK. If there are no remarks, the contraction RMK is not required.

METAR/SPECI remarks fall into 2 categories: (1) Automated, Manual, and Plain Language, and (2) Additive and Maintenance Data.

Remarks shall be made in accordance with the following:

• Where plain language is called for, authorized contractions, abbreviations, and symbols should be used to conserve time and space. However, in no case should an essential remark, of which the observer is aware, be omitted for the lack of readily available contractions. In such a case, the only requirement is that the remark be clear.

• Time entries shall be made in minutes past the hour if the time reported occurs during the same hour the observation is taken. Hours and minutes shall be used if the hour is different, or this handbook prescribes the use of the hour and minutes.

• Present weather coded in the body of the report as VC may be further described, i.e., direction from the station, if known. Weather phenomena beyond 10 statute miles of the point(s) of observation shall be coded as distant (DSNT) followed by the direction from the station. For example, precipitation of unknown intensity within 10 statute miles east of the station would be coded as "VCSH E"; lightning 25 statute miles west of the station would be coded as "LTG DSNT W".

• Distance remarks shall be statute miles except for automated lightning remarks which are in nautical miles.

• Movement of clouds of weather, if known, shall be coded with respect to the direction toward which the phenomena is moving. For example, a thunderstorm moving toward the northeast would be coded as "TS MOV NE".

• Directions shall use the eight points of the compass coded in clockwise order.

• Insofar as possible, remarks shall be entered in the order they are presented in the following paragraphs.

Automated, Manual, and Plain Language Remarks

These remarks generally elaborate on parameters reported in the body of the report. Automated and manual remarks may be generated either by an automated or manual station. Plain language remarks are only provided from manual stations.

1. Volcanic Eruptions (Plain Language). Volcanic eruptions shall be coded. The remark shall be plain language and contain the following, if known:

   • Name of volcano.

   • Latitude and longitude or the direction and the approximate distance from the station.

   • Date/Time (UTC) of the eruption.

   • Size description, approximate height, and direction of movement of the ash cloud.

   • Any other pertinent data about the eruption.
   For example, a remark on a volcanic eruption would look like the following:

   MT. AUGUSTINE VOLCANO 70 MILES SW ERUPTED 231505 LARGE ASH CLOUD EXTENDING TO APRX 30000 FEET MOVING NR.

   Pre-eruption volcanic activity shall not be coded. Pre-eruption refers to unusual and/or increasing volcanic activity which could presage a volcanic eruption.

2. Funnel Cloud (Tornadic activity_B/E(hh)mm_LOC/DIR_(MOV)). At manual stationS, tornadoes, funnel clouds, or waterspouts shall be coded in the format, TORNADIC ACTIVITY_B/E(hh)mm_LOC/DIR_(MOV), where:

   • TORNADO, FUNNEL CLOUD, or WATERSPOUT identifies the specific tornadic activity,

   • B/E denotes the beginning and/or ending time,

   • (hh)mm is the time of occurrence (only the minutes are required if the hour can be inferred from the time of the report),

   • LOC/DIR is the location and/or direction of the phenomena from the station, and

   • MOV is the movement, if known, from the station.

   Tornadic activity shall be coded as the first remark after the "RMK" entry. For example, "TORNADO B13 6 NE" would indicate that a tornado, which began at 13 minutes past the hour, was 6 statute miles northeast of the station.

3. Type of Automated Station (AO1 or AO2). AO1 or AO2 shall be coded in all METAR/SPECI from automated stations.

   • AO1 - Automated stations without a precipitation discriminator.

   • AO2 - Automated stations with a precipitation discriminator.

4. Peak Wind (PK_WND_dddff(f)/(hh)mm). The peak wind shall be coded in the format, PK_WND_dddff(f)/(hh)mm of the next METAR, where:
   • PK_WND is the remark identifier,

   • ddd is the direction of the peak wind,

   • ff(f) is the peak wind speed since the last METAR, and

   • (hh)mm is the time of occurrence (only the minutes are required if the hour can be inferred from the report time).

   There shall be a space between the two elements of the remark identifier and the wind direction/speed group. A solidus "/" (without spaces) shall separate the wind direction/speed group and the time. For example, a peak wind of 45 knots from 280 degrees that occurred at 15 minutes past the hour would be coded "PK WND 28045/15".

5. Wind Shift (WSHFT_(hh)mm). A wind shift shall be coded in the format WSHFT_(hh)mm, where:
   • WSHFT is the remark identifier and

   • (hh)mm is the time the wind shift began (only the minutes are required if the hour can be inferred from the report time).

   The contraction FROPA may be entered following the time if it is reasonably certain that the wind shift was the result of a frontal passage. There shall be a space between the remark identifier and the time and, if applicable, between the time and the frontal passage contraction. For example, a remark reporting a wind shift accompanied by a frontal passage that began at 30 minutes after the hour would be coded as "WSHFT 30 FROPA".

6. Tower or Surface Visibility (TWR_VIS_vvvvv or SFC_VIS_vvvvv). Tower visibility or surface visibility shall be coded in the formats, TWR_VIS_vvvvv or SFC_VIS_vvvvv, respectively, where:
   • vvvvv is the observed tower/surface visibility value. A space shall be coded between each of the remark elements. For example, the control tower visibility of 1 1/2 statute miles would be coded "TWR VIS 1 1/2".

7. Variable Prevailing Visibility (VIS_v_nv_n v_nv_nVv_xv_xv_x v_xv_x). Variable prevailing visibility shall be coded in the format VIS_v_n v_nv_nv_nVv_xv_x v_xv_xv_x where:
   • VIS is the remark identifier, v_n v_nv_nv_n is the lowest visibility evaluated,
   • V denotes variability between two values, and v_xv_xv_xv_xv_x is the highest visibility evaluated.

   There shall be one space following the remark identifier; no spaces between the letter V and the lowest/highest values. For example, a visibility that was varying between 1/2 and 2 statute miles would be coded "VIS 1/2V2".

8. Sector Visibility (VIS_[DIR]_vvvvv){Plain Language]. The sector visibility shall be coded in the format VIS_[DIR]_vvvvv, where:
   • VIS is the remark identifier,
   • [DIR] defines the sector to 8 points of the compass, and
   • vvvvv is the sector visibility in statute miles, using the appropriate set of values in Table A-3.

   For example, a visibility of 2 1/2 statute miles in the northeastern octant would be coded "VIS NE 2 1/2".

9. Visibility At Second Location (VIS_vvvvv_[LOC]). At designated automated stations, the visibility at a second location shall be coded in the format VIS_vvvvv_[LOC], where:
   • VIS is the remark identifier,
   • vvvvv is the measured visibility value, and
   • [LOC] is the specific location of the visibility sensor(s) at the station.

   This remark shall only be generated when the condition is lower than that contained in the body of the report. For example, a visibility of 2 1/2 statute miles measured by a second sensor located at runway 11 would be coded "VIS 2 1/2 RWY11".

10. Lightning (Frequency_LTG(type)_[LOC]).
    • When lightning is observed at a manual station, the frequency, type of lightning, and location shall be reported. The remark shall be coded in the format Frequency_LTG(type)_[LOC]. The contractions for the type and frequency of lightning shall be based on Table A-22. For example, "OCNL LTGICCG OHD", "FRQ LTG VC", or "LTG DSNT W".

    • When lightning is detected by an automated system:
      • Within 5 nautical miles of the Airport Location Point (ALP), it will be reported as TS in the body of the report with no remarks.

      • Between 5 and 10 nautical miles of the ALP, it will be reported as VCTS in the body of the report with no remarks.

      • Beyond 10 but less than 30 nautical miles of the ALP, it will be reported in remarks only as LTG DSNT followed by the direction from the ALP.

    Table A-22. Type and Frequency of Lightning
    Type of Lightning
    Type	Contraction	Definition
    Cloud-ground	CG	Lightning occurring between cloud and ground.
    In-cloud	IC	Lightning which takes place within the cloud.
    Cloud-cloud	CC	Streaks of lightning reaching from one cloud to another.
    Cloud-air	CA	Streaks of lightning which pass from a cloud to the air, but do not strike the ground.
    Frequency of Lightning
    Frequency	Contraction	Definition
    Occasional	OCNL	Less than 1 flash per minute.
    Frequent	FRQ	About 1 to 6 flashes per minute.
    Continuous	CONS	More than 6 flashes per minute.

11. Beginning and Ending of Precipitation (w'w'B(hh)mmE(hh)mm). At designated stations, the beginning and ending of precipitation shall be coded in the format, w'w'B(hh)mmE(hh)mm, where:
    • w'w' is the type of precipitation,

    • B denotes the beginning,

    • E denotes the ending, and

    • (hh)mm is the time of occurrence (only the minutes are required if the hour can be inferred from the report time).

    There shall be no spaces between the elements. The coded remarks are not required in SPECI and should be reported in the next METAR. Intensity qualifiers shall not be coded. For example, if rain began at 0005, ended at 0030, and snow began at 0020, and ended at 0055, the remarks would be coded "RAB05E30SNB20E55". If the precipitation were showery, the remark would be coded "SHRABO5E30SHSNB20E55".

12. Beginning and Ending of Thunderstorms (TSB(hh)mmE(hh)mm). The beginning and ending of thunderstorm(s) shall be coded in the format, TSB(hh)mmE(hh)mm, where:
    • TS indicated thunderstorm,

    • B denotes the beginning,

    • E denotes the ending, and

    • (hh)mm is the time of occurrence (only the minutes are required if the hour can be inferred from the report time).

    There shall be no spaces between the elements. For example, if a thunderstorm began at 0159 and ended at 0230, the remark would be coded "TSB0159E30".

13. Thunderstorm Location (TS_LOC_(MOV_DIR)) [Plain Language]. Thunderstorm(s) shall be coded in the format, TS_LOC_(MOV_DIR), where:
    • TS identifies the thunderstorm activity,
    • LOC is the location of the thunderstorm(s) from the station, and
    • MOV_DIR is the movement with direction, if known.

    For example, a thunderstorm southeast of the station and moving toward the northeast would be coded "TS SE MOV NE".

14. Hailstone Size (GR_[size])[Plain Language]. At designated stations, the hailstone size shall be coded in the format, GR_[size], where:
    • GR is the remark identifier and

    • [size] is the diameter of the largest hailstone. The hailstone size shall be coded in 1/4 inch increments.

    For example, "GR 1 3/4" would indicate that the largest hailstones were 1 3/4 inches in diameter. If GS is coded in the body of the report, no hailstone size remark is required.

15. Virga (VIRGA_(DIR)) [Plain Language]. Virga shall be coded in the format, VIRGA_(DIR) where:
    • VIRGA is the remark identifier and
    • DIR is the direction from the station. The direction of the phenomena from the station is optional, e.g., "VIRGA" or "VIRGA SW".

16. Variable Ceiling Height (CIG_h_nh_n h_nVh_xh_xh_x). The variable ceiling height shall be coded in the format, CIG_h_nh_n h_nVh_xh_xh_x, where:
    • CIG is the remark identifier,
    • h_nh_nh_n is the lowest ceiling height evaluated,
    • V denotes variability between two values, and
    • h_xh_xh_x is the highest ceiling height evaluated.

    There shall be one space following the remark identifier; no spaces between the letter V and the lowest/highest ceiling values. For example, "CIG 005V010" would indicate a ceiling that was varying between 500 feet and 1,000 feet.

17. Obscurations (w'w'_[N_sN_sN_s] h_sh_sh_s) [Plain Language]. Obscurations (surface-based or aloft) shall be coded in the format, w'w'_[N_s N_sN_s]h_sh_sh_s, where:
    • w'w' is the weather causing the obscuration at the surface or aloft,

    • N_sN_sN_s, is the applicable sky cover amount of the obscurations aloft (FEW, SCT, BKN, OVC) or at the surface (FEW, SCT, BKN), and

    • h_sh_sh_s is the applicable height.

    Surface-based obscurations shall have a height of "000". There shall be a space separating the weather causing the obscuration and the sky cover amount; there shall be no space between the sky cover amount and the height. For example, fog hiding 3-4 oktas of the sky would be coded "FG SCT000"; a broken layer at 2,000 feet composed of smoke would be coded "FU BKN 020".

18. Variable Sky Condition (N_sN_sN_s (h_sh_sh_s)_V_ N_sN_sN_s) [Plain Language]. The variable sky condition remark shall be coded in the format, N_sN_sN_s (h_sh_sh_s)_V_ N_sN_sN_s, where:
    • N_sN_sN_s (h_sh_sh_s) and N_sN_sN_s identifies the two operationally significant sky conditions and V denotes the variability between the two ranges. If there are several layers with the same sky condition amount, the layer height (h_sh_sh_s) of the variable layer shall be coded. For example, a cloud layer at 1,400 feet that is varying between broken and overcast would be coded "BKN014 V OVC".

19. Significant Cloud Types [Plain Language]. The significant cloud type remark shall be coded in all reports in the folling manner:
    1. Cumulonimbus or Cumulonimbus Mammatus (CB or CBMAM_LOC_(MOV_DIR). Cumulonimbus or cumulonimbus mammatus, as appropriate, (for which no thunderstorm is being reported) shall be coded in the format, CB or CBMAM_LOC_(MOV_DIR), where:
       • CB or CBMAM is the cloud type,
       • LOC is the direction from the station, and
       • MOV_DIR is the movement with direction (if known).

       The cloud type, location, movement, and direction entries shall be separated from each other with a space. For example, a CB up to 10 statute miles west of the station moving toward the east would be coded CB W MOV E. If the CB was more than 10 statute miles to the west, the remark would be coded CB DSNT W.

    2. Towering Cumulus (TCU_[DIR]). Towering cumulus clouds shall be coded in the format, TCU_[DIR], where:
       • TCU is the cloud type and
       • DIR is the direction from the station.

       The cloud type and direction entries shall be separated by a space. For example, a towering cumulus cloud up to 10 statute miles west of the station would be coded TCU W.

    3. Altocumulus castellanus (ACC_[DIR]). Altocumulus castellanus shall be coded in the format, ACC_[DIR], where:
       • ACC is the cloud type and
       • DIR is the direction from the station.

       The cloud type and direction entries shall be separated by a space. For example, an altocumulus cloud 5 to 10 statute miles northwest of the station would be coded ACC NW.

    4. Standing lenticular or Rotor clouds (CLD_[DIR]). Stratocumulus (SCSL), altocumulus (ACSL), or cirrocumulus (CCSL), or rotor clouds shall be coded in the format, CLD_[DIR], where:
       • CLD is the cloud type and
       • DIR is the direction from the station.

       The cloud type and direction entries shall be separated by a space. For example, altocumulus standing lenticular clouds observed southwest through west of the station would be coded ACSL SW-W; an apparent rotor cloud 5 to 10 statute miles northeast of the station would be coded APRNT ROTOR CLD NE; and cirrocumulus clouds south of the station would be coded CCSL S.

20. Ceiling Height at Second Location (CIG_hhh_[LOC]). At designated stations, the ceiling height at a second location shall be coded in the format, CIG_hhh_[LOC], where:
    • CIG is the remark identifier,
    • hhh is the measured height of the ceiling, and
    • [LOC] is the specific location of the ceilometer(s) at the station.

    This remark shall only be generated when the ceiling is lower than that contained in the body of the report. For example, if the ceiling measured by a second sensor located at runway 11 is broken at 200 feet, the remark would be CIG 002 RWY 11.

21. Pressure Rising or Falling Rapidly (PRESRR/PRESFR). At designated stations, when the pressure is rising or falling rapidly at the time of the observation, the remark PRESRR (pressure rising rapidly) or PRESFR (pressure falling rapidly) shall be included in the report.

22. Sea-Level Pressure (SLPppp). At designated stations, the sea-level pressure shall be coded in the format SLPppp, where:
    • SLP is the remark identifier and
    • ppp is the tens, units, and tenths of the sea-level pressure in hectopascals.

    For example, a sea-level pressure of 998.2 hectopascals would be coded as SLP982. For a METAR, if sea-level pressure is not available, it is coded as .

23. Aircraft Mishap (ACFT_MSHP) [Plain Language]. If a report is taken to document weather conditions when notified of an aircraft mishap, the remark ACFT_MSHP shall be coded in the report but not transmitted. The act of non-transmission shall be indicated by enclosing the remark in parentheses in the record, i.e., ACFT MSHP.

24. No SPECI Reports Taken (NOSPECI) [Plain Language]. At manual stations where SPECI's are not taken, the remark NOSPECI shall be coded to indicate that no changes in weather conditions will be reported until the next METAR.

25. Snow Increasing Rapidly (SNINCR_[inches-hour/inches on ground]). At designated stations, the snow increasing rapidly remark shall be reported, in the next METAR, whenever the snow depth increases by 1 inch or more in the past hour. The remark shall be coded in the format, SNINCR_[inches-hour/inches on ground], where:
    • SNINCR is the remark indicator,
    • inches-hour is the depth increase in the past hour, and
    • inches on ground is the total depth of snow on the ground at the time of the report.

    The depth increase in the past hour and the total depth on the ground are separated from each other by a solidus /. For example, a snow depth increase of 2 inches in the past hour with a total depth on the ground of 10 inches would be coded SNINCR2/10.

26. Other Significant Information [Plain Language]. Agencies may add to a report other information significant to their operations, such as information on fog dispersal operations, runway conditions, FIRST or LAST report from station, etc.