How to Brief Aviation Weather Before Every Flight

A complete preflight weather briefing covers the big picture (the synopsis and any adverse conditions), the specifics (current METARs and TAFs for your departure, route, destination, and alternates), the hazards (G-AIRMETs, SIGMETs, and PIREPs), the winds aloft, NOTAMs and TFRs, and finally the performance numbers those conditions produce: density altitude and runway wind components. That’s the whole job. Everything below is how to do it in a repeatable order, in about ten minutes, so nothing gets skipped.

The regulatory hook is 14 CFR 91.103, Preflight action: “Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight.” For any flight under IFR, or any flight not in the vicinity of an airport, that explicitly includes weather reports and forecasts, fuel requirements, and alternatives if the flight can’t be completed as planned. For every flight, it includes runway lengths and takeoff and landing distance data under expected conditions. Note what the rule doesn’t say: it never mentions calling anyone. How you become familiar is up to you. That it happens is not.

The three ways to get a briefing

There are three legitimate paths to the same information, and most of us use some blend of them.

Call Flight Service. 1-800-WX-BRIEF (800-992-7433) connects you to a briefing specialist at Leidos, the FAA’s contracted Flight Service provider for the continental US, Hawaii, and Puerto Rico. (Alaska still has its own FAA-run flight service stations.) A phone briefing is still the right tool when the weather is genuinely marginal and you want a second set of trained eyes, or when you’re somewhere with no data signal. The specialist has the full picture and can interpret, not just recite.

Brief online through 1800wxbrief.com. Leidos runs a web portal at the same brand. Log in, enter a route, and it generates a briefing package, files flight plans, and sends adverse-condition alerts if the picture changes after you brief. Because you’re logged in, the briefing is recorded against your name, which matters to some pilots (more on that in the FAQ).

Self-brief. Pull the products yourself from aviationweather.gov, an EFB, or an app, and assemble the picture in your own head. The FAA formally endorsed this path in Advisory Circular 91-92, Pilot’s Guide to a Preflight Briefing (2021), which lays out how to conduct a self-briefing and treats Flight Service as a consultative resource rather than a mandatory stop. Self-briefing is how most of us actually operate day to day. The catch: nobody hands you a structure, so you need to bring your own. That’s what the sequence below is for.

Standard, abbreviated, and outlook briefings

These three terms come from AIM 7-1-5, and they describe scope, not method:

• Standard briefing: the full package, requested when you haven’t already been briefed. Adverse conditions, synopsis, current conditions, en route and destination forecasts, winds aloft, NOTAMs.
• Abbreviated briefing: an update. You’ve already briefed and you want to refresh one or two items, or fill a specific gap.
• Outlook briefing: for planning, when your proposed departure is six or more hours away. Forecast data only, and it never substitutes for a standard briefing closer to departure.

The same logic maps cleanly onto self-briefing. The night before is an outlook. The full pass an hour or two before departure is your standard. The last glance at the METAR while you’re doing the walkaround is an abbreviated update.

A self-brief sequence that works

The order matters more than the tools. Work from big picture to fine detail, then hazards, then the numbers your airplane cares about. Going the other way (opening the destination METAR first, seeing it’s VFR, and calling it done) is how forecasts sneak up on people.

1. Start with the synopsis

Before any coded product, get the story: where the fronts are, what’s moving, and whether today’s pattern is building or dying. The Graphical Forecasts for Aviation (GFA) on aviationweather.gov shows clouds, weather, and surface features on one map you can step forward in time. Two minutes here gives every later product context. A TAF that says gusty southwest winds after 2000Z means more when you already know there’s a cold front due that evening.

This is also where radar and satellite belong. Not as a go/no-go tool yet, but as a reality check on the story: is there convection anywhere upstream, and is it growing or collapsing? A loop tells you far more than a still frame. What those colors actually mean, and the traps in the mosaic, are covered in reading radar like a pilot. If cells are already firing at 1600Z along a route you’ll fly at 2100Z, the afternoon TAF lines deserve your full attention.

2. METARs and TAFs for departure, route, destination, and alternate

Now the specifics. METARs tell you what’s happening right now at a reporting station; TAFs tell you what’s expected at an airport over the next 24 hours (30 at some international hubs), issued four times daily around 0000Z, 0600Z, 1200Z, and 1800Z. They answer different questions, and you need both: the METAR validates whether the TAF is verifying. If the TAF said scattered at 8,000 by now and the METAR still shows overcast at 3,000, the forecast is losing, and you should weight everything else it promises accordingly. The full comparison is in our guide to METAR vs TAF.

Here’s the kind of read we mean. Plain English first: Centennial Airport at 1653Z, wind from 170 at 8 knots, visibility 10 miles, scattered clouds at 7,000 ft with a broken layer at 12,000 ft, temperature 29 °C, dew point 9 °C, altimeter 30.12.

KAPA 231653Z 17008KT 10SM SCT070 BKN120 29/09 A3012

