Secure Flight Passenger Data Program (SFPD)

The Secure Flight Passenger Data program (SFPD) is a program of the Transportation Security Administration (TSA) designed to enhance the security of air travel. Secure Flight regulations are mandatory for all flights for U.S.-based carriers and flights which are in, out, or overflights for international –based aircraft operators.

Under Secure Flight regulations all passengers (including minors) must provide Secure Flight Passenger Data (SFPD) at the time of ticketing, or the intent to ticket (i.e. travel vouchers).

Secure Flight Passenger Data (SFPD) includes the following information:

Full Name (Mandatory)
- Full name must be provided as it appears on non-expired government issued ID used for traveling.
- PNR and security name must match (recognizing limitations in PNR name fields and length).
Date of Birth (DOB - Mandatory)
Gender (Currently M or F only – Mandatory; additional Gender types forthcoming )
Known Traveler Number (Optional)
- Used to identify passenger's eligibility for expedited screening as part of the TSA PreCheck program.
- Known Traveler Number includes Global Entry, SENTRI, NEXUS or TSA application numbers.
- See Trusted Traveler Programs for more information.
Redress Number (Optional)
- The redress number is provided by the U.S. government to uniquely identify passengers who have experienced issues with misidentification, and are continuously referred to additional screening at airports.

For additional information, see DHS Traveler Redress Inquiry Program (DHS TRIP) on the Department of Homeland Security website.

A list of TSA Frequently Asked Questions are available for review.

Name Field: SFPD

The security name submitted to Secure Flight must match the name on the non-expired government issued photo ID that will be used by the passenger when traveling.
The security name (or Secure Flight) name must also match the PNR name which is used to generate the boarding pass or seat request card. (Recognizing limitations in PNR name fields and length).
The security name can be 35 characters for each of the first, middle, and last names. The PNR name will cut off due to the shorter field lengths. If the PNR name field is exceeded, enter the full surname and as many characters of the first name as space allows.

Delta’s Enhanced Messaging

To further enhance the passenger experience for our customers, Delta has messaging in place to alert travel agencies that there is a name mismatch between a PNR name and the Passenger Security Name. This notification is designed to offer our travel partners advance opportunity to verify or update the customer name information to help ensure a smooth check-in experience.

The Passenger Security Name is the name used in a passenger’s valid government issued identification such as driver’s license, real ID, or passport.
The Security Name is the name which is required (when applicable) at ticketing for Secure Flight. It is collected in the SSRDOCS.
The PNR Name is the name entered in the passenger name field of a PNR.

The Delta message will be sent via an SSR ADPI (Special Service Request requesting Additional Passenger Information) which will drop to an agency’s queue for review. The SSR message will be:

SSR ADPI DL KK1 SECURE FLT SFPD NAME MISMATCH PLEASE VERIFY AND CORRECT

This SSR ADPI notification gives the travel agency the opportunity to verify, update or correct the PNR and Security Name with ID verification prior to the customer’s check-in. There will be no interruption of the ticketing process.

Helpful Tips

Ensuring that the names are aligned allows accurate security vetting with the Government and provides for a smooth passenger experience at check-in and at the TSA Security Checkpoint.
If the Passenger Security Name is different than the PNR Name (a mismatch), the travel agent will still be able to issue the ticket. There will be no interruption of the ticketing process.
When SSR ADPI messages are generated to the PNR, the PNR will be queued to the applicable queue for agency follow-up.
Upon receiving the PNR SSR notification via agency queues, the agency should verify that both the Passenger Security Name and the passenger PNR Name match.
If the names are not matched prior to departure, a customer who attempts to check-in on delta.com or via the Delta mobile app will be directed to the airport. Check-in via kiosk will notify the passenger of a mismatch and offer the option to scan or swipe an approved ID, such as driver’s license or passport; otherwise, he or she will be directed to see an agent for assistance.
Travel partners who use booking tools that populate PNR name fields, SkyMiles member information or other process, should consider advising customers to synch the information and match names.
If it is necessary to correct the PNR Name to ensure that it matches the Passenger Security Name, please follow Delta’s Name Correction Policy. Details can be found on the Delta Professional Travel Agency website:

Name Match Check Basics to Allow for Check-in and Pass Through at the Security Checkpoint

First and Last Names for PNR Name and Security Name (approved ID) that match completely will pass to allow check-in.
Blanks will be removed from name elements when performing individual name element comparisons.
Prefix, Suffixes in a PNR name field are not used when name match is considered. Provided all other information is accurate in the PNR and SFPD, these scenarios will typically pass to allow check in.

