Blog / Route Weather

Defining the PIREP /WX Group: Functional Purpose and Syntactic Boundaries

Explains the purpose, syntax, parsing boundaries, and evolving digital formats of the PIREP /WX group for reported weather and flight visibility.

October 23, 2026 · VectorWX · 7 min read

Defining the PIREP /WX Group: Functional Purpose and Syntactic Boundaries

Defining the PIREP /WX Group: Functional Purpose and Syntactic Boundaries

In aeronautical meteorology, the Pilot Weather Report (PIREP) provides ground-truth observation of conditions aloft. Standardized under Federal Aviation Administration (FAA) protocols, the textual structure of a PIREP relies on discrete, slash-delimited identifiers to compartmentalize telemetry, positional data, and observed meteorological variables [1]. Among these fields, the /WX group is reserved specifically for pilot-reported atmospheric phenomena and in-flight flight visibility [1], [2].

A persistent operational vulnerability in human interpretation and automated text-ingestion systems is the conflation of the /WX group with neighboring operational descriptors. The /WX field encodes observed meteorological phenomena—such as liquid or frozen precipitation, lithometeors, and atmospheric obscurations—and, when available, forward flight visibility [1]. It does not encode kinematic turbulence intensity or turbulence character, which are strictly isolated within the /TB group [1]. It does not codify structural or airframe icing accretion types, which belong exclusively to the /IC group [1]. Furthermore, it does not define spatial or geographical reference points, which are governed entirely by the /OV (over/location) field [1], [2].

The /WX group answers what weather was reported, separate from turbulence in /TB, icing in /IC, and location in /OV [1], [3].

PIREP Canonical Group Sequence:
[/OV Location] ──> [/TM Time] ──> [/FL Altitude] ──> [/TP Type] ──> [/WX Weather] ──> [/TB Turbulence] ──> [/IC Icing] ──> [/RM Remarks]
  └── Where         └── When       └── Altitude       └── Aircraft    └── What           └── Kinematic       └── Structural      └── Metadata
                                                                          (Precip/Vis)       Disturbance         Accretion

Lexical Architecture and Parsing Mechanics of the /WX Field

The internal syntax of the /WX block is parsed strictly from left to right [1]. The field accommodates up to two primary functional components: a flight visibility prefix and up to three discrete meteorological phenomenon descriptors [1], [2].

Syntax: /WX [FVxxSM] [Qualifier][Phenomenon] ... (Max 3 groups)
Example: /WX FV02SM +TSRAGR
         │  │      │ │ └─ Precip: Rain (RA) & Hail (GR)
         │  │      │ └─── Descriptor: Thunderstorm (TS)
         │  │      └───── Intensity: Heavy (+)
         │  └──────────── Visibility: 02 Statute Miles
         └─────────────── Weather Group Identifier

Flight Visibility Serialization (FV Prefix)

When forward flight visibility is included, that token comes first inside the /WX string [1]. The usual form is:

  1. The literal identifier FV.
  2. A two-digit integer indicating the visibility range in statute miles.
  3. The literal unit suffix SM.

The reported visibility value is subject to strict mathematical truncation: fractional values are rounded down to the nearest whole statute mile [1]. For instance, an observed flight visibility of 2.75 statute miles is transmitted as FV02SM [1]. In clear operating conditions aloft where visibility is functionally unimpeded (frequently defined as 10 statute miles or greater), the token FV99SM is applied to signify unrestricted forward visibility [1], [2]. If visibility is near zero due to severe obscuration or cloud immersion, the token manifests as FV00SM [1].

Meteorological Descriptors and Descriptor Sequencing

Following the flight visibility indicator (or initializing the /WX group if flight visibility is omitted), up to three distinct meteorological phenomena tokens may be recorded [1]. These tokens largely match the present weather contractions defined under International Civil Aviation Organization (ICAO) and FAA METAR/TAF standards, but they adhere to distinct PIREP aggregation rules [1], [2].

Intensity qualifiers directly precede the specific phenomenon:

  • - indicates light intensity [1].
  • The absence of an algebraic sign denotes moderate intensity [1].
  • + indicates heavy intensity [1].

The FAA specifies critical exceptions to intensity coding. Certain phenomena, including hail (GR) and ice crystals (IC when used as a METAR phenomenon code, not to be confused with the /IC PIREP group), do not accept an intensity prefix [1].

Precipitation & Obscuration Taxonomy in /WX:
├── Descriptors:    TS (Thunderstorm), SH (Showers), FZ (Freezing)
├── Precipitation:  RA (Rain), DZ (Drizzle), SN (Snow), GR (Hail), PL (Ice Pellets)
├── Obscurations:   FG (Fog, vis < 5/8 SM), BR (Mist, vis ≥ 5/8 SM), HZ (Haze), FU (Smoke)
└── Other:          VA (Volcanic Ash), SQ (Squall), FC (Funnel Cloud/Tornado)

Common phenomena include:

  • Liquid Precipitation: RA (Rain), DZ (Drizzle)
  • Frozen Precipitation: SN (Snow), PL (Ice Pellets), GR (Hail)
  • Atmospheric Obscurations: HZ (Haze), FU (Smoke), VA (Volcanic Ash)
  • Hydrometeors of variable saturation: FG (Fog, indicating visibility strictly below 5/8 statute mile), BR (Mist, indicating visibility equal to or greater than 5/8 statute mile) [1], [2].

When multiple phenomena manifest concurrently, FAA Order JO 7110.10 establishes an explicit hierarchy of descending importance [1]:

  1. Severe convective phenomena: Tornadoes, waterspouts, or funnel clouds (FC) occupy the primary slot.
  2. Thunderstorms (TS).
  3. Remaining precipitation and obscuration types ordered by relative predominance [1].

