Submitting passenger and crew data for flights into, out of, within, or over the United States is mandatory for commercial airlines and heavy charter operators. Navigating complex TSA and CBP mandates can quickly become an operational bottleneck. PnrGo helps commercial operators easily meet U.S. compliance requirements. While our automation simplifies data reporting, understanding some regulatory nuances can prevent common operational mishaps.
Launching and maintaining commercial air operations in the United States requires navigating a dense web of security and customs regulations. For scheduled and charter airlines, American compliance frameworks leave no room for manual oversight or technical error.
In this article, we examine the passenger and crew data regulatory landscape for larger carriers operating under:
- Part 121: U.S. scheduled commercial air carriers,
- Part 129: Foreign commercial air carriers conducting scheduled or charter (*) operations into, out of, or over U.S. territory.
|
(*) Operating a light charter fleet or corporate business jet under Part 91 or Part 135 / 129? Do you operate under Part 125? |
Why U.S. compliance is a maze for airlines
When it comes to PAX and CREW data compliance, commercial carriers operating in the U.S. airspace must satisfy two separate federal authorities: the Customs and Border Protection (CBP) and the Transportation Security Administration (TSA).
| Because U.S. regulatory requirements may be subject to interpretation and enforcement discretion, confirming specific obligations directly with the TSA and CBP is always recommended. |
Before launching commercial flights in the U.S., carriers face a demanding administrative and technical onboarding process involving multiple federal agencies:
- FAA approvals: Obtaining Safety Authority from the Federal Aviation Administration (the process differs slightly for Part 121 and Part 129 operators).
- OST approvals: Securing Economic Authority from the Office of the Secretary of Transportation (the process differs slightly for Part 121 and Part 129 operators).
- U.S. legal representation: Having a U.S.-based agent to receive official and legal process notices.
- TSA security programs: Establishing an accepted security plan, including compliance with Secure Flight and crew vetting programs.
- CBP data reporting programs: Registering and connecting to CBP systems for data submissions (PNR, eAPIS, iAPI, MCL, EVUS, ESTA, DocVal).
- Mandatory technical testing (CBP & TSA): Completing required electronic testing for data transfers with U.S. authorities before commencing commercial operations.
- CBP international carrier bonds: Obtaining a mandatory CBP carrier bond administered centrally through the CBP Office of Administration in Indianapolis.
- POE clearance for international operations: Requesting landing rights directly from local CBP Ports of Entry.
Core passenger and crew data obligations for airlines in the U.S.
Staying compliant requires several types of passenger and crew data transmissions and interactive checks. Depending on your business model and tech stack, your basic obligations in the USA include:
- TSA Secure Flight: Vetting passenger data against government watchlists.
- APIS PAX & Flight Crew Manifests (FCM): Transmitting Advance Passenger Information (API PAX) and crew data (API CREW / FCM) for all international flights, and just crew data for overflight legs.
- Master Crew List (MCL): Maintaining a centralized, pre-approved list of all employed crew, with mandatory updates for additions, modifications, and deletions.
- Passenger Name Record (PNR / PNRGOV): Required for any carrier utilizing a reservation system or Departure Control System (DCS). Carriers operating without both a DCS and a reservation system are exempt from PNR reporting.
- Visa Waiver Program (VWP) & ESTA: Checking ESTA status for all VWP travelers; carriers must sign a formal VWP Signatory Carrier Agreement with CBP prior to boarding any ESTA travelers (note that this agreement may expire periodically and require renewals).
- Electronic Visa Update System (EVUS): Checking EVUS status for all Chinese passport holders with 10-year B1/B2 visas.
- Document Validation (DocVal): This is an emerging CBP framework for validating passenger entry documents—such as U.S. visas or Green Cards—directly against CBP databases before boarding (currently voluntary, but transitioning toward full enforcement).
4 operational traps that catch airlines off-guard
Even seasoned dispatch teams can run into unexpected procedural hurdles during U.S. certification and daily flight operations.
1. Non-standard API data scope
Do you assume that the scope of Advanced Passenger Information (API) data is the same everywhere? When it comes to the U.S., such an assumption can be risky. Two data elements required by the U.S. authorities often catch airlines by surprise: country of residence and destination address. Be sure to include both in your API submissions to avoid potential compliance issues or operational disruptions.
2. PNRGOV capability gap in reservation systems
Commercial operators often transmit API PAX data through their Departure Control System (DCS) and handle booking data (required in PNR submissions) within their reservation system. However, some reservation systems lack native functionality to format and transmit compliant PNRGOV EDIFACT messages directly to U.S. CBP. Attempting to build a custom PNR integration from scratch just to bridge this gap can delay market launch timelines by months. This challenge is quite common for airlines using modern tech solutions such as Offer-and-Order systems.
3. Disproportionate setup hurdles for seasonal and ad-hoc flights
Sending iAPI and PNR data to the U.S. CBP requires a dedicated MQ connection that takes months of rigid testing, complex network engineering, and high upfront costs. For seasonal, charter, or one-off ad-hoc flights, this lengthy technical setup makes short-notice routes nearly impossible to launch. Off-the-shelf market solutions capable of handling both iAPI and PNR transmission at a sensible price point are exceptionally rare, leaving carriers trapped between heavy costs and missed flight opportunities.
4. Occasional clearance asymmetries
Flight legs between the U.S. mainland and U.S. territories may carry unexpected directional rules. One such example is the U.S. Virgin Islands (USVI):
- Mainland U.S. to USVI: Typically processed outbound as a domestic flight leg.
- USVI to Mainland U.S.: Requires mandatory CBP clearance prior to departure.
Because return legs from the USVI require explicit CBP filings, dispatchers must ensure these mandatory actions are factored into their flight plans.
How PnrGo simplifies U.S. data compliance for airlines
PnrGo provides a flexible, enterprise-grade compliance engine built specifically to solve complex airline data workflows.
- Full data coverage with a modular, pick-and-choose approach: PnrGo doesn’t lock you into an all-or-nothing software suite. If your existing setup already handles most mandatory data submissions but your reservation system lacks PNRGOV capabilities, you can use PnrGo as a “gap filler” to cover that specific requirement—without paying for redundant reporting functionalities.
- Easy-to-activate seasonal service: Activate and deactivate your service setup based on seasonal transatlantic flight schedules to optimize your operational costs.
- CBP backup option: While TSA prohibits backup systems for Secure Flight, CBP allows secondary data streams. PnrGo provides a reliable backup for APIS PAX (passenger manifests), FCM (Flight Crew Manifests), and PNRGOV submissions, as well as MCL (Master Crew List) updates and ESTA, EVUS, and DocVal interactive checks. This provides a valuable compliance safety net for your U.S. operations.
- Onboarding & certification assistance: We help your team through the complex testing cycles required by CBP and TSA, significantly accelerating your operational timeline.
Managing U.S. data reporting compliance demands a combination of strict operational vigilance and reliable software architecture. Partnering with dedicated compliance experts allows your flight operations team to focus on schedule efficiency while keeping your data submissions fully compliant with TSA and CBP standards.
Contact the PnrGo team today to learn more about our CBP and TSA compliance solutions and enhance your commercial flight reporting pipeline.
