> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Create a Trip

> Step-by-step guide to creating a trip using the multi-step wizard with route selection, aircraft and crew assignment, and cost estimation.

By the end of this guide, you will have a fully configured trip -- with route, aircraft, crew, and passengers -- on your dispatch schedule and ready to progress through the pipeline.

<Info>
  The Operations module must be enabled for your workspace. You also need the appropriate operations
  permissions. Contact your workspace administrator if you cannot access these features.
</Info>

<Info>
  You need the `flights.create` permission (granted to Dispatcher, Admin, Director of Operations,
  Chief Pilot, Sole Proprietor, and Account Owner roles). Before you begin, ensure at least one
  aircraft is in Active status and crew members have current qualifications.
</Info>

<Steps>
  ### Step 1: Open the new trip form

  Go to **Ops > All Trips** and click **New Trip**.

  If you are starting from a customer or owner request, open the request first and click **Review & Create Trip**. The trip wizard opens with the route and timing pre-filled.

  <Tip>
    Press `Cmd+K` (or `Ctrl+K` on Windows) and type **New Trip** to jump straight to the form.
  </Tip>

  ### Step 2: Define the route and schedule

  1. Choose the **Trip Type** (Charter, Owner, Maintenance, Positioning, or Training).
  2. Set the **Departure Date/Time**.
  3. Enter the **Origin** and **Destination** ICAO codes (e.g., `KTEB`, `KPBI`). The field autocompletes by code or airport name.

  If you need multiple legs, click **Add Leg** to add origin/destination/time fields for each additional segment.

  ### Step 3: Assign aircraft and crew

  Select an aircraft from the fleet dropdown when you are ready. Only aircraft in **Active** status appear.

  <Warning>
    If the aircraft has a scheduling conflict (double-booking or maintenance window), a conflict alert
    appears. Conflicts block confirmation -- resolve them before moving the trip to Confirmed status.
  </Warning>

  Assign crew to operational roles:

  1. **PIC** -- Select from eligible pilots. The system validates type rating, medical currency, and duty time.
  2. **SIC** -- Optionally select a second pilot (same validations apply).
  3. **Flight Attendant** -- Optionally assign cabin crew.

  <Note>
    Aircraft and crew assignment is optional during creation. You can assign or reassign later from
    the trip detail page. You can also add crew and aircraft from inline quick-add modals without
    leaving the wizard.
  </Note>

  ### Step 4: Build the passenger manifest

  Search for passengers in your directory and move them to the assigned list when the manifest is ready. If you need to add a new passenger, click **Add New Passenger** to create one inline.

  Enter catering requests, ground transportation, or special instructions in the **Special Requests** field.

  ### Step 5: Review and submit

  Review the readiness panel showing route, aircraft, crew, passengers, cost estimate, and conflict check results.

  * If details are still tentative, click **Save as Draft**. The trip is created with status **Draft** and you can complete aircraft, crew, passenger, and estimate details later.
  * If everything passes validation with no conflicts, click **Confirm Trip**. The trip is created with status **Confirmed**.

  The trip receives a unique number (e.g., `TRP-2026-0142`) and you land on the trip detail page.
</Steps>

## After creation

From the trip detail page you can:

* **Edit** trip details or reassign resources from the edit tab.
* **Advance status** through the pipeline: Confirmed, Scheduled, Planned, Released, Dispatched.
* **Release** a confirmed trip to send the flight release checklist to crew.
* **Duplicate**, **Cancel**, or **Delete** from the actions menu.

### Trip lifecycle after creation

Trips created in Draft status follow this progression through the dispatch pipeline:

1. **Draft** -- initial state, details can be freely edited
2. **Confirmed** -- aircraft and crew validated, resources committed
3. **Scheduled** -- placed on the operations schedule
4. **Planned** -- route and resource planning finalized
5. **Released** -- flight release issued to crew
6. **Dispatched** -- crew acknowledged, departure imminent
7. **Active** -- in flight
8. **Close-out** -- all legs landed, post-flight paperwork
9. **Completed** -- finalized (terminal state)

For charter trips, the flow may include **Quoted** (quote sent to client) and **Requested** (client approves or submits request) stages before Confirmed. See [Trip Statuses](/en/reference/trip-statuses) for the full state machine and transition rules.

<Tip>
  Use the [Dispatch Board](/en/how-to/ops/use-dispatch-board) to monitor trip status across your
  fleet after creation.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Trip Statuses" href="/reference/trip-statuses">
    Lifecycle statuses, transition rules, and conflict detection.
  </Card>

  <Card title="Manage Aircraft" href="/how-to/ops/manage-aircraft">
    Add and configure aircraft before assigning to trips.
  </Card>

  <Card title="Manage Crew" href="/how-to/ops/manage-crew">
    Set up crew profiles and qualifications for trip assignment.
  </Card>

  <Card title="Use the Dispatch Board" href="/how-to/ops/use-dispatch-board">
    Monitor trip and fleet status in real time.
  </Card>
</CardGroup>