Skip to main content
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.
You can import multiple trips at once from a CSV file instead of creating each trip manually. This is useful when migrating from another system, importing a season’s schedule, or loading historical trip data.

​
File Format Requirements

PlaneConnection accepts CSV files with the following column structure. Column headers must match exactly (case-insensitive).
ColumnRequiredFormatDescription
trip_numberNoStringCustom trip number. If omitted, the system auto-generates one.
originYesICAO codeDeparture airport (e.g., KTEB).
destinationYesICAO codeArrival airport (e.g., KPBI).
departure_dateYesYYYY-MM-DDDeparture date in ISO format.
departure_timeNoHH:MMDeparture time in 24-hour UTC format.
arrival_dateNoYYYY-MM-DDArrival date in ISO format.
arrival_timeNoHH:MMArrival time in 24-hour UTC format.
trip_typeNoStringOne of: charter, owner, maintenance, positioning, training. Defaults to charter.
aircraftNoStringAircraft tail number (N-number). Must match an aircraft in your fleet.
picNoStringEmail of the Pilot in Command. Must match a crew member in your roster.
sicNoStringEmail of the Second in Command. Must match a crew member in your roster.
passenger_countNoNumberNumber of passengers for the trip.
notesNoStringInternal notes for the trip.
statusNoStringInitial status. Defaults to draft. Allowed values: draft, scheduled.
Download a sample CSV template from the import page to see the exact format and column names expected.

​
Import Workflow

1
Step 1: Prepare your CSV file
2
Create a CSV file with the required columns. Ensure all ICAO codes are valid and dates are in ISO format. If referencing aircraft or crew, verify that the tail numbers and emails exist in your workspace.
3
The CSV file must use UTF-8 encoding. Files with non-UTF-8 characters (common in exports from older systems) may cause validation errors.
4
Step 2: Upload the file
5
Navigate to Ops > All Trips and click Import Trips (or use the actions menu). Select your CSV file and click Upload.
6
Step 3: Map columns
7
If your CSV column headers do not exactly match the expected names, the system displays a column mapping screen. Map each source column to the corresponding PlaneConnection field. Unmapped columns are ignored.
8
Step 4: Review validation results
9
The system validates every row before importing. The validation summary shows:
10
  • Valid rows — ready to import.
  • Warnings — rows that will import but have potential issues (e.g., aircraft not found, crew not matched).
  • Errors — rows that cannot be imported (e.g., missing required fields, invalid ICAO codes, invalid dates).
    • 11
    Review and correct any errors in your source file, then re-upload if needed.
    12
    Step 5: Confirm and import
    13
    Click Import to create the trips. All imported trips are created in the specified status (default: draft). A summary shows the number of trips created, warnings encountered, and any rows that were skipped.

    ​
    Validation and Error Handling

    The import process validates the following before creating trips:
    ValidationRuleError Behavior
    Required fieldsorigin and destination must be presentRow rejected
    ICAO codesAirport codes must exist in the airport databaseWarning (trip created without validated airport)
    Date formatDates must be valid ISO 8601 (YYYY-MM-DD)Row rejected
    Aircraft matchTail number must match an Active aircraft in your fleetWarning (trip created without aircraft assignment)
    Crew matchEmail must match a crew member in your workspaceWarning (trip created without crew assignment)
    Duplicate detectionTrips with the same origin, destination, and departure date/time are flaggedWarning (trip still created)
    Trip number uniquenessIf provided, trip_number must not already exist in the workspaceRow rejected
    Rows with warnings are still imported — the system creates the trip without the unmatched reference (aircraft, crew). You can assign these manually after import from the trip detail page.

    ​
    Bulk Import Best Practices

    Import 5-10 trips first to verify your CSV format and column mapping. Review the results before importing a full season or historical dataset.
    Import trips with status set to draft (the default). This gives dispatchers a chance to review, assign aircraft and crew, and confirm each trip individually.
    Cross-reference your airport codes against the PlaneConnection airport database. Common issues include using IATA codes (e.g., TEB instead of KTEB) or codes for airports not in the system.
    Each row in the CSV creates a single-leg trip. For multi-leg trips, import each leg as a separate row with the same trip_number. The system groups legs under the same trip when they share a trip number.
    When importing historical trips, set the status to completed only if the trip has already been flown. Include actual departure and arrival times for accurate historical reporting.

    Create a Trip

    Create trips manually with the trip wizard.

    Trip Statuses

    Understanding trip lifecycle statuses after import.

    Manage Aircraft

    Ensure aircraft records exist before importing trips with aircraft assignments.

    Manage Crew

    Set up crew members before importing trips with crew assignments.
    Last modified on April 11, 2026