A METAR looks like a wall of code until you learn to read it the way a dispatcher does: in a fixed order, one group at a time, never jumping ahead. Master the sequence and any observation becomes readable in a single pass.
Read in the order the report is written
Every METAR follows the same grammar. The trick is not memorizing every contraction — it is trusting the order so your eye always knows what comes next.
- Station & time — the ICAO identifier and the day/time in Zulu.
- Wind — direction in degrees true, speed in knots, gusts after the G.
- Visibility — statute miles in the US, meters elsewhere.
- Weather — intensity, descriptor, and phenomenon, in that order.
- Sky condition — coverage and height, lowest layer first.
- Temp / dewpoint — the spread that tells you fog risk.
- Altimeter — the A-group, your pressure setting.
- Remarks — everything after RMK that the coded groups could not say.
The groups that change a release
Not every group carries equal operational weight. For a dispatcher building a release, three deserve a second look every single time.
Wind shear and gusts
A gust spread of 15 knots or more changes runway and performance planning. Wind shear noted in remarks (WS) can drive an alternate decision on its own.
The temperature–dewpoint spread
When temperature and dewpoint converge within a couple of degrees, fog and low stratus are likely. That spread is often a better early-warning signal than the visibility group itself.
Read the spread before you read the visibility. The spread tells you where the weather is going; visibility only tells you where it is.
— Senior dispatcher, regional Part 121 carrier
Build the habit
Pull ten random METARs a day and read them aloud in order. Within two weeks the sequence becomes automatic, and the 60-second read stops being a goal and becomes your baseline.