Recommended Practice 1719a – Frequent Traveller List (FTL)

Recommended Practice 1719a (Passenger Services Conference, IATA) is the industry recommended practice that standardises the Frequent Traveller List (FTL). The FTL is a Type B teletype message generated from the departure-control system that identifies passengers on a flight who are members of a frequent-flyer or elite-status programme and conveys their relevant loyalty identifiers and tier information to the airline’s reservations, loyalty, or customer-service systems. It appears in the Passenger Services Conference Resolutions Manual (PSCRM) immediately after RP 1719 (Passenger Final Sales Message – PFS) and forms part of the 1719-series family of post-check-in / flight-close messages.

Origin, Status, and Relationship to Other Standards

As frequent-flyer programmes grew in commercial importance, airlines required a reliable, automated method of capturing which boarded passengers held elite status or frequent-traveller accounts so that:

• Mileage accrual and tier credits could be processed accurately.
• Onboard and ground service could be aligned with status entitlements.
• Central loyalty and customer-relationship systems could be updated with flown activity.

The FTL was developed within the same Type B close-out messaging framework as the PFS, PRL, ETL, TPL and ASL. It is therefore generated at the same logical point in the process (completion of check-in / flight close-out) and shares the same addressing and multi-part conventions.

It is complementary to:

• AIRIMP / SSR FQTV elements that carry frequent-traveller data in the reservation (PNR) phase.
• The PFS (RP 1719), which reports overall final sales and no-show/go-show figures.
• Modern loyalty-system APIs and NDC Order messages that may also exchange frequent-traveller data, but do not replace the operational DCS-to-loyalty close-out feed provided by the FTL.

The practice is Type B (recommended) and of indefinite duration.

Purpose and Scope

The purpose of the FTL is to provide the airline’s central systems with a definitive list of frequent travellers (and their status/tier information) who actually travelled on the flight. Typical information includes:

• Passenger name as recorded in the DCS.
• Frequent-traveller programme identifier (airline designator + account number).
• Tier / status level (e.g., Gold, Silver, Platinum, or the carrier’s internal codes).
• Optionally, related service or recognition indicators.

Scope is limited to those passengers on the final boarded list who have a frequent-traveller record associated with the booking or who were identified at check-in. It does not attempt to replace full PNR history or revenue-accounting feeds; it supplies the operational “who of status actually flew” snapshot needed by loyalty and customer-service systems.

Technical Structure and Message Content

The FTL follows standard IATA Type B message conventions:

• Address Element and Communications Reference Element.
• Message Identifier: FTL.
• Flight identification (airline, flight number, date, origin).
• One or more passenger entries containing name, frequent-traveller number and tier/status information.
• End Element (and part numbering if the list is multi-part).

The precise element layout and the set of status codes are defined in the Recommended Practice and are implemented via airline-specific configuration tables in the DCS. Name construction follows the same principles used in other passenger messages (RP 1707b). Frequent-traveller identification typically mirrors the format used in AIRIMP FQTV elements (airline code + account number, optionally followed by tier).

Implementation in Airline Operations

Generation
The DCS automatically produces the FTL at flight close-out (the same trigger used for the PFS and other 1719-series messages). Only passengers who both boarded and have an associated frequent-traveller record are included.

Addressing
The message is sent to the airline-designated loyalty, reservations or customer-service processing address. When a flight is handled by a ground handler, the handler’s DCS still generates the FTL to the operating carrier’s designated address.

Downstream use

• Loyalty systems use the list to post mileage, tier points and recognition credits.
• Customer-service and VIP desks use it for post-flight follow-up or service recovery.
• Some carriers feed the data into revenue-management or network-planning analyses of high-value passenger flows.

Relationship to reservation-phase data
Frequent-traveller information is normally already present in the PNR via SSR FQTV. The FTL confirms which of those passengers actually travelled, thereby closing the loop between reservation intent and flown activity.

Relationship to the Broader 1719-Series Family

Airlines configure which of these messages they wish to receive according to their system architecture and business priorities.

Benefits

• Loyalty programmes – Accurate, timely capture of flown frequent travellers for accrual and tier processing.
• Customer service – Clear post-flight visibility of elite passengers for recognition or recovery actions.
• Ground handlers – Standard method to report frequent-traveller activity to the operating carrier.
• Industry – Consistent Type B format that every major DCS can generate and every loyalty system can be configured to consume.

Auditability and Compliance

Compliance is demonstrated by:

• Generation at the correct close-out trigger.
• Inclusion of only boarded passengers who hold frequent-traveller records.
• Accurate transmission of account numbers and tier/status codes.
• Delivery to the airline-designated processing address.
• Message logs retained according to airline record-keeping requirements.

Conclusion

Recommended Practice 1719a – Frequent Traveller List (FTL) provides the standardised Type B mechanism for reporting which frequent-flyer and elite-status passengers actually travelled on a flight. Generated automatically by the departure-control system at close-out, it supplies loyalty and customer-service systems with a definitive flown list of high-value passengers, thereby closing the operational loop between reservation-phase FQTV data and post-flight accrual and recognition processes. It remains an integral member of the 1719-series close-out messages and continues to be supported by modern DCS platforms.

Sources include the IATA PSCRM listing for RP 1719a, the structural relationship of the 1719-series messages, AIRIMP frequent-traveller (FQTV) conventions, and standard industry practice for post-check-in loyalty messaging. Full proprietary specifications reside in the Passenger Services Conference Resolutions Manual.