Looks benign. But hold on to two numbers: 29 °C at a field elevation near 5,900 ft. That’s a density altitude problem we’ll come back to in step 7. If decoding is still slow going, run the raw text through our METAR decoder until the format reads at a glance.

Then the TAF for the same field. Decoded: forecast issued 1522Z, valid from 1600Z on the 23rd to 1200Z on the 24th. Initially wind 180 at 10 knots, better than 6 miles visibility, scattered at 8,000 ft. From 2000Z, wind 200 at 15 gusting 25 knots with thunderstorms in the vicinity and a broken cumulonimbus layer at 6,000 ft. From 0300Z, wind 270 at 8 knots and clear.

KAPA 231522Z 2316/2412 18010KT P6SM SCT080
     FM232000 20015G25KT P6SM VCTS BKN060CB
     FM240300 27008KT P6SM SKC

That FM232000 line is the whole briefing in one row: a clean morning, an ugly afternoon, and a quiet night. If your plan had you returning at 2100Z, this is where it dies. Our TAF decoder will walk each line if you want the practice.

One more habit: watch for AMD in the header. An amended TAF means the forecaster has already conceded the scheduled forecast was wrong, which is exactly the kind of day to keep re-briefing.

3. G-AIRMETs and SIGMETs

Next, the area hazards. G-AIRMETs are graphical advisories for conditions hazardous mainly to light aircraft: moderate icing, moderate turbulence, sustained surface winds over 30 knots, widespread IFR conditions, and mountain obscuration, drawn as snapshots at 3-hour intervals. SIGMETs cover weather significant to every aircraft: severe icing, severe turbulence, thunderstorm systems (as Convective SIGMETs), dust storms, and volcanic ash.

One currency note worth knowing: the old text AIRMET product was retired for the continental US in January 2025. The G-AIRMET is now the advisory of record there, so if a briefing source is still showing you six-hour text AIRMETs for the lower 48, it’s stale. We cover the products, their thresholds, and how to read the graphics in AIRMETs and SIGMETs explained.

Check these even on a blue-sky day. Clear air holds moderate turbulence advisories more often than people expect, and a mountain-obscuration G-AIRMET can be active while your departure airport reports 10 miles and clear.

4. PIREPs

Forecasts are hypotheses. PIREPs are data. A pilot report tells you what the air actually did to an airplane in the last hour: where the bases and tops really are, what the ride is like, whether the icing advisory is verifying. On aviationweather.gov and in every serious EFB, PIREPs plot along your route with age and altitude. Read the ones within about 50 miles and two hours; older than that, treat as history. And file your own, because the system only works if pilots feed it. Reading and filing both have their own conventions, covered in PIREPs: reading them, filing them.

5. Winds aloft

The winds and temperatures aloft forecast (FB) is produced four times daily from 0000Z, 0600Z, 1200Z, and 1800Z model data. It sets your groundspeed, your fuel plan, and your altitude choice, and it hints at ride quality: a large speed change between adjacent altitudes means shear, and shear means bumps. Two decoding conventions trip people up. A wind group of 9900 means light and variable, under 5 knots. And above 24,000 ft the temperature’s minus sign is dropped, because it’s always negative up there. The full format, including winds over 100 knots, is in our guide to reading winds aloft forecasts.

The practical habit: check the forecast at your planned altitude and one level above and below. Sometimes 2,000 ft buys you 15 knots of groundspeed or a smoother ride, and the FB is the only product that tells you.

6. NOTAMs and TFRs

Not weather, but 91.103 says “all available information,” and a closed runway or a stadium TFR will ruin your day faster than a 200-foot ceiling error. Pull NOTAMs for departure, destination, and alternates, and check TFRs along the route (tfr.faa.gov, or the TFR layer in your EFB). Fresh TFRs pop up on short notice, especially in the summer fire and event season, so this check belongs in your final update too, not just the standard brief.

7. Performance numbers: density altitude and runway winds

Last step: turn the weather into aircraft performance, which is the part of 91.103(b) most self-briefings skip. Two computations, every flight.

Density altitude. Take that KAPA METAR again: 29 °C at a field elevation of 5,885 ft. Standard temperature up there is about 3 °C, so the air is running roughly 26 °C hot, and the density altitude works out near 9,000 ft. A normally aspirated airplane that books a 900-foot ground roll at sea level will need on the order of twice that, and climb like it’s bored. Run your actual numbers through the density altitude calculator, then open the POH takeoff chart with the result. High elevation isn’t required for this to bite; a 35 °C afternoon at a 2,000-foot field with a short runway deserves the same math.

Runway wind components. Take the forecast wind, not just the current one. The KAPA TAF’s afternoon line, 200 at 15 gusting 25, against runway 17 is a 30-degree offset: about 8 knots of crosswind sustained, 13 in the gusts, with the rest headwind. Fine for most of us. The same gust from 260 would be nearly all crosswind, and a different conversation. The crosswind calculator does the trigonometry; you supply the honesty about your own limits.

