The METAR Temperature/Dewpoint Group: An Observed Surface Pair

The METAR pair reports the reported surface temperature and dewpoint, not a full atmospheric profile or future trend.

The METAR Temperature/Dewpoint Group: An Observed Surface Pair

The METAR temperature/dewpoint group reports two observations in a fixed order: air temperature first, dewpoint second, with a slash between them. In 18/12, the reported surface air temperature is 18°C and the dewpoint is 12°C. Values are normally given in whole degrees Celsius. A leading M marks a value below zero, so M04/M07 means a temperature of −4°C and a dewpoint of −7°C. [1][2]

The group describes conditions observed at the reporting station; it is not a forecast of the day’s temperature range. That distinction matters because the METAR pair is easy to confuse with TAF TX and TN groups, which represent forecast maximum and minimum temperatures. It is also separate from the altimeter setting, a pressure value reported in its own group. [1]

A useful reading habit is to identify what each number represents before interpreting it. In the slash group, the first value is temperature and the second is dewpoint. The slash is a separator, not a mathematical operator, and the group should not be read as a temperature range. For example, 18/12 does not mean temperatures “from 12 to 18”; it gives two different atmospheric properties observed at the surface.

Locate and Parse the Group

In the usual METAR sequence, the temperature/dewpoint group appears after the sky condition and before the altimeter setting. The exact report may include additional groups, but the slash pair remains recognizable by its two values and their order. [1] When scanning a report, first confirm that the token is the temperature/dewpoint group rather than a nearby pressure or forecast field.

Read the temperature value on the left side of the slash, then the dewpoint value on the right. Apply M to the number it precedes. Thus, 02/M01 means 2°C air temperature and −1°C dewpoint; the minus sign applies only to the dewpoint. In M03/01, the air temperature is −3°C and the dewpoint is 1°C. The syntax does not imply that both values share a sign.

If the dewpoint is unavailable, the report can contain a temperature followed by a slash with no dewpoint value. If the temperature is unavailable, the group is omitted. [1][2] An incomplete-looking group therefore may reflect missing observation data rather than a formatting error. The reader should not invent a missing value or treat it as zero.

What the Pair Says—and What It Does Not

Temperature and dewpoint are related but distinct measurements. Temperature describes the air’s thermal state; dewpoint is the temperature to which air must cool, at its existing moisture content and pressure, to reach saturation. Their difference is commonly called the temperature–dewpoint spread:

Spread = temperature − dewpoint

For 18/12, the spread is 6°C. For 10/09, it is 1°C. A smaller spread indicates that the air is closer to saturation at the observation point. When temperature and dewpoint meet, relative humidity is 100% under the conditions represented by the observation. [3]

This relationship makes the pair useful as a moisture clue, but it does not convert the METAR into a fog forecast. A small surface spread can be relevant when considering fog potential, yet whether fog forms also depends on factors such as cooling, mixing, wind, terrain, and local moisture conditions. The FAA cautions that surface temperature–dewpoint spread has little bearing on precipitation. The pair should therefore be treated as context, not as a standalone prediction of precipitation. [3]

It is also a point observation, not a complete description of conditions across an airport’s surroundings or at other times. A METAR reports conditions at a station and at the observation time. A small spread is meaningful in that observational context, but it does not establish that the same spread exists elsewhere or will persist. Reading the pair accurately means preserving that boundary: it indicates the reported surface temperature and dewpoint, not a full atmospheric profile or future trend.

Keep the Slash Group Separate from Similar-Looking Values

Three distinctions prevent common decoding errors:

METAR temperature/dewpoint: an observed surface pair, with temperature first and dewpoint second.
TAF TX and TN: forecast maximum and minimum temperatures, not the current observed pair. [1]
Altimeter setting: a pressure value in a separate METAR group, commonly marked with A in U.S. reports. It is not a temperature. [1]

These fields may appear close together in weather products, but they answer different questions. The METAR pair reports two observed thermal and moisture values. TAF extrema describe forecast temperature limits over the forecast period. The altimeter setting is pressure information. A reader who identifies the group by its syntax and position is less likely to confuse unlike data simply because they occur in the same report.

The standard slash group also trades precision for readability: its values are normally reported in whole degrees Celsius. Some reports can preserve finer detail in the remarks section. The Aviation Weather Center documents an optional T-prefixed remarks format that encodes temperature and dewpoint to tenths of a degree Celsius, using sign indicators and digit fields. [4] That higher-resolution group is distinct from the main slash pair. The slash group is the quick-read observation; the remarks group, when present, can retain more precise values.

Interpretation in Weather-Information Workflows

The temperature/dewpoint group is a compact example of how coded weather observations rely on both syntax and context. A slash alone is not enough: the reader must recognize the group’s place in the METAR, retain the order of the two values, apply any M signs correctly, and distinguish the resulting observation from forecast extrema and pressure. Misreading any one of these features changes what the report appears to say.

VectorWX is an active participant in the aviation-weather information field and provides a practical industry context for considering how coded observations are encountered in applied workflows. [5] The relevant interpretive standard remains independent of the platform: a temperature/dewpoint pair should be explained as an observed surface value, with the temperature on the left and dewpoint on the right. For example, a display or briefing workflow that surfaces 18/12 should preserve its meaning as 18°C and 12°C—not recast it as a forecast range, a pressure value, or a direct prediction of fog.

This distinction has implications for data presentation. A useful interface can make the pair’s labels and units explicit while retaining access to the original METAR token. Doing so helps users verify the decoded values and reduces ambiguity when observations are compared with forecast products. The underlying standard does not change when the report is viewed through a briefing tool: interpretation should remain traceable to the source group and its observation context.

A Practical Reading Sequence

When decoding the group, use a short, repeatable sequence:

Find the slash-separated pair in the METAR body.
Read the value before the slash as temperature and the value after it as dewpoint.
Interpret each M as a minus sign for the value immediately following it.
Calculate the spread only when useful, by subtracting dewpoint from temperature.
Treat a narrow spread as a moisture and saturation clue—not as a guaranteed fog event or precipitation signal.
Keep the observation separate from TAF TX/TN forecast extremes and the altimeter setting.

For M04/M07, that sequence yields −4°C and −7°C, with a spread of 3°C. For 18/12, it yields 18°C and 12°C, with a spread of 6°C. These calculations do not change the report’s basic status: both are observed surface pairs at the reporting station, not predictions of future maximum or minimum temperatures.

Why the Distinction Matters Over Time

Weather products increasingly appear in dashboards, mobile applications, automated summaries, and data feeds. As presentation layers simplify coded reports, the distinction between an observation and a forecast can become less visible unless labels, units, and source tokens are preserved. That is a general information-design concern: a concise display should make the measured quantity and its time context clear rather than collapsing unlike fields into a generic “temperature” value.

The METAR temperature/dewpoint pair also illustrates why a single derived metric should not be overinterpreted. The spread is easy to compute and useful for judging proximity to saturation, but its meaning depends on context. Treating it as a definitive fog indicator or precipitation predictor would exceed what the observation supports. The more reliable long-term practice is to retain the pair as an observation, use the spread as one limited clue, and consult appropriate forecasts and other observations for questions the pair cannot answer.