### BEFORE THE

DEPARTMENT OF TRANSPORTATION

WASHINGTON, D.C.

Notice of IATA Traffic Conference

Actions Tentatively Exempted

From Filing for Approval Docket OST

- 2012

- 0058

NOTICE OF TIER 1 AGREEMENTS FILING

BY THE

INTERNATIONAL AIR TRANSPORT ASSOC IATION

29 November 2013

Communications with respect to this

Document should be sent to

Douglas Lavin

Regional Vice President

– North America

International Air Transport Association

1201 F Street, NW, Suite 650

Washington, DC 20004

(202) 6 28

- 9292

### Summary DOCKET: DOT

- OST

- 2012

- 0058 DOT ORDER: None Requested

Date: 29 November 2013

Filing fee/IATA Acct: Waived by Order 2012

- 4

- 18, Appendix

A, Section D

US/UST involved Yes

Intended effective date: 1 January 201 4

Meeting site, date: 3 5 th 

### Passenger Services Conference

(PSC), Dublin 31 October

– 1 November

2013

Agreement(s)/Minutes PSC/RESO/1 62 dated 2 9 November 2013

Resolution 722f and Recommended

Practices 1708 and 1770

### NOTICE OF TIER 1 AGREEMENTS FILING

Pursuant to statements subm itted by Member airlines of the International Air Transport

Association (IATA), the undersigned has been constituted to be their attorney

- in

- fact for filing

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

Conferences.

On their behalf, and pursuant to the procedures specified in Order 2012

- 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 1 agreemen ts tentatively

exempted by Order 2012

- 4

- 18 from Condition #2 to the Department’s approval of the Provisions

for the Conduct of the IATA Traffic Conferences, which condition requires pre

- implementation

Department review. The intended effective date of the agreements is 1 January 2014

.

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 agreement s and other conference documentation sent to

airline Members of IATA 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 n umber. The cover pages include a summary to explain the nature and purpose

of the subject amendments and/or agreements.

### - 2

-

13461343.1 

### Respectfully submitted,

/s/ Douglas Lavin

Douglas Lavin

Regional Vice President

– North America

International Air Transport Association

Attorney

- In

- Fact

### - 3

-

13461343.1 

### CERTIFICATE OF SERVICE

A copy of this notice has been served this day by first class or priority mail on the

following person:

Chief, Transportation, Energy & Agriculture Section

Antitrust Division

Department of Justice

Washington, 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 Lavin

Douglas Lavin

29 November 2013

Date Served

### - 4

-

13461343.1

## M E M O R A N D U M

PSC/RESO/ 1 62

To: All Members, Passenger Services Conference

- Accredited

Representatives

Copy: IATA Strategic Partners

From: Head, Airline Distribution Standards

Date: 2 9 November 2013

Subject: EXPEDITED RESOLUTIONS & R EC OMMENDED PRACTICES

3 5 th IATA Passenger Services Conference (PSC)

Dublin, 31 October

– 1 November 2013

Attached are the expedited resolutions & recommended practices (RPs) which were adopted at the

above

- mentioned Conference.

The filing period is estab lished as 2

- 20 December 2013

. To ensure timely approval, Members are

requested to file these agreements, where required, with their Governments upon receipt of this

document and to advise this office (email: m cewend @iata.org ) of their Government’s action by the

end of the filing period ( 20 December 2013 )

.

Filing formalities with the Canadian Transportation Agency on behalf of Canadian Members will be

accomplished by this office.

Filing formalities with the United States Department of Transportation (DoT) on behalf of IATA

Members will be accomplished by IATA’s Regional Vice President, North America.

The intended effective date is 1 January 20 1 4

.

David McEwen International Air Transport Association

Route de l'Aeroport 33

PO Box 416

CH

- 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2 086

Fax: +41 22 770 2896

### OUTLINE OF CONTENTS

RESOLUTIONS & RECOMMENDED PRACTICES

ADOPTED AT:

3 5 th 

### PASS ENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 January 2014

Resolution/RP Title

PSC (3 5 ) 722f ELECTRONIC TICKET

– AIRLINE

(amending)

PSC (3 5 ) 1708 PASSENGER NAME LIST (PNL) AND ADDITIONS AND

DELETIONS LIST (ADL)

(amending)

P SC (3 5 )17 70 CODE OF RESERVATION ETHICS

(amending)

## SUMMARY OF CHANGES

RESOLUTIONS/RECOMMENDED PRACTICES ADOPTED AT:

3 5 th PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 January 2014

Resolution/

Recommended

Practice Summary of

Re solution/RP Summary of Amendment

RESOLUTION 722f

ELECTRONIC TICKET

– AIRLINE Provides governing rules

and technical specifications

on how to produce an

Electronic Ticket (ET) issued

by airlines. This allows

ticketing to be performed

without the issuance of

paper tickets. Also included

are the applicable conditions

for the issuance and

honoring of such tickets. Code OG is one of the 3 codes that

had been set aside for identifying

amounts attributed to a carbon offset

scheme. In view that this code has

nev er been used, it was agreed to

delete it.

RP 1708



### PASSENGER NAME

LIST (PNL) AND

ADDITIONS AND

DELETIONS LIST

(ADL) Provides the definitions,

formats and procedures for

the creation, transmission

and interpretation of

Passenger Name Lists

Messages and

Additions/Deletion Lists

Messages associated with

the passenger data

produced by an airline

reservations system. This proposal facilitates the collect ion

of customer contact information by

airlines and travel agents in a

structured manner, to enable the

ai rlines to provide better service to

passengers.

