The PIREP, the Pilot Weather Report, and the One Source in Your Briefing That Comes From Someone Who Was Actually Up There

A Pilot Report (PIREP) is a firsthand account of actual weather conditions reported by a pilot in flight - the only weather product in your preflight briefing sourced from someone who was physically in that air. While surface observations, forecasts, and AIRMETs rely on models, ground sensors, and algorithms, PIREPs deliver real-time cockpit data tied to a specific location, altitude, and time. Understanding how to decode them, assess their limitations, and file your own makes you a sharper pilot and a better contributor to the aviation weather network.

What Is a PIREP and Why Does It Matter?

The Federal Aviation Administration (FAA) officially calls them Pilot Weather Reports. The Aeronautical Information Manual (AIM), Chapter 7, dedicates a full section to how they work, what goes in them, and how to use them.

The core value is direct observation. Every other product in your briefing is inferring what the air is doing. A PIREP is a pilot telling you what the air was actually doing - the ice that formed on the airfoil, the turbulence that rattled the cabin, the smooth layer found above the clouds. That is irreplaceable data. That same directness also introduces limitations worth understanding before you rely on them.

Where to Find PIREPs Before Your Flight

PIREPs are available through three main sources:

• Flight Service includes applicable PIREPs during a standard weather briefing, delivered after SIGMETs and AIRMETs in the briefing sequence
• Moving map applications display PIREPs as tappable icons linked to the full report
• aviationweather.gov - the FAA’s Aviation Weather Center - has a dedicated PIREP query page filterable by location, altitude range, and time window

In every case, you are reading a report tied to a specific aircraft at a specific place and time. Your job is to decode it, assess its currency and relevance, and fold it into your overall weather picture.

How Do You Decode a PIREP?

PIREPs use a structured format with defined fields. Each one carries specific operational information.

UA / UUA - Report Type UA identifies a routine PIREP. UUA identifies an urgent PIREP. These are handled with different priority by the FAA and the National Weather Service.

OV - Location Expressed as a navaid identifier, airport code, or fix - sometimes with a bearing and distance. Two airport identifiers separated by a dash indicate a report covering the area between those two points. A VOR identifier followed by a bearing and mileage places the pilot at that radial and distance from the station.

TM - Time Always in Coordinated Universal Time (Zulu). This field anchors the report in time and tells you how stale it is. A front can move significantly in two hours. Check this field on every report.

FL - Altitude Expressed in hundreds of feet. 180 means 18,000 feet. 075 means 7,500 feet. If conditions spanned a range during a climb or descent, the pilot may report a range of altitudes. A turbulence report at a single altitude is not the same as one covering several thousand feet of airspace.

TP - Aircraft Type This field matters more than most student pilots realize. A transport-category jet reporting moderate turbulence and a Cessna 172 reporting the same intensity are not describing identical experiences. The jet crew’s threshold for “moderate” is calibrated to an aircraft that may weigh 40,000 to 50,000 pounds. When the reporting aircraft is similar in size and performance to yours, the report maps more directly to what you will feel. When it’s a heavy jet, adjust your mental model accordingly.

SK - Sky Condition Cloud layers and altitudes as observed from the cockpit. If the pilot is flying in the clouds and cannot see bases or tops, they may note continuous Instrument Meteorological Conditions (IMC) at their altitude.

WX - Present Weather Rain, snow, freezing rain, or other observed precipitation. If there is no significant weather, this field is often omitted.

TA - Outside Air Temperature Reported in degrees Celsius. This is one of the most valuable fields when assessing icing risk. Structural icing is most active between 0° and -20°C. The most aggressive accretion - fastest buildup, hardest adhesion - typically occurs between -2° and -10°C. A temperature report from a pilot at altitude gives you real data rather than a lapse rate estimate extrapolated from a surface observation.

WV - Winds Reported as a three-digit direction and speed. Winds from due west at 45 knots appear as 270/45. Reported winds can differ significantly from the Winds Aloft forecast, especially near frontal boundaries or in mountain wave areas.

TB - Turbulence The field most pilots scan first. Intensity is standardized by the AIM:

IC - Icing Intensity codes:

Icing type is reported alongside intensity when the pilot can identify it:

• RIME - Porous, opaque ice that forms when supercooled water droplets freeze almost instantly on contact. Builds up quickly and adds weight and drag.
• CLR (Clear ice) - Denser, heavier, and more aerodynamically damaging. Larger droplets partially flow before freezing, conforming to the airfoil shape and degrading lift in ways that are harder to detect and harder to shed.
• MXD (Mixed) - A combination of both, often the most unpredictable in terms of how it accretes.

RM - Remarks Free text - and often where the most operationally useful information lives. “Smooth above the layer” or “turbulence worse below 6,000” carries information the coded fields cannot convey. A note about significant updrafts and downdrafts on the west side of a ridge describes mountain wave activity that could surprise you on an instrument approach. Read the remarks. Do not skip them.

What Makes a PIREP Urgent (UUA)?

A UUA is filed when conditions meet or exceed specific hazard thresholds:

• Tornadoes or funnel clouds
• Severe or extreme turbulence
• Severe icing
• Large hail
• Low-level wind shear below 2,000 feet severe enough to affect aircraft operations
• Volcanic ash

The FAA and the National Weather Service disseminate UUAs with priority to air traffic control and Flight Service. They can trigger SIGMET issuance if conditions are widespread and persistent. A UUA in your briefing is not background information - it is a direct flag about a hazard in the airspace you are considering. Treat it accordingly.

