A valid request URL is required to generate request examples{
"pirep_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"flight_number": "QFA1",
"route": "YSSY - YMML",
"aircraft": "<string>",
"aircraft_icao": "<string>",
"registration": "<string>",
"airline": "<string>",
"airline_icao": "<string>"
}{
"error": "tracking_id is required"
}{
"success": false,
"error": "Invalid Token"
}{
"error": "PIREP not found"
}{
"error": "<string>",
"success": true,
"message": "<string>"
}File the PIREP
Closes out the flight. The server:
- Saves every entry from
flight_data(or the legacyflight_log) as ACARS LOG rows. - Recomputes total
distanceby summing great-circle segments between the FLIGHT_PATH rows accumulated during/flights/update. If no FLIGHT_PATH rows exist, the dpt-to-arr great-circle distance is used. - Files the PIREP with the supplied
landing_rate,fuel_used,flight_time, and any of the optionalzfw/block_fuel/block_time/level/routefields. - Appends any
commentsas pilot comments on the PIREP. - Calls phpVMS’s
submit()which fires thePirepFiledevent, handles diversions, and applies rank-based auto-approval.
flight_time is in decimal hours here (the server multiplies by 60 to store minutes). Either uuid or tracking_id may carry the PIREP ID.
A valid request URL is required to generate request examples{
"pirep_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"flight_number": "QFA1",
"route": "YSSY - YMML",
"aircraft": "<string>",
"aircraft_icao": "<string>",
"registration": "<string>",
"airline": "<string>",
"airline_icao": "<string>"
}{
"error": "tracking_id is required"
}{
"success": false,
"error": "Invalid Token"
}{
"error": "PIREP not found"
}{
"error": "<string>",
"success": true,
"message": "<string>"
}Authorizations
The pilot's API key, obtained via POST /pilot/login or your OAuth flow. Send as Authorization: Bearer <api_key> on every authenticated request.
Body
PIREP ID. Either this or tracking_id is required.
Log entries saved as ACARS LOG rows.
Show child attributes
Show child attributes
Legacy field name, used only when flight_data is empty.
Show child attributes
Show child attributes
Custom PIREP fields keyed by slug, written to pirep_field_values (source ACARS). Sent only when Where PIREP fields go (on Flight Tracking's Additional fields tab in Console) is set to Nested: it carries every additional field ticked under PIREP plus simulator_version. With Top level the same fields arrive as flat top-level keys instead, which this endpoint ignores.
Show child attributes
Show child attributes
Touchdown rate (feet per minute, negative).
Total fuel burn, pounds.
Total flight time in decimal hours. Server stores as minutes.
Zero-fuel weight in lbs.
Block fuel in lbs.
Block time in decimal hours.
Cruise flight level (e.g. 360).
Route. If sent as an array, the server joins on spaces. Omit to preserve the route prefiled at /flights/start.
Pilot comments to attach to the filed PIREP.
Pilot comment to attach to the PIREP. The server picks the first non-empty value from event, text, comment (in that order) if an object is supplied.
Response
PIREP filed and submitted.
Airline code + flight number (e.g. QFA1).
"QFA1"
<dpt-icao> - <arr-icao> summary.
"YSSY - YMML"
Aircraft name (falls back to registration if unnamed).
Was this page helpful?