> For the complete documentation index, see [llms.txt](https://docs.flylogs.com/fcom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flylogs.com/fcom/api-docs/reference/flights.md). # Flights ## Flight status Every flight carries a single `status` field describing where it sits in its lifecycle. It is the only lifecycle field on a flight: the legacy `draft` and `deleted` booleans have been removed from both the database and every API response, and are no longer accepted in requests. | Status | Meaning | | ------------ | ----------------------------------------------------------------------------------------------------------------- | | `DRAFT` | Unconfirmed flight created directly, without a schedule. The default for a newly created flight. | | `SCHEDULED` | Unconfirmed flight created from a schedule booking. | | `DELAYED` | Computed at read time only, never stored: a `SCHEDULED` flight whose scheduled time is more than one hour past. | | `DISPATCHED` | Dispatched through the dispatch/FRAT flow, not yet confirmed. | | `LANDED` | Confirmed flight. Only `LANDED` flights count toward logbooks, aircraft hours, duty records, billing and reports. | | `CANCELED` | Removed while still unconfirmed (was `draft = 1`, `deleted = 1`). | | `DELETED` | Removed after having been confirmed (was `draft = 0`, `deleted = 1`). | Mapping from the old booleans, for clients migrating off them: | Old condition | Equivalent status filter | | --------------------------- | --------------------------------------------------- | | `draft = 0 AND deleted = 0` | `status = LANDED` | | `draft = 1 AND deleted = 0` | `status IN (DRAFT, SCHEDULED, DELAYED, DISPATCHED)` | | `deleted = 0` | `status NOT IN (CANCELED, DELETED)` | | `deleted = 1` | `status IN (CANCELED, DELETED)` | *** ## List Flights `GET` `/flights/load/page:{page}/from:{from}/to:{to}/aircraft:{aircraftId}/pilot:{pilotId}/base:{baseId}/flight_type:{typeId}/.json` Retrieve a paginated list of flight records with optional filters. #### Path Parameters All filter parameters are optional — use empty string to skip a filter. | Parameter | Type | Description | | ------------ | ------ | -------------------------------------------------- | | page | number | Page number (starts at 1) | | from | string | Start date filter (YYYY-MM-DD) | | to | string | End date filter (YYYY-MM-DD) | | aircraft | string | Aircraft ID filter | | pilot | string | Pilot user ID filter | | base | string | Base ID filter | | flight\_type | string | Flight type ID filter | | limit | number | Records per page (optional, default 20, max 20000) | #### Example ``` GET /flights/load/page:1/from:2025-01-01/to:2025-03-31/aircraft:/pilot:/base:/flight_type:/.json ``` #### Response ```json { "flights": [ { "Flight": { "id": "5678", "date": "2025-03-10", "status": "LANDED", "callsign": "EC-ABC", "departure_airport": "LEMD", "landing_airport": "LEBL", "offblocks_time": "08:00:00", "takeoff_time": "08:15:00", "landing_time": "09:15:00", "onblocks_time": "09:25:00", "block_time": "5100", "flight_time": "3600", "rules": "VFR", "landings": "1", "engine_starts": "1", "pax": "2", "oil": "0.5", "fuel": "45", "cargo": "0", "night_flight_time": "0", "ifr_flight_time": "0" }, "Base": { "id": "5", "name": "Madrid Base" }, "Aircraft": { "id": "45", "registration": "EC-ABC", "multiengine": false, "multipilot": false, "simulator": false, "AircraftModel": { "name": "C172", "icao": "C172", "AircraftManufacturer": { "name": "Cessna" } } }, "FlightType": { "id": "1", "name": "Training", "color": "#3498db", "pic_flight_time": "pic", "sic_flight_time": "none", "supervisor_flight_time": "none" }, "Pic": { "id": "123", "user_group_id": "110", "UserDetail": { "name": "John", "surname": "Doe", "id": "123" } }, "Sic": null } ], "paginate": { "page": 1, "current": 1, "count": 156, "prevPage": false, "nextPage": true, "pageCount": 7, "limit": 25 }, "time": "1.23" } ``` #### Pagination | Field | Type | Description | | --------- | ------- | ------------------------------ | | page | number | Requested page | | current | number | Current page | | count | number | Total number of records | | prevPage | boolean | Whether a previous page exists | | nextPage | boolean | Whether a next page exists | | pageCount | number | Total number of pages | | limit | number | Records per page | #### Time Fields Flight times (`block_time`, `flight_time`, `night_flight_time`, `ifr_flight_time`) are returned in **seconds**. #### Timezone The clock fields `offblocks_time`, `takeoff_time`, `landing_time`, `onblocks_time` and the flight `date` are expressed in the company's **flight timezone**. This is `CompanySetting.flight_timezone_id` when set, otherwise the company timezone (`CompanyDetail.timezone_id`) — see [Company Settings](/fcom/api-docs/reference/company.md). This applies both to the times returned here and to the wall-clock times you submit when creating or editing a flight. Schedules and trainings use the company timezone regardless. *** ## View Flight `GET` `/flights/view/{id}.json` Retrieve full details for a single flight, including crew, airports, audit trail, and permissions. Users with `user_group_id > 170` may only view flights they are involved in (creator, PIC, SIC, supervisor, or owner of the aircraft). Otherwise returns `403 Forbidden`. #### Path Parameters | Parameter | Type | Description | | --------- | ------ | ----------- | | id | string | Flight ID | #### Response ```json { "flight": { "Flight": { "id": "5678", "date": "2025-03-10", "status": "LANDED", "callsign": "EC-ABC", "departure_airport": "LEMD", "landing_airport": "LEBL", "offblocks_time": "08:00:00", "takeoff_time": "08:15:00", "landing_time": "09:15:00", "onblocks_time": "09:25:00", "block_time": "5100", "flight_time": "3600", "night_flight_time": "0", "ifr_flight_time": "0", "rules": "VFR", "crosscountry": true, "multiengine": false, "landings": "1", "fuel": "45.5", "oil": null, "pax": "1", "cargo": null, "route": "LEMD DCT LEBL", "remarks": "", "pf": "PIC", "pic_id": "123", "sic_id": null }, "Base": { "id": "5", "name": "Madrid Base", "airport_id": "100" }, "Aircraft": { "id": "45", "registration": "EC-ABC", "photo": "https://...", "adsb": "ABC123", "multipilot": false, "active": true, "AircraftModel": { "name": "C172", "icao": "C172", "AircraftManufacturer": { "name": "Cessna" } }, "hours": "12500", "landings": "8900" }, "FlightType": { "id": "1", "name": "Training", "color": "#3498db", "description": "Training flights" }, "Pic": { "id": "123", "active": true, "pilot": true, "deleted": false, "user_group_id": "110", "UserGroup": { "role": "pilot", "name": "Pilot" }, "UserDetail": { "name": "John", "surname": "Doe", "photo": null, "id": "123" } }, "Sic": null, "DepartureAirport": { "id": "100", "name": "Adolfo Suárez Madrid–Barajas", "lat": "40.4719", "lon": "-3.5626" }, "LandingAirport": { "id": "101", "name": "Josep Tarradellas Barcelona–El Prat", "lat": "41.2971", "lon": "2.0785" }, "FlightChange": [ { "id": "890", "flight_id": "5678", "user_id": "123", "action": "created", "fields": null, "comments": null, "created": "2025-03-10 09:30:00", "User": { "id": "123", "UserDetail": { "name": "John", "surname": "Doe", "id": "123" }, "UserGroup": { "role": "pilot" } } } ], "Upload": [], "SafetyReport": [] }, "distance": 267, "canConfirm": true, "canEdit": true, "canCreate": true, "canDelete": true, "changeNames": { "created": { "icon": "fa-plus", "name": "Created", "class": "text-success" }, "confirmed": { "icon": "fa-check", "name": "Confirmed", "class": "text-primary" }, "edited": { "icon": "fa-pencil", "name": "Edited", "class": "text-warning" } } } ``` #### Permission Flags | Field | Type | Description | | ---------- | ------- | ------------------------------------ | | canConfirm | boolean | User can confirm/approve this flight | | canEdit | boolean | User can edit this flight | | canCreate | boolean | User can create new flights | | canDelete | boolean | User can delete this flight | *** ## Cancel Flight `POST` `/flights/cancel.json` Cancel (soft-delete) a flight record. The flight moves to `CANCELED` if it was still unconfirmed, or to `DELETED` if it had already been confirmed (`LANDED`), and a `cancel` entry is added to its change history. There is **no date restriction** — a flight can be cancelled at any time, including flights dated in the past. #### Request Body | Field | Type | Required | Description | | ------ | ------ | -------- | ----------------------------------------------------------------------------- | | id | string | Yes | Flight ID to cancel | | reason | string | Yes | Reason for cancellation | | text | string | No | Free-text note stored with the cancellation | | notify | string | No | `"true"` to notify the other crew (in-app message + WhatsApp where available) | #### Authorization The caller must satisfy **at least one** of the following, otherwise the request returns `400 Not authorized`: * Has the **Flight.create**, **Flight.edit**, or **Flight.confirm** company permission, or * Is a crew member of the flight — the **PIC** (`pic_id`), **SIC** (`sic_id`), or **Supervisor** (`supervisor_id`), or * Is the user who created the flight (`user_id`). Company Administrators, Operations Managers, and Compliance & Safety Managers hold these permissions by default. Note that the front-end only surfaces the Cancel action for unconfirmed flights; the endpoint itself does not restrict by status. *** ## Confirm Flight `POST` `/flights/confirm/{id}.json` Confirm an unconfirmed flight (moves it to `status = LANDED`, updates aircraft books, billing, and duty records). The flight must already have a block time, aircraft, and PIC. Requires the **Flight.confirm** company permission; when `require_flight_password` is enabled on the company, a `pass` field with the caller's password is also required. #### Overlap check Confirmation is blocked when the flight's block times overlap another **confirmed** (`status = LANDED`) flight on the **same aircraft**. The response is `400` with the usual `message`, plus a **`conflicts`** array naming the blocking flight(s) so a client can link to them: ```json { "code": 400, "message": "The selected date and time are already occupied by another flight for this aircraft.", "url": "/flights/confirm/9a1b....json", "conflicts": [ { "id": "9c2d3e4f-....", "callsign": "IBE123", "date": "2026-07-22", "offblocks_time": 1753180200, "onblocks_time": 1753185600, "link": "/flights/view/9c2d3e4f-...." } ] } ``` | Field | Type | Description | | ---------------- | -------------- | ----------------------------------------------------------------------------------------------------- | | `id` | string | Blocking flight ID | | `callsign` | string \| null | Blocking flight callsign, when set | | `date` | string | Flight date (`YYYY-MM-DD`) | | `offblocks_time` | integer | Off-blocks time, unix seconds | | `onblocks_time` | integer | On-blocks time, unix seconds | | `link` | string \| null | Relative URL to the flight — populated only for flights in the caller's own company; `null` otherwise | > The `conflicts` field is additive: clients that don't read it see the same `message`/`code` as before. Up to 20 blocking flights are returned, ordered by off-blocks time. *** ## Dispatch Flight `POST` `/flights/dispatch/{id}.json` Dispatches an existing `DRAFT` or `SCHEDULED` flight directly — the direct-dispatch counterpart to [Dispatch Schedule](/fcom/api-docs/reference/schedules.md#dispatch-schedule), used when the flight record already exists rather than being created from a schedule. On success the flight moves to status `DISPATCHED`, a `FlightChange` history row is recorded, and a linked schedule (if any) has its departure/destination synced to match. #### Path Parameters | Parameter | Type | Description | | --------- | ------ | ----------------------- | | id | string | Flight UUID to dispatch | #### Authorization The caller must satisfy **at least one** of: the **Flight.create** or **Flight.edit** company permission, or be a crew member of the flight (`user_id`, `pic_id`, `sic_id`, or `supervisor_id`) — otherwise `400 Not authorized`. The flight must currently be `DRAFT` or `SCHEDULED`, otherwise the call returns `result: false` with `"Only draft or scheduled flights can be dispatched."`. #### MEL/CDL hard block Exactly the same gate as [Dispatch Schedule](/fcom/api-docs/reference/schedules.md#dispatch-schedule): an **expired** MEL or CDL item on the flight's aircraft rejects the dispatch outright. ```json { "result": false, "message": "ATA 32 blocks dispatch — MEL Category C expired." } ``` #### Other preconditions Checked in order, each returning `result: false` with its own message when it fails: | Condition | Message | | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | FRAT required (`schedule_dispatch_frat` on, dispatcher is crew) and not completed | "A completed Flight Risk Assessment (FRAT) is required to dispatch this flight." | | Non-school company and no `pax` posted | "Number of passengers (PAX) is required to dispatch this flight." | | Departure or destination missing (neither already on the flight nor posted) | "Departure and destination airports are required to dispatch this flight." | #### Request Body | Parameter | Type | Required | Description | | ----------------------------------- | ------ | ----------- | ------------------------------------------------------------------------------------------------ | | departure\_airport | string | conditional | Required if the flight has no departure airport yet | | landing\_airport | string | conditional | Required if the flight has no destination airport yet | | pax | number | conditional | Required for non-school companies | | pob | number | no | Persons on board | | endurance | string | no | Fuel endurance | | alternate\_airport | string | no | Alternate airport | | frat\_score, frat\_band, frat\_data | — | conditional | Same FRAT fields as [Dispatch Schedule](/fcom/api-docs/reference/schedules.md#dispatch-schedule) | #### Response ```json { "result": true, "flight": { "Flight": { "id": "...", "status": "DISPATCHED" } } } ``` *** ## Export Flights (XLS) The server-side `xls:1` export has been removed. The logbook Excel file is now generated client-side by the NEO web app: it pulls the flights from the **List Flights** endpoint above (using the `limit` parameter to fetch all matching rows) and builds the XLSX in the browser. *** ## Flight Types `GET` `/flight_types.json` List all flight types configured for the company. #### Response ```json [ { "id": "1", "name": "Training", "color": "#3498db" }, { "id": "2", "name": "Charter", "color": "#e74c3c" }, { "id": "3", "name": "Private", "color": "#2ecc71" } ] ``` *** ## Bases `GET` `/bases/index.json` List all operational bases. #### Response ```json [ { "id": "5", "name": "Madrid Base", "airport_id": "100" }, { "id": "6", "name": "Barcelona Base", "airport_id": "101" } ] ```