### BEFORE THE DEPARTMENT OFTRANSPORTATION

WASHINGTON, D.C.

Notice of/AT ATraffic Conference Actions Tentatively Exempted From Filing forApproval Docket OST-2012-0058

NOTICE OF TIER 1AGREEMENTS FILING

BYTHE INTERNATIONAL AIR TRANSPORT ASSOCIATION

26 September 2013 Communications with respect tothis Document should be sent to Douglas Lavin Regional Vice President
- North America International Air Transport Association 1201 FStreet, NW, Suite 650 Washington, DC 20004 (202) 628-9292

### Date: Summary DOCKET: DOT-OST-2012-0058 DOT ORDER: None Requested
26 September 2013 Filing feelIATAAcct:
USIUST involved Intended effective date: Meeting site, date: Agreement(s )lMinutes Waived by Order 2012-4-18, Appendix A, Section D Yes INovember 2010 320d 

### Passenger Services Conference (PSC), Geneva, 21 October 2010 PSCIRESO/148 bis dated 26 September 2013 PSCIMINS/034 dated 15April 20II Resolutions 722fand 722g Recommended Practice 1722z

### NOTICE OF TIER IAGREEMENTS FILING Pursuant to statements submitted byMember airlines ofthe International Air Transport Association (lATA), the undersigned hasbeen constituted tobetheir attorney-in-fact for filing with the Department ofTransportation copies ofagreements adopted bythe lATA Traffic Conferences. Ontheirbehalf, and pursuant totheprocedures specified in Order 20I2-4-18 (13 April 2012), Iam filing with the Department, inDocket OST-2012-0058, this Notice, the subject agreements and supporting documentation. These agreements areTier I agreements tentatively exempted by Order 2012-4-18 from Condition #2tothe Department's approval ofthe Provisions forthe Conduct ofthe lATA Traffic Conferences, which condition requires pre-implementation Department review. The subject agreements amend orestablish Resolutions and/or Recommended Practices that do notaddress subject areas which the Department has indicated itstill chooses toreview under Condition #2. The text ofthe agreements and other conference documentation sentto airline Members oflATA accompany this Notice. The cover pages ofthe documentation clearly identify each affected Resolution and/or Recommended Practice and show whether the subject agreements areamendments ornew agreements. Other pages provide thetext ofeach subject agreement. Where an affected Resolution orRecommended Practice has previously been exempted fromCondition #2 byDepartment action, the cover pages include the appropriate docket and order number. The cover pages include asummary to explain the nature andpurpose ofthe subject amendments and/or agreements.13461343.1 

### Respectfully submitted,

/s/ Douglas Lavin Douglas Lavin Regional Vice President
- North America International Air Transport Association Attorney- In-Fact



### -2
-

### CERTIFICATE OF SERVICE Acopy ofthis notice hasbeen served this day by firstclass orpriority mail onthe following person: Chief, Transportation, Energy & 

### Agriculture Section Antitrust Division Department ofJustice Washington, D.C. 20530

Acopy ofthis notice has been sent this day byemail toJohn Kiser (John.Kiser@dot.gov) andtoDella Davis (Della.Davis@dot.gov) ofthe Department ofTransportation.

/s/Douglas Lavin Douglas Lavin

26 September 2013 Date Served



### -3
- 13461343.\

### To: Copy: From: Date: Subject: 

# MEMORANDUM PSC/RESO/148 bis All Members, Passenger Services Conference -Accredited Representatives lATA Strategic Partners Head, Passenger Interline Standards 26 September 2013 "PASSENGER WEEK 2010" EXPEDITED RESOLUTIONS AND RECOMMENDED PRACTICES 30'h Joint ATAIIATA Passenger Services Conference (JPSC) 32"d lATA Passenger Services Conference (PSC) Geneva, 21 October 2010

Attached are the Expedited Resolutions & Recommended Practices which were adopted atthe above-mentioned Conference. The Minutes ofthe Conference are issued separately under Memorandum PSC/MINS/034 dated 15April 2011. The resolutions and RPs were originally circulated under cover of memorandum PSC/RESO/148 dated 29 October 2010. Subsequently they were filed wtth Governments, where required, except for the United States Department ofTransportation (DoT). The intended effective date was 

## 1 November 2010. The delay infiling these resolutions and RPs with the DoTwas in recognition of new procedures to create a "self-assessment" environment for PSC agreements. These new procedures were finally revealed at the PSC meeting in October 2012 (refer to agenda item P5 in the Minutes circulated under Memorandum PSC/MINS/042 dated 28 January 2013). The DoT Order 2012-4-18 provides for athree-tiered system for filing and implementation of PSC agreements. This memorandum will be filed with the DoT using procedures for "Tier 1".

Mike Muller International AirTransport Association


# . Route de l'Aeroport 33 PO Box 416 CH -1215 Geneva 15Airport Switzerland T01: +41 22 770 2525 Fax: +41 22 798 3553(PSC ITEM NBR.)
T6

T6

R3 

### OUTLINE OF CONTENTS

EXPEDITED RESOLUTIONS & 

### RECOMMENDED PRACTICES ADOPTED AT: 32nd 

### PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE:

(as indicated)
RESOLUTION & TITLE RECOMMENDED PRACTICE PSC(32)722f ELECTRONIC TICKET -AIRLINE (amending) [OST-2012-0058] 1November 2010 PSC(32)722g ELECTRONIC TICKET - NEUTRAL (amending) [OST-2012-0058] 1November 2010 PSC(32)1722z INHIBIT TICKETING FOR SECURITY REASONS (NEW) 1November 2010

