Skip to main content
By the end of this guide, you will have created an eAPIS manifest for a trip, auto-populated it from the crew and passenger records already on the trip, validated it, and submitted (or exported) it to US Customs and Border Protection.
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.
Who should read this: Dispatchers and trip coordinators on international flights. You need the flights.read and flights.update ops permissions. eAPIS manifests must be submitted at least 60 minutes before departure for all private and charter flights departing from or arriving in the United States.

​
What is eAPIS?

The Electronic Advance Passenger Information System (eAPIS) is a US Customs and Border Protection (CBP) requirement. Under 19 CFR 122.49a and 19 CFR 122.49b, operators of private and charter aircraft must transmit an electronic manifest of all persons on board to CBP before international departures from and arrivals into the United States. The filing must be transmitted:
  • Departures: At least 60 minutes before wheels-up
  • Arrivals: At least 60 minutes before landing at a US airport
PlaneConnection generates a CBP-compliant XML manifest and tracks submission status for each international leg.

​
Prerequisites

  • The trip must involve an international departure from or arrival into the United States.
  • Configure your CBP credentials under Ops > Settings > eAPIS before attempting electronic submission.
  • Passports for all crew and passengers should be entered on their profiles before running auto-populate.

​
Navigate to the eAPIS page

  1. Open the trip from Ops > Trips or the Dispatch Board.
  2. Click the eAPIS tab in the trip navigation.
The page displays any previous submissions for this trip and a button to create or update the manifest.

​
Create and submit an eAPIS manifest

1
Step 1: Auto-populate the manifest
2
Click Auto-Populate to import crew and passenger data from the trip assignment. PlaneConnection pulls:
3
  • First name, last name, and date of birth
  • Nationality and country of birth
  • Passport number, issuing country, and expiry date
  • Crew roles (PIC, SIC, Flight Attendant)
    • 4
    Each person row shows a completeness indicator — Complete (green), Partial (amber), or Missing (red) — so you can see at a glance which records need attention.
    5
    Step 2: Review and complete each person
    6
    Click any person row to expand it for editing. Required fields for all persons:
    7
    FieldDescriptionFirst name, Last nameMust match the travel document exactlyDate of birthYYYY-MM-DD formatGenderM or FCountry of birthISO 3166-1 alpha-2 codeCountry of citizenshipISO 3166-1 alpha-2 codeCountry of residenceISO 3166-1 alpha-2 codeDocument typePassport, Passport Card, or equivalentDocument numberAs printed on the travel documentDocument issuing countryISO 3166-1 alpha-2 codeDocument expiry dateMust be future-dated
    8
    For crew members, also set the Crew Status (crew or non-crew) and Position (PIC, SIC, FA, etc.).
    9
    For US citizens, country of citizenship, birth, and residence are typically all US. For NEXUS/Global Entry members, the Passport Card option may be accepted.
    10
    Step 3: Validate the manifest
    11
    Click Validate. PlaneConnection checks:
    12
  • All required fields are present
  • Document expiry dates are in the future
  • Country codes are valid ISO values
  • At least one person is marked as crew
    • 13
    Validation errors are shown per-person. Fix all errors before proceeding — CBP will reject incomplete manifests.
    14
    Step 4: Generate the XML
    15
    Click Generate XML. PlaneConnection builds the CBP-compliant XML manifest and shows a preview. The XML is formatted to the CBP eAPIS specification (19 CFR 122.49b).
    16
    Step 5: Submit to CBP
    17
    Two submission options are available:
    18
    Electronic submission (if configured): Click Submit to eAPIS. PlaneConnection sends the XML to CBP through your configured submission method and records the confirmation number.
    19
    Manual submission: Download the XML using Download XML and upload it directly at the CBP eAPIS portal (eapis.cbp.dhs.gov). After filing, return to PlaneConnection and click Record Submission to enter the confirmation number.
    20
    Step 6: Record confirmation
    21
    After CBP acknowledges receipt, enter the confirmation number on the submission record. PlaneConnection marks the manifest as Confirmed and timestamps the submission.

    ​
    Submission statuses

    StatusMeaning
    DraftManifest created or partially populated; not yet validated.
    ReadyValidated and ready to submit to CBP.
    SubmittedManifest transmitted; awaiting CBP acknowledgment.
    ConfirmedCBP acknowledged receipt. Confirmation number stored.
    RejectedCBP rejected the manifest. See rejection reason and amend before resubmitting.
    AmendedA previously submitted manifest has been updated and resubmitted.

    ​
    Amend a submitted manifest

    If crew or passenger details change after submission, or if CBP requests corrections:
    1. Open the existing submission from the eAPIS tab.
    2. Make the necessary corrections.
    3. Click Validate, then Generate XML.
    4. Submit the amended manifest. PlaneConnection records the amendment and preserves the original submission in the audit trail.
    CBP must receive the amended manifest at least 60 minutes before departure. If the amendment is filed after that deadline, contact the destination Port Director for guidance.

    ​
    Configure eAPIS settings

    Go to Ops > Settings > eAPIS to configure:
    • CBP credentials — Required for electronic submission
    • Default departure and arrival airports — Pre-populates new manifests
    • FlashPass integration — Alternative third-party eAPIS filing service

    ​
    Auto-populate aircraft data

    For recurring international routes, PlaneConnection pre-fills aircraft details (tail number, aircraft type, color, operator name, and certificate number) from the aircraft record. Verify these fields are complete on the aircraft detail page under Ops > Aircraft to avoid manual entry on each filing.

    ​
    Regulatory reference

    RegulationRequirement
    19 CFR 122.49aElectronic manifest for private aircraft entering or departing the US
    19 CFR 122.49bTransmission requirements — 60 minutes before departure or arrival
    CBP eAPIS portaleapis.cbp.dhs.gov
    Failure to file eAPIS at least 60 minutes before departure may result in civil penalties from CBP. In some cases, CBP may also prevent the flight from departing or deny entry at the destination.

    CARECOM Filing

    File advance passenger information for CARICOM member state destinations.

    Canada CBSA Filing

    Submit advance notification for flights arriving in Canada.

    Create a Trip

    Add crew, passengers, and legs before filing international manifests.

    Manage Passengers

    Ensure passport data is complete on passenger profiles for auto-populate.
    Last modified on April 11, 2026