- Messages
- 10,951
- Reaction score
- 4,150
- # of dives
- None - Not Certified
Here is a memo to travel industry professionals (thus the phraseology):
Beginning May 15, the name you input in the Passenger Name Record (PNR) Name Field should match the name on the ID the traveler plans to use at the airport. Initially, TSA has built some flexibility in to the system. TSA has stated that small differences between the passenger's ID and the passenger's reservation information, such as the use of a middle initial instead of a full middle name or no middle name/initial at all, or prefixes and suffixes, should not cause a problem for the passenger in the near term. Nonetheless, you should begin prompting your customers to provide you with the name as it appears on the document they plan to present to airport security.
Beginning Aug. 15, the name included in the PNR Name Field and DOCS field should match the government-issued identification the passenger intends to present at the airport prior to boarding. As a result, agents should be trained and/or the automated booking tool should be designed to prompt the traveler for the ÅÏame as it appears on the ID they plan to present at the airport? The reason the Name Field and DOCS name should match is because TSA will visually compare the name listed on the boarding pass (which comes from the Name Field) against the traveler's ID as presented at the airport (which is the name that must be found in the DOCS field). As a result, to reduce the possibility of airport security/check-in delays, the Name Field, DOCS Field and Traveler's ID should all match.
If you have repeat travelers with stored profiles, you should ask the traveler to compare his/her state ID with his/her passport. For most travelers, the names on these two documents will match. In such cases, you can store the DOCS field with the name as an always move field. This will allow the Secure Flight name to automatically move into the PNR when a reservation is created.
If the traveler's name on his/her state ID does not match the name found on his/her passport, you should encourage the traveler to align the two names so that they do match. This would require the traveler to obtain a new passport or state ID. Since this is not practical for all travelers, and the Secure Flight rule does not require that names on state IDs and passports match, you will need to develop procedures for managing two different names. With repeat customers with stored profiles, you should create two different DOCS fields and store them as Optional move fields. This would require that the traveler be prompted with every reservation to identify the ID he/she plans to use so that the correct DOCS field is moved into the PNR.
Beginning May 15, the name you input in the Passenger Name Record (PNR) Name Field should match the name on the ID the traveler plans to use at the airport. Initially, TSA has built some flexibility in to the system. TSA has stated that small differences between the passenger's ID and the passenger's reservation information, such as the use of a middle initial instead of a full middle name or no middle name/initial at all, or prefixes and suffixes, should not cause a problem for the passenger in the near term. Nonetheless, you should begin prompting your customers to provide you with the name as it appears on the document they plan to present to airport security.
Beginning Aug. 15, the name included in the PNR Name Field and DOCS field should match the government-issued identification the passenger intends to present at the airport prior to boarding. As a result, agents should be trained and/or the automated booking tool should be designed to prompt the traveler for the ÅÏame as it appears on the ID they plan to present at the airport? The reason the Name Field and DOCS name should match is because TSA will visually compare the name listed on the boarding pass (which comes from the Name Field) against the traveler's ID as presented at the airport (which is the name that must be found in the DOCS field). As a result, to reduce the possibility of airport security/check-in delays, the Name Field, DOCS Field and Traveler's ID should all match.
If you have repeat travelers with stored profiles, you should ask the traveler to compare his/her state ID with his/her passport. For most travelers, the names on these two documents will match. In such cases, you can store the DOCS field with the name as an always move field. This will allow the Secure Flight name to automatically move into the PNR when a reservation is created.
If the traveler's name on his/her state ID does not match the name found on his/her passport, you should encourage the traveler to align the two names so that they do match. This would require the traveler to obtain a new passport or state ID. Since this is not practical for all travelers, and the Secure Flight rule does not require that names on state IDs and passports match, you will need to develop procedures for managing two different names. With repeat customers with stored profiles, you should create two different DOCS fields and store them as Optional move fields. This would require that the traveler be prompted with every reservation to identify the ID he/she plans to use so that the correct DOCS field is moved into the PNR.