## SUMMARY OF CHANGES EXPEDITED RESOLUTIONS 

### & RECOMMENDED PRACTICES ADOPTED AT: 32nd 

### PASSENGER SERVICES CONFERENCE (PSC)
RESOLUTION SUMMARY OF RESOLUTION SUMMARY OF AMENDMENT RESOLUTION Provides governing rules and Ticketing rules to support the action 722f technical specifications on how of inhibiting issuance oftickets that

to produce an Electronic Ticket are subject to minimum security ELECTRONIC TICKET (ET) issued by airlines. This data being present inthe Passenger

-AIRLINE allows tickets to be issued and Name Record (PNR).

exchanged without the issuance of paper value (i.e. accountable) documents. Also included are the applicable conditions for the issuance and honoring of such tickets. RESOLUTION Provides governing rules and Ticketing rules to support the action 722g technical specifications on how of inhibiting issuance oftickets that

to produce an Electronic Ticket are subject to minimum security ELECTRONIC TICKET (ET) issued bytravel agents. data being present in the Passenger

- NEUTRAL This allows tickets to be issued Name Record (PNR).

and exchanged without the issuance of paper value (i.e. accountable) documents. Also included are the applicable conditions for the issuance and honoring of such tickets. RECOMMENDED Provides guidelines regarding Establishment of a recommended PRACTICE 1722z high level system practice to provide guidelines to requirements to inhibit airlines and service providers to INHIBIT TICKETING ticketing for security reasons. cater for requirements of US FOR SECURITY legislation for "Secure Flight" and REASONS similar requirements likely to be forthcoming from other Governments.7221 T6 

### o PSC(~ 32)722f RESOLUTION 722f ELECTRONIC TICKET. AIRLINE

(amending) Expiry: Indefinite Type: B

Section 6 . Procedures 6.2. Issuance 6.2.1.2 Prior to ET issuance. the Validating Carrier shall validate that the minimum 'Secure Flight Passenger Data'. where applicable. is present inthe Passenger Name Record (PNR). Inthe absence ofthis information the Validating Carrier shall inhibit the ticketing transaction.

7229 T6 

### PSC(~ 32)722g

Section 6 . Procedures 6.2 Issuance RESOLUTION 7229 ELECTRONIC TICKET. NEUTRAL

(amending) Expiry: Indefinite

Type: B

6.2.2.2 Prior to ET issuance. the CRS/System Provider shall validate that the minimum 'Secure Flight Passenger Data'. where applicable. is present inthe Passenger Name Record (PNR). Inthe absence ofthis information the CRS/System Provider shall inhibit the ticketing transaction.

Filing Period: 1 November12 November2010 Effective Date: 

### 1 November2010

### RECOMMENDED PRACTICE 1722z INHIBIT TICKETING FOR SECURITY REASONS (new) R3 

### PSC(32) 1722z RECOMMENDED that: Members, or associated service providers, when issuing tickets, use the guidelines regarding high level system requirements to inhibit ticketing for security reasons as set forth below. 

### Note 

### 1:Allof these requirements are based on having the security indicator filed within the airline schedules. Forcode share, it

### is recommended that Marketing Carriers also file the security indicator with theirschedules. Note 2: Theminimum 3 data elements of Secure Flight Passenger Data (SFPD) that are required 72hours in advance ofdeparture by the TSA are: (1) FullName (2) Date ofbirth (3) Gender Note 

### 3: It

## is assumed, that with Product Participation Agreements where 

## a carrier does notparticipate in the booking system for this newproduct the rules willnot apply.
1. In a multi-carrier itinerary, regardless ofwho isvalidating, the ticket cannot be issued for any ofthe carriers until all required SFPD is present; irrespective ofwhether a reissue or revalidation is actioned, the same data element verification check will be performed. 2. Ifthe Marketing Carrier does not require it and the Operating Carrier does, the ticket may be issued without SFPD. 3. Ifthe Operating Carrier does not require it and the Marketing Carrier does, the ticket cannot be issued unless SFPD is present. 4. In a multi-passenger PNR, name select can be used to issue tickets for those passengers where SFPD exists. 5. Ifall passengers are selected and 1 doesn't have the required information, ticketing may be rejected for all passengers depending upon the system.6. On or before ticketing time, the booking office sending the ticketing request not only needs to validate the presence of SSR DOCS, but also ifthe required SFPD data elements ofthe SSR are present. 7. When there is an itinerary/schedule change, it is necessary to ensure that the mandatory SFPD elements are present before re-issuing/re-validating the ticket; therefore, it may be necessary to re-enter SSR DOCS. 8. Best practice would be to use non-automated SSR DOCS, DOCA and DOCO which would eliminate a lot ofthe potential issues when the booking source orthe Member is not able to automatically re-associate the SSR to the alternative segment. 9. At the time ofticketing, only the airline segments present in the itinerary which have been filed with the security indicator are considered in the eligibility check. 10.All the checks also apply to passive segments. SSR DOCS should be present inthe passive PNR. 11. The Validating Carrier does not need to perform security indicator validation during the processing ofthe TKTREQ. 12. Open segments are out ofscope.

Filing Period: 1 November12 November 2010 Effective Date: 1 November 2010