Galileo & Worldspan - Secure Flight Inhibit Ticketing Enhancement


Overview (PA 1076 - version 05)

Reason For Issue version 05:

  • Added new Error Responses for *PSI#-DOCO to 3.2.2 and 3.2.3
  • Added item 4.3.2 to describe processing when an airline has not submitted a flight filing with Apollo/Galileo or Worldspan, therefore, a flight cannot be identified as a TSA Secured Flight.
High Level Description PA 1076

Galileo and Worldspan will: 
  1. Accept a new indicator (transmitted in inbound schedules and availability data from airlines) that identifies flights requiring Secure Flight Passenger Data (SFPD) which is the name as appearing on government issued ID, date of birth and gender.
  2. Provide a product for airlines that wish to participate which will inhibit ticketing in Travelport when flights in a reservation have been identified by the airline as Secure Flight applicable but do not have corresponding SSR DOCS item(s) containing all required SFPD present in the PNR.                                                                                                                     NOTE: ALL airlines will be initially signed up with Travelport. However, airlines must publish the Secure Flight indicator on applicable flights before the Travelport product will be activated for the specific airline.
  3. Make passport expiration date mandatory when document type (P or IP) and a Passport number are present in an SSR DOCS entry.
  4. Make a country code mandatory for SSR DOCO items with a document type of R (Redress) or K (Known Traveler) and a number.
  5. Return new error responses for SSR DOCS and SSR DOCO entriescontaining insufficient information.
  6. Allow for SSR DOCS, SSR DOCA and SSR DOCO to be entered and transmitted for passivesegments (Group Bridge – Worldspan and Drop Through – Galileo included)
Additionally, Worldspan will:
  1. Only allow an HK action code in SSR DOCS entries.
  2. Automatically create an SSR DOCS item for each airline in a PNR when an SSR DOCS with a generic airline code of YY is entered. The SSR DOCS YY will continue to remain.
  3. Allow newly created airline specific SSR DOCS items to display in applicable PNR GFAX fields and in PNR history.
As a reminder, character limitations within SSR DOCS are:
  • 30 characters for the LAST NAME
  • 30 characters for the FIRST NAME
  • 30 characters for the MIDDLE NAME
Additionally, Travelport recommends the name within the SSR DOCS be entered as close as possible to what appears on the passengers Government Issued ID. Entering names is subjective to the interpretation of the reader especially when names do not follow the single LAST, FIRST, and MIDDLE name philosophy. Therefore, understanding there are endless possibilities of passenger names, Travelport recommends the following as a guide for the most common name variations with the SSR
  • If a passenger has two middle names, e.g. Anthony Michael, they should both be included in the MIDDLE NAME field:
  • If a passenger has two first names, e.g. Mark James, they should both be included in the FIRST NAME field:
  • If a passenger has a suffix, e.g. JR, add to the end of the name in the LAST NAME field:
  • If a passenger has a single name, e.g. Prince, add a title (MR, MRS, MS, DR, REV, etc) as the first name in the FIRST NAME field:
  • If a passenger has a hyphenated last name, e.g. Jones-Smith, both name should be entered with a space between names and no hyphen:
  • If a passenger has no middle name, then only enter data in the LAST NAME and the FIRST NAME. It is no longer necessary to enter a slash at the end of the FIRST NAME field to account for a MIDDLE NAME that does not exist:
Customer Benefit

  • Travel agencies will be positioned to ensure their passenger is not inconvenienced by providing SFPD in advance to allow for the TSA to approve for boarding pass issuance.
  • Travel agencies will support the U.S. government regulation for all passengers to provide SFPD via the airline 72 hours prior to departure.
Click here for more details, examples and load date.