Examples:

PNR First Name	PNR Last Name	Travel Document First Name	Travel Document Last Name
CRISTIAN	SMITH	CRISTIANJR	SMITH
MICHAEL	JONES	MICHAEL	JONESJR
PAUL	ANDERSONIII	PAUL	ANDERSON

Mismatch Names and Check-in Options

If the Passenger Security Name and PNR Name are not matched prior to departure, a customer who attempts to check-in on delta.com or via the Delta mobile app may be directed to an airport agent.
Check-in via kiosk will notify the passenger of a mismatch and offer the option to scan or swipe an approved ID, such as driver’s license or passport; otherwise, he or she will be directed to see an airport agent for assistance.Rate This Topic

Examples - Common Name Mismatches: SFPD

Examples of Common Security Name and PNR Name Mismatches

Spelling mistakes or using a nickname instead of a legal name for PNR and security names
PNR last name and security last name are different
PNR last name includes the security first name
Security last name and first name are reversed and do not align with PNR last and first names

1. Spelling mistakes or using a nickname instead of a legal name for PNR name and security name

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
NELSON	PATTY		NELSON	PATRICIA

2. PNR last name includes the security first name

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
JONESMARY	SUSAN		JONES	MARY	SUSAN

3. PNR last name and security last name are different

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
ANDERSON	MARIA		SANCHEZ	MARIA

4. Security last name and first name are reversed and do not align with the PNR last and first names

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
JONES	CATHERINE		CATHERINE	JONES
ANDERSON	ELEANOR		ELEANOR	ANDERSON

5. Security middle name is added at the beginning of the PNR first name

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
BOYDE	ANNCATHERINE		BOYDE	CATHERINE	ANN

6. Security middle name is used as the PNR first name

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
SMITH	ROBERT	JOHN	SMITH	JOHN	ROBERT

7. Security middle name initial is added to the end of the PNR first name without a space

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
ABBOTT	RONALDJ		ABBOTT	RONALD	J

8. John Smith (or other fictitious name) as entered in agency template used as security first name and last name

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
MOUNTAIN	JANE		SMITH	JOHN
MOUNTAIN	STEVEN		SMITH	JOHN

9. More than 1 passenger - the names are not aligned to the correct person

Example:

PNR Last Name	PNR First Name	PNR Middle Name	Security Last Name	Security First Name	Security Middle Name
JOHNSON	SUSAN		HARVEY	MICHAEL
HARVEY	MICHAEL		JOHNSON	SUSAN

SkyMiles Members: SFPD

Name Match Requirements

When a member adds a SkyMiles number, either at the creation of a reservation, or afterwards, if the SkyMiles number doesn't match the PNR/security name, they will be required to change the PNR/security name or remove the SkyMiles number.

Storing SkyMiles Member SFPD Information

SkyMiles members can store their SFPD information for future use when logged into MyProfile, or a specialist may do so upon request after getting consent.. Parents/guardians may request on behalf of minor children.

Booking - Res Procedures: SFPD

In most cases, Delta policy is that it is mandatory to collect Secure Flight Passenger Data (SFPD) at the time of booking a reservation prior to issuing a ticket. Most tickets cannot be issued without full SFPD, and reservations will not be held for someone without full SFPD information. Some exceptions may apply.

Upon request, direct customers that believe they have been mistakenly matched to a name on the watch list to the DHS Traveler Redress Inquiry Program (DHS TRIP) on the Homeland Security website.

Unusual Name / Age Conventions

Passenger name exceeds 24 characters	Please contact your GDS Help Desk for assistance.
Passenger has a hyphenated name	Enter name without a hyphen
Passenger has a single name	Enter the single name as the last name and enter FNU as the first name.
Passenger has a single letter last name	Please contact your GDS Help Desk for assistance.
Passenger's age exceeds 100	The first 2 digits of the year of birth are not saved, therefore SFPD information will update the year to the current century. This is not an issue.
Passenger name is the same as another passenger in the same PNR Multiple passengers with the same last name in the PNR require extra seats	Multiple passengers in the PNR with the same SFPD name will result in an error: Add a suffix that to the last name if applicable (Jr., II, etc.) Add an extra letter to the first name of the SFPD for the extra seat (CBBGa, EXSTb, etc.)

Extra Seat

SFPD is required for a 2nd seat for any customer occupying 2 seats or traveling with cabin baggage. Check with the specific GDS Help Desk for name formats and booking procedures.

Frequently Asked Questions

Where is the SFPD information entered in a reservation booked via GDS?

