The PIREP, the One Piece of Your Weather Briefing That Came From a Pilot Who Was Actually Up There, and How to Decode It and File Your Own

Learn what a PIREP is, how to decode its coded fields, and how to file your own pilot report in plain English.

Flight Instructor
Reviewed for accuracy by Matt Carlson (Private Pilot)

A PIREP (pilot report) is the only part of your weather briefing that comes from a human pilot who was actually flying through the conditions, rather than a computer model or automated sensor. It tells you what the atmosphere just did to a real airplane - cloud bases and tops, turbulence, icing, and winds - in a short coded format you can learn quickly. Reading PIREPs sharpens your go/no-go decisions, and filing your own gives the next pilot the truth from inside the sky instead of a forecast’s best guess.

Why Is a PIREP More Valuable Than the Forecast?

Every other product in your briefing is a prediction. The forecast is a model. The ATIS is an automated sensor at the field. The winds aloft are computed. All of it is useful, and all of it describes what the atmosphere is supposed to do.

A PIREP is different. It comes from a pilot who climbed through the layer, felt the ride, and reported exactly where the clouds began and ended and whether the air was smooth. It’s the difference between reading the menu and talking to someone who just ate the meal.

The system is also starving for these reports. Air traffic controllers and Flight Service specialists actively ask for them, especially when conditions are changing - because the forecast can say one thing while the sky does something entirely different, and the only way anyone finds out is if a pilot keys up and says so.

What Do UA and UUA Mean on a PIREP?

There are two types of pilot report:

  • UA - a routine pilot report.
  • UUA - an urgent pilot report.

That double “U” is the sky grabbing you by the collar. Urgent reports are reserved for hazards that hurt: severe or extreme turbulence, severe icing, hail, low-level wind shear, a funnel cloud or tornado, and volcanic ash. When you see UUA, slow down and read every field, because another pilot judged the conditions serious enough to interrupt everyone.

How Do I Decode the Fields in a PIREP?

After the type tag, a PIREP is broken into fields, each with a letter identifier. Here are the ones that matter most on a cross-country:

  • OV (location) - where the pilot was, usually a three-letter navaid identifier followed by a bearing and a distance in nautical miles. This is the pilot’s spot on the map.
  • FL (flight level) - altitude in hundreds of feet. FL060 means 6,000 feet.
  • TP (type of aircraft) - quietly one of the most important fields (more on why below).
  • SK (sky cover) - cloud layers, including the base and top of a layer. This field is gold.
  • TA (temperature aloft) - in degrees Celsius.
  • WV (wind) - direction and speed at altitude; useful for confirming the winds-aloft forecast.
  • TB (turbulence) - intensity (light, moderate, severe) and often the altitude band where it lives.
  • IC (icing) - intensity (trace, light, moderate, severe), type (rime, clear, or mixed), and the altitude where it was encountered.
  • RM (remarks) - the plain-language field where the pilot says whatever didn’t fit in a box. Sometimes the remarks are the best part: “Broke out on top into clear blue,” or “worst chop I’ve had all year.”

Why Does Aircraft Type Matter So Much in a PIREP?

The TP field tells you how much to trust that the ride will feel the same for you. If a Boeing 737 reports light turbulence and you’re flying a Cessna 172, that “light” chop will feel very different in your smaller airplane. Weight matters.

A report of moderate turbulence from another light single is one you take personally. Always read the aircraft type before you decide how seriously to take a ride report.

How Do I Read a PIREP in a Real Scenario?

Say it’s a Saturday morning and you’re planning a two-hour cross-country. The forecast is wishy-washy - marginal in places, with ceilings the TAF says should lift. In your briefing you find a routine report:

  • UA, over a navaid about 30 miles up your route
  • FL055 - 5,500 feet
  • Type: Piper
  • Sky: bottom of an overcast at 3,000, tops at 4,500
  • Temperature aloft: +2°C
  • Remarks: “smooth on top, occasional light rime in the climb”

Look at what that one line does. The forecast said “marginal.” This pilot confirms the ceiling is genuinely at 3,000, the layer isn’t thick, the tops are at 4,500, and it’s smooth and clear once you punch through. If you were instrument rated, current, and legal, a short climb gets you into sunshine.

But the same report also whispers a warning. +2°C at altitude with light rime in the climb means the atmosphere is right on the edge of icing conditions - visible moisture with a temperature near freezing. For a VFR pilot staying out of the clouds on a nice day, that’s fine. For the instrument pilot planning a quick climb through the layer, that “light rime” is the difference between a routine climb and picking up ice in an airplane with no way to shed it.

One report made the flight look better and flagged the single hazard at the same time.

How Do I File My Own PIREP?

Many new pilots never file a single PIREP during training, simply because no one showed them how. Here’s the good news: you don’t have to speak in code. You give the specialist or controller the pieces in plain English, and they code it for you.

You can file two ways:

  1. In the air, call Flight Service on the radio.
  2. Tell the controller you’re already talking to - approach, center, or even tower. Say, “I’d like to file a PIREP,” and they’ll take it.

Use this simple framework:

  1. Who you are and what you’re flying (remember, aircraft type matters).
  2. Where you are and your altitude.
  3. The one thing that made you pick up the mic - cloud bases and tops, how the ride is, whether you’re picking up ice, or whether visibility is better or worse than advertised.

That’s it. For example: “Cessna 172, ten miles south of the field, 6,500, tops of the broken layer are right at 6,000, smooth ride, visibility unlimited on top.” You just filed a PIREP.

When Should I File a PIREP?

Build the habit around these triggers:

  • When the weather differs from the forecast. This is the single most valuable report you can give. If the TAF said tops at 8,000 and you broke out at 5,000, say so - someone on the ground is making a go/no-go decision on that number.
  • When the ride is bad. Report moderate turbulence so controllers can route others around it.
  • When you pick up ice - always, every time. Icing is a hazard where one early warning can save a life.
  • When it’s good, too. “Smooth and clear on top” tells the next pilot the layer is behaving. That’s information.

How Do PIREPs Show Up on My Checkride?

The Airman Certification Standards (ACS) expect you to understand weather information and make sound decisions with it, and the pilot report sits under weather sources. Your examiner wants a pilot who can pull meaning out of a PIREP and fold it into a real decision - not just recite that PIREPs exist.

During the cross-country planning portion, don’t stop at the METAR and TAF. Find the pilot reports and decode one out loud: “Here’s a report from a Cessna at 6,000, tops at 4,500, light chop, and here’s how that changes my thinking about my cruise altitude.”

Then show judgment about the source. If you can say, “That turbulence report is from an airliner, so in my light single I’ll treat it as more than it sounds,” you’ve demonstrated weather maturity that goes well past memorizing definitions. That’s thinking like the pilot in command.

Key Takeaways

  • A PIREP is the only weather product that comes from a real pilot in real air - everything else in your briefing is a model, sensor, or computation.
  • UA is routine; UUA is urgent. A double “U” flags hazards like severe turbulence, severe icing, hail, wind shear, funnel clouds, and volcanic ash.
  • Learn the key fields - OV (location), FL (altitude), TP (aircraft type), SK (sky cover), TA (temperature), WV (wind), TB (turbulence), IC (icing), and RM (remarks).
  • Always check aircraft type - “light” turbulence in a 737 can feel very different in a Cessna 172.
  • File your own reports in plain English, especially when conditions differ from the forecast or when you encounter turbulence or ice.

Radio Hangar. Aviation talk, built by pilots. Listen live | More articles