Passenger manifest and API data requirements: standardized electronic file format, fixed fields, and UN/EDIFACT messaging compliance. The regulation mandates separate electronic files for passenger and crew manifests with a specified flat-file naming convention and a pipe-delimited record structure of 53 data elements. It prescribes fixed field lengths and types for flight identifiers, timings, ports, counts, PNR, passenger/crew biographics, travel-document and visa details, crew-license fields, and carrier contact information, identifies certain non-mandatory fields, and endorses furnishing data via UN/EDIFACT PAXLST API messaging.
Cases where this provision is explicitly mentioned in the judgment/order text; may not be exhaustive. To view the complete list of cases mentioning this section, Click here.
Provisions expressly mentioned in the judgment/order text.
Passenger manifest and API data requirements: standardized electronic file format, fixed fields, and UN/EDIFACT messaging compliance.
The regulation mandates separate electronic files for passenger and crew manifests with a specified flat-file naming convention and a pipe-delimited record structure of 53 data elements. It prescribes fixed field lengths and types for flight identifiers, timings, ports, counts, PNR, passenger/crew biographics, travel-document and visa details, crew-license fields, and carrier contact information, identifies certain non-mandatory fields, and endorses furnishing data via UN/EDIFACT PAXLST API messaging.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.