Child Traveling with Adult in a Separate PNR/Order

Remarks are required when a child traveling with an adult, is ticketed on a separate PNR/Order to help American identify a relationship between a child and an adult traveling together. This will confirm the child is accompanied by an adult.

·         The reservations should be cross-referenced in each PNR/Order with the special service requirement (SSR) or OSI field and will be verified in both PNRs/Orders that the child and adult are traveling on the same itinerary.

·         Once the system identifies the child is accompanied by an adult the restricted rules are ignored and the American flight segments will remain in the itinerary. 

Please update child and adult bookings traveling in a separate PNR/Order as follows:

PNR Required Documentation

Secure Flight Passenger Data Requirements

·        Add correct SFPD information

o   SABRE: DOCS/DB/DATE OF BIRTH/GENDER/LASTNAME/ FIRSTNAME/MIDDLENAME

Example: DOCS/DB/25DEC2003/F/DOE/JANE/ANN

·         Ensure all data is accurate at time of booking to avoid cancellation of itinerary.

Note: If you have format questions, please check with your GDS or Technology Provider.

Special Service Request Requirement (SSR) / OSI

The adult and child reservations should be cross-referenced with the special service requirement (SSR) or OSI field and the system will verify both PNRs/Orders to confirm that the child and the adult are traveling on the same itinerary.

·         Update the Child PNR/Order and the Adult PNR/Order by adding Special Service Request (SSR) or OSI indicating the number of people traveling with the minor and the adult PNR.

Child PNR

Sabre: OSI TCP#/ABCDEF (ADT PNR/Order)

Example: OSI TCP4/ABCDEF (ADT PNR/Order)

Adult PNR/Order

Sabre: OSI TCP#/LMNOPQ (ADT PNR/Order)

Example: OSI TCP4/LMNOPQ (ADT PNR/Order)

·         If more than one adult is accompanying the child and there are multiple PNRs/Orders you must add an OSI for each PNR/Order.

o   One adult traveling on outbound and another adult traveling on the return and there are separate PNR’s for the adults. 

Child PNR

Sabre: OSI TCP4/ABCDEF (Adult PNR/Order outbound flight)

Example: OSI TCP4/GHIJKL (Adult PNR/Order return flight)

Adult PNR/Order

Sabre: OSI TCP4/LMNOPQ (Child PNR/Order outbound flight)

Example: OSI TCP4/ LMNOPQ (Child PNR/Order return flight)

Note: If you have format questions, please check with your GDS or Technology Provider.

PNR/Order is not cross-referenced

When our system is unable to identify a relationship between a child and adult traveling together, our coding will identify the child booking as an unaccompanied minor. This may result in the American flight segment being canceled as the unaccompanied minor rules are very restrictive.   

Once the system identifies the child is accompanied by an adult the restricted rules are ignored and the American flight segments will remain in the itinerary.

Child under the age of 15

·         The PNR/Order is monitored to see if the TCP information is added.

·         If the PNR/Order is not updated, the system will UC the AA segments which will prevent check in.

·         The system will review all SFPD for Child qualification. Those PNR’s that have invalid itineraries will be documented in the OSI as follows:

ATTN AGCY/OA IF PAX IS UMNR UNDER THE AGE OF 15 THEY

DO NOT QUALIFY FOR TRAVEL ON AN INTERLINE CONNECTION.

PLEASE ADD THE TCP DETAILS REGARDING THE ADT PNR

WITHIN 72HRS OR AA SEGS WILL BE CXLD

Updated:  December 2024