RP 1708 currently includes 2.12.6.3

Remarks Element for Passenger

Provided Contact Information. These

amendments clarifies that it is for

Emergency Contact information. A

new section is added for the

Pass enger Contact Information

Notification for Irregular Operations

.

R P 17 70

CODE OF

RESERVATION

ETHICS Guidelines to highlight the

responsibilities of airlines,

travel agents and computer

reservations systems

regarding best practices

when reserving seat s on

airlines for their customers. Updating the passenger reservations

guidelines regarding provision of

contact information to facilitate

notification for irregular operations , e.g.

in the event of cancellation or delay in

departure

.

### RESOLUTION 7 22f

ELECTRONIC TICKET

- AIRLINE

(amending)

PSC( 34 35 )722f Expiry: Indefinite

Type: B

RESOLVED that,

.... T2.7

Attachment ‘A’

ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS DATA ELEMENTS

GLOSSARY

**...** CARRIER FEE DATA

...

Carrier Fee Type

– 2 ALPHANUM ERIC

... OG = IATA Carbon Offset Scheme Service Code

...

Filing Period: Effective Date:

2 December

- 1 January 2014

20 December 2013

### RECOMMENDED PRACTICE 1708

PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS LIST (ADL)

(amending)

PSC ( 34 35 )1708

B13.4



### .....

2.12.6.3 Remarks Element for Passenger Provided Emergency Contact Information

2.12.6.3(a) The Remarks Element for passenger emergency contact information uses the IATA AIRIMP

standard code for passenger provided contact: PCTC.

2.12.6.3(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for psgr provided contact PCTC SSR/OSI code

space

– > information

separato r contact name (if provided) TOM ODOM aa(a...a)

oblique (mandatory) / information

separator

2

- or 3

- letter country designator and telephone NL31205551234 aa(a)nnn(n..n)

number (with country, area, and local)

(if provided)

oblique (i f free text follows) / information

separator

free text SECRETARY free flow text

passenger ID

- 1FULTON/ELLIE passenger ID

**Note 1:** When the passenger provided contact has been solicited but the passenger refuses to

provide one, the word ‘REFUSED’ is used in place of the country/telephone field and the free

text field is not present.

**Note 2:** When the passenger provided contact has been solicited but is not available, it will be

indicated by the mandatory obliques only. Free text may appe ar.

Examples:

2AHARA/JOSEPHMR/KENDRAMRS

.R/PCTC JOHN DOE/US1123456789/PHONE OF UNCLE AFTER 7PM

2.12.6.x Remarks Element for Passenger IROPS Contact Information

2.12.6.x(a) The Remarks Element for passenger IROPS contact mobile phone information uses th e IATA

AIRIMP standard code for passenger provided contact: CTCM.

2.12.6.x(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for psgr provided contact CTCM SSR/OSI cod e

space

– > information

separator

phone number (mobile phone) 1 2185251234 n (includes country, area, and local number)

oblique (if preferred language follows) / information

separator

(optional) p referred language EN aa

passenger ID

- 1ODOM/TOM passenger ID

Examples:

1GALLERY/ROGERMR

.R/CTCM 15074261812

2CUSACK/GREGG/JENNIFER

.R/CTCM 31206490123

- 1CUSACK/GREGG2.12.6.x(a) The Remarks Element for passenger IROPS email information uses the IATA AIRIMP standard

code for passen ger provided contact: CTCE.

2.12.6.x(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

SSR code for psgr provided contact CTCE SSR/OSI code

space

– > information separ ator

e

- mail address HOD.MAR//MSN.COM free flow text

2 obliques are used for the change symbol (@)

2 periods are used for an underscore (_)

oblique (if preferred language follows) / information separator

(optional) p referred language NL aa

passenger ID

- 1HOD/MAR passenger ID

Examples:

1RIVERA/JAMES

.R/CTCE JAMES1.RIVERA//GMAIL .COM

2KLEIN/DAVID/ANNE

.R/CTCE DAVID.VAN..KLEIN//YA HOO.COM

- 1KLEIN/DAVID

RP1708 add 2 new SSR codes in 2.12.7

CTCM

– passenger contact information mobile phone contact

CTCE

– passenger contact information email address

PCTC

– passenger emergency contact information

Filing Period: Effective Date:

2 December

- 1 January 2014

20 December 2013

### RECOMMENDED PRACTICE 1770

CODE OF RESERVATION ETHICS

(amending)

PSC( 12 35 )1770

R3.6

...

RECOMMENDED that:

1.To guarantee smooth handling of reservations and to avoid inconvenience to the

travelling public, travel agents and airlines, accurate records must be kept covering

all reservati ons transactions. These must include flight numbers, reservations

booking designators, date of travel, departure and arrival times, status of segments,

names and initials of passengers with their contact address and/or telephone

number, mobile phone number , e

- mail address, and ticketing status. When booking

or cancelling space, it is particularly important to ensure that the reservations

booking designator being used corresponds to the fare paid by the passenger.

...

2.1.5 Always attempt to establish a teleph one number, mobile phone number, e

- mail

address, with the passenger(s)

...

RESPONSIBILITY OF TRAVEL AGENTS

— BOTH AUTOMATED AND NON

AUTOMATED

... 3.2 always provide the airline or CRS with which they are making reservations with a

passenger contact. This should include the passengers’ telephone number, mobile

phone number and e

- mail address

. This enables operational notifications, e.g. flight

cancellation, schedule change, etc. to be sent to the passenger service during hours

when the Subscriber’s office is close d

.

...

Filing Period: Effective Date:

2 December

- 1 January 2014

20 December 2013