Važna obavijest za agente - obvezni podaci za unos u PNR za letove u SAD
This is an addendum to the notification sent on the 13th of August 2010.
Introduction
In compliance with the Secure Flight program, airlines will have to send mandatory passenger data to the TSA (Transport and Security Administration), for passengers flying within, from and to the US.
As per ATA resolution 20.61 (ATA: Air Transport Association), adopted on the 22nd of July 2010, ticketing issuance must be rejected when Secure Flight Passenger Data is missing. As a result, Ticketing Inhibition will be implemented, on the 1st of October 2010, for all travel agents reporting to ARC (Airline Reporting Corporation).
Moreover, following the IATA recommended practice, Ticketing Inhibition can be activated on validating carrier's request, for all other Amadeus agents worldwide, from the 1st of November 2010.
Background on Secure Flight program
Secure Flight is the name of the program driven by the TSA (Transport and Security Administration) to ensure passenger watchlist matching. TSA belongs to the US Department of Home Security (DHS). This program aims at bringing better control of the passengers travelling within, to and from the US.
Airlines must collect Secure Flight Passenger Data (SFPD) and transmit it to TSA at least 72 hours before the flight. From the 1st of November 2010 onwards, Airlines are exposed to financial penalties if not compliant, and passengers will not be able to fly without provided the mandatory information.
SFPD consists of the following information:
- Passenger’s Name (as per passport)
- Passenger’s birth date
- Gender
- Redress Number (if available). This is a unique number that DHS currently assigns to individuals who use the DHS Traveller Redress Inquiry Program (TRIP). Under the Secure Flight program, individuals will use the Redress Number in future correspondence with DHS and when making future travel reservations.
- Known traveler number (if available – at a later stage)
Impacted customers: ARC (Airline Reporting Corp) travel agents
- Amadeus ARC travel agents, for both paper and electronic ticketing
- For tickets issued on validating carriers which requested the activation:
- All other Amadeus travel agents worldwide using Amadeus Electronic Ticketing and Electronic Ticketing Direct
- Amadeus ATO/CTOs for Altea carriers
Implementation Date
- Ticketing inhibition will be deployed in ARC markets on the 1st of October 2010
- From the 1st of November 2010 onwards, it will also apply to all Amadeus agents issuing tickets on validating carriers which have requested the activation
Information page
The list of validating carriers that have activated ticketing inhibition will be available from November, 1st in the HE SECURE FLIGHT pages.
Main benefits
- Compliancy to ATA (Airline Transport Association) resolution and to the regulation of US Department of Homeland Security (DHS)
- Ticketing inhibition prevents passenger from being rejected at boarding time when Secure Flight Data is missing
For travel agents
- Mitigates the risk of receiving Agent Debit Memos from Airlines
- Customer satisfaction
For airlines
- Mitigates the risk of receiving a penalty from TSA (Transport and Security Administration)
reduces support at the airport in case of rejected passengers
Ticketing Inhibition: description (applicable to ARC travel agents only)
Travel Agents must enter the SFPD (Secure Flight Passenger Data) through the following elements of the PNR: SSR DOCS (Passenger name, DOB, Gender) and SSR DOCO (Redress Number).
Note that only SSR DOCS presence will be checked when issuing a ticket.
SRDOCS AA HK1-----30JUN73-M--SMITH-JOHN-MICKAEL/P1
| | | | | |
| | | | | middle name
| | | | First name
| | | Surname
| | Gender
| DOB
Airline code
SRDOCO AA HK1--R-123456/P1
| | |
| | |
| | Redress Number
| Document identifier (Redress Number)
Airline code
At issuance time, system first checks if segments are Secure Flight relevant, thanks to the Secure Flight indicator (DEI 504) published in the flight schedule of the marketing carrier.
Then, for each Secure Flight relevant segment and for each passenger, system checks if a SSR DOC S is associated:
- If yes, ticket is issued.
- If no, issuance is rejected with the following messages:
Case 1: SSR DOCS has been entered with a provider that is different from the marketing carrier of the secure flight eligible segment
Ticketing Inhibited – SSR DOCS Airline provider not matching for Px (x=Passenger Number)
Case 2: no SSR DOCS at all for the passenger and the segment:
Ticketing Inhibited – SSR DOCS missing for Px
