Secure Flight Passenger Data Overview

(1)

Page Nº 1

Customer

Solutions

Secure Flight

Passenger Data

Overview

October 2010

(2)

1 Introduction

This document aims at providing a global picture of the TSA Secure Flight Passenger Data program which will impact reservations and ticketing processes.

For further information about this program, please refer to the official TSA website:

http://www.tsa.gov/what_we_do/layers/secureflight/index.shtm

2 What is Secure Flight program?

2.1 Mission and objectives of TSA Secure Flight program

In 2009 and 2010, the responsibility of watchlist matching for all passengers flying within, to, from and over the US was transferred from airlines to the Transportation and Security Administration (TSA).

Secure Flight Passenger Data is the name of the program driven by the TSA to ensure this passenger watchlist matching. It is not a replacement of Advance Passenger Information System (APIS).

2.2 Secure Flight Passenger Data (SFPD)

The following passenger information must be provided at least 72hrs prior to departure or immediately for bookings created within 72 hours.

Passenger full name as appears on travel document

Date of birth

Gender

Redress Number (if available)

Known traveller number (if available – at a later stage)

2.3 Secure Flight Process

The operating carrier is responsible for providing Secure Flight Passenger Data (SFPD) to the TSA.

When receiving SFPD 72hrs prior to departure or less the TSA will proceed with watchlist matching and return to the Airline a boarding authorization.

In case the passenger is identified as a “No Fly” or “Selectee”, the boarding pass issuance will be inhibited by the airline and the passenger cannot fly.

(4)

3 How to collect mandatory information?

3.1 SSR DOCS & DOCO

Secure Flight Passenger Data (SFPD) must be entered in the PNR within standard SSR DOCS and DOCO, in order to be correctly transmitted between systems and to the TSA. 3.1.1 Cryptic entries

Passenger first name, last name, date of birth and gender are defined by default as mandatory fields. The passenger name must be entered as it appears in the travel document, including spaces.

Airline Code Marketing carrier (mandatory) Status Code HK1 (mandatory)

Date of birth Format DDMMMYY (mandatory)

Gender M or F for adults / MI or FI for infants (mandatory)

Surname As appears on passport or other travel ID, including spaces (mandatory)

First name As appears on passport or other travel ID, including spaces (mandatory)

Middle name As appears on passport or other travel ID, including spaces (mandatory if applicable)

/P1 Passenger association is mandatory if more than one passenger in the PNR. Segment association is possible but not recommended because the SSR would be lost in case of segment cancellation.

Note: SSR DOCS is required for infants (INF), if ticketed. In such case 2 SSR DOCS are associated to the same passenger, and the infant’s gender must be MI or FI.

Redress Number for adults:

SRDOCO AA HK1--R-123456/P1

| | | | | |

| | Redress Number

| Document identifier (Redress Number) Airline code

Redress Number for infants (INF):

(5)

Page Nº 5

Watchlist matching is performed against the passenger’s full name provided in the SSR DOCS, not against the passenger’s name in the PNR (NM). However, the name on the ticket/boarding pass should match the name on the passport.

As a consequence it is important to also make the reservations under the full passenger name, as it appears on the passport, with the first and middle names (no nicknames). If the name is too long, it can be truncated in order to still be easily matched with passport name. Example of name truncation:

Name on the passport: ERICSSON, WILLIAM EDWARD Name in PNR: 1.ERICSSON/WILLIAM E

3.2 How to identify eligible flights?

3.2.1 General rule

Secure Flight program applies to:

All US Carriers flights

All flights to/from and within the US territory (including American Samoa, U.S. Virgin Islands, Guam, Northern Mariana Islands and Puerto Rico) of other carriers.

Thus, mandatory SFPD must be collected for:

All US Carriers flights

All flights of other carriers that are operating to or from the US. Note: Flights over the continental U.S. should be included in a later phase. 3.2.2 Information message at segment sell

Airlines have the possibility to display a message to Amadeus agents at segment sell time for any eligible flight, notifying the need for SFPD.

This is an optional information message. Wording may vary from an Airline to another and it is removed from the face of the PNR following End Of Transaction.

3.2.3 Amadeus e-Travel Management

With e-Travel Management it is possible to make SFPD elements mandatory at booking time which can be configured by the administrator. The check is optional and can be made based on board and off points.

3.2.4 Indicator to identify Secure Flights

From the 3rd November it will be easy to identify flights (including US over flights) as airlines will have the possibility to use a new indicator in the flight schedule.

This indicator will be available through DO entry in the “Comments” section saying “Secured Flight”.

(6)

4 New SSR - ADPI

With immediate effect this new SSR will allow the airlines to request necessary passenger information from the booking source. It may be used when SFPD or APIS information is missing.

From the 1st November all passenger data information will be mandatory for all passengers flying to, from or within the United States or on any flight operated by an American carrier.

Example:

SSR ADPI 1A KK1 AF0239 REQ SEC FLT PSGR DATA 72 HBD FOR ALL PSGRS

Note:

The addition of an SSR ADPI on an Amadeus individual PNR will trigger queue placement to Queue 1 / Category 11 of the PNR queuing office.

The addition of an SSR ADPI on an Amadeus Group PNR will trigger queue placement to Queue 87 / Category 6 of the PNR queuing office

Customers will need to regularly check these Queues in order to collect SFPD and enter missing SSR DOCS.

5 Ticketing inhibition

5.1 BSP Customers

From 1st November 2010 airlines may require to inhibit ticketing if mandatory data is missing also for non-US customers.

The check will be made:

- If airlines have activated the ticketing inhibition switch

- If the validating carrier instructs Amadeus to extend the ticketing inhibition outside of the US

- In a codeshare scenario only the marketing flight indicator will be checked. - On the presence of an SSR DOCS associated to each passenger to be ticketed

(including infants). With setting Secure Flight data elements as mandatory this will ensure the presence of SFPD.

(7)

Page Nº 7

1.SMITH/PAUL MR

2 BA 117 Y 15NOV 1 LHRJFK HK1 5 0820 1115 *1A/E* 3 IB6250 Y 20NOV 6 JFKMAD HK1 7 1800 0710+1 *1A/E*

4 AP MUC - AMADEUS DEFAULT OFFICE - A 5 TK OK02JUL/MUC1A0701 6 SSR DOCS BA HK1 ////16JAN80/M//SMITH/PAUL

7 FP CASH

8 FV PAX BA/S2-3

BA is validating carrier for the itinerary.

Both flights are flagged as “Secure Flight” in the schedules.

SSR DOCS is missing for IB flight.

The issuing agent is BSP.

If BA requires to apply the check worldwide Ticketing will be disallowed with error:

Ticketing Inhibited – SSR DOCS missing for PX

If BA doesn’t require the check to apply outside the US Ticketing will be permitted Note: The list of validating carriers that have activated ticketing inhibition will be available from 1st of November 2010 in the HE SECURE FLIGHT pages.

6 Glossary

SFPD Secure Flight Passenger Data

APIS Advance Passenger Information System. TSA Transport and Security Administration BSP British Settlement Plan