Help centre · For airline staff

Custom fields on pilots, routes and PIREPs

Custom fields let your airline keep its own details on pilots, routes and PIREPs: a Discord name on each pilot, an SOP version or cargo type on a route, the pushback time on a PIREP.

Set them up

Switch on Custom fields under Staff → Airline settings → Optional features, then open Staff → Airline settings → Custom fields. For each field choose:

• Name: what pilots and staff see (up to 60 characters).
• Answer: text, a number, yes or no, or a choice from a list (one option per line).
• Filled in by: the pilot (staff can always change it too) or staff only. Route fields are always filled in by staff.
• Shown to: pilots and staff, or staff only.
• Required: it has to be filled in where it's entered.

You can have up to 20 fields each on pilots, routes and PIREPs. Use the arrows to change the order.

Switch off hides a field everywhere and keeps what was filled in, so you can switch it back on later. Delete removes it; a field that already has values is deleted only when you tick "Also delete its values".

Where they're filled in and shown

• Pilots: pilots fill in theirs on their own pilot page (Airline → Roster → their name). Staff see and change every field on the pilot's page under Staff → Pilots. Fields shown to pilots appear on the pilot's page for everyone at the airline.
• Routes: staff fill them in on the route's edit page. Pilots see the ones shown to them on the booking page and on their booked flight.
• PIREPs: pilots fill in theirs on the manual PIREP and claim forms, and on the PIREP's page after an ACARS flight, until staff have decided it. Staff see and change every field on the PIREP's page.

Exports and the API

The pilots and PIREPs CSV files (the pilot list download and the owner's export) have one extra column per field. The routes' fields and values are in the airline's setup file (Import & export), and are added when that file is imported into an airline that has Custom fields on.

The Operations API adds custom_fields (each field's name and value) to pilots, routes and PIREPs. It holds only the fields shown to pilots, because the key is often used on a public website or by a bot.