What information can be encoded and transmitted as a remark in column 13 of METAR/SPECI observations?

What information can be encoded and transmitted as a remark in column 13 of METAR/SPECI observations?

• A. Supplemental RVR data.
• B. Wind data from dual parallel runways.
• C. Supplementary Data for an Inactive or Parallel Runway.
• D. Aircraft Mishap.

Answer: (A)

In METAR/SPECI, the remarks section (column 13) is used to carry extra information that can’t be neatly fitted into the standard fields. This space is for supplemental data that provides additional context about the observation. A common item placed there is supplemental Runway Visual Range (RVR) data. That means, beyond the primary RVR report for the main runway, the station can include extra RVR values for other runways or additional measurement points, giving a fuller picture of visibility along the airfield. This detail is particularly important at airports with multiple runways or varying sensor coverage, where pilots and operators need to know about multiple RVR conditions. The other choices don’t fit as well because wind data from dual parallel runways is already contained in the wind field and isn’t typically encoded as a remark. Likewise, a phrase like supplementary data for an inactive or parallel runway isn’t a standard RMK item, and an aircraft mishap would be handled through separate channels (NOTAM/UUA) rather than as a routine remark in METAR.

In METAR/SPECI, the remarks section (column 13) is used to carry extra information that can’t be neatly fitted into the standard fields. This space is for supplemental data that provides additional context about the observation. A common item placed there is supplemental Runway Visual Range (RVR) data. That means, beyond the primary RVR report for the main runway, the station can include extra RVR values for other runways or additional measurement points, giving a fuller picture of visibility along the airfield. This detail is particularly important at airports with multiple runways or varying sensor coverage, where pilots and operators need to know about multiple RVR conditions.

The other choices don’t fit as well because wind data from dual parallel runways is already contained in the wind field and isn’t typically encoded as a remark. Likewise, a phrase like supplementary data for an inactive or parallel runway isn’t a standard RMK item, and an aircraft mishap would be handled through separate channels (NOTAM/UUA) rather than as a routine remark in METAR.