Military PIREP: How Service Pilot Reports Differ
A military PIREP is built from the same parts as a civil one. Same fields, same slashes, same hazard words. A decoder that handles one handles the other without a change.
What differs is not the format. It is the kind of flying behind the report, and that changes which hazards turn up and where.
The format is shared
Every PIREP uses tagged fields, each opened by a slash and a two-letter code.
/OV gives the location, usually a fix and a bearing and distance. /TM gives
the time in hours and minutes Zulu. /FL gives the altitude. /TP gives the
aircraft type.
Then the hazards. /TB carries turbulence, /IC carries icing, /SK carries
cloud and tops, /WX carries flight visibility and weather, and /RM carries
remarks in plain words.
A service report uses all of these in the same way. The aircraft in /TP may be
a C17 or an F16 rather than a B738, and the field does the same job.
Routine and urgent
The header carries either UA or UUA, and the difference is worth knowing.
UA is a routine report. UUA is urgent, and it is used when the report holds
something hazardous: severe or extreme turbulence, severe icing, low-level wind
shear, a tornado, hail, or volcanic ash.
Urgent reports move through the system ahead of routine ones. If you see UUA,
somebody decided this could not wait.
That marker is the same on civil and military reports. It is set by what was met in the air, not by who was flying.
What service flying puts in the feed
The hazard words do not change. The mix does, and it follows the mission.
Low-level route training puts aircraft down where the air is roughest. That produces mountain wave and low-level wind shear reports from heights most airline traffic has long since climbed through.
Formation work produces turbulence reports with a sharper edge, because a wing aircraft feels air the leader has already stirred.
High-altitude operations add clear-air turbulence reports from above the usual airway levels. Air refuelling tracks generate reports from long periods at one level, which makes them unusually good evidence about that level.
Reading the type field
/TP matters more here than almost anywhere else, and it is easy to skip.
Turbulence intensity is defined by what the aircraft does, so the same air gives different words from different aircraft. Moderate from a heavy transport is not moderate from a light trainer.
A fighter reporting light chop tells you very little about what a light twin will find. A tanker reporting moderate at your level tells you a great deal.
So read /TP before you weigh /TB. The type sets the scale the intensity word
was measured on.
Where to find them
Military reports are not held in a separate system. They land in the same feed as everything else.
The aviation weather data services carry both, and flight planning tools show them together. A report from a military aircraft appears next to one from an airliner, with nothing but the type field to tell them apart.
That is useful in thin areas. Over sparsely flown terrain, a service aircraft on a low-level route may be the only report you get for a long way in any direction.
Reading the remarks
The /RM field is plain words, and on a service report it often holds the best
part.
A coded field can only say so much. The remark is where a pilot writes what the codes have no slot for. Where the wave started. Which side of the ridge was worse. How fast the ice built.
Some of the most useful remarks are about what stopped. Tops of a layer, the level where chop died away, the height where the ice let go. Those give you a way out, not just a warning.
Read the remark even when the coded fields look mild. A light turbulence report with a note about a sharp wave over a ridge is a different report from a bare one.
Verdict on military PIREP
Treat a military PIREP as an ordinary PIREP with a different aircraft on the front. The fields, the hazard words and the urgency marker all work the same way.
The value is in where these aircraft fly. Low levels over rough ground, high levels above the airways, and quiet regions with no other traffic. Read the type field, weigh the intensity against it, and take the report as seriously as you would any other.
Frequently asked questions
Is a military PIREP formatted differently from a civil one?
No. It uses the same slash-delimited fields: OV for location, TM for time, FL for altitude, TP for aircraft type, and TB and IC for turbulence and icing. A decoder that reads one reads the other.
What is a UUA?
An urgent pilot report. It replaces UA in the header when the report carries something hazardous, such as severe turbulence, severe icing, wind shear, a tornado or volcanic ash. Urgent reports are distributed ahead of routine ones.
Do military pilots report different hazards?
The vocabulary is the same, but the flying is not. Low-level route work, formation and high-altitude operations produce more mountain wave, low-level wind shear and high-level turbulence reports than typical civil traffic.
Where do military PIREPs appear?
In the same feed as civil ones. Flight planning tools and the aviation weather data services carry both together, so a report from a military aircraft sits alongside airline and general aviation reports.
Is an AIREP the same as a PIREP?
No. An AIREP starts with ARP and is downlinked automatically by the aircraft, with fields in fixed positions and no slashes. A PIREP is passed by a pilot and uses tagged fields.