BEFORE THEDEPARTMENT OF TRANSPORTATION

WASHINGTON, D.C.

Notice of/AT A Traffic ConferenceActions Tentatively ExemptedFrom Filing for Approval

Docket OST-2012-0058

NOTICE OF TIER 1 AGREEMENTS FILINGBY THE

INTERNATIONAL AIR TRANSPORT ASSOCIATION

26 September 2013

Communications with respect to thisDocument should be sent to

Douglas LavinRegional Vice President - North AmericaInternational Air Transport Association1201 F Street, NW, Suite 650Washington, DC 20004(202) 628-9292

Date:

Summary DOCKET: DOT-OST-2012-0058 DOT ORDER: None Requested

26 September 2013

Filing feelIA TA Acct:

USIUST involved

Intended effective date:

Meeting site, date:

Agreement(s )lMinutes

Waived by Order 2012-4-18, AppendixA, Section D

Yes

I November 2010

320d Passenger Services Conference(PSC), Geneva, 21 October 2010

PSCIRESO/148 bis dated 26 September2013

PSCIMINS/034 dated 15 April 20 II

Resolutions 722f and 722g

Recommended Practice 1722z

NOTICE OF TIER I AGREEMENTS FILING

Pursuant to statements submitted by Member airlines of the International Air Transport

Association (lATA), the undersigned has been constituted to be their attorney-in-fact for filing

with the Department of Transportation copies of agreements adopted by the lATA Traffic

Conferences.

On their behalf, and pursuant to the procedures specified in Order 20 I2-4-18 (13 April

2012), I am filing with the Department, in Docket OST-2012-0058, this Notice, the subject

agreements and supporting documentation. These agreements are Tier I agreements tentatively

exempted by Order 2012-4-18 from Condition #2 to the Department's approval of the Provisions

for the Conduct of the lATA Traffic Conferences, which condition requires pre-implementation

Department review.

The subject agreements amend or establish Resolutions and/or Recommended Practices

that do not address subject areas which the Department has indicated it still chooses to review

under Condition #2. The text of the agreements and other conference documentation sent to

airline Members of lATA accompany this Notice. The cover pages of the documentation clearly

identify each affected Resolution and/or Recommended Practice and show whether the subject

agreements are amendments or new agreements. Other pages provide the text of each subject

agreement. Where an affected Resolution or Recommended Practice has previously been

exempted from Condition #2 by Department action, the cover pages include the appropriate

docket and order number. The cover pages include a summary to explain the nature and purpose

of the subject amendments and/or agreements.

13461343.1

Respectfully submitted,

/s/ Douglas LavinDouglas Lavin

Regional Vice President - North AmericaInternational Air Transport AssociationAttorney- In-Fact

- 2 -

CERTIFICATE OF SERVICE

A copy ofthis notice has been served this day by first class or priority mail on thefollowing person:

Chief, Transportation, Energy & Agriculture SectionAntitrust DivisionDepartment of JusticeWashington, D.C. 20530

A copy of this notice has been sent this day by email to John Kiser (John.Kiser@dot.gov)and to Della Davis (Della.Davis@dot.gov) of the Department of Transportation.

/s/ Douglas LavinDouglas Lavin

26 September 2013Date Served

- 3 -13461343.\

To:

Copy:

From:

Date:

Subject:

MEMORANDUMPSC/RESO/148 bis

All Members, Passenger Services Conference - AccreditedRepresentatives

lATA Strategic Partners

Head, Passenger Interline Standards

26 September 2013

"PASSENGER WEEK 2010"EXPEDITED RESOLUTIONS AND RECOMMENDED PRACTICES30'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 at theabove-mentioned Conference. The Minutes of the Conference are issued separately underMemorandum PSC/MINS/034 dated 15 April 2011.

The resolutions and RPs were originally circulated under cover of memorandum PSC/RESO/148dated 29 October 2010. Subsequently they were filed wtth Governments, where required, exceptfor the United States Department of Transportation (DoT). The intended effective date was 1November 2010.

The delay in filing these resolutions and RPs with the DoT was in recognition of new procedures tocreate a "self-assessment" environment for PSC agreements. These new procedures were finallyrevealed at the PSC meeting in October 2012 (refer to agenda item P5 in the Minutes circulatedunder Memorandum PSC/MINS/042 dated 28 January 2013).

The DoT Order 2012-4-18 provides for a three-tiered system for filing and implementation of PSCagreements. This memorandum will be filed with the DoT using procedures for "Tier 1".

Mike Muller

International Air Transport Association.Route de l'Aeroport 33PO Box 416CH -1215 Geneva 15 AirportSwitzerland

T01: +41 22 770 2525Fax: +41 22 798 3553

(PSCITEMNBR.)

T6

T6

R3

OUTLINE OF CONTENTS

EXPEDITED RESOLUTIONS & RECOMMENDED PRACTICES

ADOPTED AT:

32nd PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE:(as indicated)

RESOLUTION & TITLERECOMMENDEDPRACTICE