When is the SFPD data transmitted to the TSA? Since the required information should be received 72 hours prior to flight time, are there any issues with name corrections or new reservations booked less than 72 hours prior to departure?

Can a passenger name entered in the SSR DOCS field for SFPD differ from the name field in the PNR?

If the name in a SkyMiles profile name differs from the name used for SFPD (matching the valid government issued ID) will mileage credit still be given?

Will Secure Flight affect traveler profiles stored in GDS or self booking tools?

What is a Redress Number used for and how can I obtain one?

Do the airlines keep the TSA information as history?

What steps or processes are you putting in place if the traveler is unable to print a boarding pass once the required data elements have already been transferred to the TSA?

How does a travel agent determine which airline’s policies to apply when reviewing this program?

What should Travel Agents do to assist Delta to ensure full compliance?

Where is the SFPD information entered in a reservation booked via GDS?

Full name, Date of Birth and Gender must be entered in the SSR DOC-S. The Redress Number will be accepted in a SSR DOC-O format. Questions on formats should be directed to the applicable GDS Help Desk.

When is the SFPD data transmitted to the TSA? Since the required information should be received 72 hours prior to flight time, are there any issues with name corrections or new reservations booked less than 72 hours prior to departure?

A passenger’s SkyMiles profile name may differ from the name used and entered for SFPD. Mileage credit is not based on the information in the SSRDOCS. Mileage credit will be given based on the name in the Frequent Flyer profile and the FF number. However, Delta recommends that information within SkyMiles profiles be updated to be in sync with government issued identification used for travel and SFPD.

Can a passenger name entered in the SSR DOCS field for SFPD differ from the name field in the PNR?

Small differences between the passenger's ID and the passenger name printed on the boarding pass, such as the use of a middle initial instead of a full middle name or no middle name/initial at all, or hyphens and apostrophes should not cause a problem for the passenger.

If the name in a SkyMiles profile name differs from the name used for SFPD (matching the valid government issued ID) will mileage credit still be given?

A passenger’s SkyMiles profile name may differ from the name used and entered for SFPD. Mileage credit is not based on the information in the SSRDOCs. Mileage credit will be given based on the name in the Frequent Flyer profile and the FF number. However, Delta recommends that information within SkyMiles profiles be updated to be in sync with government issued identification used for travel and SFPD.

Will Secure Flight affect traveler profiles stored in GDS or self booking tools?

Name information in profiles that will be used in the SSR DOC-S for SFPD should match a passenger’s valid non-expired government issued photo ID used for travel. You should ensure that the name stored in the profile that is transferred in the name field of a PNR matches the name on the passenger’s valid non-expired issued photo ID. Small differences between the passenger's ID and the passenger name printed on the boarding pass, such as the use of a middle initial instead of a full middle name or no middle name/initial at all, or hyphens and apostrophes should not cause a problem for the passenger. Delta recommends that information within customer profiles be updated to be in sync with government issued identification used for travel and SFPD.

What is a Redress Number used for and how can I obtain one?

Passengers who may have a name that is similar to an individual on the watch list and who have been mistakenly matched to a name on the watch list are invited to apply for Redress through DHS TRIP. For more information on the redress process, visit www.dhs.gov/trip. Secure Flight uses the results of the Redress process in its watch list matching process, thus preventing future misidentifications.

BACK TO TOP

Do the airlines keep the TSA information as history?

Airlines are required per government regulations to keep the TSA information (to include vetting result and any other messages received from the TSA) for a specific period of time. Additional historical use occurs for research purposes.

What steps or processes are you putting in place if the traveler is unable to print a boarding pass once the required data elements have already been transferred to the TSA?

If a traveler is unable to print a boarding pass, an airport customer service agent will provide assistance as they do today. Updates to SFPD which are sent to the TSA can occur at any time prior to boarding.

How does a travel agent determine which airline’s policies to apply when reviewing this program?

Travel agents need to determine the operating carrier in the itinerary. The operating carrier is required to ensure the passengers’ SFPD has been transmitted to the TSA and ensure compliance. Delta’s policies apply to all DL operated flights.

What should Travel Agents do to assist Delta to ensure full compliance?

Please review all the rules and policies found on the Delta Professional Travel Agency website. It will also be helpful to work with your ticketing agencies to see that corporate-traveler profiles are updated and direct booking tools are capable of capturing mandatory SFPD data.

Questions?

For questions concerning GDS booking entries please contact your GDS provider. For all other questions, please contact Global Sales Support or Delta Reservations for assistance.

Updated 07/2018