Sign in

v1

latestOpenAPI 3.1.02026-07-22162733.8 KB
Flights

File the PIREP

Closes out the flight. The server:

  1. Saves every entry from flight_data (or the legacy flight_log) as ACARS LOG rows.
  2. Recomputes total distance by 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.
  3. Files the PIREP with the supplied landing_rate, fuel_used, flight_time, and any of the optional zfw / block_fuel / block_time / level / route fields.
  4. Appends any comments as pilot comments on the PIREP.
  5. Calls phpVMS's submit() which fires the PirepFiled event, 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.

post/flights/complete

Request body

uuidstring uuid

PIREP ID. Either this or tracking_id is required.

tracking_idstring uuid
landing_ratenumber float

Touchdown rate (feet per minute, negative).

fuel_usednumber float

Total fuel burn, pounds.

flight_timenumber float

Total flight time in decimal hours. Server stores as minutes.

zfwnumber float

Zero-fuel weight in lbs.

block_fuelnumber float

Block fuel in lbs.

block_timenumber float

Block time in decimal hours.

levelnumber float

Cruise flight level (e.g. 360).

Response

PIREP filed and submitted.

pirep_idstring uuid required
flight_numberstring required

Airline code + flight number (e.g. QFA1).

routestring required

<dpt-icao> - <arr-icao> summary.

aircraftstring required

Aircraft name (falls back to registration if unnamed).

aircraft_icaostring required
registrationstring required
airlinestring required
airline_icaostring required

Example response

{
  "flight_number": "QFA1",
  "route": "YSSY - YMML"
}