The preflight weather briefing checklist

The sequence above, compressed to something you can run every time. Order preserved on purpose.

The night before (outlook):

1. Synopsis and GFA: what’s the pattern, and which way is it trending?
2. TAFs for departure and destination: does the plan survive the forecast?
3. Winds aloft: pick a candidate altitude, rough out the fuel.

1 to 2 hours before departure (standard):

4. Synopsis again: did the story change overnight?
5. METARs: departure, route, destination, alternate. Are the TAFs verifying?
6. TAFs: reread every line against your actual times, in Zulu.
7. G-AIRMETs and SIGMETs along the route, including one panel past your ETA.
8. PIREPs within about 50 miles and 2 hours of your route.
9. Winds aloft: confirm altitude choice, fuel required plus reserves.
10. NOTAMs for all airports of intended use, TFRs along the route.
11. Density altitude at departure and destination; POH takeoff and landing distances.
12. Wind components for the runways you’ll actually use, using forecast winds.
13. Decide: go, delay, reroute, or scrub. Say it out loud, with a reason.

At the airplane (abbreviated):

14. Latest METAR, any new SIGMETs or TFRs, one last radar look if convection is possible.

If any item surprises you at step 14, the sequence starts over, not the engine.

Common self-briefing mistakes

Briefing the destination and skipping the route. The classic. Departure clear, destination clear, and a 40-mile band of IFR ceilings sitting quietly between them. The GFA and the route METARs exist for exactly this.

Reading current conditions as forecasts. A gorgeous 1500Z METAR says nothing about your 2200Z return. Summer convection builds on a schedule, and the TAF’s FM lines are where that schedule is written.

Ignoring the forecast’s track record. A TAF that has already busted twice today deserves skepticism about tonight, too. Comparing METAR to TAF each time you brief is the cheapest forecast-verification tool there is.

Treating the app’s summary as the briefing. Color-coded route summaries are a starting point, not a conclusion. The summary can’t know that your personal crosswind limit is 12 knots or that your airplane climbs poorly at 9,000 ft density altitude. Open the underlying products.

Skipping hazards on clear days. Turbulence and mountain obscuration advisories don’t need a cloud in the sky over your departure airport to be active along your route.

Stopping before the performance step. Knowing it’s 29 °C is weather trivia. Knowing your ground roll just doubled is a briefing. 91.103(b) makes the takeoff and landing distance check a required part of preflight action, not an optional extra for high-elevation pilots.

Briefing once and going quiet. A standard briefing at 1400Z does not cover a 2300Z return leg. Brief the round trip as two flights, and update before the second one.

FAQ

Is a self-briefing legal?

Yes. 14 CFR 91.103 requires that you become familiar with all available information before flight; it doesn’t prescribe a source or require contacting Flight Service. The FAA addressed this directly in AC 91-92, which provides guidance for conducting preflight self-briefings using automated resources and positions Flight Service as a consultative option. The regulation cares that the briefing happened and was complete, not who read the TAF to you.

Does a self-briefing count if something goes wrong? Am I “on record”?

Calling 1-800-WX-BRIEF or briefing while logged into 1800wxbrief.com creates a retrievable record that you were briefed. Loading products on aviationweather.gov anonymously does not. Legally, the record was never the requirement; familiarity was. If you want documentation, an EFB briefing package or a logged 1800wxbrief.com session provides it, and either is worth having if you’re ever asked to show your preflight action was thorough.

How far in advance should I brief the weather?

Twice, at minimum. An outlook look the evening before tells you whether the plan is plausible and lets you sleep on alternatives. The real briefing belongs within a couple of hours of departure, when the current TAF cycle and fresh METARs describe the flight you’re actually about to make, followed by a final update at the airplane. Weather products age fast: a six-hour-old briefing describes a different atmosphere.

Common questions

What is the difference between a standard, abbreviated, and outlook briefing?

Standard, abbreviated, and outlook describe scope, not method (AIM 7-1-5). A standard briefing is the full package when you have not been briefed yet: adverse conditions, synopsis, current conditions, forecasts, winds aloft, NOTAMs. An abbreviated briefing updates one or two items you have already seen. An outlook briefing covers a departure six or more hours away and is forecast data only, never a substitute for a standard brief closer to departure.

How long does a preflight weather briefing take?

Run in a fixed order, a self-brief takes about ten minutes: two minutes on the synopsis and GFA, a few on METARs and TAFs for departure, route, destination and alternate, then hazards, winds aloft, NOTAMs and TFRs, and finally density altitude and runway wind components. The fixed order is the point, and it is what keeps anything from being skipped.

Does 14 CFR 91.103 require takeoff and landing distance calculations?

Yes. For every flight, 91.103(b) requires the pilot in command to be familiar with runway lengths at airports of intended use and with takeoff and landing distance data for the expected conditions. That means turning the weather into performance: density altitude at departure and destination, then the POH chart. It applies at a low-elevation field on a hot afternoon, not just in the mountains.