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 ASSOCIATION

29 January 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) 628-9292
Summary DOCKET: DOT-OST-2012-0058 DOT ORDER: None Requested

Date: 29 January 2013

Filing fee/IATA Acct: Waived by Order 2012-4-18, Appendix 

A, Section D

US/UST involved Yes

Intended effective date: 1 June 2013

Meeting site, date: 34th Passenger Services Conference 

(PSC), Abu Dhabi, 18-19 October 2012

Agreement(s)/Minutes PSC/RESO/154 dated 28 January 2013

Resolutions 003, 720, 720a, 722, 722a, 

722c, 722f, 722g, 722h, 725a, 725b, 

725f, 725g, 725h, 726a, 726e, 726f, 727, 

728, 735, 735d, 742c, 742d, 746, 751, 

760a, 780 and 780e.

Recommended Practices 1701j, 1706a, 

1707a, 1707b, 1708, 1719, 1719b, 1719e, 

1735, 1745, 1761a, 1777, 1779, 1786, 

1788, 1790, 1791d, 1797, 1797a and 

1800.
NOTICE OF TIER 1 AGREEMENTS FILING

Pursuant to statements submitted 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 agreements 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 June 2013. 

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 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 number. 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 January 2013

Date Served
-

4- 13461343.1
MINUTES

32nd Joint A4A/IATA Passenger Services Conference (JPSC)

34th IATA Passenger Services Conference (PSC)

Abu Dhabi

18-19 October 2012

International Air Transport Association

Route de l’Aeroport 33

PO Box 416

CH - 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2731

Fax +41 22 770 2896

www.iata.org E-Mail: mullerm@iata.org

M E M O R A N D U M

PSC/MINS/042

TO: All Members, Passenger Services Conference - Accredited 

Representatives

All Members, Joint A4A/IATA Passenger Services Conference -

Accredited Representatives (A4A members via Ms P. Edwards)

COPY: IATA Strategic Partners

FROM: Head, Interline & Intermodal Policy

DATE: 28 January 2013

SUBJECT: MINUTES

32nd Joint A4A/IATA Passenger Services Conference (JPSC)

34th IATA Passenger Services Conference (PSC)

Abu Dhabi, 18-19 October 2012

Please find attached the Minutes of the 32nd Joint A4A/IATA Passenger Services 

Conference (JPSC) and the 34th IATA Passenger Services Conference (PSC) as 

approved by the Chairman.

The “expedited resolutions and recommended practices” referred to in these Minutes 

are issued under cover of Memorandum PSC/RESO/153 dated 30 October 2012.

The “book of finally adopted resolutions & RPs – Part 1” is issued under cover of 

Memorandum PSC/RESO/154 dated 28 January 2013.

The “book of finally adopted resolutions & RPs – Part 2” regarding Resolution 787 is

issued under cover of Memorandum PSC/RESO/156 dated 28 January 2013.

Michael Muller

M I N U T E S

32nd Joint A4A/IATA Passenger Services Conference (JPSC)

34th IATA Passenger Services Conference (PSC)

Abu Dhabi, 18-19 October 2012

TABLE OF CONTENTS

ADMINISTRATION

Agenda 

Item

Subject Page 

Number

A1 Opening of Meeting 1

A2 Examination of Credentials of Accredited 

Representatives

1

A3 Approval of Minutes – JPSC/31 and PSC/33 1

A4 Status of PSC Resolutions and RPs 1

A5 Effectiveness Date of Amendments to Industry 

Standards

1

A6 Any Other Business 2

A7 Date and Place of Next Meeting 2

POLICY

P1 Report – Status of Industry Coding Systems 2

P2 Ratification of Special Fees and Charges Codes (Resolution 728) 2

P2.1 Ratification of Credit Card Code (Resolution 728) 2
P2.2 High-Level Document Regarding Change of Resolution 762 3

P3 Report – BSP Form Codes and Document Supply Chain 3

P4 Report – Coding Working Group (CODEWG) 3

P5 Co-ordination with the US Department of Transportation (DoT) –

Initiative for Self-Assessment

4

P6 Report – Simplifying the Business (StB) and Think Tank 5

P6.1 Report – IATA e-services 5

P6.2 Report - Baggage Improvement Program (BIP) and Baggage 

Quality Program (BQP)

5

P6.3 Report – Fast Travel / Passenger Experience Working Group 

(PEMG)

5

P6.3.1 Automated and Self-Service Flight Rebooking for Irregular 

Operations (RP1701j)

6

P6.4 Report – Passenger Facilitation 6

P6.5 Report – Checkpoint of the Future 6

P6.6 Report – New Distribution Capability (NDC) 6

P7 Report – Passenger Distribution Group (PDG) 7

P7.1 Resolution 787 – Proposed Amendment 9

P8 Co-ordination with the Commission of European Communities 

(CEC) on PSC Matters

9

P9 Report – Expert Advisory Task Force (EATF) on Industry 

Messaging Standards

9

P10 Report – PCI DSS Working Group (PDWG) 10

P11 Report – Involuntary Rerouting Working Group (IRWG) 10

P12 Airline Distribution: End-to-End Process Lifecycle 10
AIRPORT SERVICES

B1 Report of the Airport Services Committee (ASC) 11

B2 Report of the A4A Baggage Committee 11

B3 Report of the IATA Ground Handling Council 

(IGHC)

11

B4 Report of the Baggage Working Group (BWG) 11

B5 Report of the Baggage Steering Group (BSG) 11

B6 Mishandled Baggage Article 4 in Resolutions 

780/780e

12

B6.1 Pro Rate of International Travel (Resolution 780e) 12

B7 New Resolution 751 - Use of 10 digit Licence 

plate

12

B8/P Baggage Working Group “Package” 12

B8.1/P Format description of the aircraft compartment in 

the .U element 13

B8.2/P Retain the .L and .K elements as an optional 

element in RP1745 13

B8.3/P Editorial Issues in RP1800 = BPM .I element is 

conditional for all processes 13

B8.4/P Editorial Issues in RP1800 – BTM DEL 

inconsistency in documentation 13
B8.5/P Restoration of the “H” designator in .J element 14

B8.6/P Standardized Code .E/CUST for bags to be 

inspected by customs to be used in RP1800 

Offload / Reload process and in RP1745 BUM

14

B8.7/P RP1800 Self-Service Tagging Proposal and 

Amendments

14

B9 Report of the DCS Messages Working Group 

(DCSMWG)

14

B10/P DCS Messages Working Group “Package” 14

B10.1/P Clarification of “NOSHO” 14

B10.2/P

Credit Card as FOID 14

B10.3/P Chargeable Family SSRs 15

B11 Add Additional Service Remark Format 15

B12 Post Departure Message Requirements for 

Additional Services

15

B13 Clarification of “GOSHN” & “GOSHO” 15

B14 RP 1797 and RP 1797a 15
TICKETING

T1 Report of the Ticketing Committee

Selection of Committee Membership for the IATA 

Ticketing Committee (TKTcom)

16

T2/P Ticketing “Package” 16

T2.1/P New Example of Validity for Exchanges 16

T2.2/P Tour Code Box Required for Staff Travel 17

T2.3/P Editorial Change: Optimize the Process to Provide the 

Actual Coupon Status in Display Response

17

T2.4/P Reissued Flown Ticket/Document Number and Date of 

Issue

17

T2.5/P Single Matching Item and Multiple Matching Items

Display

17

T2.6/P Revise System Update Message Construction Matrices 18

T2.7/P Add System Update to ET Ground Handler Message 

Construction Matrix

18

T2.8/P Deletion of IDEC Requirement for Interline Billing 18

T2.9/P Add ABR (Automated Baggage Rule) Additional 

Information to the Electronic Ticket Record

19

T2.10/P Add ABR( Automated Baggage Rule) MSC Information 

to the Electronic Ticket Record

19
T2.11/P Application of Free Baggage Allowance/Excess 

Baggage Charges in case of IROP

19

T2.12/P Changes to All Resolutions – Baggage Allowance 19

T2.13/P Allow Travel Agents to Re-Associate EMD-A After 

Ticket Reissue

19

T2.14/P Statistical Code Definition Amendment 20

T2.15/P Not Valid After and Not Valid Before Date on EMD-S 20

T2.16/P Addition of Attribute Group and Attribute Sub-Group to 

EMD Unsolicited Billing Request

20

T2.17/P Add Product Characteristics to EMD Unsolicited Billing 

Request

20

T2.18/P Allow Access to the ET Issued by Airline in Exchange 

for Agent Original ET

21

T2.19/P New Routing Indicator Domestic vs. International 21

T2.20/P Remove Remaining References to Sundry Charges 21

T2.21/P Revision of SAPP (Source of Approval Code) Values 21

T2.22/P Editorial Changes to RP1790/A4A10.90 22

 T3 Itinerary and EMD Fee Calculation 22

 T4 Deletion of Ticketing Provisions for Euro Transition 22

 T5 New Schedule Change Recommended Practice 22

 T6 Imprint correct name in “Name of Passenger” box and 

“Passenger Name” field

23

 T7 Add ‘Remarks’ to 725g Message Construction Matrix 23

 T8 Complimentary Amendments to Resolution 722f 23
RESERVATIONS

R1 Report – A4A/IATA Reservations Committee 

(ResCom)

23

R2 Report – Reservations Working Group 

(RESWG) 

24

R3 Chargeable Family SSRs 24

R4/P Reservations “Package” 24

R4.1/P Amend Description of Miscellaneous RBDs 25

R4.2/P Contact Information in OSI 25

R4.3/P Credit Card as FOID 25

R4.4/P Moveable Arm Rest Characteristics – Seat 

Map and Seat Request

25

R4.5/P PNR Update Message to Advise EMD 

Number

25

R4.6/P SSR ASVC Related to Seats on Change of 

Gauge Flight

26

R4.7/P Review of RP 1762 on Reconfirmation 

Procedures

26

R4.8/P Rewrite Chapter 3.19 Pre-Reserved Seat 

Selection and Boarding Pass Notification

26

R4.9/P Editorials to Construction of OSI 26

R4.10/P Online Married Segment Control 26

R4.11/P Full PNR Itinerary Information 27
R4.12/P Add a Definition to Codes HHL and CCR 27

R4.13/P SSR ASVC and Service Cancellation after 

Issuance

27

R4.14/P Cancelling SSR Elements by the Member 27

R4.15/P Use of SSR ADTK to Request Ticket Number 

for Ticketing Time Limit

27

R5 Electronic Reservation Services Providers 

(ERSPs)

28

MISCELLANEOUS

M1 Report - PSC Steering Group (PSCSG) 28

M2 Report - PADIS Board (PADIS) 28

M2.1 Report – PNRGOV Working Group 28

M3 Report - Cargo Services Conference (CSC) 28

M4 Report – Worldwide Airport Slots 29

M4.1 Report - Schedules Information Standards Committee (SISC) 29

M4.2 Guidelines for the Allocation of Airport Slots 29

M5 Report – Fraud Prevention Working Group (FPWG) 29

M6 Report – BSP Data Interchange Standards Group (BDISG) 29

M7 Report – Strategic Partnerships 29

M8 Report – Travel Partners Standards Council (TPSC) 29

M9 Report - Agency Solutions Technical Working Group (ASTWG) 30

M10 Customer Satisfaction Surveys 30

Close of Meeting 30
1

MINUTES

32nd Joint A4A/IATA Passenger Services Conference (JPSC)

34th IATA Passenger Services Conference (PSC)

Abu Dhabi, 18-19 October 2012

ADMINISTRATION

A1 Opening of Meeting

1. The Chairman, Mrs. Patricia George, opened the 32nd Joint A4A/IATA

Passenger Services Conference (JPSC) and the 34th IATA Passenger

Services Conference (PSC) at 1400 hours on 18 October 2012. She

introduced Rosalie Crabbe (UA), Chairperson of the A4A Passenger Council. 

The attendance list is shown in Attachment A.

2. The Chairman advised the meeting that the coffee breaks and lunch breaks 

would be generously sponsored by Etihad Airways.

3. Conference noted the anti-trust warnings regarding discussion on

competitively sensitive topics as well as meeting guidelines for the Chairman

and delegates.

A2 Examination of Credentials of Accredited Representatives

4. Conference noted the list of IATA PSC accredited representatives and A4A

Passenger Council representatives.

A3 Approval of Minutes – JPSC/31 and PSC/33

5. Conference approved as published the Minutes from the 31st meeting of the

JPSC and 33rd meeting of the PSC.

A4 Status of PSC Resolutions & RPs

6. The Secretary, Mr Mike Muller (IATA), reported that he had filed the very first 

PSC agreement as a “Tier 1” filing in master docket OST-20112-0058 (refer 

to agenda item P5 for more details).

A5 Effectiveness Date of Amendments to Industry Standards

7. Conference confirmed that the general effective date of 1 June 2013 would

apply to all amendments regarding Resolutions, RPs and AIRIMP unless

otherwise agreed.
2

A6 Any Other Business

8. No other business was presented.

A7 Date and Place of Next Meeting

9. The Secretary advised that it is planned to hold the next meeting in

conjunction with the World Passenger Symposium in October 2013. Final

confirmation of dates and venue will be advised.

Secretary note: it has been decided to hold the 2013 JPSC/PSC meeting 

in Dublin, Ireland during the week of 28 October. To see the “week at a 

glance” schedule for standards setting conferences please refer to folder 

“PSC 35” in the extranet site: http://www.iata.org/whatwedo/workgroups/Pages/psc.aspx

Secretary note: for online information regarding IATA meetings, refer to: http://www.iata.org/whatwedo/workgroups/Pages/calendar.aspx

POLICY

P1 Report – Status of Industry Coding Systems

10.Conference noted this report.

P2 Ratification of Special Fees and Charges Codes (Resolution 728)

11.Conference agreed to ratify the list of codes shown in Attachment B that

had been assigned on a provisional basis since the last meeting of the JPSC

in October 2011. The Secretary advised that there are only 16 alpha/alpha 

codes remaining in the stock together with 4 frozen codes. Airlines and 

system providers confirmed that their systems had already been updated to 

accept alpha/numeric codes.

P2.1 Ratification of Credit Card Code (Resolution 728)

12.Conference agreed to amend Resolution 728 with the addition of code UP to 

identify China UnionPay as an international payment card. The changes to 

Resolution 728 are shown in the book of finally adopted resolutions & RPs, 

published separately. The A4A Passenger Council adopted counterpart 

changes to SIPP Resolution 110.16.
3

P2.2 High-Level Document Regarding Change of Resolution 762

13.Mr Jorg Troester (Hahn Air) advised that the paper regarding Global 

Consolidation Services (GCS) providers was not for voting at this time. 

Rather he proposed that it be forwarded to the Coding Working Group 

(CODEWG) to determine if it would be possible to make changes to 

Resolution 762 that would allow CRS codes to be used to display flight 

information and fares. Mr Jim Erickson (Navitaire) confirmed that he was 

interested in the concept and would support further discussions. Conference 

agreed to send the paper to the CODEWG.

ACTION: CODEWG

P3 Report – BSP Form Codes and Document Supply Chain

14.Mr Dave McEwen (IATA) advised that all existing form codes had been 

allocated, whereas in the past several had been set aside and annotated 

“reserved for future industry allocation”. He reported that he expected an 

explosion of form code usage due to a sharp increase in issuance of EMDs 

to cater for the new products and services sold as “ancillary services”.

15.Accordingly he urged the Conference to be forward looking and start 

researching which form codes could be re-allocated in view of the phasing 

out of paper documents by the industry deadline of April 2016. Moreover he 

believed that form code “0” held great promise in view that it was unlikely 

that a billion form codes would be required by each airline for non-standard 

documents.

16.Conference acknowledged the emerging problem and directed the Ticketing 

Committee (TKTcom) to start exploring a transition for parts of form code “0” 

and other paper form codes to cater for the likely explosion of requirements 

for airline EMD and OPEMD numbers.

ACTION: TKTcom

P4 Report – Coding Working Group (CODEWG)

17.Conference agreed that the CODEWG should continue its mandate and in 

2013 focus on developing workable solutions for problematic metropolitan 

areas and multiple city locations. 

Secretary note: the next meeting is scheduled to take place in Miami on

13-15 February 2013.
4

P5 Co-ordination with the US Department of Transportation (DoT) –

Initiative for Self-Assessment

18.The Secretary advised that the US Department of Transportation (DoT), in a 

huge vote-of-confidence in the pro-competitive nature of our standards 

setting process, had agreed with the IATA proposal to exempt the majority of 

Passenger and Cargo Conference agreements from the obligation to 

undergo prior DoT review. Refer to DoT Order 2012-4-18, by searching 

online for Order 2012-4-18 here: http://www.regulations.gov/#!home;tab=search This

means the industry can start implementation after IATA has provided 30 

days’ notice to the DoT. This is in contrast to the former system which often 

resulted in waiting many months for the review process to be completed. 

19.The Secretary reported that the process started in 2009 when IATA had 

opened dialogue with the US DoT regarding the development of new 

procedures to create a “self-assessment” environment. This concept was for 

all PSC agreements (with a few exceptions) to be provided to the DoT for 

“information only”. The huge advantage to this new system would be that 

the PSC would no longer suffer delays to implementation regarding the vast 

majority of standards. However, PSC activities would need to be even more 

closely monitored by IATA Legal to ensure that Conference activity remains 

consistent with US law. This is in recognition that the US DoT does not 

provide anti-trust immunity to any standards that have been filed for 

“information only”.

20.The Secretary highlighted that DoT Order 2012-4-18 provides for a threetiered system for filing and implementation of PSC agreements as follows.

Tier 3 Agreements

It is rare that the PSC would wish to use procedures for “Tier 3” 

because this is limited to subjects where IATA would be specifically 

seeking approval, or approval and antitrust immunity.

Tier 2 Agreements

A small amount of PSC agreements will need to be filed using the 

procedures for “Tier 2” which require review by the DoT as shown in 

Attachment C. This would be similar to the traditional way of filing 

whereby the DoT has no time limit within which to respond and IATA 

would seek an exemption or an approval on the agreement.

It is important to note that the PSC would also need to use Tier 2 

procedures for new agreements that address substantially similar 

subjects, e.g. ticket notices, conditions of carriage, and carriage of 

passengers requiring special assistance.
5

Tier 1 Agreements

The vast majority of PSC agreements will henceforth be filed using 

the procedures for “Tier 1” which means submission at least 30 days 

prior to the intended effective date. This would allow the DoT and 

other interested parties a minimum of 30 days to review each 

agreement. If DoT does not react within 30 days then IATA may 

declare the agreement effective, but such agreements would not 

enjoy antitrust immunity.

However, within the 30 day filing period it is worth noting that the DoT 

has the ability to insist on a longer period of reflection. Or the DoT 

could direct IATA to file all or parts of the agreements in the traditional 

way for review (i.e. Tier 2 or Tier 3).

21.The Secretary confirmed that during 2013 he would be filing PSC 

agreements that he had been holding in abeyance for the last 3 years in 

anticipation of this action by the US DoT. 

ACTION: Secretary

P6 Report – Simplifying the Business (StB) and Think Tank

22.Conference noted the report and the launching of three new StB projects 

regarding Passenger Facilitation, Checkpoint of the Future and New 

Distribution Capability (refer to agenda items P6.4, P6.5 and P6.6). 

Regarding the Think Tank, the Secretary noted that an updated “white 

paper” had been produced to deliver 5 goals that aim to change the 

passenger experience and revolutionize passenger travel by 2020 as shown 

in Attachment D.

Secretary note: for more information on StB initiatives please refer to:

http://www.iata.org/whatwedo/stb/Pages/index.aspx

P6.1 Report – IATA e-services

23.Conference noted this report.

P6.2 Report - Baggage Improvement Program (BIP) and Baggage Quality 

Program (BQP)

24.Conference noted this report and that the BIP project closes at the end of 

2012.

P6.3 Report – Fast Travel / Passenger Experience Working Group (PEMG)

25.Conference noted this report.
6

P6.3.1 Automated and Self-Service Flight Rebooking for Irregular 

Operations (RP1701j)

26.In 2011 the Fast Travel Working Group developed Recommended Practice 

1701j - Automated and Self-Service Flight Rebooking for Irregular 

Operations. Subsequently RP1701j was reviewed by representatives of the 

Ticketing Committee and the Reservations Committee who proposed minor 

changes regarding irregular operations management. The PSC agreed to 

change RP 1701j as shown in the book of finally adopted resolutions & RPs. 

The A4A Secretary advised that they will review this at their next meeting of 

the Passenger Council.

ACTION: A4A Passenger Council

P6.4 Report – Passenger Facilitation

27.Conference noted this report.

P6.5 Report – Checkpoint of the Future

28.Conference noted this report.

P6.6 Report – New Distribution Capability (NDC)

29.Mr Eric Leopold, IATA Director Passenger, advised that IATA had formed a 

new section to drive the establishment of industry standards to support and 

shape a new airline distribution capability. At the core of NDC is the 

development of a new data exchange standard based on XML for use in the 

distribution of airline products and services. Resolution 787 is designed to 

support the development of an open XML-based data exchange standard to 

eventually replace the outdated TELETYPE and EDIFACT based data 

exchange standards. This common language will in turn enable the New 

Distribution Capability, a set of business processes that will allow airlines to 

present robust offers to consumers via both direct and indirect channels.

30.The new standards will aim to offer more choice, transparency and 

personalization to consumers by stimulating innovation and competition in 

the distribution space. Mr Leopold noted that airlines could do this quite well 

today via their own websites but found great difficulty in providing the same 

experience when selling via third parties. Therefore many airlines wanted to 

raise themselves to the next level of retailing and merchandising, looking at 

models such as Amazon.com.

31.He reported that the IATA Board of Governors launched this initiative as one 

of the 2012 Industry Priorities with a goal to first deliver a foundational 

standard in the form of an industry resolution to provide a high-level 

framework for airlines to move to a dynamic content distribution model. This 

would allow airlines to take advantage of new technologies and start selling 

their products in a similar way through all distribution channels, whether they 

be direct sales (e.g. airline’s own website) or indirect sales (e.g. via a travel 

agent).
7

32.Mr Leopold described the high level scope of the new airline distribution 

model as follows.

• Change how an airline distributes its products and services

• Airline responds with price, constructs the offer and intermediary 

aggregates

• Collaboration across the industry – open and transparent process 

• The relationship airline-customer is more interactive

• The airline knows who is requesting the offer

• Offer the ability to sell what airline wants, to who they want, through 

more channels

33.He described the industry benefits as follows.

For Passengers:

• Greater transparency of what they are buying 

• Ability to compare airline offerings - different kinds of seats, for 

example 

• Recognition by airlines and potentially preferred and personalized 

products, prices or availabilities

For Airlines:

• Ability to differentiate their product offerings, gaining value from

investment in product quality 

• Greater ability to recognize and reward customers 

• Increased competition in the area of distribution (system providers 

which will stimulate further innovation, improving the value offered by 

the indirect channel)

For Travel agents:

• Greater access to airline ancillary products, some of which currently 

are only available on individual airline websites 

• Will have the ability to show, and therefore sell, the value of the 

proposition, not just standard seats 

• Increased competition in the area of distribution will mean more 

innovation and more choice for travel agents 

• Simplified and quicker shopping and booking process for the end-toend journey

34.Accordingly IATA’s initial role would be to bring together airlines, the travel 

trade, GDSs and other third parties to develop industry standards, starting 

with the “shopping” experience. He advised that an industry business case 

and associated 5 year roadmap would be presented to the IATA Board of 

Governors in December 2012. Conference noted this report with interest.

P7 Report – Passenger Distribution Group (PDG)

35.The Secretary reported that the PDG had been established by the PSC in 

2011. Since that time, member representatives had been defining the vision 

of a new distribution capability where requests come to airlines who will 

respond with an offer for their product. This is considerably different to the 

existing model where content is “pushed” to systems (e.g. schedules, fares 

and availability) and the offer is created without direct involvement of the 

carriers.
8

36.The rationale behind the new distribution capability is to increase 

competition, stimulate innovation, reduce distribution costs and improve 

consumer choice. The PDG had defined a set of key business principles 

which would allow carriers to more dynamically interact with the customer 

behind intermediaries in order to provide access to a much wider range of 

products and services across a much wider number of distribution channel 

providers where currently they may only be provided through “direct”

channels (e.g. airlines’ own websites). 

37.The requirement that had been identified was for a foundational standard 

that gives a clear industry direction on how to approach a more “shopping 

and comparison” based travel purchase experience that goes beyond the 

current publication of schedules and fares, and the location of key records 

such as an airline booking in a traditional reservations and ticketing 

environment.

38.At the request of the PDG, the first meeting of the Data Exchange Working 

Group (DDXWG) had been held during 9-13 July in Geneva where business 

scenarios were explored and some business requirements for data 

exchange standards formulated. The DDXWG included representatives from 

airlines, IT system providers, Global Distribution Systems (GDS), Online 

Travel Agency (OTA) and a Travel Management Company (TMC).

Conference was advised that subsequently various webinars had been 

provided to the industry to provide more detailed information as shown in 

Attachment E.

39.The PDG therefore drafted a proposal for a new Enhanced Airline 

Distribution resolution to initially cover only the concept of the business 

requirement, being a foundational resolution to provide an industry 

framework for “authenticated shopping”. It was noted that Resolution 787 

would be a platform to enable further resolutions and messaging standards 

to be developed as more business requirements are evaluated. 

40.AC, AF, AZ, AY, DL, LH and LX voiced strong support for the establishment 

of Resolution 787. FI urged IATA to ensure that small and medium sized 

carriers would be encouraged to join in the activities surrounding the 

development of industry standards regarding Enhanced Airline Distribution. 

JL advised that they had invested heavily in the current distribution system 

and therefore it would be important to ensure that transition to any new 

distribution system would be on a voluntary basis.

41.Regarding voting for the establishment of Resolution 787, the Chairman saw

no opposition from the PSC and noted abstentions from JL and TK. 

Accordingly Resolution 787 was adopted as shown in the book of finally 

adopted resolutions & RPs (Part 2). The A4A Secretary advised that they 

will review this at their next meeting of the Passenger Council.

ACTION: A4A Passenger Council

42.Conference agreed to extend the mandate of the PDG for a further 12 

months with terms of reference as shown in Attachment F. 
9

P7.1 Resolution 787 – Proposed Amendment

43.JL proposed to add an extra “key principle” to Resolution 787 to ensure that

“any cost attributable to this new business model, from IT research 

development to implementation/operation, will not be incumbent on Members 

who do not wish to adopt it”. JL felt that it was important to have this 

clarification enshrined in Resolution 787 in order that airlines not interested 

in this initiative would not be obliged to convert any of their systems unless 

they determined there would be an appropriate benefit.

44.Mr Tim Powell (Sabre) noted that whereas it is too early to be able to 

estimate costs by any individual supplier or airline, implementation is not 

mandatory as per the opening language of Resolution 787. Accordingly, 

noting the abstention of HR, the PSC adopted new paragraph 1.2.9 in 

Resolution 787 as shown in the book of finally adopted resolutions & RPs 

(Part 2). The A4A Secretary advised that they will review this at their next 

meeting of the Passenger Council.

ACTION: A4A Passenger Council

P8 Co-ordination with the Commission of European Communities (CEC) 

on PSC Matters

45.Conference noted this report.

P9 Report – Expert Advisory Task Force (EATF) on Industry Messaging 

Standards

46.Ms Marie Zitkova (IATA) reminded Conference that in 2011 the JPSC had 

established an Expert Advisory Task Force (EATF) with a mandate to advise 

on the strategy for the development of messaging standards in the area of 

passenger services and the future role of Passenger Airline Data 

Interchange Standards (PADIS) Board, operating under the Resolution 783. 

Driving concern for this review was the lack of direct airline involvement in 

the PADIS activities. Two industry surveys carried out by EATF confirmed 

that both airlines and IT providers rate highly the value of building an industry 

data dictionary and associated data model, one of the key recommendations 

considered by the EATF, and that they wish to leverage IATA to address 

common issues in the area of communications.

47.Conference noted the findings of the surveys and endorsed the position of 

PADIS as a common, application- and technology-agnostic, service to 

accommodate requests for data and data exchange standardization. 

Moreover, Conference agreed that the key responsibility of the PADIS Board 

should be to ensure the interoperability of data exchange standards across 

all relevant business domains and the interoperability with airlines’ business 

partners.
10

48.The EATF proposed the establishment of two permanent committees, the 

Data Dictionary and Schema Coordination Committee (DDSCC) responsible 

for semantic interoperability, and the Communications Protocols 

Coordination Committee (CPCC) responsible for facilitating interoperability 

on the implementation level (including data security). This was opposed by 

LH and UA due to lack of transparency on timelines for deliverables. 

Accordingly Conference agreed to establish the DDSCC and CPCC with a 

one year mandate with terms of reference as shown in Attachment G and 

requested that the transition of current EDIFACT activities to the new model 

is delayed by at least the next 12 months.

49.Conference agreed to extend the mandate of the EATF by 12 months. KL 

urged IATA to contact airline CIOs with a request that they nominate 

appropriate staff to lead PADIS activities.

ACTION: PADIS Secretary

P10 Report – PCI DSS Working Group (PDWG)

50.Conference noted this report and agreed to establish RP 1791d for Payment 

Card Industry Data Security Standards (PCI DSS) Compliance as shown in 

the book of finally adopted resolutions & RPs. The A4A Secretary advised 

that they will review this at their next meeting of the Passenger Council.

ACTION: A4A Passenger Council

51.Whereas it was agreed to disband the PCI DSS Working Group (PDWG), it 

was noted by BA that there is still a considerable amount of work to be done 

that could affect industry standards and therefore he urged IATA to provide 

regular updates to the JPSC and the PAConf. This was agreed.

ACTION: Program Manager, PCI DSS

P11 Report – Involuntary Rerouting Working Group (IRWG)

52.The Chairman of the IRWG, Ms Mitsue Sato (NH), advised that the group 

had made good progress by developing a recommended practice in 

consultation with ticketing, reservations and revenue accounting experts. 

She noted that a resolution is not possible in recognition of certain 

fundamental issues that cannot be resolved at this time. Conference noted 

this report and agreed to extend the mandate of the IRWG by 12 months 

with terms of reference as shown in Attachment H.

P12 Airline Distribution: End-to-End Process Lifecycle

53.Mr Dave McEwen (IATA) advised that he had developed a Recommended 

Practice to document the distribution lifecycle in order to provide a complete 

and transparent summary as to which standards (resolutions and 

recommended practices) and their working groups and committees cover 

each business process. 
11

54.He suggested that such a document would be useful for PSC committees 

and working groups because it is becoming increasingly important to be able 

to review proposals for changes to standards with a view of what impact they 

will have across the entire supply chain. Accordingly he had drafted a 

Recommend Practice as a reference point whereby proponents can evaluate 

the impact on all the affected business areas. He apologized for the late 

submission of this item which had not allowed much time for airlines to 

review the content across various departments.

55.Noting opposition from DL and UA, Conference agreed to establish RP 1786

– Passenger Distribution Lifecycle as shown in the book of finally adopted 

resolutions & RPs. The A4A Secretary advised that they will review this at 

their next meeting of the Passenger Council.

ACTION: A4A Passenger Council

AIRPORT SERVICES

B1 Report of the Airport Services Committee (ASC)

56. Conference noted this report which advised that the ASC had met 

electronically and endorsed all the agenda items submitted to it. There are 

10 vacant positions on the ASC membership, and 5 airlines agreed to 

participate in the ASC for the coming year. During 2013 the ASC will be 

asked to review the terms of reference for the group. A copy of the ASC 

membership for 2013 is shown in Attachment I. New nominations to fill the 

vacant seats should contact the ASC Secretary Mr Andrew Price 

(pricea@iata.org).

B2 Report of the A4A Baggage Committee

57.Conference noted the group’s terms of reference and its membership.

B3 Report of the IATA Ground Handling Council (IGHC)

58.Conference noted the report of the IGHC.

B4 Report of the Baggage Working Group (BWG)

59. Conference noted the report of the BWG and agreed to extend the 

mandate for the group by a further 12 months.

B5 Report of the Baggage Steering Group (BSG)

60. Conference noted the report of the BSG and agreed to extend its 

mandate by a further 12 months. SAS and AA volunteered to fill the 2 empty 

positions on the steering group.
12

B6 Mishandled Baggage Article 4 in Resolutions 780/780e

61. The ASC submitted this proposal to update the resolutions governing the 

pro-rate process for passenger baggage claims, which the PSC unanimously 

approved. The changes to Resolutions 780 and 780e are shown in the book 

of finally adopted resolutions & RPs. The A4A Secretary advised that they 

will review this at their next meeting of the Passenger Council.

ACTION: A4A Passenger Council

B6.1 Pro Rate of International Travel (Resolution 780e)

62. Resolution 780 was amended by the 2010 PSC to remove Article 5.4.10 

regarding advance notification of claims exceeding USD 1,500. However it 

was overlooked to make the equivalent change to Resolution 780e. 

Accordingly the PSC agreed to amend Resolution 780e as shown in the 

book of finally adopted resolutions & RPs. The A4A Secretary advised that 

they will review this at their next meeting of the Passenger Council.

ACTION: A4A Passenger Council

B7 New Resolution 751 - Use of 10 digit Licence Plate

63. The ASC submitted this new resolution. Since changing the allowed 

leading digits for a baggage license plate several years ago, it has been 

essential that this leading digit is transmitted in baggage messages. This 

resolution mandates that all baggage license plate messages are sent in 

their 10 numeric digit form, rather than as a 2 character airline code and 6 

digit baggage identification number. The PSC agreed to establish 

Resolution 751 as shown in the book of finally adopted resolutions & RPs. 

The A4A Passenger Council agreed to establish counterpart Resolution 

30.01 as shown in Part II of the A4A Minutes.

B8/P Baggage Working Group “Package”

64. This “package” contained miscellaneous items documented in B8.1/P 

through B8.7/P which had been developed by the BWG and endorsed by the 

ASC with no opposition noted. The Chair advised that agenda item B8.7/P 

had been removed from the package by AA. The PSC agreed to all 

proposed changes in agenda items B8.1/P through B8.6/P as shown in the 

book of finally adopted Resolutions & RPs. The A4A Passenger Council 

agreed to make counterpart changes to A4A resolutions in agenda items 

B8.1/P through B8.6/P as shown in Part II of the A4A Minutes.
13

B8.1/P Format description of the aircraft compartment in the .U element

65.The ASC noted that the symbology used to represent aircraft holds in the 

Baggage environment and in the Load Control environment were not 

aligned. Accordingly it was proposed to amend RP 1745 and A4A 30.45 to 

match the load control symbology. The PSC agreed to amend RP 1745 as 

shown in the book of finally adopted resolutions & RPs. The A4A Passenger 

Council agreed to make counterpart changes to Resolution 30.45 as shown 

in Section II of the A4A Minutes.

B8.2/P Retain the .L and .K elements as an optional element in RP 1745

66.The ASC noted that whilst the .L and .K elements are not used in RP 1800, 

but are used in BSMs, they should remain as optional elements in RP 1745

and A4A 30.45. The PSC agreed to amend RP 1745 as shown in the book of 

finally adopted resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 30.45 as shown in Section II of the 

A4A Minutes.

B8.3/P Editorial Issues in RP 1800 = BPM .I element is conditional for all 

processes

67.The ASC noted that RP 1800 required updating for the .I element to ensure 

consistency with RP 1745, and requested that A4A 30.49 also be updated. . 

The PSC agreed to amend RP 1800 as shown in the book of finally adopted 

resolutions & RPs. The A4A Passenger Council agreed to make counterpart 

changes to Resolution 30.49 as shown in Section II of the A4A Minutes.

B8.4/P Editorial Issues in RP 1800 – BTM DEL inconsistency in 

documentation

68.The ASC noted that RP 1800 needed updating for the inclusion of the 

meaning of a BTM DEL message. The ASC requested that RP 1800 and 

A4A 30.49 be updated to include the meaning. The PSC agreed to amend 

RP 1800 as shown in the book of finally adopted resolutions & RPs. The 

A4A Passenger Council agreed to make counterpart changes to Resolution 

30.49 as shown in Section II of the A4A Minutes.

B8.5/P Restoration of the “H” designator in .J element

69. The ASC was requested to re-add the H designator in the .J element to 

RP 1745 and A4A 30.45 as it is used by some airlines and ground handlers 

to indicate that a bag has been scanned by a hand-held scanner. The PSC 

agreed to amend RP 1745 as shown in the book of finally adopted 

resolutions & RPs. The A4A Passenger Council agreed to make counterpart 

changes to Resolution 30.45 as shown in Section II of the A4A Minutes.
14

B8.6/P Standardized Code .E/CUST for bags to be inspected by customs 

to be used in RP 1800 Offload/Reload process and in RP 1745

BUM

70. The ASC noted that the code .E/CUST was not used consistently in the 

RP 1800/A4A 30.49 and RP 1745/A4A 30.45 documentation and requested 

that the documentation be updated to have this consistency. The PSC 

agreed to amend RP 1745 and RP 1800 as shown in the book of finally 

adopted resolutions & RPs. The A4A Passenger Council agreed to make 

counterpart changes to Resolution 30.45 and 30.49 as shown in Section II of 

the A4A Minutes.

B8.7/P RP 1800 Self-Service Tagging Proposal and Amendments

71. This item was withdrawn and forwarded to the Baggage Steering Group 

(BSG) for further discussion in light of action being taken by the Fast Travel 

group.

ACTION: BSG & Fast Travel

B9 Report of the DCS Messages Working Group (DCSMWG)

72. Conference agreed to extend the mandate of the DCSMWG by 12 

months.

B10/P DCS Messages Working Group “Package”

73. This “package” contained miscellaneous items documented in B10.1/P 

through B10.3/P which had been developed by the DCSMWG and endorsed 

by the ASC with no opposition noted. The PSC agreed to all proposed 

changes in agenda items B10.1/P through B10.3/P as shown in the book of 

finally adopted Resolutions & RPs.

B10.1/P Clarification of “NOSHO”

74. ASC proposed to amend RP 1719 for clarity, as the description of a noshow, in terms of which passengers fall into the category in the PFS in not 

sufficiently clear. The PSC agreed to amend RP 1719 as shown in the book 

of finally adopted Resolutions & RPs.

B10.2/P Credit Card as FOID

75. To be in compliant with PCI DSS specifications, the ASC proposed to 

truncate credit card numbers when used as a form of identification. Similar 

action had been agreed by ResCom and adopted by PSC under agenda 

item R4.3/P. The PSC agreed to amend RP 1708 as shown in the book of 

finally adopted Resolutions & RPs.
15

B10.3/P Chargeable Family SSRs

76. Consequent to the development (and as adopted by PSC under agenda 

item R3) of a family of SSRs to be used with ASVC for chargeable services 

when no SSR is available, the ASC proposed that the same SSRs be added 

to RP 1708. The PSC agreed to amend RP 1708 as shown in the book of 

finally adopted Resolutions & RPs.

B11 Add Additional Service Remark Format

77. The DCSMWG proposed to amend RP 1708 and 1707a in response to 

the request from EMD Task Force to clarify PNL/ADL formats for ancillary 

services. This item had been dependent on the adoption of the agenda item 

R3, as the proposal included references to family of SSRs being proposed. 

Having confirmed adoption of R3, the PSC agreed to amend RP 1708 and 

RP 1707a as shown in the book of finally adopted Resolutions & RPs.

B12 Post Departure Message Requirements for Additional Services

78. The DCSMWG proposed to introduce a new ‘Additional Service List’ to 

update the post-departure message to accommodate passengers who use 

ancillary services. The group explored the options of updating the ETL, 

creating a new list of a combination of the two. It was identified that because 

EMD-A is synchronized with the e-ticket which is already included in the 

message, no action would be needed to amend the ETL. However, since the 

EMD-S is not synchronized with the e-ticket, it was determined that a 

separate message from the ETL would be useful. The PSC agreed to 

establish RP 1719e and update RP 1707a, RP 1708b and RP 1719b as 

shown in the book of finally adopted Resolutions & RPs.

B13 Clarification of “GOSHN” & “GOSHO”

79. Further to the clarification proposed for NOSHO in agenda item B10.1/P, 

the DCSMWG proposed a similar update for GOSHO and GOSHN for clarity. 

The PSC agreed to amend RP 1719 as shown in the book of finally adopted 

Resolutions & RPs.

B14 RP 1797 and RP 1797a

80. The Common Use Working Group (CUWG) proposed a number of minor 

changes to RP 1797 in recognition of new knowledge gained from 

implementations. Moreover the AIDX sub-group requested the full 

publication of the provisions of RP 1797a to facilitate access to these 

standards. The PSC agreed to amend RP 1797 and RP 1797a as shown in 

the book of finally adopted resolutions & RPs. The A4A Passenger Council 

agreed to make counterpart changes to Resolution 30.201a as shown in 

Section II of the A4A Minutes.
16

TICKETING

T1 Report of the Ticketing Committee 

81. Conference noted the report of the Joint Passenger Ticketing Committee 

(JPTC) as presented. Chairman thanked the Committee for its work done 

throughout the year.

82. Conference was advised that the term of office for DL, JL, LA and SK 

were expiring and also that as a result of the merger of UA and CO, CO 

would no longer be represented separately. Accordingly five Ticketing 

Committee members would need to be selected. The Chairman asked if 

there were any other Members that wished to be considered.

83. There were a total of 5 nominations for the five vacant positions. 

Accordingly DL, CX, AY, JL and SK were elected by acclamation for a three 

year period. A copy of the updated membership is shown in Attachment J. 

Conference noted that all places are now taken.

84. Conference also renamed the JPTC to simply the “Ticketing Committee 

(TKTcom)” with Terms of Reference as shown in Attachment K. Moreover it 

was agreed to establish a Ticketing Working Group (TKTWG) with Terms of 

Reference as shown in Attachment L and a workplan as shown in 

Attachment M.

T2/P Ticketing “Package”

85. This “package” contained miscellaneous items documented in T2.1/P 

through T2.22/P which had been approved at JPTC with no opposition 

noted. Agenda item T2.15/P was withdrawn from the package for further 

consideration. 

86. The PSC unanimously adopted agenda items T2.1/P through T2.22/P as 

shown in the book of finally adopted Resolutions & RPs as detailed below. 

87. Noting that T2.1/P, T2.2/P, T2.11/P and T2.14/P were for IATA action 

only, the A4A Passenger Council unanimously agreed to counterpart 

changes in items T2.3/P through T2.22/P (except T2.1/P, T2.2/P, T2.11/P

and T2.14/P) as shown in Section II of the A4A Minutes.

T2.1/P New Example of Validity for Exchanges

88. The Ticketing Committee (JPTC) proposed to add an additional example 

to Resolution 735 to make it clear what is the new validity of an exchanged 

ticket with a one year validity. The PSC agreed to amend Resolution 735 as 

shown in the book of finally adopted Resolutions & RPs.
17

T2.2/P Tour Code Box Required for Staff Travel

89. The Ticketing Committee (JPTC) proposed to amend Recommended 

Practice 1788 to eliminate the list of categories with a reference to the ISTA 

for the current list of SAF categories. The PSC agreed to amend 

Recommended Practice 1788 as shown in the book of finally adopted 

Resolutions & RPs.

T2.3/P Editorial Change: Optimize the Process to Provide the Actual 

Coupon Status in Display Response

90.The Ticketing Committee (JPTC) proposed amendments to resolutions to 

align the definitions of Coupon Status Indicator ‘C’.

91.The PSC agreed to amend Resolutions 722f, 722g, 722h, 725f, 725g and 

725h as shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

20.60, 20.61, 20.62, 20.63, 20.64 and 20.66 as shown in Section II of the 

A4A Minutes.

T2.4/P Reissued Flown Ticket/Document Number and Date of Issue

92. The Ticketing Committee (JPTC) proposed amendments to resolutions 

adding reissued flown data elements to the glossary and matrices as they 

are necessary for future reissue or refund transactions. 

93.The PSC agreed to amend Resolutions 722f, 722g, 722h, 725f, 725g and 

725h as shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

20.60, 20.61, 20.62, 20.63, 20.64 and 20.66 as shown in Section II of the 

A4A Minutes.

T2.5/P Single Matching Item and Multiple Matching Items Display

94.The Ticketing Committee (JPTC) proposed amendments to resolutions to 

ensure consistency in all resolutions that when there are multiple matching 

items in a display response all resolutions should specify to display a similar 

record list response.

95.The PSC agreed to amend Resolutions 722f, 722g, 722h, 725f, 725g and 

725h as shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

20.60, 20.61, 20.62, 20.63, 20.64 and 20.66 as shown in Section II of the 

A4A Minutes.
18

T2.6/P Revise System Update Message Construction Matrices

96. The Ticketing Committee (JPTC) proposed amendments to resolutions to

make consistent the matrices for the system update message.

97.The PSC agreed to amend Resolutions 722f, 725f, and 725h as shown in the 

book of finally adopted Resolutions & RPs. The A4A Passenger Council 

agreed to make counterpart changes to Resolutions 20.60, 20.63 and 20.66 

as shown in Section II of the A4A Minutes.

T2.7/P Add System Update to ET Ground Handler Message Construction 

Matrix

98. The Ticketing Committee (JPTC) proposed amendments to resolutions to

define the system update message in the ET Ground Handling Matrix.

99.The PSC agreed to amend Resolution 722h as shown in the book of finally 

adopted Resolutions & RPs. The A4A Passenger Council agreed to make 

counterpart changes to Resolution 20.62 as shown in Section II of the A4A 

Minutes.

T2.8/P Deletion of IDEC Requirement for Interline Billing

100. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to delete the reference to IDEC since IDEC will cease to be used 

as a file format for the transmission of interline billing and settlement data 

when the last file is transmitted from ATPCO on October 25 as a result of the 

implementation of the paperless Simplified Interline Settlement 

implementation.

101. The PSC agreed to amend Resolution 722f as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 20.60 as shown in Section II of the 

A4A Minutes.

T2.9/P Add ABR (Automated Baggage Rule) Additional Information to 

the Electronic Ticket Record

102. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to develop a means to disclose the details of carry-on and 

checked baggage allowance, and to provide on the e-ticket confirmation the 

first and second bag charge by adding a whole new seasons of data 

elements to the glossary and messaging matrices. 

103. The PSC agreed to amend Resolutions 720a, 722f, 722g and 722h as 

shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

110.15, 20.60, 20.61and 20.62 as shown in Section II of the A4A Minutes.
19

T2.10/P Add ABR (Automated Baggage Rule) MSC Information to the 

Electronic Ticket Record

104. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to amend the recently adopted mail vote (MV S088 issued 21 

May 2012) to change the ‘Baggage Determining Carrier Code’ from 

‘Optional’ to “Conditional’ in the matrices.

105. The PSC agreed to amend Resolutions 722f, 722g and 722h as 

shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

20.60, 20.61and 20.62 as shown in Section II of the A4A Minutes.

T2.11/P Application of Free Baggage Allowance/Excess Baggage 

Charges in case of IROP

106. The Ticketing Committee (JPTC) proposed amendments to Resolution

735d to clarify that passengers should be entitled to the baggage allowance 

as applied to the original itinerary when involuntarily rerouted. The PSC 

agreed to amend Resolution 735d as shown in the book of finally adopted 

Resolutions & RPs.

T2.12/P Changes to All Resolutions – Baggage Allowance

107. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to amend the standards not permitting a blank value being shown 

in the baggage allowance box/data element. It should be noted that a “blank”

should cease to exist in the current compliance environment. 

108. The PSC agreed to amend Resolutions 720a, 722, 722a, 722c, 722f, 

722g, 722h, 727, 724c, 742d, 746 and RP 1706a as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolutions 110.15, 20.10, 20.12, 20.13, 

20.18, 20.51, 20.52 20.60, 20.61and 20.62 as shown in Section II of the A4A 

Minutes.

T2.13/P Allow Travel Agents to Re-Associate EMD-A After Ticket Reissue

109. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to allow a means for travel agents to re-associate EMD-A’s as 

previously issued by that agent according to the Validating Airline’s rules.

110. The PSC agreed to amend Resolution 725g as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 20.64 as shown in Section II of the 

A4A Minutes.
20

T2.14/P Statistical Code Definition Amendment

111. The Ticketing Committee (JPTC) proposed amendments to resolution

722f to clarify the definition of the data element ‘Statistical Code’ and explain 

the way in which the values are computed.

112. The PSC agreed to amend Resolution 722f as shown in the book of 

finally adopted Resolutions & RPs. 

T2.15/P Not Valid After and Not Valid Before Date on EMD-S

113. This item was removed from the ticketing package for further 

discussion. The Ticketing Committee (JPTC) proposed amendments to 

Resolution 722f/A4A 20.60 to add two new data elements for EMD-S: “Not 

Valid After” and “Not Valid Before”, providing no message upgrade is 

required for these optional fields related to the service at a coupon level. 

114. The Airlines Reporting Corporation (ARC) suggested an expedited 

effectiveness date of 1 January 2013 in order to align standards with what 

they have already implemented. Accordingly, the PSC agreed to amend 

Resolution 722f an expedited effectiveness date of 01 January 2013 as 

shown in the Expedited Resolutions and Recommended Practices. The A4A 

Passenger Council agreed to make counterpart changes to Resolution 20.60 

as shown in Section II of the A4A Minutes.

T2.16/P Addition of Attribute Group and Attribute Sub-Group to EMD 

Unsolicited Billing Request

115. The Ticketing Committee (JPTC) proposed amendments to add 

optional data elements to the EMD Unsolicited Billing message for Additional 

Services Attribute Group, Additional Services Attribute Sub-group, Additional 

Services Industry Carrier Indicator and Additional Services Service Type into 

Resolution 725f.

116. The PSC agreed to amend Resolution 725f as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 20.63 as shown in Section II of the 

A4A Minutes.

T2.17/P Add Product Characteristics to EMD Unsolicited Billing Request

117. The Ticketing Committee (JPTC) proposed amendments to add new 

optional data elements to the EMD Unsolicited Billing message for Product 

Characteristic Type and Product Characteristic Value into Resolution 725f.

118. The PSC agreed to amend Resolution 725f as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 20.63 as shown in Section II of the 

A4A Minutes.
21

T2.18/P Allow Access to the ET Issued by Airline in Exchange for Agent 

Original ET

119. The Ticketing Committee (JPTC) proposed amendments to resolution 

722g/A4A 20.61 to allow an agent to display an airline exchanged or 

reissued electronic ticket as long as the original electronic ticket being 

exchanged or reissued is issued by either the same agent or an accredited 

branch.

120. The PSC agreed to amend Resolution 722g as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 20.61 as shown in Section II of the 

A4A Minutes.

T2.19/P New Routing Indicator Domestic vs. International

121. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to clarify the definition of Statistical Code for international and 

domestic scenarios.

122. The PSC agreed to amend Resolutions 722f, 722g, 725f and 725g as 

shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

20.60, 20.61, 20.63 and 20.64 as shown in Section II of the A4A Minutes.

T2.20/P Remove Remaining References to Sundry Charges

123. The Ticketing Committee (JPTC) proposed amendments to 

resolutions to remove the remaining references to sundry charges.

124. The PSC agreed to amend Resolutions 722c, 725a and 725b as 

shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolution

20.200 as shown in Section II of the A4A Minutes.

T2.21/P Revision of SAPP (Source of Approval Code) Values

125. The Ticketing Committee (JPTC) proposed amendments to align the 

DISH and Resolutions 722f/20.60 for Source of Approval Code.

126. The PSC agreed to amend Resolution 722f as shown in the book of 

finally adopted Resolutions & RPs. The A4A Passenger Council agreed to 

make counterpart changes to Resolution 20.60 as shown in Section II of the 

A4A Minutes.
22

T2.22/P Editorial Changes to RP1790/A4A10.90

127. The Ticketing Committee (JPTC) proposed amendments to include a 

reference to fee calculation for EMD.

128. The PSC agreed to amend Recommended Practice 1790 as shown in 

the book of finally adopted Resolutions & RPs. The A4A Passenger Council 

agreed to make counterpart changes to Resolution 10.90 as shown in 

Section II of the A4A Minutes.

T3 Itinerary and EMD Fee Calculation

129. The Ticketing Committee (JPTC) proposed amendments to 

Resolutions 725a and 725b to add the wording in the resolution to prohibit 

the issuance of EMD with fee calculation if a routing is not present on the 

EMD coupons.

130. Although there was some strong support for this proposal two 

Members felt that it would put restrictions in place for carriers that wanted to 

use it. It was suggested to refer this item back to the newly formed TKTWG.

ACTION: TKTWG

T4 Deletion of Ticketing Provisions for Euro Transition

131. The Ticketing Committee (JPTC) proposed amendments to 

Resolutions 720a, 722, 722f, 722g, 725a, 725b, 725f, 725g, 726a, 726e, and 

726f to delete references to the euro transition process since it has never 

been invoked and is not supported by tariff composite resolutions any longer.

132. Noting abstentions from KE and LX, the PSC agreed to amend 

Resolutions 720a, 722, 722f, 722g, 725a, 725b, 725f, 725g, 726a, 726e, and 

726f as shown in the book of finally adopted Resolutions & RPs. The A4A 

Passenger Council agreed to make counterpart changes to Resolutions 

20.60, 20.63 and 20.64 as shown in Section II of the A4A Minutes.

T5 New Schedule Change Recommended Practice

133. The Ticketing Committee (JPTC) proposed to introduce a new 

Recommended Practice 1735 to provide an industry direction and 

methodology for servicing when planned schedule changes takes place. It is

acknowledged that this proposal is a first step approach and further work is 

needed to evaluate what should happen with partially used tickets.

134. A Member felt this was not the way forward since it could affect the 

commercial decisions of an airline. Noting the opposition of BA, the PSC 

agreed to establish Recommended Practice 1735 as shown in the book of 

finally adopted Resolutions & RPs. The A4A Secretary advised that they will 

review this at their next meeting of the Passenger Council.

ACTION: A4A Passenger Council
23

T6 Imprint correct name in “Name of Passenger” box and “Passenger 

Name” field

135. A Member proposed to amend ticketing resolutions to make it clear 

that the name entered in reservations and tickets should be the same as 

what is in the official travel document. Whilst there was some support for 

this proposal Members were concerned as to how letters with characters 

would be represented in a uniform manner. In addition what would happen 

with long names which would be truncated.

136. On a formal vote with 4 Members opposed and 1 abstention this item 

was declared defeated by the Chairman who directed this issue back to the 

TKTcom and ResCom. 

ACTION: TKTcom & ResCom

T7 Add ‘Remarks’ to 725g Message Construction Matrix

137. IATA Management proposed to make an editorial amendment to

Resolution 725g to add “Remarks” to the Resolution 725g matrix since it had 

been omitted when the data element was adopted.

138. The PSC agreed to adopt changes to Resolution 725g as shown in 

the book of finally adopted Resolutions & RPs.

T8 Complimentary Amendments to Resolution 722f

139. As a result of changes agreed at the IATA Composite Conference,

IATA Management submitted this onsite item to delete references to the 

Banker’s Buying Rate in Resolution 722f and Recommended Practice 1721

with an expedited effectiveness date of 1 April 2013.

140. The PSC agreed to adopt changes to Resolution 722f and 

Recommended Practice 1721 with an expedited effectiveness date of 1 April 

2013 as shown with the Expedited Resolutions and Recommended 

Practices.

RESERVATIONS

R1 Report - A4A/IATA Reservations Committee (ResCom)

141. Conference noted this report. NH, DL, LY, AY, JL, KL, SK and UA

were appointed to the IATA Reservations Committee as shown in

Attachment AA.
24

142. ResCom proposed to reduce the voting period for the mail vote 

process down from 30 days to 14 days to reflect current business practices 

and accelerate adoption of future standards. The PSC agreed to amend 

Resolution 760a as shown in the book of finally adopted Resolutions & RPs. 

The A4A Passenger Council agreed to make counterpart changes to 

Resolution 10.40 as shown in Section II of the A4A Minutes. 

R2 Report - Reservations Working Group (RESWG)

143. Conference noted this report and endorsed the work plan as shown in

Attachment BB. Conference agreed to extend the mandate of RESWG for

a further 12 months.

R3 Chargeable Family SSRs

144. ResCom proposed to introduce 14 new distinctive bilateral SSR codes 

to identify the “family” of products/services with the understanding that in the 

future, when no other SSR code was available, these codes would be used 

as an alternative to creating a new SSR for a chargeable service.

145. The introduction of these bilateral SSRs, while based on a business 

need, will also support existing system processes including filing in order to 

ensure that charges filed contain an SSR. For those members who chose to 

use them, these SSRs offer a new way to identify chargeable services in 

conjunction with the SSR ASVC.

146. Current methods outlined in AIRIMP which include the use of an SSR 

ASVC alone for the sale of chargeable products/services, or the use of the 

standards and non-standard SSR in conjunction with SSR ASVC when 

chargeable products/services are requested, and finally the use of auxiliary 

SVC segments, are still available as before when ancillary products/services 

are involved. Conference agreed to amend AIRIMP as shown in Attachment 

CC. The A4A Passenger Council agreed to counterpart changes in SIPP 

also as shown in Attachment CC. 

R4/P Reservations “Package”

147. This “package” contained miscellaneous items documented in R4.1/P

through R4.15/P which had been approved at ResCom with no opposition

noted. Conference unanimously adopted changes to AIRIMP in agenda

items R4.1/P through R4.15/P as shown in Attachments DD through OO. 

The A4A Passenger Council unanimously agreed to counterpart changes to

SIPP in agenda items R4.1/P through R4.15/P also as shown in

Attachments DD through OO.
25

R4.1/P Amend Description of Miscellaneous RBDs

148. ResCom proposed to amend AIRIMP to reflect the broader use of the 

RBDs, deleting the current description for RBDs G, U and E and replacing 

with ‘For individual airline use’. Conference agreed to amend AIRIMP as 

shown in Attachment DD. The A4A Passenger Council agreed to 

counterpart changes in SIPP also as shown in Attachment DD.

R4.2/P Contact Information in OSI

149. ResCom proposed to amend the current description of the P-Indicator 

for contact information in OSI to meet the requirement of a member.

Conference agreed to amend AIRIMP as shown in Attachment EE. The 

A4A Passenger Council agreed to counterpart changes in SIPP also as 

shown in Attachment EE.

R4.3/P Credit Card as FOID

150. JPSC/33 defeated a proposal to remove credit card as FOID and 

requested RESWG/ResCom to review further. ResCom agreed that any 

transmission of credit card information for interline message should be 

truncated by the sender to be in compliant with PCI DSS specifications, and 

that such message is no longer valid for financial transactions however may 

be used for FOID. ResCom proposed to amend AIRIMP to specify how the 

truncation process should be applied by replacing certain numbers with ‘X’s, 

and to amend the examples so that more specific messages are shown for 

clarity. Conference agreed to amend AIRIMP as shown in Attachment FF. 

The A4A Passenger Council agreed to counterpart changes in SIPP also as 

shown in Attachment FF.

R4.4/P Moveable Arm Rest Characteristics – Seat Map and Seat Request

151. ResCom proposed to establish a code for a “moveable arm rest” to 

identify seats assignable for extra seat for comfort. Conference agreed to 

amend AIRIMP as shown in Attachment GG. The A4A Passenger Council 

agreed to counterpart changes in SIPP also as shown in Attachment GG.

R4.5/P PNR Update Message to Advise EMD Number

152. ResCom proposed to add an example for a message from booking 

source to a member advising that the EMD had been issued for a service/fee 

that was not previously filed. Conference agreed to amend AIRIMP as shown 

in Attachment GG. The A4A Passenger Council agreed to counterpart 

changes in SIPP also as shown in Attachment HH.
26

R4.6/P SSR ASVC Related to Seats on Change of Gauge Flight

153. ResCom proposed to apply the same rule to SSR ASVC related to 

chargeable seats on change of gauge flight, where the flight leg data would 

be used in SSR ASVC instead of flight segment data, to be able to link the 

SSR ASVC to the correct seat on the correct leg. Conference agreed to 

amend AIRIMP as shown in Attachment II. The A4A Passenger Council 

agreed to counterpart changes in SIPP also as shown in Attachment II.

R4.7/P Review of RP 1762 on Reconfirmation Procedures

154. ResCom proposed to delete RP 1762 on Reconfirmation Procedures 

in view that airlines make their own reconfirmation procedures. The PSC 

agreed to rescind RP 1762 as shown in Resolution 003 in the book of finally 

adopted Resolutions & RPs.

R4.8/P Rewrite Chapter 3.19 Pre-Reserved Seat Selection and Boarding 

Pass Notification

155. ResCom proposed to remove references to advance boarding pass 

notification in AIRIMP since it is no longer used in reservation messages. 

Conference agreed to amend AIRIMP as shown in Attachment JJ. The 

A4A Passenger Council agreed to counterpart changes in SIPP also as 

shown in Attachment JJ.

R4.9/P Editorials to Construction of OSI

156. ResCom proposed to make editorial changes to AIRIMP to keep 

cross-references correct. Conference agreed to amend AIRIMP as shown in 

Attachment KK. The A4A Passenger Council agreed to counterpart 

changes in SIPP also as shown in Attachment KK.

R4.10/P Online Married Segment Control

157. ResCom proposed to establish a possibility to apply Married Segment 

Control for up to 6 segments in one marriage, regardless whether round-trip 

marriage is applied/involved or not, for consistency across all GDSs. The 

PSC agreed to amend RP 1777 as shown in the book of finally adopted 

Resolutions & RPs. The A4A Passenger Council agreed to make 

counterpart changes to Resolution 105.177 as shown in Section II of the A4A 

Minutes.
27

R4.11/P Full PNR Itinerary Information

158. So that full PNR itinerary information content sent by GDSs/CRSs to 

the airlines has clear definition and leaves no room for interpretation, 

ResCom proposed to make changes to RP 1779. The PSC agreed to amend 

RP 1779 as shown in the book of finally adopted Resolutions & RPs. The 

A4A Passenger Council agreed to make counterpart changes to Resolution 

105.79 as shown in Section II of the A4A Minutes.

R4.12/P Add a Definition to Codes HHL and CCR

159. ResCom proposed to add the word “(Automated Format)” to HHL 

code (Hotel accommodation) as well as to CCR Code (Car rental) in AIRIMP 

2.10 as it is already written in AIRIMP 7.1.7.5. Conference agreed to amend 

AIRIMP as shown in Attachment LL. The A4A Passenger Council agreed 

to counterpart changes in SIPP also as shown in Attachment LL.

R4.13/P SSR ASVC and Service Cancellation after Issuance

160. ResCom proposed updating AIRIMP procedures for ASVC regarding 

cases of service cancellation after issuance of an EMD by adding examples 

for clarity. Conference agreed to amend AIRIMP as shown in Attachment 

MM. The A4A Passenger Council agreed to counterpart changes in SIPP 

also as shown in Attachment MM.

R4.14/P Cancelling SSR Elements by the Member

161. ResCom proposed to amend AIRIMP by adding new section 3.3.9, 

introducing the use of HX advice code as a standard when a member 

advises booking source that cancellation of a Special Service Request is 

made. Conference agreed to amend AIRIMP as shown in Attachment NN. 

The A4A Passenger Council agreed to counterpart changes in SIPP also as 

shown in Attachment NN.

R4.15/P Use of SSR ADTK to Request Ticket Number for Ticketing Time 

Limit

162. ResCom proposed to amend AIRIMP whereby ADTK would be used 

to request for ticket numbers to minimize the use of codes OTHS and TKTL 

for efficiency. For ticketless carriers no ticket number will be sent back when 

SSR ADTK is send and they will continue to use the codes OTHS and TKTL. 

Conference agreed to amend AIRIMP as shown in Attachment OO. The 

A4A Passenger Council agreed to counterpart changes in SIPP also as 

shown in Attachment OO.
28

R5 Electronic Reservation Services Providers (ERSPs)

163. IATA Secretary proposed to take counterpart action on the PSC side 

by rescinding Resolution 784 in recognition of PAConf action that rescinded 

Resolution 898a with effect 31 December 2012 as the resolution on the 

Electronic Reservation Services Providers (ERSPs) was no longer required 

in today’s more evolved electronic environment. Consequent to this action, 

references to ERSPs need to be deleted in other standards, as well as for 

similar action for AIRIMP. 

164. Concern was raised by LH that the proposal had not gone through 

RESWG or ResCom, however IATA Secretary advised that this is a 

consequential action due to agreement made by PAConf at the 2011 

meeting. With abstentions from AF, BA, IB, the PSC agreed to rescind 

Resolution 784 by Resolution 003 action, as shown in the book of finally 

adopted Resolutions & RPs. Secretary will make appropriate editorial 

changes to RP 1706c, RP 1776a, RP 1778 and RP 1797. It has also been 

agreed to amend AIRIMP as shown in Attachment PP. The A4A Passenger 

Council agreed to counterpart changes in SIPP also as shown in 

Attachment PP.

MISCELLANEOUS

M1 Report - PSC Steering Group (PSCSG)

165. Conference noted this report. The position for TC1 was filled by Rick 

Nagy from Alaska Airlines (AS).

M2 Report - PADIS Board (PADIS)

166. Conference noted this report. The PADIS Secretary expressed her 

deep appreciation to Amadeus, Sabre, SITA, Travelport and other partners 

who continued to provide tremendous support and guidance to the work of 

the PADIS working groups.

M2.1 PNRGOV Working Group

167. Conference noted this report and established the terms of reference 

as shown in Attachment N as amended on site.

M3 Report - Cargo Services Conference (CSC)

168. Conference noted this report.
29

M4 Report – Worldwide Airport Slots

169. Conference noted this report.

M4.1 Report - Schedules Information Standards Committee (SISC)

170. Conference noted this report.

M4.2 Guidelines for the Allocation of Airport Slots

171. The Worldwide Slot Guidelines (WSG) is published by IATA to provide 

the global air transport community with a single set of standards for the 

management of airport slots. The management of airport slots is required at 

some airports where the available airport infrastructure is insufficient to meet 

the demand of airlines and other aircraft operators. The WSG is overseen 

by the IATA Joint Slot Advisory Group (JSAG), comprised of an equal 

number of IATA Member airlines and airport coordinators. 

172. JSAG meets regularly to agree on proposals for changes to the WSG 

and to consult on the administration of the twice yearly IATA Slot Conference 

(SC). All changes are agreed by JSAG before being endorsed by the Heads 

of Delegation of the SC. Accordingly it was recommended that members 

use the guidelines as published in the WSG. In order to promote these 

guidelines to as wide an audience as possible, it was proposed to establish 

them as part of a PSC recommended practice. The PSC agreed to establish 

RP 1761 Guidelines for the allocation of airport slots as shown in the book of 

finally adopted resolutions & RPs.

M5 Report – Fraud Prevention Working Group (FPWG)

173. Conference noted this report and agreed to disband the FPWG under 

the governance of the PSC. 

M6 Report – BSP Data Interchange Standards Group (BDISG)

174. Conference noted this report.

M7 Report – Strategic Partnerships

175. Conference noted this report.

M8 Report – Travel Partners Standards Council

176. The Secretary advised that this group would be revived back into life 

in order to address “goal number 5” from the StB Think Tank regarding a 

“seamless end-to-end customer journey through interoperability of travel 

partners”.
30

M9 Report - Agency Solutions Technical Working Group (ASTWG)

177. Conference noted this report and agreed to disband the ASTWG 

under the governance of PSC. The Chairman and Sabre voiced their strong 

desire to ensure that IATA would continue to provide a forum to allow 

airlines, GDSs and travel agents to discuss issues of common interest. Mr 

Popovich (IATA) assured the Conference that such a group would continue 

its activity but henceforth be managed by the IATA Distribution department.

M10 Customer Satisfaction Surveys

178. The Secretary reported that a generic online survey had been 

circulated to the meeting participants of various Committees and working 

groups. He advised that the results would be shared with each of the groups 

concerned as well as the PSC Steering Group (PSCSG) to monitor service 

levels and areas for improvement.

ACTION: PSCSG

Close of Meeting

179. The Secretary requested John Meeks to come to the head table to 

accept an appreciation certificate on behalf of his former colleague Ms 

Adrianna Colbath who had recently retired. The whole Conference including 

the Secretariats of the A4A and IATA wished him to pass on their heartfelt 

gratitude to Adrianna for all her support and leadership over many years and 

wished her a restful and gratifying retirement. 

180. The Chairman closed the meeting at 1130 hours on 19 October 2012. 

She profusely thanked Etihad for their fantastic hospitality during the entire 

week of meetings.
 JPSC/32 PSC/34 Oct 12

 Attachment: A

 Page: 1 of 3

Airline / Company Name First Name Last Name Job Title Email

Aerolineas Argentinas Marta Chiban BSP Travel Agencies Management mchiban@aerolineas.com.ar

Aerolineas Argentinas Jorge Rizzuto BSP Accounting Coordinator jrizzuto@aerolineas.com.ar

Air Canada Janet Wallace Director, Airport Services janet.wallace@aircanada.ca

Air France Helene Arnaud-Millet distribution senior manager hearnaudmillet@airfrance.fr

Airlines for America James Casey Vice President & Deputy General Counsel jcasey@airlines.org

Airlines for America Patty Edwards Managing Director, Passenger Services pedwards@airlines.org

Airlines Reporting Corporation (ARC) James Keith Venzke Senior Manager Industry Standards kvenzke@arccorp.com

Airlines Reporting Corporation (ARC) Philip Myers Manager pmyers@arccorp.com

Alaska Airlines Rick Nagy Manager - Ground Ops Product Development rick.nagy@alaskaair.com

Alitalia Compagnia Aerea Italiana Anna Rita Coletta GDS Relation Senior Manager coletta.anna.rita@alitalia.it

All Nippon Airways Yoko Kajino assistant manager y.kajino@ana.co.jp

All Nippon Airways Kumiko Ozawa Manager ku.tsukahara@ana.co.jp

All Nippon Airways Mitsue Sato Assistant Manager, IT Strategy & Planning mitsue@ana.co.jp

All Nippon Airways Etsuko Tada Director,Passenger Regulations,Revenue Managee.tada@ana.co.jp

All Nippon Airways Izumi Tateno Assistant Manager i.tateno@ana.co.jp

All Nippon Airways Chiharu Tsuzuki Senior Manager c.tsuzuki@ana.co.jp

Amadeus Daniel Hassellof Product Manager dhassellof@amadeus.com

Amadeus Isabelle Poucet Unit Manager - Airline IT Ancillary Services ipoucet@amadeus.com

American Airlines Valerie Folger Sr. Manager, Customer Contact Management valerie.folger@aa.com

Austrian Airlines Marcus Lenk Manager Global Sales and Distribution Projects marcus.lenk@austrian.com

AXESS International network INC. Tomoko Igawa Senior Manager igawa.tomoko@axess.co.jp

British Airways Jerry Foran Head of Product Delivery, Revenue Management jerry.foran@ba.com

British Airways Glenn Morgan Head of Service Transformation glenn.morgan@ba.com

China Southern Airlines Lin Qing Manager, Sales Division linqing@csair.com

China Southern Airlines Liu Zhe pricing manager liuzhea@csair.com

Czech Airlines Michal Hajek Regulations Specialist michal.hajek@csa.cz

Delta Air Lines Kendal Chapman Project Leader Electronic Ticketing kendal.chapman@delta.com

Delta Air Lines Stephanie Yen Manager - Industry Affairs stephanie.yen@delta.com
Deutsche Lufthansa AG Michelle Bryant Manager Development Distribution Systems and I michelle.bryant@dlh.de

Egyptair Tamer Gebril manager industry affairs industry_aff@egyptair.com

El Al Israel Airlines Ltd. Linda Grinfeld deputy director iata and pricing linda@elal.co.il

Emirates Claus Basse Manager Industry Affairs claus.basse@emirates.com

Emirates Richard Pearl Industry Affairs Suptd. richard.pearl@emirates.com

Finnair Päivi Rautanen Application Specialist paivi.rautanen@finnair.com

Hahn Air Lines Katharina Becker Director Legal k.becker@hahnair.com

Hahn Air Lines Jorg Troester SVP Corp Strat j.troester@hahnair.com

Hainan Airlines Tang Limin supervisor of of international pricing management lm_tang@hnair.com

Hainan Airlines Chen Siyang specialist of international pricing management siyang-chen@hnair.com

HP Daniel Friedli Project Manager daniel.friedli@hp.com

IATA Paul Behan Head, Passenger Experience behanp@iata.org

IATA Hugh Best Implementation Manager besth@iata.org

IATA Stephan Copart Project Manager, Fast Travel coparts@iata.org

IATA Ann Farrell Mgr Airline Codes & MITA Interlining farrella@iata.org

IATA Daniel Kanter Senior Legal Counsel kanterd@iata.org

IATA Christophe Kato Assistant director, industry card services katoc@iata.org

IATA Eric Leopold Director, IATA Passenger leopolde@iata.org

IATA David McEwen Manager, Airline Distribution Standards mcewend@iata.org

IATA Claude Muller Head, New Distribution Capability mullerc@iata.org

IATA Andrew Price Head of Baggage Services pricea@iata.org

IATA Cristina Rotor Manager - Tariff Solutions & Distribution rotorc@iata.org

IATA Thibaut Ruy Manager ruyt@iata.org

IATA Alban Sato Manager Tariffs and Reservation Standards satoa@iata.org

IATA Winnifred Yoong Regional Manager, Passenger & IATA Financial yoongw@iata.org

IATA Marie Zitkova Manager, Messaging Standards zitkovam@iata.org

IATA Sebastien Touraine Project Manager, e-Services touraines@iata.org

IATA (PSC Secretary) Mike Muller Head, Interline & Intermodal Policy mullerm@iata.org

Iberia Airlines Timothy Ling Project Coordinator & Industry Relations tjling@iberia.es

Icelandair Helga Bjornsdottir Projet manager Pricing helgabj@icelandair.is

Icelandair Anita Knutsdottir Mgr. Pricing & Tariffs ak@icelandair.is

Icelandair Anna Gudrun Tomasdottir Manager Ticketing agt@icelandair.is

ITA Software by Google Amy Sexton Sr Product Specialist amysexton@google.com

Japan Airlines Koichi Fukunaga Senior Director koichi.fukunaga@jal.com

Japan Airlines Eri Miyake Manager eri.miyake@jal.com

JPSC / PAPGJC Chairman Patricia George Chairman Industry Meetings pageorge@wanadoo.fr

KLM Royal Dutch Airlines Johan Lodewijckx Manager IATA & Industry Affairs johan.lodewijckx@klm.com

Korean Air Keunhae Kim Deputy General Manager kimkh@koreanair.com
Korean Air Tae Noh general manager trnoh@koreanair.com

LOT Polish Airlines Elzbieta Dmowska IATA Rules and Regulation Adviser e.dmowska@lot.pl

Middle East Airlines Salim Kharrat Assistant Head, PAssenger and Cargo kharrats@mea.com.lb

Navitaire Jim Erickson Industry Consultant james.erickson@navitaire.com

Olympic Air Eleni Papaioannou Res & Distribution Support Manager e.papaioannou@olympicair.com

Philippine Airlines Ianthe Aquino Vice President tads_aquino@pal.com.ph

Philippine Airlines Rosario Sanciangco Manager-Alliances cail_lim@pal.com.ph

Sabre Holdings Tim Powell Director Industry Affairs tim.powell@sabre.com

Saudi Arabian Airlines Ayed Alotaibi snr. splct. airport svcs programs aalotaibi@saudiairlines.com

Saudi Arabian Airlines Adil Hanbazaza gm. procedures and quality standars ahanbazaza@saudiairlines.com

Saudi Arabian Airlines Mohammed ALshaikh Manager DCS malshaikh@saudiairlines.com

Scandinavian Airlines Elaine Rusén Manager Industry Affairs elaine.rusen@sas.se

SITA John Meeks Manager, Business and Competitive Analysis john.meeks@sita.aero

South African Airways Madelein Vorster Manager madeleinvorster@flysaa.com

Southwest Airlines Lance Morton Director Operational Strategies lance.morton@wnco.com

Swiss International Air Lines Ltd Patrick Graf Head of Revenue Management Business Solutionpatrick.graf@swiss.com

Thai Airways Janpen Rana janpen.r@thaiairways.com

Thai Airways Ohm Planichaya Director, Distribution & Commercial Procedure Deohm.p@thaiairways.com

Travelport Caroline Wilkinson Senior Product Manager caroline.wilkinson@travelport.com

Turkish Airlines Bilge Sahin Manager, IATA Ticketing and Regulations bilges@thy.com

Unisys John Kunitz Sr Applications Development Manager john.kunitz@unisys.com

United Airlines Rosalie Crabbe Mgr. Accessible Programs/ Industry Affairs rosalie.crabbe@united.com

US Airways Heather Hamel Sr. Analyst Airport Customer Service Policies & Prheather.hamel@usairways.com

US Airways Deryl Purvis Senior Analyst deryl.purvis@usairways.com

Vietnam Airlines Trang Tran Thi Deputy Manager Tariffs and Ticketing trangtt@vietnamairlines.com

Virgin Australia Simon Pitt Manager, International Revenue simon.pitt@virginaustralia.com

Yemen Airways Mukhtar Alhaidary Manager Revenue Accounting Sales mukhtar.alhaidary@yemenia.com
End
Attachment: B

Page: 1 of 3

NEW TAX CODES

Since September 2011

CODE NAME COUNTRY REQUESTED

BY

DATE PURPOSE / DETAILS

-VH- IMMIGRATION USER 

FEE

SENEGAL SENEGAL 

AIRLINES

09/09/2011 TO FINANCE INVESTMENTS RELATED TO THE 

ESTABLISHMENT AND OPERATION OF AN 

INTEGRATED CONTROL SYSTEM OF IMMIGRATIO 

THE INTERNATIONAL AIRPORTS.

-WE- PASSENGER FACILITY 

CHARGE

GUYANA DELTA AIR 

LINES

06/10/2011 FOR THE COMMON USE TERMINAL 

EQUIPMENT (CUTE).

-KV- ENVIRONMENTAL 

LEVY

ST KITTSNEVISAMERICAN 

AIRLINES

09/11/2011 FOR SOLID WASTE STORAGE, COLLECTION, 

TREATMENT AND DISPOSAL.

-AQ- AIRPORT CHARGE ST KITTSNEVISAMERICAN 

AIRLINES

10/11/2011 AIR SERVICE CHARGE TO UPGRADE AND 

MAINTAIN THE AIRPORT INFRASTRUCTURE 

AND A SECURITY CHARGE FOR THE 

PROVISION OF SECURITY EQUIPMENT AND 

SERVICES AT THE AIRPORT.

-XM- SECURITY CHARGE LATVIA AIR BALTIC 04/01/2012 CHARGE FOR SECURITY AND RESCUE

-XN- EMBARKATION FEE ERITREA ERITREAN 

AIRLINES

04/01/2012 PASSENGER SERVICE

-XU- AIR TRANSPORT 

SUPERVISION 

CHARGE

FINLAND FINNAIR 04/01/2012 TO COVER THE COSTS OF FLIGHT SAFETY 

AND SECURITY OVERSIGHT AND PUBLIC 

ADMINISTRATIVE DUTIES IN THE FIELD OF 

AVIATION IN FINLAND.

-XZ- SECURITY CHARGE PAKISTAN PAKISTAN 

INTERNATION

AL AIRLINES

05/01/2012 COVER EXPENSES INCURRED FOR SECURITY

-YD- INFRASTRUCTURE 

DEVELOPMENT 

CHARGE

PAKISTAN PAKISTAN 

INTERNATION

AL AIRLINES

05/01/2012 INFRASTRUCTURE DEVELOPMENT

-YI- GOVERNMENT 

AIRPORT TAX

PAKISTAN PAKISTAN 

INTERNATION

AL AIRLINES

05/01/2012 GENERATE ADDITIONAL REVENUE

-YM- DEVELOPMENT FEE INDIA AIR INDIA 11/01/2012 BRIDGE THE FUNDING GAP FOR 

INFRASTRUCTURE DEVELOPMENT AT INDIRA 

GANDHI INTERNATIONAL AIRPORT (DEL)

-BV- SAFETEY AND 

SECURITY CHARGE

COMOROS AIR AUSTRAL 19/01/2012 SAFETY AND SECURITY PROVISIONS AT THE 

COMOROS AIRPORTS

-FM- PASSENGER SERVICE 

CHARGE

COMOROS AIR AUSTRAL 19/01/2012 PROVISION OF PASSENGER SERVICES

-YU- CIVIL AVIATION TAX COMOROS AIR AUSTRAL 19/01/2012 GOVERNMENT REVENUE, CIVIL AVIATION

-GS- SALES TAX COMOROS AIR AUSTRAL 19/01/2012 GOVERNMENT REVENUE, TAX ON CONSUMPTIO

-XI- AVIATION 

INFRASTRUCTURAL 

DEVELOPMENT FUND 

LEVY FEE

ZIMBABWE AIR 

ZIMBABWE 

20/01/2012 FOR AN INFRASTRUCTURE DEVELOPMENT 

AND EQUIPMENT MODERNIZATION 

PROGRAMME BASED ON THE USER-TO-PAY 

CONCEPT.

-YV- AIRPORT CAPITAL 

IMPROVEMENT 

SURCHARGE

GRENADA VIRGIN 

ATLANTIC 

AIRWAYS

26/01/2012 AIRPORT INFRASTRUCTURE, REPLACEMENT OF 

NAVIGATION AIDS AND RUNWAY REPAIRS.
Attachment: B

Page: 2

-AD- VALUE ADDED TAX DEMOCRATIC 

REPUBLIC OF 

CONGO

BRUSSELS 

AIRLINES

08/03/2012 COLLECTION OF GOVERNMENT 

APPROVED DOMESTIC VALUE 

ADDED TAX. 

-AH- AIRPORT SECURITY FEE PANAMA COPA AIRLINES 21/03/2012 TO SUPPORT SECURITY SERVICES IN 

TOCUMEN INTERNATIONAL AIRPOR

-AV- VALUE ADDED TAX MONGOLIA MONGOLIAN 

AIRLINES

26/03/2012 COLLECTION OF GOVERNMENT 

APPROVED DOMESTIC VALUE 

ADDED TAX

-SS- EXCISE TAX SOUTH SUDAN KENYA AIRWAYS 04/04/2012 COLLECTION OF GOVERNMENT 

APPROVED EXCISE TAX

-CS- CONSUMPTION TAX ANGOLA TAAG 12/04/2012 COLLECTION OF CONSUMPTION 

TAX APPLIED TO DOMESTIC 

FLIGHTS

-FT- AIRPORT DEPARTURE 

TAX 

SOMALIA TURKISH 

AIRLINES

18/04/2012 FOR PROVISION OF AIRPORT 

SERVICE

-HM- PASSENGER FACILITY 

FEE

BAHRAIN EMIRATES 09/05/2012 COLLECTION OF CUP CHARGES

-IO- AIRPORT BUILDING

CHARGE

SAUDI ARABIA EMIRATES 18/05/2012 FOR DEVELOPMENT OF MED 

AIRPORT

-LI- PASSENGER SERVICE 

CHARGE

PHILIPPINES PHILIPPINES 

AIRLINES

29/05/2012 PASSENGER SERVICE

-MC- AVIATION SECURITY 

CHARGE

SIERRA LEONE BRUSSELS 

AIRLINES

04/06/2012 PROVISION OF SECURITY 

FACILITIES

-NS- SALES TAX SOMALIA TURKISH 

AIRLINES

05/06/2012 SALES TAX LEVIED ON ALL 

INTERNATIONAL AND DOMESTIC 

TICKETS ISSUED AND SOLD 

WORLDWIDE FOR TRAVEL

INCLUIDING A POINT IN 

SOMALIA

-QC- TRAVEL PROMOTION 

LEVY

ARUBA TIARA AIR 

ARUBA

20/06/2012 CONTRIBUTION FOR THE

PROMOTION OF TOURISM IN 

ARUBA

-QE- DEPARTURE TAX COOK ISLANDS AIR NEW 

ZEALAND

28/06/2012 PASSENGER SERVICE

-QK- AIRLINE PASSENGER 

LEVY

JAMAICA CARIBBEAN 

AIRLINES

07/08/2012 PASSENGER SERVICE

-QP- PASSENGER SAFETY 

AND AIRPORT 

DEVELOPMENT 

CHARGE

TURKMENISTAN TURKMENISTAN 

AIRLINES

22/08/2012 SAFETY AND AIRPORT 

DEVELOPMENT
Attachment: B

Page: 3

CODES RESCINDED, WITHDRAWN OR EXPIRED

CODES REINSTATED

No codes were reinstated

CODE NAME COUNTRY REQUESTED

BY

DATE PURPOSE / DETAILS

-CD- INTERNATIONAL AND 

DOMESTIC SALES TAX

DEMOCRATIC 

REPUBLIC OF 

CONGO

BRUSSELS 

AIRLINES

08/03/2012 CD code remains assigned to 

both Tourist Development Fund 

and Embarkation and Security 

Tax

-ZL- DOMESTIC AND 

INTERNATIONAL FISCAL

STAMP TAX

ANGOLA TAAG - LINHAS 

AEREAS DE 

ANGOLA

20/03/2012 The code ZL is now available for 

new assignment from 

21/03/2014
Attachment: C

Page: 1 of 1

Tier 2 Agreements – for the PSC

• Resolution 700 - Acceptance and Carriage of Passengers Requiring Special 

Assistance

• Resolution 724 - Ticket Notices

• Resolution 745b - Acceptance of Power Driven Wheelchairs or Other Battery 

Powered Mobility Aids as Checked Baggage

• RP 1700b - Carriage of Passengers with Reduced Mobility and Escorts 

Requirement

• RP 1700c - Seat Assignment for Passengers With Reduced Mobility and for 

Escorts

• RP 1700d - Passengers with Reduced Mobility Group Travel

• RP 1700e - Publication in Airline Guides of Rates and Conditions Relating To 

Travel of Passengers with Reduced Mobility

• RP 1708a - Passenger Assistance List (PAL) and Change Assistance List (CAL)

• RP 1724 - General Conditions of Carriage (Passenger and Baggage)

• RP 1749 - Carriage of Carry-on Baggage

• RP 1799 - Denied Boarding Compensation
IATA presents the New 

Simplifying the Business 

(StB) Program

Tomorrow’s passenger journey will be simple, 

from travel shopping to airport security

IATA presents the New Simplifying the Business Program

Air transport today is an integral part of the global economy. The industry moves people and goods across the globe 

quickly and efficiently, fostering economic development, greater human understanding and international trade. In the 

future, as economic interdependence grows so will the need for fast and secure transport, facilitated by a successful 

aviation industry. But our industry has been in survival mode for as long as we can remember. Today’s environment is no 

exception, as we struggle to contend with a deepening economic crisis, increasing government regulation and oil price 

uncertainty. 

To put ourselves on a path toward sustainable profitability, we must innovate together to provide the foundation for 

new, efficient ways of doing business, enabling the creation of new products tailored to specific unique customer 

needs, providing better service and preserving healthy competition. Today consumers face numerous pain points 

in their journey, from the travel shopping experience to long lines at security.

Since 2004, the industry has completed transformational projects through the StB program and delivered projects 

on e-ticketing, common-use self-service kiosks, bar coded boarding passes, automated baggage rules etc, saving 

the industry up to $18bn. The first set of StB projects is coming to a natural end, and in 2011 the StB think-tank 

was created to identify the next set of transformational projects that will help the industry to “prepare for tomorrow’s 

passenger”. 

Last year the StB think tank identified 5 goals (airline products, passenger data, real-time interaction, hassle free, 

and a seamless journey) which provide the framework to guide us to a more efficient industry and a new customer 

experience, in a transformed environment that embraces innovation. Now in its second and final year in its current format, 

the work of the StB think tank will conclude with the identification of a new set of transformational work programs, set 

out in this document. These will be the focus of a renewed StB program designed to deliver the 5 goals which aim to 

change the passenger experience and revolutionize how we travel by 2020. 

Sincerely yours,

Eric Léopold

Director, Passenger

IATA 

02
A DAY IN THE LIFE – 

A TRAVEL EXPERIENCE 

IN 2020

Caroline, 38, is an eCommerce consultant. She and 

her husband live in the countryside outside of Milan.

It is Tuesday 22 September 2020, and Caroline is looking to book a long weekend trip with her partner – somewhere with great cultural and culinary options.

She is hoping to leave Milan on Wednesday evening to be 

able to get to her destination at a reasonable time to make 

the most of the stay. She activates the voice notification 

service on her personalized travel cloud, describes her 

requirements through her mobile phone (date, activities, 

flight time, time difference and so on) and asks for a recommended destination based on experiences reported 

by her friends, as well as her own preferences.

The suggested destination is Cape Town, and 

immediately, flight options appear. Her travel cloud has 

intuitively presented a virtually complete itinerary. Because 

Caroline’s buying behaviors are held in her travel cloud, 

the offers are personalized. She often goes away for the 

weekend with her partner and her buying patterns have 

been noted. The airlines know she does not always fly 

business, but sometimes upgrades her flight experience 

with greater seat pitch and extra pillows. They also know 

her partner is a vegetarian and prefers a window seat. 

For the flight and airport experience Caroline chooses 

extra leg room, lounge access and a priority boarding 

option. She books the suggested boutique hotel and 

selects from a choice of restaurants, but decides to 

wait on the excursions till she gets there.

She makes her final selections in her shopping cart 

and pays with her phone. She receives a summary of her 

entire trip which corresponds to all of the elements in her 

shopping basket, from the flight to the hotel reservation, 

restaurants and entertainement.

The voice notification reminds her that her e-passport 

will expire in about 9 months, including visas and biometrics. But it’s OK: the visa process is electronic and doesn’t 

involve any heavy paperwork like it did in the past. The visa 

is granted directly by the State and confirmed to the airline, 

eliminating surprises at time of boarding or on arrival in 

the country.

At the same time, her cloud informs her that their e-visas 

comply with the governmental requirements, her flight is 

confirmed and she and her partner are ready to fly.

On the day of travel they drop their bags at one of the 

downtown locations, on their way to the airport using 

public transportation. Their bags have an electronic tag 

that is built into their cases, and as a result they are known 

to the system. When arriving at the airport, there is nobody 

queuing in the very small departure hall: in the past there 

were people everywhere, queuing for check-in (which no 

longer exists as a process because passengers are all 

checked–in by default), for security, etc. Their passports 

are electronic and contain their biometric identifiers which 

act as their single token identifier and will correspond 

with their security checks and border controls.

They proceed through security. It is fast, seamless and 

barely noticeable. The design of security check point is 

such that although it is embedded with sophisticated 

technology, it does not feel intrusive. The couple is quickly 

assessed as not being a security risk. Immigration checks 

for passport and visa were done at the same time along 

with revalidation of information sent by her to the South 

African authorities at the time of making her reservation.

They get through from the curb to airside in a matter of 

minutes. Caroline has received two messages from airport 

retailers informing her of discounts on their favorite designer 

labels. They take the time for some duty free shopping and 

the items they purchase will be delivered upon arrival of 

their return flight. 

The final check is at the gate using the single token 

verification and they get through and board the aircraft.

During the flight while enjoying their previously ordered 

meals, one vegetarian and the other carb free, a member 

of the crew, as would an onboard concierge, approaches 

the couple to welcome them on board and to apologize 

once more for the delay she incurred receiving her bag 

on her last trip. As she is connected through Wi-Fi while 

airborne, she is informed by the hotel that their room 

upgrade had been confirmed as requested. The crew 

member notices on the couple’s itinerary that they have 

not ordered a car at the airport and asks if they would like 

to order one. They gladly accept the offer and take the 

opportunity to add a short excursion to Table Mountain. 

The car is ordered and paid for as it is added to their 

shopping basket.

03
The travelers know that their bags will be picked up and 

delivered to the hotel, as the information will be automatically electronically pushed to the hotel address, as per 

the information made available to the airline. On arrival the 

couple passes through immigration using the automated 

border control gate with their single token; the ready-tofly status also means ready-to-arrive, just an automated 

biometric identity check is done to ensure it all matches. 

They leave the airport after a very pleasant experience 

and start to enjoy their weekend.

During their transfer to Table Mountain, she enters some 

comments about her trip in her travel cloud, to share her 

experience with her friends in case they are looking for a 

nice trip in the near future. She updates her social media 

sites with the following status: “Very pleasant journey. 

All went to plan. We arrived here feeling great, and have 

time to see the magnificent views of Cape Town from the 

top of Table Mountain. Flying is such a beautiful thing, 

and so simple.”

04
GOAL 1: AIRLINE PRODUCTS

Where we are today

Many airlines have invested heavily in their direct 

sales channels (e.g. web site) by deploying Customer 

Relationship Management (CRM), loyalty, dynamic product 

inventory systems and affinity search and pricing engines, 

to improve their retail capability and the customer experience they are offering. In many cases, this customer

centric retail-based strategy has worked well for them. 

For airlines, there are two key benefits of this direct 

retail approach:

1. Direct interaction with customers, enabling customer 

relationship management and personalization.

2. Increased speed to market of new products, enabling 

product innovation and differentiation, also providing 

visual displays of their products.

Consumers have come to expect this customer-centric, 

retail approach, where the consumer is king, and which 

has been adopted by many other industries (such as consumer goods with Amazon and music with Apple’s iTunes 

for example). Consumers expect airlines to compete 

through product choices and product personalization, 

as well as price and schedule – offering customized 

value instead of a commodity.

Unbundling the product has become increasingly popular 

with some carriers. It involves breaking down the journey 

into separate components to allow customers to pick and 

choose what they value. Some customers might prefer 

lounge access with an economy fare, while others may 

want to ensure a seat with extra leg room.

Unfortunately, the existing indirect channel tells a 

different story. This channel still mostly manages the 

travel experience as a commodity. It was not designed to 

support product differentiation and innovation nor was it 

designed to support product personalization. For example, 

as of today, the indirect channel is limited in offering and 

displaying the full range of products and services to enable travel agents to give the customer a personalized 

choice of fares and services that might be available 

from the airline.

About half of airline tickets worldwide are sold via 

Global Distribution Systems (GDSs), meaning that 

airline revenue opportunities from ancillary services are 

restricted. In 2011, ancillary revenues were worth around 

US $32.5 billion to the industry, according to an Amadeus 

and IdeaWorks report. This represented a 43.8% increase 

on 2010, almost exclusively through direct sales.

For customers to be better informed and offered 

greater choice, air transport must develop a model that 

works across all channels, that focuses on customers 

and provides a true retail experience.

Vision 2020

The future will be a travel industry where customers 

can choose to access the products they desire, with ease, 

and benefit from personalized and dynamically packaged 

offers. Airlines will be able to tailor products according to 

an individual’s buying habits and agreements that they, 

or their employers, might have with an airline. They will 

be able to offer these products and services through all 

channels if they choose to do so. 

Programs of work

IATA launched the e-services project in January 2010 and 

the New Distribution Capability project in January 2012.

E-services

The Electronic Miscellaneous Document (EMD) is 

a “method to document the sales and track usage of 

charges”. In other words the scope of EMD is to facilitate 

the fulfillment, tracking and accounting of the ancillary 

sales. This project will come to a close at the end of 

2013 when EMD will be rolled out across the industry.

New Distribution Capability

The aim of this initiative is to enhance the airline indirect 

distribution channel by developing a set of industry standards for the transmission of data that will facilitate product differentiation, increased sales of ancillary products 

and services and personalized offerings. For passengers, 

this initiative will offer more choice of products and services, more personalization and more transparency.

The industry will benefit from a model which is retail like 

(shopping cart), customer centric (personalized packages) 

and which offers differentiated shopping (for example 

upsell, cross-sell) as the customer chooses.

05
06
GOAL 2: PASSENGER DATA

Where we are today 

Today, harmonization between countries on the collection 

and distribution of passenger data is limited and is 

complicated by an increase in both privacy and security 

regulations affecting passenger data by more and 

more governments. Airlines are liable for fines when 

passengers are denied boarding due to missing data 

or documentation. Passengers are confused due to the 

inconsistency of the information required depending 

on different regulations.

In most cases airlines are required to collect relevant 

data prior to departure. Depending on where the passenger interacts with the airline, this may be online, at 

check-in, at bag drop or even at boarding. This process 

can cause delays in the check-in process and on occasion, 

results in denied boarding due to documentation not being correct to allow the passenger to travel, as airlines 

may not be able to validate whether the passenger has 

the right documentation until they reach the gate. 

As a consequence, carriers have had to invest in their own 

IT systems to meet the different government requirements, 

or contract with independent data processors. This has 

resulted in additional costs to carriers and separate, 

often incompatible solutions across the industry.

Vision 2020

In 2020 passengers will know that they are ready to fly, 

because governments will have confirmed that they can 

in advance. And becoming “ready to fly” will be simple.

Program of work

Through a closer relationship with authorities, the industry 

is helping to shape and harmonize the regulatory framework. Previously, the standards for the transmission of 

such data were not always harmonized. In 2011, several 

data-alignment initiatives conducted with various countries 

were successfully concluded. IATA proposes one new 

program of work.

E-Border

The Australian government has led the way in the last 

few years with the “e-visitor program”. It’s the passenger 

who executes the process and the government that 

confirms if the visa application has been successful 

or not. This is direct interaction between passenger 

and government. There are other countries with similar 

programs for example the US with the Electronic System 

for Travel Authorization (ESTA) which is more like a 

waiver than a visa.

The industry and passengers would greatly benefit 

from adoption of a program that is similar to the Australian 

program in a globally harmonized manner, with an extension 

that allows passport data to be electronically verified, 

similar to how banks verify credit cards. The International 

Civil Aviation Organization (ICAO) is the appropriate 

body to move this forward with input from the industry. 

Governments that have been approached are aligned 

and as with ESTA in the US, the process costs can 

be recovered. This is a significant task that will require 

government support globally, but that can unlock huge 

benefits for the industry and the customer.

The E-Border program will establish the deployment 

of standardized data requirements and remove paper 

from the system. The next strategic phase will be for 

the industry to aim for governments to adopt a passport 

validation system complemented by global e-Visas which, 

depending on the risk profile, are completed by the passenger around the time of booking or in the consulate 

or embassy. This will simplify the process and allow the 

validation to be moved away from the airport and to the 

government in advance of the journey, which will also 

enable better border control. 

07
GOAL 3: REAL-TIME INTERACTION

In many processes related to passenger air travel, 

having the contact details of the traveler is important. 

For example, the airline might want to let a passenger 

know of a disruption, inform her on the tracking of her baggage, or offer a special service to drive customer loyalty 

and satisfaction.

Currently, while there are some standards on how 

certain passenger contact details could be transmitted, 

there are no rules as to when and what details must be 

communicated from one entity to the next, for example 

from the booking source to the airlines, the passenger 

to the airline, or an airline to a partner airline.

So to overcome the problem of incorrect or missing 

information, standards should be set to clarify which 

elements need to be sent with which message, and 

possibly for which purposes they should and should not 

be used — all established within the existing regulatory 

framework. And ideally the passenger contact information 

should be provided to the airline at the time of booking 

just like in an online retail experience.

Customers to have easy access 

to real-time airline data, at airports

The industry and the customer need to be able to interact 

at anytime and anywhere. This is essential for the industry 

to provide better service for customers. Good connectivity will build the personalized relationship that all parties 

need. Currently access to Wi-Fi is fragmented, there are 

no global standards and high roaming charges hinder 

access. Airlines and their partners need to agree on a 

solution that will make access easy, instantaneous and 

less than one click away. 

Where we are today

Passengers suffer from uncertainty and stress associated 

with queues, flight delays, cancellations and bag mishandling. Optimization of modern technology could go a long 

way to ease the pain, by allowing access to information in 

real-time. 

Today the lack of customer contact information creates 

further frustrations for passengers, airlines, and airport 

staff when dealing with irregular operations. Social media 

and smart phones deliver immediate information to passengers that are not necessarily available to airline and 

airport staff who manage customer service and expectations. So in some cases the passenger is getting more 

information about what’s happening than the employees 

at the airline or airport.

Airlines do a good job with contact information for frequent flyers but that only covers a small portion of their 

customer base, and the majority of airlines do not have 

all the crucial passenger contact data available, making it 

very difficult to implement any true customer experience 

management solutions.

Vision 2020

Real-time and contextualized communication between 

airlines and their customers will transform the passenger 

travel experience. Cooperation across the whole value 

chain to maintain this relationship will build loyalty and 

bring benefits for all.

Programs of work

IATA will launch 2 new programs of work in this area.

Customer Contact Information

To be able to deliver excellent customer service 

the airlines need to have sufficient passenger contact 

details available to reach the passenger, including when 

the passenger has already commenced the trip. This will 

enable proactive and real-time messages; it will also allow 

the passenger to request relevant real-time information 

when needed.

08
GOAL 4: HASSLE FREE

Where we are today

The biggest pain point for passengers today is the 

hassle associated with airport processes and controls. 

Passengers experience uncertainty and stress due to 

inconsistency and unpredictability of processes at airports 

which can be better integrated than they are today. There 

can be long wait times, in addition to different procedures 

to be followed at different airports around the world. The 

goal is to move as many steps as possible off airport.

Vision 2020

The airport experience is fast: curb to airside is seamless. 

It is predictable, secure and globally consistent. 

Programs of work

IATA has a number of different initiatives already in 

place, and some new programs are proposed below, 

the combination of which will lead to a seamless airport 

experience for the passenger.

Fast Travel

Fast Travel will satisfy the passengers’ demands for self 

service options across their journey, from boarding pass to 

baggage collection. By 2020, 80% of global passengers 

will be offered a complete self-service suite based on 

industry standards.

Checkpoint of the Future

Security processes are evolving to be risk-based 

and IATA’s flagship security program, ‘Checkpoint of 

the Future’ is built around this principle. In the long term, 

the project will build toward a paradigm shift in screening 

that includes a fully integrated model for passenger differentiation, biometrics and advanced screening technologies to further improve security while minimizing the need 

for passengers to unpack or disrobe. 

Automated Border Control

As the passenger credentials for both departure and 

arrival immigration clearance have already been verified, 

including risk assessment, by the relevant immigration 

authorities (see Goal 2), all that is required is to ensure 

that the passenger is the person that he/she states to 

be. That can be done in a fast and low intrusive biometric 

way, whereby only exceptional cases are to be handled 

manually. 

Check-out (no more check-in)

At the time of booking a passenger should be considered 

checked in. Seating may be assigned either by the 

passenger at the time of booking or by the airline at the 

moment that the passenger passes the security checkpoint. This will ensure that the airline knows precisely 

who will fly, which allows the fast and efficient completion 

of flight release for which exact passenger numbers are 

required. 

The elimination of the check-in process will further enable 

airlines to simplify the business, save time and reduce costs.

Fast and simple common bag drop

The ideal scenario for the future would be for passengers 

to be able to drop their baggage off even before they 

reach the airport. In the short term the industry would 

benefit from a global common standard for bag drop and 

airport processes with the aim to create a more consistent 

customer ground experience. This can be achieved by 

having the baggage tagging process completed before 

the passenger reaches the airport, through factory in-built, 

or airline supplied, permanent baggage tags or simply 

home printed baggage tags. These new processes could 

enable a much faster and simpler bag drop experience.

09
Single token

A single token for all elements of a journey would 

significantly streamline and simplify the travel process. 

The single token would correspond to everything from 

travel documents, access on board the aircraft to a bag 

identifier and all of the ancillary purchases bought at the 

time of booking.

To get there the industry needs to set an interoperability 

blueprint as a first step. There are questions, such as 

what will the token be attached to? It could be linked to 

biometrics or ePassports. This in turn could address the 

necessity for boarding passes and passport checks at 

the gate by building the two elements into part of a single 

electronic token. The “boarding pass” as we know it now 

will cease to exist.

And, if all of these processes are completed around the 

time of booking, off airport (see Goal 2 - Passenger Data), 

with the passenger validated by the government as ‘ready 

to fly’, this could be one of the key enablers for a seamless 

and intuitive travel experience.

10
GOAL 5: SEAMLESS 

END-TO-END JOURNEY

Where we are today 

Customers cannot experience a seamless integrated 

journey of a consistently high quality with reduced stress 

levels if travel partners are not connected. Currently there 

are no reliable connections between airlines, railways, 

hotels, rental car and other travel related companies. When 

a flight is changed, for example, the airport pick-up service 

may not be notified, or the cruise ship that is connected to 

the flight has not been informed, these elements create a 

disconnected travel experience for the passenger. 

The center of all elements that make up a journey from 

start to finish is the traveler. Today all of the sections of 

a journey are kept in separate information repositories 

with various travel service providers; there are different 

accounts for different airlines, car hire companies, or hotel 

chains for example. These repositories are standalone 

pockets of information, precluding the possibility of seamless travel in certain key areas of the travel experience. 

The lack of a standardized industry framework hampers 

opportunities for technological development, improvement 

of the travel experience, and ancillary offerings. 

 

Vision 2020

All travel partners, covering the whole trip, including the 

customer, will have the ability to exchange information with 

each other across the entire journey, with permission of 

the customer. 

Programs of work

IATA will launch two new programs of work that will 

provide the capability for the customer to have access to 

all travel elements together in one place, with technology 

that allows travel partners to exchange vital information 

with each other, and the traveler, in a single repository. 

Airline Industry Application Programming Interfaces 

(APIs)

This concept is about enabling a set of services “publish 

and subscribe” which is a contract between the customer 

and the service provider (or API provider).

• From a customer point of view this is about the 

customer being in control and interoperability across 

the travel experience;

• From an industry point of view it is about the need for 

a set of standards that will allow the eco-system to 

interact and exchange messages because all partners 

will have agreed on a common messaging standard.

In summary, it’s about creating the capability for 

a standard interface across the industry value chain. 

It means that all parts of the journey experience will be 

able to talk to customers: a late flight will trigger messages 

to the other travel partners who will then be able to adapt 

their service or product accordingly; a new meeting in 

the calendar will trigger changes to the itinerary and trip 

details. Ultimately it could allow the traveler to have all 

of her information interconnected in one location linking 

together credentials across all her travel partners.

This approach will foster the creation of new services 

to simplify the travel experience, automate information 

provision and minimize information inconsistencies, 

errors and duplication and put the customer in control 

of her travel information. It will also allow travel partners 

access to accurate passenger information enabling them 

to communicate with each other and the customer more 

effectively.

Airline Industry Data Model

A passenger-centric airline industry data model will 

provide an invaluable base for airlines to manage the 

customer experience. The data model will enable airlines 

to link real-time passenger data flowing from a variety of 

sources, including reservation centers, airline web sites, 

mobile devices, and social platforms. An airline adding an 

analytics layer will provide it the key insights it needs to 

personalize the travel experience at every passenger 

touch point.

The data model will enable interoperability across the 

entire spectrum of services providers and agents, who 

work with airlines to provide a seamless travel experience. 

An industry agreed and open set of data standards will 

ease the entry of new players, stimulate innovation and 

increase the pace of change.

Accurate customer contact information is essential for 

all the components of the new passenger travel initiatives 

and the industry data model, the combination of which will

serve as the backbone for the industry and a catalyst for 

change.

11
12

The new StB program

Goal 1

Airline Products

Goal 2

Passenger Data

Goal 3

Real Time Interaction 

Goal 4

Hassle Free

Goal 5

Seamless Journey

Vision 2020 The future will be a 

travel industry where 

customers can choose 

to access the products 

they desire, with ease, 

and benefit from personalized and dynamically packaged offers. 

Airlines will be able to 

offer these products 

and services through 

all channels if they 

choose to do so.

In 2020 passengers 

will know that they are 

ready to fly, because 

governments will have 

confirmed that they 

can in advance. And 

becoming “ready to fly” 

will be simple.

Real-time and contextualized communication 

between airlines and 

their customers will 

transform the passenger travel experience. 

Cooperation across the 

whole value chain to 

maintain this relationship will build loyalty 

and bring benefits for all.

The airport experience 

is fast: curb to airside is 

seamless. It is predictable, secure and globally consistent.

All travel partners, 

covering the whole trip, 

including the customer, 

will have the ability to 

exchange information 

with each other across 

the entire journey, 

with permission of 

the customer.

Where we 

are today

Commoditized products 

and a dominance of a 

small number of large 

players. Airlines cannot 

offer passengers personalized packages due 

to lack of visibility of 

their full product range.

Passengers send 

passport and visa 

information to airlines. 

The airline sends that 

information to governments. The airline is 

held responsible for the 

integrity of the information, and liable for fines. 

Passenger information 

is incomplete and 

fragmented.

Passengers don’t know 

what to expect with 

inconsistent queuing 

times, along with cumbersome processes.

Travel partners, airlines, 

railways, hotels etc. are 

not connected, which 

can lead to a disjointed 

and frustrating travel 

experience for the 

customer 

Programs 

in place

• E-Services (EMD) • Fast Travel

• Check point Of the 

Future

• Automated Border 

Control

New 

Programs

• New Distribution 

Capability (NDC)

• E-Border • Customer Contact 

Information

• Customers to have 

easy access, to realtime airline data, at 

airports

• Check out (no more 

check in)

• Fast and simple 

Common bag drop

• Single token

• Airline Industry APIs

• Airline Industry Data 

Model

12
13

• True Customer focus:

Customers will be recognized and remembered as 

opposed to being treated as a one-off transaction.

• Acceleration of innovation:

It will be easier and faster to innovate; airlines will be 

able to offer more products and services with dynamic 

packaging, greater benefits will be unlocked from the 

New Distribution Capability (NDC) standards.

• Cost savings:

Process simplification could drive significant back office 

cost savings.

• Greater flexibility:

It will provide the industry with a greater ability to adapt 

to structural changes e.g. mergers, or joint ventures. 

IATA will bring together a group of airline experts who will 

establish the detailed scope of this new topic. This group 

will report back to the 2013 World Passenger Symposium 

with an assessment of the opportunities and benefits and 

a recommendation for next steps.

FURTHER DEVELOPMENT 

The StB think tank has identified a new development 

which could further transform the airline industry. 

It consists of streamlining the airline back-office 

financial process.

Since the 1970’s and well before the internet was 

invented the airline industry has been at the heart of 

e-commerce. Passengers have benefited from a near 

real-time automated reservation exchange that has 

enabled passengers to have one ticket for one journey 

over multiple airlines. This has served the industry and 

its customers well to date, but the current processes 

and systems lack flexibility to serve the customer and 

fulfill buying expectations in today’s world of eCommerce 

merchandizing, not to mention the huge costs for the 

industry that this model generates.

In a new transformed model, where airlines will treat 

customers uniquely based on a relationship and not 

just a transaction, what should become of the notion 

of Ticket, PNR and Passenger Revenue Accounting ? 

Any simplification of the “order to cash” process should 

deliver benefits in the following areas:
CONCLUSION

The Simplifying the Business program is all about 

delivering value. We need to have a common vision 

across the value chain of what needs to be achieved 

and the value that it will bring to the industry and to its 

customers. Once we have that, good ideas, upon which 

we can cooperate, can form the foundation for further 

innovation. In other words, when people and companies 

see the value that is to be gained, they are ready to work 

together.

This paper is the result of just that. A dedicated group 

of airline people and experts from air travel and other 

industries working collaboratively to fit together the 

pieces into work programs; looking into the near future 

to ensure that the needs and ever growing expectations 

of consumers are met, and that the whole of the value 

chain has the necessary technological and regulatory 

framework in place to enable it to flourish.

The paper is shared at the annual World Passenger 

Symposium where the air travel industry meets, reviews 

progress, identifies new trends, adjusts industry roadmaps 

and agrees on industry standards, with a single and 

committed voice.

Aviation is an important force for good in our world, 

enabling journeys of discovery, bringing goods to market 

and reuniting friends and families. In its first hundred 

years, commercial aviation has changed the way that the 

world lives and works together. And we have only just 

begun. Working together, we can drive change to deliver 

even greater value in the next century of commercial air 

transport.

Simplifying the Business (StB) does not belong 

to IATA - it belongs to the airline industry as a whole. 

From e-ticketing through to today’s new programs of 

work, StB remains a call to action which is recognized 

as bringing transformational change to benefit the entire 

aviation value chain and the customers it serves.

IATA will lead this new program on behalf of and in 

collaboration with the entire air travel value chain. 

14
Airline Delegates 

The following airline delegates are members of the StB 

Think Tank and were appointed to propose a way forward 

for Simplifying the Business.

Matthias Koch

Director Customer Ground Experience

Air France - KLM

Todd Grace

Strategy Manager

Air New Zealand

Glenn Morgan

Head of Service Transformation

British Airways

CONTRIBUTIONS 

IATA wishes to thank all contributors to this paper. 

The names of participating airlines and strategic partners are listed below. 

Credits: 

Yanik Hoyles – IATA StB think tank facilitator

Rosalind Shirkie – IATA StB think tank copywriter

Stephanie Yen

Manager Industry Affairs

Delta Air Lines

Rob Broere

Vice President IT – Passenger Services 

Systems & Passenger Experience

Emirates 

15
Nicola Simionato

General Manager, EMEA / APAC

ITA Software at Google

John Thomas

Vice President

LEK 

Vijay Anand

Senior Director, Industries Business Unit

Oracle

Strategic Partners

The following delegates were appointed by their 

companies, which are IATA Strategic Partners, to advise 

IATA on the implementation of strategic initiatives.

Patricia Semillon Dorne

Head of Airlines Operations Strategy, 

Airline IT Amadeus

Ike Anand

Senior Director, Strategy 

and Business Development

Expedia, Inc.

Daniel Friedli

Travel and Transportation Product Strategy

Hewlett Packard

16
THE GLOBAL

PASSENGER SURVEY 2012

www.iata.org/paxsurvey

NO-ONE 

CAN 

STAY

YOUNG

FOREVER

Out of all the choices for 

favorite things to do during a 

flight, ‘playing games’ was 

the least popular.

Even less popular than 

‘catching up on work’!

We know because we asked.

Do you know what passengers really think?

We know because we asked air travelers of every 

age, background and gender in more than 100 

countries.

Independent, in depth and unbiased, the IATA Air 

Passenger Survey gives unrivalled insight into what 

passengers want, how they behave, why they make 

choices and what they spend their money on. 

If you can step into the heads of your customers, 

you can stay a step ahead of the competition. 

To find out more, email paxsurvey@iata.org or visit:

www.iata.org

PRINTED IN SWITZERLAND – OCTOBER 2012
Simplifying the Business 1  COPYRIGHT IATA 2012

New Distribution Capability 

(NDC)

Webinar: Introducing Resolution 787 

‘Enhanced Airline Distribution’ 
Simplifying the Business 2  COPYRIGHT IATA 2012

Webinar Presented by the NDC 

Team

Facilitator: Shaunelle Harris Drake

Manager, NDC Implementation 

Presenter: David McEwen 

Manager, Airline Distribution Standards
Simplifying the Business 3  COPYRIGHT IATA 2012

Guidelines for Participation 

This meeting is being conducted in compliance with the Provisions for

the Conduct of the IATA Traffic Conferences. Pursuant thereto, this

meeting will not discuss or take action to develop fares or charges, nor

will it discuss or take action on remuneration levels of any

intermediaries engaged in the sale of passenger air transportation. The

meeting also has no authority to discuss or reach agreement on the

allocation of markets, the division or sharing of traffic or revenues, or

the number of flights or capacity to be offered in any market. Delegates

are cautioned that any discussion regarding such matters, or

concerning any other competitively sensitive topics outside the scope of

the agenda, either on the floor or off, is strictly prohibited.
Simplifying the Business 4  COPYRIGHT IATA 2012

 Objective

 Introduction and background to NDC

 Some Clarifications

 Benefits the WIN! WIN! WIN! WIN!

 Introducing Resolution 787 

 Resolution 787 Highlights

 Introducing Your NDC Team

 Final Thought

 Questions 

Running Order
Simplifying the Business 5  COPYRIGHT IATA 2012

 Provide Detailed Background

 Understand the Issues that are Raised

 Look at NDC, what it is and what we are doing

 Look in detail at the proposed Resolution text

 Opportunity for you to review the proposal

 Ask questions and give feedback

Objective
Simplifying the Business 6  COPYRIGHT IATA 2012

What is Distribution

 How the airline product gets to 

their customer

 All the processes are connected

 NDC will first focus on building 

standards that impact the 

shopping process

Airline Distribution Life Cycle

NDC focuses 

on this aspect 

of the process
Simplifying the Business 7  COPYRIGHT IATA 2012

Introduction to New Distribution Capability 

 What IATA member airlines are saying:

 Need ability to differentiate through innovation and personalization

 Need ability to sell what they want to whom they want through more 

channels

 What is IATA going to do about it:

 Setting Industry Standards to support airline distribution capability

 The new standards aim to stimulate competition, innovation and offer 

more choice to consumer
Simplifying the Business 8  COPYRIGHT IATA 2012

Stakeholder Engagement

 NDC – A balanced view & value chain collaboration 

 Stakeholder engagement - Collaborative mindset, fully open and 

transparent 

 Engage all players 

 Airlines (IATA members and non-members) 

 System providers – GDSs and others 

 Third parties – ATPCO, ARC, etc. 

 Travel agents – including TMC and online TAs

 Engage at all levels

 Board 

 PDG

 Distribution Data Exchange Group 
Simplifying the Business 9  COPYRIGHT IATA 2012

 Passenger Distribution Group (PDG)

 Includes Directors Distribution at AC, AZ, UA, DL, AF/KL, BA, LH, LX, KE, CX, SQ

 Initial meeting: 7th September 2011

 Membership in the group is restricted to airlines

 PDG unanimously endorsed the NDC model

 Endorsement for model: 18th April 2012

 There are 8 Key principles

 Stakeholders and landscape for new model

 Message flows

 PDG created a Distributed Data Exchange workgroup (DDX WG)

 First meeting: July 09-13, 2012

 Next meeting: Nov 27-30, 2012

NDC Background - Summary
Simplifying the Business 10  COPYRIGHT IATA 2012

So... What is NDC About?

Enabling the capabilities that exist on the airlines’ website 

through Indirect channels

 There are 2 basic requirements

 A standard way of connecting (common API)

 Personalisation through Authenticated Shopping

 The initial scope is the shopping process

 In tomorrow’s new distribution, airlines will have greater ability to 

interact with who is requesting and provide tailor-made product 

offers

 Product innovation / Differentiation / Personalization
Simplifying the Business 11  COPYRIGHT IATA 2012

The Problem Today 

 Airline pushes the data – GDS constructs the offer

 Airlines push information through 3rd parties suppliers Distributors 

who constructs the final offer

 The “push” has limited interactivity with the airlines

 This became obvious constraints with ancillary trend, sophisticated 

dynamic pricing revenue management and increasing data mining 

usage 

 New technology: more agile, faster and more cost effective

 Lots of noise with several “standard organizations” aiming at reengineering distribution landscape (bottom – up approach) 
Simplifying the Business 12  COPYRIGHT IATA 2012

 It is critical airlines construct/own their product. Need to connect to 

customers through indirect channels with interactive relationship

 Should use modern messaging. XML based protocols and web 

services as an example

 Must not to be constrained by backward compatibility with existing 

legacy messages

 Standards must facilitate authentication of customer identity, enable 

personalized offers through the whole distribution supply chain

 The new model will be able to cope with changes and support a 

shopping basket approach (to add and remove product)

 The ways to display product attributes will be standardized to facilitate 

comparison on sites such as fare comparison sites

Key Principles New Distribution Model
Simplifying the Business 13  COPYRIGHT IATA 2012

Airline builds & owns a personalized offer for each consumer

Airline

Product 

Price and 

Availability 

Engine

Dynamic

Airline

Shoppin

g

Interfa

ce

Retailer

Consumer

Distributor

Retailer

Benefits: 

•Bring consistency in price/product offers across the different channels with one industry standard

•Greater access to airline ancillary products which currently are only available on individual airline websites 

and gain in competitiveness. 

•Increased competition in the area of distribution will mean more innovation and more choice for agents 

•Simplified and quicker shopping and booking process for the end-to-end journey
Simplifying the Business 14  COPYRIGHT IATA 2012

Areas to clarify

 This is not about by-passing the GDSs

 This is not about going direct to the Customer

 This not about simply rolling out the Direct Connect concept 

as it exists in the US today

 This is a top down approach where we will engage all key 

stakeholders

 Both distribution models will live side by side for some 

considerable time
Simplifying the Business 15  COPYRIGHT IATA 2012

 Airlines

 Passengers

 Distributors

 Travel Agents

What are the benefits of NDC?
Simplifying the Business 16  COPYRIGHT IATA 2012

Benefits of NDC 1/2

Airlines: 

 To bring consistency in price/product offers across the different channels with one 

industry standard

 Greater ability to recognize and reward customers 

 Increased competition in the area of distribution (system providers which will 

stimulate further innovation, improving the value offered by the indirect channel)

 Simplification of the airline distribution model

Passengers: 

 Greater transparency of what they are buying 

 Increased competition by getting access to each carrier’s full offerings, e.g., seat 

selection, lounge access, wifi, etc.

 Greater personalization and offerings based on authentication
Simplifying the Business 17  COPYRIGHT IATA 2012

Distributors

 A wider display of products and services

 Stimulate innovation and offer more choice to consumers

 Flexibility to bring new products to markets

 Ability to facilitate the content to Travel agents 

 With one industry standard it enables connectivity to Low Cost Carrier

Travel Agents:

 To bring consistency in price/product offers across the different channels with one 

industry standard

 Greater access to airline ancillary products which currently are only available on 

individual airline websites and gain in competitiveness. 

 Increased competition in the area of distribution will mean more innovation and more 

choice for travel agents 

 Simplified and quicker shopping and booking process for the end-to-end journey

Benefits of NDC 2/2
Simplifying the Business 18  COPYRIGHT IATA 2012

IATA DG & CEO Tony Tyler - IATA AGM, Beijing 11. June 2012 

“I have also focused on how IATA can contribute to greater innovation in distribution than is 

currently possible through the GDSs. I understand that airlines cannot afford to miss any more 

business opportunities while waiting for the GDSs to meet their needs. GDSs and others are of 

course welcome partners in the process. Our target is to complete the foundation standard for 

a new distribution capability for approval during the World Passenger Symposium this 

October. The new distribution capability will unleash innovation and new entrants that will 

revolutionize airline relationships with their customers. In parallel with developing the standard, we 

are evaluating what other innovations IATA can offer to ensure that we are delivering the greatest 

value to you in this area.”

NDC – Supported by the Board
Simplifying the Business 19  COPYRIGHT IATA 2012

Introducing Resolution 787

‘Enhanced Airline Distribution’
Simplifying the Business 20  COPYRIGHT IATA 2012

 Based on the key principles agreed at PDG 18 April 

2012

 Idea of a DAS API and the infrastructure framework 

diagram based on a small focus group discussion in 

February

 The basic business requirements for data exchange 

standards based on selected output from DDXWG in 

July

 Definitions to support the text 

 Reviewed and endorsed by PDG 11 September 2012 

The Resolution – How it was crafted 
Simplifying the Business 21  COPYRIGHT IATA 2012

 Is a foundational resolution to provide an industry 

framework for ‘authenticated shopping’

 Becomes a platform that will enable further resolutions 

and messaging standards to be developed as further 

business requirements are evaluated

 Covers the business requirements for data exchange 

standards

The Resolution
Simplifying the Business 22  COPYRIGHT IATA 2012

 All product offers (including ancillaries) will be available 

for distribution through all channels that an airline wishes 

to sell them through

 The standard will enable the creation of a Dynamic 

Airline Shopping engine Application Programme

Interface (DAS API) based on IATA XML messages

 The focus of this resolution will describe the main 

business processes that are required to support it

 Not be constrained by any need to have full backwards 

compatibility

Resolution Adoption
Simplifying the Business 23  COPYRIGHT IATA 2012

 Does not obligate any Member to implement this 

capability if they choose not to

 Members who choose to adopt the capability uses these 

standards

 Resolution does not mean industry mandate to do it but 

more if you decide to follow this business model this is 

how you should implement it. Systems should also follow 

it

 Recommended Practice offers a best practice to 

implementation

Resolution Adoption – what does it mean?
Simplifying the Business 24  COPYRIGHT IATA 2012

The New Distribution Landscape
Simplifying the Business 25  COPYRIGHT IATA 2012

Members and/or systems providers may, for online or interline carriage,

provide capability to offer a wide selection of their products and services to

their customers through a wide variety of distribution channels. Members

and/or systems providers shall apply the following procedures when

distributing enhanced content through multiple channels of distribution with

their many partners.

This resolution recognizes that a standard process is required for airlines

to create their own product offer within their own systems (i.e. assemble

fares, schedules and availability - all in one transaction) which will be

provided directly by and owned by the airline. This will enable more agile

pricing and more personalized offerings. In this way, all product offers

(including ancillaries) will be available for distribution through all channels

that an airline wishes to sell them through.

Resolution 787 Highlighted Text
Simplifying the Business 26  COPYRIGHT IATA 2012

Resolution 787 Highlighted Text

 2.1 ANCILLARY SERVICES means anything outside of product 

attributes (optional or discounted).

 2.2 AUTHENTICATION means the process by which a system 

identifies an individual or a business entity to make sure that the 

user or the business entity is who they claim to be, based on 

attributes that are sent in a message.

 2.3 DYNAMIC AIRLINE SHOPPING APPLICATION PROGRAMME 

INTERFACE (DAS API) means a set of routines, protocols and tools 

for building software applications capable of processing interactive 

messages from a requester to an airline rules engine.
Simplifying the Business 27  COPYRIGHT IATA 2012

 2.4 EXTENSIBLE MARK-UP LANGUAGE (XML) means a simple, 

flexible mark-up language which enables the exchange of a wide 

variety of data on the internet and supports the implementation of a 

wide range of web services.

 2.5 INTERMEDIARIES means any entity that has the capability to 

interface with an airline’s DAS API (e.g. metasearch engines, 

distribution channel IT solution providers, travel agents including 

online agencies, travel management and corporate travel 

companies, high street agencies, specialist agencies, tour and 

cruise line providers) and interline partners making a booking 

request. 

Resolution 787 Highlighted Text
Simplifying the Business 28  COPYRIGHT IATA 2012

 2.6 PRODUCT ATTRIBUTES means what is bundled and included 

in the fare, e.g. flat bed seat, in-flight entertainment, pre-reserved 

seating, meals etc.

 2.7 PRODUCT OFFER means the response including product 

attributes and ancillary services capable of being displayed in the 

requesting system.

 2.8 RULES ENGINE means the repository of an airline’s business 

rules capable of receiving and responding to requests to provide a 

product offer.

Resolution 787 Highlighted Text
Simplifying the Business 29  COPYRIGHT IATA 2012

Resolution 787 Highlighted Text

 3 Business Process Description

 Authenticate and Shop

 a dialogue ..... to request a product offer from a carrier and will allow 

such carrier to respond with the offer based on the information 

received in the request.

 Order Process

 A dialogue .... that will confirm the commitment to purchase. This 

may also include payment information. The order process will 

provide the carrier the opportunity to fulfill the transaction, create the 

booking record, issue the document(s) and respond with 

confirmations. 
Simplifying the Business 30  COPYRIGHT IATA 2012

 Change Process

 a dialogue .... that will request a modification, addition, cancellation 

or refund to an existing confirmed order. The request shall include 

data that enables a carrier to identify the original order.

 Data Elements

 A number of key data elements identified in the business 

requirements at DDXWG have been included in each process 

description text that should be included. This is not exhaustive and 

will be expanded in future workstreams. 

Resolution 787 Highlighted Text
Simplifying the Business 31  COPYRIGHT IATA 2012

 A Passenger Distribution Management Group hereinafter referred to 

as the Management Group is established for managing the 

development of passenger distribution processes and standards as 

published in IATA Resolutions and Recommended Practices, and 

the development of modern technology messaging standards (e.g. 

XML) under the provisions of Resolution 783. 

 Proposals to amend the passenger distribution standards may be 

submitted by the passenger distribution sub-groups, any A4A or 

IATA Member, or members of the IATA Strategic Partners Program.

Resolution 787 Highlighted Text
Simplifying the Business 32  COPYRIGHT IATA 2012

 The Passenger Distribution Implementation Manual shall 

contain:

 An end-to-end Passenger Process,

 A Passenger Process Toolbox covering the end-to-end process,

 Recommended Practices,

 Technical Specifications,

 Implementation Guides,

 Templates for Service Level Agreements

Resolution 787 Highlighted Text
Simplifying the Business 33  COPYRIGHT IATA 2012

Next Steps and Future Activities
Simplifying the Business 34  COPYRIGHT IATA 2012

ä IATA World Passenger Symposium, 16-18 October 2012

 New IATA Resolution 787 for airline distribution to be adopted at PSC 

October 2012

 Technical messaging standards to be developed (PADIS Board (XML))

 Industry Business Case & Roadmap to be presented to the Board

 Value chain collaboration

 Enable airline product differentiation

1st industry pilot in 2013

The Future of Airline Distribution – Next 

Steps and Activities
Simplifying the Business 35  COPYRIGHT IATA 2012

Introducing Your NDC Team
Simplifying the Business 36  COPYRIGHT IATA 2012

Introducing Your NDC Team

 Claude Muller; Head NDC

 Shaunelle Harris Drake; Manager NDC Implementation

 Cécile Rousseau; Manager Channel Distribution

 Guennadi Klioutchnikov; Manager Distribution Technical Standards

 Andrei Grintchenko; Manager NDC Standards
Simplifying the Business 37  COPYRIGHT IATA 2012

Final Thought
Simplifying the Business 38  COPYRIGHT IATA 2012

Questions, Summary, Conclusions ?

Its all Connected Through Automation
Simplifying the Business 39  COPYRIGHT IATA 2012

Questions
Simplifying the Business 40  COPYRIGHT IATA 2012

World Passenger 

Symposium and PSC

15-19 October 2012

Abu Dhabi

Further information and assistance

http://www.iata.org/workgroups/psc

http://www.iata.org/events/passeng

er-symposium/Pages/index.aspx
Simplifying the Business 41  COPYRIGHT IATA 2012
Attachment: F

Page: 1 of 1

Passenger Distribution Group (PDG)

Terms of Reference

The Passenger Distribution Group is established by the Passenger Services Conference 

(PSC) to with the following terms of reference.

Objectives

• Set a vision for multi-channel airline distribution

• Validate the strategy and industry business case and requirements

• Act as an industry voice on airline distribution

• Define key industry messages for distribution-related matters

• Review progress of IATA projects in distribution

• Act as a watch group on industry developments

• Be the central provider of industry informational and statistical data

Appointments

• This is a group comprised of IATA member airlines; non-member airlines may 

receive a special appointment by IATA SVP IDFS

• Delegates are airline director-level or above in charge of airline distribution or 

distribution system strategy; there are no alternates

• Industry stakeholders may be invited to attend meetings upon invitation by IATA SVP 

IDFS

Schedule

• annual in-person meetings at IATA’s Head (Montreal), Executive (Geneva), or 

Regional offices

• Regular calls (monthly or quarterly)

• Meeting agendas shall be circulated in advance of each meeting for review and 

comments by delegates, the Chairmen of the PSC Steering Group and the StB 

Steering Group. Minutes shall be taken at each meeting and circulated among the 

delegates for review, comment, and approval.

Technical sub-groups

1. The PDG may create technical sub-groups to address specific issues and business 

requirements, for example requirements to develop new schemas or rules and tools. 

Such sub-groups will be coordinated with the secretariat of the PSC and/or the 

Passenger Agency Conference (PAConf).

Administrative

• The PDG will have a one year mandate (renewable as required) and will report to the 

PSC with any proposed technical improvements, recommendations and an industry 

standards implementation plan.

• During the year the PDG will provide regular progress reports to the PSC Steering 

Group and the StB Steering Group

• The group will coordinate its activities with other industry groups involved in airline 

distribution

• The Secretary is the IATA Director Passenger (leopolde@iata.org)
Attachment: G

Page: 1 of 1

Data Dictionary and Schema Coordination Committee (DDSCC)

Terms of Reference

The DDSCC reports to the PADIS Board and is tasked to promote and oversee 

semantic interoperability across IATA standards.

The DDSCC receives and reviews requests for modifications of the IATA data

dictionary and generates specifications such as XML schemas, EDIFACT messages 

or other syntax as necessary to meet the business requirements.

The DDSCC maintains best practices and methodology guidance for application 

specific working groups to document their data and data modeling needs. 

The Secretary is IATA Manager, Messaging Standards (zitkovam@iata.org)

Communications Standards Coordination Committee (CSCC)

Terms of Reference

The CSCC reports to the PADIS Board and is tasked to promote and oversee 

interoperability on the level of communications protocol and general implementation 

of data exchanges. 

The CSCC provides a service to business by documenting common components of 

communications standards (including data security) that can be used by industry 

applications. It is responsible for the maintenance of the IATA Systems and 

Communications Reference Volumes.

The CSCC maintains best practices and methodology guidance for application 

specific working groups to document their needs in the area of communications 

protocols and general implementation of data exchanges. 

The Secretary is IATA Manager, Messaging Standards (zitkovam@iata.org)
Attachment: H

Page: 1 of 1

Involuntary Rerouting Working Group (IRWG)

Terms of Reference

An Involuntary Rerouting Working Group (IRWG) is established with the following 

Terms of Reference:

1. Perform a complete review of current IATA and A4A industry standards 

related to involuntary rerouting.

2. Identify outdated and/or conflicting processes, within the IATA and A4A 

standards and perform a comparison between them.

3. Identify the main differences to determine best practices from both resolutions

4. Liaise with other industry groups with potential impact for gaining intellect 

including (but not limited to) revenue accounting, tariffs, reservations, airports.

5. Develop a common approach for re-ticketing in the case of planned schedule 

changes.

6. Prepare agenda item(s) as necessary to promote quick and efficient 

involuntary rerouting processes both unplanned (i.e. Irregular operations) 

scenarios and planned schedule changes .

7. Report findings and/or proposals to the Ticketing Working Group (TKTWG).

PARTICIPANTS

Volunteers from the TKTWG, RESWG and RAWG who have indicated their 

participation.

REPORTING STRUCTURE/MANDATE RESTRICTION

The working group will have a mandate for 1 year. All activity of the working group 

will be fully communicated to TKTWG and TKTcom for discussion. A report will be 

submitted to the JPSC with recommendations and proposals. 
Attachment: I

Page: 1 of 1

Airport Services Committee (ASC) Membership 2013

Airline Traffic Conference Area Term of Office Expires 

Air Canada 1 2015

Alitalia 2 2015

American Airlines 1 2014

British Airways 2 2015

Delta Air Lines 1 2014

Egyptair 2 2013

El Al 2 2013

Iberia 2 2014

Japan Airlines 3 2013

KLM 2 2015

South African Airways 2 2014

United Airlines 1 2015

US Airways 1 2015

vacant

vacant

vacant

vacant

Vacant
Attachment: J

Page: 1 of 1

Ticketing Committee (TKTcom) Membership

Airline

Traffic 

Conference 

Area

Year Term of Office Expires 

at Conclusion of Passenger 

Services Conference:

Air Canada 1 2014

Air France 2 2014

All Nippon Airlines 3 2014

American Airlines 1 2014

British Airways 2 2013*

Cathay Pacific 3 2015

Delta Air Lines 1 2015

Egyptair 2 2013*

El Al 2 2014

Emirates 2 2013*

Finnair 2 2015

Japan Airlines 3 2015

KLM 2 2013*

Lufthansa 2 2013*

SAS 2 2015

South African Airways 2 2014

United Airlines 1 2014

US Airways 1 2013*

* Expires at the conclusion of PSC 2013
Attachment: K

Page: 1 of 1

Ticketing Committee (TKTcom)

Terms of Reference

As directed by the Passenger Services Conference (PSC), 

• To review and develop recommendations (in the form of draft or new 

Resolutions/Recommended Practices, etc.) to the PSC on manual, automated 

and electronic passenger traffic documents, and their related procedures;

• To undertake other specific assignments in the above category as directed by 

the PSC or its Chairman;

• To give direction and advice to assist in the maintenance of the Ticketing 

Handbook;

• To liaise and hold meetings with its counterpart industry committees on 

matters of mutual interest. The Committee may meet jointly with the 

equivalent A4A group as required.

Membership on the TKTcom shall be by IATA Member airline, not individual. A list of 

airlines interested in TKTcom membership shall be prepared at meetings of the 

TKTcom. Carriers not in attendance at such meetings may advise the Secretary of 

their interest prior to meetings. It is not necessary for an airline to be present at a 

TKTcom meeting to accept or decline a nomination. A list of all nominated carriers 

will be forwarded to the Passenger Services Conferences which shall select up to 18 

members for three year terms. One third of membership places will be open for 

election each year. In order to maintain some geographical distribution, Committee 

membership should consider representation from each Traffic Conference Area 

(TC1, TC2 and TC3).

The Secretary is IATA Manager, Airline Distribution Standards (mcewend@iata.org)
Attachment: L

Page: 1 of 1

Ticketing Working Group (TKTWG)

Terms of Reference

A Working Group is established by the Joint A4A/IATA Passenger Services 

Conference with the following terms of reference. The Working Group shall:

• consist of A4A/IATA member airlines, CRS suppliers and other interested 

members of the IATA Strategic Partners programme;

• make recommendations relating to the development of standards for current and 

future ticketing tools and procedures;

• review system activities between airlines, between airlines and suppliers 

including consideration of government regulations as they impact industry 

ticketing systems, communication standards and technical procedures;

• interface with other working groups that relate to passenger ticketing systems 

and procedures, such as the RESWG (Reservations Working Group) for 

reservations. DCSMWG for departure control and RAWG for revenue accounting;

• interface with other working groups that relate to other means of communications 

for passenger ticketing systems, such as the PADIS RES/APTS 

(reservations/airports) EDIFACT and XML working groups;

• report any conclusions and recommendations it develops through the A4A/IATA 

Ticketing Committee (TKTcom) to the Joint A4A/IATA Passenger Services 

Conference (JPSC).

The working group will have a one year mandate with an approved work plan. Ad 

hoc items may be added with the approval of the Ticketing Committee (TKTcom) or 

PSC Steering Group.

The Secretary will ensure that all activities of the working group are coordinated 

between A4A and IATA, and amongst related industry working groups.

The Secretary is IATA Manager, Airline Distribution Standards (mcewend@iata.org)
Attachment: M

Page: 1 of 4

TICKETING WORKING GROUP (TKTWG)

WORK PLAN

Topic Progress Next Steps Action By Target Date

1 Baggage (a/i JPTC Jun/12 10.4) IATA to prepare Secretary TKTcom 

Mar 13

2 Involuntary Rerouting RBD to be 

Used (a/i JPTC Jun/12 12.1)

WG Formed KL, DL, AF, BA, LH, 

AC,JL to align the verbiage of 735d 

and 766

Kick off call to be arranged All TKTcom 

Mar 13

3 Booking Space Discrepancy 

Between Resos and Actual 

Practice (a/i JPTC Jun/12 12.2)

WG Formed KL, DL, AF, BA, LH, 

AC JL to align the verbiage of 735d 

and 766

Kick off call to be arranged All TKTcom 

Mar 13

4 EMD Interline Lite Solution (a/i 

EMDTF/2 Jan/12 10/JPTC Jun12 

14.3)

WG formed under e-services to 

document processes. AY, EK, 1S, 

ATPCO, 1A

Conference Call arranged ruyt@iata.org EMDTF Jan 

13

5 Rebooked SSR and existing 

EMD to be linked (a/i JPTC 

Jun/12 14.5)

WG Formed 1P, 1A, AY Prepare a proposal TKTcom 

Mar 13

6 Exchange and Equivalent 

Exchange fields on EMD(A/I 

Jun/12 14.6 

No movement as yet AY TKTcom 

Mar 13

7 Service Fee Taxation (a/i 

EMDTF/2 Jan/12 5 JPTC 

June/12 14.7)

Members to discuss with ATPCO 

and ATPCO to provide status 

update

TKTcom 

Mar 13

8 Sub Codes Combine with PADIS 

Code Sets (a/i JPTC Jun/12 

14.10)

Conference Call to develop a 

proposal for March ATPCO, 

representatives from Revenue 

Accounting, PADIS, DISH, IATA, 

LH, Navitaire, 1P, 1A Unisys. AF 

and AY invited

TKTcom 

Mar 13
Attachment: M

Page: 2

Topic Progress Next Steps Action By Target Date

9 ATPCO 99X and 98X Fees and 

EMD Standalone (a/i EMDTF/2 

Jan/12 3 JPTC Jun/12 14.11)

WG LH, 1S, AY, LY, 1A, NH, 1P. Sabre to lead TKTcom 

Mar 13

10 Reason for Issuance Sub Code 

List (a/i JPTC Jun/12 14.13)

IATA to coordinate a call with 

ATPCO

Secretary TKTcom 

Mar 13

11 Monitoring Standards 

Requirements for EMD (a/i JPTC 

Jun/12 14.19)

IATA to coordinate Secretary TKTCOM 

Mar 

13/EMDTF 

Jan 13

12 Update Procedures for the 

Exchange/Reissue of Partially 

Flown Coupons (a/i JPTC Jun/12 

15)

Item to be added to involuntary 

rerouting items

TKTcom 

Mar 13

13 New Electronic Status Code for 

No –Show (a/i JPTC Jun/12 17)

Conference Call coordinated 

by ATPCO and volunteers 

DL, Navitaire, AA, 1P, AC, 

AY, 1S, RO, TA, 1A, EK, HR, 

LH ITA, LY

ATPCO to lead TKTcom 

Mar 13

14 Updating the ‘Applicable to’ 

Comments in the Glossary (a/i 

JPTC Jun/12 19)

1P agreed to review and submit a 

proposal 

Travelport TKTcom 

Mar 13

15 Include all Glossary Data 

Elements in each Message 

Construction Matrices (a/i Jun/12 

24

WG formed A4A, XB, AA, 1P Meeting arranged for 7-8 

November in ATL

Secretary TKTcom 

Mar 13
Attachment: M

Page: 3

Topic Progress Next Steps Action By Target Date

16 Add New Data Element Form of 

Payment Reporting Type (a/i 

Jun/12 26)

1A agreed to prepare a proposal Amadeus TKTcom 

Mar 13

17 Add History Display Message to 

EMD Airline Resolutions (a/i 

JPTC Jun/12 27)

AA to draft a proposal to 

remove History Display from 

722f/20.60. Travelport to draft 

a proposal to add History 

Display to 725f/20.63

AA : 1P TKTcom 

Mar 13

18 EMD Exchanges How to handle 

exchanges of single or multiple 

EMDs with multi currencies (a/i 

EMDTF/2 Feb/12 15 and 16)

WG formed HP, 1S, AY, BA, 1P, 

ITA, Expedia, 1A, LH, AF, IB, BA, 

NH, JL. All JPTC invited.

Conference Calls started kick 

off held 22 Sep

Secretary TKTcom 

Mar 13

19 EMD Exchanges How to manage 

the future usage of unused 

coupons currencies (a/i EMDTF/2 

Feb/12 17)

WG formed HP, 1S, AY, BA, 1P, 

ITA, Expedia, 1A, LH, AF, IB, BA, 

NH, JL. All JPTC invited.

Conference Calls started kick 

off held 22 Sep

Secretary TKTcom 

Mar 13

20 Further enhancements of 

Schedule Changes 

Recommended Practice

WG formed Initial RP submitted to JPSC Secretary TKTcom 

Mar 13

21 Involuntary Rerouting of 

Additional Services

No active discussion taken place Kick off calls as part of other 

involuntary rerouting 

discussions 

Secretary TKTcom 

Jun 13
Attachment: M

Page: 4

Topic Progress Next Steps Action By Target Date

22 Examination of all ticketing 

resolutions and removal of text to 

support sunset of all paper tickets 

eff 1 April 2016.

No active discussions To be commenced Secretary TKTCOM 

Mar 14

23 Review of all involuntary 

rerouting procedures

Identify outdated and/or 

conflicting processes, within the 

IATA and A4A standards and 

perform a comparison between 

them. Identify the main 

differences to determine best 

practices from both resolutions.

To be included in regular involuntary 

rerouting discussions

On-going Secretary TKTCOM 

Jun 13

24 Provide EMD examples and 

comments on latest version of the 

IATA Ticketing Handbook

None undertaken IATA to invite carriers and 

systems to submit examples. 

Survey to be undertaken

IATA December 

2012.
Attachment: N

Page: 1 of 2

PNRGOV Working Group (PNRGOV WG)

Terms of Reference

Purpose

Under an agreement between IATA and the World Customs Organization (WCO), 

maintenance of the PNRGOV message format and control over the authorization of 

modifications to that message structure has been assumed by the WCO itself.

The PNRGOV WG is established by and operates under the guidance of the PADIS 

Board. The PNRGOV WG’s primary role is to administer the PNRGOV message 

modification process, in accordance with the WCO’s approval process and based upon 

direction from the WCO API Contact Committee (WCO API CC).

Scope of Activity and Functions

The PNRGOV WG will:

• Develop and recommend modifications in the Implementation Guide, Principles 

Guide, and PNRGOV messaging standards as needed for the implementation of 

the PNRGOV message in the agreed message syntax (IATA EDIFACT and/or 

XML). 

• Review all recommended changes as proposed to or by the WCO API CC and 

submit applicable message changes through the DMR process to the WCO API 

CC as related to technical implementation and standards. This review would 

include a technical assessment conducted on behalf of the PADIS Board to 

ensure consistency and alignment with the IATA PADIS Message Standards 

Directory.

• Recommend PNRGOV message changes to the PADIS Board for approval

The scope of the PNRGOV WG does not include the authority to make or change policy 

as related to the PNRGOV message. Policy related decisions will be taken within the 

policy forum as established by the IATA Security and Facilitation Department.

The PNRGOV WG, in the spirit of collaborative industry efforts, will share lessons 

learned during implementation with a view of improving the PNRGOV message. It is 

not in the scope of the PNRGOV WG to discuss the terms of a specific bilateral 

agreement between two entities.
Attachment: N

Page: 2

Membership

Meetings of the PNRGOV WG are open to all A4A/IATA member airlines, IATA 

Strategic Partners, and government representatives who are interested in the 

standardized PNRGOV message. 

Delegates representing any member organization are expected to:

• Attend meetings on a regular basis

• Have the knowledge necessary to act as the subject matter experts and possess 

expertise relevant to documentation of business requirements and development 

of specifications

• Provide clear and concise input to the discussions and, where appropriate, 

ensure the relevant information is documented and shared in advance

Elections of Officers

The PNRGOV WG will elect a Chairman from an A4A/IATA airline member. The 

PNRGOV WG will elect a Vice-Chairman from a government or Strategic Partner 

company. 

The Chairman and the Vice-Chairman will both serve in these positions for a 2 (two) 

year term provided their organization is a member of the group for this same period and 

will be elected on alternating years to ensure continuity of the group and of the 

representatives elected. Officers are eligible for re-election after the conclusion of their 

term.

Meetings and Decision Making

PNRGOV WG meetings are to take place as necessary and as approved by the active 

group participants. The quorum required for any meeting is no less than 3 (three) 

A4A/IATA member airlines, 2 (two) Strategic Partners, and 2 (two) governments.

Multiple delegates from participating organizations are encouraged to attend as needed 

for technical expertise. However, a singular voice from each organization will be 

accepted towards the overall consensus of the group as needed to approve and/or 

progress agenda items and/or issues.. If consensus within the group cannot be 

reached, the PNRGOV WG Chairman will be responsible for determining the future 

action of such item and/or issue.

The Role of A4A/IATA

A4A/IATA will provide Secretariat services including all coordination with the Secretariat 

of any 3rd party organization that may be instrumental to the ongoing maintenance of 

the PNRGOV message.

Attachment: AA

Page: 1 of 1

IATA Reservations Committee Membership

Airline TC area Year Term of Office Expires

Air France (AF) 2 2013

Air Canada 1 2013

All Nippon Airways (NH) 3 2015

British Airways (BA) 2 2014

Delta Air Lines (DL) 1 2015

Egyptair (MS) 2 2014

El Al (LY) 2 2015

Emirates (EK) 2 2014

Etihad (EY) 2 2014

Finnair (AY) 2 2015

Iberia (IB) 2 2014

Japan Airlines (JL) 3 2015

KLM (KL) 2 2015

Lufthansa (LH) 2 2013

Scandinavian Airlines System (SK) 2 2015

South African Airways 2 2014

United Airlines (UA) 1 2015

US Airways (US) 1 2014
Attachment: BB

Page: 1 of 2

Topic Progress Next Steps Action by Target Date

1 Credit Card as FOID Amended; endorsed by ResCom Secretary JPSC

2 Self Service Flight 

Rebooking for Involuntary 

Rerouting

Reviewed Done

3 Moveable arm rest 

characteristic – Seat maps 

and requests

Endorsed by ResCom Check with PADIS regarding code X; 

code has been changed to P and it has 

been confirmed by PADIS this is available 

and it has been reserved

Secretary JPSC

4 Re-write 3.19 – advance 

boarding passes

Endorsed by ResCom Secretary JPSC

5 Additional description in 

Name Element (Extra Seat)

Agreed; ResCom agreed further 

review is necessary

Needs input from JPTC before 

proceeding; to be sent to June JPTC 

meeting and then to RESWG/19

Secretary RESWG/19

6 New 14 SSRs for each 

group of ATPCO ancillary 

services

Endorsed by ResCom Working Group formed to develop a 

proposal for ResCom; IATA/A4A/Chair to 

draft background paper for JPSC

Secretary JPSC

7 Reservations Services 

Manual

Version 1.0 to be published this 

summer. Additional updates to be 

included in version 2.0 for 

publication summer 2013.

Members to send comments to IATA 

(satoa@iata.org) ; still open

All ResCom

RESWG/19

8 New RP for Ancillary 

Services

Amadeus to prepare draft proposal prior 

to RESWG/19 for circulation and 

members to comment.

Amadeus 

and to be 

reviewed 

by all

RESWG/19

9 Linking the correct SSR 

ASVC to the correct 

standard SSR when the 

same SSR exists multiple 

times for the same 

passenger on the same flight

Travelport RESWG/19
Attachment: BB

Page: 2 of 2

Topic Progress Next Steps Action by Target Date

10 Agenda item 9 of 

ResCom/24 – example 6 

and 7 need to be further 

reviewed and also reviewed 

by JPTC prior to next 

RESWG – IATA/A4A to 

prepare an onsite for JPTC 

next week to get feedback or 

inclusion in the RESWG/19 

agenda

SITA to draft an onsite for JPTC and then 

draft an item for RESWG/19 agenda 

including JPTC comments

SITA JPTC/

RESWG/19

11 Cancelling SSR Elements by 

the member

AF/KL RESWG/19

12 Alphanumeric in SSR CLID On-site discussion at ResCom/24 LH to follow up and members to research LH RESWG/19

13 Management of portion filed 

ancillary services

AF/KL RESWG/19
Attachment: CC

Page: 1 of 5

AIRIMP & SIPP Resolution 105.175, section 3.5.14

2.6.14 Unaccompanied Minor

.....

Example:

SSR UMNR BA NN21 JFKFCO0110Y31AUG.UM08/09

.....

2.11.6.6 Construction Rules for Chargeable Special Service Requests

(Bilateral) (Editor’s note: renumber the current 2.11.6.6 and 2.11.6.7)

SSRs from the SSR matrix referring to this chapter have to follow these construction rules 

and are sent together with an SSR ASVC like any other standard SSR which represents a 

chargeable service.

The SSR Codes where the first two characters are PD, are always chargeable and should 

never be used as a stand-alone non chargeable SSR.

Components Number and 

Type of 

Characters

Mandatory/o

ptional

/Conditional

Examples

(a) Element Identifier 3 a M SSR

(b) SSR Service Code 4 a M PDML

(c) Airline designator (3 character 

codes are preceded with an 

oblique)

2 an or 3 a M BA

(d) Action Code 2 a M NN

(e) Number of services requested 1 – 3 n M 1

(f) Departure Airport 3 a M NCL

(g) Arrival Airport 3 a M LHR

(h) Flight number (with leading 

zeros)

4 n M 1321

(i) Reservation Booking 

Designator

1a M J

(j) Date 2 n 3 a M 30JUN

(k) If applicable, Name element, 

preceded by a hyphen Refer 

to name element paragraph 

2.11.6.1(k)

C -1BIGGIN/ANDREW

(l) Period M .

(m) Reason for Issuance Code 

(RFIC)

1 an M G

(n) Reason for Issuance sub 

code (RFISC) (1)

3–15 an M /0B3

(o) Commercial Name of service 

if available (1)

1–30 an C /CHINESE MEAL

(p) Free Text (1) 1-30 an O /NO MSG

(1) Components (n) – (p) must be preceded by an oblique (/). Where components are not available, an oblique is inserted to indicate 

that an element is missing. When no further components are provided, do not include obliques beyond the final component 

provided.
Attachment: CC

Page: 2 of 5

2.11.6.8 SSR MATRIX

(Editor’s note: the following SSR codes will be added to the current matrix, no separate matrix 

will be created)

SSR Code Action 

Code

Reply Automated 

Format

Free Text 

in Request

Free Text in 

Reply/Cancel

Reference

PDBG Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral) 

PDCO Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDFF Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDGT Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDIE Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDLG Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDML Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDPT Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDRO Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDSB Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDST Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDTS Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDUM Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

PDUG Mandatory Mandatory Mandatory Mandatory Mandatory 2.11.6.6

(Bilateral)

3.21.1.1 Rules of Usage

.....

(xi) If a request for a service is made using a Chargeable SSR (See 2.11.6.6) an SSR 

ASVC must be included in both the original request from the booking source as well 

as in the reply from the member.

.....
Attachment: CC

Page: 3 of 5

3.21.1.3 Examples

.....

Example 10 – Message from the booking source to the member requesting a chargeable 

meal using one of the standard predefined chargeable SSRs

MUCRM1A

.SWIRM1G

SWI1G ABCDEF/ABC/5725602/AMS/1G/NL/T

1RAUTIOMAKI/TIMOMR 1EDWARDS/PATTYMRS

AY0123Y10JUN HELMAD HK2 

SSRPDMLAYNN1 HELMAD0123Y10JUN-1RAUTIOMAKI/TIMOMR.A/ABC/PAELLA

SSRASVCAYNN1 HELMAD0123Y10JUN-1RAUTIOMAKI/TIMOMR.A/ABC/PDML/PAELLA

SSRPDMLAYNN1 HELMAD0123Y10JUN-1EDWARDS/PATTYMRS.A/ABB/LASAGNA

SSRASVCAYNN1 HELMAD0123Y10JUN-1EDWARDS/PATTYMRS.A/ABB/PDML/LASAGNA

Example 10(a) – Message from the Member to the booking source confirming the 

chargeable meal

SWIRM1G

.MUCRM1A

SWI1G ABCDEF

1RAUTIOMAKI/TIMOMR 1EDWARDS/PATTYMRS

AY0123Y10JUN HELMAD HK2 

SSRPDMLAYKK1 HELMAD0123Y10JUN-1RAUTIOMAKI/TIMOMR.A/ABC/PAELLA

SSRASVCAYKD1 HELMAD0123Y10JUN-1RAUTIOMAKI/TIMOMR.A/ABC/PDML/PAELLA

SSRPDMLAYKK1 HELMAD0123Y10JUN-1EDWARDS/PATTYMRS.A/ABB/LASAGNA

SSRASVCAYKD1 HELMAD0123Y10JUN-1EDWARDS/PATTYMRS.A/ABB/PDML/LASAGNA

Example 11 – Message from the booking source to the Member requesting a Child Meal; 

ASVC is also sent denoting agent is aware and EMD is required.

HDQRMAA

.HDQRM1P

HDQ1P ZYXZYX/AC8R/12345678/NYC/1P/T/US

1MORRIS/WAYNEMR 1MORRIS/EMMAMISS

AA0003Y10JUL JFKLAX HK2

AA0040Y20JUL LAXJFK HK2

SSRCHMLAANN1 JFKLAX0003Y10JUL-1MORRIS/EMMAMISS

SSRCHMLAANN1 LAXJFK0040Y20JUL-1MORRIS/EMMAMISS

SSRASVCAANN1 JFKLAX0003Y10JUL-1MORRIS/EMMAMISS.G/0HF/CHML/HAPPY MEAL

SSRASVCAANN1 LAXJFK0040Y20JUL-1MORRIS/EMMAMISS.G/0HF/CHML/HAPPY MEAL
Attachment: CC

Page: 4 of 5

Example 11(a) – Message from the Member to the booking source advising the service is 

not available. SSR CHML is followed by Free Text although Free Text is not allowed in Reply 

Messages according to the SSR Matrix in 2.11.6.8. An exception is applicable when the reply 

code of the SSR is NO. See 2.11.6.4.1

HDQRM1P

.HDQRMAA

HDQ1P ZYXZYX

1MORRIS/WAYNEMR 1MORRIS/EMMAMISS

AA0003Y10JUL JFKLAX HK2

AA0040Y20JUL LAXJFK HK2

SSRCHMLAANO1 JFKLAX0003Y10JUL-1MORRIS/EMMAMISS.SERV NOT AVAILABLE

SSRCHMLAANO1 LAXJFK0040Y20JUL-1MORRIS/EMMAMISS.SERV NOT AVAILABLE

SSRASVCAANO1 JFKLAX0003Y10JUL-1MORRIS/EMMAMISS.G/0HF/CHML/HAPPY MEAL

SSRASVCAA/// /SERV NOT AVAILABLE

SSRASVCAANO1 LAXJFK0040Y20JUL-1MORRIS/EMMAMISS.G/0HF/CHML/HAPPY MEAL

SSRASVCAA/// /SERV NOT AVAILABLE
Attachment: CC

Page: 5 of 5

AIRIMP & SIPP Resolution 105.170

7.1.8.2 Special Service Requirements (SSR) Code

Prepaid Baggage (Chargeable)............................................................................ PDBG

Carbon Offset (Chargeable) ................................................................................ PDCO

Frequent Flyer (Chargeable) ................................................................................ PDFF

Ground Transportation and Non Air Services (Chargeable) ..................................... PDGT

In-Flight Entertainment (Chargeable) ................................................................... PDIE

Lounge (Chargeable) ..........................................................................................PDLG

Meal/Beverage (Chargeable) .............................................................................. PDML

Rule Override (Chargeable) ................................................................................ PDRO

Pets (Chargeable) ..............................................................................................PDPT

Standby (Chargeable)........................................................................................ PDSB

Store (Chargeable).............................................................................................PDST

Travel Services (Chargeable) ...............................................................................PDTS

Unaccompanied Minor (Chargeable).....................................................................PDUM

Upgrades (Chargeable) ...................................................................................... PDUG

7.2 PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (Decoding)

PDBG............................................................................ Prepaid Baggage (Chargeable)

PDCO................................................................................ Carbon Offset (Chargeable)

PDFF.................................................................................Frequent Flyer (Chargeable)

PDGT...................................... Ground Transportation and Non Air Services (Chargeable)

PDIE.................................................................... In-Flight Entertainment (Chargeable)

PDLG ..........................................................................................Lounge (Chargeable)

PDML............................................................................... Meal/Beverage (Chargeable)

PDPT ..............................................................................................Pets (Chargeable)

PDRO.................................................................................Rule Override (Chargeable)

PDSB........................................................................................ Standby (Chargeable)

PDST ............................................................................................ Store (Chargeable)

PDTS .............................................................................. Travel Services (Chargeable)

PDUM .................................................................... Unaccompanied Minor (Chargeable)

PDUG.......................................................................................Upgrades (Chargeable)
Attachment: DD

Page: 1 of 1

AIRIMP and A4A Resolution 110.16. A.1.

Miscellaneous

G Conditional reservation

For individual airline use

U Shuttle service

No reservation needed.

Seat Guaranteed

For individual airline use

E Shuttle service – no reservation allowed –seat to be confirmed at Check-in

Passenger service – reservation permitted

For individual airline use

O For individual airline use

R For individual airline use

Secretary note: counterpart action may be required for SISC
Attachment: EE

Page: 1 of 1

AIRIMP and A4A SIPP Resolution 3.9.11.1

2.11.7.4 Contact Information in OSI

Whenever it is necessary to transmit contact information to another airline, use the following format and 

enter the components in the following sequence:

(a) Supplementary Item Identifier OSI;

(b) Action Identifier — airline designator;

(c) Contact CTC — follow the abbreviation CTC by the nature of contact, e.g.:

A — Address (home or hotel),

B — Business telephone,

E — E-mail,

Note:

Use // (double slash) in place of @ (at sign) and “..” (double dot) in place of “_” (underscore) in E-mail 

address.

F — Datafax, Fax,

H — Home telephone,

M — Mobile phone,

T — Travel Agent telephone,

P — Passenger telephone, type may be specified Telephone nature not known

Note:

“X” may be used to separate the telephone number from an extension or room number.

(d) Boarding Point Location Code— three-letter city/airport code of the boarding point for which the 

contact is intended;

(e) Contact Information — other than addresses and telephone numbers, is expressed in plain language.

Example 1:

OSI YY CTCH DAL 214 720 3321

.........

Example 5:

OSI SK CTCP CPH BY 8890

OSI BW CTCP TAB 1 868 639 5678 PRIMARY

OSI KX CTCP GCM 1 480 639 3000 SECONDARY
Attachment: FF

Page: 1 of 1

AIRIMP and SIPP Resolution 105.175 – new Section 11

3.10.1 General Format for Form of ID

Follow standard SSR element construction rules, using the code SSR, four-character 

code FOID, airline designator (“YY” not allowed), Status Code “HK” followed by the 

number of passengers to which the SSR applies and a slash, two-character code for 

type of ID, followed optionally by two-character ISO country code or state code and up 

to 25 alphanumeric document number and dash followed by passenger identification. 

When the type of ID is “FF”, the airline designator of the carrier shall be included in the 

Frequent Traveler Identification Number and if the type of ID is “CC”, the two letter code 

of the credit card vendor shall be included in the Credit Card identification number.

To comply with PCI DSS specifications, whenever a credit card is used as an FOID, it 

must be truncated. Truncated means only the first 6 and last 4 digits may be transmitted 

in clear text and each of the remaining numbers is replaced by an ‘X’. 

.....

3.10.3 Examples:

.....

(d) Notification that a truncated Diners Club Credit Card number will be used as Form of Identification for Passenger 

Check-in Identification. 

SSR FOID SK HK1/ CC DC 36141212123434-1SUNDSFJORD/YNGVAR

MUCRM1A

.SWIRM1G

SWI1G QWERTY/ABC/57256802/STO/1G/T/SE

1SUNDSFJORD/YNGVAR

SK0909Y10JUN CPHEWR HK1

SK0910Y20JUN EWRCPH HK1

SSR FOID SK HK1/ CC DC

361412XXXX3434-1SUNDSFJORD/YNGVAR

(e) Notification that a truncated Credit Card number will be used as a form of identification at check-in for two 

passengers travelling together.

SSR FOID QF HK2/CCVI4929123456789-1ALLEYNE/JENNIFER MISS 1PERKINS/JOANNA MRS

MUCRM1A

.SWIRM1G

SWI1G QWERTY/ABC/57256802/STO/1G/T/SE

1ALLEYNE/JENNIFER MISS 1PERKINS/JOANNA MRS

SK0909Y10JUN CPHEWR HK2

SK0910Y20JUN EWRCPH HK2

SSR FOID SK HK2/CCVI492912XXXXXX6789
Attachment: GG

Page: 1 of 1

AIRIMP and SIPP Resolution 105.175 section 3.9.5.11 and 105.15, section 2.5.2

3.19.2.5 Location codes

Location codes are optional and follow the zone code. They may be one or two characters 

in the following sequence:

W - Window Seat

A – Aisle Seat

B – Bulkhead Seat

C – Chargeable Seat (bilateral agreement)

E – Exit Row Seat

F – Non Chargeable Seat (bilateral agreement)

H(1) – Handicapped Seat

I – Passenger with Infant

L- Leg Space Seat (bilateral)

M(1) – Medically Okay to Travel

R – Rear facing Seat (bilateral agreement)

U – Unaccompanied Minor

P - Extra seat for comfort - Arm rest can be raised
Attachment: HH

Page: 1 of 1

AIRIMP and SIPP Resolution 105.175, section 17.2

3.21.2 Additional Services – Non-Segment Associated Services

3.21.2.1 Examples

.....

Example 5 – Message from booking source to Member advising the EMD has been issued for a 

rebooking fee for which no previous request was sent

HDQRMDL

.MUCRM1A 231051

MUC1A 2GLYIP/NCL7X2063/96129250/NCL/1A/N/GB//GS

2WILKINSON/BRUNOMR/CAROLINEMRS

DL1234Y18NOV LHRATL HK2

DL4321Y22NOV ATLLHR HK2

SVC DL HS1 LHR 18NOV/D/993/REBOOKING FEE/NM-1WILKINSON/BRUNOMR

/0061234567890C1.CHANGE FEE GBP25

SVC DL HS1 LHR 18NOV/D/993/REBOOKING FEE/NM-1WILKINSON/CAROLINEMRS

/0061234567891C1.CHANGE FEE GBP25
Attachment: II

Page: 1 of 2

AIRIMP and SIPP Resolution 105.175, Section 17.1

3.21.1 Segment-Associated Additional Services

[...]

3.21.1.1 Rules of Usage

(i) Unless otherwise specified standard SSR rules apply.

(ii) An SSR ASVC is typically used in conjunction with a standard SSR element which requests the 

service. If no standard SSR code (refer to 2.11.6.6) exists for the type of service being requested, an SSR 

ASVC is used to request the service.

(iii) If an SSR code exists for the requested service and an EMD is required, the message includes both 

the existing SSR and an SSR ASVC. The SSR ASVC may be included in the original request or as part of 

the reply from the Member.

(iv) Each SSR ASVC element must be associated to a single passenger.

(v) If a request for the service includes more than one passenger name and if the response contains SSR 

ASVC elements, there must be a separate SSR ASVC for each passenger.

(vi) One SSR ASVC may be used to request multiple services of the same type on the same flight 

segment for a single passenger.

(vii) SSR ASVC must be segment related. When SSR ASVC is linked to a seat element on change of 

gauge flight, flight leg data must be specified instead of flight segment data 

(viii) When including the EMD number, include the appropriate coupon number.

(ix) When an SSR is cancelled, any related SSRs pertaining to that same service must also be cancelled 

and included in the message.

(x) When sending messages, use one of the action/reply/advice/status codes as listed in 3.21.1.2:

3.21.1.4 Examples of Request and Reply Messages for Pre-reserved seats in SSR

SEAT elements in conjunction with SSR ASVC elements

[...]

Example 7 — Change of gauge

Example 7(a) — Message from booking source to Member requesting a non-smoking window seat

assignment; no ASVC is sent.

MADRMIB

.MUCRM1A 210944

MUC1A 3SX9ZU/MUC1A0701/12345675/MUC/1A/A/DE//PR

1SURMONT/AC

IB6123Y20DEC BCNMIA HK1

SSR NSST IB NN1 BCNMIA 6123Y20DEC-1SURMONT/AC.NW
Attachment: II

Page: 2 of 2

Example 7(b) — Message from Member to booking source confirming the seat assignment on BCNMAD 

and MADMIA legs; ASVC is sent with KD on MADMIA leg as EMD-A is required on this leg.

MUCRM1A

.MADRMIB 210945

MUC1A 3SX9ZU

1SURMONT/AC

IB6123Y20DEC BCNMIA HK1

SSR NSST IB KK1 BCNMAD 6123Y20DEC-1SURMONT/AC.26F

SSR NSST IB KK1 MADMIA 6123Y20DEC-1SURMONT/AC.15A

SSR ASVC IB KD1 MADMIA 6123Y20DEC-1SURMONT/AC.A/0B5/NSST/

SSR ASVC IB ///CHARGEABLE SEAT

Example 7(c) — Message from booking source to Member advising the EMD-A has been

Issued for seat on leg MADMIA.

MADRMIB

.MUCRM1A 220944

MUC1A 3SX9ZU/MUC1A0701/12345675/MUC/1A/A/DE//PR

1SURMONT/AC

IB6123Y20DEC BCNMIA HK1

SSR ASVC IB HS1 MADMIA 6123Y20DEC-1SURMONT/AC.A/0B5/NSST/

SSR ASVC IB ///CHARGEABLE SEAT/A/0750241234567C1
Attachment: JJ

Page: 1 of 12

AIRIMP and SIPP Resolution 105.115, section 2

3.19 PRE-RESERVED SEAT SELECTION AND BOARDING PASS NOTIFICATION

3.19.1 Scope

The rules in this paragraph for requesting, changing or cancelling pre-reserved seats and advising when 

a boarding pass has been issued are applicable between Members and between Members and CRSs on 

a bilateral basis.

3.19.2 Definitions

Pre-reserved seat selection and boarding pass notification details will be transmitted in the 

Supplementary Element of the teletype message as an SSR SEAT element, when requesting, cancelling 

or changing seat selection and/or advising a Member that a boarding pass has been issued.

3.19.2.1 The maximum number of seats and/or segments will be as bilaterally agreed.

3.19.2.2 Requests for pre-reserved seats may be made in advance of boarding pass issuance allowances 

as bilaterally agreed.

3.19.2.32 Message Identifier

SEAT element, when requesting, cancelling or changing seat selection. and/or advising a Member that a 

boarding pass has been issued.

3.19.2.43 Zone Codes

The following mandatory codes specify a section within an aircraft compartment:

N — Non-smoking Seat;

S — Smoking Seat.

3.19.2.54 Location Codes

Location Codes are optional and follow the zone code. They may be one or two characters in the 

following sequence:

W — Window Seat

A — Aisle Seat

B — Bulkhead Seat

C — Chargeable Seat (bilateral agreement)

E — Exit Row Seat

F — Non Chargeable Seat (bilateral agreement)

H (1) — Handicapped Seat

I — Passenger With Infant

L — Leg Space Seat (bilateral)

M (1) — Medically Okay to Travel

R — Rear-Facing Seat (bilateral agreement)

U — Unaccompanied Minor

(1) Requires a separate Supplementary Element defining the medical or handicapped status of passenger.
Attachment: JJ

Page: 2 of 12

3.19.2.65 Specific Seat Numbers

When specific seats are included in the message, the seat numbers must be contiguously entered with no 

separators. All seat numbers must include two to four characters (one to three numerics followed by one 

alpha).

3.19.2.76 The Message Identifier BPR is used for messages that include SSR SEAT.

3.19.3 General Construction Rules

3.19.3.1 A separate Supplementary Item must be entered for each flight segment in the itinerary where 

the passenger desires a pre-reserved seat.

3.19.3.2 If the Supplementary Item exceeds 69 characters, each new line of data must commence with 

the mandatory “SSR SEAT” elements and may not exceed 69 characters.

3.19.3.3 In the construction of the SSR SEAT message, when the Supplementary Item exceeds 69 

characters, the following lines (not to exceed 99) must start with the mandatory SSR SEAT, two-character 

designator of the airline to take action, followed by three obliques, followed by the additional or remaining 

text of the message. Words or names must not be split between SSR SEAT items.

Examples:

SSR SEAT US NN5PITLAX0234Y23MAY-4WILLIAMS/MAUREENMRS/CHRISTOPHER/

SSR SEAT US ///BELINDAMS/KEITH1THOMPSON/BMS.16D16E16F17D17F

SSR SEAT US NN5LAXPIT0123Y28MAY-4WILLIAMS/MAUREENMRS/CHRISTOPHER/

SSR SEAT US ///BELINDAMS/KEITH1THOMPSON/BMS.23A23B23C24A24C

3.19.3.4 Free text information will contain the passenger(s) desired seating preference by generic zone, 

location code or specific seat number. The passenger's seating preference must be preceded by a period 

(.).

Example — no smoking window, unaccompanied child:

SSR SEAT UA NN1DENORD0193F15APR.NWU

3.19.3.5 SEAT requests may be for all names or some of the names within the name message.

Seats will be reserved in the order the names appear in the name element. If seats in different zones are 

required for a party of two or more within the same name message, two or more SSR SEAT items must 

be created and names are mandatory.

Examples:

SSR SEAT UA NN2SINLAX0193Y15APR-2BAKER/FANNYMS/GRETCHENMS.S

SSR SEAT UA NN2SINLAX0193Y15APR-2BAKER/FRANK/SAM.N

3.19.3.6 As bilaterally agreed, seat requests may be for less than the total number in party.

When some but not all names are requesting seats, name(s) are mandatory in the SSR SEAT item.

Example of seat request for some but not all passengers:

HDQRMDL

.HDQRM1P 022202

BPR

HDQ1P YC42YA/0578105

1SMITH/HENRY 1JONES/JENNY 1HARRIS/JIMMSTR

DL123B19AUG ATLMSY HK3

SSRSEATDLNN2ATLMSY0123B19AUG-1JONES/JENNY1HARRIS/JIMMSTR.23A23B
Attachment: JJ

Page: 3 of 12

3.19.3.7 The data following the period will be the SEAT and Zone data. The information following the 

slash will be the Transaction Identifier or explanatory note. When no SEAT/Zone data exists, the period 

(.) will be followed by an oblique (/).

3.19.4 Construction and Sequence of Components

3.19.4.1 Use the following instructions when composing a Supplementary Item for pre-reserved seat 

selection/boarding pass issue authority:

(a) Supplementary Item Identifier SSR;

(b) Special Service Requirement Code SEAT;

(c) Action Identifier — enter the airline designator of the airline to take action. The same carrier code is 

sent in the reply;

(d) Action Code and Number of Seats — use the appropriate action code (NN/IN/XX/

IX/HX/KK/LK/ UC/UN/NO/HS/OX) followed by the number of seats.

Note:

“IX” and “LK” as bilaterally agreed.

(e) Segment — enter the segment using the boarding point (three-letter airport code), deplaning point 

(three-letter airport code), flight number (4 numerics), class of service, which must be the same as shown 

in the Segment Element (1 alpha), local boarding date (2 numerics, 3 alpha);

(f) when the SEAT request is for some, but not all, of the names in the name element, the name(s) is 

mandatory. The name(s) must be identical to that in the name element of the teletype message. Name(s), 

when present, must be preceded by a hyphen (-) followed by the numeric number in the family name;

(g) Seating Requirements/Comments — free text information shall be preceded by a period (.).

Only passenger seating requirements/comments specified in this chapter may be used in free text:

(i) generic requests must include a zone and may be followed by one or two up to 4 Location Codes. 

Specific seat requests may be included and will not have a Zone Code appended,

(ii) when more than one seat number is included in the entry, the seat numbers will be included with no 

separation,

(iii) when unable to confirm a pre-reserved seat request, following the seating request, include the reason 

preceded by an oblique (may not be used in conjunction with a Transaction Identifier);

(h) when applicable, enter a unique two alpha Transaction Identifier following the seating request, 

preceded by an oblique:

RB — a reserved seat response; boarding pass is inhibited until bilaterally agreed time frame;

RG — boarding pass authority response for change of gauge segment(s);

RS — reserve seat request/response; boarding pass inhibited. If RS is in the request it must be included 

in the response;

RC — a seat has been reserved, boarding pass issuance is inhibited on a change of gauge flight;

RZ — a seat has been reserved on a change of gauge flight. Boarding Pass issuance is inhibited until 

bilaterally agreed time limit.
Attachment: JJ

Page: 4 of 12

3.19.5 Pre-reserved Seat Request

3.19.5.1 Seats will be reserved in the same order as the names appear in the Name Element of the 

message unless individual name(s) have specific seat needs, as shown in name associated SSR SEAT 

requests.

3.19.5.2 Use the Action Code “NN”.

3.19.5.3 Pre-reserved SEAT requests on change of gauge flights may be shown as a single SSR SEAT 

or as multiple SSR SEAT elements depending on the requester's knowledge of the flight routing and 

aircraft used.

3.19.5.4 Examples of Requests for a Pre-reserved Seat

Example 1 — Smoking seat/Window (pre-reserved seat only):

SSR SEAT CO NN3MCIDEN0719Y15NOV.SW

Example 2 — No smoking seat (boarding pass desired):

SSR SEAT CO NN3MCIDEN0719Y15NOV.N

Example 3 — Specific seat request (boarding pass desired):

SSR SEAT CO NN3MCIDEN0719Y15NOV.23A23B23C

Example 4 — No smoking seat, aisle with infant Non smoking aisle seat, suitable for lap infant:

SSR SEAT CO NN3MCIDEN0719Y15NOV.NAI 

Example 5 — Multiple change of gauge flight request:

Segment is UA0845Y05NOV LAXNRT HK1

SSR SEAT UA NN1 LAXSFO 0845Y05NOV.N

SSR SEAT UA NN1 SFONRT 0845Y05NOV.S

Example 6 — (By bilateral agreement) A request for one pre-reserved rear-facing seat on BA flight 0011, 

F class, on February 4, at aisle in the non-smoking section:

SSR SEAT BA NN1 LHRSYFD0011F04FEB-1DRAKE/STEVE.NAR or (assuming that PNR 

contains only one name):

SSRSEAT BA NN1 LHRSYFD0011F04FEB.NAR

Example 7 — (By bilateral agreement) A request for pre-reserved rear-facing seats on BA flight 4505, J 

class, on July 6, for all three passengers of a PNR party, in the non-smoking section:

SSR SEAT BA NN3 LGWNAS4505J06JUL.NR

Example 8 – (By bilateral agreement) A request for a chargeable pre-reserved window seat in the exit row 

with extra leg space on LH flight 723, D class, on 10th June in the nonsmoking section of the aircraft:

SSR SEAT LH NN1 PEKMUC0723D10JUN-1DIVABRYANT/MICHELLE MS.NCWEL

3.19.6 Pre-reserved Seat Change

3.19.6.1 If the passenger wishes to change a pre-reserved seat, two separate items must be entered. 

Enter a Supplementary Item to cancel seats, followed by the new seat request.

3.19.6.2 The cancelled item must include the seat number(s).

3.19.6.3 Use the Action Code “XX” or “OX” to cancel the seats.
Attachment: JJ

Page: 5 of 12

3.19.6.4 Examples of a Change of a Pre-reserved Seat

Example 1:

The transmission of an item with the “XX” Action Code will apply only when the pre-reserved seat(s) 

shows as confirmed in the requesting Member's system. The “XX” or “IX” item indicates the seat was 

cancelled in the requesting system and is to be cancelled in the receiving system regardless of whether 

the “NN” seat is available or not the status of the SSR in the receiving system.

SSR SEAT CO XX2 MCIDEN 0719Y15NOV.12A12B

SSR SEAT CO NN2 MCIDEN 0719Y15NOV.23A23B

Example 2:

The transmission of a seat item with the “OX” Action Code will apply when the pre-reserved seat shows 

confirmed in the requesting Member's system. The “OX” seat item is not to be cancelled in the receiving 

system unless the alternate “NN” seat can be confirmed.

SSR SEAT CO OX1 MCIDEN 0123Y15NOV.23A

SSR SEAT CO NN1 MCIDEN 0123Y15NOV.08A

3.19.7 Pre-reserved Seats and PNR Change

3.19.7.1 Cancel/No Rebooking

When the message contains cancelled flight segment(s), with no rebooking, the receiving Member will 

assume all associated seat(s) are to be cancelled. No Supplementary Item will be required to cancel the 

seats.

3.19.7.2 Cancel/Rebook Different Flight Segment(s)

(a) When the message contains cancelled flight segment(s), with a booking for different flight segment(s), 

the receiving Member will assume all associated seats are to be cancelled for the cancelled flight 

segment(s). No Supplementary Item will be required to cancel the seats.

(b) If the passenger is rebooking a new flight segment(s), enter a separate Supplementary Item for each 

new flight segment. Use the Action Code “NN”.

3.19.7.3 Cancel/Rebook Same Flight Segments(s)

Note:

Determination of the RBDs within a compartment will be as bilaterally agreed.

(a) Different RBD/Same Compartment

When the message contains a cancelled flight segment and a rebooking of the same flight, date, city pair, 

in the same compartment, different RBD, all associated seats will be retained. A Supplementary Item 

confirming the retained seats with Advice Code “KK” is not required.

Itinerary/Seats:

DL1019Y20OCTPBIATLHK1

SSR SEAT DLHK1PBIATL1019Y20OCT.23AN

Message:

HDQRMDL

.HDQRM1P 22145

HDQ1P B98Y12

1REYNOLDS/BRUCE

DL1019Y20OCTPBIATLXX1

DL1019B20OCTPBIATLSS1/1240 1430

The original seat assignment is to be retained.

(b) If a seat is to be cancelled subject to the confirmation of a different seat, use the Action/Advice
Attachment: JJ

Page: 6 of 12

Code “OX” (cancel only if the requested seat is available) for the existing seat followed by the 

Action/Advice Code “NN” for the new seat request.

Itinerary/Seats:

DL1019Y20OCTPBIATLHK1

SSR SEAT DLHK1PBIATL1019Y20OCT.23AN

Message:

HDQRMDL

.HDQRM1P 221455

HDQ1P B98Y12

1REYNOLDS/BRUCE

DL1019Y20OCTPBIATLXX1

DL1019B20OCTPBIATLSS1/1240 1430

SSR SEAT DLOX1PBIATL1019Y20OCT.23AN

SSR SEAT DLNN1PBIATL1019B20OCT.23CN

(c) Different Compartment

When the message contains a cancelled flight segment and a rebooking of the same flight,

date, city pair, in a different compartment, associated seats will not be retained.

If seats are to be reserved in the new compartment, a new Supplementary Item will be

required. Use the Action Code “NN”.

3.19.7.4 Confirming from Waitlist

Note:

Determination of the RBDs within a compartment will be as bilaterally agreed.

When the passenger is confirmed in one RBD and is subsequently confirmed from the waitlist in a 

different RBD in the same compartment (compartment as bilaterally agreed) for the same flight, date, city 

pair, all associated seats will be retained when the original flight segment is cancelled. Since space to be 

cancelled is only part of a Member's complete space, include a reference to all of the Member's space 

and identify action desired on each segment.

Itinerary/Seats:

DL 245B19OCTATLPBIHK1 355P 523P

UA 458Y20OCTPBIATLHK1 415P 554P

UA 458B20OCTPBIATLKL1 415P 554P

SSR SEAT UAHK1PBIATL0458Y20OCT.23AN

Message:

HDQRMUA

.HDQRMDL

HDQDL 23R56Y

1JONES/BILLY

UA458Y20OCTPBIATLXX1

UA458B20OCTPBIATLHK1

Note:

Upon receipt of the cancel message, UA will retain the originally reserved seat.
Attachment: JJ

Page: 7 of 12

3.19.7.5 Reduce Number in Party

(a) When the message contains cancelled flight segments reducing the number in party, the seats 

associated with the cancelled name(s) will be automatically cancelled.

(b) If the remaining number in party wish to reserve the cancelled seat(s), a separate SSR item must be 

transmitted. Use the rules in 2.11.6 for changing a preserved seat.

3.19.7.6 Divide Party

When the PNR is divided due to an itinerary modification for one or more passengers, change in an 

existing reservation is to change the itinerary of one or more passengers differently from the remainder of 

an existing party, process the seat selection transaction as follows:

(a) seats associated with the Name Element will be divided along with the itinerary for the party making 

the change;

(b) cancelled flight segments will automatically cancel associated segments supplementary items;

(c) enter a Supplementary Item to request seats for the new flight segments

(d) if the remaining number in party wish to reserve the cancelled seat(s), a separate SSR item must be 

transmitted. Use the rules in 2.11.6 “Construction and Sequence of Components” for changing a prereserved seat.

3.19.7.7 Name Change

When there is a change in passenger name(s) or name correction, any SSR SEAT(s) associated with the 

name(s) will be retained. If the existing SSR SEAT item(s) are not to be retained for the new passenger, 

they must be cancelled. A new SSR SEAT(s) must be requested, if desired. Use the rules in 2.12.6 for 

changing a pre-reserved seat.

3.19.8 Reply Messages

3.19.8.1 Enter a Separate SSR SEAT element in the reply for each SSR SEAT element received in the 

request.

3.19.8.2 In cases where pre-reserved seats are confirmed in alphabetical order by the receiving Member, 

the reply message must show the seats in the same order as the names appear in the Name Element of 

the message.

3.19.8.3 Use the appropriate Action Code “KK/UC/UN/NO” to advise the booking Member/CRS the seats 

are confirmed or unable.

3.19.8.4 When seats are confirmed, the Zone Code must follow each seat number.

3.19.8.5 When the receiving Member is unable to confirm a seat for one or more flight segments, include 

the reason in the reply message. The Advice Code transmitted may be self-explanatory, e.g. UN or UC, 

or may require an explanation by definition, e.g. NO. In free text, explanatory notes must follow the actual 

seat numbers or zone/location request, preceded by an oblique. 

Examples of possible explanatory notes:

Unable to confirm seat request, confirmed

alternate follows: .................................................... /CONFIRMED ALTERNATE SEAT

Unable to confirm, in airport control ......................... /AIRPORT CHECKIN

Seat selection not offered on that flight ................... /PRE-RESERVED SEATING NOT AVAILABLE

Smoking zone unable, only NS available ................ /NON-SMOKING AVAILABLE

Non-smoking zone unable, only S available............ /SMOKING AVAILABLE

Schedule change ..................................................... /SCHEDULE CHANGE

No smoking flight...................................................... /NO SMOKING FLIGHT

The reply may contain a new SSR SEAT item to indicate alternate seat confirmation.
Attachment: JJ

Page: 8 of 12

3.19.8.6 Examples of Reply Items

Example 1 — Boarding pass OK Smoking

SSR SEAT CO KK2 MCIDEN 0719Y15NOV.23AS23BS

Example 21 — Reserved seat (Boarding pass inhibited):

SSR SEAT CO KK2 MCIDEN 0719Y15NOV.23AN23BN/RS

Example 32 — Unable to assign seat:

SSR SEAT CO UC2 MCIDEN 0719Y15NOV.23AN23BN/ARPT ONLY

Example 43 — Unable to confirm original request, alternate confirmed seats (Boarding pass inhibited):

SSR SEAT UA NO2 ORDLAX 0100Y23AUG.NW/ALT SEAT

SSR SEAT UA KK2 ORDLAX 0100Y23AUG.17DN17EN/RS

Example 54 — Unable to confirm the “NN” item when accompanied by an “OX” item. The originally held 

seat is retained (Boarding pass inhibited):

SSR SEAT CO UC1 MCIDEN 0123Y15NOV 08A/SEAT NOT AVAILABLE

SSR SEAT CO KK1 MCIDEN 0123Y15NOV 23AN/RS

Example 65 — Cancel/re-book, different Reservation Booking Designator/same compartment, new seat 

request. Able to confirm the “NN” item. The “OX” item is cancelled in the receiving system and assumed 

will be cancelled in the requesting Member's system upon receipt of the “KK” for the new seat (Boarding 

pass inhibited):

SSR SEAT DL KK1 PBIATL 1019B20OCT.23CN/RS

Example 76 — (By bilateral agreement) A confirmation for one pre-reserved rear-facing seat (3A) on BA 

flight 0011, F class, on February 4, at aisle in the non-smoking section (Boarding pass inhibited):

SSR SEAT BA KK1 LHRSYD0011F04FEB-1DRAKE/STEVE.3AN/RS or (assuming that PNR 

contains only one name)

SSR SEAT BA KK1 LHRSYD0011F04FEB. 3AN/RS

Example 87 — (By bilateral agreement) A confirmation for pre-reserved rear-facing seats on BA flight 

4505, J class, on July 6, for all three Members of a PNR party, in the non-smoking section (Boarding pass 

inhibited):

SSR SEAT BA KK3 LGWNAS4505J06JUL.07CN07DN07EN/RS

Example 8 – (By bilateral agreement) A confirmation for a chargeable pre-reserved window seat in the 

exit row with extra leg space on LH flight 723, D class, on June 10 in the non-smoking section of the 

aircraft:

SSR SEAT LH KK1 PEKMUC0723D10JUN-1DIVABRYANT/MICHELLE MS.03HNCWEL/RS

3.19.9 Boarding Pass Issuance

3.19.9.1 A boarding pass must not be issued if the seat has not been confirmed to a specific passenger 

named in the message and SEAT replies must always include the Transaction Identifier (RS or RC as 

applicable).

3.19.9.2 If the Transaction Identifier RS and/or RC has been transmitted with the seat confirmation, the 

Member/CRS Supplier in control is responsible for inhibiting boarding pass issuance for the specified 

flight. If the Transaction Identifier RB or RZ is received the controlling Member/CRS is responsible for 

disallowing boarding pass issuance until the mutually agreed time/date for boarding pass issuance.

3.19.9.3 Notification for boarding pass issuance is optionally agreed. When notification is required, the 

following will apply:

(a) use the Advice Code “HS” to advise the applicable Member that a boarding pass has been

issued;

(b) a separate SSR item must be entered for each flight segment;
Attachment: JJ

Page: 9 of 12

(c) boarding pass issuance may be for less than the total number in party. However all names in the PNR 

name element must be specified even though the SSR Seat Item is for less than total number in party. 

When the number of boarding passes being issued is less than the total number in party, the names for 

whom the boarding passes were issued must be included in

the SSR SEAT item;

(d) example of Boarding Pass issued:

HDQRMDL

.HDQRM1P 022202

BPR

HDQ1P YC42DA/0578105

1SMITH/HENRYMR 1JONES/JENNYMRS 1HARRIS/JIMMSTR

DL123B19AUG ATLMSY HK3

SSR SEAT DL HS1ATLMSY0123B19AUG-1SMITH/HENRYMR.09A

3.19.10 Schedule Change

3.19.10.1 Time Change Only

If the message involves a time change and the flight segment is HK, all pre-reserved seats will be 

protected.

3.19.10.2 Equipment Change Only

If an equipment change occurs on the day of departure, the Member will not notify of the change to the 

pre-reserved seat(s). Notification when equipment changes occur prior to the day of departure will be as 

bilaterally agreed.

Example of Equipment Change Only Message:

SSR SEAT UA NO2MCIDEN0719Y15NOV.23A23B/SKED CHG

SSR SEAT UA KK2MCIDEN0719Y15NOV.16DN16BN/RS

or

SSR SEAT UA UN2MCIDEN0719Y 15NOV.23A23B

SSR SEAT UA KK2MCIDEN0719Y 15NOV.16AN16BN/RS

3.19.10.3 Cancelled Flight Segments

(a) If the message to another Member/CRS involves a flight cancellation with an Advice Code “UN”, not 

re-accommodated to a new flight segment, all pre-reserved seats associated with the NOOP segment will 

be cancelled by the receiver.

(b) The Member receiving the Status Advice Code “UN” must send a new pre-reserved seat request, 

unless the sender has confirmed an alternate seat.

Example of a Schedule Change Item:

HDQRMAA

.ATLRMDL 031519

Message Identifier .................. ASC

Record Locator....................... HDQAA AB76AB/12345678

Name Element........................ 1JONES/JMR

Segment Element (NOOP)..... DL719Y15NOV LAXSEA UN1

Segment Element (alternate

confirmation)......................... DL743Y15NOV LAXSEA TK1/1500 1710

Supplementary Element

(confirming pre-reserved

seat) ..................................... SSR SEAT DL KK1LAXSEA0743Y15NOV.20AN/RS

(c) When the cancelled flight is re-accommodated, the Member making the change must also send an 

advice when the SSR SEAT(s) is re-accommodated (as bilaterally agreed). This SEAT advisory may be 

included in the ASC or in a subsequent BPR message. When constructing the SSR item, use the airline 

designator of the carrier to which the flight/date/service applies.
Attachment: JJ

Page: 10 of 12

Examples of a Schedule Change and Seat Re-accommodation in One Message:

HDQRMAA

.ATLRMDL 031519

ASC

HDQAA AB76AB/12345678

1JONES/JONATHANMR

DL719Y15NOV LAXSEA UN1

DL743Y15NOV LAXSEA TK1/1500 1710

DL743Y15NOV LAXSEA HK1

SSR SEAT DL KK1LAXSEA0743Y15NOV.20AS/RS

Example of a Schedule Change and SEAT Re-accommodation in Two separate messages:

HDQRMAA

.ATLRMDL 030052

ASC

HDQAA AB76AB/12345678

1JONES/JONATHANMR

DL719Y15NOV LAXSEA UN1

DL743Y15NOV LAXSEA TK1/1500 1710

HDQRMAA

.ATLRMDL 030052

ASCBPR

HDQAA AB76AB/12345678

1JONES/JONATHANMR

DL743Y15NOV LAXSEAHK1

SSR SEAT DL KK1LAXSEA0743Y15NOV.20AN/RS

(d) Re-accommodation of pre-reserved SEATs on a change of gauge flight.

Example of re-accommodation for all legs:

UA916Y22APR TPELAX UN2

UA900Y22APR TPELAX TK2/1700 1000

SSR SEAT UA KK2 TPENRT 0900Y22APR.20AN20BN/RC

SSR SEAT UA KK2 NRTSFO 0900Y22APR.19AN19BN/RC

SSR SEAT UA KK2 SFOLAX 0900Y22APR.15EN15DN/RZS

Example of re-accommodation for a single leg:

UA916Y22APR TPELAX TK2/1700 1000

3.19.11.1 Any Member receiving a pre-reserved seat request for a change gauge flight may respond with 

one or more separate Supplementary Items in the reply message when seats are confirmed:

(a) when different seats are assigned on different sectors, two or more SSR items are sent in reply. The 

flight segment in each item may use the boarding point and the local boarding date where the 

equipment/seat assignment changes.

Examples:

SSR SEAT UA KK2DENLAX0816Y26MAY.31DN31EN

SSR SEAT UA KK2LAXAKL0816Y26MAY.38GS38HS/RGC

(b) the second item will show the unique identifier RG, if boarding pass authority granted, or RC if only 

reserved seat authorized, or RZ if boarding pass issuance is inhibited until bilaterally agreed time limit 

allows. The first SSR item may show a different Transaction Identifier than the second. For example, the 

Member may allow boarding pass issuance on the first segment but not allow it on the second.
Attachment: JJ

Page: 11 of 12

3.19.11.2 Examples of Change of Gauge Items

Example 1 — Seats reserved (boarding pass allowed):

SSR SEAT CO KK2MCIDEN0719Y15NOV.23AN23BN

SSR SEAT CO KK2DENLAX0719Y15NOV.47AN47BN/RG

Example 21 — Seats reserved (boarding pass inhibited):

SSR SEAT CO KK2MCIDENO719Y15NOV.23AN23RN/RS

SSR SEAT CO KK2DENLAX0719Y15NOV.47AN47BN/RC

Example 3 — Seats reserved (boarding pass inhibited on one segment):

SSR SEAT CO KK2MCIDEN0719Y15NOV.23AN23BN

SSR SEAT CO KK2DENLAX0719Y15NOV.47AN48BN/RC

Example 4 — Seats reserved (boarding pass inhibited on one segment until bilaterally agreed time

period):

SSR SEAT CO KK2MCIDEN0719Y15NOV.23AN23BN

SSR SEAT CO KK2DENLAX0719Y15NOV.47AN48BN/RZ

Example 5 — Advance seat reservation allowed on only one segment of the change of gauge

flight:

SSR SEAT CO KK2MCIDEN0719Y15NOV.23AN23BN/RC

SSR SEAT CO NO2DENLAX0719Y15NOV./SEAT SELECTION NOT OFFERED

Example 6 2 — Multiple SSR reply, confirming more than one seat number per passenger, including

a date change (boarding pass allowed):

SSR SEAT NW KK2 MSPNRT0807F19DEC.03AN03BN

SSR SEAT NW KK2 NRTHKG0807F20DEC.04AN04BN/RG

 

3.19.12 Group Seating

(a) Group Seating Request

The SSR Code “GPST” shall be used to request group seating when names are unknown or

no individual seat assignment is desired. Include the number of no smoking and/or smoking

seats followed by the zone code “N” or “S”, if known. Adjacent seating is desired, if possible.

To request individual seat assignments when names are known use the SSR Codes “NSSA”,

“NSSB”, “NSST”, “NSSW”, “RQST”, “SMSA”, “SMST”, “SMSB” and “SMSW”.

The Booking Agent must advise the appropriate airline(s) when proportional changes to no

smoking seats and smoking seats occur. Enter a supplementary item to cancel the existing

“GPST” item followed by a new “GPST” item.

Example 1 — Group seats (names unknown, group total 40):

SSR GPST LX NN40AMSGVA0795Y14FEB.30N10S

Example 2 — Group seats (partial names, group total 40). No seat numbers requested:

SSR NSST NW NN2MSPNRT0103B20SEP-2BAKER/JOHNMR/THELMAMRS

SSR SMST NW NN1MSPNRT0103B20SEP-1JOHNSON/DON

SSR GPST NW NN37MSPNRT0103B20SEP

Example 3 — Group seats (partial names, group total 40). Seat numbers requested:

SSR NSST PA NN5LHRJFK0001Y20SEP-4MCCALL/TOMMR/HARRYMR/SUEMS/

SSR NSST PA ///JOANNEMS1POTTER/JOSEPHINEMRS.25A25B25C25D25E

Example 4 — Proportional changes in no smoking and smoking seats (reduce number in

party — 40 to 25):

SSR GPST LX XX40AMSGVA0795Y14FEB.30N10S

SSR GPST LX NN25AMSGVA0795Y14FEB.18N7S

Example 5 — Proportional change in no smoking seats and smoking seats (no change in

number in party):

SSR GPST LX XX40AMSGVA0795Y14FEB.30N10S

SSR GPST LX NN40AMSGVA0795Y14FEB.35N5S
Attachment: JJ

Page: 12 of 12

(b) Group Seating Reply

When replying to a group seating request whether names are known or unknown, the

responding airline may assign specific seat numbers or allocate a block of seats.

Example 1 — Group seats (names unknown, group total 40):

SSR GPST LX KK40AMSGVA0795Y14FEB.30N10S

Example 2 — Group seats (partial names, group total 40):

SSR NSST NW KK2MSPNRT0103B20SEP-2BAKER/JOHNMR/THELMAMRS.10A10B

SSR SMST NW KK1MSPNRT0103B20SEP-1JOHNSON/DON.42C

SSR GPST NW NO37MSPNRT0103B20SEP.NEED NAMES

Example 3 — Group seats (partial names, group total 40):

SSR NSST PA UN5LHRJFK0001Y20SEP-4MCCALL/TOMMR/HARRYMR/SUEMS/

SSR NSST PA ///JOANNEMS1POTTER/JOSEPHINEMRS

SSR NSST PA KK5LHRJFK0001Y20SEP-4MCCALL/TOMMR/HARRYMR/SUEMS/

SSR NSST PA ///JOANNEMS1POTTER/JOSEPHINEMRS.10A10B10C12A12B

(c) Replying to GPST

Seats confirmed or allocated using the code “GPST” shall be used for informational purposes

only by the booking agent.

Additional messages using the SSR code “GPST” are not required except when there is a

change to the proportion of no smoking seats and smoking seats.
Attachment: KK

Page: 1 of 1

AIRIMP & SIPP Resolution 105.175, section 3.9.5

2.11.7 Construction of OSI

2.11.7.1 Components

Enter the components in the following sequence:

(a) Supplementary Item Identifier OSI;

(b) Action Identifier Airline/GDS Designator (see 2.11.6.1(c));

(c) Service Information,

(d) Names (optional). If it is desired to indicate an association with one or more passenger 

names, the names should be formatted consistently with the rules used for construction of 

names in SSR elements as described in 2.11.6.1(f) 2.11.6.1(k).

2.11.7.2 Example of OSI Items (see also 2.6.15 2.6 “Name Element”)

OSI TW TCP5 2THOMPSON 1CLARK

OSI DL PASSENGER AFRAID OF FLYING

OSI/PAT VIP FREEDMAN/P PROFESSOR EMERITUS
Attachment: LL

Page: 1 of 1

AIRIMP & A4A SIPP Resolution 105.110

2.10: AUXILIARY SERVICE ELEMENT 

.....

(e) - Seven formats are acceptable for transmitting Auxiliary Service Elements:

 

 ATX – Air Taxi

 CAR – Car Rental

 CCR - Car Rental (Automated Format)

 HTL – Hotel accommodation

 HHL – Hotel accommodation (Automated Format)

 SUR – Surface (ship, rail, bus, etc.)

 SVC- Additional Service – Non Segment – Associated

 TUR – Tour (sightseeing, etc.)
Attachment: MM

Page: 1 of 3

AIRIMP & A4A SIPP Resolution 105.175, section 3.9.10

3.21.1 Segment-Associated Additional Services

[...]

3.21.1.3 Examples

[...]

Example 1(d) — Message from the booking source to the Member advising the EMD-A has been issued. 

This message is sent in response to a KD or SD.

HDQRMBA

.HDQRM1S 061520

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG HK2

SSR ASVC BA HS1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.H/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT/A/1250241234567C3

Example 1(e) — Message from the booking source to the Member cancelling the service after issuance. 

SSR ASVC XX includes EMD number

HDQRMBA

.HDQRM1S 061520

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

2SMITH/WALTERMR/MARYMRS

BA 0202Y14MAY LHRCDG HK2

SSR ASVC BA XX1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.H/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT/1250241234567C3

[...]

Example 3 — Message from the booking source to the Member requesting unaccompanied minor 

handling; ASVC is also sent denoting agent is aware an EMD is required.

HDQRMBA

.HDQRM1S 061519

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA NN1 LHRCDG 0202Y14MAY.UM07

SSR ASVC BA NN1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR

Example 3(a) — Message from the Member to the booking source confirming the unaccompanied minor 

handling; ASVC is sent with KD indicating an EMD-S is required.

HDQRM1S

.HDQRMBA 061519

HDQ1SQWERTY

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07

SSR ASVC BA KD1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR/S
Attachment: MM

Page: 2 of 3

Example 3(b) — Message from the booking source to the Member advising the EMD-S has been issued.

HDQRMBA

.HDQRM1S 061519

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR ASVC BA HS1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR/1250241234567C1

Example 3(c) — Message from the booking source to the Member cancelling the service after EMD 

issuance. ASVC with EMD number is sent along with SSR cancellation 

HDQRMBA

.HDQRM1S 061519

HDQ1SQWERTY/89D1/12345678/CBB/1S/T/BO/BOB

1SMITH/WALLYMSTR

BA 0202Y14MAY LHRCDG HK1

SSR UMNR BA XX1 LHRCDG 0202Y14MAY.UM07

SSR ASVC BA XX1 LHRCDG 0202Y14MAY.I/L04/UMNR/

SSR ASVC BA /// UNACCOMPANIED MINOR/1250241234567C1

3.21.1.4 Examples of Request and Reply Messages for Pre-reserved seats in SSR

SEAT elements in conjunction with SSR ASVC elements

[...]

Example 1 — Message from booking source to Member requesting a non-smoking aisle seat assignment; 

no ASVC is sent.

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB/K32/91295315/NCL/1P/T/GB//GS

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL NN1 NCLAMS1234S30JAN.NA

Example 1(a) — Message from the Member to the booking source confirming the seat assignment; no 

AVSC is included because no EMD is required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS
Attachment: MM

Page: 3 of 3

Example 1(b) — Message from the Member to the booking source confirming the seat assignment; ASVC 

is sent with KD as EMD-A is required.

HDQRM1P

.MUCRM1A 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS

SSR ASVC KL KD1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT/A

Example 1(c) — Message from the booking source to the Member advising the EMD-A has been issued.

MUCRM1A

.HDQRM1P 230920

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR ASVC KL HS1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT

SSR ASVC KL ////0740241234567C1

Example 1(d) — Message from the booking source to the Member cancelling the seat after EMD 

issuance. ASVC with EMD number is sent along with Seat cancellation

MUCRM1A

.HDQRM1P 230920

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S30JAN NCLAMS HK1

SSR SEAT KL XX1 NCLAMS1234S30JAN.24CN/RS

SSR ASVC KL XX1 NCLAMS1234S30JAN.H/S23/SEAT/CHARGEABLE SEAT

SSR ASVC KL ////0740241234567C1
Attachment: NN

Page: 1 of 2

AIRIMP & A4A SIPP Resolution 105.175

3.3.9 Cancelling Special Service Request by the member

3.3.9.1 Whenever an airline needs to cancel a Special Service Request (automated format) 

originally booked by a Member/CRS, use Advice Code “HX” on the SSR Element(s) affected. 

3.3.9.2 An SSR OTHS may be included advising the booking Member/CRS of the reason for the 

cancellation.

3.3.9.3. Example of these cancellation messages

SWIRM1G

.MUCRM1A

Record Locator .....................SWI1G QWERTY

Name Element ......................1MANSART/PASCALEMRS

Segment Element .................KL1223Y10MAR AMSCDG HK1

Segment Element .................AF2240Y15MAR CDGAMS HK1

Supplementary Element........SSR BIKE KL HX1 AMSCDG1223Y10MAR

Supplementary Element........SSR BIKE AF HX1 CDGAMS2240Y15MAR

Supplementary Element........SSR OTHS 1G SERVICE XXLD BY PSGR

SWIRM1G

.MUCRM1A

Record Locator...........................SWI1G QWERTY

Name Element ...........................1MANSART/PASCALEMRS 1POUCET/ISABELLEMRS

Segment Element.......................KL1223Y10MAR AMSCDG HK2

Segment Element.......................AF2240Y15MAR CDGAMS HK2

Supplementary Element.............SSR SEAT KL HX1 AMSCDG1223Y10MAR.10AN1MANSART/PASCALEMRS

Supplementary Element.............SSR SEAT AF HX1 CDGAMS2240Y15MAR.11AN1MANSART/PASCALEMRS

Supplementary Element.............SSR SEAT KL KK1 AMSCDG1223Y10MAR.20HN1MANSART/PASCALEMRS

Supplementary Element.............SSR SEAT AF KK1 CDGAMS2240Y15MAR.21HN1MANSART/PASCALEMRS

Supplementary Element.............SSR OTHS 1G ONLINE REBOOKING BY PSGR

3.3.9 10 Booking Space and Cancelling/Booking SSR Elements by a Member 

(Bilateral)

Secretary Note: re-number the rest of the section
Attachment: NN

Page: 2 of 2

3.21.1.3 Examples

.....

Example 1(e) – Message from the member to the booking source advising the service has been 

cancelled since no EMD was issued.

HDQRM1S

.HDQRMBA

HDQ1S QWERTY

2SMITH/WALTERMR/MARYMRS

BA020Y14MAY LHRCDG HK2

SSR ASVC BA HX1 LHRCDG020Y14MAY-1SMITH/WALTERMR.H/E23//IN FLIGHT

SSR ASVC BA /// ENTERTAINMENT

SSR OTHS 1S SERVICE XXLD – NO EMD ISSUED

.....

Example 4(c) – Message from the member to the booking source advising the seat has been 

cancelled since no EMD was issued.

HDQRM1P

.MUCRM1A

HDQ1P Y7HAWB 110550

1WALKER/JOHNMR

KL1234S20JAN NCLAMS HK1

SSR NSSA KL HX1 NCLAMS1234S20JAN.24C

SSR ASVC KL HX1 NCLAMS1234S20JAN.H/S23/NSSA/CHARGEABLE SEAT

SSR OTHS 1P SEAT XXLD – NO EMD ISSUED

.....

3.21.1.4 Examples of Request and Reply Message for Pre-reserved seats in SSR SEAT 

elements in conjunction with SSR ASVC elements

.....

Example 1(c) – Message from the member to the booking source advising the seat has been 

cancelled since no EMD was issued.

HDQRM1P

.MUCRM1A 110550

BPR

HDQ1P 7YHAWB

1WALKER/JOHNMR

KL1234S20JAN NCLAMS HK1

SSR SEAT KL HX1 NCLAMS1234S20JAN.24CN/RS

SSR ASVC KL HX1 NCLAMS1234S20JAN.H/S23/SEAT/CHARGEABLE SEAT

SSR OTHS 1P SEAT XXLD – NO EMD ISSUED
Attachment: OO

Page: 1 of 2

AIRIMP & A4A SIPP Resolution 105.86, section 1.8/105.175

3.1.14 Ticket Numbers Request (Bilateral)

(Note: bilateral agreement required.)

3.1.14.1 Definitions

When a ticketing ticket number is requested due to time limit, message is required, SSR 

ADTK should be used. SSR OTHS should not be used for this purpose. The booking 

source is expected to advise ticket numbers using applicable SSR, TKNA, TKNM or 

TKNE.

3.1.14.2 Example

Example of aAirline request for ticket numbers to CRS, the originator of the booking:

SWIRM1G

.AMSRMKL 121314

SWI1G ABC472

2VANDERGOOT/MR/MRS

KL652B14APR IADAMS HK2

KL341B15APR AMSGVA HK2

SSR ADTK 1G TO KL BY 10APR 2200 OTHERWISE WILL BE XLD

The expected reply for this message will be sending the ticket number to the requester 

via the applicable SSR, TKNA, TKNM or TKNE.

3.1.14.3 Construction Rules and Sequence of Components

A space ( ) is inserted between each of elements.

Components

Number and 

Type of 

Characters

Mandatory 

or Optional Examples

(a) Supplementary Identifier 3a Mandatory SSR

(b) Special Service Requirement Code 4a Mandatory ADTK

(c) System code of the addressee 2an Mandatory 1G

(d) Fixed text 2a Mandatory TO

(e) Airline code 2an Mandatory KL

(f) Fixed text 2a Mandatory BY

(g) Local Date 2n3a Mandatory 10APR

(h) Local Time 4n Optional 2200

(i) Free text 1-30 an Optional OTHERWISE 

WILL BE XLD
Attachment: OO

Page: 2 of 2

2.11.6.7 SSR Matrix

SSR Code Action Code Reply

Automated

Format

Free Text in 

Request

Free Text in 

Reply/Cancel Reference

ADTK Not permitted Not permitted Not permitted Mandatory Not permitted Bilateral See

3.1.14
Attachment: PP

Page: 1 of 1

AIRIMP & SIPP

2.5 RECORD LOCATOR ELEMENT

2.5.1 Construction

......

2.5.1.3 Point of Sale Information in Booking Message

(a) Rules

Point of Sale Information must be constructed according to the following rules:

.....

• the 7 to 8-digit user identification number may be one of the following:

o the IATA/ARC travel agency number

o TIDS (Travel Industry Designator Service) number

o ERSP (Electronic Reservation Services Provider) number; when an ERSP number is 

present, the ERSP unique user identification number and the point of first departure are 

mandatory, as defined in IATA Resolution 784

o Pseudo number assigned by the Member/CRS

• the user type is mandatory, in accordance with the following list:

o Airline

o E—Electronic Reservation Services Provider (ERSP, as defined in IATA Passenger 

Agency Conference Resolution 898a)

o N— User does not have a user identification number assigned by IATA/ARC

o T—User has a user identification number assigned by IATA/ARC other than an ERSP 

number

(b) Construction:

• Point of Sale Information may contain the following components and the components

should be entered in the following sequence:

.....

ERSP unique user identification number (assigned by the ERSP)

(conditional) ..................................................................................................... AB397DK3P

Point of first departure (conditional) ........................................................................... CDG

(c) Examples of Record Locators with Point of Sale Information:

.....

Example 4—With an ERSP provider, ERSP unique user identifier, and the point of first departure:

MUC1A K1EABJ/ATL025/54465380/JFK/LO/E/US///AB397DK3P/CDG
M E M O R A N D U M

PSC/RESO/154

To: All Members, Passenger Services Conference - Accredited 

Representatives

Copy: IATA Strategic Partners

From: Head, Interline & Intermodal Policy

Date: 28 January 2013

Subject: BOOK OF FINALLY ADOPTED RESOLUTIONS & RPs – Part 1

34th IATA Passenger Services Conference (PSC)

Abu Dhabi, 18-19 October 2012

Attached are the resolutions & recommended practices (RPs) which were adopted at the abovementioned Conference (except for Resolution 787).

The filing period is established as 29 January – 18 March 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: mullerm@iata.org) of their Government’s 

action by the end of the filing period (18 March 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 June 2013.

“Part 2” of the book of finally adopted resolutions and RPs was circulated on 28 January 2013

comprising Resolution 787 so that it could be filed separately with the DoT with a request for 

approval. Refer to memorandum PSC/RESO/156.

The Minutes of the Conference are issued separately under Memorandum PSC/MINS/042 dated 

28 January 2013.

Mike Muller International Air Transport Association

Route de l'Aeroport 33

PO Box 416

CH - 1215 Geneva 15 Airport

Switzerland

Tel: +41 22 770 2731

Fax: +41 22 770 2896

OUTLINE OF CONTENTS

RESOLUTIONS & RECOMMENDED PRACTICES

ADOPTED AT:

34th PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE: 1 JUNE 2013

Resolution/RP Title

PSC(34)003 STANDARD RECISSION RESOLUTION

PSC(34)720 PASSENGER TICKET AND BAGGAGE CHECK -

TECHNICAL SPECIFICATIONS

(amending)

PSC(34)720a PASSENGER TICKET AND BAGGAGE CHECK -

ISSUANCE AND HONORING PROCEDURES

(amending)

PSC(34)722 TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC(34)722a OFF PREMISE TRANSITIONAL AUTOMATED TICKET 

(OPTAT)

(amending)

PSC(34)722c AUTOMATED TICKET/BOARDING PASS - VERSION 2 

(ATB2)

(amending)

PSC(34)722f ELECTRONIC TICKET – AIRLINE

(amending)

PSC(34)722g ELECTRONIC TICKET – NEUTRAL

(amending)

PSC(34)722h ELECTRONIC TICKET – GROUND HANDLING

(amending)

PSC(34)725a MISCELLANEOUS CHARGES ORDER (MCO) –

ISSUANCE AND HONOURING PROCEDURES BY 

MEMBERS

(amending) 

PSC(34)725b

MISCELLANEOUS CHARGES ORDER (MCO) –

ISSUANCE AND HONOURING PROCEDURES 

(AGENTS) 

(amending)
PSC(34)725f ELECTRONIC MISCELLANEOUS DOCUMENT –

AIRLINE

(amending)

PSC(34)725g ELECTRONIC MISCELLANEOUS DOCUMENT –

NEUTRAL

(amending)

PSC(34)725h ELECTRONIC MISCELLANEOUS DOCUMENT –

GROUND HANDLING

(amending)

PSC(34)726a MULTIPLE PURPOSE DOCUMENT (MPD)—CARRIER, 

CARBONISED, AUTOMATED

(amending)

PSC(34)726e MULTIPLE PURPOSE DOCUMENT (MPD) – NEUTRAL, 

CARBONISED, MANUAL

(amending)

PSC(34)726f MULTIPLE PURPOSE DOCUMENT (MPD) - CARRIER, 

CARBONISED, MANUAL

(amending)

PSC(34)727 TICKETS - ALTERATIONS TO FLIGHT COUPONS

(amending)

PSC(34)728 CODE DESIGNATORS FOR PASSENGER TICKET 

AND BAGGAGE CHECK

(amending)

PSC(34)735 PERIOD OF VALIDITY

(amending)

PSC(34)735d INVOLUNTARY CHANGE OF CARRIER, ROUTING, 

CLASS OR TYPE OF FARE

(amending)

PSC(34)742c GOVERNMENT EXCESS BAGGAGE AUTHORIZATION 

(GEBA) FORM

(amending)

PSC(34)742d UNITED STATES GOVERNMENT EXCESS BAGGAGE 

AUTHORIZATION/ TICKET (GEBAT)

(amending)

PSC(34)746 POOLING OF BAGGAGE

(amending)

PSC(34)751 USE OF THE 10 DIGIT LICENCE PLATE

(new)

PSC(34)760a CHANGES TO RESERVATIONS INTERLINE 

MESSAGE PROCEDURES - PASSENGER (AIRIMP)

(amending)
PSC(34)780 FORM OF INTERLINE TRAFFIC AGREEMENT -

PASSENGER

(amending)

PSC(34)780e IATA INTERLINE TRAFFIC PARTICIPATION 

AGREEMENT – PASSENGER

(amending)

PSC(34)1701j AUTOMATED AND SELF-SERVICE FLIGHT 

REBOOKING FOR IRREGULAR OPERATIONS

(amending)

PSC(34)1706a FUNCTIONAL SPECIFICATION FOR PASSENGER 

SELF-SERVICE SYSTEMS

(amending)

PSC(34)1707a DATA FIELD DIRECTORY FOR DCS PASSENGER 

MESSAGES

(amending)

PSC(34)1707b DATA ELEMENT DIRECTORY FOR DCS PASSENGER 

MESSAGES

(amending)

PSC(34)1708 PASSENGER NAME LIST (PNL) AND ADDITIONS AND 

DELETIONS LIST (ADL)

(amending)

PSC(34)1719 PASSENGER FINAL SALES MESSAGE (PFS)

(amending)

PSC(34)1719b PASSENGER RECONCILE LIST (PRL)

(amending)

PSC(34)1719e ADDITIONAL SERVICE LIST (ASL)

(new)

PSC(34)1735 PLANNED SCHEDULE CHANGES

(new)

PSC(34)1745 BAGGAGE INFORMATION MESSAGES

(amending)

PSC(34)1761a GUIDELINES FOR THE ALLOCATION OF AIRPORT 

SLOTS

(new)

PSC(34)1777 ONLINE MARRIED SEGMENT CONTROL

(amending)

PSC(34)1779 JOURNEY DATA

(amending)
PSC(34)1786 PASSENGER DISTRIBUTION LIFECYCLE

(new)

PSC(34)1788 TICKETING AND BAGGAGE REGULATIONS FOR 

FREE AND REDUCED TRANSPORTATION

(amending)

PSC(34)1790 ADDITIONAL SERVICES

(amending)

PSC(34)1791d PAYMENT CARD INDUSTRY DATA SECURITY 

STANDARDS (PCI DSS) COMPLIANCE

(new)

PSC(34)1797 COMMON USE PASSENGER PROCESSING 

SYSTEMS (CUPPS)

(amending)

PSC(34)1797a AVIATION INFORMATION DATA EXCHANGE (AIDX)

(amending)

PSC(34)1800 AUTOMATED BAGGAGE HANDLING BASED ON THE 

IATA LICENCE PLATE CONCEPT

(amending)
SUMMARY OF CHANGES

RESOLUTIONS/RECOMMENDED PRACTICES FINALLY ADOPTED AT:

34th PASSENGER SERVICES CONFERENCE (PSC)

INTENDED EFFECTIVE DATE:

1ST JUNE 2013

Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 003

STANDARD 

RECISSION 

RESOLUTION

Resolution rescinds a 

previously adopted Resolution.

Resolution 784, ‘Electronic 

Reservations Services Providers’ and 

Recommended Practice 1762, 

‘Reconfirmation Procedures’ are 

rescinded. 

RESOLUTION 720

PASSENGER TICKET 

AND BAGGAGE 

CHECK - TECHNICAL 

SPECIFICATIONS

Provides technical 

specifications for the issuance 

of manual passenger tickets.

The ‘Baggage Allowance’ box is 

amended to remove the word ‘free’ 

and to remove the option to leave it 

blank.

RESOLUTION 720a

PASSENGER TICKET 

AND BAGGAGE 

CHECK – ISSUANCE 

AND HONOURING 

PROCEDURES

Provides governing rules on 

how to issue a ticket, and 

applicable conditions for the 

honoring and re-issuance of 

tickets.

Procedures for EMU transition to Euro 

currency are deleted.

Provisions are added to provide 

additional baggage information.

RESOLUTION 722

TRANSITIONAL 

AUTOMATED TICKET 

(TAT)

Provides governing rules on 

how to produce an 

“automated” ticket issued by 

airlines. It also provides the 

technical specifications and 

applicable conditions for the 

honoring of such tickets.

Procedures for EMU transition to Euro 

currency are deleted.

The ‘Baggage Allowance’ box is 

amended to remove the word ‘free’ 

and to remove the option to leave it 

blank.

RESOLUTION 722a

OFF PREMISE 

TRANSITIONAL 

AUTOMATED TICKET 

(OPTAT)

Provides technical 

specifications and print line 

specifications for the issuance 

of paper ‘automated’ tickets 

issued by airlines.

The ‘Baggage Allowance’ box is 

amended to remove the word ‘free’.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 722c

AUTOMATED 

TICKET/BOARDING 

PASS - VERSION 2 

(ATB2)

Provides governing rules on 

how to produce an 

“automated” ticket issued by 

airlines on magnetic stripe 

encoded ticket stock. It also 

provides the technical 

specifications and applicable 

conditions for the honoring of 

such tickets.

The ‘Baggage Allowance’ box is 

amended to remove the word ‘free’.

A technical correction is made to 

amend Sundry Charges to read 

‘Reservations Change Fee’.

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.

Procedures for EMU transition to Euro 

currency are deleted.

The itinerary receipt is amended to 

remove the word ‘free’ from the 

baggage allowance.

Technical clarifications are added to 

make it clear to whom a display 

request message is sent.

A new set of data elements to add 

more definition to baggage 

allowances is added.

Additional data elements are added to 

the ‘reissued flown flight coupon data’.

New data elements are added to 

identify domestic vs. international 

routing differentiation in electronic 

tickets and miscellaneous documents.

Corresponding changes to messaging 

matrices are added.

RESOLUTION 722g

ELECTRONIC

TICKET – NEUTRAL

Provides governing rules and 

technical specifications on how 

to produce an Electronic Ticket 

(ET) issued by travel agents. 

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.

Procedures for EMU transition to Euro 

currency are deleted.

The itinerary receipt is amended to 

remove the word ‘free’ from the 

baggage allowance.

Technical clarifications are added to 

make it clear to whom a display 

request message is sent.

A provision is added for agents who 

issued the original ticket to 

exchange/reissue or refund tickets 

which were subsequently changed by 

the original validating carrier.

New data elements are added to the 

messaging matrices.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 722h

ELECTRONIC 

TICKET – GROUND 

HANDLING

Provides governing rules and 

technical specifications to be 

followed for the third party 

ground-handling of electronic 

tickets (ETs). This allows 

airlines to have their electronic 

tickets handled by third party 

ground handlers.

The itinerary receipt is amended to 

remove the word ‘free’ from the 

baggage allowance.

A provision is added that a ground 

handler shall return the actual coupon 

status in a display response when 

there is a single matching electronic 

ticket.

New data elements are added to the 

messaging matrices.

RESOLUTION 725a

MISCELLANEOUS 

CHARGES ORDER 

(MCO) – ISSUANCE 

AND HONOURING 

PROCEDURES BY 

MEMBERS

Provides governing rules on 

how to issue and honor a

Miscellaneous Charges Order 

(MCO) issued be airlines.

‘Sundry Charges’ is amended to read 

‘Reservations Change Fee’

Procedures for EMU transition to Euro 

currency are deleted.

RESOLUTION 725b

MISCELLANEOUS 

CHARGES ORDER 

(MCO) – ISSUANCE 

AND HONOURING 

PROCEDURES 

(AGENTS)

Provides governing rules on 

how to issue and honor a 

Miscellaneous Charges Order 

(MCO) issued be agents.

‘Sundry Charges’ is amended to read 

‘Reservations Change Fee’

Procedures for EMU transition to Euro 

currency are deleted.

RESOLUTION 725f

ELECTRONIC 

MISCELLANEOUS 

DOCUMENT –

AIRLINE

Provides governing rules for 

the issuance and use of 

Electronic Miscellaneous 

Documents (EMD) by airlines.

The EMD is an electronic 

method to document the sale 

and usage of charges 

associated to various usage, 

e.g. excess baggage charges.

Procedures for EMU transition to Euro 

currency are deleted.

Technical clarifications are added to 

make it clear to whom a display 

request message is sent.

New data elements are added to the 

messaging matrices.

RESOLUTION 725g

ELECTRONIC 

MISCELLANEOUS 

DOCUMENT –

NEUTRAL

Provides governing rules for 

the issuance and use of 

Electronic Miscellaneous 

Documents (EMD) by agents.

A ‘System Update’ message to allow 

agents to request the validating carrier 

to associate an EMD-A to an ET 

coupon is added.

Procedures for EMU transition to Euro 

currency are deleted.

Technical clarifications are added to 

make it clear to whom a display 

request message is sent.

New data elements are added to the 

messaging matrices.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 725h

ELECTRONIC 

MISCELLANEOUS 

DOCUMENT –

GROUND HANDLING

Provides governing rules and 

technical specifications to be 

followed for the third party 

ground-handling of electronic 

miscellaneous documents 

(EMDs). This allows airlines to 

have their EMDs handled by 

third party ground handlers.

Technical clarifications are added to 

make it clear to whom a display 

request message is sent.

New data elements are added to the 

messaging matrices.

RESOLUTION 726a

MULTIPLE PURPOSE 

DOCUMENT (MPD) -

CARRIER, 

CARBONISED, 

AUTOMATED

Provides governing rules on 

how to issue a Multiple 

Purpose Document (MPD) by 

airlines in an automated 

environment.

Procedures for EMU transition to Euro 

currency are deleted.

RESOLUTION 726e

MULTIPLE PURPOSE 

DOCUMENT (MPD) –

NEUTRAL, 

CARBONISED, 

MANUAL

Provides governing rules on

how to issue a Multiple 

Purpose Document (MPD) by 

agents. 

Procedures for EMU transition to Euro 

currency are deleted.

RESOLUTION 726f

MULTIPLE PURPOSE 

DOCUMENT (MPD) -

CARRIER, 

CARBONISED, 

MANUAL

Provides governing rules on 

how to issue a Multiple 

Purpose Document (MPD) by 

airlines in a manual 

environment.

Procedures for EMU transition to Euro 

currency are deleted.

RESOLUTION 727

TICKETS -

ALTERATIONS TO 

FLIGHT COUPONS

Provides governing rules on 

how to make alterations to 

flight coupons.

‘Free’ is deleted from the baggage 

allowance.

RESOLUTION 728

CODE 

DESIGNATORS FOR 

PASSENGER TICKET 

AND BAGGAGE 

CHECK

Provides various coding 

structures in order to identify 

the type of fare and other 

conditions of travel for tickets 

and other documents.

A new payment card code is added 

for ‘China Union Pay’ card.

RESOLUTION 735

PERIOD OF 

VALIDITY

Provides governing rules to 

establish the period of validity 

of a ticket.

A new example of how to calculate 

the maximum validity of an unused 

ticket is added.

RESOLUTION 735d

INVOLUNTARY 

CHANGE OF 

CARRIER, ROUTING, 

CLASS OR TYPE OF 

FARE

Provides governing rules for 

the involuntary rerouting of 

passengers due to flight 

disruptions.

Clarifications are added to make it 

clear which baggage allowance shall 

apply to a passenger that is subject to 

an involuntary rerouting.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 742c

GOVERNMENT 

EXCESS BAGGAGE 

AUTHORIZATION 

(GEBA) FORM

Provides governing rules on 

how to issue a government 

excess baggage authorization 

form.

‘Free’ is deleted from the baggage 

allowance.

RESOLUTION 742d

UNITED STATES 

GOVERNMENT 

EXCESS BAGGAGE 

AUTHORIZATION/ 

TICKET (GEBAT)

Provides governing rules on 

how to issue United States 

government excess baggage 

authorization/Ticket.

‘Free’ is deleted from the baggage 

allowance.

RESOLUTION 746

POOLING OF 

BAGGAGE

Provides governing rules on 

when baggage can be pooled. 

‘Free’ is deleted from the baggage 

allowance.

RESOLUTION 751

USE OF THE 10 

DIGIT LICENCE 

PLATE

Provides rules for sending 

baggage identification 

numbers based on Resolution 

740

Provides that all baggage license 

plate messages are sent in their 10 

numeric digit form, rather than as a 2 

character airline code and 6 digit 

baggage identification number

RESOLUTION 760a

CHANGES TO 

RESERVATIONS 

INTERLINE 

MESSAGE 

PROCEDURES -

PASSENGER 

(AIRIMP)

Provides rules on how to 

changes interline reservation 

messages as published in the 

A4A/IATA AIRIMP manual

Reduces voting period for the mail 

vote process down from 30 days to 14 

days 

RESOLUTION 780

FORM OF INTERLINE 

TRAFFIC 

AGREEMENT –

PASSENGER

Provides the standard text for 

multi-lateral interline traffic 

agreements.

Updates the resolution regarding the 

pro-rate process for passenger 

baggage claims

RESOLUTION 780e

IATA INTERLINE 

TRAFFIC 

PARTICIPATION 

AGREEMENT –

PASSENGER

Provides the standard text for 

multi-lateral interline traffic 

agreements where only one 

airline is able to issue tickets.

Updates the resolution regarding the 

pro-rate process for passenger 

baggage claims and to removes 

Article 5.4.10 regarding advance 

notification of claims exceeding USD 

1,500. 

RP 1701j

AUTOMATED AND 

SELF-SERVICE 

FLIGHT REBOOKING 

FOR IRREGULAR 

OPERATIONS

One of the “passenger 

experience standards” that 

provides guidelines for selfservice re-booking in cases of 

irregular operations

Clarifies that requests for availability 

and confirmations shall be performed 

in accordance with the procedures for 

involuntary rerouting and not via 

general availability.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 1706a

FUNCTIONAL 

SPECIFICATION FOR 

PASSENGER SELFSERVICE SYSTEMS

Provides guidelines regarding

functional specifications for the 

development of self-service 

systems for airline passengers

‘Free’ is deleted from the baggage 

allowance specifications. 

RP 1707a

DATA FIELD 

DIRECTORY FOR 

DCS PASSENGER 

MESSAGES

Provides definitions and 

formats for the automatic 

creation, transmission, receipt 

and interpretation of this group 

of messages.

Clarifies PNL/ADL formats for 

ancillary services and introduces a 

new ‘Additional Service List’ to update 

the post-departure message to 

accommodate passengers who use 

ancillary services.

RP 1707b

DATA ELEMENT 

DIRECTORY FOR 

DCS PASSENGER 

MESSAGES

Provides specifications and 

rules governing the use of 

DCS Passenger Messages. 

These messages are used to 

provide various pieces of 

information that support the 

“seamless” interline 

transportation of passengers.

Introduces a new ‘Additional Service 

List’ to update the post-departure 

message to accommodate 

passengers who use ancillary 

services.

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.

Clarifies PNL/ADL formats for 

ancillary services and adds a family of 

SSRs to be used with ASVC for 

chargeable ancillary services. Also 

truncates credit card numbers when 

used as a form of identification to be 

in compliant with PCI DSS 

specifications,

RP 1719

PASSENGER FINAL 

SALES MESSAGE 

(PFS)

The PFS message gives 

information to reservations 

systems about the final counts 

loaded on an aircraft at the 

departure station. List 

contains a numeric summary 

of passenger counts and may 

contain passenger names

Clarifies the types of passengers who 

fall in the categories NOSHO, 

GOSHO and GOSHN.

RP 1719b

PASSENGER 

RECONCILE LIST 

(PRL)

The PRL is a list containing all 

passenger check-in details for 

actual boarded passengers of 

a flight departure.

Editorial update to facilitate recording 

of Additional Services.

RESOLUTION 1719e

ADDITIONAL 

SERVICE LIST (ASL)

Provides guidelines for 

recoding of use of Additional 

Services by passengers 

New Recommended Practice.

RESOLUTION 1735

PLANNED 

SCHEDULE 

CHANGES

Provides guidelines for the 

servicing of tickets affected by 

a planned schedule change.

New Recommended Practice.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RP 1745

BAGGAGE 

INFORMATION 

MESSAGES

Provides the definitions, 

formats and specifications for 

all of the messages used in 

the baggage handling process.

Various editorial updates to improve 

accuracy and consistency.

RESOLUTION 1761a

GUIDELINES FOR 

THE ALLOCATION 

OF AIRPORT SLOTS

Provides guidelines for the 

allocation of airport slots.

New Recommended Practice.

RESOLUTION 1777

ONLINE MARRIED 

SEGMENT CONTROL

Provides guidelines for 

implementing online married

segment control

Introduced need for capability to apply 

Married Segment Control for up to 6 

segments in one marriage, regardless 

whether round-trip marriage is 

applied/involved or not, for 

consistency across all GDSs.

RESOLUTION 1779

JOURNEY DATA

Provides guidelines regarding 

the transmission of journey 

data

Clarifies that full PNR itinerary 

information content is to be sent by 

GDSs/CRSs to the airlines. 

RESOLUTION 1786

PASSENGER 

DISTRIBUTION 

LIFECYCLE

Provides a description of a 

twelve process model detailing 

the different disciplines, 

business units and expertise 

that goes to make up the 

passenger distribution lifecycle 

and the associated industry 

groups that develop the 

standards and illustrates the 

linkage between them.

New Recommended Practice.

RESOLUTION 1788

TICKETING AND 

BAGGAGE 

REGULATIONS FOR 

FREE AND 

REDUCED 

TRANSPORTATION

Provides guidelines for 

issuance of tickets based on 

free or reduced rate industry 

transportation.

Deletes the full list of ‘employing 

company codes’ since these are 

described in the interline staff travel 

agreement.

RP 1790

ADDITIONAL 

SERVICES

Guidelines to facilitate the 

reservations, sales and 

delivery of airline additional 

services

Editorial corrections.

RESOLUTION 1791d

PAYMENT CARD 

INDUSTRY DATA 

SECURITY 

STANDARDS (PCI 

DSS) COMPLIANCE

Provides guidelines on how to 

become PCC DSS compliant 

and maintain such compliance.

New Recommended Practice.

RP 1797

COMMON USE 

PASSENGER 

PROCESSING 

SYSTEMS (CUPPS)

Provides guidelines for 

CUPPS systems that enable 

airlines to share check-in 

desks or gate podiums for 

boarding processes

Editorial updates.
Resolution/

Recommended 

Practice

Summary of 

Resolution/RP

Summary of Amendment

RESOLUTION 1797a

AVIATION 

INFORMATION DATA 

EXCHANGE (AIDX)

Provides guidelines on how to 

exchange flight related 

information for the purposes of 

displaying or accruing such 

information.

Recommended Practice fully revised 

to provide detailed information to

describe the use of interfaces 

specifications and standards by which 

parties exchange information between 

their systems.

RESOLUTION 1800

AUTOMATED 

BAGGAGE 

HANDLING BASED 

ON THE IATA 

LICENCE PLATE 

CONCEPT

Provides guidelines for 

automated baggage handling 

within airline operations from 

an airline perspective

Editorial updates.
 RESOLUTION 003

STANDARD RECISSION RESOLUTION

PSC(34)003 Expiry: 2 June 2013

Type: B

Resolved that, effective 1 June 2013, the following Resolution and Recommended 

Practice are rescinded:

Resolution 784 – Electronic Reservation Services Providers R5

RP 1762 – Reconfirmation Procedures R4.7/P

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 720

PASSENGER TICKET AND BAGGAGE CHECK—TECHNICAL SPECIFICATIONS

(amending)

PSC(33 34)720 Expiry: Indefinite

Type: B

RESOLVED that:

.....

T2.12/P

22. “BAGGAGE” BOXES

22.1 “Allow” Box

22.1.1 Enter the free baggage allowance amount followed by kilos ‘K’ or pounds ‘L’, e.g. 

20K or 44L. When the free baggage allowance is based on pieces, the field may shall 

contain ‘PC’ optionally preceded by the number of pieces, e.g. PC or 2PC. When the 

free baggage allowance is unknown, the free baggage allowance field may also be 

blank. When the fare used does not permit any free baggage allowance, ‘NO’, ‘NIL’ or 

‘XX’ shall be entered in the free baggage allowance field.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 720a

PASSENGER TICKET AND BAGGAGE CHECK—ISSUANCE AND HONOURING

PROCEDURES

(amending)

PSC(33 34)720a Expiry: Indefinite

Type: B

T4

13. “FARE” BOX1

....

13.1.1 For travel commencing in the countries of the Economic and Monetary Union 

(EMU) the “Fare” box may show only the ISO currency code of the “euro”2,3.

....

2 Applicable during the EMU transition period. When it is advised that an EU Member 

State will be converting from a legacy currency to the euro the “Fare” box may show 

either the ISO currency code of the national currency or the ISO currency code of the 

“euro”.

3

Implementation of these procedures for the transition period will be advised by IATA 

Head, Interline & Intermodal Policy.

....

14. “EQUIVALENT FARE PAID” BOX1

....

14.1.1.1 Exception for new EMU countries. During the period of transition2

the new EMU countries may have dual expression of the same currency. No entry in

the “EQUIVALENT FARE PAID” box shall be made when payment is in either euro or 

the national currency expression.

....

2 Implementation of these procedures for the transition period will be advised by IATA 

Head, Interline & Intermodal Policy.

.....
T2.9/P

22. “BAGGAGE” BOXES

.....

22.3 Additional Baggage Information

22.3.1 When the baggage allowance is based on pieces and the maximum baggage 

weight and/or baggage dimensions are determined, these may be stored for 

each flight coupon.

22.3.2 If any allowable baggage types for baggage allowance other than weight and 

dimensions are determined, these may be stored for each flight coupon.

22.3.3 Baggage charge amount for the first and second baggage may be stored for 

each flight coupon. 

22.3.4 Carry-on baggage allowance of the carry-on baggage allowance determining 

carrier may be stored for each flight coupon with the maximum weight and/or 

dimensions .

 Attachment ‘B’ T4

REISSUANCE PROCEDURES (optional for Members which are Members of

A4A—Applicable to manually issued and automated tickets)

....

5. DOCUMENTS REQUIRING REISSUE FROM A LEGACY CURRENCY OF AN EU 

MEMBER STATE TO THE EURO.

The entire paragraph 5 becomes effective only upon notification by IATA Head, Interline 

& Intermodal Policy and applies only for the duration of the transition period

from a legacy currency to the euro. The following procedures will apply when tickets, 

issued before the commencement of the transition period and showing a fare in the 

national legacy currency of one of the EMU countries, and are reissued on or after com 

mencement of the transition period.

5.1 Reissues Without a Change in Fare

5.1.1 If there is no change in the fare, convert the original legacy currency to EUR, 

using the fixed conversion rate1 and rounded up to next higher EUR 1.

_______

1 The fixed conversion rate will be established in accordance with currency procedures 

and will be notified upon commencement of the transition period.
5.2 Reissues Resulting in a Higher Fare

5.2.1 Establish the original NUC amount used to construct the fare in the original legacy 

currency.

5.2.2 Establish the fare for the new itinerary in NUCs. (This NUC amount is to be 

converted to EUR applying the IROE and rounded up to the next higher EUR 1 and

shown in the ‘Fare’ box of the new ticket.)

5.2.3 Calculate the difference in NUCs between the fare for the new itinerary and the 

original ticket.

5.2.4 Convert the difference into EUR, rounded up to the next higher EUR 1. This 

amount is to be paid by the passenger.

5.2.5 The ‘Equivalent Fare Paid’ box will only show the currency code(s) shown in the 

“EFP” box of the original ticket plus the code of the currency of additional collection. 

When an EMU legacy currency is shown in the EFP box of the original ticket, enter 

EUR.

5.2.6 The ‘Total’ box will show the amount to be collected, preceded by the currency 

code of additional collection. Follow this entry by ‘A’.

5.3 Reissues Resulting in a Lower Fare

5.3.1 Establish the original NUC amount used to construct the fare in the original legacy 

currency.

5.3.2 Establish the fare for the new itinerary in NUCs.

5.3.3 Calculate the difference in NUCs between the fare of the original ticket and the 

new itinerary.

5.3.4 Convert the difference into EUR, rounded up to the next higher EUR 1.

5.3.5 This amount is to be refunded to the passenger. A balance MCO showing an EUR 

amount may be issued instead.

5.3.6 The ‘Equivalent Fare Paid’ box will only show the currency code(s) shown in the 

EFP' box of the original ticket. When an EMU legacy currency is shown in the

EFP box of the original ticket, enter EUR.

5.3.7 The ‘Total’ box will show NOADC to reflect the fact that no additional collection is 

made. 
5.4 Taxes/Fees/Charges

5.4.1 When a reissue requires the additional collection of taxes/fees/charges, these 

taxes/fees/charges shall be shown in the currency of additional collection. 

Taxes/fees/charges of EMU countries which have not been filed in EUR shall be 

converted to EUR, using the fixed conversion rate, and rounded up to the next higher 

EUR 0.01.

5.4.2 For taxes/fees/charges already paid, enter “PD” in the tax/fee/charge box followed 

by the tax/fee/charge amount already paid and the applicable tax/fee/charge code 

without conversion to the euro.

5.5 Miscellaneous Charges Orders

5.5.1 MCO's issued before the end of the transition period and showing an EMU legacy 

currency may be accepted subject to the validity of the MCO but only at the EUR 

equivalent using the fixed rate of conversion that will be advised.

5.5.2 The deduction method for MCO's showing an amount in an EMU legacy currency 

may not be used after the last day of the end of the transition period. Instead, the MCO 

must first be reissued into an MCO with an EUR amount, using the fixed rate of 

conversion and rounded up to the next higher EUR 1. Subsequently, the EUR amount 

due may be deducted from the value of the MCO. (Deduction method shall not be 

applicable to Stand Alone Electronic Miscellaneous Documents (EMD-S) issued for 

residual value).

6. REFUNDS AFTER THE END OF A EURO TRANSITION PERIOD

Refunds of tickets issued before the end of the transition period and showing a fare in 

the national legacy currency of the new EMU country(ies) shall be established in EUR, 

using the fixed conversion rate which will be advised.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 722

TRANSITIONAL AUTOMATED TICKET (TAT)

(amending)

PSC(33 34)720a Expiry: Indefinite

Type: B

T4

3.17 FARE1

....

3.17.2 For travel commencing in the countries of the Economic and Monetary Union 

(EMU) the “Fare” box may show only the ISO currency code of the “euro”2,3

....

3.18 EQUIVALENT FARE PAID1

....

3.18.1.1.1 Exception for new EMU countries. During the period of transition2 the new 

EMU countries may have dual expression of the same currency. No entry in the “EQUIV 

FARE PAID” box shall be made when payment is in either euro or the national currency 

expression.

______________

2 Applicable during an EMU transition period. When it is advised that an EU Member 

State will be converting from a legacy currency to the euro the “Fare” box may show 

either the ISO currency code of the national currency or the ISO currency code of the 

“euro”.

3

Implementation of these procedures for the transition period will be advised by IATA 

Head, Interline & Intermodal Policy.

.....

T2.12/P

3.26 BAGGAGE INFORMATION

3.26.1 Allow

Imprint the free baggage allowance amount followed by kilos ‘K’ or pounds ‘L’, e.g. 20K 

or 44L. When the free baggage allowance is based on pieces, imprint ‘PC’ optionally 

preceded by the number of pieces, e.g. PC or 2PC. When the free baggage allowance 

is unknown, the free baggage allowance box shall also be blank. When the fare used 

does not permit any free baggage allowance, ‘NO’, ‘NIL’ or ‘XX’ shall be entered in the 

free baggage allowance box.
Attachment ‘B’

TRANSITIONAL AUTOMATED TICKET (TAT)

LINE SPECIFICATIONS –CHARACTER ALLOCATIONS

....

PRINT LINES G, H, I AND J

Print Position

....

(70–72)

Free Baggage Allowance

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 722a

OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT)

(amending)

PSC(33 34)722a Expiry: Indefinite

Type: A

T2.12/P

Attachment ‘B’

OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT)

LINE SPECIFICATIONS–CHARACTER ALLOCATIONS

....

PRINT LINES G, H, I AND J

Print Position

....

(70–72)

Free Baggage Allowance

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 722c

AUTOMATED TICKET/BOARDING PASS—VERSION 2 (ATB2)

(amending)

PSC(33 34)722c Expiry: Indefinite

Type: B

T2.12/P

RESOLVED that:

....

3.2.13 Baggage Information

3.2.13.1 Imprint the free baggage allowance amount followed by kilos ‘K’ or pounds ‘L’, 

e.g. 20K or 44L. When the free baggage allowance is based on pieces, imprint ‘PC’ 

optionally preceded by the number of pieces, e.g. PC or 2PC. When the free baggage 

allowance is unknown, the free baggage allowance box may also be blank. When the 

fare used does not permit any free baggage allowance, ‘NO’, ‘NIL’ or ‘XX’ shall be 

entered in the free baggage allowance box.

....

Attachment ‘B’

1.1 Flight Coupon

....

ATB2-PRINT LINE SPECIFICATIONS

...

Print-line Print Position Imprinted data Remarks

O 41–43 Free bBaggage allowance

....

Attachment ‘C

MASTER LIST- AUTOMATED TICKET/BOARDING PASS – ATB2

ATB2 MAGNETIC STRIPE ITEM NUMBERS, ELEMENT DESCRIPTIONS,

FIELD SIZES AND REFERENCE NUMBERS

....

Item no Element Description Field Size Reference No(s).

118 Free b Baggage allowance 3 59

MAGNETIC STRIPE LAYOUT-ATB2

FLIGHT COUPON - TRACK 3

(FORMAT CODE B)

....

Format Code 01 Free b Baggage allowance 118
MAGNETIC STRIPE SPECIFICATIONS – ATB2

BOARDING PASS/REBOARDING PASS (FORMAT CODE W)

....

Item No. Element Description Field Size Track 3 Block Reference Nos. 

118 Free b Baggage allowance 3 22 59

...

MAGNETIC STRIPE LAYOUT-ATB2

BOARDING/REBOADING PASS - TRACK 3

(FORMAT CODE W)

....

Format Code 01 Free b Baggage allowance 118

T2.20/P

Attachment ‘C’ – Master List – Automated Ticket/Boarding Pass – ATB2, Magnetic Strip

No. 1E Reason For Issuance of ATB2 Miscellaneous Charges Order (MCO): 

A Air transportation.

B Surface transportation.

C Bag shipped as cargo.

D Land arrangements for Inclusive Tour.

E Car hire.

F Sleeper/berth.

G Up-grading.

H Under collections.

I Taxes/fees/charges. 

J Deposits/down payments.

K Refundable Balances. 

L Hotel Accommodations.

M Sundry Charges Reservation Change Fees.

N Cancellation Fee.

O Other.

P Rebooking Fee Domestic (with taxes e.g. VAT

where applicable).

Q Rebooking Fee International.

R Lost Ticket Fee (charge for replacement). 

S Unaccompanied Minor Fee Domestic (with taxes 

e.g., VAT where applicable).

T Unaccompanied Minor Fee International. 

U Collection for Excess Baggage Charges. 

V-Z For individual airline use. 

1 Prepaid Ticket Advise (PTA)/Ticket on 

Departure (TOD). 

2-9 Reserved for future industry use. 

...

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 722f

ELECTRONIC TICKET — AIRLINE

(amending)

PSC(33 34)722f Expiry: Indefinite

Type: B

.....

Section 1 – Introduction/Scope

T2.8/P

1.6 Carriers shall participate in the Interline Data Exchange Centre (IDEC) for electronic 

interline billing and settlement of electronic flight coupons.

.....

T4

Section 6—Procedures

6.1 GENERAL

6.1.1 ISO currency codes shall be used as published in the IATA Airline Coding 

Directory. Data elements for amount fields shall apply decimal placement as defined for 

each currency code in the IATA Tariff Composite 024d Attachment A. Exception: 

Applicable during an EMU transition period; when it is advised that an EU Member State 

will be converting from a legacy currency to the euro ETs may show either the ISO 

currency code of the legacy national currency or the ISO currency code of the “euro” for 

the duration of the transition period. At the end of the transition period ETs may only be 

issued in euros.

....

T2.12/P

6.2 ISSUANCE

....

6.2.1 Electronic Ticket

....

6.2.1.7

....

Endorsements/Restrictions (including period of validity) (when present)

Free Baggage Allowance (Conditional)

Passenger Check-In Identification Type

(FOID)—Optional4

.....
6.3 Display

....

T2.5/P

6.3.6 If the result of a display request is multiple matching items, the carrier shall 

respond with a similar record list display response. 

....

T2.3/P

6.3.9 When a carrier receives a Display Request and the result is a single matching ET, 

the carrier shall ensure the actual coupons statuses are included in the response. For 

this purpose: 

6.3.9.1 Whenever If at least one coupon is in control of an interline partner, the carrier 

shall send a Display Request to the to each airline holding control of at least one 

coupon, except if the airline holding control is the sender of the initial display request 

message. 

6.3.9.2 Whenever If at least one coupon is in control of a Ground Handler, the carrier 

shall send a Display Request to the to each Ground Handler holding control of at least 

one coupon, as described in resolution 722h. 

6.3.9.3 In case the display is rejected or times out, coupon status 'A' shall be included in 

the response.

T2.9/P

Attachment ‘A’

ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS DATA ELEMENTS 

GLOSSARY

.....

ADDITIONAL BAGGAGE INFORMATION

(applicable to 722f/g/h only)

Information pertaining to the free baggage allowance which further defines the 

provisions around the baggage determination and type.

Allowable Baggage Types – 3 ALPHANUMERIC

(Repeatable field)

Defines the permitted baggage types by RFISC for the applicable baggage 

allowance.
Allowable Baggage Number of Types– 2 NUMERIC

(Repeatable field)

Defines the maximum number of each allowable baggage type.

Maximum Free Baggage Dimensions – 4 ALPHANUMERIC

When the baggage allowance is based on pieces, the maximum linear 

dimensions of the baggage followed by centimeters ‘C’ or inches ‘I’.

Maximum Free Baggage Weight – 3 ALPHANUMERIC

When the baggage allowance is based on pieces, the maximum baggage weight 

followed by kilos ‘K’ or pounds ‘L’, e.g. 23K or 50L.

Baggage Charge Types – 3 ALPHANUMERIC

(Repeatable field)

Defines the baggage charge types by RFISC for the applicable baggage charge. 

Baggage Charge Amount – 9 NUMERIC

(Repeatable field)

Defines the baggage charge amount which is applied to the 1st and 2nd checked 

baggage. 

Baggage Charge Amount Currency Code– 3 ALPHA

(Repeatable field)

This element shall contain the applicable three-character ISO currency code 

representing the currency for payment of a baggage charge. 

....

Carry-on Allowable Baggage Determining Carrier Code

– 3 ALPHANUMERIC

(Repeatable field)

Defines the determining carrier code of the applicable carry-on allowance 

baggage types.

Carry-on Allowable Baggage Types – 3 ALPHANUMERIC

(Repeatable field)

Defines the permitted baggage types by RFISC for the applicable carry-on

baggage allowance.

Carry-on Allowable Baggage Number of Types– 2 NUMERIC

(Repeatable field)

Defines the maximum number of each allowable baggage type

.....
FREE BAGGAGE ALLOWANCE—3 ALPHANUMERIC T2.12/P

The applicable free baggage allowance amount followed by kilos ‘K’ or pounds ‘L’, e.g. 

20K or 44L. When the free baggage allowance is based on pieces, the field may shall 

contain ‘PC’ optionally preceded by the number of pieces, e.g. PC or

2PC. When the free baggage allowance is unknown, the free baggage allowance field 

may also be blank. When the fare used does not permit any free baggage allowance, 

‘NO’, ‘NIL’ or ‘XX’ shall be entered in the free baggage allowance field.

(Note this will have to be re-positioned alphabetically)

T4

....

BASE FARE SELL AMOUNT5 —12 ALPHANUMERIC

....

_______

5

Exception: Applicable during an EMU transition period; when it is advised that an EU 

Member State will be converting from a legacy currency to the euro this data element 

may show either the ISO currency code of the legacy national currency or the ISO 

currency code of the euro.

....

EQUIVALENT FARE PAID NET AMOUNT5 —12 ALPHANUMERIC

....

EQUIVALENT FARE PAID NET AMOUNT5 —12 ALPHANUMERIC

....

EQUIVALENT FARE PAID SELL AMOUNT5—12 ALPHANUMERIC

5 Exception: Applicable during an EMU transition period; when it is advised that an EU 

Member State will be converting from a legacy currency to the euro this data element 

may show either the ISO currency code of the legacy national currency or the ISO 

currency code of the euro.

....

TOTAL TICKET/DOCUMENT AMOUNT5 —12 ALPHANUMERIC

....

_______

5

Exception: Applicable during an EMU transition period; when it is advised that an EU 

Member State will be converting from a legacy currency to the euro this data element 

may show either the ISO currency code of the legacy national currency or the ISO 

currency code of the euro.

.....

T2.4/P

REISSUED FLOWN FLIGHT COUPON DATA

(Repeatable field)

A series of data elements representing sold data for coupons that have been flown from 

a previously reissued ticket. This data set is repeated for every flown coupon and 

carried forward for every reissue transaction and is comprised of the following data 

elements:

....
Reissued Flown Ticket Designator

....

Reissued Flown Ticket Date of Issue – 7 ALPHANUMERIC

(applicable to 722f/g/h, 20.60/20.61/20.62)

‘Date of issue’ of a ticket that represents sold data for coupons that have been 

flown from a previously reissued ticket. Format DDMMMYY.

Reissued Flown Ticket/Document Number – 14 ALPHANUMERIC

(applicable to 722f/g/h, 20.60/20.61/20.62)

‘Ticket/document Number’ that represents sold data for coupons that have been 

flown from a previously reissued ticket. See glossary definition for 

‘TICKET/DOCUMENT NUMBER’.

.....

T2.19/P

ROUTING DOM/INT INDICATOR — 1 ALPHA

Used for domestic or international routing differentiation of the sold document; “D” or “I” 

should be inserted in the first character position. 

For tickets, EMD-A and EMD-S with routing:

• If the document routing is Domestic (all board and off point within the same 

country), value should be “D”.

• If the document routing is International (all board and off point not within the 

same country), value should be “I”.

For EMD-S with no routing:

• If the EMD-S has no routing attached, value should be blank.

.....

T2.21/P

SOURCE OF APPROVAL CODE (CREDIT CARD) — 1 ALPHANUMERIC

This code identifies how the approval code for a credit card sale was obtained. Valid 

codes are:

Blank = No approval code obtained/reported

C = Credit authorization is issued by a credit card company or via a direct link with the 

company of a designated provider of authorizations

F = Approval code assigned by a CRS using floor limits

M = Approval code obtained by the agent and entered manually

S = Approval code assigned by credit card company and Automatically by the CRS

.....
T2.14/P

STATISTICAL CODE — 3 ALPHANUMERIC

For tickets:

Used for domestic or international sales differentiation; “D” or “I” should be inserted in 

the first character position. For self-sale transactions, the “D” or “I” shall be followed by 

“/S”.

• If the ticket itinerary is Domestic and the point of sale is within the country of the 

itinerary, value should be “D”.

• If the ticket itinerary is Domestic and the point of sale is outside of the country of 

the itinerary, value should be “I”.

• If the ticket itinerary is International, value should be “I”.

For EMD-A:

Used for domestic or international sales differentiation; “D” or “I” should be inserted in 

the first character position.

• If EMD-A coupons routing is domestic (all board points and off points within the 

same country) and the point of sale is within the country of the routing, value 

should be “D”.

• If EMD-A coupons routing is domestic (all board points and off points within the 

same country) and the point of sale is outside of the country of the routing, value 

should be “I”. 

• If EMD-A coupons routing is international, value should be “I”.

For EMD-S:

Used for domestic or international sales differentiation; “D” or “I” should be inserted in 

the first character position.

• If the EMD-S has a routing, the same rule than for EMD-A applies.

• If the EMD-S has no routing attached, value should be blank.
Attachment ‘B’

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – AIRLINE 

MESSAGES

T2.4/P

Element Description

Transaction No. 

Char,

A, N, 

or A/N

Display Unsolicited 

Airport 

Control

History 

Display

Request 

Airport 

Control

Change of 

Status

Redirect 

Airport 

Control

Reservation 

Change

Emergency 

Lock

System 

Update

Resolution 

722f/20.60

Req Res Req Res Req Res Req Res Req Res Req Res Req Res Req Res Req Res

Reissued 

Flown Ticket 

Designator

15 A/N C C C

Reissued 

Flown 

Ticket/Docume

nt Number

14 A/N C C C

Reissued 

Flown Ticket 

Date of Issue

7 A/N C C C

T2.9/P

ELEMENT 

DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

DISPLAY UNSOLICITED 

AIRPORT 

CONTROL 

(INF4MATION –

A4A ONLY)

HISTORY 

DISPLAY

REQUEST 

AIRPORT 

CONTROL

CHANGE OF 

STATUS

REDIRECT 

AIRPORT 

CONTROL

RESERVATION 

CHANGE

EMERGENCY 

LOCK

SYSTEM 

UPDATE

Action Code ---> D, J T (I – A4A ONLY H B C N A M U

RESOLUTION 722 f 

/20.60

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Allowable Baggage 

Types

3 A/N O O O

Allowable Baggage 

Number of Types

2 N O O O

Maximum Free 

Baggage Dimensions

4 A/N O O O

Maximum Free 

Baggage Weight

3 A/N O O O

Baggage Charge Types 3 A/N O O O

Baggage Charge 

Amount

9N O O O

Baggage Charge 

Amount Currency Code

3A/N O O O

Carry-on Allowable 

Baggage Types

3A/N O O O

Carry-on Allowable 

Baggage Number of 

Types

2 N O O O

Carry-on Baggage 

Allowance Determining 

Carrier Code

3 A/N O O O

...
T2.10/P

ELEMENT 

DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

DISPLAY UNSOLICITED 

AIRPORT 

CONTROL 

(INFORMATION 

– ATA ONLY)

HISTORY 

DISPLAY

REQUEST 

AIRPORT 

CONTROL

CHANGE 

OF STATUS

REDIRECT 

AIRPORT 

CONTROL

RESERVATION 

CHANGE

EMERGENCY 

LOCK

SYSTEM 

UPDATE

Action Code --

->

D, J T (I – ATA 

ONLY

H B C N A M U

RESOLUTION 

722 f

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Baggage 

Determining 

Carrier Code

3 A/N O C O C O C

...

T2.19/P

ELEMENT 

DESCRIPTION

Transaction NO CHAR.

A, N 

OR A/N

DISPLAY

UNOLICITED 

AIRPORT 

CONTROL

HISTORY 

DISPLAY

REQUEST 

AIRPORT 

CONTROL

CHANGE OF 

STATUS

REDIRECT 

AIRPORT 

CONTROL

RESERVATION 

CHANGE

EMERGENCY 

LOCK

SYSTEM 

UPDATE

Action code -> D,J T (I-ATA only) H B C N A M U

RESOLUTION 722f REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Routing dom/int 

indicator 1A

...

T2.6/P

ELEMENT DESCRIPTION

Transaction

NO CHAR

A, N OR A/N

SYSTEM

UPDATE

Action code ---> U

RESOLUTION 722F/20.60 REQ RESP

...

In Connection With Coupon Number 1 N M

In Connection With Document Number 14 A/N M

In Connection With Qualifier 1 N CM

......

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 722g

ELECTRONIC TICKET — NEUTRAL

(amending)

PSC(33 34)722g Expiry: Indefinite

Type: B

T2.5/P

....

5.5 MESSAGES 

....

5.5.3.1 Display — Request to Validating Carrier to retrieve data elements necessary to 

display the complete record of the ET. Response provides data elements necessary to 

display this complete record, or display a similar name record list or denies the request.

....

T4

Section 6—Procedures

6.1 GENERAL

6.1.1 ISO currency codes shall be used as published in the IATA Airline Coding 

Directory. Data elements for amount fields shall apply decimal placement as defined for 

each currency code in the IATA Tariff Composite 024d Attachment A. Exception: 

Applicable during an EMU transition period; when it is advised that an EU Member State 

will be converting from a legacy currency to the euro ETs may show either the ISO 

currency code of the legacy national currency or the ISO currency code of the “euro” for 

the duration of the transition period. At the end of the transition period ETs may only be 

issued in euros.

.....

T2.12/P

6.2 ISSUANCE

....

6.2.3 Electronic Ticket

....

6.2.3.8

....

Endorsements/Restrictions (including period of validity) (when present)

Free Baggage Allowance (Conditional)

Passenger Check-In Identification Type

(FOID)—Optional3

.....
6.3 DISPLAY 

....

T2.18/P

6.3.3 An ET shall only be displayed to the issuing agent or an accredited branch 

location of the issuing agent, identified by Agent Numeric Code, irrespective of the 

CRS/System Provider generating the request. .

6.3.3.1 When an ET originally issued by an agent has been exchanged/reissued by the 

original validating carrier, it may subsequently be displayed by the original agent or an 

accredited branch location when authorized by that original validating carrier.

T2.5/P

6.3.4 The primary search criterion to display an ET is the Ticket/Document Number. 

....

6.3.7 If the result of a display request is multiple matching items, the carrier shall 

respond with a similar record list display response. 

6.3.7 6.3.8 When the passenger's name is used for display, the passenger's surname 

(family name) display request message shall contain a minimum of the first two 

characters and optionally the given (first) name and title of the passenger. 

6.3.8 6.3.9 When a carrier receives a Display Request and the result is a single 2.3&5/P

matching ET, the carrier shall ensure the actual coupons statuses are included in the 

response. For this purpose: 

T2.3/P

6.3.8.1 6.3.9.1 Whenever If at least one coupon is in control of an interline partner, the 

carrier shall send a Display Request to the to each airline holding control of at least one 

coupon, as described in Resolution 722f. 

6.3.8.2 6.3.9.2 Whenever If at least one coupon is in control of a Ground Handler, the 

carrier shall send a Display Request to the to each Ground Handler holding control of at 

least one coupon, as described in resolution 722h.

6.3.8.3 6.3.9.3 In case the display is rejected or times out, coupon status 'A' shall be 

included in the response.

.....
T2.18/P

6.6 EXCHANGE/REISSUE

...

6.6.12 An ET shall only be exchanged/reissued by the issuing agent or an accredited 

branch location of the issuing agent, identified by Agent Numeric Code, irrespective of 

the CRS/System Provider generating the request. .

6.6.12.1 When an ET originally issued by an agent has been exchanged/reissued by the 

original validating carrier, it may subsequently be exchanged/reissued by the original 

agent or an accredited branch location when authorized by that original validating 

carrier.

.....

6.8 REFUND

...

6.8.4 An ET shall only be refunded by the issuing agent or an accredited branch 

location of the issuing agent, identified by Agent Numeric Code, irrespective of the 

CRS/System Provider generating the request. .

6.8.4.1 When an ET originally issued by an agent has been exchanged/reissued by the 

original validating carrier, it may subsequently be refunded by the original agent or an 

accredited branch location when authorized by that original validating carrier.
Attachment ‘B’

ELECTRONIC TICKET MESSAGE CONSTRUCTION MATRIX – NEUTRAL 

MESSAGES

T2.9/P

ELEMENT DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

ISSUANCE

(INFORMATION 

– ATA ONLY)

DISPLAY HISTORY 

DISPLAY

EXCHANGE/

REISSUE

REFUND RESERVATIONS 

CHANGE

SYSTEM 

CANCEL

REFUND 

CANCEL

VOID

Action Code ---> S(I-ATA ONLY) D H E R A X,Y Z V,W

RESOLUTION 722 G/20.61 REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Allowable Baggage Types 3 A/N O O O O

Allowable Baggage Number 

of Types

2 N O O O O

Maximum Free Baggage 

Dimensions

4 A/N O O O O

Maximum Free Baggage 

Weight

3 A/N O O O O

Baggage Charge Types 3A/N O O O O

Baggage Charge Amount 9N O O O O

Baggage Charge Amount 

Currency Code

3A O O O O

Carry-on Allowable Baggage 

Types

3A/N O O O O

Carry-on Allowable Baggage

Number of Types

2N O O O O

Carry-on Baggage Allowance 

Determining Carrier Code 

3A/N O O O O

...

T2.10/P

ELEMENT 

DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

ISSUANCE

(INFORMATION 

– ATA ONLY)

DISPLAY HISTORY 

DISPLAY

EXCHANGE/

REISSUE

REFUND RESERVATIONS 

CHANGE

SYSTEM 

CANCEL

REFUND 

CANCEL

VOID

Action Code --

->

S(I-ATA ONLY) D H E R A X,Y Z V,W

RESOLUTION 

722 G

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Baggage

Determining 

Carrier Code

3 A/N O C O C O C O C

...
T2.19/P

ELEMENT 

DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

ISSUANCE DISPLAY HISTORY 

DISPLAY

EXCHANGE/

REISSUE

REFUND SYSTEM 

CANCEL

REFUND 

CANCEL

VOID

Action Code --

->

S D H E R X,Y Z V,W

RESOLUTION 

722g

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Routing 

dom/int 

indicator

1A O C O C C

...

T2.4/P

Element Description

Transaction No. 

Char

,

A, N, 

or 

A/N

Issuance Display History 

Display

Exchange/

Reissue

Refund Reservatio

n Change

System 

Cancel

Refund 

Cancel

VOID

Resolution 

722g/20.61

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Re

q

Re

s

Reissued 

Flown Ticket 

Designator

15 

A/N

C C C

Reissued 

Flown 

Ticket/Docume

nt Number

14 

A/N

C C C

Reissued 

Flown Ticket 

Date of Issue

7 

A/N

C C C

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 722h

ELECTRONIC TICKET — GROUND HANDLING

(amending)

PSC(33 34)722h Expiry: Indefinite

Type: B

.....

Section 6 – Procedures

T2.12/P

6.1 GENERAL

....

6.1.4

....

Endorsements/Restrictions (including period of validity) (when present)

Free Baggage Allowance (Conditional)

Passenger Check-In Identification Type

(FOID)—Optional4

T2.3/P & T2.5/P

....

6.2 Display

....

....

6.2.3 The primary search criterion to display an ET is the Ticket/Document Number.

....

6.2.6 If the result of a display request is multiple matching items, the carrier shall 

respond with a similar record list display response. 

....

6.2.11 When a Ground Handler receives a Display Request and finds a match for an ET

the result is a single matching ET, the Ground Handler shall include in the response the 

actual coupons statuses in the response for all the coupons of which it holds the control. 
Attachment ‘B’

MESSAGE CONSTRUCTION MATRIX – GROUND HANDLING

T2.9/P

ELEMENT DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

DISPAY AIRPORT 

CONTROL 

REQUEST –

GROUND 

HANLDLING)

CHANGE OF 

STATUS

REDIRECT EMERGENCY 

LOCK

UNSOLICITED 

AIRPORT 

CONTROL –

GROUND 

HANDLING

SYSTEM 

UPDATE

Action Code ---> D G C N M K U

Resolution 722 h REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Allowable Baggage Types 3 A/N O O O

Allowable Baggage Number of Types 2 N O O O

Maximum Free Baggage Dimensions 4 A/N O O O

Maximum Free Baggage Weight 3 A/N O O O

Baggage Charge Types 3A/N O O O

Baggage Charge Amount 9N O O O

Baggage Charge Amount Currency 

Code

3A O O O

Carry-on Allowable Baggage Types 3A/N O O O

Carry-on Allowable Baggage Number 

of Types

2N O O O

Carry-on Baggage Allowance 

Determining Carrier Code

3A/N O O O

...

T2.10/P

ELEMENT DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

DISPAY AIRPORT 

CONTROL 

REQUEST –

GROUND 

HANLDLING)

CHANGE OF 

STATUS

REDIRECT EMERGENCY 

LOCK

UNSOLICITED 

AIRPORT 

CONTROL –

GROUND 

HANDLING

SYSTEM 

UPDATE

Action Code ---> D G C N M K U

Resolution 722 h REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Baggage Determining 

Carrier Code

3 A/N O C O C O C

...
T2.7/P

....

ELEMENT DESCRIPTION

Transaction NO. 

CHAR’ 

A, N 

OR A/N

DISPLAY AIRPORT 

CONTROL 

REQUEST –

GROUND 

HANDLING

CHANGE 

OF STATUS

REDIRECT 

AIRPORT 

CONTROL

EMERGENCY 

LOCK

UNSOLICITE

D AIRPORT 

CONTROL –

GROUND 

HANDLING

SYSTEM 

UPDATE

Action Code ---> D G C N M K U

RESOLUTION 722h REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

...

Coupon Number 1 N M

...

Document Type 1 A M

...

In Connection With Coupon Number 1 N M

In Connection With Document 

Number

14 A/N M

In Connection With Qualifier 1 N M

...

Number of Ticket/Document 

Numbers

2 N M

...

Response Comments 64 A/N O

...

Ticket Issuance Originator Code 1 A/N

Ticket/Document Number 14 A/N M

Ticket Type Indicator 3 A/N

...

Transaction Action 1 A M

Transaction Agent I.D. 11 A/N M

...

...

T2.4/P

Element Description

Transaction No. 

Char,

A, N, or 

A/N

Display Airport Control 

Request -

Ground Handling

Change of 

Status

Redirect Airport 

Control

Emergency Lock Unsolicited Airport 

Control – Ground 

Handling

Resolution 

722h/20.62

Req Res Req Res Req Res Req Res Req Res Req Res

Reissued Flown 

Ticket Designator

15 A/N

Reissued Flown 

Ticket/Document 

Number

14 A/N

Reissued Flown 

Ticket Date of Issue

7 A/N

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 725a

MISCELLANEOUS CHARGES ORDER (MCO) – ISSUANCE AND HONOURING 

PROCEDURES BY MEMBER

(amending)

PSC(33 34)725a Expiry: Indefinite

Type: B

T2.20/P

RESOLVED that:

Members may use the Miscellaneous Charges Order (MCO) form as described in 

Resolution 725 to cover collections for such services as air or surface transportation, 

excess baggage charges, baggage shipped as cargo, land arrangements for inclusive 

tours, car hire, superior air or surface accommodations, extra fares, additional 

collections in connection with upgradings or under collections, taxes/fees/charges, 

deposits, down payments, sundry charges reservation change fees as provided in 

Resolution 727a, refundable balances, hotel accommodations, and to cover collection 

for a Prepaid Ticket Advice (PTA) as provided in Resolution 731. The MCO shall not be 

used for transmittal of funds only. When issuing and honoring MCOs, Members shall 

apply the following procedures. 

.....

T4

2.2 ENTRIES

....

2.2.3 “Value for Exchange” Boxes

....

2.2.3.2 “CURRENCY”. Enter applicable IATA currency code;.

Exception: Applicable during an EMU transition period. When it is advised that an EU 

Member State will be converting from a legacy currency to the euro the “Currency” box 

may show either the ISO currency code of the legacy national currency or the ISO 

currency code of the “euro” during the transition period.

.....

2.2.5 “Equivalent Amount Paid” Box

When payment is in a currency other than that shown in the “Value for Exchange” 

boxes, or in a currency other than the national currency of the country of sale enter the 

exchange value in the currency actually collected, preceded by the applicable IATA 

currency code. Exception: Applicable during an EMU transition period. When it is 

advised that an EU Member State will be converting from a legacy currency to the euro 

such country may have dual expression of the legacy currency and the euro.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 725b

MISCELLANEOUS CHARGES ORDER (MCO) – ISSUANCE AND HONOURING 

PROCEDURES (AGENTS)

(amending)

PSC(33 34)725b Expiry: Indefinite

Type: B

T2.20/P

RESOLVED that:

Members may use for issuance by approved Passenger Sales Agents, the 

Miscellaneous Charges Order (MCO) form as described in Resolution 725 to cover 

collections for a Prepaid Ticket Advice (PTA) as provided in Resolution 731 and 

collections for specified services such as air or surface transportation (including 

combination with air transportation), excess baggage charges (whether rated as 

baggage or cargo), land arrangements for inclusive tours, car hire, surface 

accommodations, taxes/fees/charges, deposits, down payments, sundry charges 

reservation change fees as provided in Resolution 727a, and hotel accommodations. 

When issued for a PTA, the MCO shall not be used for transmittal of funds only. The 

MCO shall not be issued for unspecified air transportation. When issuing and honoring 

MCOs, Agents shall apply the following procedures. 

.....

T4

2.2 ENTRIES

....

2.2.3 “Value for Exchange” Boxes

....

2.2.3.2 “CURRENCY”. Enter applicable IATA currency code.

Exception: Applicable during an EMU transition period. When it is advised that an EU 

Member State will be converting from a legacy currency to the euro the “Currency” box 

may show either the ISO currency code of the legacy national currency or the ISO 

currency code of the “euro” during the transition period.

....

2.2.5 “Equivalent Amount Paid” Box

When payment is in a currency other than that shown in the “Value for Exchange” 

boxes, or in a currency other than the national currency of the country of sale enter the 

exchange value in the currency actually collected, preceded by the applicable IATA 

currency code. Exception: Applicable during an EMU transition period: when it is 

advised that an EU Member State will be converting from a legacy currency to the euro 

such country may have dual expression of the legacy currency and the euro for the 

duration of the transition period.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 725f

ELECTRONIC MISCELLANEOUS DOCUMENT — AIRLINE

(amending)

PSC(33 34)725f Expiry: Indefinite

Type: B

.....

Section 6—Procedures

6.1 GENERAL

....

T4

6.1.1 ISO currency codes shall be used as published in the IATA Airline Coding 

Directory. Data elements for amount fields shall apply decimal placement as defined for 

each currency code in the IATA Tariff Composite 024d Attachment A. Exception: 

Applicable during an EMU transition period; when it is advised that an EU Member State 

will be converting from a legacy currency to the euro EMDs may show either the ISO 

currency code of the legacy national currency or the ISO currency code of the ‘euro’ for 

the duration of the transition period. At the end of the transition period EMDs may only 

be issued in euros.

.....

6.4 Display

....

T2.5/P

6.4.6 If the result of a display request is multiple matching items, the carrier shall 

respond with a similar record list display response. 

T2.3/P

6.4.7 When a carrier receives a 'Display' request and finds a match for an EMD for 

which neither the receiving carrier nor the requesting carrier is the Validating Carrier, 

the response may include the Airline Designator(s) of the Validating Carrier(s) as a 

"Response Comments". 

6.4.8 When the form of payment is credit card, the Form of Payment Credit Card 

Account Number shall not be included in the Display Response message. 

6.4.9 When a carrier receives a Display Request and the result is a single matching 

EMD, the carrier shall ensure the actual coupon status is included in the response. For 

this purpose: 
6.4.9.1 Whenever a If at least one coupon is in control of an interline partner, the carrier 

shall send a one Display Request to the to each airline holding control of at least one 

coupon, except if the airline holding control is the sender of the initial display request 

message.

6.4.9.2 Whenever a If at least one coupon is in control of a Ground Handler, the carrier 

shall send a one Display Request to the to each Ground Handler holding control of at 

least one coupon, as described in resolution 725h. 

6.4.9.3 In case the display is rejected or times out, coupon status 'A' shall be included in 

the response.
Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION 

MATRIX – AIRLINE MESSAGES

T2.16/P

ELEMENT DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

UNSOLICITED 

BILLING

Transaction Action Code ---> L

RESOLUTION 725 f/20.63 REQ RESP

...

Additional Services Attribute Group 3 A/N O

Additional Services Attribute Sub-Group 3 A/N O

...

Additional Services Industry Carrier Indicator 1 A/N O

...

Additional Services Service Type 1 A/N O

...

T2.6/P

ELEMENT DESCRIPTION

Transaction

NO CHAR

A, N OR A/N

SYSTEM

UPDATE

Action code ---> U

725f/20.63 REQ RESP

...

In Connection With Coupon Number 1 N CM

In Connection With Document Number 14 A/N M

In Connection With Qualifier 1 N M

......
T2.17/P

....

ELEMENT DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

UNSOLICITED 

BILLING

Action Code ---> L

RESOLUTION 725 f/20.63 REQ RESP

...

Product Characteristic Type 35 A/N O

Product Characteristic Value 70 A/N O

...

T2.4/P

Element Description

Transaction No. Char,

A, N, or 

A/N

Display Request Airport Control Change of Status System Update

Resolution 725f Req Res Req Res Req Res Req Res

Reissued Flown Stopover Code 1 A C C

Reissued Flown Ticket/Document 

Number

14 A/N C C

Reissued Flown Ticket/Document 

Date of Issue

7 A/N C C

T2.19/P

ELEMENT DESCRIPTION

Transaction NO CHAR.

A, N OR A/N DISPLAY REQUEST AIRPORT CONTROL CHANGE OF STATUS SYSTEM UPDATE

Action code -> D B C U

RESOLUTION 725f REQ RESP REQ RESP REQ RESP REQ RESP

...

Routing dom/int indicator 1A

...

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 725g

ELECTRONIC MISCELLANEOUS DOCUMENT — NEUTRAL

(amending)

PSC(33 34)725g Expiry: Indefinite

Type: B

.....

T2.13/P

3.5 DATA ELEMENTS - The components of PADIS messages. The following 

messages are defined in this Resolution: 

....

- System Cancel Message

- System Update Message

- Void Message

....

5.5 MESSAGES

....

5.5.3.9 System Update - A Request from an agent to the validating carrier to associate 

an EMD-A coupon(s) to an ET coupon. Response either acknowledges or denies the 

request. 

...

Section 6—Procedures

....

6.1 GENERAL

....

T4

6.1.1 ISO currency codes shall be used as published in the IATA Airline Coding 

Directory. Data elements for amount fields shall apply decimal placement as defined for 

each currency code in the IATA Tariff Composite 024d Attachment A. Exception: 

Applicable during an EMU transition period; when it is advised that an EU Member State 

will be converting from a legacy currency to the euro EMDs may show either the ISO 

currency code of the legacy national currency or the ISO currency code of the ‘euro’ for 

the duration of the transition period. At the end of the transition period EMDs may only 

be issued in euros.

....
6.3 Display

T2.3/P & T2.5/P

....

6.3.7 If the result of a display request is multiple matching items, the carrier shall 

respond with a similar record list display response. 

....

6.3.7 6.3.8 When the passenger's name is used for display, the passenger's surname 

(family name) display request message shall contain a minimum of the first two 

characters and optionally the given (first) name and title of the passenger. 

6.3.8 6.3.9 When a carrier receives a Display Request and the result is a single 

matching EMD, the carrier shall ensure the actual coupon status is included in the 

response. For this purpose: 

6.3.8.1 6.3.9.1 Whenever a If at least one coupon is in control of an interline partner, 

the carrier shall send a one Display Request to the to each airline holding control of at 

least one coupon, as described in Resolution 725f. 

6.3.8.2 6.3.9.2 Whenever a If at least one coupon is in control of a Ground Handler, the 

carrier shall send a one Display Request to the to each Ground Handler holding control 

of at least one coupon, as described in resolution 725h. 

6.3.8.3 6.3.9.3 In case the display is rejected or times out, coupon status 'A' shall be 

included in the response.

.....

T2.13/P

6.10 SYSTEM UPDATE

6.10.1 Association initiated by the CRS/System Provider of EMD-A

6.10.1.1 An agency may associate an EMD-A issued by the issuing agency or an 

accredited branch if authorized by the Validating Carrier. 

6.10.1.2 Prior to initiating a "System Update" message for association the CRS/System 

Provider shall verify that the EMD-A value coupons to be associated are not in final 

status, the operating carrier is the same and the same board and off points including 

multi-airports within the same metropolitan area are present in the same order as in the 

ET record to which the EMD-A will be associated and that the name of the passenger 

matches that of the passenger in the associated ET and that the EMD-A which has 

been previously issued, is used for the identical service.

6.10.1.3 The Validating Carrier of the EMD-A and each of the Operating Carrier shall be 

the same. 

6.10.1.4 Upon receipt of the System Update message from the CRS/System Provider of 

the EMD-A, the validating carrier of the ET shall update the ET record with the in 

connection with Document number and the in the connection Coupon number and 

amend the in Connection With Qualifier to indicate that the EMD-A is associated. 

....
Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENT CONSTRUCTION MATRIX –

NEUTRAL MESSAGES

T2.4/P

Element Description

Transaction No. 

Char,

A, N, 

or A/N

Issuance Display History 

Display

Exchange/

Reissue

Refund System 

Cancel

Refund 

Cancel

VOID

Resolution 722g Req Res Req Res Req Res Req Res Req Res Req Res Req Res Req Res

Reissued Flown 

Ticket Designator

15 

A/N

C C C

Reissued Flown 

Ticket/Document 

Number

14 

A/N

C C C

Reissued Flown 

Ticket/Document 

Date of Issue

7 A/N C C C

T2.13/P

Data Element

Characters

A N, OR A/N

System Update

Transaction Action Code U

RESOLUTION 725g/20.64 REQ RESP

....

Coupon Number 1 N M

....

Document Type 1 A M

....

In Connection With Coupon Number 1 N M

In Connection With Document Number 14 A/ N M

In Connection With Qualifier 1 N M

....

Number of Ticket/Document Numbers 2 N M

....

Response Comments 64 A/N O

....

Ticket/Document Number 14 A/N M

....

Transaction Action 1 A M

Transaction Agent I.D. 11 A/N M

....
T2.19/P

ELEMENT 

DESCRIPTION

Transaction CHAR. 

A, N 

OR 

A/N

ISSUANCE DISPLAY HISTORY 

DISPLAY

EXCHANGE/

REISSUE

REFUND SYSTEM 

CANCEL

REFUND 

CANCEL

VOID

Action Code ---> S D H E R X,Y Z V,W

RESOLUTION 

725gG

REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Routing dom/int 

indicator

1A O C O C C

...

T7

ELEMENT DESCRIPTION

Transaction

NO

CHAR. 

A, N 

OR 

A/N

ISSUANCE

(INFORMAT

ION – ATA 

ONLY)

DISPLAY HISTORY 

DISPLAY

EXCHANGE/

REISSUE

REFUND SYSTEM 

CANCEL

REFUND 

CANCEL

VOID

Action Code ---> S (I-ATA only) D H E R X,Y Z V,W

RESOLUTION 20/64 / 725g REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP

...

Remarks 70 A/N C C C C C

...

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 725h

ELECTRONIC MISCELLANEOUS DOCUMENT — GROUND HANDLING

(amending)

PSC(33 34)725h Expiry: Indefinite

Type: B

.....

Section 6 – Procedures

....

6.2 Display

....

T2.5/P

6.2.5 If the result of a display request is multiple matching items, the carrier shall 

respond with a similar record list display response. 

....

6.2.9 The Ground Handler may include the Validating Carrier in a Display Request to 

the Operating Carrier. Upon receiving the Display Request, the Operating Carrier shall 

then send its own Display Request to the specified Validating Carrier. On receipt of the 

response from the validating Carrier, the Operating Carrier shall then forward this to the 

Ground Handler. 

6.2.10 When the Display Request is initiated by the Operating Carrier to the Ground 

Handler, Transaction Action ‘J’ shall be used. 

6.2.11 When the form of payment is credit card, the form of payment credit card account 

number shall not be included in the response message. 

T2.3/P & T2.5/P

6.2.12 When a Ground Handler receives a Display Request and finds a match for an 

EMD the result is a single matching EMD, the Ground Handler shall include in the 

response the actual coupons statuses in the response for all the coupons of which it 

holds the control.
Attachment ‘B’

ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION 

MATRIX – GROUND HANDLING

T2.6/P

ELEMENT DESCRIPTION

Transaction

NO CHAR

A, N OR A/N

SYSTEM

UPDATE

Action code ---> U

RESOLUTION 725h/20.66 REQ RESP

...

In Connection With Coupon Number 1 N CM

In Connection With Document Number 14 A/N M

In Connection With Qualifier 1 N M

......

T2.4/P

Element Description

Transaction No. Char,

A, N, or A/N

Display Airport Control Request -

Ground Handling

Change of Status System Update

Resolution 722h Req Res Req Res Req Res Req Res

Reissued Flown Ticket Designator 15 A/N

Reissued Flown Ticket/Document 

Number

14 A/N

Reissued Flown Ticket/Document Date 

of Issue

7 A/N

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RESOLUTION 726a

MULTIPLE PURPOSE DOCUMENT (MPD)—CARRIER, CARBONISED,

AUTOMATED

(amending)

PSC(33 34)726a Expiry: Indefinite

 Type: B

T4

.....

2.2 ENTRIES

....

2.2.1 Fixed Area

....

2.2.1.11 “Fare/Charges” Box

Imprint, right justified, the amount of fare or charges (excluding taxes/fees/charges) 

immediately preceded by the applicable currency code. If the Fare/Charges amount 

(excluding taxes/fees/charges) is greater than the space available the currency code 

may be omitted. 

Imprint the applicable IATA currency code. Exception: Applicable during an EMU 

transition period; when it is advised that an EU Member State will be converting from a 

legacy currency to the euro the “Fare/Charges” box may show either the ISO currency 

code of the legacy national currency or the ISO currency code of the “euro” during the 

transition period. At the end of the transition period MPDs may only be issued in euros.

2.2.1.12 “Equivalent Amount/Fare Paid” Box

If payment is made in a currency other than that shown in the “Fare/Charges” box, 

imprint, right justified, the equivalent amount paid for the fare or charges immediately 

preceded by the applicable currency code. If the Fare/Charges amount (excluding tax) 

is greater than the space available the currency code may be omitted. Applicable during 

an EMU transition period: when it is advised that an EU Member State will be converting 

from a legacy currency to the euro such country may have dual expression of the legacy 

currency and the euro for the duration of the transition period.

....

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 726e

MULTIPLE PURPOSE DOCUMENT (MPD)—NEUTRAL, CARBONISED,

MANUAL

(amending)

PSC(33 34)726e Expiry: Indefinite

 Type: B

T4

.....

2.2 ENTRIES

2.2.1 Fixed (pre-format) Area

....

2.2.1.11 “Fare/Charges” Box

Enter the amount of fare or charges (excluding taxes/fees/charges (TFCs)) preceded by 

the applicable currency code.

Exception: Applicable during an EMU transition period; when it is advised that an EU 

Member State will be converting from a legacy currency to the euro the “Fare/Charges” 

box may show either the ISO currency code of the legacy national currency or the ISO 

currency code of the “euro” during the transition period. At the end of the transition 

period MPDs may only be issued in euros.

2.2.1.12 “Equivalent Amount/Fare Paid” Box

If payment is made in a currency other than that shown in the “Fare/Charges” box, enter 

the equivalent amount paid for the fare or charges preceded by the applicable

currency code.

2.2.1.12.1 Exception: Only for EMU countries during the euro transition period 01 

January 1999—31 December 2001; (Paragraph 2.2.1.12.1 will expire on 1 January

2002).

2.2.1.12.2 During this period the EMU countries will have dual expressions of the same 

currency. If a euro amount is shown in the “AMOUNT IN LETTERS” and “AMOUNT IN 

FIGURES” boxes, and payment is made in another EMU country in euro, no entry shall 

be made in the “EQUIVALENT AMOUNT PAID” box. (Paragraph 2.2.1.12.2 will expire 

on 1 January 2002).

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 726f

MULTIPLE PURPOSE DOCUMENT (MPD)—CARRIER, CARBONISED, MANUAL

(amending)

PSC(33 34)726f Expiry: Indefinite

Type: B

T4

.....

2.2 ENTRIES

2.2.1 Fixed (pre-format) Area

....

2.2.1.10 “Fare/Charges” Box

Enter the amount of fare or charges (excluding taxes/fees/charges) preceded by the 

applicable currency code.

Exception: Applicable during an EMU transition period; when it is advised that an EU 

Member State will be converting from a legacy currency to the euro the “Fare/Charges” 

box may show either the ISO currency code of the legacy national currency or the ISO

currency code of the “euro” during the transition period. At the end of the transition 

period MPDs may only be issued in euros.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 727

TICKETS—ALTERATIONS TO FLIGHT COUPONS

(amending)

PSC(33 34)727 Expiry: Indefinite

Type: B

RESOLVED that:

T2.12/P

.....

2.5 If the change in the reservations entry being made by use of a sticker affects the 

free baggage allowance, if shown, alter the “Allow” box(es) in the following manner:

Strike out the original entry and enter the new allowance immediately above or below as 

space permits, or in the “Endorsements/Restrictions” box of the applicable flight

coupon(s) and the passenger coupon. 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 728

CODE DESIGNATORS FOR PASSENGER TICKET AND BAGGAGE CHECK

(amending)

PSC(33 34)728 Expiry: Indefinite

Type: B

P2.1

....

7. FORM OF PAYMENT CODE (mandatory)

....

International Payment Cards

Diners Club DC

China UnionPay UP

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 735

PERIOD OF VALIDITY

(amending)

PSC(32 34)735 Expiry: Indefinite

Type: B

T2.1/P

....

Example 1: For a totally unused ticket issued 08JUN10 08JUN11 when such ticket is 

presented for exchange on 06JUN11 06JUN12 for travel commencing 07JUN11

07JUN12, such ticket will have a validity of 07JUN12 07JUN13 based on the new date 

of commencement of travel for a ticket with a one year validity.

Example 2: For a totally unused ticket issued 08JUN10 08JUN11 with a one year 

validity when such ticket is presented for exchange on 09JUN11 09JUN12 for travel 

commencing 10JUN11 10JUN12, such ticket is expired and may no longer be accepted 

for further exchange.

Example 3: Totally unused ticket issued 08JUN11 with a one year validity. When such 

ticket is presented for exchange on 08JUN12 for travel commencing 12OCT12, such 

ticket will have a validity of 12OCT13 based on the new date of commencement of 

travel for a ticket with a one year validity.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 735d

INVOLUNTARY CHANGE OF CARRIER, ROUTING, CLASS OR TYPE OF FARE

(amending)

PSC(33 34)735d Expiry: Indefinite

Type: B

RESOLVED that:

T2.11/P

.....

3. BAGGAGE

3.1 A passenger shall be entitled to the free baggage allowance applicable to the fare 

and/or baggage fees originally paid applicable to the original itinerary and as per Tariff 

Composite Resolution 302.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 742c

GOVERNMENT EXCESS BAGGAGE AUTHORIZATION (GEBA) FORM

(amending)

PSC(33 34)742c Expiry: Indefinite

Type: B

RESOLVED that:

T2.12/P

.....

3.2.4 Free Allowance—enter free baggage allowance, checking off “lb”, “kg” or “pcs”, as 

applicable;

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 742d

UNITED STATES GOVERNMENT EXCESS BAGGAGE AUTHORIZATION/ TICKET 

(GEBAT)

(amending)

PSC(33 34)742d Expiry: Indefinite

Type: B

RESOLVED that:

T2.12/P

.....

5.2 FREE ALLOWANCE

Show number of pieces or amount of weight, or free baggage allowance, followed by 

“pcs”, “lb” or “kg”.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 746

POOLING OF BAGGAGE

(amending)

PSC(33 34)746 Expiry: Indefinite

Type: B

T2.12/P

RESOLVED that:

Where two or more passengers, travelling as one party to a common destination or 

point of stopover by the same flight, present themselves and their baggage for travelling 

at the same time and place, they shall be permitted a total free baggage allowance 

equal to the combination of their individual free baggage allowances. To comply with 

passenger and baggage reconciliation requirements, each passenger of a non-family 

group should be given their own individual baggage claim checks.

Refer to Resolution 720a for the required ticketing entries.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 751

USE OF THE 10 DIGIT LICENCE PLATE

(new)

PSC(34)751 Expiry: Indefinite

Type: B

B7

RESOLVED that for the carriage of interline baggage, Members shall use a baggage 

identification number that is composed of all three components (Leading Digit, Baggage 

Tag Issuer Code and six-digit serial number) as defined in Resolution 740/5.1.2, and 

that only this baggage identification number shall be used in all baggage messaging 

and this entire number shall remain unchanged during the entire journey and in all uses. 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 760a

CHANGES TO RESERVATIONS INTERLINE MESSAGE PROCEDURES —

PASSENGER (AIRIMP)

R1

PSC(15 34)760a Expiry: Indefinite

Type: B

Resolved that:

.....

3. For introduction of additional miscellaneous abbreviation and other proposed 

changes in AIRIMP at times other than during a JPSC Meeting, Members and/or CRS 

Suppliers to such committees shall institute the following procedures:

3.1 forward requests for additions or changes to the IATA's Head, Interline & Intermodal 

Policy;

3.2 all such recommended changes shall be circulated by the IATA's Head, Interline & 

Intermodal Policy to the Members of the A4A Passenger Council/IATA Reservations 

Committee and the CRS delegates to such committees for comment within thirty (30)

fourteen (14) days after the date of the initial notification. Both A4A and IATA to send 

results to all Members of the A4A Passenger Council/IATA Reservations Committee 

and the CRS delegates to such committees on the 31st 15th day;

3.3 unless such recommended additions or changes have been protested by an A4A 

Passenger Council or IATA Reservations Committee Member within the specific 30 14-

day period, IATA's Head, Interline & Intermodal Policy shall arrange for their interim

effectiveness on a date mutually agreed upon by A4A and IATA. Final ratification for 

publication in AIRIMP will be made at the next meeting of the JPSC;

3.4 additions and changes on which agreement has not been reached will be referred to 

the next meeting of the JPSC.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 780

FORM OF INTERLINE TRAFFIC AGREEMENT – PASSENGER

(amending)

PSC (32 34)780 Expiry: Indefinite

Type: B

.....

B6

4.1.6 There is no prorating on delivery expenses. Delivery costs from such an Airport to 

the passenger may only be recharged by the delivering carrier (not the delivering 

vendor) to the member responsible for the mishandling if they are in excess of US$25 or 

its equivalent per delivery.

.....

The amount recharged shall be supported by proof of the costs incurred, and by a copy 

of the PIR either the PIR reference to allow the receiving Airline to check baggage 

tracing system files using the available transactions within the system, or if a tracing 

member only and or non IATA Carrier a copy of the PIR report, or in the case of 4.1.5.2 

by the original or copy of the expedite tag.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RESOLUTION 780e

IATA INTERLINE PARTICIPATION AGREEMENT – PASSENGER

(amending)

PSC (33 34)780e Expiry: Indefinite

Type: B

.....

B6

4.1.6 There is no prorating on delivery expenses. Delivery costs from such an Airport to 

the passenger may only be recharged by the delivering carrier (not the delivering 

vendor) to the member responsible for the mishandling if they are in excess of US$25 or 

its equivalent per delivery.

.....

The amount recharged shall be supported by proof of the costs incurred, and by a copy 

of the PIR either the PIR reference to allow the receiving Airline to check baggage 

tracing system files using the available transactions within the system, or if a tracing 

member only and or non IATA Carrier a copy of the PIR report, or in the case of 4.1.5.2 

by the original or copy of the expedite tag.

.....

B6.1

5.4.10 When processing claims involving international travel and airline(s) pro rata share of 

such claim exceeds US$1,500 (or equivalent), the claim receiving airline shall notify each such 

airline before playing the claim. Failure to respond within thirty (30) days from the date of 

notification will signify authorization to the carrier handling the claim to settle. For the purposed 

of proration, settlement of partial loss and/or damage by the claim receiving airline shall be 

accepted by the prorate partner(s) up to a limit of the total weight of the bag.

(Editor’s note: re-number subsequent paragraphs)

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1701j

AUTOMATED AND SELF-SERVICE FLIGHT REBOOKING FOR IRREGULAR 

OPERATIONS

(amending)

PSC(33 34)1701j

P6.3.1

.....

6. IRREGULAR OPERATIONS MANAGEMENT

.....

(Secretary note: this change concerns the words in brackets of the last cell in the table of that 

section) 

Note: Request availability from other airline through various established methods (e.g. 

seamless availability; direct sales; direct access; interactive sales) in order to get firm 

confirmation of the availability. (Need to follow rules as defined by IATA Resolutions 

766/735d, A4A Resolution 120.20 and AIRIMP or as provided in procedures outlined 

through bilateral agreements) in order to get firm confirmation of the availability (need 

to follow rules as defined by IATA Resolutions 766/735d, A4A Resolution 120.20 and 

AIRIMP, or as provided in procedures outlined through bilateral agreements).

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1706a

FUNCTIONAL SPECIFICATION FOR PASSENGER SELF-SERVICE SYSTEMS

(amending)

PSC(MV78 34)1706a

T2.12/P

RECOMMENDED that, Members apply the following specifications when implementing 

passenger self-service systems:

....

3.5.1 Definition

....

verification of free baggage allowance;

delivery of baggage tags;

....

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1707a

DATA FIELD DICTIONARY FOR DCS PASSENGER MESSAGES

(amending)

PSC(33 34)1707a

B12

RECOMMENDED that:

Members who transmit Departure Control (DCS) Passenger Messages shall apply the 

following definitions and formats for the automatic creation, transmission, receipt and 

interpretation of this group of messages.

This Data Field Dictionary for DCS Passenger Messages is the primary reference for 

the Data Element Directory for DCS Passenger Messages found in Recommended 

Practice 1707b. The Data Field Dictionary and the Data Element Directory are the 

primary references for the description, use, interpretation and guide while working with 

DCS Passenger Messages as described in Recommended Practices 1708–1719de.

Note: DCS Baggage Messages are documented in Recommended Practice 1745.

B11

Data Field Name Example Format/Reference

.....

commercial name of service CHARGEABLE SEAT 1-30 an

.....

EMD Type A 1 a

A – EMD-A (Associated)

S – EMD-S (Stand-Alone)

.....

reason for issuance code (RFIC) H 1 an

reason for issuance sub code (RFISC) E23 3-15 an

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1707b

DATA ELEMENT DIRECTORY FOR DCS PASSENGER MESSAGES

(amending)

B12

PSC(33 34)1707b

.....

Section 1 — DCS Messages and Data Elements

1.1 STANDARD DCS MESSAGES FOR PASSENGERS

. . .

• RP1719d: Ticketless Product List (TPL)

The TPL is generated by the DCS to advise selected applications of all locally boarded passengers 

who checked in with a Ticketless Product.

• RP1719e: Additional Service List (ASL)

The ASL is generated by the DCS to advise selected applications of all locally boarded passengers 

who checked in with an Additional Service.

Note: Refer to RP 1745 for DCS Messages related to baggage.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1708

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

(amending)

PSC(33 34)1708 .....

2.12 REMARKS ELEMENT

....

B10.2/P

2.12.6.6 Remarks Element for Ticket Number Information

2.12.6.6(a) The Remarks Element for ticket number identification information uses the 

IATA AIRIMP standard codes for ticketing, such as TKNE or TKNA.

2.12.6.6(b) Construction rules

.....

Examples:

2KORY/MICHAELDR/BARBARAMS-A5 .L/Y9DVZN .O/LH148C07MUC

.R/TKNE HK1 0745678432123/2-1KORY/MICHAELDR

.R/TKNE HK1 0745678432124/2-1KORY/BARBARAMS

2LARSON/TOMMR/JANEMRS .R/INFT HK1 12JAN07 LARSON/BILLYMSTR1LARSON/JANEMRS

.R/FOID HK2 CC MC1234567890123 

.R/FOID HK2 CC MC123456XXX0123

.R/TKNE HK1 0745675676578/3-1LARSON/TOMMR

.R/TKNE HK1 0749879879876/2-1LARSON/JANEMRS

.R/TKNE HK1 INF0749879879877/2-1LARSON/JANEMRS

1OLSEN/OLAFMR-A5 .R/TKNE HK1 0745678432125/2

2OXTORP/JOHNMR/PETERMR-A5

.R/FOID HK1 FF LH 992003018320931-1OXTORP/JOHNMR

.R/FOID HK1 FF LH 992003018313902-1OXTORP/PETERMR

.R/TKNE HK1 22021100010014/1-1OXTORP/JOHNMR

.R/VGML HK1-1OXTORP/JOHNMR

.R/TKNE HK1 22021100010025/1-1OXTORP/PETERMR

....

B11

2.12.6.11 Remarks Element for Chargeable Special Service Requests

2.12.6.11(a) This element is conditional and is sent together with an EMD for an additional service.

2.12.6.11(b) The Remarks Element for Chargeable Special Service Requests uses PD as the first

two characters.

2.12.6.11(c) Construction rules
Field Example Data Field Name

(see RP 1707a/b)

element ID . R/ element ID

chargeable special service code PDML code

space → information separator

status code and number HK1 status code

space → information separator

reason for issuance code G reason for issuance code

oblique / information separator

reason for issuance sub code 0B3 reason for issuance sub code

oblique / information separator

commercial name of service CHINESE MEAL commercial name of service

oblique (if free text follows) / information separator

free text NO MSG information separator

passenger ID -1HUSAK/JAY passenger ID

Note 1: The 14 chargeable special service requests are as follows:

PDBG Prepaid Baggage 

PDCO Carbon Offset 

PDFF Frequent Flyer 

PDGT Ground Transportation and Non Air Services 

PDIE In-Flight Entertainment 

PDLG Lounge 

PDML Meal/Beverage 

PDPT Pets 

PDRO Rule Override 

PDSB Standby 

PDST Store 

PDTS Travel Services 

PDUM Unaccompanied Minor 

PDUG Upgrades 

Examples:

.R/PDLG HK1 A/J60/LOUNGE ACCESS

.R/ASVC HI1 H/E23/LOUNGE ACCESS/S/0061234567890C1

2ADDAMS/GREG/KATE

.R/PDIE HK1 F/T95/INFLIGHT ENTERTAINMENT-1ADDAMS/KATE

.R/ASVC HI1 F/T95//INFLIGHT ENTERTAINMENT/A/6240241234571C3-1ADDAMS/KATE

2.12.6.12 Remarks Element for Additional Service Information

2.12.6.12a) The Remarks Element for Additional Services identification information uses the IATA AIRIMP standard 

code for Additional Services, such as ASVC.

2.12.6.12(b) Construction rules

Field Example Data Field Name

(see RP 1707a/b)

element ID .R/ element ID

additional service element identifier ASVC SSR (ASVC)

space → information separator

status code and the number 1 HI1 status code

space → information separator

reason for issuance code H reason for issuance code

oblique / information separator

reason for issuance sub code S23 reason for issuance sub code

oblique / information separator
if applicable, SSR Code SEAT SSR code

oblique / information separator

commercial name of service CHARGEABLE SEAT commercial name of service

oblique / information separator

EMD Type A EMD type

 (A – EMD-A Associated)

 (S – EMD-S Stand-alone)

oblique / information separator

EMD number including coupon number 0745678432123C2 n[13]a(1)n[1] 

passenger ID -1MUELLER/MIKEMR passenger ID

Note 1: There are four possible status codes.

HK – Holding Confirmed; no EMD required

HD – Holding Confirmed; EMD required

HI – Holding Confirmed; EMD issued

HN – Holding Need

Examples:

.R/RQST HK1 12C

.R/ASVC HI1 H/S23/SEAT/CHARGEABLE SEAT/A/1251234567890C1

.R/PDIE HK1 F/T95/INFLIGHT ENTERTAINMENT-TOWNSEND/JOHNMR

.R/ASVC HI1 F/T95//INFLIGHT ENTERTAINMENT/A/624024123457C3-1TOWN

.RN/SEND/JOHNMR

.R/VGML HK1

.R/ASVC HI1 M/S23/VGML/CHARGEABLE MEAL/S/1251234567890C4

B10.3/P

2.12.7 Table of SSR Codes

The following SSR codes from the IATA AIRIMP are used in DCS messages in .R/ 

Remarks Elements. They are shown in this table in alphabetical order by code.

SSR Code See Note Number Description

PDBG Prepaid Baggage (Chargeable)

PDCO Carbon Offset (Chargeable)

PDFF Frequent Flyer (Chargeable)

PDGT Ground Transportation and Non Air Services (Chargeable)

PDIE In-Flight Entertainment (Chargeable)

PDLG Lounge (Chargeable)

PDML Meal/Beverage (Chargeable)

PDPT Pets (Chargeable)

PDRO Rule Override (Chargeable)

PDSB Standby (Chargeable)

PDST Store (Chargeable)

PDTS Travel Services (Chargeable)

PDUM Unaccompanied Minor (Chargeable)

PDUG Upgrades (Chargeable)

....
B11

.....

3.1.2 PNL Message Example (Part 2)

AMSKMKL

.MADRMIB 042345

PNL

IB881/05MAR AMS PART2

-AGP80Y-PAD05

1GERSHWIN/GEORGEMSTR .R/UMNR HK1 UM08

2GERTKAMP/KRANZMR/JULIAMRS

1GERTMAN/STEFANMR .L/ABC32G

.R/DOCS HK1/P/US/732154364/US/12FEB86/M/21AUG07/GERTMAN/STEFAN/MICHAEL

3GOURMET/NOELMR/VICKYMRS/WILLIAMMSTR .R/CHLD 24APR04

2HARSMA/LARRYMR/OMARMRS .ID2/PSN57

2JONES/JOSEPHMR/CLARICEMRS .R/FQTV AF 12345-1JONES/JOSEPHMR

1LODEWIJS/RUDIMR-E2

2MOLEMAN/TOMMR/COURTNEYMRS .R/VGML NN1-1MOLEMAN/COURTNEYMRS

17NONAMES-F28 .C/WINDMILLTOUR

1NYSSEN/VICTORMR .O/IB441Y05PMI

2OOMEN/MARCMR/PAULAMRS .ID1/PSN32

1OPPERSTAL/GINAMRS

1PETERSON/JAMESMR .R/SVC HK1 H/E23/LOUNGE ACCESS

.R/PDLG HK1 H/E23/LOUNGE ACCESS

.R/ASVC HI1 H/E23/LOUNGE ACCESS/S/0061234567890C1

.R/ASVC HKI1 F/C92//DECK OF CARDS/S/8937261524364C1

5ROMANOW/ARTHURMR/CAROLMRS/CLAREMR/GINAMISS/WENDYMISS

1ROMPANI/ANGELINAMS-D4 .R/VGML NN1

2ROMYN/ALANMR/KATEMRS .ID2/PSN48

1SMITH/NOELMR .R/FQTV BA 12345

1TEPPATI/TUSHIMR .L/7232H3 .R/NSSA HK1 22C

.R/ASVC HKI1 GH/S23/NSSASEAT/CHARGEABLE SEAT 22C/A/4488342034539C21251234567890C1

2THOM/JANEDR/DEREKMR .L/DF9323

1VANDALEN/LIAMMR-E2 .R/ASVC HKI1 AGPQRL/B/9R7/SURFACE BUS/S/0742468246833C1

3VANDENHEUVEL/LIEFMR/PRITHVIMRS/WILLIEMMISS-F28

1VANDERGROOT/NICHOLAMRS .R/INFT HK1

2VANDERAA/WILLIAMMR/PAULINEMRS-F28

1VANHOUTEN/RUTGERMS .RG2/PSN02

2VIANDOLOS/JUSTINMR/LORNAMRS

4VOERMANS/WILLEMMR/PRIDAMRS/KATIEMISS/NIGELAMISS-F28

1WEISSMANN/RAYMR .R/KSML NN1

2WENNEMA/GORDONMR/DIANNEMRS-F28

4WOOL/ANDERSMR/BARBARAMRS/CARLMR/DINAMRS .R/RQST HK4 24A24B25A25B

ENDPNL

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RECOMMENDED PRACTICE 1719

PASSENGER FINAL SALES MESSAGE (PFS)

(amending)

PSC(33 34)1719

B10.1/P

B13

.....

2.8 CATEGORY ELEMENT

......

2.8.8 The categories are:

CFMWL Passenger without OK ticket, shown on PNL/ADL as a revenue passenger on the 

waiting list (.WL/); boarded.

FQTVN Frequent traveler number (if not shown on, or modified from, the passenger data 

the PNL/ADL).

NOSHO Shown on PNL/ADL but not checked-in (exclude .ID2/, .DG2/, .RG2/, .WL/ 

passengers)

OFFLK Passenger with OK ticket shown in PNL/ADL, checked-in but not departed. For 

example, not boarded because of capacity.

OFFLN Passenger with OK ticket, not shown on PNL/ADL, checked-in but not departed. 

For example, not boarded because of capacity.

NOREC Passenger with OK ticket, not shown on PNL/ADL; departed.

GOSHN Passenger without OK ticket, not shown on PNL/ADL; not departed; indicates to 

reservations that a higher passenger demand than the offered aircraft capacity 

has existed(exclude .ID2/, .DG2/, .RG2/ or .WL/ passengers).

GOSHO Passenger without OK ticket, not shown on PNL/ADL; departed (exclude .ID2/, 

.DG2/, .RG2/ or .WL/ passengers).

CHGCL Voluntary Compartment Change; upgraded/downgraded, passenger-to be listed 

under compartment travelled.

INVOL Involuntary Compartment Change; upgraded/downgraded, passenger-to be listed 

under compartment travelled.

CHGSG Change of Segment; passenger travelling to another destination then 

booked to.

CHGFL Passenger, not covered under any other category transferred to other flight due 

to flight irregularity.

IDPAD ID passenger boarded on a space available basis.

APIPX Changed or added API information for this passenger.

......

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1719b

PASSENGER RECONCILE LIST (PRL)

(amending)

PSC(33 34)1719b

B12

.....

Section 3—Examples

3.1 EXAMPLE OF A PRL; PART ONE OF A MULTI-PART PRL

QK ATLLSNW HDQRMNW MKCZKNW

.CDGKMAF NW/231429 GAT

PRL

NW049/24APR CDG PART1

-DTW004J

. . .

-DTW265Y

1BOOT/RICHARDJ

.L/NQUF8O

.W/K/1/20

.N/AF214975/1/NRT

.O/NW347Y24DTWSFO15551810

.O2/NW015Y24SFONRT19202210/1HK

.R/DOCS HK1/P/GBR/706013638/GBR/12APR74/M/13APR16/BOOT/RICHARDJOHN

.R/DOCO HK1//V/011905166

.R/DOCA HK1/R/USA

.R/DOCA HK1/D/USA/471 38TH STREET AVE APT C/SANTA CRUZ/CALIFORNIA

.R/FQTV NW100203546936 .R/TKNE HK1 0122134872230/1

.R/SEAT HK1 18C

.R/ASVC HI1 H/S23/SEAT/CHARGEABLE SEAT/A/1/251234567890C1

1FACON/ARNAUDMR

.L/OPP2DH

.W/K/2/41

.N/AF240630/2/DTW

.R/DOCS HK1/P/FRA/00PF15887/FRA/21JAN75/M/22MAR11/FACON/ARNAUD

.R/DOCA HK1/R/FRA

.R/DOCA HK1/D//MARIOTT 123 AIRPORT/DETROIT

.R/FQTV NW518101113 .R/TKNE HK1 0575225640011/1

.R/SEAT HK1 11A

ENDPART1

=

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1719e

ADDITIONAL SERVICE LIST (ASL)

(new)

PSC(34)1719e

B12

RECOMMENDED that:

In order to report the use of Additional Services for actual boarded passengers, 

Members shall use the message as described below.

Section 1 — General Description

1.1 DEFINITION

The Additional Service List shows a list of actually boarded passengers who used an 

additional service. The list also includes e-ticket numbers. 

1.1.1 ASL

The Additional Service List (ASL) shows a list of passengers who used an 

additional service.

1.1.2 Targeted ASL

The ASL, according to bilateral agreement, can be created to contain only the 

passengers that belong to a specific marketing flight on the affected operating 

flight. The header of such a targeted ASL contains the flight carrier code and 

flight number of either the operating carrier or marketing carrier, as bilaterally 

agreed.

1.2 TIME OF DISPATCH

1.2.1 The Additional Service List (ASL) is dispatched after flight departure as bilaterally 

agreed.

1.2.2 Diagram of ASL Transmission Rules

For a flight with itinerary A-B-C-D, the following ASLs would be dispatched, 

including the indicated

passengers for the indicated segments.

From DCS: To EMD System To EMD System To EMD System To EMD System

Station A Passengers:

A-B

A-C

A-D

(none) (none) (none)

Station B (none) Passengers:

B-C

B-D

(none) (none)

Station C (none) (none) Passengers:

C-D

(none)

Station D (none) (none) (none) (none)
1.3 MESSAGE IN MULTIPLE PARTS

If the ASL message is generated in multiple parts, each part must contain the 

Address Element,

Communications Reference Element, Message Identifier Element, Flight 

Element, Totals By Destination Element and the End Element.

1.4 COMPONENTS

The ASL contains the following components:

Address Element HDQRMDL

Communications Reference Element .AMSKMKL 131313

Message Identifier Element ASL

Flight Element DL0055/13MAR AMS PART1

Seat Configuration Element CFG/F22C33Y222

Actual Time of Departure Element ATD/1427

Totals By Destination Element -MSP010C

Name Element 1KLINE/GREGG

Automated PNR Address Element .L/ABC123/AF

Marketing Flight Information Element .M/CX3322F22HKGNRT1230HK

Remarks Element TKNE (conditional) .R/TKNE HK1 0188765434567/2

Remarks Element ASVC .R/ASVC HI1 H/S23/SEAT/CHARGEABLE SEAT/A/

Remarks Continuation Element .RN/1251234567890C1

End Element ENDPART1

Section 2 — Detailed Specifications

2.1 ADDRESS ELEMENT

2.1.1 This element is mandatory.

2.1.2 This element is governed by the IATA Systems and Communications Reference 

Manual.

2.1.3 For construction rules, see RP 1707b, Address Element.

2.2 COMMUNICATIONS REFERENCE ELEMENT

2.2.1 This element is mandatory.

2.2.2 This element is governed by the IATA Systems and Communications Reference 

Manual.

2.2.3 For construction rules, see RP 1707b, Communications Reference Element.

2.3 MESSAGE IDENTIFIER ELEMENT

2.3.1 This element is mandatory.

2.3.2 The Additional Service List uses the message identifier ASL.

2.3.3 For construction rules, see RP 1707b, Message Identifier Element.

2.4 FLIGHT ELEMENT

2.4.1 This element is mandatory.

2.4.2 For construction rules, see RP 1707b, Flight Element.

2.4.3 Example:

IB777/15JUL MAD PART1

Note: When there are no passengers to include in the whole message, insert the NIL 

Element on the next line after the Flight Element and terminate the message with the 

End Element.
2.5 SEAT CONFIGURATION ELEMENT

2.5.1 This element is optional.

2.5.2 For construction rules, see RP 1707b, Seat Configuration Element.

2.5.3 Examples:

CFG/111Y/MD8 (one configuration, one compartment, with optional 

aircraft type)

CFG/020F179Y (one configuration, two compartments)

2.6 ACTUAL TIME OF DEPARTURE ELEMENT

2.6.1 This element is optional.

2.6.2 For construction rules, see RP 1707b, Actual Time of Departure Element.

2.6.3 Example:

ATD/292215

2.7 TOTALS BY DESTINATION ELEMENT

2.7.1 This element is mandatory.

2.7.2 Only compartments that have boarded passengers are included in the message.

2.7.3 For construction rules, see RP 1707b, Totals by Destination Element.

2.7.4 Example:

-JFK123Y

2.8 NAME ELEMENT

2.8.1 This element is mandatory.

2.8.2 Names appear in the message in alphabetical order under each 

destination/compartment.

2.8.3 A surname is to be listed individually; for example, 2SMITH/ANDREW/BARBARA 

is listed as

 1SMITH/ANDREW and 1SMITH/BARBARA.

2.8.4 For construction rules, see RP 1707b, Name Element.

2.8.5 Examples:

1JONES/TRAVISMR

1MILLER/JAMES

1SMITH/THOMASMR

1SMITH/SUSANMRS

2.9 AUTOMATED PNR ADDRESS

2.9.1 This element is conditional.

2.9.2 When multiple record locators exist for an entry, include the record locator only of 

the addressee of the ASL, if known.

2.9.3 For construction rules, see RP 1707b, .L/ Automated PNR Address Element. 

This element uses

element ID “.L/”.

2.9.4 Example:

 .L/6Y21AS/CX

2.10 REMARKS ELEMENTS

2.10.1 This element is mandatory.

2.10.2 The Name Element is followed by Remarks Elements for ASVC and TKNE if available.

2.10.3 All elements follow the construction rules of Recommended Practice 1708 for the individual 

elements, and the construction rules in RP 1707b, .R/ Remarks Element. This element uses 

element ID “.R/’.

2.10.4 Examples:

1BRADLEY/JOEMR .L/543654/AY
.R/TKNE HK1 1250181239876/4

.R/ASVC HI1 M/S23/VGML/CHARGEABLE MEAL/S/1251234567890C4

1TAYLOR/RODNEYDR .L/987G4R/AY

.R/TKNE HK1 6242185255474/3

.R/ASVC HI1 F/T95//INFLIGHT ENTERTAINMENT/A/624024123457C3

2.11 END ELEMENT

2.11.1 This element is mandatory.

2.11.2 For construction rules, see RP 1707b, End Element.

2.11.3 The Additional Service List (ASL) ends with ENDASL.

Section 3 — Examples

3.1 EXAMPLE OF AN ASL WITH NAMES, PRESENT FOR SOME 

DESTINATION/COMPARTMENTS, BUT NOT ALL

CPHRMQI

.SGDRQQI 151422

ASL

QI798/15MAR MAD PART1

-CPH000F

-CPH003Y

1ANDERSEN/EMILYMRS .L/4567AS/SK

.R/TKNE HK1 0188765434567/2

.R/ASVC HI1 H/S23/SEAT/CHARGEABLE SEAT/A/1/251234567890C1

1BENNSSEN/TIM .L/348B22/SK

.R/TKNE HK1 0188765434567/2

.R/ASVC HI1 F/T95//INFLIGHT ENTERTAINMENT/A/624024123457C3

1JENSEN/ABNERMR .L/39328J/SK

.R/TKNE HK1 0188765434567/2

.R/ASVC HI1 M/S23/VGML/CHARGEABLE MEAL/S/1251234567890C4

ENDASL

=

NNNN

3.2 EXAMPLE OF NIL ASL

CPHRMQI

.SGDRQQI 151422

ASL

QI798/15MAR SGD PART1

NIL

ENDASL

=

NNNN

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RECOMMENDED PRACTICE 1735 

PLANNED SCHEDULE CHANGES

(new)

PSC(34)1735

T5

RECOMMENDED that:-

In order to better facilitate the handling of planned schedule changes the following 

procedure be applied:

1. SCOPE

The provisions of this Recommended Practice shall apply only in respect of planned 

schedule changes based on an airline’s own criteria for ticketed passengers who have 

not commenced travel and not unplanned schedule changes as a result of irregular 

operations. It shall not apply to group to bookings and/or route withdrawals for which 

separate agreements may apply.

2 OBJECTIVE

To ensure that when it is required to reissue a ticket that is subjected to a schedule 

change that all coupons that remain open should be reissued so that the passenger 

does not have multiple tickets being issued on different carriers stock when only parts of 

the itinerary are reissued and thereby rendering it impossible to service the original 

ticket when the passenger makes any subsequent voluntary changes.

The focus of this Recommended Practice therefore shall be to define who is responsible 

for the reissue whilst providing direction that travel agents could also perform such 

reissues. By having a standalone Recommend Practice for planned schedule changes, 

it becomes clear under which specific circumstances Resolutions 735d and 735e should 

be used without being explicit about it.
3. DEFINITIONS

For the purpose of this Recommended Practice the following definitions will apply:

3.1 PLANNED SCHEDULE CHANGE means any modification to the operation of a 

flight as filed in an airline’s schedules which may require passenger notification, and/or 

rebooking and/or re-ticketing. This may be a change in arrival or departure times, flight 

number or Reservations Booking Designator (RBD), frequency of operation or airports 

served. A change of arrival or departure time, as a result of a city's conversion to or 

from Daylight Time, also constitutes a planned schedule change.

3.1.1 PLANNED SCHEDULE CHANGE FREQUENCY OF OPERATION REDUCTION

means a reduction in the number of flights operating between two points (e.g. a 

reduction from five flights per day to three flights per day or a daily service to three 

times weekly).

3.1.2 PLANNED SCHEDULE CHANGE MISCONNECTION occurs when a passenger 

is unable to use reserved accommodation into or out of a connection point due to the 

planned schedule change. 

3.3 UNPLANNED SCHEDULE CHANGE means any change to a passenger’s booked 

and ticketed itinerary which takes place as a result of an inability to operate a carrier’s 

planned flight schedule due to unforeseen circumstances (irregular operations) for 

which the provisions of Resolution 735d shall apply. 

4. GENERAL PROVISIONS

4.1 The Validating Carrier or the issuing agent shall be responsible for any 

exchange/reissue of the affected ticket when required or, as bilaterally agreed, ticket 

update.

4.2 The provisions of this recommended practice shall apply whenever a Member 

makes a planned schedule change which results in the requirement to make a change 

to a booked and ticketed itinerary.

4.3 If a Member’s flight will not operate, such Member shall endeavor to confirm an 

alternative most comparable to the passenger's original flight.

4.4 When it becomes necessary for any Member to protect one of its passengers by 

making for that passenger a reservation on the line of a second Member, the provisions 

of Resolution 766 shall apply. 

4.5 Members or its agents booking interline space shall ensure that such space is 

reserved with due consideration for such receiving interline carrier’s availability. 
4.6 If a Member’s flight will depart or arrive earlier or later and this will result in a 

misconnection such Member shall endeavor to confirm an alternate most comparable to 

the passenger’s original flight in order to ensure the connection is maintained.

4.7 Members shall not advise schedule changes without endeavoring to offer an 

alternative. If no alternative is possible simply advise times and do not cancel any other 

flights as A Member or its Agent who booked the original space may elect to use earlier 

or later alternative arrival or continuation flights.

4.8 Upon advice of schedule change, the Member or its Agent who receives the 

information must record details for use in conjunction with subsequent transactions 

and/or ticketing purposes and take the following actions.

4.9. The Member or its agent will:

4.9.1 cancel any unacceptable space at once

4.9.2 with due consideration to any government regulations in force, make any required 

adjustment of subsequent space or arrival or continuation on other Member airlines, as 

directed by the Member advising the schedule change provided that such alternative is 

acceptable to the passenger, 

4.9.3 rebook the passenger on alternative flights acceptable to the passenger if 

possible, if the schedule change has caused the connection to become subminimum 

(where in the particular circumstance, the minimum connection time is no longer 

maintained).

5 PROCEDURAL REQUIREMENTS

5.1 If no alternative as outlined in Section 4 is acceptable to the passenger, a refund 

may be made in accordance with the provisions for Involuntary Refunds in Resolution

737.

5.2 If an alternative as outlined in Section 4 is acceptable to the passenger and the 

ticket is totally unused the Validating Carrier or the Ticket Handler acting on its behalf 

shall be responsible for ensuring that the entire original ticket is reissued. 

6. PROCEDURES FOR REISSUE

A reissue may not be required where a minor planned schedule change has no impact 

on the itinerary (e.g. minor time changes)
Totally Unused Tickets 

6.1 For totally unused tickets the Original Validating Carrier or the Ticket Handler acting 

on its behalf shall provide a reissued ticket. This procedure should be applied when 

alternative flights acceptable to the passenger have been confirmed or waitlisted. The 

reissued ticket shall include coupons for the entire itinerary.

6.2 The new ticket shall include the Original Fare Calculation, Fare, Tax/Fee/Charge, 

Equivalent Fare Paid, Fare Basis, Baggage Allowance, Not Valid After and Not Valid 

Before dates. 

6.2.1 The Not Valid After date shall reflect the date of departure of the flight(s) on which 

the passenger has been rebooked. Alternatively, if the original NVA date is later than 

the new travel date, the original NVA date may be used or may be left blank.

6.2.2 The Not Valid Before date shall reflect the date of departure of the flight(s) on 

which the passenger has been rebooked or may be left blank.

6.3 The first five places of the endorsement/restriction text shall reflect the characters 

‘SKCHG’.

7 ACTIONS BY TRAVEL AGENTS

If acceptable to the Original Validating Carrier, exchanges/reissues as a result of 

planned schedule change action may be performed by the travel agent in accordance 

with the terms of their Passenger Sales Agency Agreement

8 ACTIONS BY THE ORIGINAL MARKETING/OPERATING CARRIER

If acceptable to the Original Validating Carrier exchanges/reissues as a result of 

planned schedule change action by the Marketing/Operating may be performed by such 

Marketing/Operating Carrier. In such cases all remaining open for use coupons shall be 

exchanged or reissued. 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RECOMMENDED PRACTICE 1745

BAGGAGE INFORMATION MESSAGES

(amending)

PSC(33 34)1745

P8.5/P

.....

2.3.13 .J Processing Information; 9 characters minimum; 55 characters 

maximum

Construction Example 

Format

2.3.13.1 Element identifier: Full stop (.), ‘J’ .J .a

2.3.13.2 Separator: oblique (/) / /

2.3.13.3 Secondary code R 

a

— G = Ground Tracking; R = Reconciliation;

S = Sortation, H=Hand Scanner

2.3.13.4 Separator: oblique (/) / /

2.3.13.5 Agent Identification (2 to 9 characters) 43S mm(m..m)

2.3.13.6 Separator: oblique (/) / /

2.3.13.7 Scanner Identification (2 to 8 characters) 120D32 mm(m..m)

2.3.13.8 Separator: oblique (/) 

...

P8.2/P

4.5 ELEMENT SEQUENCE SUMMARY

The following shows the sequence of elements in a BSM.

Element Requirement Definition

BSM Mandatory Standard Message Identifier

CHG or DEL Conditional Change of Status Indicator

.V Mandatory Version and Supplementary Data

.F Conditional Outbound Flight Information

.I Conditional Inbound Flight Information

.O Conditional Onward Flight Information

.N Mandatory Baggage Tag Details

.D Conditional Check in Location Information

.S Conditional Reconciliation Data

.H Conditional Handling Location

.W Optional Pieces Weight, Dimensions and Type Data

.P Conditional Passenger Name

.G Conditional Ground Transport

.Y Optional Frequent Traveler Number
.C Optional Corporate or Group Name

.L Automated PNR Address

.T Optional Baggage Tag Printer ID

.K Default Message printer

.E Conditional Baggage Exception Data

.R Optional Internal Airline Data

.X Conditional Baggage Security Screening

ENDBSM Mandatory End of Message Identifier

4.6 MULTIPLE USE OF ELEMENTS

Multiple use of elements may be accomplished by following the structure of the BSM 

and the sequencing of elements. The primary elements are the ......

.....

P8.1/P

5.7.6 The notification for the Hold/Bulk compartment as load unit will be:

HLD1234(5)CC(C).

This notification is according the notation for ULD-s

HLD = indicator for Hold (container type)

1234(5) = serial number

CC(C) = Carrier code of transporting carrier (flight number related)

The Hold position in the aircraft will be according notation :

Hx(x) 1-2 numerics (Hold as section of the bulk compartment of the aircraft, 

See example 5.9.9)

.....

5.9.9 Single Bag From Reconciliation/Loading System

BPM<≡

.V/1LLHR

.F/BA117/03OCT/SEL<≡

.U/HLD0004BA/H4<≡ [new notation is : .U/HLD0004BA/4<≡]

.N/0125123456001<≡

.N/0125234567001<≡

.N/0125987654001<≡

ENDBPM<≡
B8.6/P

6.9 EXAMPLE MESSAGES

6.9.1 Standard Offload (Type-B), with Acknowledgement Request

LAXBRXH<≡ From Address

.HDQKMCX 311840<≡ To Address

BUM<≡ Standard Message Identifier

.V/1TLAX//1234567890/A/123ABC456Z<≡ Transfer bag in LAX; Ack requested; Ref 

Nbr 1234567890 with Encryption

.F/CX881/15JUN/HKG/Y<≡ Outbound to HKG on CX881

.U/AVE4321SQ/024L/T/Y/HKG<≡ Loading Information

.N/0131123456001<≡ Bag tag nbr; nbr of consecutive tags

.Q/006<≡ Loading sequence of bag

.S/N//N<≡ Reconciliation data: Not authorized to load

.H/T1/CENTRAL/E20<≡ Handling Terminal; Handling Bay/Pier; 

Handling Gate/Stand/Claim

.P/WONG/V< Passenger's name

.L/SBJ14X<≡ PNR Address

.E/CUST

.R/CUSTOMS REQUEST<≡ Internal Airline Data

.X/SEL/XRAY/SECURITY/TRANSFER<≡ Screening description

ENDBUM<≡ End of Message Identifier

RECOMMENDED PRACTICE 1745 

Attachment ‘A’ 

1. CODE SET FOR THE BAG HANDLING LOCATION IDENTIFIER 

.....

1.3 Additional Recommended Codes for Baggage Identification or Handling 

CPY A copy tag is required or has been done for

CPYA A copy tag is authorized for this baggage

CPYD A copy tag will be performed by the DCS

CPYN A copy tag is not authorized for this baggage

CREW Crew member's baggage 

CUST Bag (to be) inspected by customs

DAA Indicates baggage that has to be Deliver(ed) 

DUPE Duplicate tag number for the same flight

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1761a

GUIDELINES FOR THE ALLOCATION OF AIRPORT SLOTS

(new)

M4.2

PSC(34)1761a

The management of airport slots is required at some airports where the available airport 

infrastructure is insufficient to meet the demand of airlines and other aircraft operators. 

The Worldwide Slot Guidelines (WSG) is published by IATA to provide the global air 

transport community with a single set of standards to facilitate the management of 

airport slots. 

The WSG is overseen by the IATA Joint Slot Advisory Group (JSAG), comprised of an 

equal number of IATA Member airlines and airport coordinators. 

JSAG meets regularly to agree on proposals for changes to the WSG and to consult on 

the administration of the twice yearly IATA Slot Conference (SC). All changes are 

agreed by JSAG before being endorsed by the Heads of Delegation of the SC.

It is recommended that Members use the WSG as published in Attachment ‘A’.

Attachment ‘A’ is published separately and can be found at www.iata.org/wsg

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1777

ONLINE MARRIED SEGMENT CONTROL

(amending)

R4.10/P

PSC(MV78 34)1777

.....

1. OBJECTIVE AND DESCRIPTION

1.2 Definition

Married Segment Control (MSC) is the designation of two or more segments in an 

itinerary as a marriage, by the Member(s) providing the service. There needs to be a 

capability to include six or more segments in a marriage. Segments once identified 

defined as married by the Member(s) providing the service are actioned as a single unit 

(set) and shall be unconditionally treated as such by the receiving system.

An example of Married Segment Control is LAX–IAH–MIA, where a connection occurs 

in IAH and the two segments are designated by the Member as a marriage. Some 

Members also consider designate a round trip journey, e.g. LGW-AMS-LGW as a 

marriage. A journey such as LAX-IAH-MIA-LAX may also be designated by the 

Member as a marriage.

.....

1.5. Married Segment Control Indicators (Interactive Communication)

1.5.2 Members to CRSs

In both options (A and B) Members will indicate in a response message to CRSs, by 

use of unique MSC indicators, when two or more segments are to be married. 

Segments, once defined as married by the Member, shall be unconditionally treated as 

such by the receiving system. The absence of indicators from the Member to the CRS 

means no marriage.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1779

JOURNEY DATA

(amending)

R4.11/P

PSC(MV78 34)1779

.....

2. APPLICATION OF JOURNEY DATA 

Some applications that may invoke transmission of existing Journey Data include 

Seamless Sell, Seamless Availability, Direct Access, Seamless Cancel and End 

Transaction/Wrap Up.

To the members using this service, Journey Data shall be fully included in all 

transmissions, e.g. Seamless Availability, Direct Access, Seamless Cancel and End 

Transaction/Wrap Up Message. 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRATICE 1786

PASSENGER DISTRIBUTION LIFECYCLE

(new)

PSC(34)1786

RECOMMENDED that:

P12

Members, or associated service providers use the standards and procedures for the 

passenger distribution lifecycle as set forth in Attachment ‘A’. 

A twelve step process model has been developed to provide a process map of the 

individual steps that may be required. A number of the steps may be duplicated at one 

or more of the points in the transaction.

RECOMMENDED PRACTICE 1786

Attachment ‘A’

Passenger Distribution Process

1. INTRODUCTION/SCOPE

1.1. The Passenger Distribution Process describes the complete process in a series of 

12 distinct steps (see figure 1) from schedule filing through to revenue recognition.

1.1.1 There is a section for each of the main process steps within the overall twelve step 

model and also contains;

1.1.2 A description for main process steps

1.1.3 A list of the main Resolutions and Recommended Practices covering each of the 

main processes

1.1.4. A list of the Committees and Working Groups responsible for maintaining the

standards

1.1.5 This Recommended Practice remains a live document, to be amended as 

required, to reflect changes in process requirements or solutions development.

1.1.6 The end-to-end passenger process which defines what happens from a passenger 

processing perspective is documented in a series of Recommend Practices as shown in 

Recommended Practice 1701.
Figure 1: 12 Step Process

2. PURPOSE

Conceptually, as there is more and more reliance on automation, this Recommended 

Practice is designed to illustrate the linkage between all the various business processes 

through greater awareness and understanding of how they fit together to unlock 

synergies as defined in any number of standards references e.g. Scheduling Standards, 

Tariff Composite resolutions, Passenger Services Conference resolutions and 

recommended practices.

2.1 The purpose of this Recommended Practice is to document the complete range of 

process steps thus allowing all industry stakeholders (IATA/A4A Member airlines, 

participants in the IATA Strategic Partnership program, non-Member airlines and other 

industry suppliers and intermediaries) to deploy any passenger distribution process and 

supporting solution defined in the resolutions and recommended practices.

2.2 Any resulting amendments to existing resolutions and recommended practices as 

well as any new standards will be formally proposed to the JPSC annually.
3. BUSINESS PROCESSES

3.1 Scheduling

3.1.1 The Schedules Information Standards Committee (SISC) is responsible for the 

development of standard schedules data procedures and formats for the exchange of 

schedules information, maintained within the Standards Schedules Information Manual 

(SSIM). The objective of the SSIM is to ensure that there is available an official set of 

Recommended Practices which guides the industry along mutually compatible lines in 

the development of schedules data handling procedures. Full consideration is also 

given to the needs of those agencies which also require schedule or schedule related 

data, including government departments, airport and air traffic control authorities, 

timetable publishing agencies, fuel companies, etc. The manual aims to set common 

standards for external exchanges.

3.1.2 The SSIM also publishes appendices A,D, F and I to recommend amendments to 

aircraft type codes , airport passenger terminal codes, time zone information and region 

codes 

3.2 Filing

3.2.1 Carriers may file their own fares whether for online or interline carriage based on 

their own commercial criteria via an established fare filing vendor or directly with a 

system provider. IATA fares, known as ‘flex fares’ are established for interline carriage 

via the IATA e-Tariffs platform. 

3.2.2 e-Tariffs is an online solution allowing the aviation industry to maintain and 

develop multilateral interline fares and rules for systems and consumers worldwide. 

e-Tariffs provides airline pricing experts with the tools to submit their proposals for 

changes, and vote on fares packages, directly from their desks.

3.2.3 e-Tariffs provides a simplified meeting process, is convenient and an easy-to-use 

application. It is cost and time efficient as it eliminates travel and effort. It is equally 

acceptable to regulators. e-Tariff is the mechanism through which any changes are 

made on ‘flex fares’. 
3.3 Shopping, Search and Comparison

3.3.1 The Passenger Distribution Group (PDG) is responsible for the development of 

standards that support greater product transparency that enhances existing functionality 

to create an enhanced approach to shopping and comparison that goes beyond the 

existing methodologies based on price and schedule alone. 

3.4 Booking/Reservation

3.4.1 The Reservations Committee (ResCom) is responsible for the development of 

recommendations on all procedures and policy issues relating to reservations rules and 

regulations, including the transmission of reservations services for use by customers 

and agents.

3.4.2 ResCom also reviews proposals and develop recommendations for additions, 

deletions and amendments to the A4A/IATA Reservations Interline Message 

Procedures - Passenger (AIRIMP) manual and the IATA Reservation Services Manual.

3.4.3 The standards that are developed allow for the exchange of reservations 

information related to published schedules, connections, availability, inventory, and 

special requests and enables systems to store and/or transmit the information to enable 

the creation of the reservations record known as the Passenger Name Record (PNR).

3.5. Price Quote

3.5.1 How a price is constructed is based on many different factors including a carrier’s 

own commercial criteria and the application of applicable taxes, fees and charges. 

Resolutions and procedures on how a fare is constructed is documented in the Tariff

Composite and Worldwide Resolution Manual. This manual details resolutions in the 

series 001 through to 312. 

3.5.2 The Tariff Composite Conference is the body responsible for establishing 

standards related to fare construction. It meets annually.

3.5.3 Proposals for the Tariff Composite Conference are reviewed by the Resolution 

Advisory Working Group (RADWG) which meets to:

3.5.4 Discuss and develop uniform interpretations of existing resolutions and 

procedures relating to the application of tariffs and interlineable fares and rules. 

3.5.5 Discuss developments in distribution channels and recommend changes to 

existing resolutions and procedures relating to the application of tariffs and interlineable 

fares and rules. 

3.5.6 Review and advise on the implementation strategy of adopted changes and 

interpretations to current tariff resolutions, procedures and methodologies.
3.5.7 The clarification of these standards ensures the common application of the rules in 

CRSs and paper tariffs. It also ensures that industry rules are written against the 

background of the known standards to ensure the accurate programming into CRSs and 

the correct application.

3.6 Payment

3.6.1 Standard forms of payment are published in Resolution 728.

3.6.2 Standards for the reporting of travel documents issued by IATA travel agents via 

the IATA Billing and Settlement Plan (BSP) are published in the Data Interchange 

Standards Handbook (DISH). This global data interchange standard is implemented by 

all BSPs, to ensure consistency and the exchange of the highest possible quality data 

between BSPs and GDSs, airlines and other business partners.

3.6.3 Technical standards are developed and maintained within the DISH for the 

exchange of passenger ticketing and related data between travel agents and airlines for 

remittance and settlement purposes. 

3.6.4 Payment Card Industry Data Security Standards (PCI-DSS) require that credit 

card should either be masked or truncated when transmitted and should not be used for 

purposes other than payment in industry messages. 

3.7 Ticketing

3.7.1 IATA maintains the standards for Standard Traffic Documents (STDs) both in 

paper and electronic formats. They are published in the Passenger Services 

Resolutions Manual in the 720 series.

3.7.2 In general only standards affecting electronic tickets and electronic miscellaneous 

documents are reviewed. Paper ticket standards remain for those carriers who still use 

them. These will be abolished (in accordance with the decision of the PSC in October 

2011) on 01 April 2016 when only electronic documents will exist. 

3.7.3 The Ticketing Committee, held jointly with the Airlines For America (A4A), 

develops and maintains standards and procedures related to interline ticket forms, 

electronic tickets and electronic miscellaneous documents. The committee is 

responsible for the development of standards and for publishing these standards as 

Resolutions and Recommended Practices in the Passenger Services Conference 

Resolution Manual (PSCRM). The main focus of the work performed by this committee 

is to develop standards leading to greater use of automation and technology in an 

electronic environment. The Ticketing Committee no longer develops paper ticket 

standards since the removal of paper tickets on 1 June 2008 in all IATA's Billing and 

Settlement Plans (BSPs). Especially important is the continued development of 

standards to support the issuance of Electronic Miscellaneous Documents (EMD) which 

itself supports the fulfillment of ancillary services and automated baggage rules.
3.8 Servicing, Changes and Cancel

3.8.1 Standards covering Servicing, Changes and Cancellations to reservations and 

tickets are covered by all of disciplines documented in 3.1 through to 3.7.

3.8.2. How to recalculate a ticket where applicable in an exchange or reissue 

transaction is covered in the Tariff Composite Conference Resolution manual. Currency 

procedures are also documented in this manual.

3.8.3 Standards for the exchange/reissue of tickets are covered in the ticketing 

standards. 

3.8.4 In addition standards for the voluntary and involuntary refunds are also covered in 

the Passenger Services Conference Resolution manual and reviewed by the Ticketing 

Committee.

3.8.5 Rules for the servicing, exchange/reissue of tickets in an involuntary rerouting 

scenario as a result of irregular operations are covered by Resolutions 735d and 735e 

and reviewed by the Ticketing Committee.

3.9. Delivery

3.9.1 IATA maintains the standards for baggage tags, baggage security control, excess 

baggage ticket, mishandled baggage, baggage identification chart and dangerous 

goods in baggage. These are published in the Passenger Services Resolution Manual 

in the 740 series.

3.9.2 The Baggage Working Group (BWG) is established by the Airport Services 

Committee (ASC) to review and develop recommendations into a form that can be

adopted by the ASC and eventually the Passenger Services Conference (PSC) as 

recommended practices or resolutions. 

3.9.3 The majority of these changes occur from examination of RP1745 for ‘Baggage 

Information Messages’, RP 1800 for ‘Automated Baggage Handling Based on the IATA 

Licence Plate Concept’ and other related Recommended Practices such as RP 1740C 

that addresses Radio Frequency Identification (RFID) and its technological 

requirements.

3.9.4 IATA maintains the standards for ‘Type B’ messages to be used in Departure 

Control Systems (DCS) passenger messages. Series RP1706 addresses ‘Functional 

Specifications for Departure Control System’, RP1707 series addresses ‘Standard 

Symbols, Data Dictionary and Data Element Dictionary for DCS Passenger Messages. 

RP1708 through to RP1719 deals with formats for a wide variety of industry standard 

messages from and to a DCS system.
3.9.5 The DCS Message Working Group (DCSMWG) meets to evolve standards that 

impact DCS messaging 

3.9.10 The DCSMWG reviews, amends, and synchronizes DCS messages in 

Recommended Practices 1707-1719d with the work in other, associated IATA 

passenger and baggage working groups, such as the Reservations Committee and the 

Joint A4A/IATA Passenger Ticketing Committee.

3.9.11 The DCSMWG monitors and supports industry security related activities to 

include Advanced Passenger Information System (APIS) requirements for security.

3.9.12 The Passenger Experience Management Group (PEMG) oversees development 

of a whole series of recommended practices from 1701 through to 1701n related to 

passenger processing within an airport environment on such topics as document 

scanning, immigration, security screening and boarding.

3.10 Revenue Accounting

3.10.1 Revenue Accounting has three main functional areas covered by industry 

standards:

Sales

Prorate

Interline Billing and Settlement 

3.10.1 Sales of air transportation and related information is derived from a variety of 

different distribution channel sources including intermediaries. Sales data is supplied to 

revenue accounting either directly from a carrier’s own sales or indirectly via the HandOff Tapes (HOT) from IATA as a result of information supplied from the GDSs on the 

Reporting Tape (RET) in accordance with the standards as defined in the DISH (see 

3.6)

3.11 Prorate

3.11.1 Airlines engaged in the interlining of passengers and cargo depend on settlement 

agreements to assist in the determination of each airline's revenue. These agreements 

are referred to as the Multilateral Prorate Agreement-Passenger and the Multilateral 

Prorate Agreement-Cargo.

3.11.2 IATA's Prorate Agency maintains the passenger and cargo prorate agreements 

on behalf of airlines signatory to the Prorate Agency Agreement (PAA). The PAA is an 

agreement between the carriers and IATA to allow for the creation of the Prorate 

Agency to oversee these agreements on behalf of the signatories. The Prorate Agency 

is located in Geneva.

3.11.3 There are over 200 signatory airlines to the PAA. Signatory to the PAA is 

required before being able to sign one or both of the multilateral prorate agreements. 

Prorate Factors are contained in the Prorate Factor Manual (PMP).
3.11.4 The Interline Prorate Advisory Committee (IPAC) work with the Prorate Agent on 

technical and administrative matters relating to interline revenue proration. 

3.11.5 The committee oversees working groups that have been established to advise 

and make recommendations on the editorial content of the Prorate publications, and 

improvements to the proration process. Membership in the IPAC is open to IATA and 

non-IATA airlines that are signatory to the Prorate Agency Agreement. 

3.12 Interline Billing and Settlement

3.12.1 Standards for the interline billing and settlement of travel documents are 

publishes in the Revenue Accounting Manual (RAM).

3.12.2 Interline Billing and Settlement is completed in a paperless environment that is 

known as Simplified Interline Billing (SIS). Leveraging on the successful introduction of 

100% electronic ticketing, by taking advantage of today's all-data world, the Integrated 

Settlement (IS) solution seeks to eliminate paper and simplify the entire process to allow 

for more effective exchange of transaction information between billing entities and their 

interline partners. SIS is the electronic invoicing system that optimizes the interline 

billing & settlement processes, eliminates paper, and reduces costs

3.12.3 The Revenue Accounting Working Group (RAWG) is responsible to establish, 

maintain and enhance standard procedures for the interline billing and settlement of 

amounts becoming due pursuant to interline agreements which are published in the 

traditional RAM and the newer SIS-RAM.

3.12.4 The Revenue Accounting Working Group also provides a forum for the resolution 

of disputes arising from the interpretation and application of those procedures. In 

addition, the RAWG seeks to maintain awareness of action by other industry groups 

which have revenue accounting implications. 

3.13 Industry Messaging Standards.

3.13.1 Enabling a seamless flow of data across all the business functions and 

organizations requires the development of standard industry messages.

3.13.2 The Passenger and Airport Data Interchange Standards (PADIS) Board develops 

and maintains Electronic Data Interchange and XML message standards for passenger 

travel and airport-related passenger service activities. PADIS is governed by the 

Passenger Services Conference Resolution 783.
3.13.3 The following business areas are covered by PADIS EDIFACT message 

standards or XML schemas: 

• Reservations and electronic ticketing, including electronic miscellaneous 

documents; 

• Airport resource management and airport handling, including baggage handling; 

• Data exchange between airlines and governments concerning passenger data; 

• Data exchange between airlines and airports for operational and passenger data 

(including XML schemas to exchange data on bar coded boarding pass); 

• Slot management and scheduling messages based on the SSIM. 

3.13.4 PADIS maintains IATA’s data communication standards such as Type X. Those 

standards are found in IATA Systems Communications and Reference (SCR) volumes. 

3.13.5 For each business area, airlines and other interested parties form a working 

group of subject matter experts and document their initial needs in a Business 

Requirements Document (BRD). This document is then passed on to the Technical 

Assessment Group (TAG) for translation in EDIFACT messages and XML schemas. 

The working group then proceeds to build an implementation guide published along the 

message standard to facilitate implementation. 

3.13.6 Standards adopted by PADIS are being released twice a year and comprises a 

Message Standard Document, Reservation Implementation Guide and an Airports 

Implementation Guide

3.13.7 PADIS Code Set Directory for EDIFACT and XML, PNRGOV Implementation 

guide, all XML schemas and associated implementation guides as well as SCR 

Volumes are available for download on the PADIS Extranet site. 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1788

TICKETING AND BAGGAGE REGULATIONS FOR FREE AND REDUCED 

TRANSPORTATION

(amending)

PSC(32 34)1788 Expiry: Indefinite

 Type: B

T2.2/P

....

6. TOUR CODE BOX/DATA ELEMENT

....

When using the Tour Code Box/Data Element for entry of data for free and reduced rate 

ID travel, the following shall be entered in the order shown below. 

....

6.2 Rebate Type Codes

01 – Dead Heading Crews

06 – Duty Travel Firm (Bookable)

07 – Personal Travel Firm (Bookable)

10 – Duty Travel Standby

12 – Personal Travel Standby

Examples: 

11OCT95SK01

01JUL76LHO6

15SEP87BA12

6.3 Employing Company Code

(Staff means Employee/Retiree and eligible nominees of Employee/Retiree)

A Staff of airline through which benefits are derived (i.e., main contracting 

airline party in bilateral agreements)

B – Z As described in the Interline Staff Travel Agreement (ISTA) current at the 

time of ticketing. Staff of scheduled airline owned 100% by the airline 

through which benefits are derived

C Staff of scheduled airline owned 50-99% by the airline through which 

benefits are derived

D Staff of scheduled airline owned less than 50% by the airline through 

which benefits are derived

E Staff of non-airline subsidiary owned 100% by the airline through which 

benefits are derived
F Staff of carter or cargo airline subsidiary owned 51-100% by the airline 

through which benefits are derived

G Staff of airline operating as a Franchisee under the operating code of the 

airline through which benefits are derived

H Staff of other entities agreed bilaterally

I Reserved for airline internal use only

Examples:

11OCT95SK01A

07JUL67LH06BF

15SEP87BA12DH

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RECOMMENDED PRACTICE 1790

ADDITIONAL SERVICES

(amending)

PSC(33 34)1790

.....

T2.22/P

5. TICKETING AND PAYMENT PROCESS

An Electronic Miscellaneous Document shall be issued as payment for the Additional 

Services in accordance with the provisions of Resolutions 722f, 725f and 725g. 

Notwithstanding the provisions of Resolution 725f and 725g, when a fare fee calculation 

for additional services is required such fare fee calculation shall be in accordance with 

the provisions of Resolutions 722 725a and 725b paragraph 5 2.16. 

....

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1791d

PAYMENT CARD INDUSTRY DATA SECURITY STANDARDS (PCI DSS) 

COMPLIANCE

(new)

PSC(34)1719d

P10

Recommended that:

Member Airlines and/or Ticket System Providers (TSPs) may use the following 

guidelines to enable compliance with the requirements of the Payment Card Industry 

Data Security Standards (PCI DSS) whenever a payment card number is present as a 

Form of Identification (FOID), Form of Payment (FOP) and/or Transmitted in industry 

messages.

OBJECTIVES

1. GENERAL

The payment card industry has mandated that since 2008, all entities that process, 

store or transmit payment card data shall comply with the PCI DSS. PCI DSS protects 

customer’s personal data, reduces the risk of compromise of card for fraudulent usage, 

secures business reputation and removes the risk of fines and fees due to noncompliance in the event of a card data compromise.

This Recommended Practice recognizes that full payment card data is used for a variety 

of functions, such as payment for air transport and associated services (e.g. excess 

baggage, upgrades,). Payment cards are also used to facilitate check-in and other 

processes, whilst acknowledging that the presence of this information in readable or 

coded format may not be PCI DSS compliant. This Recommended Practice details the 

recommendations to be followed to ensure PCI DSS compliance, whilst continuing to 

support business needs. 

1.1.Scope

This Recommended Practice (RP) recognizes that a standardized method for 

processing, storing and transmitting of payment card data is required to enable the 

business processes and at the same time protect the integrity of payment card data. It is 

suggested that, to meet PCI DSS requirements, in non-payment-related messages, only 

truncated or masked card numbers should be used.

Non-adherence to PCI DSS by one Member sending payment card data to another 

Member in a non PCI DSS compliant way will nullify the PCI DSS efforts undertaken by 

the latter. 

1.2.Guiding Principles

When accepting cards as a method of payment, card numbers need to be handled in 

order to perform certain business processes. However, the following guiding principles 

should be integrated in these processes. Well documented and enforced handling 

procedures must be in place. 
Guiding principles are:

• To remove altogether from an airline IT infrastructure the presence of full card 

numbers by outsourcing processing to a PCI DSS compliant Payment Service 

Provider (PSP), or to replace such card numbers with tokens that have no intrinsic 

value. The International Card Schemes publish lists of PCI DSS compliant PSPs on 

their websites.

• To limit handling of card numbers as much as possible, by outsourcing processes to 

a PCI DSS compliant PSP.

• To secure card numbers whenever stored or transmitted (PCI DSS provides 

guidelines how to achieve this).

• To limit access to card numbers on a need to know basis and ensure proper access 

control are in place (e.g. accessible only with passwords).

2. DEFINITIONS

For the purpose of this Recommended Practice, the following definitions will apply:

Payment Card Industry means American Express, Discover/Diners, MasterCard 

Worldwide, Visa International and JCB1

. 

PCI DSS (Payment Card Industry Data Security Standards means the requirements 

issued and periodically updated by the PCI SSC (Payment Card Industry Security 

Standard Council). They can be found at 

https://www.pcisecuritystandards.org/index.shtml. For the purposes of this 

Recommended Practice, PCI DSS includes also the requirements issued by the Council 

under PTS (PIN Transaction Security) and PA DSS (Payment Application DSS) if 

applicable. 

Payment Card Data means card data embossed or printed on the card and included in 

the magnetic stripe and/or in the chip

Primary Account Number (PAN) means otherwise known as the card number 

3. METHODOLOGIES FOR PCI DSS COMPLIANCE

3.1 General

In accordance with PCI DSS requirements, masking is demanded when the PAN is 

displayed. Truncation is one of several options specified to meet PCI DSS requirements 

to ‘render the PAN unreadable...’. Masking and truncation are both methods of 

rendering the full PAN unreadable by removing or replacing a segment of the full PAN.

Note: PCI SSC states that: ‘This requirement does not apply to employees and other 

parties with a legitimate business need to see the full PAN.’ 

 1

While airlines and other merchants also accept other card brands than the 5 major international card brands making 

the PCI Council, it is recommended to consider applying PCI DSS standards to all card transactions in order to 

provide a consistent level of protection to all card paying clients and not appear discriminating between them. 
3.2 Masking: 

3.2.1 Masking applies to PANs that are displayed (for example, on paper receipts, 

reports, or computer screens).

3.2.2. Even if a PAN is masked when displayed, the full PAN may still be electronically 

stored and would need to be protected in accordance with PCI DSS requirements to be 

encrypted, truncated, or hashed.

3.2.3 PCI DSS requirements specify that when card data is masked for display, a 

maximum of the first six and last four digits (1234 56XX XXXX 7890) can be displayed. 

3.3 Truncation: 

Truncation applies to PANs that are electronically stored. 

3.3.1 When truncating is used, a maximum of the first six and last four digits should be 

stored after truncation. If an entity cannot meet the ’first 6 last 4‘ rule, and needs to 

store, for example, 8+0 (1234 5678 XXXX XXXX), and therefore is not able to use 

truncation to meet the PCI DSS requirements, then it shall use encryption, hashing or 

compensating controls to protect that stored data. 

3.4 One-way hashing:

3.4.1 A hash is intended to be irreversible by taking a variable-length input and 

producing a fixed-length string of cipher text. 

3.4.2 As the PAN has been 'replaced', it should be considered out of scope in the same 

manner receipt of truncated PANs are out of scope for PCI compliance. 

3.4.3 PCI DSS requirements state that the hash must be strong and one-way. This 

implies that the algorithm must use strong cryptography (e.g. collisions would not occur 

frequently) and that the hash cannot be recovered or easily determined during an attack

4. RESERVATIONS

To comply with PCI DSS specifications, whenever a credit card is used as a FOID, it 

must be truncated. Truncated means only the first 6 and last 4 digits may be transmitted 

in clear text and each of the remaining numbers is replaced by an ‘X’. 

5. TICKETING

5.1 Form of Payment (FoP)

Where a payment card is used as a form of payment, ticketing resolutions stipulates 

that the ‘form of payment’ data entered on the ticket, miscellaneous documents, excess 

baggage tickets and/or the passenger itinerary receipt shall be replaced with the letter X 

with the exception of the last four digits in accordance with the provisions of Resolution 

728 (i.e. XXXX XXXX XXXX 1234).
Note: This exceeds the requirements of PCI DSS and in the United States the 

requirements of the Fair_and_Accurate_Credit_Transactions_Act (FACTA) which 

prohibits businesses from printing more than 5 digits of any customer's card number or 

card expiration date on any receipt provided to the cardholder at the point of sale or 

transaction. 

5.2 Form of Identification (FOID)

Where a payment card is used as a Form of Identification (FOID) in electronic tickets, 

the FOID shall include only the first 6 and the last 4 digits of the payment card number. 

All remaining digits shall be replaced with an X. E.G. VI1234 56XX XXXX 7890.

Messages related to FOID will no longer pollute airline systems with full card data. 

Airlines using card number as FOID, will still be able to do so, since a partially 

masked/truncated number is not considered a “payment card” number for the purposes 

of PCI DSS compliance 

6. AIRPORT PROCESS

6.1 All payment card data that is read and transmitted by Common Use Self Service 

kiosks (CUSS) and Common Use Passenger Processing Systems (CUPPS) when used 

for FOID purposes shall be truncated in accordance with the provisions of paragraph 

3.3.

6.2 Applications that still need the complete PAN for payment shall be modified to 

access this data by requesting the card to be re-presented.

7. BSP (Billing and Settlement Plan) Processes

7.1 Airline Billing Analysis reports are sent by default with masked card numbers (1234 

56XX XXXX 7890). Such reports are not meant to be used for card payment 

processing.

7.2 Airline Accounting/Sales Data (formerly Hand Off Tapes) (HOT) files distributed to 

airlines, continue to be sent by default with card numbers shown in full in order to allow 

those airlines who process their card transactions in-house to continue do so.

7.3 BSPlink consultation of transaction history does not allow accessing the full card 

number; only a masked version is displayed on screen.

7.4 BSPlink refund requests initiated by Travel Agents have the card number data field 

‘auto-populated’ from the BSPlink database, thus removing the risk of typing mistake 

while guaranteeing the integrity of the link with the original purchase. This also removes 

the need for the Agent to conserve the original card number used to make the 

purchase. Only a masked version of the card number is visible on screen.
7.5 Airline Impact Review

7.5.1 Airlines are strongly advised to review their processes where the full payment card 

number needs to be present since payment card numbers in full are only required for 

the remittance of the transactions to the acquirer. 

7.5.2 It is recommended that transaction reconciliation can be conducted with truncated 

card numbers which avoids polluting revenue accounting systems with full payment 

card numbers. Using truncated numbers will allow airlines to de-scope such system 

from the mandatory PCI DSS compliance.

8. INTERLINING

Airlines should ensure that payment card data, whether sent in interline ticketing or 

reservations messages for form of payment or form of identification, is either masked, 

truncated or hashed in order not to pollute their interline partners systems and thereby 

rendering such partners not compliant with PCI DSS.

9. REVENUE ACCOUNTING

Airlines should ensure that payment card data when used in revenue accounting 

systems is fully compliant with PCI DSS.

10.FINANCIAL SYSTEMS AND PROCESSES

Airlines should ensure that all other financial systems and processes are fully compliant 

with PCI DSS.

11.ACTION BY TRAVEL AGENTS

Travel Agents shall ensure their full compliance with the Payment Card Industry (PCI) 

Data Security Standards, as provided by the Card companies and made available to 

agents through IATA, and that all sensitive card data obtained during the process of 

completing a card sales transaction is handled, stored, and transmitted with due regard 

to the security of the data. In accordance with the provisions of Resolution 890. 
12.ACTION BY TICKETING SYSTEM PROVIDERS (TSPs)

In accordance with the provisions of Resolution 854 as amended at the Passenger 

Agency Conference (34) held October 2011, the following provisions shall apply:

12.1. Provisions (The provisions of this section 12.1 become effective 01 January 

2014) as follows:-

12.1.1 That all equipment (software, hardware and transmission channels) installed and 

used in an Approved Location shall be PCI DSS compliant,

12.1.2 That the Operation or Operations of the Electronic Ticketing Service Provider, its 

agents or service providers shall be PCI DSS compliant,

12.1.3 That all transmission channels used by the Electronic Ticketing Service Provider, 

its agents or service providers to transmit files and reports including but not limited to 

Airlines, Data Processing Centers shall be PCI DSS compliant,

12.1.4 That all Electronic Ticketing Systems Providers shall submit annually to IATA a 

Certificate of Compliance as described by the PCI Security Standards Council (SSC),

13.ACTION BY GROUND HANDLERS

Members should ensure that ground handlers who conduct payment card transactions 

on behalf of the airlines whose airport work stations they are manning should ensure 

that they are adequately covered by their internal PCI DSS compliance program.

14.AVANCED PASSENGER INFORMATION (API)

Where it is required to transmit API information the payment card number is currently 

not required.

15.Additional Information

For additional information: 

https://www.pcisecuritystandards.org/index.php

or contact: 

pcidss@iata.org
16.SPECIFIC COUNTRY ISSUES

Italy

Italy has a local tax requirement that all sales be reported on paper. Consequently, a 

receipt of each BSP payment card transaction must be printed and forwarded to a 

service provider contracted by IATA, who sorts and dispatches the printed receipts to 

each relevant airline. The receipt printed from the ticketing system has a truncated 

payment card number in compliance with PCI DSS

Peru

Airlines are required to forward to tax authorities a report of their payment card sales. 

To comply with this requirement the Data Processing Center produces a specific report 

which is forwarded to each airline or its contractor. This procedure falls under the 

individual PCI DSS compliance project of each airline, as the IATA BSP local office is 

not handling that procedure. 

Airlines having BSP card sales in Peru are invited to ensure that this special BSP 

country activity is enclosed in their individual PCI DSS compliance project. 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1797

COMMON USE PASSENGER PROCESSING SYSTEMS (CUPPS)

(amending)

PSC(33 34)1797

....

B14

1.6 CUTE to CUPPS Migration

With any next-generation standard or product, a mechanism must be provided to 

migrate from the previous standard or product to the next-generation standard. This 

section provides the migration considerations for moving from CUTE to CUPPS. Given 

the wide array of variations between CUTE implementations combined with the 

differences that exist due to the local business and operational scenarios at each CUTE 

location, there is no one migration strategy that is applicable across suppliers. 

Therefore, each platform provider and/or platform supplier that proposes a CUPPS 

solution must provide a reasonable and realistic migration strategy.

Note: CUTE suppliers are required to provide support for their existing CUTE platforms 

for a period of three years from the date of first publication of the CUPPS Technical 

Specification.

....

Table 0.5: Required Workstation Components

Function Description

Computer The computer and its internal components.

Keyboard A standard 101+-key keyboard is required for each end-user workstation per local

configurations.

Pointing Device A pointing device is required for each workstation.

Touch Screen A touch screen is required to support the check-in and boarding functionality required by 

airlines and airports.

Windows Operating Windows provided print spooler, file access, memory management, etc.

System Services

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013

RECOMMENDED PRACTICE 1797a

AVIATION INFORMATION DATA EXCHANGE (AIDX)

(amending)

PSC(30 34)1797a

B14

RECOMMENDED that:

Members, airports or associated service providers use the specifications and standards as set forth in 

Attachment ‘A’ when planning to exchange flight related information for the purposes of displaying or 

accruing such information.

(Attachment ‘A’ is published separately – refer to: www.iata.org/workgroups/pemg)

(Secretary note: the rest of the text is new).

When an airline, airport or associated service provider plan to exchange Domestic or International flight or 

flight related information for the purposes of displaying or accruing such information, the specifications 

and standards as described in this Recommended Practice shall be applied.

1. INTRODUCTION

The Aviation Information Data Exchange (AIDX) Interface Recommended Practice describes the use of 

interface specifications and standards by which airlines, airports and other participants exchange 

information within or between their systems and organizations. The data exchanged is intended to be 

used for Domestic or International flights in the current Operational Window, and not for sending monthly 

schedules.

1.1 Use of the AIDX Information

This RP does not state or define how the AIDX data will be used. However examples of the applications 

that will make use of the data might be Flight Information Display System (FIDS), Resource Management 

System (RMS) or Baggage Handling Systems (BHS). Any data that may be shared by or provided to a 

3rd party have to be agreed upon in bilateral agreements between sender and receiver. It is possible that 

information will be communicated to areas outside the airport. 

1.2 Senders and Receivers

AIDX assumes there will be at minimum a Data Sender and a Data Receiver who exchange AIDX data 

over networks using predetermined protocols and formats. The Senders typically would be airlines or 

other providers of real time flight data, and the Receivers would be airports and third parties inside or 

outside of the airport environment requiring flight-related information. These parties could include 

stakeholders in aircraft turnaround, providers of information systems and various service providers who 

may need flight-related data to operate the service. The expectation is that all Senders and Receivers of 

AIDX data exchange will use the IATA PADIS XML Schema(s) defined for this purpose. The objective of 

this RP is to ensure that the Data Receiver obtains the correct flight information in a timely and reliable 

manner.

2. USAGE SCENARIOS

2.1 Normal Mode

AIDX assumes there will be at minimum a Data Sender and a Data Receiver who exchange AIDX data 

over networks using predetermined protocols and formats defined in a Bilateral Interface Agreement. This 

is the expected mode of operation for the directions contained within this RP for one data sender and one 

data receiver. The illustration shows the expected data flow - Data Sender to Data Receiver.
2.2 Potential Areas of Usage

This document does not define or make any recommendations as to the implementation of the potential 

additional usage of the AIDX data. Below are examples that might exist. There may be an Intermediate 

Receiver which receives AIDX data from the Data Sender and passes it on to one or more Data 

Receivers. In such a case, the Intermediate Receiver’s responsibilities will be similar to both a Data 

Receiver and Data Sender.

2.2.1 Possible Usage 1

2.2.2 Possible Usage 2
2.2.3 Possible Usage 3

3. AIDX TECHNICAL SPECIFICATION SUMMARY

To exchange the data as described in this Recommended Practice, the below description and definitions 

form the AIDX requirements for the data exchange.

The AIDX standard does not dictate stringent requirements on the information sent and instead relies on 

the participants to clarify their data requirements based upon what data is described in the standard. 

Different operational windows may and probably will exist for each data sender transmitting data to a 

receiver.

3.1 Data Exchanged

This section defines the data to be exchanged and its structure. 

3.1.1 Unique Flight Identifier

The Unique Flight Identifier consists of the minimum data fields needed to uniquely identify a flight leg. 

The unique flight identifier as defined in the Schema should be adhered to by all users of the schema in 

order to ensure the unambiguous identification of flights among all entities involved in data exchange.

3.1.2 Data Elements

The Schema identifies an extensive set of optional data elements, which are held in groups based on 

operational type e.g. arrival times and airport resources. The data elements cover public and non-public 

aspects. The intent is that this RP will be employed for a number of different applications. Therefore each 

time the RP is employed the potential sub-set of optional data will probably differ. With the exception of 

the Unique Flight Identifier, all of the data elements in the Schema are optional.

3.1.3 XML Schema

The XML Schema will follow the IATA PADIS XML best practices and standards and will be developed, 

maintained and published by IATA PADIS XMLWG under the PADIS Board. 

3.1.4 Resolving Data Differences

In some cases there could be multiple parties sending the same flight information, for example estimated 

arrival time sent from an airline or FAA or third party. There may be differences in the data depending on 

the Sender. It is the responsibility of the Receiver to resolve this issue.
3.1.5 Proprietary Data

As many of the fields are optional, it will be at the discretion of the Sender and Receiver to agree what 

data elements will be sent. Within the standard there are a set of minimum data requirements that has to 

be sent. Outside of the minimum requirements, the Sender and Receiver shall agree on how the data is 

to be used, stored, shared and secured. A bilateral agreement shall be established between sender and 

receiver on data exchanged and responsibilities for recipient of data, such as (but not limited to) 3rd party 

access, confidentiality of data, storage of data and usage of data.

3.2 Data Transport

The recommended practice does not specify a method of data transport of the XML data. This will be an 

agreement between the Sender and Receiver. Common protocol such as web services, HTTPS, SOAP, 

or FTP are expected to be used. The transport could be through a B2B VPN over the internet or a leased

line. Uni-directional serial connections should be avoided; rather architecture of standard open 

connections is recommended. It is the responsibility of the Sender and the Receiver to set up their 

transport method and determine the level of security required in their Interface Agreement. 

4. Management of the Schema

The XML Standard is developed, maintained and published by PADIS XMLWG under the IATA PADIS 

Board. The request for changes to the developed standard shall be requested by or through the CUSS 

Management Group and its associated Working Groups.

4.1 Availability of Standard

IATA shall produce, update, and make available the IATA PADIS standard XML Schema(s) and 

supporting documentation for AIDX Data exchange standard in electronic format and make it available to 

potential Senders and Receivers using existing screening and access rules to the IATA PADIS XML 

release site. The PADIS XML standards will be published on a separate IATA Extranet site. 

5. ROLES AND RESPONSIBILITIES OF AIDX PARTIES

This section addresses the roles and responsibilities of the various AIDX parties, as they pertain to overall 

interface provisioning and maintenance during live operation.

5.1 Data Sender’s Responsibility

The Sender will ensure that:

 Transmitted flight records conform to the IATA AIDX methods and schema as defined in the IATA 

PADIS XML release site.

 When a flight message is sent, it contains the latest information and that it is sent in a timely 

manner.

 Every time the sender sends a message, it will include every data item within the agreed subset 

with values known at the time of message transmission. The message will contain no indication of 

what data may have changed from previous transmissions.

 Messages are sent within the window agreed between the sender and receiver.
5.2 Data Receiver’s Responsibility

The Receiver will ensure that:

 Optional acknowledgment message are sent as agreed in the interface agreement.

 Use of the data conforms to any commercial restrictions as agreed with the sender of the 

information ( i.e. Passenger figures are to be used only on airport staff screens)

5.3 CERTIFICATION

There is no certification required. This is an agreement between the parties to deploy the IATA PADIS 

XML standards for exchange of AIDX data. If certificate or encryption of data has to take place, this will 

also be part of the bilateral agreement between sender and receiver.

6. BILATERAL INTERFACE AGREEMENT

Before implementation of an AIDX link, the sender and receiver should create a Bilateral Interface 

Agreement which records various technical and commercial factors which are necessary for the 

satisfactory implementation. The parties should agree on at least the following:

 What optional fields will be included in their specific interface. This will define the maximum 

subset of the flight message schema which the sender is capable of sending 

 Network communications, transport protocols and related factors.

 How to resolve differences in data received from other parties.

 Agreement of any features defined as optional in this RP

 The maximum subset of the flight message schema which the sender is capable of sending.

 The use of the optional data request message from the data recipient.

 The use of optional message application acknowledgement and/or error detection feature from 

the data recipient – including any timeout parameters

 Any other information which needs to be agreed for the unambiguous implementation and 

operation of the sender to receiver interface

 NOTE – a interface agreement template will be attached

 NOTE – a SLA template will be attached

7. REFERENCES

7.1 Standards

The AIDX Interface Standard references and acknowledges the standards shown below.

Table 7.1: IATA and ACC Recommended Practices

IATA A4A ACC Title

RP1785 Public Information Systems and Standards

ACC-ITS0010 ACC – ‘Airports IT & Systems Guidelines’

RP1797 RP30.201 CUPPS Technical Standard
7.2 Definitions

For the purposes of this Recommended Practice, the following definitions will apply:

Certification - The process by which an application or platform is validated to ensure proper operation 

against the defined specifications. There is no certification of the AIDX interface deployment other than 

the agreements between the parties to utilize the IATA PADIS XML standards for exchange of AIDX data.

CUPPS - Common Use Passenger Processing Systems.

Data Sender - The entity that creates the AIDX data to be distributed to others.

Data Receiver - The entity that receives the AIDX data for use within that entity’s systems and 

organization.

AIDX - Aviation Information Data Exchange intended to provide flight data to various systems.

Intermediate Receiver - The entity that receives the AIDX data from the Data Sender on behalf of 

another Receiver.

Interface System - Comprises the network, server, software and data storage components required to 

receive and utilize the AIDX data.

Leg-Based Flights - An aircraft movement comprising the flight between a departure airport and the 

corresponding arrival airport

Network - The communications equipment, software, cabling (wire, fiber, wireless), protocols and rules 

that securely delivers AIDX data between Data Sender and Data Receiver.

Node-Based Flights - When a flight is considered from an airport’s point of view. It can be either an 

arrival out of a particular airport or a departure out of a particular airport. Each leg would have two node 

based flights: a departure flight at the leg’s origin and an arrival flight at the leg’s destination.

Operational Window - That period agreed between the relevant parties, in which updates to flights 

operating in the window are required for distribution to interested parties. Note, the primary use of the 

AIDX standard is during the operational window, but wider usage is not excluded.

PADIS - Passenger and Airport Data Interchange Standards.

Unique Flight Identifier - The data fields which together define a unique flight leg

XML - Extensible Markup Language, the open standard for data formatting used by the AIDX protocol.

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013
RECOMMENDED PRACTICE 1800

AUTOMATED BAGGAGE HANDLING BASED ON THE IATA LICENCE PLATE 

CONCEPT

(amending)

PSC(32 34)1800

.....

P8.3/P

5.5 “Tracking” — Automated Baggage Tracking

...

5.5.8 Specific Elements

M — Mandatory

C — Conditional

O — Optional

.A (M) BCM-BAM

.C (O) BPM

.D (C) BPM

.E (C) BTR, BPM

.F (C) BTR, BPM

.H (C) BTR, BPM

.I (C) BTR, (O) BPM

.J (C) BPM

.N (M) BTR, BPM

.O (C) BTR, BPM

.P (C) BTR, (O) BPM

.R (O) BPM

.V (M) all messages used in this process

.X (C) BPM
B8.6/P

RP 1800/30.49: 6. Process Specific Baggage Codes according to IATA RP1745/ATA RP 30.45Note: S = significant to process; O = nice to have in process 

Code Description

Bag 

Message 

Element

InterModal

Receipt

Sortation Security

Screening

Security

Transport 

Authorization 

(Reconciliation)

Tracking OffLoading Re- Loading Tracing Re- Routing Re- Flighting Re- Tagging Inter- modal

Delivery

Remark

...

CURB Bag Check-In Location 

Identifier: Curb side

.D O S O O

CUST Bag (to be) inspected 

by customs

.E O S O O O S O S O O

D Security Screening 

Result Reason combined with result indicator REJ:Dark/shield alarm –blockage of visual image

.X O S O O
.....

5.6.8 Relevant Messages “Re-Routing” from DCS

P8.4/P

i = incoming, o = outgoing

BTM (o) — informs a receiving carrier and/or other handling partner(s) about 

incoming transfer bags for sorting

and/or reconciliation purposes

— contains the “new flight” in the “Baggage Outbound Flight Segment” 

and the “Baggage Class of

Travel”

— conditionally, the “Baggage Inbound Flight Segment”, the “Baggage 

Onward Flight Segment”

— conditionally, baggage data such as “Baggage Loading Priority” 

and/or “Baggage Type” and/or

“Baggage Identification And Handling” code

— contains the “Baggage Identification And Handling” code RRTE in the 

.E element, conditionally the

code IROP in the .E element

BSM DEL 

(o)

— indicates that the baggage data for the contained tag number is void 

for the “original flight”

— the “Baggage Loading Authorization” in the .S element will be N = “not 

authorized for loading”

— contains the “Baggage Identification and Handling” code RRTE, 

conditionally the code IROP in the .E element

BTM DEL 

(o) 

— indicates that the baggage data that have previously been sent for the 

contained tag number via a BTM are no longer valid 

Filing Period: Effective Date:

29 January - 1 June 2013

18 March 2013