Recommended Practice 1717a (Passenger Services Conference, IATA) is the industry recommended practice that adopts and references the UN/EDIFACT Passenger List (PAXLST) message for the electronic exchange of passenger and crew data between airlines and border-control authorities. It appears in the Passenger Services Conference Resolutions Manual (PSCRM) immediately after RP 1717 (Teletype Passenger Manifest – TPM) and forms the standardised vehicle for Advance Passenger Information (API) reporting in the air mode.
The PAXLST message is jointly maintained under the auspices of the World Customs Organization (WCO), IATA and ICAO. The detailed technical specification is published in the WCO/IATA/ICAO Passenger List Message (PAXLST) Implementation Guide, which IATA formally adopts for airline use through RP 1717a.
Origin, Status, and Relationship to Other Standards
The need for structured electronic passenger data grew rapidly in the 1990s and 2000s as governments introduced API programmes. Early solutions were often proprietary. The UN/EDIFACT PAXLST message was selected as the global standard because it already existed for multi-modal transport and could be constrained to an air-mode subset.
IATA’s role is to:
- Formally recommend the air-mode implementation of PAXLST to its members.
- Participate in the joint WCO/IATA/ICAO API Contact Committee that maintains the Implementation Guide.
- Ensure alignment with related IATA standards (RP 1717 TPM for simple name lists, RP 1707-series data-element directories, and later interactive-API best practices).
RP 1717a is Type B (recommended) and of indefinite duration. Updates to the underlying PAXLST Implementation Guide are reflected in subsequent editions of the PSCRM and in airline system implementations.
It is complementary to, not a replacement for, the simpler Teletype Passenger Manifest (RP 1717). Where a government requires only a name list, the TPM may still be used; where full biographic, document and itinerary data are required, PAXLST is the mandated format.
Purpose and Scope
The PAXLST message permits the transfer of passenger and/or crew data from an aircraft operator to a Customs, Immigration or other designated authority in the country of departure and/or arrival. Its principal purposes are:
- To facilitate the clearance of low-risk passengers and crew.
- To allow border authorities to concentrate resources on higher-risk individuals.
- To satisfy legal requirements for Advance Passenger Information (API) without the need for paper manifests (consistent with ICAO Annex 9).
Scope covers both:
- Batch API – one (or multi-part) message containing the full passenger list (or full crew list) for a flight.
- Interactive / passenger-by-passenger API – individual PAXLST messages sent in near real time, typically at check-in or boarding.
A separate PAXLST message is used for passengers and for crew. The message is mode-independent in the UN/EDIFACT directory but the air-mode Implementation Guide constrains segments, qualifiers and code lists to aviation use.
Technical Structure
PAXLST is a UN/EDIFACT message. Key characteristics of the air-mode implementation include:
Message identification
- Message type: PAXLST
- Typical version/release used in aviation: D.05B or D.02B (with Association assigned code “IATA”)
- Controlling agency: UN
Core segments commonly used in the air-mode subset
- UNH – Message header
- BGM – Beginning of message (distinguishes passenger list vs crew list; document name codes 745 = Passenger, 250 = Crew)
- RFF – Reference (message reference, unique passenger reference, etc.)
- TDT – Details of transport (flight number)
- LOC – Place/location (departure, arrival, transit points)
- DTM – Date/time/period (scheduled and actual times)
- NAD – Name and address (passenger or crew name and address data)
- ATT – Attribute (gender, etc.)
- NAT – Nationality
- DOC – Document/message details (passport, visa, other travel documents)
- CNT – Control total (number of passengers or crew)
- UNT – Message trailer
Additional segments (COM, FTX, GEI, MEA, etc.) are available when required by a particular national implementation.
Message organisation
- One PAXLST for all passengers on the flight (or individual interactive messages).
- A separate PAXLST for crew.
- Multi-part messages are supported when the data volume exceeds practical limits; each part carries the necessary flight identification and the final part is flagged.
The WCO/IATA/ICAO Implementation Guide maps the agreed maximum set of API data elements into these segments and defines mandatory versus conditional status, code lists, and usage notes. National authorities may require a subset of the full element set, but should not invent elements outside the agreed guide.
Implementation in Airline Operations
Airlines (or their departure-control / API gateway providers) implement RP 1717a by:
- Extracting the required data from the reservation (PNR) and departure-control systems at the mandated trigger points (e.g., 72/48/24 hours before departure, at check-in, at departure).
- Mapping the data into the correct PAXLST segments and qualifiers according to the current Implementation Guide and any national overlay.
- Transmitting the message over Type B, MQ, AS4, or other agreed protocols to the national single window or designated authority address.
- Handling acknowledgements (often CUSRES or APERAK) and error corrections.
- Supporting both batch and interactive (iAPI) modes where required.
- Maintaining audit logs for regulatory and quality purposes.
Many modern API solutions also support the interactive variant in which a unique passenger reference is exchanged and border-system responses (board/do-not-board, etc.) are returned in near real time.
Relationship to ICAO Annex 9 and Data Harmonisation
ICAO Annex 9 encourages States to follow the WCO/IATA/ICAO API Guidelines and to use the PAXLST message. It also promotes the Single Window concept so that airlines transmit once. RP 1717a is therefore the practical expression, within the IATA standards framework, of the global policy that passenger data programmes should be harmonised, standards-based and limited to necessary data (see also RP 1701a Passenger Data Harmonization).
Benefits
- Airlines – Single global message format instead of dozens of national proprietary formats; reduced system-development cost; clearer compliance path; support for both batch and interactive programmes.
- Governments – Structured, machine-readable data of predictable quality; ability to perform risk assessment before arrival; reduced reliance on paper manifests.
- Passengers – Faster border processing for low-risk travellers; fewer last-minute document problems when data are captured and validated early.
- Industry – Foundation for subsequent interactive API, iAPI best practices, and the pre-travel digital-admissibility processes defined under One ID (RP 1701p).
Auditability and Continuous Improvement
Compliance and quality are measured by:
- Correct use of the current PAXLST version and air-mode subset.
- Completeness and accuracy of mandatory data elements.
- Timeliness of transmission relative to national deadlines.
- Acknowledgement and error rates.
- Alignment of national requirements with the joint WCO/IATA/ICAO element set (a key objective of RP 1701a).
Conclusion
Recommended Practice 1717a – PAXLST Message is the IATA vehicle that formally recommends the UN/EDIFACT Passenger List message for airline-to-government exchange of passenger and crew data. By adopting the jointly maintained WCO/IATA/ICAO Implementation Guide, it provides a single, globally recognised structure for Advance Passenger Information, supports both batch and interactive reporting, and underpins the broader industry goal of harmonised, efficient and privacy-respecting passenger data programmes. It remains the technical backbone of API reporting worldwide and coexists with the simpler name-list TPM (RP 1717) for residual legacy requirements.
Sources include the WCO/IATA/ICAO PAXLST Implementation Guide, IATA PSCRM listings for RP 1717a, UN/EDIFACT directory definitions of the PAXLST message, national API implementation guides that reference the standard, and related IATA facilitation materials. Full proprietary references and any IATA-specific constraints reside in the Passenger Services Conference Resolutions Manual.
Samsung Demo Phone
The Samsung Demo Phone currently tops our rank of the greatest Samsung phones available, beating even the pricier iPhone Ultra Max Mega.
So unsurprisingly this is an absolutely fantastic phone. The design isn't massively changed from the previous generation, but most other elements have been upgraded. This is what we call a big boost.
