SubmitPirep Web Service Example

PIREPs are used to add additional information to briefings when a pilot calls 1800wxbrief, they use the Leidos Flight Service Website, or you submit a web service for a briefing.  Below is an example of a PIREP web service call:


/usr/bin/curl -k -A "Mozilla/5.0" -i --header "Authorization: Basic bWVAbGV0bWVpbi5jb206TXlQYXNzdzByZCE=" --data "aircraftIdentifier=TTTDEMO&pirepLocation1=SEA&pirepLocation1LatLong=4760N12233W&pirepTime=2023-03-06T16%3A36%3A00.000Z&flightLevel=50&aircraftType=A2&skyCover=OVC100&visibility=FU010&airTemperature=50&windsAloft=10050&turbulence=SEV%20001&icing=CLR&nearestReportingStation=MIA&filingTime=2023-03-06T16%3A36%3A00.000Z" "https://[Operational or Test Environment URL]/rest/util/submitPirep" -v

PIREP Fields

*Please note that the following is a description of the fields in the submitPirep web service. For complete information, see the WSDL here: https://ffspelabs.leidos.com/Website2/resources/doc/WebService.xml.

Leidos Web Service FieldField in Message to FAA (example)

Required or Optional

Notes
pirepLocation1/OV KPIE
/OV BAL
/OV BLD320050
/OV 3110N08151W		Required

The location can be an airport, NAVAID, FRD, or lat/long.

Lat/Long Conversion:

  • The lat/long will be converted to the nearest fix in FRD format (BLD320050) before transmission to WMSCR.

  • If the lat/long is over ocean/sea, it will be transmitted as an actual lat/long.

Lat/Long Format:

  • Example: 4158N08753W
  • The latitude must be 4 digits
  • The longitude must be 5 digits
  • The direction is required
  • Do not separate with "/"
pirepLocation2
OptionalIf included, this field allows a 2-point PIREP to be submitted.
pirepTime/TM 1059Required
flightLevel/FL 025RequiredAllowable range: 000-999
aircraftType/TP C172Required
skyCover/SK SCT-BKN04* Optional
visibility/WX FV05SM FG* Optional
airTemperature/TA 16* Optional
windsAloft/WV 225017KT* Optional
turbulence/TB MOD-SE* Optional
icing/IC MOD RM* Optional
remarks/RM <remarks>OptionalIf desired, can include the name of the company or application submitting the PIREP.
filingTime
Required


* Optional: Note that all of the weather condition parameters are optional.  However, at least one of the following weather phenomenon elements must be provided for the web service call to validate:

PIREP Data Flow in Live Operations

  1. The vendor submits a pilot report via the SubmitPIREP web service.
  2. Leidos Flight Service receives the request and encodes the PIREP as either hazardous (urgent - UUA) or non-hazardous (routine - UA).
  3. Leidos Flight Service submits a message to the FAA NAS (WMSCR) which sends it to NOAA IPSM.
  4. The PIREPs are displayed at the NOAA Aviation Weather Center (AWC): https://www.aviationweather.gov/airep.
  5. NOAA IPSM sends ALL PIREPs to us as weather which is then displayed on the Flight Service Map and included in weather briefings applicable to the PIREP location. If the PIREP submission is accepted, it will be typically be displayed on our map within a minute.
  6. Leidos Flight Service retains PIREPs for one hour.

Urgent PIREPs

PIREPs are classified as either hazardous (urgent - UUA) or non-hazardous (routine - UA).

When Leidos receives a submitPirep web service, the PIREP is encoded as urgent (UUA) if any of the following conditions are present:

Limitation of Testing in the Flight Service Lab

Sending PIREP Web Service Requests to Leidos Flight Service

Configure the NOAA National Weather Service Aviation Weather Center (AWC) to match the Leidos Flight Service PIREP display in Live Operations


Leidos Flight Service website (operations)

NOAA National Weather Service Aviation Weather Center (AWC):