Flight Planning API
Hierarchy: Mission → Flight Plan → Flight Session → Telemetry
A Flight Plan is the precise operative unit under a Mission. It binds one asset, one pilot, a schedule window inside the mission, and a geographic envelope stored in the Constraint Engine.
Access:
org_type= Asset Owner for create, update, and delete (Admin+) and reads (Member+). Airspace Managers (Member+) can read plans that fall within zones they own or hold a Manager or Monitor membership for. See Access control.
Endpoints
| Endpoint | Method | Description |
|---|---|---|
/flight-plans?mission_uuid={mission_uuid} | POST | Create a flight plan under a mission |
/flight-plans?mission_uuid={mission_uuid} | GET | List flight plans for a mission |
/flight-plans/{plan_uuid} | GET | Flight plan details |
/flight-plans/{plan_uuid} | PUT | Update a flight plan |
/flight-plans/{plan_uuid} | DELETE | Soft-delete a flight plan (INACTIVE) |
/flight-plans/logs | GET | Combined list of flight plans |
/permissions?parent_type=FLIGHT_PLAN&parent_uuid={plan_uuid} | POST | Manual permission request for a plan (when required) |
/permissions/{permission_uuid} | PUT | Airspace Manager grant or deny |
Header required for most routes: X-Organisation-ID.
Full request and response schemas for create, update, delete, and permission evaluation live in the Mission Planning API flight-plan sections. This page states the flight-plan contract and permission behaviour.
Relationship to missions
- Create the parent mission first (Mission Planning API).
- Schedule windows on the plan must fall within the mission window.
- Zone intersection and auto-approval run at mission creation. Flight plans inherit mission permissions by reference.
- Strategic deconfliction applies only to flight plans: if the plan envelope overlaps an active approved plan in the same time window, intersecting zones on this plan are force-set to
Rejected, shadowing the inherited rows. The plan is still created;permission_summaryreflects rejection.
Canonical rules: Permission Auto-Approval Rules and Strategic Deconfliction.
Execution
After a plan is ready for flight:
- Start a flight session for the asset and plan.
- Stream telemetry per the Telemetry wire contract.
- End the session when the operation completes.