Flight Plan
A Flight Plan defines the operational parameters for a single planned flight within a Mission. It binds one asset and one pilot to a schedule window and a geographic envelope stored in the Constraint Engine.
Role in the platform
Flight plans are the precise unit for strategic deconfliction and for starting flight sessions. They inherit Permission rows from the parent mission by reference. They do not independently invent a second zone-approval pass, except where strategic deconfliction shadows inherited rows when envelopes conflict.
Core fields
| Field | Description |
|---|---|
plan_uuid / plan_udai_id | Public identifiers |
mission_uuid | Parent mission |
org_uuid | Operations owner organisation |
asset_uuid | Assigned aircraft |
user_uuid | Assigned pilot |
payload_id / payload_type | Payload reference for the plan |
schedule_start_time / schedule_end_time | Window within the mission |
constraint_uuid | Plan envelope in the Constraint Engine |
min_height / max_height | Altitude bounds in metres AGL |
airspace_restrictions_covered | Overlapping zone UUIDs |
permissions | Inherited permission references; may be shadowed by deconfliction |
flight_status / status | Plan and record lifecycle (see Enums) |
Related APIs
Last updated on