A TAF is a forecast for weather significant to aviation within roughly five statute miles of an airport's runway complex. Most United States TAFs cover 24 hours; selected large airports receive 30-hour forecasts. The safest way to read one is as a timeline. Begin with the base conditions, then replace or temporarily modify them only when a change group says to.

Worked forecast

TAF KORD 161720Z 1618/1724 21012KT P6SM SCT035 BKN080 TEMPO 1620/1624 3SM TSRA BKN025CB FM170200 29010KT P6SM SCT040

Issued on the 16th at 17:20 UTC, valid from 18:00 on the 16th through 24:00 on the 17th. Base conditions begin with southwest wind, visibility above six miles and cloud at 3,500 and 8,000 feet. Thunderstorms with three-mile visibility and cumulonimbus are temporarily expected between 20:00 and midnight. From 02:00 on the 17th, the forecast changes to northwest wind with better visibility and scattered cloud.

Build the validity timeline first

KORD is the station. 161720Z is issue time: day 16 at 17:20 UTC. 1618/1724 is the forecast validity period, from day 16 at 18:00 until day 17 at 24:00 UTC. Midnight may appear as 24 rather than 00 at the end of a period. Writing the dates and UTC hours on a line prevents the most common error: applying a later group to the wrong day.

The next groups use almost the same codes as a METAR observation. Wind is 210 degrees at 12 knots. P6SM means visibility greater than six statute miles. SCT035 and BKN080 are scattered cloud at 3,500 feet and broken cloud at 8,000 feet. Unlike a METAR, these are expected conditions, not a measurement.

FM replaces; TEMPO interrupts

FM170200 means from day 17 at 02:00 UTC. An FM group starts a new prevailing forecast and replaces the earlier wind, visibility, weather and cloud picture. If a detail is omitted from the new group under the applicable format rules, do not casually carry every earlier hazard forward. Read the complete group as published and use the national guidance for the product.

TEMPO 1620/1624 means temporary fluctuations are expected between 20:00 and midnight on the 16th. The base forecast remains the prevailing condition, but periods of the listed thunderstorm weather can occur. TEMPO does not say the poorer condition will fill the whole four-hour window. It says it may occur in temporary episodes within it.

BECMG, used more often outside the United States, describes a gradual transition during a time window. PROB30 or PROB40 adds an explicit probability to the conditions that follow, where the issuing state uses those groups. A probability is not a timing prediction. It communicates uncertainty around whether the event will occur.

Read operational clues, not just rain codes

CB after a cloud layer marks cumulonimbus, the cloud associated with thunderstorms. That can matter more than the rain code: convective cells bring lightning, hail, strong vertical currents and abrupt wind changes. The companion guide follows how thunderstorms turn into reroutes and airport delays.

Wind shifts can also change airport capacity. A forecast change from 210 degrees to 290 degrees may trigger a runway configuration change, depending on airport geometry and actual wind. That transition is explained in the runway and crosswind guide. A TAF cannot tell you which runway ATC will choose, but it shows why a switch may become likely.

A TAF is a bounded forecast, not a promise

The NOAA TAF product documentation defines the forecast area as within five statute miles of the airport center. A thunderstorm 12 miles away can disrupt an arrival path without appearing as a condition at the terminal. Conversely, a TEMPO thunderstorm group can verify somewhere in the terminal area without passing directly over every runway.

Scheduled United States TAFs are issued at least four times daily, and amendments can arrive as conditions or confidence change. AMD marks an amended forecast; COR marks a correction. Always check the issue time and whether a newer forecast exists. A screenshot copied hours ago is not a current briefing.

What a passenger can responsibly infer

A TAF can explain risk, not determine your flight's status. Repeated low ceilings, strong gusts or TEMPO thunderstorms raise the chance that airport capacity will fall. They do not prove a specific flight will be late. Aircraft location, crew duty, maintenance, runway demand and the airline's recovery plan all matter. Use the source-by-source tracking workflow alongside the airline's official status.

