Status Summary
| Status | Database Value | Description |
|---|---|---|
| Draft | draft | Trip has been created but not yet confirmed. |
| Confirmed | confirmed | Trip has been confirmed and is on the schedule. |
| Active | active | Trip is currently in progress. |
| Completed | completed | Trip has been completed. |
| Cancelled | cancelled | Trip has been cancelled and will not take place. |
Status Lifecycle
Detailed Status Definitions
Draft
The trip has been created in the system with preliminary information. Required fields such as aircraft assignment, crew assignment, route, and schedule may be incomplete. Draft trips do not appear on the active flight schedule. Dispatch availability: Not dispatched. Does not affect aircraft or crew availability calculations.Confirmed
The trip has been reviewed and confirmed by a dispatcher or authorized user. All required fields — aircraft, crew, route, departure time, and passenger manifest (if applicable) — have been populated and validated. Confirmed trips appear on the active flight schedule. Dispatch availability: The assigned aircraft and crew are marked as committed for the trip’s time window. Scheduling conflicts are flagged.Active
The trip is currently in progress. This status is set when the aircraft departs for the first leg of the trip. Active trips are monitored in the dispatch view. Dispatch availability: The assigned aircraft and crew are unavailable for other assignments.Completed
The trip has been completed. All legs have been flown and the aircraft has arrived at the final destination. Post-flight data (actual times, fuel burn, discrepancies) can be recorded against completed trips. Dispatch availability: The assigned aircraft and crew are released and available for new assignments.Cancelled
The trip has been cancelled and will not take place. A cancellation reason is recorded. Cancelled trips are retained in the system for record-keeping but are excluded from active scheduling views. Dispatch availability: The assigned aircraft and crew are released. Any scheduling blocks are removed.Status Transition Rules
| From | To | Permitted Roles | Conditions |
|---|---|---|---|
| Draft | Confirmed | Dispatcher, admin | Aircraft, crew, and route assigned |
| Draft | Cancelled | Dispatcher, admin | Cancellation reason required |
| Confirmed | Active | Dispatcher, admin, PIC | Departure time reached or manual activation |
| Confirmed | Cancelled | Dispatcher, admin | Cancellation reason required |
| Active | Completed | Dispatcher, admin, PIC | All legs completed |
Fields
| Field | Type | Description |
|---|---|---|
trip_number | String | Unique trip identifier. |
status | Enum | Current lifecycle status. |
aircraft | Reference | Assigned aircraft. |
crew | Array | Assigned crew members with roles. |
legs | Array | Ordered list of flight legs (origin, destination, times). |
passengers | Array | Passenger manifest. |
requested_by | String | Person or entity that requested the trip. |
cancellation_reason | Text | Reason for cancellation (required if cancelled). |
created_at | Timestamp | Record creation timestamp (UTC). |
updated_at | Timestamp | Last modification timestamp (UTC). |