SKskyvexsoftware
Flights

Begin tracking a booked flight

Changed on

Prefiles a PIREP for the chosen bid and returns a tracking_id (the new PIREP's UUID) that subsequent /flights/update and /flights/complete calls reference.

If bid_id is omitted, the phpVMS reference implementation falls back to the pilot's most recent bid. This exists for older client builds that send an empty body. New integrations should always send bid_id.

Aircraft selection priority on the server:

  1. SimBrief-attached aircraft (if the pilot has a SimBrief OFP for this flight)
  2. The bid's aircraft_id (if the bid was made against a specific airframe)
  3. The first available aircraft from the flight's subfleets

If none can be resolved, the server returns 500 with "No aircraft attached to bid".

post/flights/start

Request

Request body

bid_idinteger

Bid to start flying. Omit to fall back to the pilot's most recent bid (legacy behaviour).

Response

PIREP prefiled. Use tracking_id on subsequent flight calls.

tracking_idstring uuid required

PIREP UUID. Send this back as uuid or tracking_id on /flights/update, /flights/complete, and /flights/cancel.

confirmationstring

Optional message shown to the pilot in a confirmation dialog before tracking starts (e.g. flagging a simulator setup mismatch). When present, the client blocks the start until the pilot either acknowledges via "Start tracking anyway" (subject to override permission) or re-validates and retries.

can_overrideboolean

Optional per-start override flag, only meaningful alongside confirmation. Takes priority over the airline's Allow Start Override setting for the confirmation dialog: true always lets the pilot "Start tracking anyway"; false always disables the button. Omit to fall back to the airline setting.

Changes

  • 51e47958ed25Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status