For example, an observation containing severe convective activity, significant liquid precipitation, and hail is assembled as /WX FV00SM +TSRAGR [1]. In this compound string, FV00SM establishes zero visibility, the + indicates heavy intensity, TS identifies the thunderstorm cell, RA identifies the dominant precipitation as rain, and GR flags the presence of hail [1], [2].

Disambiguation Strategies and Operational Ingestion Models

The proper decoding of raw PIREP messages requires clear disambiguation between the /WX element and adjacent tokens. When manual readers or legacy regular-expression parsers scan an alphanumeric report, token collisions can happen if contextual delimiters are not strictly enforced.

Group Token Functional Domain Permitted Syntactic Values Erroneous /WX Cross-Contamination
/OV Spatial Coordinates / Fix NAVAID radials, DME, airport identifiers (e.g., ORD, MRB090020) [1] Treating NAVAID identifiers or fix offsets as weather phenomena.
/WX Meteorological Phenomena FVxxSM, RA, SN, TS, HZ, FG, BR, etc. [1] Canonical target: observed phenomena and flight visibility only.
/TB Mechanical/Convective Turbulence NEG, LGT, MOD, SEV, EXTRM, CAT, CHOP [1], [3] Classifying turbulence severity levels as weather descriptors.
/IC Airframe Icing Accretion NEG, LGT, MOD, SEV, RIME, CLR, MX [1], [3] Confusing structural icing type/intensity with precipitation fields.

Consider the following complete pilot report:

UUA /OV KOKC180040/TM 1930/FL080/TP C172/WX FV02SM +RA FG/TB MOD/IC LGT RIME/RM DURD

A manual or algorithmic parser must systematically extract the constituent groups based on their structural delimiters:

  1. /OV KOKC180040: Identifies location 40 nautical miles south (180° radial) of the Oklahoma City VOR [1]. It contains no present weather data.
  2. /WX FV02SM +RA FG: Identifies a flight visibility of 2 statute miles (FV02SM), heavy rain (+RA), and fog (FG) [1].
  3. /TB MOD: Identifies kinematic turbulence as moderate [1], [3]. This value cannot be appended to /WX.
  4. /IC LGT RIME: Identifies structural ice accumulation as light rime [1], [3]. This metric describes aerodynamic structural contamination, not the falling hydrometeor token within /WX.

Automated Parsing Heuristics: An Industry Application

VectorWX (https://vectorwx.app) is a student tool for reading these groups. A parser that does not end /WX at the next slash can attach weather text to a later group [4].

Deterministic parsing models rely on finite state machines (FSM) or rigid regular expressions that enforce explicit lookaheads for subsequent operational tokens (/TB, /IC, /RM). When an aircraft encounters freezing rain, pilots occasionally submit reports such as:

.../WX FZRA/TB MOD/IC MOD...

If a parser lacks strict token isolation, it may erroneously merge the structural icing intensity from /IC MOD with the weather token FZRA, or misinterpret MOD as a turbulence descriptor qualifying the freezing rain itself. Research environments such as VectorWX demonstrate that separating these entities at the lexical analysis layer—before passing the parameters to route-risk evaluation engines—is critical for preventing false negatives in cockpit hazard displays.

Systemic Evolution and Future Standards in Airborne Weather Reporting

The reliance on ASCII-serialized, slash-delimited PIREPs presents technical challenges for next-generation air traffic management. While human observers efficiently identify complex environmental transitions, manual transcription introduces syntax drift, typographical errors, and inconsistent group ordering [1], [3].

Under the auspices of the ICAO and the World Meteorological Organization (WMO), aviation weather infrastructure is shifting from traditional alphanumeric codes (TAC) to digital formats based on the ICAO Meteorological Information Exchange Model (IWXXM). IWXXM uses Extensible Markup Language (XML) and Geography Markup Language (GML) schemas to replace slash-delimited text blocks with strictly validated, semantically unambiguous nodes:

<!-- Conceptual IWXXM Schema Implementation for PIREP Weather Observation -->
<iwxxm:observedProperty>
    <iwxxm:AircraftWeatherObservation>
        <iwxxm:horizontalVisibility uom="SM">2.0</iwxxm:horizontalVisibility>
        <iwxxm:weatherCondition>
            <iwxxm:Phenomenon intensity="HEAVY" descriptor="THUNDERSTORM" precipitation="RAIN"/>
        </iwxxm:weatherCondition>
    </iwxxm:AircraftWeatherObservation>
</iwxxm:observedProperty>

In an IWXXM schema, the parameters traditionally grouped under /WX are isolated into distinct, validated XML tags. Flight visibility is assigned a floating-point value with a defined unit of measure attribute (uom="SM"), eliminating the ambiguity of truncated integers. Meteorological phenomena are structured via hierarchical enumerations, preventing the syntactic bleeding of icing or turbulence data into the weather condition node.

Concurrently, the rise of automated aircraft sensor networks—transmitting automated parameters like Eddy Dissipation Rate (EDR) for turbulence and onboard optical icing detector telemetry—is narrowing the operational scope of the manual PIREP. However, automated aircraft systems cannot yet universally identify multi-layered lithometeors, specific cloud-embedded obscurations, or precise forward visibility limitations.

The reading task is to keep /WX on reported weather and visibility, and to leave turbulence, icing, and location in their own groups. This is student data-reading practice. It does not produce an official report or flight-decision advice. Verify with official sources.

References

  1. https://aviationweather.gov/help/data/
  2. https://aviationweather.gov/help/pirep/
  3. https://www.weather.gov/aviation/
  4. https://vectorwx.app
PIREP WX weather group data reading