Begin tracking a booked flight
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:
- SimBrief-attached aircraft (if the pilot has a SimBrief OFP for this flight)
- The bid’s
aircraft_id(if the bid was made against a specific airframe) - The first available aircraft from the flight’s subfleets
If none can be resolved, the server returns 500 with "No aircraft attached to bid".
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
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.
PIREP UUID. Send this back as uuid or tracking_id on /flights/update, /flights/complete, and /flights/cancel.