PSC(32)722f ELECTRONIC TICKET - AIRLINE(amending)

[OST-2012-0058]1 November 2010

PSC(32)722g ELECTRONIC TICKET - NEUTRAL(amending)

[OST-2012-0058]1 November 2010

PSC(32)1722z INHIBIT TICKETING FOR SECURITYREASONS

(NEW)

1 November 2010

SUMMARY OF CHANGES

EXPEDITED RESOLUTIONS & RECOMMENDED PRACTICESADOPTED AT:

32nd PASSENGER SERVICES CONFERENCE (PSC)

RESOLUTION SUMMARY OF RESOLUTION SUMMARY OF AMENDMENT

RESOLUTION Provides governing rules and Ticketing rules to support the action722f technical specifications on how of inhibiting issuance of tickets that

to produce an Electronic Ticket are subject to minimum securityELECTRONIC TICKET (ET) issued by airlines. This data being present in the Passenger

- AIRLINE allows tickets to be issued and Name Record (PNR).exchanged without theissuance of paper value (i.e.accountable) documents. Alsoincluded are the applicableconditions for the issuanceand honoring of such tickets.

RESOLUTION Provides governing rules and Ticketing rules to support the action722g technical specifications on how of inhibiting issuance of tickets that

to produce an Electronic Ticket are subject to minimum securityELECTRONIC TICKET (ET) issued by travel agents. data being present in the Passenger

- NEUTRAL This allows tickets to be issued Name Record (PNR).and exchanged without theissuance of paper value (i.e.accountable) documents. Alsoincluded are the applicableconditions for the issuanceand honoring of such tickets.

RECOMMENDED Provides guidelines regarding Establishment of a recommendedPRACTICE 1722z high level system practice to provide guidelines to

requirements to inhibit airlines and service providers toINHIBIT TICKETING ticketing for security reasons. cater for requirements of USFOR SECURITY legislation for "Secure Flight" and

REASONS similar requirements likely to beforthcoming from otherGovernments.

7221 T6 o

PSC(~ 32)722f

RESOLUTION 722fELECTRONIC TICKET. AIRLINE

(amending)

Expiry: IndefiniteType: 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 in the Passenger NameRecord (PNR). In the absence of this information the Validating Carrier shall inhibitthe ticketing transaction.

7229 T6

PSC(~ 32)722g

Section 6 . Procedures

6.2 Issuance

RESOLUTION 7229ELECTRONIC TICKET. NEUTRAL

(amending)

Expiry: IndefiniteType: B

6.2.2.2 Prior to ET issuance. the CRS/System Provider shall validate that theminimum 'Secure Flight Passenger Data'. where applicable. is present in thePassenger Name Record (PNR). In the absence of this information the CRS/SystemProvider shall inhibit the ticketing transaction.

Filing Period:1 November-12 November 2010

Effective Date:1 November 2010

RECOMMENDED PRACTICE 1722zINHIBIT TICKETING FOR SECURITY REASONS

(new)R3

PSC(32) 1722z

RECOMMENDED that:

Members, or associated service providers, when issuing tickets, use the guidelinesregarding high level system requirements to inhibit ticketing for security reasons asset forth below.

Note 1:All of these requirements are based on having the security indicator filedwithin the airline schedules. For code share, it is recommended that MarketingCarriers also file the security indicator with their schedules.

Note 2: The minimum 3 data elements of Secure Flight Passenger Data (SFPD)that are required 72 hours in advance of departure by the TSA are:(1) Full Name(2) Date of birth(3) Gender

Note 3: It is assumed, that with Product Participation Agreements where a carrierdoes not participate in the booking system for this new product the rules will notapply.

1. In a multi-carrier itinerary, regardless of who is validating, the ticket cannot be issuedfor any of the carriers until all required SFPD is present; irrespective of whether areissue or revalidation is actioned, the same data element verification check will beperformed.

2. If the Marketing Carrier does not require it and the Operating Carrier does, the ticketmay be issued without SFPD.

3. If the Operating Carrier does not require it and the Marketing Carrier does, the ticketcannot be issued unless SFPD is present.

4. In a multi-passenger PNR, name select can be used to issue tickets for thosepassengers where SFPD exists.

5. If all passengers are selected and 1 doesn't have the required information, ticketingmay be rejected for all passengers depending upon the system.

6. On or before ticketing time, the booking office sending the ticketing request not onlyneeds to validate the presence of SSR DOCS, but also if the required SFPD dataelements of the SSR are present.

7. When there is an itinerary/schedule change, it is necessary to ensure that themandatory 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 whichwould eliminate a lot of the potential issues when the booking source or the Memberis not able to automatically re-associate the SSR to the alternative segment.

9. At the time of ticketing, only the airline segments present in the itinerary which havebeen 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 in thepassive PNR.

11. The Validating Carrier does not need to perform security indicator validation duringthe processing of the TKTREQ.

12. Open segments are out of scope.

Filing Period:1 November-12 November 2010

Effective Date:1 November 2010