What Are the Limitations of PIREPs?

PIREPs are real data from real pilots, but that does not make them complete, current, or perfectly objective. Three limitations matter most.

Coverage gaps. PIREPs depend on pilots filing them. On a busy route, coverage may be solid. On a rural cross-country through a sparsely flown corridor - especially at night - you may find zero PIREPs for your entire route. The absence of PIREPs is not clearance to proceed. It is a data gap, and data gaps call for conservative assumptions, not optimism.

Recency. A PIREP from three hours ago on an active frontal day may not reflect current conditions. Most briefing tools filter for reports within the last one to two hours, but in thin-coverage areas, older reports may be all that’s available. Use them as historical context, not as a current-conditions snapshot.

Subjectivity. The AIM and the FAA Aviation Weather Handbook codify intensity standards, but human judgment is still in the loop. A pilot with thousands of hours in pressurized turbine equipment and a student pilot on their first significant weather encounter will not have identical calibration for light versus moderate turbulence. The aircraft type field helps you adjust, but it does not eliminate the variability.

These limitations do not make PIREPs less valuable. They make PIREPs one layer in a briefing, not the entire briefing.

How Do PIREPs Factor Into the ACS Checkride?

The Airman Certification Standards (ACS) for the private pilot certificate require you to obtain, interpret, and use aviation weather reports and forecasts appropriate to the flight. PIREPs are specifically included.

An examiner is not going to ask you to define a PIREP in isolation. They will present a weather scenario, walk you through a briefing, and watch how you work through it.

One approach that works: after reviewing the surface analysis, METARs, TAFs, and AIRMETs, stop and ask yourself one question - What is the air actually doing, right now, at the altitudes I plan to fly? PIREPs are your best attempt to answer that with real data.

Solid PIREP coverage with recent reports matching the forecast is meaningful confirmation. No PIREPs at all is a data gap, and your go/no-go decision needs to account for that uncertainty explicitly.

A Practical Example: Mountain Weather

You are planning a flight through the mountains. The TAF at your destination shows broken clouds at 8,000 feet. An AIRMET Sierra covers IFR conditions in the mountains. An AIRMET Tango covers moderate turbulence below 12,000 feet. Both are real, but both are broad - the kind of coverage that is essentially always issued for mountain terrain on active weather days.

Then you check PIREPs. A Piper Cherokee filed 40 minutes ago: moderate turbulence at 7,500 feet, worse in the valleys; smooth at 11,000 feet above the layer. A light twin filed 15 minutes ago: trace to light mixed icing between 8,000 and 10,000 feet; remarks note it started on the climb and cleared above 9,500 feet.

Now you have something specific. The AIRMET Tango is not just a forecast - it is confirmed. The smoother ride is at 11,000 feet. There is a real icing window in the climb through the clouds.

For a VFR-only pilot, those ceilings at 8,000 feet with icing and turbulence embedded in the clouds carry different weight than the TAF suggested on its own. For an instrument-rated pilot, you now know what altitude to request, what to brief passengers on, and what your contingency looks like if icing is worse than reported. Two pilots who took a few minutes to file gave you that picture.

Why Filing Your Own PIREPs Matters

The AIM is direct: pilot weather reports are a vital source of information that cannot be duplicated by any other means. The network works because pilots report. Many do not.

You fly through moderate turbulence at 8,000 feet on a cross-country. Uncomfortable for twenty minutes, nothing dangerous. You land, grab your bag, make your calls. You walk to the car.

Did you file?

Somewhere behind you, a pilot is staring at an AIRMET Tango and trying to decide whether the turbulence is actually occurring or whether it is a blanket forecast. Your PIREP answers that question with data they cannot get any other way.

Negative PIREPs matter too. A smooth ride at an altitude where turbulence was forecast is as operationally useful as an adverse conditions report. Confirmation that the atmosphere is better than predicted helps the next pilot just as much as a warning that it is worse. File both.

How Do You File a PIREP?

Filing is simpler than most pilots expect.

In flight:

• Contact Flight Service on the national frequency 122.2
• Advise a controller you would like to file a PIREP - they will relay it
• Many EFB applications support electronic filing in a few taps

On the ground:

• Call Flight Service directly
• File electronically through a supported app

What to include:

1. Your location over a fix or navaid
2. The time in Zulu
3. Your altitude
4. Your aircraft type
5. Observed conditions: sky condition, temperature, turbulence, icing, winds
6. Remarks with any context that adds operational value

The threshold for filing is lower than most pilots think. Any conditions another pilot would want to know about are worth two minutes. You will rarely know whose decision your report helped - but someone will read it and make a better call because you took the time.

Key Takeaways

• A PIREP is the only weather product in your briefing sourced from a pilot who was physically in that air - not a model, forecast, or ground sensor
• Decode every field: OV (location), TM (time in Zulu), FL (altitude), TP (aircraft type), SK (sky condition), WX (weather), TA (temperature), WV (winds), TB (turbulence), IC (icing), RM (remarks - read these)
• The TP field is critical for calibration - a heavy jet’s “moderate turbulence” and a light single’s may describe different actual intensities; adjust your interpretation based on aircraft type
• Absence of PIREPs is a data gap, not a green light; apply conservative assumptions when coverage is thin
• Negative PIREPs - reporting smooth conditions where turbulence was forecast - are as valuable as hazard reports; file them
• Primary references: AIM Chapter 7 and the FAA Aviation Weather Handbook (free at aviationweather.gov)