For an operational decision, use a complete weather briefing and current products from the Aviation Weather Center. This decoder is an educational reading aid, not dispatch or flight-planning advice.

A reliable four-pass reading workflow

  1. Write the validity range. Convert its start and end into dates and UTC times before reading any weather.
  2. Copy the base forecast. Record wind, visibility, weather and cloud that prevail at the opening time.
  3. Place every change group. Mark FM as a new base state and TEMPO or PROB as a temporary or conditional layer.
  4. Find your actual window. Apply only the groups active during the proposed arrival or departure period, then check for a newer AMD or COR.

This prevents a common error in which readers blend the worst condition anywhere in a 24-hour message into the whole day. It also prevents the opposite error: reading only the first line and missing a later deterioration.

Example with probability and gradual change

Suppose a forecast reads TAF EHAM 161700Z 1618/1724 22012KT 9999 SCT025 BECMG 1621/1623 5000 RA BKN012 PROB30 TEMPO 1702/1706 1500 TSRA BKN006CB. The base is good visibility with scattered cloud. Between 21:00 and 23:00 on day 16, conditions are forecast to become 5,000 meters in rain with a broken ceiling at 1,200 feet. Between 02:00 and 06:00 on day 17, there is a 30 percent probability of temporary thunderstorm conditions with 1,500-meter visibility and a 600-foot cumulonimbus layer.

The probability applies only to the group it introduces. The BECMG conditions form the later prevailing state; the PROB30 TEMPO conditions are a possible temporary departure from it. A passenger can reasonably read this as increased disruption risk overnight, not as a 30 percent chance the entire airport closes.

How a forecast verifies

Forecast quality is not judged by whether every minute matches one literal line. Change groups describe expected prevailing, temporary or probabilistic conditions within defined areas and periods. Compare observations with the correct forecast window and category. A thunderstorm slightly outside the terminal area can affect routes without technically verifying a terminal group, while rain at the field can verify without disrupting every flight.

What operational planning adds beyond the TAF

Dispatchers and pilots do not plan a route from one terminal forecast. They review departure, destination and alternate weather, en-route hazards, winds, notices and suitable approaches. Fuel planning includes regulatory and company requirements plus operational judgment. A TAF contributes to that process because it provides a standardized terminal forecast; it does not replace the rest of the briefing.

For a connecting passenger, the relevant weather set can include three airports and two routes. Good weather at the connection does not prevent an inbound delay from a storm elsewhere. Compare the inbound aircraft on the tracked-flight directory with official airline status instead of treating the destination weather icon as the whole network.

A responsible public explanation should quote the exact validity window, state the uncertainty group and avoid language such as the forecast says the airport will close. TAFs describe meteorological conditions. Airport and airline decisions occur later and depend on capacity, equipment and demand.

Three common TAF reading errors

First, readers treat every group as cumulative. FM normally establishes a new prevailing state; TEMPO and probability groups modify a limited window. Second, they convert UTC to local time but forget that the validity period crosses midnight or a daylight-saving change. Third, they read one airport's forecast as coverage for an entire metropolitan area or route.

A simple written timeline solves the first two. A map of station locations solves the third. Preserve UTC beside any local conversion so another reader can reproduce it. If an airport has no TAF, do not copy the nearest one without stating the distance and terrain difference.

Finally, do not confuse forecast amendment with forecast failure. An AMD is evidence that the service incorporated new observations or expectations. For a current decision, the amended product is the one to read.

For a flight spanning several changes, write one row for each interval and include the prevailing condition plus any temporary or probability group that overlaps it. This timeline prevents a dramatic short-lived condition from being presented as an all-day forecast and makes later amendments easy to compare.

Quick lookups

Does TEMPO mean the bad weather lasts for the whole window?

No. It means temporary episodes are expected inside the stated interval while the base forecast remains prevailing. The group does not identify exact start and stop minutes.

Why does my airport have no TAF?

TAFs are issued for selected terminals, not every airport. Use nearby observations and the official graphical and area forecast products appropriate to the flight instead of borrowing a distant TAF as if it covered the field.