BEFORE THE DEPARTMENT OF TRANSPORTATION WASHINGTON, D.C. Agreements Adopted by the Passenger Services. International Air Transport Association

Transcription

1 BEFORE THE DEPARTMENT OF TRANSPORTATION WASHINGTON, D.C. Agreements Adopted by the Passenger Services Conference (PSC) of the International Air Transport Association Docket OST APPLICATION FOR APPROVAL OF AGREEMENTS BY THE INTERNATIONAL AIR TRANSPORT ASSOCIATION March 10, 2008 Communications with respect to this document should be sent to: Douglas E. Lavin Regional Vice President North America International Air Transport Association 601 Pennsylvania Avenue, NW Washington, D.C (202)

2 Summary DOCKET: OST-2008 DOT ORDER: pending Date: March 10, 2008 Filing fee/iata Acct: $2013 A328 US/UST involved?: YES Intended effective date: June 1, 2008 Memorandum: PSC/RESO/141 dated February 8, 2007 Finally Adopted Resolutions & Recommended Practices r1-r33 PSC/MINS/023 dated February 28, 2006 MINUTES Summary is included. 7 Resolutions and 11 Recommended Practices (RPs) are submitted for information only because they are among the tranched items that no longer require DOT review and approval. The 7 Resolutions and 11 RPs are identified on the cover of PSC/Reso/141. r r2. 720a r r4. 722c r5. 722f r6. 722g r7. 722h r8. 725a r9. 725b r f r g r r d r r r r r e r r d r a r c r e r r r r r r r r r r Summary is included. APPLICATION FOR APPROVAL OF AGREEMENTS 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 Sections and of Title 49 of the United States Code and Parts , and (c) of Title 14 of the Code of Federal Regulations, I am filing with the Department this application for approval of an IATA agreement. This agreement and related factual and explanatory materials and documentation required by 14 C.F.R and Department and Civil Aeronautics Board (CAB)

3 3 precedent are contained in the IATA Traffic Conference documentation summarized above. This agreement arises from the continuing process of Services Conferences through which IATA Member airlines establish standardized facilitation arrangements intended to ease international air transportation and interline procedures. This agreement was developed in the context of prior Department and CAB rulings addressing related agreements which reflected regulatory and market conditions then in effect. The present agreement, which makes amendments to the framework agreements forming the charter for ongoing facilitation programs or creates new agreements pursuant to that framework, should be viewed as part of a dynamic process of IATA Member airline adjustment to governmental and economic factors. On previous occasions, the Department and CAB have found these framework agreements to be consistent with the public interest. The present agreement does not impair the previous bases for approval and themselves are not adverse to the public interest. Moreover, approval of this agreement, which reflects compromises among the differing economic and social philosophies of the many nations whose airlines are parties, will advance the public interest in maintaining good aviation relations with other countries. We request early approval by the Department pursuant to 49 U.S.C and the grant of full antitrust immunity pursuant to 49 U.S.C The conferral of full antitrust immunity would be in the public interest and necessary for the transaction to proceed. This agreement is a product of the IATA Services Conferences which the Department found to be anticompetitive but nevertheless approved and immunized in Order (May 6, 1985) on foreign policy and comity grounds. The agreement embodies amendments to services resolutions/recommended practices that have been previously approved and immunized or creates new resolutions / recommended practices pursuant to the framework forming the charter for ongoing facilitation programs. Therefore, consistent with the Department's policy of immunizing amendments coextensively with the underlying agreement, the subject agreement should be granted immunity. Respectfully submitted: Douglas Lavin Regional Vice President North America International Air Transport Association

4 4 CERTIFICATE OF SERVICE A copy of this application or a summary notice thereof has been served by first class or priority mail on the following persons: Chief, Transportation, Energy & Agriculture Section Antitrust Division Department of Justice Washington D.C Douglas Lavin Date Served

5 M E M O R A N D U M PSC/RESO/141 TO: FROM: All Members, Passenger Services Conference - Accredited Representatives IATA Strategic Partners Director, Passenger DATE: 8 February 2008 SUBJECT: BOOK OF FINALLY ADOPTED RESOLUTIONS & RPs PART 2 29 th IATA Passenger Services Conference (PSC) Toronto, 9-10 October 2007 Attached are the Resolutions & Recommended Practices (RPs) that were adopted at the above-mentioned Conference. The filing period is established as 18 February 30 April. To ensure timely approval, Members are requested to file these agreements, where required, with their Government upon receipt of this document and to advise this office ( feldmanm@iata.org) of their Government s action by the end of the filing period (30 April 2008). 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. Please note that Resolutions 720b, 722a, 726,726a, 726e, 726f, 740 together with RPs 1707a, 1707b, 1708, 1715, 1716, 1718, 1719, 1719b, 1719c, 1743e and 1745 are submitted for information only: they are in the category of select passenger service standards the DoT has determined need not be submitted for review and approval. The intended effective date is 1 June The Minutes are issued separately under Memorandum PSC/MINS/023 dated 8 February Part 1 of the Book of Finally Adopted Resolutions and RPs was circulated under cover of Memorandum PSC/RESO/140 dated 31 January The Expedited Resolutions & Recommended Practices were circulated under cover of Memorandum PSC/RESO/138 dated 30 October Michael Feldman International Air Transport Association Route de l'aeroport 33 PO Box 416 CH Geneva 15 Airport Switzerland Tel: Fax:

6

7 OUTLINE OF CONTENTS & STATUS OF EFFECTIVENESS RESOLUTIONS/RECOMMENDED PRACTICES FINALLY ADOPTED AT: 29 th PASSENGER SERVICES CONFERENCE (PSC) INTENDED EFFECTIVE DATE: 1 ST JUNE 2008 Resolution/RP Title PSC(29)720 PASSENGER TICKET AND BAGGAGE CHECK TECHNICAL SPECIFICATIONS (amending) PSC(29)720a PSC(29)720b [not for DoT approval] PSC(29)722 PSC(29)722a [not for DoT approval] PASSENGER TICKET AND BAGGAGE CHECK- ISSUANCE AND HONORING PROCEDURES (amending) CARBONISED TRAFFIC DOCUMENTS TECHNICAL SPECIFICATIONS (amending) TRANSITIONAL AUTOMATED TICKET (TAT) (amending) OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT) (amending) PSC(29)722c AUTOMATED TICKET/BOARDING PASS VERSION 2 (ATB2) (amending) PSC(29)722f ELECTRONIC TICKET AIRLINE (amending) PSC(29)722g ELECTRONIC TICKET NEUTRAL (amending) PSC(29)722h ELECTRONIC TICKET/ELECTRONIC MISCELLANEOUS DOCUMENTS GROUND HANDLING (amending) PSC(29)725a MISCELLANEOUS CHARGES ORDER (MCO) ISSUANCE AND HONOURING PROCEDURES BY MEMBERS (amending) PSC(29)725b MISCELLANEOUS CHARGES ORDER (MCO) ISSUANCE AND HONOURING PROCEDURES (AGENTS) (amending) PSC(29)725f ELECTRONIC MISCELLANEOUS DOCUMENT AIRLINE (amending)

8 Page 2 PSC(29)725g ELECTRONIC MISCELLANEOUS DOCUMENT NEUTRAL (amending) PSC(29)726 [not for DoT approval] PSC(29)726a [not for DoT approval] PSC(29)726e [not for DoT approval] PSC(29)726f [not for DoT approval] PSC(29)728 PSC(29)735d PSC(29)740 [not for DoT approval] PSC(29)762 MULTIPLE PURPOSE DOCUMENT (MPD) (amending) MULTIPLE PURPOSE DOCUMENT (MPD) CARRIER, CARBONISED, AUTOMATED (amending) MULTIPLE PURPOSE DOCUMENT (MPD) NEUTRAL, CARBONISED, MANUAL (amending) MULTIPLE PURPOSE DOCUMENET (MPD) CARRIER CARBONISED, MANUAL (amending) CODE DESIGNATORS FOR PASSENGER TICKET AND BAGGAGE CHECK (amending) INVOLUNTARY CHANGE OF CARRIER, ROUTING, CLASS OR TYPE OF FARE (amending) FORM OF INTERLINE BAGGAGE TAG (amending) AIRLINES DESIGNATORS (amending) PSC(29)766 PSC(29)767 INTERLINE PASSENGER RESERVATIONS PROCEDURE (amending) AIRLINE ACCOUNTING CODES AND AIRLINES PREFIXES (amending) PSC(29)780 FORM OF INTERLINE TRAFFIC AGREEMENT PASSENGER (amending) PSC(29)780e IATA INTERLINE TRAFFIC PARTICIPATION AGREEMENT PASSENGER (amending) PSC(29)792 BAR CODED BOARDING PASS (BCBP) VERSION 2 (amending) PSC(29)1707a [not for DoT approval] PSC(29)1707b [not for DoT approval] DATA FIELD DICTIONARY FOR DCS PASSENGER MESSAGES (amending) DATA ELEMENT DIRECTORY FOR DCS PASSENGER MESSAGES (amending)

9 Page 3 PSC(29)1708 [not for DoT approval] PSC(29)1715 [not for DoT approval] PSC(29)1716 [not for DoT approval] PSC(29)1718 [not for DoT approval] PSC(29)1719 [not for DoT approval] PSC(29)1719b [not for DoT approval] PSC(29)1719c [not for DoT approval] PSC(29)1719d PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS LIST (ADL) (amending) PASSENGER SERVICE MESSAGE (PSM) (amending) PASSENGER INFORMATION LIST (PIL) (amending) PASSENGER TRANSFER MESSAGE (PTM) (amending) PASSENGER FINAL SALES MESSAGE (PFS) (amending) PASSENGER RECONCILE LIST (PRL) (amending) ELECTRONIC TICKET LIST (ETL) (amending) ELECTRONIC TICKET LIST (ETL) (new) PSC(29)1720a PSC(29)1740c PSC(29)1743a [not for DoT approval] PSC(29)1743e STANDARD THIRTEEN-DIGIT NUMBERING SYSTEM FOR TRAFFIC DOCUMENTS (amending) RADIO FREQUENCY IDENTIFICATION (RFID) SPECIFICATIONS FOR INTERLINE BAGGAGE (amending) TRACING PROCEDURE FOR MISSING CHECKED BAGGAGE (amending) BAGGAGE IRREGULARITY REPORT (amending) PSC(29)1745 [not for DoT approval] PSC(29)1797b 1746 BAGGAGE INFORMATION MESSAGES (amending) BAGGAGE SYSTEM INTERFACE (BSI) (amending)

10 Page 4 PSC(29)1749 CARRIAGE OF CARRY-ON BAGGAGE (amending) PSC(29)1771 PSC(29)1773 SELL AND REPORT OR FREE SALE AGREEMENTS (amending) SPECIAL MEAL DEFINITIONS AND CODES (amending) PSC(29)1776 SEAMLESS CONNECTIVITY (amending) PSC(29)1779 JOURNEY DATA (amending) PSC(29)1790 ADDITIONAL SERVICES (new) PSC(29)1797 PSC(29)1798 PSC(29)1800 COMMON USE TERMINAAL EQUIPMENT (CUTE) PASSENGER PROCESSING SYSTEMS (CUPPS) (amending) CARRIAGE OF PASSENGERS WITH COMMUNICABLE DISEASES CONTACT OF AIR PASSENGERS EXPOSED TO A HEALTH HAZARD (amending) AUTOMATED BAGGAGE HANDLING BASED ON THE IATA LICENSE PLATE CONCEPT (amending)

11 SUMMARY OF CHANGES RESOLUTIONS/RECOMMENDED PRACTICES FINALLY ADOPTED AT: 29 th PASSENGER SERVICES CONFERENCE (PSC) INTENDED EFFECTIVE DATE: 1 ST JUNE 2008 Resolution/ Recommended Practice RESOLUTION 720 PASSENGER TICKET AND BAGGAGE CHECK TECHNICAL SPECIFICATIONS RESOLUTION 720a PASSENGER TICKET AND BAGGAGE CHECK - ISSUANCE AND HONOURING PROCEDURES RESOLUTION 720b CARBONISED TRAFFIC DOCUMENTS TECHNICAL SPECIFICATIONS Summary of Resolution/RP Provides the technical specifications for the manufacture of passenger tickets issued by airlines. Provides governing rules on how to issue a ticket, and applicable conditions for the honouring and re-issuance of tickets. Provides the technical specifications for carbonised traffic documents required for ticket vendors to manufacture paper traffic documents Summary of Amendment Provision of ticket notices is amended as a result of action taken to consolidate all ticket notices into one resolution (Resolution 724). A procedure for the ticketing of passengers with single letter family names is added. In addition, a clarification is added that the deduction method used with residual value MCOs shall not apply to EMDs. A number of ticketing rules for fare constructions are deleted as a result of tariff composition action to delete them from fare calculation rules (i.e. directional minimum, one way sub journey, common point minimum and return sub journey check). Reference to the technical requirements for the printing of ticket notices is deleted.

12 Resolution/ Recommended Practice RESOLUTION 722 TRANSITIONAL AUTOMATED TICKET (TAT) RESOLUTON 722a OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT) RESOLUTION 722c AUTOMATED TICKET/BOARDING PASS VERSION 2 (ATB2) Summary of Resolution/RP Provides governing rules on how to produce an automated ticket issued by airlines. It also provides the technical specifications and applicable conditions for the honouring of such tickets. Provides governing rules and technical specifications on how to produce an automated ticket issued by travel agents. It also provides the applicable conditions for the honouring of such tickets. Provides governing rules and technical specifications on how to produce an automated ticket/boarding pass (ATB2) ticket issued by airlines. It also provides the applicable conditions for the issuance and honouring of such tickets. Summary of Amendment Provision of ticket notices is amended as a result of action taken to consolidate all ticket notices into one resolution (Resolution 724). A procedure for the ticketing of passengers with single letter family names is added. A number of ticketing rules for fare constructions are deleted as a result of tariff composition action to delete them from fare calculation rules (i.e. directional minimum, one way sub journey, common point minimum and return sub journey check). References to the OPTAT being supplied by the IATA Billing and Settlement Plans (BSPs) is deleted as a result of 100 percent electronic ticketing in BSPs effective 1 June 2008 and a clarification is added that all ET eligible itineraries shall be issued as ETs. Provision of ticket notices is amended as a result of action taken to consolidate all ticket notices into one resolution (Resolution 724). An expiry date is added of 31 December 2010 with regard to the issuance of ATB2 magnetic stripe encoded boarding passes. Provision of ticket notices is amended as a result of action taken to consolidate all ticket notices into one resolution (Resolution 724). A procedure for the ticketing of passengers with single letter family names is added.

13 Resolution/ Recommended Practice RESOLUTION 722f ELECTRONIC TICKET AIRLINE RESOLUTION 722g ELECTRONIC TICKET NEUTRAL Summary of Resolution/RP 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 honouring of such tickets. 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 honouring of such tickets Summary of Amendment Various changes to the electronic ticket resolution for airlines as follows:- A Billing Carrier indicator is added to identify the codeshare partner in a block space codeshare scenario; As a result of action taken to consolidate all ticket notices into one resolution (Resolution 724), the notice imprinted on the passenger itinerary receipt is completely revised and the provision of ticket notices is amended; An option is added for the printing of a 2D bar code on the passenger itinerary receipt; Procedures are added detailing the response to a request for control of a flight coupon where the Marketing or Operating carrier no longer has control; A series of new data elements are added to the data elements glossary and matrices for the collection of carrier fees, excess baggage and the automated recalculation of fares and taxes/fees/charges. Various changes to the electronic ticket resolution for travel agents as follows:- References to OPTAT and OPATB2 form codes are deleted as a result of 100 percent ETs in BSPs effective 1 June As a result of action taken to consolidate all ticket notices into one resolution (Resolution 724), the notice imprinted on the passenger itinerary receipt is completely revised and the provision of ticket notices is amended; An option is added for the printing of a 2D bar code on the passenger itinerary receipt; The data elements matrix is amended to facilitate a series of new data elements that enables the collection of carrier fees, excess baggage and the automated recalculation of fares and taxes/fees/charges.

14 Resolution/ Recommended Practice RESOLUTION 722h ELECTRONIC TICKET/ ELECTRONIC MISCELLANEOUS DOCUMENTS GROUND HANDLING RESOLUTION 725a MISCELLANEOUS CHARGES ORDER (MCO) ISSUANCE AND HONOURING PROCEDURES BY MEMBERS RESOLUTION 725b MISCELLANEOUS CHARGES ORDER (MCO) ISSUANCE AND HONOURING PROCEDURES (AGENTS) Summary of Resolution/RP 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. Provides governing rules and technical specifications on how to issue an MCO issued by airlines. Provides governing rules and technical specifications on how to issue an MCO issued by travel agents. Summary of Amendment New data elements are incorporated into the matrix. A clarification that the deduction method shall not apply to the Stand Alone Electronic Miscellaneous Document (EMD-S) is added; A procedure for the ticketing of passengers with single letter family names is added. A clarification that the deduction method shall not apply to the Stand Alone Electronic Miscellaneous Document (EMD-S) is added; A procedure for the ticketing of passengers with single letter family names is added.

15 Resolution/ Recommended Practice RESOLUTION 725f ELECTRONIC MISCELLANEOUS DOCUMENT AIRLINE RESOLUTION 725g ELECTRONIC MISCELLANEOUS DOCUMENT NEUTRAL Summary of Resolution/RP 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. Provides governing rules for the issuance and use of Electronic Miscellaneous Documents (EMD) by agents. Summary of Amendment Various changes to the Electronic Miscellaneous Document issued by airlines as follows:- Clarification that when an associated EMD is changed into a stand-alone EMD it shall be exchanged and vice versa; Clarification that each EMD shall be issued with only one reason for issuance code; A new notice is added that shall be imprinted on the EMD receipt; Provision for 99 new and 99 paid tax/fee/charge amounts and their associated qualifiers is added; Procedures for the association of an EMD initiated by the Operating Carrier are added; Clarifications added for the association/disassociation of an EMD in the system update message; New data elements are incorporated into the matrix. Various changes to the Electronic Miscellaneous Document issued by travel agents as follows:- Clarification that when an associated EMD is changed into a stand-alone EMD it shall be exchanged and vice versa; Clarification that each EMD shall be issued with only one reason for issuance code; A new notice is added that shall be imprinted on the EMD receipt; Provision for 99 new and 99 paid tax/fee/charge amounts and their associated qualifiers is added; New data elements are incorporated into the matrix.

16 Resolution/ Recommended Practice RESOLUTION 726 MULTIPLE PURPOSE DOCUMENT (MPD) RESOLUTION 726a MULTIPLE PURPOSE DOCUMENT (MPD) CARRIER, CARBONISED, AUTOMATED RESOLUTION 726e MULTIPLE PURPOSE DOCUMENT (MPD) NEUTRAL, CARBONISED, MANUAL RESOLUTION 726f MULTIPLE PURPOSE DOCUMENT (MPD) CARRIER CARBONISED, MANUAL RESOLUTION 728 CODE DESIGNATORS FOR PASSENGER TICKET AND BAGGAGE CHECK RESOLUTION 735d INVOLUNTARY CHANGE OF CARRIER, ROUTING, CLASS OR TYPE OF FARE RESOLUTION 740 FORM OF INTERLINE BAGGAGE TAG RESOLUTION 762 AIRLINES DESIGNATORS Summary of Resolution/RP Provides detailed description of the reasons for which a Multiple Purpose Document (MPD) may be issued and its related printed terms and conditions. Provides governing rules on how to produce an automated carbonised multi purpose document issued by airlines. It also provides the technical specifications and applicable conditions for the honouring of such documents. Provides governing rules and technical specifications on how to issue an automated MPD issued by travel agents. Provides governing rules on how to issue a manual carbonised multi purpose document issued by airlines. Provides various coding structures in order to identify the type of fare and other conditions of travel for tickets and other documents. Provides governing rules for the involuntary rerouting of passengers due to flight disruptions. Provides information, standards and specifications for industry baggage tags/labels. Provides the governing rules for the assignment and use of airline designators for the entire airline and travel and tourism industry. Summary of Amendment Resolutions 725f and 725g (airline and neutral EMDs) is added as an exception whereby the deduction method, when issued as an unspecified miscellaneous charges order, shall not apply. A procedure for the ticketing of passengers with single letter family names is added. A procedure for the ticketing of passengers with single letter family names is added. A procedure for the ticketing of passengers with single letter family names is added. Reference to IATA Resolution 722d is deleted. The provision for the absorption of passenger expenses in an involuntary rerouting situation is completely revised. The exception whereby a Member operating a domestic service need not comply with the provisions of this paragraph is deleted. Editorial change to clarify existing text and facilitate manufacturer s compliance. Editorial change deleting the reference to ATA and IATA Member airlines as this is no longer a valid criterion as eligibility for codes.

17 Resolution/ Recommended Practice RESOLUTION 766 INTERLINE PASSENGER RESERVATIONS PROCEDURE RESOLUTION 767 ASSIGNMENT CRITERIA FOR AIRLINE ACCOUNTRING CODES AND AIRLIN PREFIXES RESOLUTION 780 FORM OF INTERLINE TRAFFIC AGREEMENT PASSENGER RESOLUTION 780e IATA INTERLINE TRAFFIC PARTICIPATION AGREEMENT PASSENGER RESOLUTION 792 BAR CODED BOARDING PASS (BCBP) VERSION 2 RP 1707a DATA FIELD DICTIONARY FOR DCS PASSENGER MESSAGES Summary of Resolution/RP Provides the definitions and governing rules for passenger reservations in an interline environment. Provides governing rules for the assignment and use of airline accounting codes and airline prefixes. Provides terms and conditions relating to the interlining between carriers of passengers and their baggage. Provides terms and conditions relating to the interlining between carriers of passengers and their baggage. Provides information, standards and specifications for bar coded boarding passes. Provides definitions and formats for use in DCS Passenger Messages. Summary of Amendment A reference is added for the procedures to be followed for requesting reservations in an irregular operation. Editorial change deleting the reference to ATA and IATA Member airlines as this is no longer a valid criterion as eligibility for codes. An accounting code is assigned for BSPlink agent. Provision of ticket notices is amended as a result of action taken to consolidate all ticket notices into one resolution (Resolution 724). References to the ATPCO All Fares product is deleted. Appendices A, B and C are deleted from the resolution since they are published separately. Provision of ticket notices is amended as a result of action taken to consolidate all ticket notices into one resolution (Resolution 724). Changes to facilitate the acceptance of bar codes on electronic devices such as PDAs and mobile phones. These changes included the adoption of 3 different symbologies that will allow a variety of choice and not force any particular matrix code on any airline. In addition, provision is added for the printing of a 2D bar code on the itinerary receipt of an electronic ticket. Minor editorial change

18 Resolution/ Recommended Practice RP 1707b DATA ELEMENT DIRECTORY FOR DCS PASSENGER MESSAGES RP 1708 PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS LIST (ADL) RP 1715 PASSENGER SERVICE MESSAGE (PSM) RP 1716 PASSENGER INFORMATION LIST (PIL) RP 1718 PASSENGER TRANSFER MESSAGE (PTM) RP 1719 PASSENGER FINAL SALES MESSAGE (PFS) RP 1719b PASSENGER RECONCILE LIST (PRL) Summary of Resolution/RP 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. 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. Provides guidance on how to inform downline stations of disembarking and transiting passengers who require assistance or special handling Provides guidance to member s cabin crews on necessary information concerning passengers on board and, optionally, about seats blocked for other purposes and downline seat protection Provides guidance on how to inform arrival stations of transfer passengers and their baggage, 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. The PRL is a list containing all passenger check-in details for actual boarded passengers of a flight departure. Summary of Amendment Changes to Data Element Dictionary to ensure that the DCS messages are consistent with AIRIMP as well as editorial changes. Small editorial changes Minor editorial change Minor editorial change Minor editorial change Minor editorial change Minor editorial change

19 Resolution/ Recommended Practice RP 1719c ELECTRONIC TICKET LIST (ETL) RP 1719d TICKETLESS PRODUCT LIST (TPL) RP 1720a STANDARD THIRTEEN-DIGIT NUMBERING SYSTEM FOR TRAFFIC DOCUMENTS RP 1740c RADIO FREQUENCY IDENTIFICATION (RFID) SPECIFICATIONS FOR INTERLINE BAGGAGE RP 1743a TRACING PROCEDURE FOR MISSING CHECKED BAGGAGE RP 1743e BAGGAGE IRREGULARITY REPORT RP 1745 BAGGAGE INFORMATION MESSAGES RP 1797b 1746 BAGGAGE SYSTEM INTERFACE (BSI) RP 1749 CARRIAGE OF CARRY-ON BAGGAGE Summary of Resolution/RP Provides guidance on how to report the use of electronic tickets for actual boarded passengers Provides guidelines to facilitate a standard process between an operating carrier and its ground handling company for ticketless products Provides guidelines regarding the numbering systems for airline and travel agent traffic documents. Provides guidance to members on RFID for baggage Provides guidance for the provision of tracing services for delayed or mishandled baggage. Provides a standard set of codes to use when reporting lost luggage that aids in reports, management and improvement of baggage recovery. Provides the definitions, formats and specifications for all of the messages used in the baggage handling process. Guidelines for the designing of a baggage system interface General guidance for carry-on luggage Summary of Amendment Minor editorial change The establishment of bilateral standards to allow industry systems to process ticketless products All BSP neutral ticket form codes have been revised as Off Premise Electronic Ticket (OPETs) as a result of 100 percent ET in BSPs effective 1 June Footnotes are added indicating the previous usage up to 31 May Various form code assignments and amendments. A new IATA Objective ID for Internal Airport Status. Replacement of date in object identifier 12.6 in Julian format rather than in the current day and month format. Also some additional editorial changes. Editorial changes to ensure that the correct resolutions are reference when the settlement of a claim is undertaken Editorial changes Editorial changes and a new message is necessary to enable the automated baggage re-tagging as described in the IATA RP 1800 Change of resolution number only. A complete rewrite of the RP concerning carry on baggage, because much of the content was out of date and no longer relevant

20 Resolution/ Recommended Practice RP 1771 SELL AND REPORT OR FREE SALE AGREEMENTS RP 1773 SPECIAL MEAL DEFINITIIONS AND CODES RP 1776 SEAMLESS CONNECTIVITY RP 1779 JOURNEY DATA RP 1790 ADDITIONAL SERVICES RP 1797 COMMON USE TERMINAL EQUIPMENT (CUTE) PASSENGER PROCESSING SYSTEMS (CUPPS) RP 1798 CARRIAGE OF PASSENGERS WITH COMMUNICABLE DISEASES CONTACT OF AIR PASSENGERS EXPOSED TO A HEALTH HAZARD RP 1800 AUTOMATED BAGGAGE HANDLING BASED ON THE IATA LICENSE PLATE CONCEPT Summary of Resolution/RP Guidelines for reservations systems regarding free sale and reporting procedures Provides guidance to standardise world-wide meal definitions Guidelines for reservations systems regarding the realtime exchange of data Guidelines for reservations systems regarding interactive communications of journey data Guidelines to facilitate the reservations, sales and delivery of airline additional services Provides procedures and specifications of a common use passenger processing systems Airline guidelines for instances when it is suspected that they have carried a passenger who is a health hazard Provides guidance for automated baggage handling within airline operations from an airline perspective Summary of Amendment Update to reflect new irregular operations procedures A complete rewrite and updating of meal definitions in order to comply with new legal and medical guidelines New procedures for cases where there is a reduction in the number of party Addition of new data element Establishment of a new recommended practice Guidance for the industry as it moves towards a new common use platform. Name changed from CUTE to CUPPS (Common Use Passenger Processing Systems). The entire text was deleted and replaced with reference to CUPPS documentation regarding procedures and specifications. Updating of guidelines in line with the International Health Regulations (IHR) Editorial changes as well as the addition of new text to promote clarity in the RP definitions and examples.

21 003 P5 T2.18/P 0 RESOLUTION 003 STANDARD RECISSION RESOLUTION PSC(29)003 Expiry: 2 June 2008 Type: B 003 P5 T2.18/P Resolved that, effective 1 June 2008, the following resolutions are rescinded: Resolution 721a: Billing and Settlement Plan Canada (Use of Traffic Documents) Resolution 722d: Off Premise Automated Ticket/Boarding Pass Version 2 (OPATB2) Resolution 724a: Passenger Ticket Notice of Overbooking of Flights (except USA/US Territories) Resolution 724b: Informing Passengers of Taxes, Fees and User Charges Resolution 724c: Notice of Liability Limitations Neutral Filing Period: Effective Date: 18 February June April 2008

22 720 P5.1 0 RESOLUTION 720 PASSENGER TICKET AND BAGGAGE CHECK TECHNICAL SPECIFICATIONS (amending) 720 P5.1 PSC(29) TICKET NOTICES Expiry: Indefinite Type: B 720 P5.1 The Warsaw Convention/Montreal Convention Notice and the Notice of Contract Terms Incorporated by Reference, the Advice to International Passengers on Limitation of Liability, and the Notice of Baggage Liability Limitations The Conditions of Contract and Other Important Notices as set forth in Resolution 724 shall be contained in the ticket. Optionally, they may be included as part of the ticket set which is given to the passenger, in which case the ticket set shall incorporate the title Passenger Ticket and Baggage Check, and the wording as shown in Attachment E shall be contained in the ticket. Attachment E NOTICE TO BE CONTAINED IN THE TICKET IF THE LEGAL NOTICES (AS REFERRED TO IN PARAGRAPH 5 3 OF THIS RESOLUTION) ARE NOT CONTAINED IN BUT PROVIDED WITH THE TICKET: AIR TRANSPORTATION If the passenger s journey involves an ultimate destination or stop in a country other than the country of departure the Warsaw Convention or the Montreal Convention may be applicable and these Conventions govern and may limit the liability of carriers for death or bodily injury and in respect of loss of or damage to baggage. Many air carriers have waived the Warsaw limits for death and bodily injury. Further information may be obtained from the carrier. Passengers on a journey involving an ultimate destination or a stop in a country other than the country of departure are advised that international treaties known as the Montreal Convention, or its predecessor, the Warsaw Convention, including its amendments (the Warsaw Convention System), may apply to the entire journey, including any portion thereof within a country. For such passengers, the applicable treaty, including special contracts of carriage embodied in any applicable tariffs, governs and may limit the liability of the carrier. CHECK WITH YOUR CARRIER FOR MORE INFORMATION. With this ticket you will receive a set of notices which forms part of the ticket and contains the Notice of Contract Terms Incorporated by Reference and other important notices Conditions of Contract and Other Important Notices. Please make sure that you have received these notices, and if not, contact the nearest office of the issuing airline or travel agent to obtain copies prior to the commencement of your trip. NON-AIR TRANSPORTATION AND/OR SERVICES Where this ticket is issued for transportation or services other than air travel, specific terms and conditions may apply. These terms and conditions may be included in the ticket set or may be obtained from the issuing company or agent. Filing Period: Effective Date: 18 February June April 2008

23 720a 720a T2.21/P T2.25/P T9 T2.25/P 0 RESOLUTION 720a PASSENGER TICKET AND BAGGAGE CHECK ISSUANCE AND HONOURING PROCEDURES (amending) PSC(29)720a Expiry: Indefinite Type: B 2 NAME OF PASSENGER BOX Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either: double the single letter family name as the family name. For example, Miss Moan Y represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS.

24 720a T9 Attachment A A* Fare Construction Principle Directional Minimum on normal one way fares, normal open jaw fares and special one way fares. One way sub-journey check Open Jaw Common Point Minimum Check Return sub journey check From/To Column Carrier Column Fare Calculation Column Draw horizontal line at Enter the amount end of itinerary. On against the P Enter P against the succeeding lines enter at city of the city pair, cities to which the ross out the unused directional fare box applies for that fare component Leave blank Draw horizontal line at end of itinerary Leave blank One way sub-journey check (OSC) Enter H on same line as amount. Draw horizontal line at end of itinerary Enter P on same line as amount Return sub-journey check (RSC) Enter U on same line as amount. Enter points determining minimum fare on line following end of itinerary. On succeeding line, enter applicable amount. Draw horizontal line at end of itinerary Enter R/ and the city code of the common point on one line and, when there are two common points, R/ and city code of the second common point on the next line. On following line, enter amount Enter points determining minimum fare on line following end of itinerary. On succeeding line, enter applicable amount. Resolution Reference 017c -17d 017d 017d

25 720a T2.21/P Attachment B B* 5.5 Miscellaneous Charges Orders MCOs issued before the end of the transition period and showing an EMU le currency may be accepted subject to the validity of the MCO but only at the equivalent using the fixed rate of conversion that will be advised The deduction method for MCOs 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). Filing Period: Effective Date: 18 February June April 2008

26 720b P5.1 0 RESOLUTION 720b CARBONISED TRAFFIC DOCUMENTS TECHNICAL SPECIFICATIONS (amending) PSC(29)720b Expiry: Indefinite Type: B 720b P TICKET NOTICES The Notice of Contract Terms Incorporated by Reference and other Notices for Neutral Documents shall be capable of being printed in multi-colours as required (two colours shall be regarded as normal). Filing Period: Effective Date: 18 February June April 2008

27 722 P5.1 T2.25/P T9 0 RESOLUTION 722 TRANSITIONAL AUTOMATED TICKET (TAT) (amending) PSC(29)722 Expiry: Indefinite Type: A 722 P T2.25/P 2.3 TICKET NOTICES The Warsaw Convention/Montreal Convention Notice and the Notice of Contract Terms Incorporated by Reference, the Advice to International Passengers on Limitation of Liability, and the Notice of Baggage Liability Limitations The Conditions of Contract and Other Important Notices as set forth in Resolution 724 shall be contained in the ticket. Optionally, they may be included as part of the ticket set which is given to the passenger, in which case the ticket set shall incorporate the title Passenger Ticket and Baggage Check, and the wording as shown in Attachment F shall be contained in the ticket NAME OF PASSENGER BOX Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either: double the single letter family name as the family name. For example, Miss Moan Y represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS. 722 T FARE CALCULATION MINIMUM FARES Directional Minimum One Way Fare Components (DMC) Where it is necessary to raise the fare for a one way fare component to a directional minimum level, imprint P followed by the city pairs and the amount. This entry shall be made at the end of the itinerary preceding the total amount in NUCs. Example: P TYOLON Lowest Combination Used to Establish an Unpublished Fare DMC/COM/COP P_C/LON_ REKCTG333.33

28 RSC U_C/SIN_AKLSID33.33 Where it is necessary to establish a fare between any two ticketed points for fare construction checks (such as HIP, BHC, COM, DMC, CTM, RWM, OSC, RSC, and COP), imprint C/ and the ticketed point used for construction immediately preceding the city pair of the check and the amount One Way Sub Journey Check Where it is necessary to raise the sum of a series of consecutive/contiguous one way sub journeys to the published direct fare, imprint H followed by the pair of points and the amount. This entry shall be made at the end of the itinerary in the order in which it occurs in the calculation of the fare. Example: H ZRHLCA Return Sub journey Check Where it is necessary to raise the sum of a series of consecutive/contiguous return sub journeys to the highest return fare, imprint U followed by the pair(s) of points and the amount. This entry shall be made at the end of the itinerary in the order in which it occurs in the calculation of the fare. Example: U TLVTYO (return sub-journey check) U ZRHCCU ZRHJAI (return sub-journey check with open jaw) 722 T Open Jaw Common Point Minimum Where it is necessary to raise the constructed fare to the level of the applicable fare to or from a common ticket point in the country of commencement of travel and/or country of turnaround, imprint P R/, city code(s) of common point(s), followed by amount. This entry shall be made at the end of the itinerary preceding the total amount in NUCs. Example: P R/CPH8.00 P R/STO/AKL Secretary Note: Paragraphs will require renumbering

29 722 T9 Attachment C H H ZRHLCA One way sub-journey check. C U U TLVTYO (return sub-journey check) U ZRHCCU ZRHJAI (return sub-journey check with open jaw) P MOWJNB15.00 Increase to a directional minimum one way fare component of a one way journey. P R/CPH8.00 P R/STO/AKL Increase constructed fare to level of applicable fare to or from a common ticket point in country of commencement of travel and/or country of turnaround. 722 P5.1 Attachment F F NOTICE TO BE CONTAINED IN THE TICKET IF THE LEGAL NOTICES (AS REFERRED TO IN PARAGRAPH 2.3 OF THIS RESOLUTION) ARE NOT CONTAINED IN BUT PROVIDED WITH THE TICKET: AIR TRANSPORTATION If the passenger s journey involves an ultimate destination or stop in a country other than the country of departure the Warsaw Convention or the Montreal Convention may be applicable and these Conventions govern and may limit the liability of carriers for death or bodily injury and in respect of loss of or damage to baggage. Many air carriers have waived the Warsaw limits for death and bodily injury. Further information may be obtained from the carrier. Passengers on a journey involving an ultimate destination or a stop in a country other than the country of departure are advised that international treaties known as the Montreal Convention, or its predecessor, the Warsaw Convention, including its amendments (the Warsaw Convention System), may apply to the entire journey, including any portion thereof within a country. For such passengers, the applicable treaty, including special contracts of carriage embodied in any applicable tariffs, governs and may limit the liability of the carrier. CHECK WITH YOUR CARRIER FOR MORE INFORMATION. With this ticket you will receive a set of notices which forms part of the ticket and contains the Notice of Contract Terms Incorporated by Reference and other important notices Conditions of Contract and Other Important Notices. Please make sure that you have received these notices, and if not, contact the nearest office of the issuing airline or travel agent to obtain copies prior to the commencement of your trip. NON-AIR TRANSPORTATION AND/OR SERVICES Where this ticket is issued for transportation or services other than air travel, specific terms and conditions may apply. These terms and conditions may be included in the ticket set or may be obtained from the issuing company or agent. Filing Period: Effective Date: 18 February June April 2008

30 722a P5.1 T2.18/P T2.30/P 0 RESOLUTION 722a OFF PREMISE TRANSITIONAL AUTOMATED TICKET (OPTAT) (amending) 722a 722a T2.18/P T2.30/P PSC(29)722 Expiry: Indefinite Type: A RESOLVED that: Notwithstanding Resolution 722, for interline carriage, the Off Premise Transitional Automated Ticket (OPTAT) shall be used as provided herein. Section 1 General 1.1 The OPTAT is a multi-copy carbonised ticket designed for use in various automated printing devices, for which data may be computer generated. 1.2 The OPTAT shall not be issued manually. 1.3 The OPTAT shall not be issued for more than one passenger for international travel. 1.4 In accordance with their interline traffic agreements, Members shall honour the OPTAT. 1.5 The OPTAT shall be used at Off Premise locations, i.e. passenger sales agents and commercial accounts, when two or more Members individually transmit data from their systems for issuance, or the ticket printing device is neither provided nor controlled by the Member. In all other cases, the OPTAT may be used at such off premise locations. 1.6 In countries/areas where the IATA Billing and Settlement Plan has been implemented, the OPTAT shall be used by those passenger sales agents who utilise automated ticket printing devices. an electronic ticket (OPET) in accordance with resolution 722g shall be issued. 1.7 USE BY MEMBERS The OPTAT ticket format may be used by Members at their own offices A Member may use, in its own ticket offices which are staffed and operated as a wholly owned airline ticket office, the neutral BSP OPTATs in use in the same country, which shall be obtained from the local BSP. Any such tickets which are lost, stolen, fraudulent or otherwise suspicious, and missing, shall be reported to the Billing and Settlement Plan Manager, who shall list them in the Industry Automated Authorization System and Loss Prevention Bulletin (LPB) operated by ARINC. The airline name and accounting code number imprinted on such tickets shall be that of the airline which has been supplied with the stock by the Billing and Settlement Plan, or any other airline with which the airline being supplied with the stock has a bilateral agreement to issue tickets on their behalf. Section 1 General 1.7 When the itinerary to be ticketed is e-ticket eligible, and it is technically and/or procedurally feasible, an ET shall be issued.

31 722a T2.18/P Section 2 Specifications A 2.1 FRONT COVER The outside front cover, if any, shall bear the descriptive title Passenger Ticket and Baggage Check, the words Issued By, followed by the name and address of the Member, the words Member of International Air Transport Association, and/ or Air Transport Association of America. When the ticket is printed in Neutral form, i.e. it bears no individual issuing carrier identification, the front cover, if any, shall bear the IATA insignia, the words Passenger Ticket and Baggage Check, and the statement Subject to Notice of Contract Terms Incorporated by Reference in this Ticket, and the statement This Ticket is Not Valid and Will Not be Accepted for Carriage Unless Purchased from the Issuing Carrier or its Authorised Travel Agent. 2.2 COUPONS The OPTAT shall contain the following coupons, the front of which shall have the background colours as specified: Audit Coupon (optional) green; Audit Coupon/Universal Charge Form (optional) white with 1 2 inch green stripe across the top of the coupon (only for use by Members when the OPTAT is used at their own offices); Agent Coupon/Universal Charge Form (optional) white with a 1 2 inch (1.27 cm) pink stripe across the top of the coupon (only for use by BSPs); Universal Charge Form (optional) white; Four Flight Coupons predominantly buff/beige; Agent Coupon (optional) pink; Tax/fee/charge Coupon (optional) pink; Passenger Coupon white. If the Audit and Agent Coupons are not included in the ticket set, facsimiles of them may be printed on plain paper or reproduced from the electronic ticketing record The Audit and Agent coupons shall contain a valid only if issued before overprint indicating the date by which a ticket will no longer be valid for issuance. Such dates shall be deter-mined by IATA IDFS in charge of Billing and Settlement Systems. 722a T2.18/P 2.4 TICKET NOTICES The Warsaw Convention/Montreal Convention Notice and Notice of Contract Terms Incorporated by Reference in this Ticket, the Advice to International Passengers on Limitation of Liability and the Notice of Baggage Liability Limitations, as set forth in Resolution 724, shall be contained in the ticket. Where the OPTAT coupons are provided independently from the ticket notices, such coupons shall include the wording as shown in Attachment C (to be printed on the back of the Passenger Coupon) and shall be delivered to the passenger in the a ticket wallet. as supplied by IATA. This wallet shall contain all mandatory ticket notices. Optionally for carrier issued tickets the mandatory ticket notices may be included as part of the ticket set which is given to the passenger, in which case the ticket set shall incorporate the title Passenger Ticket and Baggage Check, and the wording as shown in Attachment C shall be contained in the ticket. A

32 722a P a T2.18/P 2.4 TICKET NOTICES The Warsaw Convention/Montreal Convention Notice and Notice of Contract Terms Incorporated by Reference in this Ticket, the Advice to International Passengers on Limitation of Liability and the Notice of Baggage Liability Limitations, The Conditions of Contract and Other Important Notices as set forth in Resolution 724, shall be contained in the ticket. Where the OPTAT coupons are provided independently from the ticket notices, such coupons shall include the wording as shown in Attachment C (to be printed on the back of the Passenger Coupon) and shall be delivered to the passenger in the ticket wallet as supplied by IATA. This wallet shall contain all mandatory ticket notices. Optionally for carrier issued tickets the mandatory ticket notices may be included as part of the ticket set which is given to the passenger, in which case the ticket set shall incorporate the title Passenger Ticket and Baggage Check, and the wording as shown in Attachment C shall be contained in the ticket The form code and serial number shall be pre-printed when the OPTAT is used at off premise locations, when two or more Members individually transmit data from their systems for issuance, or the ticket printing device is neither provided nor controlled by a Member., or the OPTAT is used by Passenger Sales Agents in countries/areas where the IATA Billing and Settlement Plan has been implemented. Note: Computer generated document numbers may be used for the issuance of neutral OPTATs in specified countries/areas, provided such documents are issued under the control of a single Member s system. or where a BSP has been adopted for that country/area, under the control of the IATA BSP Manager. When computer generated document numbers are used for issuance of OPTATs, the exchange of sales accounting and ticketing information shall be made available to participating members in the form of the super-long record described in the Billing and Settlement Plan Data Interchange Specifications Handbook. Additionally, to offset the negative effect on carriers that use optical scanning equipment to read document numbers, the above information, as required, shall be provided to those carriers at no extra cost. Secretary note: The words IATA BSP shall be deleted from the published facsimiles if adopted.

33 722a P5.1 Attachment C C NOTICE TO BE CONTAINED IN THE TICKET IF THE LEGAL NOTICES (AS REFERRED TO IN PARAGRAPH 2.4 OF THIS RESOLUTION) ARE NOT CONTAINED IN BUT PROVIDED WITH THE TICKET: AIR TRANSPORTATION If the passenger s journey involves an ultimate destination or stop in a country other than the country of departure the Warsaw Convention or the Montreal Convention may be applicable and these Conventions govern and may limit the liability of carriers for death or bodily injury and in respect of loss of or damage to baggage. Many air carriers have waived the Warsaw limits for death and bodily injury. Further information may be obtained from the carrier. Passengers on a journey involving an ultimate destination or a stop in a country other than the country of departure are advised that international treaties known as the Montreal Convention, or its predecessor, the Warsaw Convention, including its amendments (the Warsaw Convention System), may apply to the entire journey, including any portion thereof within a country. For such passengers, the applicable treaty, including special contracts of carriage embodied in any applicable tariffs, governs and may limit the liability of the carrier. CHECK WITH YOUR CARRIER FOR MORE INFORMATION. With this ticket you will receive a set of notices which forms part of the ticket and contains the Notice of Contract Terms Incorporated by Reference and other important notices Conditions of Contract and Other Important Notices. Please make sure that you have received these notices, and if not, contact the nearest office of the issuing airline or travel agent to obtain copies prior to the commencement of your trip. NON-AIR TRANSPORTATION AND/OR SERVICES Where this ticket is issued for transportation or services other than air travel, specific terms and conditions may apply. These terms and conditions may be included in the ticket set or may be obtained from the issuing company or agent. Filing Period: Effective Date: 18 February June April 2008

34 722c P5.1 T2.25/P T5 0 RESOLUTION 722c AUTOMATED TICKET/BOARDING PASS VERSION 2 (ATB2) (amending) PSC(29)722c Expiry: Indefinite Type: B 722c T5 RESOLVED that: Members may issue the Automated Ticket/Boarding Pass Version 2 (ATB2) as described herein. All of the following specifications define the required characteristics of the fully converted or manufactured document, unless otherwise specified. The Automated Ticket/Boarding Pass Version 2 (ATB2) may also be issued in the form of an Excess Baggage ticket, Miscellaneous Charges Order, or Prepaid Ticket Advice, in accordance with Resolutions 742e, 725c and 731a respectively. 722c P5.1 The provisions of this resolution with regard to the issuance of ATB2 magnetic stripe encoded boarding passes shall expire 31 December TICKET NOTICES 722c T2.25/P The Warsaw Convention/Montreal Convention Notice and Notice of Contract Terms Incorporated by Reference in this Ticket, the Advice to International Passengers on Limitation of Liability and the Notice of Baggage Liability Limitations, The Conditions of Contract and Other Important Notices as set forth in Resolution 724, shall be included as part of the complete ATB2 set which is given to the passenger. This set shall also incorporate the title Passenger Ticket and Baggage Check. The wording as shown in Attachment A shall be printed in English on the back of specified coupons. Optionally, reference to additional notices provided with the ticket may be added NAME OF PASSENGER BOX Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either: (a) double the single letter family name as the family name. For example, Miss Moan Y will be represented as YY/MOANMISS, or (b) combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS.

35 722c P5.1 Attachment A A NOTICE ON BACK OF COUPON (see 2.2) AIR TRANSPORTATION If the passenger s journey involves an ultimate destination or stop in a country other than the country of departure the Warsaw Convention or the Montreal Convention may be applicable and these Conventions govern and may limit the liability of carriers for death or bodily injury and in respect of loss of or damage to baggage. Many air carriers have waived the Warsaw limits for death and bodily injury. Further information may be obtained from the carrier. Passengers on a journey involving an ultimate destination or a stop in a country other than the country of departure are advised that international treaties known as the Montreal Convention, or its predecessor, the Warsaw Convention, including its amendments (the Warsaw Convention System), may apply to the entire journey, including any portion thereof within a country. For such passengers, the applicable treaty, including special contracts of carriage embodied in any applicable tariffs, governs and may limit the liability of the carrier. CHECK WITH YOUR CARRIER FOR MORE INFORMATION. With this ticket you will receive a set of notices which forms part of the ticket and contains the Notice of Contract Terms Incorporated by Reference and other important notices Conditions of Contract and Other Important Notices. Please make sure that you have received these notices, and if not, contact the nearest office of the issuing airline or travel agent to obtain copies prior to the commencement of your trip. NON-AIR TRANSPORTATION AND/OR SERVICES Where this ticket is issued for transportation or services other than air travel, specific terms and conditions may apply. These terms and conditions may be included in the ticket set or may be obtained from the issuing company or agent. Filing Period: Effective Date: 18 February June April 2008

36 722f 722f T2.3/P T2.4/P T2.5/P T2.6/P T2.7/P T2.8/P T2.9/P T2.10/P T2.11/P T2.12/P T2.13/P T2.14/P T2.15/P T2.16/P T2.19/P T3 T4 T11 T12 P2.3 P5.1 T3 0 RESOLUTION 722f ELECTRONIC TICKET AIRLINE (amending) PSC(29)722f 5.5 MESSAGES Expiry: Indefinite Type: B 722f P Unsolicited airport control A message generated by the Validating Carrier to the Marketing Carrier providing airport control of an ET flight coupon(s). This message may also be sent by the Operating Carrier, by including the Billing Carrier Indicator, to advise the Billing Carrier of the Flown Ticket/Coupon(s) information when a special settlement agreement exists. This shall provide the billing carrier the information needed to settle ticket/coupon(s) with the Validating Carrier. Response provide Response comments regarding the ET flight coupon(s) The Validating Carrier shall deliver an Itinerary/Receipt. This document shall include, but not be limited to, the following:... The Notice contained in Resolution 724, Attachment A. A notice with the following wording: Carriage and other services provided by the carrier are subject to conditions of carriage, which are hereby incorporated by reference. These conditions may be obtained from the issuing carrier. Passengers on a journey involving an ultimate destination or a stop in a country other than the country of departure are advised that international treaties known as the Montreal Convention, or its predecessor, the Warsaw Convention, including its amendments (the Warsaw Convention System), may apply to the entire journey, including any portion thereof within a country. For such passengers, the applicable treaty, including special contracts of carriage embodied in any applicable tariffs, governs and may limit the liability of the carrier. Check with your carrier for more information. Further information may be obtained from the carrier. With this ticket you will receive a set of notices which forms part of the ticket and contains the Conditions of Contract and Other Important Notices. Please make sure that you have received these notices, and if not, contact the issuing airline or travel agent to obtain copies prior to the commencement of your trip.

37 722f T12 This Itinerary/Receipt constitutes the passenger ticket for the purposes of Article 3 of the Warsaw Convention and the Montreal Convention, except where the carrier delivers to the passenger another document complying with the requirements of Article 3. (optional) Optionally a 2D bar code compliant with Resolution 792 Bar Coded Boarding Pass may be printed, in order to make the itinerary receipt machine readable at a self-service kiosk for example. The items of the bar code should be populated as much as possible with the data available in the system at the time of issuance. The item 16 should be used and contain the value I standing for Itinerary Receipt so that the check-in application can recognise that the bar code is printed on an Itinerary Receipt and not on a Boarding Pass. 722f P The Validating Carrier 1 shall deliver the notice of contract terms incorporated by reference Conditions of Contract and Other Important Notices contained in Resolution 724, Attachment A, and the legal notices provided for in Resolution 724, Attachments B and C, Resolution 724a, 724b and Resolution f T2.6/P Section 6 Procedures 6.4 CONTROL When the Validating Carrier requests control from the Marketing or Operating Carrier and the Marketing or Operating Carrier database shows that they no longer have control, the Marketing or Operating Carrier shall respond with a positive Change of Status response message. When the Marketing or Operating carrier no longer has the ET in their database, they shall return the error response Ticket number not found and the Validating Carrier shall assume control.

38 722f T2.3/P Attachment A ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS DATA ELEMENTS GLOSSARY AIRLINE DESIGNATOR (VALIDATING CARRIER) 3 ALPHANUMERIC A 722f T2.14/P The two/three character designator identifying the Validating Carrier. (see Resolution definition of Validating Carrier), when different from either the requesting or receiving carrier in a display response message. AROUND THE WORLD FARE INDICATOR 1 ALPHANUMERIC An indicator denoting that the fare is classified as a published/promotional Around the World fare A 722f T2.4/P Y = Around the World fare Blank = Not applicable ASSOCIATED FARE BASIS TICKET DESIGNATOR 15 ALPHANUMERIC A 722f 722f T2.8/P T3 The applicable code as provided for in IATA Resolution 728 for the ET associated to the EMD. BANK EXCHANGE RATE (BBSR) 13 ALPHANUMERIC Banker s buying selling rate used to convert the base amount into the Equivalent Amount Paid. BILLING CARRIER INDICATOR - 1 ALPHANUMERIC A code to indicate the originator of the Unsolicited Airport Control Message is the Operating Carrier when the Billing Carrier is different from the Operating Carrier. A A 722f T4 J = Billing Carrier Indicator. CARRIER FEE DATA Carrier Fee Fare Component Number 2 ALPHANUMERICS (Repeatable Field) This is an absolute number representing the order of the Fare Component within the itinerary to which the Carrier Fee applies. For example 1 means this is the first fare component in the itinerary, 2 means this is the second fare component in the itinerary. Carrier Fee Fare Component Rule Code 3 ALPHANUMERIC (Repeatable Field) A system generated data element indicating the new rule category being referenced by the Carrier Fee purchased (e.g. 031, 033). Carrier Fee Fare Component Rule Number 4 ALPHANUMERIC The new rule number being referenced by the Carrier Fee purchased. Carrier Fee Fare Component Rule Matching Fare Class 8 ALPHANUMERIC The Fare Class Code that must be used when matching alternate category data as specified by the Carrier Fee Fare Rule Code, Carrier Fee Rule Number, and Carrier Fee Tariff Number fields. Data in this field does not specify fare class that must appear on the passenger s ticket.

39 Carrier Fee Fare Component Tariff Number 3 NUMERIC The new tariff number being referenced by the Carrier Fee purchased. Carrier Fee Owner 3 ALPHANUMERIC The two/three character designator representing the carrier whose fee is represented by the Carrier Fee Code. 722f T2.9/P Carrier Fee Reporting Indicator The identifier reflecting the method of pricing for the carrier fee. 1 NUMERIC A 722f 722f T2.8/P T2.19/P 0 = System priced without manual intervention 1 = Priced with manual intervention Carrier Fee Type 2 ALPHANUMERICS (Repeatable Field) A code identifying the type of fee being imposed by a carrier as shown in the IATA Airline Coding Directory. OA = Fee related to booking OB = Fee related to ticketing OC = Fee related to service XP = PTA service charge (applicable to EMD-S only)... CHECKED-IN/LIFTED FLIGHT PREFIX/SUFFIX (MARKETING CARRIER) 1 ALPHA The Marketing Carrier s Flight Prefix/Suffix for each coupon checked-in or lifted A A CHECKED-IN/LIFTED FLIGHT PREFIX/SUFFIX (OPERATING CARRIER) 1 ALPHA The Operating Carrier s Flight Prefix/Suffix for each coupon checked-in or lifted. Present only when the Operating Carrier is different from the Marketing Carrier. 722f T2.11/P COMMISSION TYPE 6 ALPHANUMERIC (Applicable to IATA Only Neutral Resolution) A A code to identify the type of commission applicable to the transaction and associated with the corresponding commission rate or commission amount. A full description of the codes can be found in the Glossary (Chapter 11) of the current version of the BSP Data Interchange Specifications Handbook under data element COTP. Blank CCP CCPPSC N PSC XLP Standard Commission (initial use) The commission amount was calculated on a fare refundable after the cancellation penalty is deducted The commission amount calculated by subtracting the taxes/fees/charges amount(s) from the commission rate and multiplying it by the commission rate (this may apply to either refunds or exchanges) The standard commission amount is calculated on an amount other than the gross fare (excluding taxes/fees/charges). The commission amount has been calculated by multiplying the taxes/fees/charges amount(s) by the commission rate. The commission taken on a cancellation penalty or administrative fee applies to refunds only

40 722f 722f T2.8/P T2.8/P COUPON VALUE 12 ALPHANUMERIC (applicable to 725f and 725g only) The value associated to a single coupon of a miscellaneous document. This amount may shall be preceded by the three-character ISO currency code. EXCESS BAGGAGE DATA ELEMENTS (applicable to 725f and 725g only) A A Currency Code Per Unit 3 ALPHA The ISO code of the currency of calculation. Excess Baggage / Over Allowance Qualifier 1 ALPHA P = PIECES L = POUNDS K = KILOS S = SEATS USED FOR BULKY BAGGAGE Rate Per Unit 12 ALPHANUMERIC The rate being charged per kilo or per pound, per piece or per seat used for bulky baggage. 722f T2.7/P Total Number in Excess 12 ALPHANUMERIC The numeric value for the excess weight, excess pieces or seats used for bulky baggage. FARE COMPONENT CALCULATION Fare Component Agreement Code 15 ALPHANUMERICS The applicable Tour/Value Coding/Contract/Commercial Agreement Reference Code (e.g. as specified in the Category 35 or Category 27) used to price the fare component. These may be different to the codes used in BSP Settlement. A Fare Component Fare Rule Code 3 ALPHANUMERICS (Repeatable Field) (Applicable to Neutral Resolution Only) A system generated data element indicating the ticketed fare is from created by a specified filed fare rule filed (e.g. Category 35-Net Fares) fare sent by the issuing system. This amends the base fare, for example: 019 or C19 = Children Discounts 020 or C20 = Tour Conductor Discounts 021 or C21 = Agent Discounts 022 or C22 = All Other Discounts 025 or C25 = Fare By Rule 035 or C35 = Negotiated Fares

41 722f 722f T2.8/P T2.16/P FARE COMPONENT CALCULATION A series of data elements representing sold data supporting the fare construction applicable to each fare component in a transaction. A fare calculation may include multiple fare components and there may be data elements within each fare component that are repeated, when applicable. When included as data elements on an EMD, the fare component calculation elements apply to the EMD. A fare component is comprised of the following data elements: Fare Component Ticket Designator 15 ALPHANUMERIC (Repeatable field) The applicable code as provided for in ATA SIPP Resolution or IATA Resolution 728. Further ticket designators will be reported at the Fare Component level as matched from a Ticket Discount, ATPCO Category 35, Category 25, or Category A A The following field will be added to the data element glossary: Fare Component Ticket Designator Qualifier 3 ALPHANUMERIC (Repeatable field) 001 = Ticketed Designator 002 = Input Ticket Designator (Pricing) 003 = ATPCO Fare Class Record 01 Ticket Designator 019 = ATPCO Category 19 Ticket Designator 020 = ATPCO Category 20 Ticket Designator 021 = ATPCO Category 21 Ticket Designator 022 = ATPCO Category 22 Ticket Designator 025 = ATPCO Category 25 Ticket Designator 035 = ATPCO Category 35 Ticket Designator 722f T2.12/P Fare Component Construction Principle Indicator 3 ALPHANUMERIC (Repeatable field) A 722f 722f 722f T2.15/P T2.8/P T2.19/P A code identifying a rule used to formulate the fare as identified in SIPP or IATA Resolution 720a, Attachment A (e.g., Surcharge, Stopover/Transfer Charge, Passenger Facility Charge, Mileage Deviation). Alternatively this element may contain LC to denote the inclusion of a ticket discount. Fare Component Coupon Priced RBD 2 ALPHANUMERIC The Reservation Booking Designator at the time of pricing. This may be different from the RBD at the time of ticket issuance. FEE OWNER AIRLINE DESIGNATOR 3 ALPHANUMERIC (applicable to 725f and 725g only) The two/three character designator representing the carrier whose fee was used on the EMD coupon(s). FLOWN FLIGHT PREFIX/SUFFIX (MARKETING CARRIER) 1 ALPHA The Marketing Carrier s Flight Prefix/Suffix for each coupon flown. A A A

42 722f 722f 722f 722f 722f T2.19/P T2.8/P T2.25/P T2.8/P T2.8/P FLOWN FLIGHT PREFIX/SUFFIX (OPERATING CARRIER) 1 ALPHA The Operating Carrier s Flight Prefix/Suffix for each Coupon flown. Present only when the operating Carrier is different from the Marketing Carrier. REDIRECTED FLIGHT PREFIX/SUFFIX 1 ALPHA This field contains the Flight Prefix/Suffix of the Redirected Flight. NON-REISSUEABLE/NON-EXCHANGEABLE INDICATOR 1 ALPHA (applicable to 725f and 725g only) Y = Non-Reissuable/Non-Exchangeable Blank = Not Applicable PASSENGER NAME Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP PRESENT AT 43 ALPHANUMERIC (applicable to 725f and 725g only) Location of service provider. PRESENT TO 43 ALPHANUMERIC (applicable to 725f and 725g only) Name of service provider. PROMOTIONAL CODE 15 ALPHANUMERICS (applicable to 725f and 725g only) A code that indicates which promotion has been applied to a fee. REASON FOR ISSUANCE SUB CODE 3 ALPHANUMERIC (applicable to 725f and 725g only) A secondary code that qualifies the Reason for Issuance Code at the coupon level as sourced from ATPCO for optional service fees or when used for an excess baggage collection as defined below. EXW Excess Weight EXP Excess Pieces EXV Excess Valuation EWV Excess Weight and Excess Valuation EWO Excess Weight and Oversize/Bulky EWP Excess Weight and Excess Pieces EPV Excess Pieces and Excess Valuation OVB Oversize/Bulky OVV Oversize/Bulky and Excess Valuation OTH Other OTV Other and Excess Valuation PET Pet Carriage ANE Angling Equipment GOE Golfing Equipment SKE Skiing Equipment SPE Sporting Equipment A A A A A

43 722f 722f T2.8/P T2.13/P REMARKS - 70 ALPHANUMERIC (Repeatable field) (applicable to 725f and 725g only) Free text describing the service on the EMD at the coupon level (e.g. carriage of antlers). SEGMENT/COUPON IDENTIFIER (Print line B) 2 NUMERICS The sequential number of an individual flight segment or value coupon, e.g. the first segment of a multi-coupon segment ticket or the first value coupon of a multi-coupon EMD. (Print Line B) TAX/FEE/CHARGE DATA AT THE TICKET COUPON LEVEL Cabin 1 ALPHANUMERIC The sold cabin of passenger travel for the coupon. Equipment Code 3 ALPHANUMERICS The standard code of the equipment used for the coupon flight. Journey Turnaround Airport/City Code 5 ALPHANUMERIC The airport/city code which has been assumed to be the journey turnaround point in the construction of the itinerary by the pricing system. Passenger Date of Birth 6 NUMERIC The date of birth of the passenger in the format DDMMYY Tax/fee/charge Amount 12 ALPHANUMERIC (Repeatable field) The tax amount applicable to the Coupon Tax/Fee/Charge Code preceded by the applicable ISO currency code. Tax/fee/charge Code 2 ALPHANUMERIC (Repeatable field) The Tax/Fee/Charge code applicable to the coupon. Arrival and departure taxes will be referenced to the coupon matching the Origin and Destination. Sale taxes will be referenced to coupon 0. Unticketed Point City/Airport Code 5 ALPHANUMERIC The airport or city code identifying an un-ticketed point which occurs between the coupon origin and destination. Un-ticketed point refers to a physical location at which the passenger makes a (potentially taxable) arrival and departure which does not appear in the Good for Passage Area of the ticket. Unticketed Point Date and Local Time of Arrival 11 ALPANUMERIC The date and time of arrival in GMT at the un-ticketed point. Unticketed point refers to a physical location at which the passenger makes a (potentially taxable) arrival and departure which does not appear in the Good for Passage Area of the ticket. Unticketed Point Date and Local Time of Departure 11 ALPHANUMERIC The date and time of departure in GMT from the un-ticketed point. Unticketed point refers to a physical location at which the passenger makes a (potentially taxable) arrival and departure which does not appear in the Good for Passage Area of the ticket.

44 722f T2.8/P Unticketed point departure Equipment Code 3 ALPHANUMERICS The standard code of the equipment used for the coupon flight departing from the unticketed point. TAX ON EMD QUALIFIER - 1 ALPHA An indicator which designates a tax has been collected and is due to local government from the validating carrier of the EMD. T = Tax on EMD Blank = Not Applicable A 722f T2.5/P TOTAL NUMBER OF FLIGHT SEGMENTS / VALUE COUPONS 2 NUMERICS Total Number of flight segments or value coupons included in this transaction. TRANSACTION ACTION 1 ALPHA Defines the purpose of a request/outbound message. Transaction Action Codes are listed in this Glossary. J = Display Indicates a request from an Operating Carrier to a Ground Handler to exhibit information associated with the ET/EMD A

45 722f T2.5/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES Display B* Transaction Action Code D, J 722f T3 Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction NO. CHAR. A, N OR A/N UNSOLICITED AIRPORT CONTROL (INFORMATION ATA ONLY) T (I-ATA only) Action Code---> RESOLUTION 722f REQ RESP Billing Carrier Indicator 1 A/N C 1 722f T2.15/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY UNSOLICI TED AIRPORT CONTROL REQUEST AIRPORT CONTROL req resp req resp req resp Fare Component Coupon Priced RBD 2 A/N C C C. 722f T2.8/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* Segment/Coupon Identifier Total Number of Flight Segments / Value Coupons

46 722f T2.9/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction Carrier Fee Data Carrier Fee Type Carrier Fee Code Carrier Fee Reporting Indicator (Applicable 722g/20.61) No. Char. A, N OR A/N 2 A/N 3 A/N 1 N 722f T2.10/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY UNSOLICI TED AIRPORT CONTROL REQUEST AIRPORT CONTROL req resp req resp req resp Fare Component Calculation Account Code 20 A/N C C C Fare Component Agreement Code 15 A/N C C C 722f T2.19/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY HISTORY DISPLAY CHANGE OF STATUS req resp req resp req resp Checked In/Lifted Flight Prefix/Suffix (Marketing Carrier) 1A O O O Checked In/Lifted Flight Prefix/Suffix (Operating Carrier) 1A O O O Flown Flight Prefix/Suffix (Marketing Carrier) 1A O O O Flown Flight Suffix (Operating Carrier) 1A O O O Redirected Flight Prefix/Suffix 1A O O O

47 722f T2.13/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY UNSOLICI TED AIRPORT CONTROL REQUEST AIRPORT CONTROL req resp req resp req resp Tax/Fee/Charge Data at the Ticket Coupon Level Cabin 1 A/N C C C Equipment Type 3 A/N C C C Journey Turnaround Airport/ City Code 5 A/N C C C Passenger Date of Birth 6 N C C C Tax/Fee/Charge Amount 12 A/N C C C Tax/Fee/Charge Code 2 A/N C C C Unticketed Point City/Airport Code 5 A/N C C C Unticketed Point Date and Local Time of Arrival 11 A/N C C C Unticketed Point Date and Local Time of 11 A/N C C C Departure Unticketed Point Departure Equipment Type 3 A/N C C C 722f T2.14/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY UNSOLICI TED AIRPORT CONTROL REQUEST AIRPORT CONTROL req resp req resp req resp Around the World Fare Indicator 1 A/N C C C.

48 722f T2.16/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY UNSOLICI TED AIRPORT CONTROL REQUEST AIRPORT CONTROL req resp req resp req resp Fare Component Ticket Designator 15 A/N C C C Fare Component Ticket Designator Qualifier 3 A/N C C C. 722f T4 Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722f/20.60 Carrier Fee Data Carrier Fee Type Carrier Fee Owner (Applicable 722g/20.61).. Carrier Fee Tax on Tax Application Code Carrier Fee Fare Component Number (Applicable 722g/20.61) Carrier Fee Fare Component Rule Code (Applicable 722g/20.61) Carrier Fee Fare Component Rule Number (Applicable 722g/20.61) Carrier Fee Fare Component Tariff Number (Applicable 722g/20.61) Carrier Fee Fare Component Rule Matching Fare Class (Applicable 722g/20.61) Certificate Number. No. Char. A, N OR A/N 2 A/N 3 A/N 2 A/N 2 A/N 3 A/N 4 A/N 3 N 8 A/N 14 A/N

49 722f T11 Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code --- > Flown Airline Designator (Marketing Carrier) Flown Airline Designator (Operating Carrier) Flown Destination Airport/City Code Flown Origin Airport/City Code NO CHAR. A, N OR A/N ISSUANCE (INFORMAT ION ATA ONLY) DISPLAY HISTORY DISPLAY EXCHANGE/ REISSUE REFUND SYSTEM CANCEL REFUND CANCEL S (I-ATA only) D H E R X,Y Z V,W REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP 3 A/N O O 3 A/N O O 5 A/N O O 5 A/N O O VOID Filing Period: Effective Date: 18 February June April 2008

50 722g T2.2/P T2.4/P T2.8/P T2.9/P T2.10/P T2.13/P T2.14/P T2.15/P T2.16/P T2.19/P T2.22/P T3 T4 T11 T12 P2.3 P5.1 0 RESOLUTION 722g ELECTRONIC TICKET NEUTRAL (amending) PSC(29)722g 722g P2.3 Section 5 Technical Specifications Expiry: Indefinite Type: B 722g T FORM CODES Electronic Ticket The form code for an Electronic Ticket (ET) shall be the same as the computer generated form code for the Off-Premise Automated Ticket/Boarding Pass (OPATB) or the Off-Premise Transitional Automated Ticket (OPTAT) as shown in Recommended Practice 1720a, Attachment A The issuing travel agency shall deliver an Itinerary/Receipt. This document shall include, but not be limited to the following: This Itinerary/Receipt constitutes the passenger ticket for the purposes of Article 3 of the Warsaw Convention and the Montreal Convention, except where the carrier delivers to the passenger another document complying with the requirements of Article 3. (optional) Optionally a 2D bar code compliant with Resolution 792 Bar Coded Boarding Pass may be printed, in order to make the itinerary receipt machine readable at a self-service kiosk for example. The items of the bar code should be populated as much as possible with the data available in the system at the time of issuance. The item 16 should be used and contain the value I standing for Itinerary Receipt so that the check-in application can recognise that the bar code is printed on an Itinerary Receipt and not on a Boarding Pass

51 722g P The issuing travel agency shall deliver an Itinerary/Receipt(s). The document(s) shall include, but not be limited to, the following: The Notice contained in Resolution 724, Attachment A. A notice with the following wording: Carriage and other services provided by the carrier are subject to conditions of carriage, which are hereby incorporated by reference. These conditions may be obtained from the issuing carrier. Passengers on a journey involving an ultimate destination or a stop in a country other than the country of departure are advised that international treaties known as the Montreal Convention, or its predecessor, the Warsaw Convention, including its amendments (the Warsaw Convention System), may apply to the entire journey, including any portion thereof within a country. For such passengers, the applicable treaty, including special contracts of carriage embodied in any applicable tariffs, governs and may limit the liability of the carrier. Check with your carrier for more information The Validating Carrier 1, or when the electronic ticket is issued by a travel agent, the issuing travel agent, shall deliver the notice of contract terms incorporated by reference Conditions of Contract and Other Important Notices contained in Resolution 724, Attachment A, and the legal notices for in Resolution 724, Attachments B and C, Resolution 724b and Resolution 745.

52 722g T2.8/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* Segment / Coupon Identifier Total Number of Flight Segments/Value Coupons 722g T2.9/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY RESOLUTION 722G Carrier Fee Data Carrier Fee Type 2 A/N C C C Carrier Fee Code 3 A/N C C C Carrier Fee Reporting Indicator 1 N C C C D EXCHANG E/ REISSUE E 722g T2.10/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 722G Fare Component Calculation Account Code 20 A/N C C C Fare Component Agreement Code 15 A/N C C C E

53 722g T2.2/P Attachment B ELECTRONIC TICKET AND MISCELLANEOUS DOCUMENTS MESSAGE CONSTRUCTION MATRIX - NEUTRAL B* ELEMENT DESCRIPTION Transaction NO CHAR. A, N OR A/N ISSUE DISPLAY HISTORY DISPLAY EXCHANGE/ REISSUE REFUND Action code ---> S D H E R RESOLUTION 722 g / REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP CHECKED-IN/LIFTED AIRLINE DESIGNATOR (MARKETING CARRIER) 3 A/N O O CHECKED-IN/LIFTED AIRLINE DESIGNATOR (OPERATING CARRIER) 3 A/N O O CHECKED-IN/LIFTED DESTINATION AIRPORT/CITY CODE 5 A/N O O CHECKED-IN/LIFTED ORIGIN AIRPORT/CITY CODE 5 A/N O O DOCUMENT TYPE 1 A M C M C C C FARE CALCULATION PRICING INDICATOR 1 A/N M C M C FARE CALCULATION REPORTING INDICATOR 1 N M C M C FLOWN AIRLINE DESIGNATOR (MARKETING CARRIER) FLOWN AIRLINE DESIGNATOR (OPERATING CARRIER) 3 A/N O O 3 A/N O O FLOWN DESTINATION AIRPORT/CITY CODE 5 A/N O O FLOWN ORIGIN AIRPORT/CITY CODE 5 A/N O O SOURCE OF APPROVAL CODE 1 A/N C C C C C

54 722g T2.13/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANG E/ REISSUE req resp req resp req resp RESOLUTION 722g Tax/Fee Charge Data at the Ticket Coupon Level Cabin 1 A/N C C C Equipment Type 3 A/N C C C Journey Turnaround Airport/ City Code 5 A/N C C C Passenger Date of Birth 6 N C C C Tax/Fee/Charge Amount 12 A/N C C C Tax/Fee/Charge Code 2 A/N C C C Unticketed Point City/Airport Code 5 A/N C C C Unticketed Point Date and Local Time of Arrival 11 A/N C C C Unticketed Point Date and Local Time of 11 A/N C C C Departure Unticketed Point Departure Equipment Type 3 A/N C C C E 722g T2.14/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req Resp RESOLUTION 722G Around the World Fare Indicator 1 A/N C C C. E

55 722g T2.15/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 722G Fare Component Coupon Priced RBD 2 A/N C C C. E 722g T2.16/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 722G Fare Component Ticket Designator 15 A/N C C C Fare Component Ticket Designator Qualifier 3 A/N C C C. E

56 722g T2.19/P Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Checked In/Lifted Flight Prefix/Suffix (Marketing Carrier) (Applicable 722f/722h/20.60/20.63) Checked In/Lifted Flight Prefix/Suffix (Operating Carrier) (Applicable 722f/722h/20.60/20.63 Flown Flight Prefix/Suffix (Marketing Carrier) (Applicable 722f/722h/20.60/20.63 Flown Flight Suffix (Operating Carrier) (Applicable 722f/722h/20.60/20.63 Redirected Flight Prefix/Suffix (Applicable 722f/722h/20.60/20.63 No. Char. A, N OR A/N 1A 1A 1A 1A 1A 722g T3 Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction NO. CHAR. A, N OR A/N UNSOLICITED AIRPORT CONTROL (INFORMATION ATA ONLY) T (I-ATA only) Action Code---> RESOLUTION 722g REQ RESP Billing Carrier Indicator 1 A/N (Applicable 722f)

57 722g T4 Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY HISTORY DISPLAY EXCHANG E/ REISSUE D H E RESOLUTION 722G Carrier Fee Data Carrier Fee Type 2 A/N C C C Carrier Fee Owner 3 A/N C C C.. Carrier Fee Tax on Tax Application Code 2 A/N C C C Carrier Fee Fare Component Number 2 A/N C C C Carrier Fee Fare Component Rule Code 3 A/N C C C Carrier Fee Fare Component Rule Number 4 A/N C C C Carrier Fee Fare Component Tariff Number 3 N C C C Carrier Fee Fare Component Rule Matching 8 A/N C C C Fare Class Certificate Number 14 A/N C C C C. 722g T11 Attachment B MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code --- > Flown Airline Designator (Marketing Carrier) Flown Airline Designator (Operating Carrier) Flown Destination Airport/City Code NO CHAR. A, N OR A/N ISSUANCE (INFORMAT ION ATA ONLY) DISPLAY HISTORY DISPLAY EXCHANGE/ REISSUE REFUND SYSTEM CANCEL REFUND CANCEL S (I-ATA only) D H E R X,Y Z V,W REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP 3 A/N O O 3 A/N O O 5 A/N O O VOID Flown Origin Airport/City Code 5 A/N O O Filing Period: Effective Date: 18 February June April 2008

58 722h T2.5/P T2.9/P T2.10/P T2.13/P T2.14/P T2.15/P T2.16/P T2.19/P T2.31/P T3 T4 T11 0 RESOLUTION 722h ELECTRONIC TICKET/ELECTRONIC MISCELLANEOUS DOCUMENTS GROUND HANDLING (amending) PSC(29)722h Expiry: Indefinite Type: B 722h T2.5/P 5.3 MESSAGES 722h 722h T2.5/P T2.9/P Display Request from a Ground Handler to a carrier or from an Operating Carrier to a Ground Handler to retrieve data elements necessary to display the complete record of the ET/EMD including flight/value Coupon Status Indicator(s). Response provides data elements necessary to display the complete record, display a similar record list or denies the request. Section 6 Procedures 6.2 DISPLAY 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 it s 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. When the Display Request is initiated by the Operating Carrier to the Ground Handler, transaction action J shall be used. Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Carrier Fee Data Carrier Fee Type Carrier Fee Code Carrier Fee Reporting Indicator (Applicable 722g/20.61) No. Char. A, N OR A/N 2 A/N 3 A/N 1 N

59 722h T2.10/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722H Fare Component Calculation Account Code Fare Component Agreement Code (Applicable 722f/722g/20.60/20.61) No. Char. A, N OR A/N 20 A/N 15 A/N 722h T2.13/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722h Tax/Fee/Charge Data at the Ticket Coupon Level Cabin (Applicable 722f/722g/20.60/20.61) Equipment Type (Applicable 722f/722g/20.60/20.61) Journey Turnaround Airport/ City Code (Applicable 722f/722g/20.60/20.61) Passenger Date of Birth (Applicable 722f/722g/20.60/20.61) Tax/Fee/Charge Amount (Applicable 722f/722g/20.60/20.61) Tax/Fee/Charge Code (Applicable 722f/722g/20.60/20.61) Tax Coupon Unticketed Point City/Airport Code (Applicable 722f/722g/20.60/20.61) Unticketed Point Date and Local Time of Arrival (Applicable 722f/722g/20.60/20.61) Unticketed Point Date and Local Time of Departure (Applicable 722f/722g/20.60/20.61) Unticketed Point Departure Equipment Type (Applicable 722f/722g/20.60/20.61) No. Char. A, N OR A/N 1 A/N 3 A/N 5 A/N 6 N 12 A/N 2 A/N 5 A/N 11 A/N 11 A/N 3 A/N

60 722h T2.14/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722H Around the World Fare Indicator (Applicable 722f/722g/20.60/20.61). No. Char. A, N OR A/N 1 A/N 722h T2.15/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722H Fare Component Coupon Priced RBD (Applicable 722f/722g/20.60/20.61). No. Char. A, N OR A/N 2 A/N 722h T2.16/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722H Fare Component Ticket Designator (Applicable 722f/722g/20.60/20.61) Fare Component Ticket Designator Qualifier (Applicable 722f/722g/20.60/20.61). No. Char. A, N OR A/N 15 A/N 3 A/N

61 722h T2.19/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY CHANGE OF STATIUS REDIRECT AIRPORT Control UNSOLICITE D AIRPORT CONTROL GROUND HANDLING req resp req resp req resp req resp Checked In/Lifted Flight Prefix/Suffix (Marketing Carrier) 1A C C Checked In/Lifted Flight Prefix/Suffix (Operating Carrier) 1A C C Flown Flight Prefix/Suffix (Marketing Carrier) 1A C C Flown Flight Suffix (Operating Carrier) 1A C C Redirected Flight Prefix/Suffix 1A C C 8 722h T3 Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction NO. CHAR. A, N OR A/N UNSOLICITED AIRPORT CONTROL (INFORMATION ATA ONLY) T (I-ATA only) Action Code---> RESOLUTION 722h REQ RESP Billing Carrier Indicator 1 A/N (Applicable 722f)

62 722h T2.31/P Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction NO. CHAR' A, N OR A/N. REQUEST AIRPORT CONTROL EMERGENCY LOCK UNSOLICITED AIRPORT CONTROL Action Code ---> B M T Resolution 722h REQ RESP REQ RESP REQ RESP Coupon/Itinerary Sequence Number 2 A/N C C C Ticket Type Indicator 3 A/N O O Transaction Agent I.D. 11 A/N M M M M 722h T4 Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 722h/20.62 Carrier Fee Data Carrier Fee Type Carrier Fee Owner (Applicable 722g/20.61).. Carrier Fee Tax on Tax Application Code Carrier Fee Fare Component Number (Applicable 722g/20.61) Carrier Fee Fare Component Rule Code (Applicable 722g/20.61) Carrier Fee Fare Component Rule Number (Applicable 722g/20.61) Carrier Fee Fare Component Tariff Number (Applicable 722g/20.61) Carrier Fee Fare Component Rule Matching Fare Class (Applicable 722g/20.61) Certificate Number. No. Char. A, N OR A/N 2 A/N 3 A/N 2 A/N 2 A/N 3 A/N 4 A/N 3 N 8 A/N 14 A/N

63 722h T11 Attachment B MESSAGE CONSTRUCTION MATRIX GROUND HANDLING B* ELEMENT DESCRIPTION Transaction Action Code --- > Flown Airline Designator (Marketing Carrier) Flown Airline Designator (Operating Carrier) Flown Destination Airport/City Code Flown Origin Airport/City Code NO CHAR. A, N OR A/N ISSUANCE (INFORMAT ION ATA ONLY) DISPLAY HISTORY DISPLAY EXCHANGE/ REISSUE REFUND SYSTEM CANCEL REFUND CANCEL S (I-ATA only) D H E R X,Y Z V,W REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP REQ RESP 3 A/N O O 3 A/N O O 5 A/N O O 5 A/N O O VOID Filing Period: Effective Date: 18 February June April 2008

64 725a T2.21/P T2.25/P 0 RESOLUTION 725a MISCELLANEOUS CHARGES ORDER (MCO) ISSUANCE AND HONOURING PROCEDURES BY MEMBERS (amending) 725a 725a 725a T2.21/P T2.25/P T2,21.P PSC(29)725a Expiry: Indefinite Type: B Deduction Method (not applicable to Stand Alone Electronic Miscellaneous Documents (EMD-S) 2.2 ENTRIES Name of Passenger Box Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either; double the single letter family name as the family name. For example, Miss Moan Y will be represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS Coupon Value Box A multi-coupon MCO may be issued by either the Specific Exchange Coupon Value method or by the Deduction Method. The two methods shall not be combined on the same MCO. The Deduction method shall not be applicable to Stand Alone Electronic Miscellaneous Documents (EMD-S) issued for residual value Deduction method: (Applicable to paper documents) (a) make no entries in Coupon Value boxes; (b) enter an X in the Value For Which Honoured To Be Deducted From Original or Residual Value box. Note: NUCs are not a currency and are not to be entered in this box. 3.3 DEDUCTION METHOD The Deduction method shall not be applicable to Stand Alone Electronic Miscellaneous Documents (EMD-S) issued for residual value. Filing Period: Effective Date: 18 February June April 2008

65 725b T2.21/P T2.25/P 0 RESOLUTION 725b MISCELLANEOUS CHARGES ORDER (MCO) ISSUANCE AND HONOURING PROCEDURES (AGENTS) (amending) 725b T2.25/P PSC(29)725b 2.2 ENTRIES Name of Passenger Box Expiry: Indefinite Type: B Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either double the single letter family name as the family name. For example, Miss Moan Y will be represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS. 725b T2.21/P 3.3 DEDUCTION METHOD/ EXCHANGE COUPONS ISSUED BY A MEMBER The Deduction method shall not be applicable to Stand Alone Electronic Miscellaneous Documents (EMD-S) issued for residual value. Filing Period: Effective Date: 18 February June April 2008

66 725f T2.1/P T2.4/P T2.8/P T2.9/P T2.10/P T2.13/P T2.14/P T2.15/P T2.16/P T2.21/P T2.22/P T2.23/P T2.24/P 0 RESOLUTION 725f ELECTRONIC MISCELLANEOUS DOCUMENT - AIRLINE (amending) PSC(29)725f Expiry: Indefinite Type: B 725f T2.8/P In order to change an EMD-A to an EMD-S or vice versa, the document shall be exchanged Each EMD shall be issued with only one Reason For Issuance Code. ** renumber f 725f 725f T2.24/P T2.8/P T2.22/P The Validating Carrier shall deliver a Receipt. This document shall include, but not be limited to: A notice with the following wording Where this document is issued for transportation, or services other than passenger air transportation, specific terms and conditions may apply. These terms and conditions may be provided separately or may be obtained from the issuing company or agent The Terms and Conditions Notice shall be provided to the passenger or purchaser in accordance with the requirements of Resolution 725 Attachment F, or Resolution 726 Attachment A., as applicable Systems shall provide for 99 occurrences of the tax/fee/charge amount data element and 99 occurrences of each associated tax/fee/charge qualifier 1 in accordance with standard PADIS messages. ** renumber Section 6 - Procedures 6.2 ISSUANCE EMD-Stand-alone An EMD-S shall be limited to one passenger or, in the case of payment of a deposit, a group name. only.

67 725f 725f 725f 725f T2.21/P T2.8/P T2.8/P T2.8/P Section 6 - Procedures 6.2 ISSUANCE EMD-Stand-alone The deduction method shall not be applicable to EMD-S issued for residual value The Validating Carrier shall verify that the corresponding flight coupon(s) in the ET record are in a status other than Final or Suspend Status before issuing the EMD-A When the ET flight coupon(s) are not at final or suspend status, the receiving system shall not deny the System Update request. When the corresponding ET flight coupon(s) are at final or suspend status, the receiving system shall deny the System Update request Association initiated by the Operating Carrier of the EMD The EMD-A shall only be associated by the Operating Carrier when there is no change of route or operating carrier(s) The Operating Carrier shall send a System Update message to the Validating Carrier of the EMD-A to request the association of the EMD-A value coupon(s) to the corresponding ET flight coupon(s). ** renumber Upon receipt of System Update message from the Operating Carrier, the Validating Carrier of the EMD-A shall update the EMD-A with the new In Connection with Document Number and the new In Connection With Coupon Number and amend the In Connection With Qualifier to indicate the EMD-A is associated The Validating Carrier of the EMD-A shall send a system update message to the Validating Carrier of the ET to request the association of the EMD-A value coupon(s) to the corresponding ET flight coupon(s) Where control of the corresponding EMD-A value coupon(s) has already been passed to an Operating Carrier, the Validating Carrier of EMD-A shall send the system update message to the Operating Carrier(s) to advise of the association of the new EMD-A value coupon(s) to the ET flight coupon(s). The Validating Carrier is not required to send the system update message to the Operating Carrier who initiated the request.

68 725f T2.1/P Section 6 Procedures 6.3 SYSTEM UPDATE Upon receipt of the System Update message from the Validating Carrier of the EMD-A, the Validating Carrier of the ET and the Operating Carrier(s) shall update the ET record to remove the In Connection With Document Number and In Connection With Coupon Number amend the In Connection With Qualifier to indicate that the EMD-A is disassociated Upon receipt of the System Update message from the Operating Carrier, the Validating Carrier of the EMD-A shall update the EMD-A record to remove the In Connection With Document Number and In Connection With Coupon Number amend the In Connection With Qualifier to indicate that the ET is disassociated Upon receipt of the System Update message from the Validating Carrier of the ET, the Validating Carrier of the EMD-A shall update the EMD-A its ET record to remove the In Connection With Document Number and In Connection With Coupon Number amend the In Connection With Qualifier to indicate that the ET is disassociated. 725f T2.21/P 6.7 EXCHANGE/REISSUE EMD-Stand-alone The deduction method shall not be applicable to EMD-S issued for residual value.

69 725f T2.4/P Attachment B MISCELLANEOUS DOCUMENTS MESSAGE CONSTRUCTION MATRIX - AIRLINE B* ELEMENT DESCRIPTION Transaction NO CHAR. A, N OR A/N DISPLAY REQUEST AIRPORT CONTROL Action code - D B RESOLUTION 725 f / REQ REQ REQ RESP Fare Basis/Ticket Designator 15 A/N C M Associated Fare Basis/Ticket Designator 15 A/N 725f T2.10/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY REQUEST AIRPORT CONTROL req resp Req resp Fare Component Calculation Account Code 20 A/N C C Fare Component Agreement Code 15 A/N C C

70 725f T2.13/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY REQUEST AIRPORT CONTROL req resp req resp Tax/Fee Charge Data at the Ticket Coupon Level Cabin 1 A/N C C Equipment Type 3 A/N C C Journey Turnaround Airport/ City Code 5 A/N C C Passenger Date of Birth 6 N C C Tax/Fee/Charge Amount 12 A/N C C Tax/Fee/Charge Code 2 A/N C C Unticketed Point City/Airport Code 5 A/N C C Unticketed Point Date and Local Time of Arrival 11 A/N C C Unticketed Point Date and Local Time of 11 A/N C C Departure Unticketed Point Departure Equipment Type 3 A/N C C 725f T2.9/P Attachment B MISCELLANEOUS DOCUMENTS MESSAGE CONSTRUCTION MATRIX - AIRLINE B* ELEMENT DESCRIPTION Transaction Carrier Fee Data Carrier Fee Type Carrier Fee Code Carrier Fee Reporting Indicator (Applicable 725g/20.64) No. Char. A, N OR A/N 2 A/N 3 A/N 1 N

71 725f T2.14/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction Around the World Fare Indicator (Applicable 722f/722g/20.60/20.61) No. Char. A, N OR A/N 1 A/N 725f T2.15/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY REQUEST AIRPORT CONTROL req resp req resp Fare Component Coupon Priced RBD 2 A/N C C 725f T2..16/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* ELEMENT DESCRIPTION Transaction No. Char. A, N OR A/N DISPLAY REQUEST AIRPORT CONTROL req resp req resp Fare Component Ticket Designator 15 A/N C C Fare Component Ticket Designator Qualifier 3 A/N C C

72 725f T2.8/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* Data Element Characters A, N, or A/N Display Request Airport Control Change of Status System Update Transaction Action Code D B C U 20.63/725f Req Resp Req Resp Req Resp Req Resp Carrier Fee Data: (Applicable 20.64/ 725g) Carrier Fee Type (Applicable 20.64/ 725g) 2 A/N Carrier Fee Code (Applicable 20.64/ 725g) 2 A/N Carrier Fee Amount (Applicable 20.64/ 725g) 12 A/N Carrier Fee Application Code (Applicable 20.64/ 725g) 2 A/N Carrier Fee From Airport/City Code (Applicable 20.64/ 725g) 5 A/N Carrier Fee To Airport/City Code (Applicable 20.64/ 725g) 5 A/N Carrier Fee Form of Payment Type (Applicable 20.64/ 725g) 24 A/N Carrier Fee Form of Payment Credit Card Vendor Code (Applicable 20.64/ 725g) 2 A Carrier Fee Form of Payment Credit Card Account Number (Applicable 20.64/ 725g) 25 A/N Carrier Fee Approval Code (Credit Card) (Applicable 20.64/ 725g) 6 A/N Carrier Fee Expiry Date (Applicable 20.64/ 725g) 4 N Carrier Fee Tax Code (Applicable 20.64/ 725g) 2 A/N Carrier Fee Tax Amount (Applicable 20.64/ 725g) 12 A/N Carrier Fee Tax Currency Code (Applicable 20.64/ 725g) 3 A Carrier Fee Tax Application Code (Applicable 20.64/ 725g) 2 A/N Carrier Fee Tax on Tax Code (Applicable 20.64/ 725g) 2 A/N Carrier Fee Tax on Tax Amount (Applicable 20.64/ 725g) 12 A/N Carrier Fee Tax on Tax Currency Code (Applicable 20.64/ 725g) 3 A/N Carrier Fee Tax on Tax Application Code (Applicable 20.64/ 725g) 2 A/N

73 725f T2.8/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* Data Element Characters A, N, or A/N Display Request Airport Control Change of Status System Update Transaction Action Code D B C U 20.63/725f Req Resp Req Resp Req Resp Req Resp Excess Baggage Data Elements Currency Code per Unit 3 A C C Excess Baggage/ Over Allowance Qualifier 1 A C C Rate per Unit 12 A/N C C Total Number in Excess 12 A/N C C... Fare Component Calculation Elements 12 Fee Owner Airline Designator 3 A/N C C Non-Reissuable/Non-Exchangeable Indicator 1 A C C Promotional Code 15 A/N C C Reason For Issuance Service Sub Code 3 A/N C C Remarks 70 A/N C C Segment / Coupon Identifier 2 N C M Tax on EMD Qualifier 1 A C C Total Number of Flight Segments / Value Coupons 2 N C M NOTES: 12. To be used when Fare Component Calculation Elements apply to the EMD

74 725f T2.23/P Attachment B MESSAGE CONSTRUCTION MATRIX AIRLINE MESSAGES B* Data Element Characters A, N, or A/N Display Request Airport Control Change of Status System Update Transaction Action Code D B C U 20.63/725f Req Resp Req Resp Req Resp Req Resp Agent Pseudo City Code 8 N C C Booking Agent Identification 6 A/N C C Coupon Value 12 A/N C 1 C 1 Flown Airline Designator (Marketing Carrier) 3 A/N O C Flown Airline Designator (Operating Carrier) 3 A/N O C Flown Destination Airport/City Code 5 A/N O C Flown Origin Airport/City Code 5 A/N O C Non-Refundable/No Value/Penalty Amount Non-Refundable Amount Qualifier/No Value Amount Qualifier/Penalty Amount Qualifier 12 A/N O O O 2 A O O O Passenger Name 49 A/N O 2 C C M Settlement Authorisation Code 14 A/N C C 5 Soled Airline Designator (Marketing Carrier) 3A/N O 2 C M C Ticket Handledr Airline Designator 3 A/N C C C C Total Number of Flight Segments 2 N C M C Filing Period: Effective Date: 18 February June April 2008

75 725g 725g 725g T2.4/P T2.8/P T2.9/P T2.10/P T2.13/P T2.14/P T2.15/P T2.16/P T2.21/P T2.22/P T2.23/P T2.24/P T2.8/P T2.24/P 0 RESOLUTION 725g ELECTRONIC MISCELLANEOUS DOCUMENT - NEUTRAL (amending) PSC(29)725g Expiry: Indefinite Type: B In order to change an EMD-A to an EMD-S or vice versa, the document shall be exchanged Each EMD shall be issued with only one Reason For Issuance Code. ** renumber Systems shall provide for 99 occurrences of the tax/fee/charge amount data element and 99 occurrences of each associated tax/fee/charge qualifier1 in accordance with standard PADIS messages The corresponding flight coupon(s) in the ET record shall be in a status other than Final or Suspend Status before issuing the EMD-A The issuing travel agency shall deliver a Receipt. This document shall include, but not be limited to: A notice with the following wording Where this document is issued for transportation, or services other than passenger air transportation, specific terms and conditions may apply. These terms and conditions may be provided separately or may be obtained from the issuing company or agent The Terms and Conditions Notice shall be provided to the passenger or purchaser in accordance with the requirements of. Resolution 725 Attachment F, or Resolution 726 Attachment A, as applicable.

76 725g T2.21/P Section 6 - Procedures 6.2 ISSUANCE EMD-Stand-alone The deduction method shall not be applicable to EMD-S issued for residual value. 725g T2.22/P Section 6 - Procedures 6.2 ISSUANCE EMD-Stand-alone An EMD-S shall be limited to one passenger or, in the case of payment of a deposit, a group name. only. 725g T2.21/P 6.4 EXCHANGE/REISSUE EMD-Stand-alone The deduction method shall not be applicable to EMD-S issued for residual value. 725g T2.4/P Attachment B MISCELLANEOUS DOCUMENTS MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction NO CHAR. A, N OR A/N ISSUE DISPLAY HISTORY DISPLAY EXCHANGE/ REISSUE REFUND Action code ---> S D H E R RESOLUTION 725 g / REQ RES P REQ REQ REQ RESP REQ RESP REQ RESP Fare Basis/Ticket Designator 15 A/N M C M C C Associated Fare Basis/Ticket Designator 15 A/N

77 725g T2.8/P Attachment B MISCELLANEOUS DOCUMENTS MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* 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 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 Carrier Fee Data: Carrier Fee Type 2 A/N C C C Carrier Fee Code 2 A/N C C C Carrier Fee Amount 12 A/N C C C Carrier Fee Application Code 2 A/N C C C Carrier Fee From Airport/City Code 5 A/N C C C Carrier Fee To Airport/City Code) 5 A/N C Carrier Fee Form of Payment Type 24 A/N C C C Carrier Fee Form of Payment Credit 2 A C C C Card Vendor Code Carrier Fee Form of Payment Credit 25 A/N C C C Card Account Number Carrier Fee Approval Code (Credit Card)) 6 A/N C Carrier Fee Expiry Date 4 N C C C Carrier Fee Tax Code 2 A/N C C C Carrier Fee Tax Amount 12 A/N C C C Carrier Fee Tax Currency Code 3 A C C C Carrier Fee Tax Application Code 2 A/N C C C Carrier Fee Tax on Tax Code 2 A/N C C C Carrier Fee Tax on Tax Amount 12 A/N C C C Carrier Fee Tax on Tax Currency Code 3 A/N C C C Carrier Fee Tax on Tax Application Code 2 A/N C C C VOID Notes : 1 Mandatory when used to cancel an Exchange/Reissue Message. 2 See resolution text for required combination of search criteria 6.3 Display 3 Used by the validating Carrier to locate the document(s) being exchanged. 4 If a paper ticket is issued, the Coupon Status indicator T is mandatory. 5 This data element shall not be sent in an Information Message. 6 This data element applies to the new ticket. All other data elements in the Response Message applies to the ticket coupon being exchanged 7 To be used when Fare Component Calculation Elements apply to the EMD A = ALPHABETIC CHARACTERS ONLY M = MANDATORY (must provide at all times) N = NUMERIC CHARACTERS ONLY C = CONDITIONAL (must provide if available/applicable) A/N = ALPHABETICAL AND NUMERIC CHARACTERS ALLOWED O = OPTIONAL

78 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 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 Excess Baggage Data Elements Currency Code per Unit 3 A C C C C C Excess Baggage/ Over Allowance Qualifier 1 A C C C C C Rate per Unit 12 A/N C C C C C Total Number in Excess 12 A/N C C C C C... Fare Component Calculation Elements 7... Fee Owner Airline Designator 3 A/N C C C C C Non-Reissuable/Non-Exchangeable Indicator 1 A C C C C C Promotional Code 15 A/N C C C C C Reason For Issuance Service Sub Code 3 A/N C C C C C Remarks 70 A/N C C C C C Segment / Coupon Identifier 2 N M C M O O Tax on EMD Qualifier 1 A C C C C C Total Number of Flight Segments/ Value Coupons 2 N M C M M M VOID Notes : 1 Mandatory when used to cancel an Exchange/Reissue Message. 2 See resolution text for required combination of search criteria 6.3 Display 3 Used by the validating Carrier to locate the document(s) being exchanged. 4 If a paper ticket is issued, the Coupon Status indicator T is mandatory. 5 This data element shall not be sent in an Information Message. 6 This data element applies to the new ticket. All other data elements in the Response Message applies to the ticket coupon being exchanged 7 To be used when Fare Component Calculation Elements apply to the EMD A = ALPHABETIC CHARACTERS ONLY M = MANDATORY (must provide at all times) N = NUMERIC CHARACTERS ONLY C = CONDITIONAL (must provide if available/applicable) A/N = ALPHABETICAL AND NUMERIC CHARACTERS ALLOWED O = OPTIONAL

79 725g T2.9/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY RESOLUTION 725G Carrier Fee Data Carrier Fee Type 2 A/N C C C Carrier Fee Code 3 A/N C C C Carrier Fee Reporting Indicator 1 N C C C D EXCHANG E/ REISSUE E 725g T2.10/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 725G Fare Component Calculation Account Code 20 A/N C C C Fare Component Agreement Code 15 A/N C C C E

80 725g T2.13/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 725G Tax/Fee/Charge Data at the Ticket Coupon Level Cabin 1 A/N C C C Equipment Type 3 A/N C C C Journey Turnaround Airport/ City Code 5 A/N C C C Passenger Date of Birth 6 N C C C Tax/Fee/Charge Amount 12 A/N C C C Tax/Fee/Charge Code 2 A/N C C C Unticketed Point City/Airport Code 5 A/N C C C Unticketed Point Date and Local Time of Arrival 11 A/N C C C Unticketed Point Date and Local Time of 11 A/N C C C Departure Unticketed Point Departure Equipment Type 3 A/N C C C E 725g T2.14/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code RESOLUTION 725G Around the World Fare Indicator (Applicable 722f/722g/20.60/20.61) No. Char. A, N OR A/N 1 A/N

81 725g T2.15/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 725G Fare Component Coupon Priced RBD 2 A/N C C C E 725g T2.16/P Attachment B ELECTRONIC MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code No. Char. A, N OR A/N ISSUANCE (INFORMA TION ATA ONLY) S (I-ATA only) DISPLAY D EXCHANGE/ REISSUE req resp req resp req resp RESOLUTION 725G Fare Component Ticket Designator 15 A/N C C C Fare Component Ticket Designator Qualifier 3 A/N C C C E

82 725g T2.23/P Attachment B MESSAGE MISCELLANEOUS DOCUMENT MESSAGE CONSTRUCTION MATRIX- NEUTRAL MESSAGES B* ELEMENT DESCRIPTION Transaction Action Code -- -> RESOLUTION 725 G Flown Airline Designator (Marketing Carrier) Flown Airline Designator (Operating Carrier) Flown Destination Airport/City Code NO CHAR. A, N OR A/N ISSUANCE (INFORMAT ION ATA ONLY) S (I-ATA only) REQ RES P DISPLAY REQ HISTORY DISPLAY EXCHANGE/ REISSUE REFUND SYSTEM CANCEL REFUND CANCEL D H E R X,Y Z V,W RES P 3 A/N O O 3 A/N O O 5 A/N O O REQ RESP REQ RESP RE Q RES P VOID REQ RESP REQ RESP REQ RES P Flown Origin Airport/City Code 5 A/N O O Filing Period: Effective Date: 18 February June April 2008

83 726 T2.21/P 0 RESOLUTION 726 MULTIPLE PURPOSE DOCUMENT (MPD) (amending) PSC(29)726 Expiry:Indefinite Type: B 726 T2.21/P 8 FORMAT 61 Unspecified Miscellaneous Charges Order Deduction Method (not applicable to Resolutions 725f, 725g 726b and 726e) Filing Period: Effective Date: 18 February June April 2008

84 726a T2.25/P 0 RESOLUTION 726a MULTIPLE PURPOSE DOCUMENT(MPD) CARRIER, CARBONISED, AUTOMATED (amending) 726a T2.25/P PSC(29)726a 2.2 ENTRIES Expiry: Indefinite Type: B Fixed Area Name of Passenger Box (d) Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either:- double the single letter family name as the family name. For example, Miss Moan be represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS. Filing Period: Effective Date: 18 February June April 2008

85 726e T2.25/P 0 RESOLUTION 726e MULTIPLE PURPOSE DOCUMENT(MPD) NEUTRAL, CARBONISED, MANUAL (amending) PSC(29)726e Expiry: Indefinite Type: B 726e T2.25/P 2.2 ENTRIES Fixed (pre-format) Area) Name of Passenger Box Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either: double the single letter family name as the family name. For example, Moan Y will be represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS. Filing Period: Effective Date: 18 February June April 2008

86 726f T2.21/P T2.25/P 0 RESOLUTION 726f MULTIPLE PURPOSE DOCUMENT (MPD) CARRIER, CARBONISED, MANUAL (amending) PSC(29)726f Expiry: Indefinite Type: B 726f 726f T2.21/P T2.25/P Unspecified MCO Deduction Method (not applicable to Electronic Miscellaneous Documents (EMD-S) issued for residual value) 2.2 ENTRIES Fixed (pre-format) Area) Name of Passenger Box (d). Ticketing of passengers with single letter family names shall be accomplished in accordance with the reservations procedures established in AIRIMP which states, to accommodate systems that cannot process single letter family names either:- double the single letter family name as the family name. For example, Miss Moan be represented as YY/MOANMISS, or combine the single letter family name with the first given name of that passenger as the family name. For example, Miss Moan Y will be represented as YMOAN/MISS and Miss Tuyetmai Van A will be represented as ATUYETMAIVAN/MISS. Multiple members of a single letter family name are to be represented by individual name elements. For example John and Sally U would be represented as UJOHN/MR and USALLY/MRS. Filing Period: Effective Date: 18 February June April 2008

87 728 T2.18/P 0 RESOLUTION 728 CODE DESIGNATORS FOR PASSENGER TICKET AND BAGGAGE CHECK (amending) PSC(29)728 Expiry: Indefinite Type: B 728 T2.18/P 728 T2.18/P 7. FORM OF PAYMENT CODE (mandatory) CREDIT CARD CODES (NUMERIC) 1 Exception: For ATB2, OPATB2 tickets, automated MCOs and Excess Baggage Tickets issued under Resolutions 722c, 722d, 725c, 725d and 742e for the Passenger Receipt and the Flight/Exchange Coupon(s) replace each of the characters in the credit card number with the exception of the last four with the letter X. Filing Period: Effective Date: 18 February June April 2008

88 735d T6 0 RESOLUTION 735d INVOLUNTARY CHANGE OF CARRIER, ROUTING, CLASS OR TYPE OF FARE (amending) PSC(29)735d Expiry: Indefinite Type: B 735d T6 5. ABSORPTION OF PASSENGER EXPENSES The carrier responsible for the condition which creates a need for an involuntary change in the passenger s journey shall be responsible for such of the passenger s expenses as may be incurred during the period of the passenger s delay at the place where the involuntary change occurred, and may absorb such expenses at subsequent points en route where they are a direct consequence of such a change, provided that they are limited to essential expenses such as hotel room, suitable meals and beverages without regard to class of service, ground transportation, transit taxes, and reasonable communications costs necessarily incurred by the passenger because of the involuntary change; provided further that where a domestic service of the carrier responsible for the delay causes such a change, such Original Marketing/Operating Carrier, or the Ticket Handler acting on their behalf need not comply with the requirements of this paragraph and such responsibilities may be assumed instead by the Original Operating Carrier or the New Operating Carrier. In an interline journey it is the responsibility of the carrier responsible for a delay causing involuntary change of a passenger's journey to arrange for a reasonable alternative route within a reasonable time and if such time limit is not feasible to comply with the requirements of absorption of passenger's expenses as may be incurred during the period of the passenger s delay at the place where the involuntary change occurred and to absorb such expenses at subsequent points en route where they are a direct consequence of such a change, provided that they are limited to essential expenses such as hotel room, suitable meals and beverages without regard to class of service, ground transportation, transit taxes, and reasonable communications costs necessarily incurred by the passenger because of the involuntary change. Filing Period: Effective Date: 18 February June April 2008

89 740 B8.6/P 0 RESOLUTION 740 FORM OF INTERLINE BAGGAGE TAG (amending) PSC(29)740 Expiry: Indefinite Type: B 740 B8.6/P 8. CUSS (COMMON USE SELFSERVICE) 8.1 Definition A CUSS bag tag is a demand printed baggage tag issued by a CUSS KIOSK as defined in RP1706c.(ATA ). 8.2 Specifications Baggage tags issued at CUSS locations are to comply with the specifications in IATA 740 and 1740a (ATA and 30.42) Length: Tags used in a CUSS Kiosk shall be twenty-one (21) inches in length. This is the length of the printable label and not inclusive of the liner. Filing Period: Effective Date: 18 February June April 2008

90 762 P1.3 0 RESOLUTION 762 AIRLINE DESIGNATORS (amending) PSC(29)762 Expiry: Indefinite Type: B 762 P ASSIGNMENT CRITERIA FOR NEW APPLICANTS ATA and IATA Member Airlines, and airlines which are parties to the ATA Interline Traffic Agreement Passenger (Resolution 5.65), the IATA Interline Traffic Agreement Passenger (Resolution 780/780e), or the IATA Interline Traffic Agreement Cargo (Resolution 660); non-ata/non-iata Member airlines publishing and operating scheduled air service in accordance with the definition of a scheduled air service contained in IATA Recommended Practice 1008 in standard air transport guides. However, if such airline does not intend to conclude an interline traffic agreement within 90 days of assignment, the two-character designator shall be recalled and it shall be assigned a three-letter designator; until such time as three-letter designators can be handled by airlines and Computer Reservation Systems, such airlines shall also be assigned a duplicated airline designator in a controlled environment. Filing Period: Effective Date: 18 February June April 2008

91 766 R6.10/P 0 RESOLUTION 766 INTERLINE PASSENGER RESERVATIONS PROCEDURES (amending) PSC(29)766 Expiry: Indefinite Type: B 766 R6.10/P 10. SALES AVAILABILITY AGREEMENTS AND CONTRACTS 10.6 Availability maintained by a Member or CRS is not to be used for irregular operations protection, even when the bookings are for parties below the quota sale bilaterally agreed. Flight inventory on the new Carrier (always use Operating Carrier in a codeshare situation) for irregular operations protection must be requested by telephone and/or AIRIMP message in accordance with AIRIMP irregular operations message procedures (refer to AIRIMP section Irregular Operations Messages and Resolution 735d, paragraphs through Filing Period: Effective Date: 18 February June April 2008

92 767 P1.2 P1.3 0 RESOLUTION 767 ASSIGNMENT CRITERIA FOR AIRLINE ACCOUNTING CODES AND AIRLINE PREFIXES (amending) PSC(29)767 Expiry: Indefinite Type: B 767 P ASSIGNMENT CRITERIA FOR AIRLINE ACCOUNTING CODES AND AIRLINE PREFIXES 2.1 Three numeric airline accounting codes or airline prefixes shall be assigned for the purposes described in Paragraph 1 to: Members of the International Air Transport Association (IATA) which issue interline traffic documents; Members of the Air Transport Association of America (ATA) which issue interline traffic documents; Computerised reservations system companies which provide ticketing services for the airline industry; Airlines having bilateral interline traffic agreements with another airline individual Members of IATA or ATA, and issue accountable interline traffic documents; 767 P AIRLINE ACCOUNTING CODES AND AIRLINE PREFIXES NOT AVAILABLE FOR ASSIGNMENT 5.1 The following airline accounting codes shall not be assigned to individual airlines or non-airline companies qualifying for an airline accounting code for use on passenger traffic documents: Code Assignee 777 BSP Tour Operators/Hotels/Courier Companies/Insurance Companies 792 BSP Car Rentals 793 BSP Ships/Hovercraft 794 BSP Bus Lines 799 BSP Railways 888 Scheduled Airlines Traffic Offices Inc. 889 ARC 890 ARC 950 SITA 953 BSP 954 BSP 955 BSP 956 BSPlink agent Filing Period: Effective Date: 18 February June April 2008

93 780 P4.5 P5.1 0 RESOLUTION 780 FORM OF INTERLINE TRAFFIC AGREEMENT - PASSENGER (amending) PSC(29)780 Expiry: Indefinite Type: B 780 P5.1 Attachment A Article 1 Definitions 1.27 TICKET is the document entitled Passenger Ticket and Baggage Check described in the applicable IATA and ATA Resolutions (including Electronic Tickets) and Recommended Practices, issued by or on behalf of an Issuing Airline and including the Notice of Contract Terms Incorporated by Reference and Notices set forth in Resolutions 724 and 724a Conditions of Contract and Other Important Notices as set forth in Resolution P FURNISHING OF TARIFFS, ETC. A Each party shall furnish to each other party the tariffs and other information necessary for the sale, as contemplated hereunder, of the transportation services currently being offered by it. In case any schedule, tariff, form of ticket or MCO of any party hereto relating to transportation over its lines, shall be modified or amended at any time, or in case any service of any such party shall be suspended, modified or cancelled, such party will notify each other party as far in advance as practicable, of the effective date of any such modification, amendment, suspension or cancellation. In the interest of ensuring the widest possible collection and dissemination of accurate fares information throughout the airline industry, each party is requested to furnish, or arrange to furnish, (possibly via official sources such as SITA, Genesis, etc.) to ATPCO, interlineable fares and related conditions (both domestic and international fares) established other than through the IATA Tariff Coordinating Conferences. This shall apply until such time as the All Fares product (currently being developed by IATA and ATPCO) is recognized and agreed unanimously by the Passenger Services Conference as being the single source, at which time the above reference to ATPCO will be deemed to read All Fares. See Government Reservations Section, United States. In the interest of ensuring the widest possible collection and dissemination of accurate schedule information throughout the airline industry, each party is requested to furnish, or arrange to furnish, their schedule and schedule change information following SSIM formats. It is recommended that at least 360 days of advance schedules data, including Minimum Connect Time data, should be distributed on an equal basis to all schedules aggregators, reservations and ticketing systems in which a carrier participates, to maximise the efficiencies of such systems.

94 780 P Requests for prorate shall be made to the headquarters central baggage claims office using the format shown in Appendix C PRORATE NOTICE (published separately) as a cover sheet for the following documents which are required to support any claim under this agreement including requests for 100%: 780 P APPLICATION TO BECOME A PARTY HERETO Any airline desiring to become a party to this Agreement shall make written application to IATA s Director, Passenger Services by completing the application form shown in Appendix A (published separately). The IATA Director, Passenger shall mail to each party hereto a copy of such application on the first day of the month subsequent to the date on which the written application is received. 780 P Each year on the anniversary date of a non-iata airline becoming a party to the agreement, the IATA Director, Passenger Services shall dispatch by registered mail to such non-iata party, the Annual Review Form contained in Appendix B (published separately). If the party advises that it is no longer operating scheduled services, or it does not return the form within thirty (30) days of mailing, the IATA Director, Passenger shall have the party withdrawn from the agreement under the provisions of P4.5 Attachment A Appendix A, Appendix B, Appendix C A Secretary note: delete the entire Appendix A, B and C. Filing Period: Effective Date: 18 February June April 2008

95 780e P5.1 0 RESOLUTION 780e IATA INTERLINE TRAFFIC PARTICIPATION AGREEMENT - PASSENGER (amending) PSC(29)780e Expiry: Indefinite Type: B 780e P5.1 Article 1 Definitions 1.29 TICKET is the document entitled Passenger Ticket and Baggage Check described in the applicable IATA and ATA Resolutions (including Electronic Tickets) and Recommended Practices, issued by or on behalf of an Issuing Airline and including the Notice of Contract Terms Incorporated by Reference and Notices set forth in Resolutions 724 and 724a Conditions of Contract and Other Important Notices as set forth in Resolution 724. Filing Period: Effective Date: 18 February June April 2008

96 792 B4 T12 0 RECOMMENDED PRACTICE 792 BAR CODED BOARDING PASS (BCBP) VERSION 2 (amending) PSC(29)792 Expiry: Indefinite Type: B 792 B4 RESOLVED that: Members may issue, either for online or interline carriage, a Boarding Pass with version 2.0 of the Bar Code standard as described herein. All of the following specifications define the required characteristics of the elements and format of the Bar Code on the Boarding Pass or electronic (mobile) device. Section 1 General INTRODUCTION This resolution defines a machine-readable bar code for boarding passes or electronic (mobile) devices. This data format supports single segment, multi-segment and inter-line data encoding. The 2-dimensional Bar Code format has the capacity to convey this data allowing a wider range of devices to display or produce boarding passes with encoded data. 1.1 USE OF BAR COADED BOARDING PASS The Bar Code presented here is designed for use on all forms of Boarding Pass stock, including ATB, General Purpose (i.e. kiosk) and, when electronic tickets are issued, selfprinted (i.e. web check-in) Boarding Passes. The Bar Code shall be printed on the same side of the page as the passenger and flight information. In contrast to the Magnetic Stripe, the Bar Code does not require any specific placement or orientation on the Boarding Pass. However it is recommended that the Bar Code be printed adjacent and parallel to an edge of the document in order to facilitate the use of reading devices. This resolution addresses the Bar Code format for use on single-segment and multisegment Boarding Passes. This does not preclude the ability for a Member to adopt their own Bar Code for online use, or for use as bilaterally agreed upon between a Member and an interline partner. The Bar Code format also permits an airline to include its own proprietary data alongside the required Bar Code information. A Bar Coded Boarding Pass may not be issued for more than one passenger USE OF PAPER BAR CODED BOARDING PASS The Bar Code presented here is designed for use on all forms of Boarding Pass stock, including ATB, General Purpose (i.e. kiosk) and, when electronic tickets are issued, selfprinted (i.e. web check-in) Boarding Passes. The Bar Code shall be printed on the same side of the page as the passenger and flight information. In contrast to the Magnetic Stripe, the Bar Code does not require any specific placement or orientation on the Boarding Pass. However it is recommended that the Bar Code be printed adjacent and parallel to an edge of the document in order to facilitate the use of reading devices.

97 792 B4 792 B USE OF ELECTRONIC (MOBILE) DEVICE BOARDING PASS The Bar Codes presented here are designed for use as an electronic (mobile) boarding pass. These bar codes should be able to be displayed by all modern electronic (mobile) devices and the screen display optimised. Readers should be able to read the printed bar codes as well as the electronic (mobile) presented symbologies. 1.2 ACCEPTANCE In accordance with their interline travel agreements, Members shall accept and honour the boarding passes or documentation with Bar Codes issued under this resolution. Section 2 Technical Specifications Scope This data structure is designed exclusively for use on Bar Coded airline boarding documents or passes. The resolution defines the encoding of Bar Code data, and its visual representation and placement on a document or electronic (mobile) device. The use of this Bar Code does not impose additional requirements or restrictions on what else is displayed on the boarding document or pass 792 B4 2.1 TECHNICAL REQUIREMENTS Printed Boarding Pass The Bar Code presented here is a 2-dimensional Bar Code in PDF417 standard containing a structured data message (SDM). This message as defined in ISO/IEC contains fixed-length fields and variable-length data that can be used by airlines at their discretion. The PDF417 Bar Code format permits flexibility in the size, readability, robustness and capacity of printed Bar Codes. It is widely supported by current Bar Code scanners and printers, and is already in use within the airline industry. 792 B Electronic (Mobile) Boarding Pass The bar codes presented here are 2-dimensional bar codes in Aztec, Datamatrix and QR code containing a structured data message (SDM). The Datamatrix message as defined in ISO/IEC contains fixed-length fields and variable-length data that can be used by airlines at their discretion. The QR message as defined in ISO/IEC contains fixed-length fields and variablelength data that can be used by airlines at their discretion. The Aztec message as defined in the Association for Automatic Identification and Mobility (AIM Global) contains fixed-length fields and variable-length data that can be used by airlines at their discretion. Aztec, Datamatrix and QR permit flexibility in the size, readability, robustness and capacity of Bar Codes.

98 792 B4 2.2 STRUCTURE REQUIREMENTS 792 B4 This Bar Code format allows for 1 fixed-length and 2 variable-length sets of data. The fixed-length data refers to all elements that are required and must be included within every Bar Code. The first set of variable-length data is conditional (use if available) and the second set of variable length data is optional which allows airlines to include their own information alongside the required elements. The variable-length data can include non-printable (binary) data. A Bar Code scanning system designed for this Bar Code format must scan and accept with valid data, including non-printable data in the variable length segment, even if it does not use of all of the data. The maximum size of the bar code shall not exceed 600 characters. 2.3 BAR CODE STRUCTURE SPECIFICATIONS See Resolution 792, Attachment A 2.4 EXAMPLES Four examples reflecting the positioning of the data in the bar code and the string of characters to be encoded can be found in Resolution 792, Attachment B. 2.5 BAR CODE SPECIFICATION PDF 417 barcode As it is envisaged that Bar Codes will be produced in different environments (e.g. home printer, kiosk, etc.) and read with different devices (laser, optical, etc.), the following guidelines have been developed. Printing resolution of an ink jet personal printer: minimum 300 dpi (maximum not applicable) Printing resolution of a direct thermal GPP: minimum 200 dpi (maximum not applicable) X Dim = 10 mils or 0.03CM (one inch is approximately 3CM) X to Y ratio = 3 Error Correction Level: 3 Notes: X Dim is the width of a narrow bar. Most ISO and AIM standards indicate that the minimum X dimension should be 10 mils for open systems (meaning compatibility with different bar code scanner brands) The Y dimension is the height of each row within the PDF417 symbol. PDF417 is usually printed with an X to Y ratio from 1:2 to 1:5. By changing the X to Y ratio to 1:2 or 1:3, a significant amount of space can be saved. However, some scanners cannot read X to Y ratios of less than 1:3 and most read best at 1:4. PDF417 uses Reed Solomon error correction instead of check digits. This error correction allows the symbol to withstand some damage without causing loss of data. This high level of error correction is far more advanced than linear barcodes with check digits. The error correction level depends on the amount of data that needs to be encoded, the size, and the amount of symbol damage that could occur. The AIM recommendation for the error correction level to use depends on the number of data code words generated. *

99 Error Correction Level 3 4 AIM Recommendation for data encoded 792 B4 2.6 REFERENCES: BAR CODE SPECIFICATIONS Attachment C C 792 B4 Attachment A A* Item Number BCBP M FORMAT VERSION 1 2 Element Description Field Size Unique /Repeated Data Type Formatting 46 Date of Flight (Julian Date) 3 R N Leading zeroes 4 21 Airline designator of boarding pass issuer 3 U f Left justified and trailing blanks o 23 Baggage Tag License Plate Number (s) 13 U f As per BSM specifications p Reference No (s). 17 Field size of following structured message - 2 R f Right justified and leading zeros k repeated 22 Date of Issue of Boarding Pass (Julian Date) 4 U N First digit for the year then 3 digits with 4 leading zeroes

100 792 B4 Attachment B B* New Item Number Element Description Field Size Unique /Repeated EXAMPLE 1 M1 USING NEW FIELDS Notes 46 Date of Flight (Julian Date) 3 R August 14th 8 > - beginning of version 2 R > number 9 Version Number 1 U Airline designator of boarding 3 U pass issuer 23 Baggage Tag License Plate 13 U Number (s) 17 Field size of following 2 R structured message -repeated 22 Date of Issue of Boarding Pass (Julian Date) 4 U = =August 13th

101 792 B4 Attachment B B* New Item Number Element Description Field Size Unique /Repeated EXAMPLE 2 M1 USING NEW FIELDS Notes 46 Date of Flight (Julian Date) 3 R August 16th 8 > - beginning of version number 2 R > 9 Version Number 1 U Airline designator of boarding pass 3 U issuer 23 Baggage Tag License Plate 13 U Number (s) 17 Field size of following structured 2 R message -repeated 22 Date of Issue of Boarding Pass (Julian Date) 4 U

102 792 B4 Attachment B B* New Item Number Element Description Field Size Unique /Repeated EXAMPLE 3 M2 USING DIFFERENT NEW FIELDS Notes 46 Date of Flight (Julian Date) 3 R = August 14th 8 > - beginning of version 2 R > number 9 Version Number 1 U Date of Issue of Boarding Pass (Julian Date) 4 U = =August 13th 21 Airline designator of boarding 3 U pass issuer 23 Baggage Tag License Plate 13 U Number (s) 17 Field size of following structured message -repeated 2 R 46 Date of Flight (Julian Date) 3 R = August 15th

103 792 B4 Attachment B B* New Item Number Element Description Field Size Unique /Repeated EXAMPLE 4 M2 USING DIFFERENT NEW FIELDS Notes 46 Date of Flight (Julian Date) 3 R = August 16th 8 > - beginning of version 2 R > number 9 Version Number 1 U Date of Issue of Boarding 4 U Pass (Julian Date) 21 Airline designator of boarding 3 U pass issuer 23 Baggage Tag License Plate 13 U Number (s) 17 Field size of following structured message -repeated 2 R 46 Date of Issue of Boarding Pass (Julian Date) 4 U = August 16th

104 792 B4 Attachment C C* REFERENCES No Description Notes Set of Values 4 Date of Flight (Julian Date) - Date of Issue (Julian Date) Calendar date. In date of issue, precede by single digit for year "001": Jan 1st, "6001": Jan 1st 2006, "365" Dec 31st, "6365": 31st Dec Passenger Status 0 ticket issuance/passenger not checked in, 1 ticket issuance/passenger checked in, 2 baggage checked - passenger not checked in, 3 Baggage checked/passenger checked in, 4 Passenger passed security check, 5 Passenger passed gate exit (coupon used), 6 Transit, 7 Standby. Seat Number not printed on Boarding pass at time of check-in. (Seat number to be printed at time of seat assignment.) 8 Boarding data revalidation done. (Gate, Boarding Time and Seat on Revalidation Field already used.) 9 Original boarding line used at time of ticket issuance. A Up- or down-grading required at close out, e.g. when passenger waitlisted in C class and OK in Y class.) B Z Reserved for future industry use "0": passenger not checked in, "1": passenger checked in, "7": Standby (Seat Number not printed on Boarding pass at time of check-in, seat number to be printed at time of seat assignment), "A": Up- or downgrading required at close out (e.g. when passenger waitlisted in C class and OK in Y class), "B Z": Reserved for future industry use. 47 X/O Indicator 65 Electronic Ticket Indicator Indicates that the Boarding Pass was E- Boarding pass issued against an Electronic Ticket issued against an Electronic Ticket a Format code S for single, M for Multiple

105 792 B4 Attachment C C* REFERENCES No Description Notes Set of Values d Field Size of following field Size of data used within the subsequent From 00 to FF variable fields, in ASCII-printed hexadecimal. Value of item 6 = sum of sizes of items 8, 9, 10, 15, 12, 14, 22, 16, 21, 23, 17, 142, 143, 18, 108, 19, 20, 236, 89, 118, 4 (if item is left blank, size equals zero). If not used, enter 00. g Field size of following structured message unique Size of data used within the fields, in ASCII-printed hexadecimal. Value of item 10 = sum of sizes of items 15, 12, 14, 22, 16, 23, 21 (if item is left blank, size equals zero). If not used, enter "00" If not used, enter 00. k Field size of following structured message repeated Size of data used within the subsequent variable fields, in ASCII-printed hexadecimal. Value of item 17 = sum of sizes of items 142, 143, 18, 108, 19, 20, 236, 89, 118 (if item is left blank, size equals zero). If not used, enter "00". m Marketing carrier designator Airline code of the marketing carrier Airline Designator, Ref Resolution 762 n Frequent flyer airline Airline code of the airline s FFP Airline Designator, Ref Resolution 762 o Airline designator of boarding pass issuer Identifies the origin of the data encoded Airline Designator, Ref Resolution 762 in the airline individual use field p Baggage Tag License Plate Number(s) As per BSM specifications

106 792 T USAGE ON ELECTRONIC TICKET PASSENGER ITINERARY RECEIPT When a 2D barcode is printed on an electronic passenger itinerary receipt, it shall be in accordance with the provisions of this resolution. Conditional element 16 shall be present with indicator I to identify that the barcode is printed on an itinerary receipt and not the boarding pass document. Secretary Note: To the matrix in Attachment A add the following footnote:- Elements 11 Passenger Name, 16 Document Type, 142 Airline Numeric Code, 143 Document Form Serial Number *Mandatory when issuing an Electronic Ticket Passenger Itinerary Receipt Elements 20 Frequent Flyer Designator and 236 Frequent Flyer Number ** Conditional when issuing a Passenger Itinerary Receipt. Filing Period: Effective Date: 18 February June April 2008

107 1707a B9 0 RECOMMENDED PRACTICE 1707a DATA FIELD DICTIONARY FOR DCS PASSENGER MESSAGES (amending) PSC(29)1707a 1707a B9 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 cd. Filing Period: Effective Date: 18 February June April 2008

108 1707b B6.3/P B6.5/P B6.8/P B6.10/P B6.11/P B9 B11 0 RECOMMENDED PRACTICE 1707b DATA ELEMENT DICTIONARY FOR DCS PASSENGER MESSAGES (amending) PSC(29)1707b 1707b B9 1707b B9 Section 1.1 STANDARD DCS MESSAGES FOR PASSENGERS Add new bullet point 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. 1.3 STANDARD ELEMENTS USED IN DCS PASSENGER MESSAGES Adding a new column for the TPL, as follows: * Element ID Ref in 1707b Element Title 1708 PNL 1719c ETL 1719d TPL 2.1 Address M 2.2 Communications M Reference 2.4 Flight M 2.3 Message Identifier M 2.9 Name M 2.5 Totals by Destination M ATD 2.16 Actual Time of Departure O CFG 2.12 Seat Configuration CO O END 2.21 End of Message M ENDPART 2.21 End of Part C NIL 2.18 NIL C PART 2.4 Part Number M.BG/ Baggage Pooling C.L/ 3.18 Automated PNR Address C.N/ 3.20 Baggage Tag Details C.R/ 3.24 Remark M.RN/ 3.27 Remarks Continuation C.W/ 3.32 Pieces/Weight Data O

109 1707b B6.8/P 2.9 NAME ELEMENT When there is more than one surname in a PNR in the reservation system, then the name Element includes a Party/Group/Tour Identification, associating the surnames with each other. When the Name Element plus Party/Group/Tour Identification is more than 64 characters 1707b B6.5/P Passenger names and 2DOE/JACKMR/ JANESMS-C3 name element and party identification group identifier Seat blocking 1ZZ/CBBG-C3 name element and group identifier Note: When PNRs are created for purposes other than passenger accommodation, the surname is shown as ZZ preceded by number of seats to be blocked and the given name shows the reason. A Party /Group Identifier always follows a ZZ name element when seats are blocked for passenger special service (CBBG, EXST, STCR ) Examples: 1DOEDEN/AARONMR 2KOSTER/ADAMDR/VIOLAMRS 1JONES/PETER-C2.R/EXST HK1 23A 1MEYSEMBOURGH/AMYMS 1ZZ/EXST-C2 170b B6.8/P Party/Group/Tour Identification Passengers of different surnames travelling together and booked in the same PNR are considered a party/group/tour and are given separate Name Elements. The Name Elements are associated with each other with Party/Group/Tour Identification. Party/group/tour identifiers range from A to Z and then AA to ZZ party/group/tour total number of seats in the party/group/tour

110 1707b B6.5/P Block Seats Indicator When inventory is booked in RES for special usage, such as for extra cabin baggage (CBBG) or stretcher (STCR), the SSR/OSI codes are shown in.r/ elements with the individual name of each applicable passenger in the PNL/ADL. The seats blocked for the special usage are shown on the PNL/ADL with a special form of the Name Element using ZZ as the surname in alphabetical sequence. The given name field can show free text or an SSR/OSI code to show the special usage. The passenger name appears on the PNL/ADL with a party/group identifier as 1JONES/PETER-C2 followed by a.r/ element for the service item (CBBG) and the number of seat(s) blocked appears with same party/group identifier, as 1ZZ/CBBG- C2 under the relevant Totals by Destination element. No other information or PNL/ADL element can appear following a ZZ entry. This special form of the Name Element is used only to show the number of seats blocked and appears only on the PNL/ADL, as bilaterally agreed. Examples: 1DUPONT/PIERREMR-A8.R/STCR KK1 BROKEN HIP IN PLASTER... 1JONES/PETER-C2.R/CBBG HK1 CELLO 135X25CM 15KILOS ZZ/STCR-A8 1ZZ/CBBG-C2 25ZZ/KLALLOTMENT 1707b B6.10/P 3.18 L/ AUTOMATED PNR ADDRESS ELEMENT Members may include one or more automated PNR addresses (also known as file references or record locators). When a single.l/ element appears, the company designator is optional. When a single.l/ element appears with no company designator, it is assumed to be the record locator of the sender of the message airline code of the airline in the Flight Element of the DCS message. When more than one automated 1707b B R/REMARKS ELEMENTS applicable SSR or, OSI code or bilateral agreed code SFML SSR or, OSI code or bilateral agreed code (number, when present, may precede OSI code) 1VIP (Bilateral agreed code) ETLP 1707b B action/status code and number KK1 status code HK3 number/one-to-three HN1

111 1707b B6.11/P PAXLST DOCA Element action/status code and the number 1 HK1 status code action/status code HK status code number of passengers to whom the element applies 2 number/one-to-three oblique / information separator (Editor s note: please re-number all subsequent paragraphs in this section.) Examples:.R/DOCA HK1/D/US...R/DOCA HK3/R/CH/33 ROUTE DE LAEROPORT/GENEVA/SWITZERLAND/ b B6.3/P 4.2 The discount codes. RG Reduced fare Group passenger, such as a member of a commercial group. RG Free or reduced fare transportation for IATA Passenger Sales Agents. Filing Period: Effective Date: 18 February June April 2008

112 1708 B6.2/P B6.4/P B6.5/P B6.6/P B6.7/P B6.8/P B6.9/P B9 B11 0 RECOMMENDED PRACTICE 1708 PASSENGER NAME LIST (PNL) AND ADDITIONS AND DELETIONS LIST (ADL) (amending) PSC(29) B6.8/P 1.4 COMPONENTS Party/Group/Tour Identification Element -A B6.7/P 2.6 DEL (DELETE) ELEMENT 2.6 ADL ELEMENTS The elements for delete (DEL), add (ADD), and change (CHG) are for use only on an ADL. These elements are the headers, by destination and compartment, for ADL messages, which alter the passenger information sent previously on PNLs or ADLs. These three elements always appear in the sequence DEL, then ADD, then CHG, and each appears on an ADL only if it has passenger entries. The following rules apply: A Name Element for a member of a non-group PNR is to appear under the DEL or CHG Element precisely as it appeared on a previously dispatched PNL or ADL, including the party/group identifier. A Name Element for a named member of a Group PNR is to appear under the DEL or CHG Element precisely as it appeared on a previously dispatched PNL or ADL, including the party/group identifier. A Name Element for an un-named (NONAMES) member of a group PNR can appear only under the DEL or ADD Element, and it appears as NONAMES, preceded by the appropriate number of NONAMES. When a Name Element (a passenger) is to be deleted, use DEL, including the party/group identifier. When a Name Element (a passenger) is to be added, use ADD, including all of its associated elements, including the party/group identifier, when applicable (such as for a name change). When the elements that are associated with a Name Element are to be replaced, added, or deleted, the Name Element is to appear under the CHG Element precisely as it appeared on a previously dispatched PNL or ADL, followed by all of the currently applicable associated elements, including the party/group identifier. The CHG Element is not used to change a Name Element. All actions to the Name Element use DEL and/or ADD Elements B6.7/P DEL (DELETE) ELEMENT Editor s note: please renumber the sub-paragraphs [2.6.1-to-2.6.6] as [ to ] B6.7/P 2.7 ADD (ADD) ELEMENT ADD (ADD) ELEMENT Editor s note: please renumber the sub-paragraphs [2.7.1-to-2.7.5] as [ to ] B6.7/P 2.8 CHG (CHANGE) ELEMENT CHG (CHANGE) ELEMENT Editor s note: please renumber the sub-paragraphs [2.8.1-to ] as [ to ], including this change below to the newly-renumbered

113 1708 B6.7/P in one compartment and destination and compartment are included 1708 B6.7/P Add an SSR/OSI element in the PNR, and show all of the current elements on the CHG entry: Original entries on the PNL: PNR with just a wheelchair and a special meal for party of 2: CHG entry on ADL: Add a special meal and a seat request for Mr. Bainge: 1BAINGE/DAVIDMR-D2.R/WCHR CHG 1TRANE/RONMR-D2.R/VGML.R/WCHR 1BAINGE/DAVIDMR-D2.R/WCHR.R/ SFML.R/NSST 1TRANE/RON MR.R/VGML.R/WCHR 1708 B6.7/P CHG 1VONCANSTEIN/RABANMR ADL FORMAT FOR COMMON RES FUNCTIONS Example of a divided PNR: 1708 B6.7/P Example of a divided PNR confirmed from waitlist: The PNL showed Mr. Mackie waitlisted in F-class, and confirmed in Y-class: 1MACKIE/IANMR-D2.L/CDE1RY/BA.WL/PD1 -MSP12F 1MACKIE/IANMR-D2.L/CDE1RY/BA.WL/PD1 -MSP207Y 1MACKIE/IANMR-D2.L/CDE1RY/BA.R/RQST HK1 17D 1708 B6.7/P Example of a cancellation in RES of one/some (but not all) of the passengers, in a PNR: The PNL showed the PNR for the Gajve family as: -IAD15F 3GAJVE/DEVENDRAMR/YOGIMRS/CLARAMS-M6.L/HEX123.R/INFT HK1 07DEC07-1GAJVE/CLARAMS Mrs. Gajve cancels her booking in this PNR, so the ADL shows: -IAD14F DEL 3GAJVE/DEVENDRAMR/YOGIMRS/CLARAMS.L/HEX123 ADD 2GAJVE/DEVENDRAMR/CLARAMS.L/HEX123.R/INFT HK1 07DEC07-1GAJVE/CLARAMS

114 1708 B6.7/P Example of a name-change in RES with a single surname: The PNL showed the Rogers family as: -HNL55Y 5ROGERS/JMR/CMRS/EMS/PMS/MMS.L/AND123 First names were added with a name-change in RES, so the ADL shows: -HNL55Y DEL 5ROGERS/JMR/CMRS/EMS/PMS/MMS.L/AND123 ADD 5ROGERS/JEFFMR/CHRISTINEMRS/EMILYMS/PHOEBEMS/MEGANMS.L/AND B6.7/P Example of a name-change in RES with a single surname that becomes multiple surnames: The PNL showed the PNR for the Gulbrandson family as: -LAX14F 2GULBRANDSON/DAVIDMR/MARYMRS.L/D9E8EE Mrs. Gulbranson will not travel and the name change becomes Jack Brown, so the ADL shows (now including a party/group identifier): -LAX14F DEL 2GULBRANDSON/DAVIDMR/MARYMRS.L/D9E8EE ADD 1BROWN/JACKMR-T2.L/D9E8EE 1GULBRANDSON/DAVIDMR-T B6.8/P The following rules apply: A name element is deleted by showing the Name Element under this indicator in precisely the same way it appeared in a previous list message, except for the party/group/tour indicator. The only associated element required is the Automated PNR Address. Group members are deleted by showing individual names as they were originally transmitted in the PNL or ADL, except for the party/group/tour indicator.

115 1708 B6.7/P in one compartment and destination and compartment are included 1708 B6.6/P 2.8 CHG (CHANGE) ELEMENT This element is used when passenger level elements, included on previously dispatched PNL and ADL(s) must be replaced This element is used to replace, add, or delete passenger-level elements (which appear after the Name Element), as included on a previously dispatched PNL or ADL. The Name Element is to be followed by all currently applicable associated elements, including the party/group identifier B6.7/P in one compartment and destination and compartment are included 1708 B6.8/P 2.10 PARTY/GROUP/TOUR IDENTIFICATION ELEMENT For construction rules, see RP 1707b, Party/Group/Tour Identification under the Name Element If a party/group/tour PNR has an inbound connection, this element appears with only the first individual s Name Element If a party/group/tour PNR has onward connection(s), this element appears with only the first individual s Name Element B6.8/P This element conveys supplementary information from reservations control to the boarding airport s Departure Control System. In general, it contains information that is held in the PNR of one or more passengers in the SSR or OSI elements of the PNR. Where a Remarks Element is derived from a PNR for a party/group/tour, it shall be shown against the individual name of each applicable passenger in the party/group/tour to whom it applies. Remarks Elements are entered after any Inbound and Onward Connection Elements B6.9/P Remarks Element for Infant Information free text from RES SSR INFT element, which should contain full name of infant and date of birth as ddmmmyy 29MAR07 free flow text should contain the infant s date of birth as ddmmmyy, space, and full name 29MAR07 free flow text (c) Construction rules for SSR INFT Occupying a Seat free text which contains the infant s age date of birth, followed by a space and the letter R to indicate that the infant is occupying a seat 14JAN05 R free flow text..

116 1708 B6.2/P Remarks Element for Child Information (Valid from 01JUN07) action/status code HK status code number of children 1 1 action/status code and the number 1 HK1 status code 1708 B6.9/P (b) Construction rules.. Examples: 2LARSON/TOMMR/JANEMRS.R/INFT HK1 12JAN07/LARSON/BILLYMSTR 2LARSON/TOMMR/JANEMRS.R/INFT HK1 12JAN07 LARSON/BILLYMSTR 1708 B Remarks Element for Ticket Number Information (b). 2LARSON/TOMMR/JANEMRS.R/INFT HK1 12JAN07/LARSON/BILLYMSTR.R/FOID HK2 CC MC OXTORP/JOHNMR/PETERMR-A5.R/FOID HK1 FF LH OXTORP/JOHNMR.R/FOID HK1 FF LH OXTORP/PETERMR 1708 B Remarks Element for Ticketless Product Information (bilateral agreement) (a) This element is conditional, being used for only Ticketless passengers (b) The Remarks Element for Ticketless Product Information uses the bilaterally code ETLP (c) Construction rules Field Example Data Field Name (see RP 1707a/b) element ID.R/ element ID Ticketless Product code ETLP bilaterally agreed code space information separator status code and number HK1 status code space information separator ticketless product number NS17 m[..15] passenger ID -1TAYLOR/SIMONMR passenger ID Example:.R/ETLP HK NS17-1TAYLOR/SIMONMR

117 1708 B6.4/P Table of SSR Codes AVML ASVC EPAY ESVC Additional Services, segment-associated Notification of EMD for Additional Services Other than Optional Services Table of AUX/OSI Codes and Miscellaneous Abbreviations The following AUX/OSI codes and LEGB SVC segment-associated Additional Services code from Auxiliary Service element, not 1708 B Table of OSI Codes and Miscellaneous Abbreviations The following OSI codes and miscellaneous abbreviations from the IATA AIRIMP or bilaterally agreed codes are used in.r/ Remarks Elements. They are shown in the table in alphabetical order by code. Editors note: Add code in alphabetical sequence ETLP Electronic Ticketless Product Information (bilaterally agreed) 1708 B6.8/P When a party/group/tour holds a reservation under a common name (corporate name) in one PNR, the first surname of such a party/group/tour on a list message can include a Corporate Or Group Name Element B6.8/P If a party/group/tour has a marketing flight number reservation, this element appears only with the first individual appearing on the list B6.5/P Section 3 Examples PNL Message Example (Part1) -BCN30Y 2BREEMER/GEORGEMR/TANYAMRS-B10 1BRYAN/GARYMR-D6.L/ R/STCR HK1 BROKEN HIP IN PLASTER ESCORTED BY MISS ALLEN NURSE 1ZBAUD/LAURAMS.O/IB441Y05PMI.R/RQST HK1 5A 5ZZ/STCR-D PNL Message Example (Part2)

118 5ZZ/MEDA.L/ R/OTHS 5SEATS BLOCKED FOR.RN/STRETCHER AND PATIENT BRYAN ENDPNL = NNNN 1708 B6.7/P Subsequently in RES, Mr. Mackie is confirmed into F-class from his Y-class waitlist. His PNR has only a change of class and status, so the ADL shows ADD 1MACKIE/IANMR.L/CDE1RY/BA.R/RQST HK1 2A -MSP206Y DEL 1MACKIE/IANMR.L/CDE1RY/BA -MSP13F ADD 1MACKIE/IANMR.L/CDE1RY/BA.R/RQST HK1 2A -MSP206Y DEL 1MACKIE/IANMR.L/CDE1RY/BA 1708 B6.4/P PNL Message Example (Part 2) 1OPPERSTAL/GINAMRS 1PETERSON/JAMESMR.R/SVC HK1 E23/LOUNGE ACCESS/ C1.R/ASVC HK1 C92//DECK OF CARDS/ C1 1SMITH/NOELMR.R/FQTV BA TEPPATI/TUSHIMR.L/7232H3.R/NSSA HK1 22C.R/ASVC HK1 S23/NSSA/CHARGEABLE SEAT 22C/ C2 2THOM/JANEDR/DEREKMR.L/DF9323.R/ESVC HK1 X99/EXCESS BAGGAGE 21KILOS/ C1-1THOM/JANEDR Filing Period: Effective Date: 18 February June April 2008

119 1715 B6.4/P B6.12/P 0 RECOMMENDED PRACTICE 1715 PASSENGER SERVICE MESSAGE (PSM) (amending) PSC(29) B6.12/P 2.4 FLIGHT ELEMENT This element is mandatory For a code-share flight, show operating carrier and flight number. (Renumber accordingly) 1715 B6.4/P 2.6 SSR/OSI/AUX CODES AND COUNTS ELEMENT allowable SSR/OSI/AUX codes list the SSR/OSI/AUX code(s) and allowable SSR/OSI/AUX codes ASVC Additional Services, segment-associated BLND EMIG ESVC Notification of EMD for Additional Services Other than Optional Services STCR SVC Additional Services, not segment-associated 1715 B6.12/P 2.9 ONWARD CONNECTION If the onward connection is a code-share flight, show operating carrier and flight number The entry begins on a new line, preceded with one space. (Renumber accordingly) Filing Period: Effective Date: 18 February June April 2008

120 1716 B6.4/P 0 RECOMMENDED PRACTICE 1716 PASSENGER INFORMATION LIST (PIL) (amending) PSC(29) B6.4/P 2.4 PASSENGER INFORMATION (Message-specific Data) As a minimum, the PIL includes passengers who have one or more SSR or OSI SSR/OSI/AUX services. Filing Period: Effective Date: 18 February June April 2008

121 1718 B6.12/P 0 RECOMMENDED PRACTICE 1718 PASSENGER TRANSFER MESSAGE (PTM) (amending) PSC(29) B6.12/P 2.4 FLIGHT ELEMENT This element is mandatory For a code-share flight, show operating carrier and flight number For construction rules, see RP1707b, Flight element. (Renumber accordingly) If the onward connection is a code-share flight, show operating carrier and flight number Construction Rules Field Example Data Field Name(see RP 1707a/b) operating connecting flight XY311 flight (Renumber accordingly) Filing Period: Effective Date: 18 February June April 2008

122 1719 B6.4/P 0 RECOMMENDED PRACTICE 1719 PASSENGER FINAL SALES MESSAGE (PFS) (amending) PSC(29) B6.4/P The categories are: PXLST ADDSV Add Additional Services (for example, ESVC) 2.17 PAXLST ELEMENTS 2.18 ADDITIONAL SERVICES INFORMATION This element is conditional The PFS includes details of Additional Services collected at the airport for ESVC only For definition and construction rules see RP END ELEMENT 2.19 END ELEMENT Filing Period: Effective Date: 18 February June April 2008

123 1719b B6.4/P 0 RECOMMENDED PRACTICE 1719b PASSENGER RECONCILE LIST (PRL) (amending) PSC(29)1719b 1719b B6.4/P 2.18 REMARKS ELEMENT This element follows the guidelines of RP 1708 (PNL/ADL) for the SSR and OSI inclusion of SSR/OSI/AUX codes. Filing Period: Effective Date: 18 February June April 2008

124 1719c B6.1/P B11 0 RECOMMENDED PRACTICE 1719c ELECTRONIC TICKET LIST (amending) PSC(29)1719c 1719c B6.1/P 1.2 TIME OF DISPATCH The Electronic Ticket List (ETL) is sent immediately after flight departure as bilaterally agreed. 1719c B EXAMPLE OF ETL WITH MARKETING FLIGHT ELEMENT AND BAGGAGE INFORMATION 1ALLEN/ROSAMRS.L/ZG4V9W.R/TKNE HK /3.BG/101.R/FOID HK1 PP M/KL2019C21AMSCDG Filing Period: Effective Date: 18 February June April 2008

125 1719d B9 0 RECOMMENDED PRACTICE 1719d TICKETLESS PRODUCT LIST (TPL) (new) PSC(29)1719d 1719d B9 RECOMMENDED that: In order to report the use of a Ticketless Product for actually boarded passengers, Members shall use the message as described below. Section 1 General Description 1.1 DEFINITION The Ticketless Product List shows a list of actually boarded passengers who used a Ticketless Product for travel. 1.2 TIME OF DISPATCH The TICKETLESS PRODUCT LIST (TPL) is dispatched after flight departure, as bilaterally agreed. 1.3 MESSAGE IN MULTIPLE PARTS If the TPL 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 TPL contains the following components: Address Element HDQRMQI Communications Reference Element.CPHKMQI Message Identifier Element TPL Flight Element QI0055/13MAR CPH PART1 Seat Configuration Element CFG/F22C33Y222 Actual Time of Departure Element ATD/1427 Totals By Destination Element -CPH010C Name Element 1BASSET/AMYMRS Automated PNR Address Element.L/ABC123/QI Remarks Element.R/ETLP HK AN4567 Remarks Continuation Element.RN/CO TRAVEL PERMITTED Pieces/Weight Data Element.W/P/5 Baggage Pooling Element.BG/003 Baggage Tag Details Element.N/ /SFO End Element ENDPART1

126 1719d B9 Section 2 Detailed Specifications 2.1 ADDRESS ELEMENT This element is mandatory This element is governed by the IATA Systems and Communications Reference Manual For construction rules, see RP 1707b, Address Element. 2.2 COMMUNICATIONS REFERENCE ELEMENT This element is mandatory This element is governed by the IATA Systems and Communications Reference Manual For construction rules, see RP 1707b, Communications Reference Element. 2.3 MESSAGE IDENTIFIER ELEMENT This element is mandatory The Ticketless Product List uses the message identifier TPL For construction rules, see RP 1707b, Message Identifier Element. 2.4 FLIGHT ELEMENT This element is mandatory For construction rules, see RP 1707b, Flight Element 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 This element is optional For construction rules, see RP 1707b, Seat Configuration Element 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 This element is optional For construction rules, see RP 1707b, Actual Time of Departure Element Example: ATD/ TOTALS BY DESTINATION ELEMENT This element is mandatory Only compartments that have boarded passengers are included in the message For construction rules, see RP 1707b, Totals by Destination Element Example: -JFK123Y

127 1719d B9 2.8 NAME ELEMENT This element is mandatory Names appear in the message in alphabetical order under each destination/compartment A surname is to be listed individually; for example, 2SMITH/ANDREW/BARBARA is listed as 1SMITH/ANDREW and 1SMITH/BARBARA For construction rules, see RP 1707b, Name Element Examples: 1JONES/TRAVISMR 1MILLER/JAMES 1SMITH/THOMASMR 1SMITH/SUSANMRS 2.9 AUTOMATED PNR ADDRESS This element is conditional When multiple record locators exist for an entry, include the record locator only of the addressee of the TPL, if known For construction rules, see RP 1707b,.L/ Automated PNR Address Element. This element uses element ID.L/ Example:.L/6Y21AS/CX 2.10 REMARKS ELEMENTS This element is mandatory The Name Element is followed by Remarks Elements for only ETLP 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/ Examples: 1BAKER/BOBMR.L/543654/AY.R/ETLP HK TAYLOR/SIMONDR.L/987G4R/AY.R/ETLP HK1 QI MOTT/CELINEMS.L/9548T6/AY.R/ETLP HK1 RC PIECES/WEIGHT DATA ELEMENT This element is optional For pooled baggage it appears only with the Name Element for the head of pooled baggage For construction rules, see RP 1707b,.W/ Pieces/Weight Data Element. This element uses element ID.W/ Examples:.W/P/5.W/K/2/ BAGGAGE POOLING ELEMENT This element is conditional It is used when passenger baggage is pooled It appears with the Name Element for every member of a baggage pool When pooled baggage is being used, the Name Element of the Head of Pooled Baggage is indicated either by.w/ and/or.n/ Elements For construction rules, see RP 1707b,.BG/Baggage Pooling Element. This element uses element ID.BG/ Example:.BG/001

128 1719d B BAGGAGE TAG DETAILS ELEMENT This element is conditional It is used when baggage tag number(s) exist in the DCS for the passenger For pooled baggage it appears only with the Name Element for the head of pooled baggage For construction rules, see RP 1707b, Baggage Tag Details Element Examples:.N/ /SFO.N/NW234567/1/RST 2.14 END ELEMENT This element is mandatory For construction rules, see RP 1707b, End Element The Ticketless Product List (TPL) ends with ENDTPL. 1719d B9 Section 3 Examples 3.1 EXAMPLE OF A TPL WITH NAMES AND BAGGAGE DETAILS, PRESENT FOR SOME DESTINATION/COMPARTMENTS, BUT NOT ALL CPHFFQI.SGDRQQI TPL QI798/15MAR SGD PART1 -CPH004F 1ANDERS/EMILYMRS.L/4567AS/IB.R/ETLP HK1 1R23A BENNETT/TIM.L/348B22/IB.R/ETLP HK1 1233T8383E838.R/ETLP HK1 INF1233T8383E838 1BENNETT/SARAMRS.L/348B22/IB.R/ETLP HK1 12S35T SMITH/ABNERMR.L/39328J/IB.R/ETLP HK H837U82 -CPH006Y 1APPLE/ANNE.L/3GH234/IB.R/ETLP HK1 12A312M BANANA/JAMESMR.L/3246MH/IB.R/ETLP HK1 123H5454Y5454 1BANANA/CAMERONMISS.L/3246MH/IB.R/ETLP HK1 123R9W393D939 2MINT/GINA/UNA.L/346834/IB.R/ETLP HK2 12T356W566K66 1PINEAPPLE/MARIE.L/32J454/IB.R/ETLP HK1 1238F898G9898 ENDTPL = NNNN 1719d B9 3.2 EXAMPLE OF NIL TPL CPHFFQI.SGDRQQI TPL QI798/15MAR SGD PART1 NIL ENDTPL = NNNN Filing Period: Effective Date: 18 February June April 2008

129 1720a P2.3 0 RECOMMENDED PRACTICE 1720a STANDARD THIRTEEN-DIGIT NUMBERING SYSTEM FOR TRAFFIC DOCUMENTS (amending) 1720a P2.3 PSC(28 29)1720a Attachment A A* PASSENGER TRAFFIC DOCUMENT NUMBER ASSIGNMENTS Stock Provider Party. Agency (BSP) Type of Form Off-Premise Transitional Automated Ticket (OPTAT) & Electronic Ticket No. of Coupons 4 Coupon IATA Resolution / Recommended Practice 722a 722g ATA Resolution Airline Code Form Code Serial Number Number of Digits in Serial Number Method of Check Digit Calculation (see below) Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d 722g Agency (BSP) 2 9 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Passenger Ticket (Domestic Only) Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (4 inch Pre-printed) -- Various -- 4 Coupon _ 722g 722a 722g _ _ 3 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (4 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (4 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (4 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (4 inch Pre-printed) -- 4 Coupon 722a 722g

130 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (OPTAT) & Electronic Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon -- 4 Coupon 722a/722g a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Off-Premise Electronic Ticket (OPET) --

131 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) 4 Coupon -- 4 Coupon -- 4 Coupon 722a 722g 722a 722g 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Pre Coupon 722a 722g

132 printed) Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (3.5 inch Preprinted) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (7 inch Pre-printed) -- 4 Coupon 722a 722g

133 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (8 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (Single Feed 3.25 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket (Single Feed 3.25 inch Pre-printed) -- 4 Coupon 722a 722g Agency (BSP) 2 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Passenger Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon -- 4 Coupon g 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g

134 Agency (BSP) 2 10 Agency (BSP) 2 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency (BSP) 2 10 Agency 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Passenger Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon -- 4 Coupon 722a 722g g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g 722a 722g Off-Premise Electronic Ticket -- (OPET) Off-Premise Transitional 4 Coupon 722a

135 (BSP) 2 10 Agency (BSP) 2 9 Agency (BSP) Automated Ticket Off-Premise Electronic Ticket (OPET) Passenger Ticket (Domestic Only) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Various -- Coupon-by- Coupon 722g 3 _ 722g 3 9 _ 8 722d/722g _ 3 Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d/722g Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d/722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d/722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d/722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 9 Agency (BSP) Off-Premise Electronic Ticket (OPET) Passenger Ticket (Domestic Only) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & -- Various -- Coupon-by- Coupon _ 722g 5 4 _ 8 722d/722g _ 3

136 5 Electronic Ticket Agency (BSP) 2 9 Agency (BSP) Off-Premise Electronic Ticket (OPET) Passenger Ticket (Domestic Only) Off-Premise Electronic Ticket (OPET) Off Premise Transitional Automated Ticket (OPTAT) & Electronic Ticket -- Various -- 4 Coupon _ 722g 5 8 _ 8 722d/722g _ 3 Agency (BSP) 2 9 Agency (BSP).2 5 Off-Premise Electronic Ticket (OPET) Passenger Ticket (Domestic Only) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Various -- Coupon-by- Coupon _ 722g 6 0 _ 8 722d/722g _ 3 Agency (BSP) 2 9 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Passenger Ticket (Domestic Only) Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- Various -- 4 Coupon _ 722g 722a 722g 6 3 _ _ 3 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g

137 Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 Agency (BSP) Off-Premise Electronic Ticket (OPET) Passenger Ticket Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- 4 Coupon -- Coupon-by- Coupon g d/722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) 2 10 Off-Premise Electronic Ticket (OPET) Off-Premise Transitional Automated Ticket -- 4 Coupon 722a 722g Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d/722g Agency (BSP) Off-Premise Electronic Ticket (OPET) Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket -- Coupon-by- Coupon 722d/722g Off-Premise Electronic Ticket (OPET) --

138 1720a P2.3 Attachment A 3 Up to 31 May 2008 this form code was classified as Off-Premise Transitional Automated Ticket (OPTAT) & Electronic Ticket using check digit method 2. 5 Up to 31 May 2008 this form code was classified as Off-Premise Automated Ticket/Boarding Pass (OPATB) & Electronic Ticket using the same check digit method 3. 9 For travel agency service fee only. Up to 31 May 2008 this form code was classified as Domestic Only with no specified check digit method. 10 Up to 31 May 2008 this from code was classified as Off-Premise Transitional Automated Ticket (pre-printed) using check digit method 1. A Filing Period: Effective Date: 18 February June April 2008

139 1740ca B8.11/P B8.12/P B8.13/P 0 RECOMMENDED PRACTICE 1740c RADIO FREQUENCY INDENTIFICATION (RFID) SPECIFICATIONS FOR INTERLINE BAGGAGE (amending) * PSC(29)1740c Table 1: Object Identifiers & Data Elements Object Identifier Object Mandatory Status Memory Bank Decoded Data Characteristics Destination Code N R/W 11 M[3] Internal Airport Status N R/W 11 ATL or not See encoding rules below 1740c B8.11/P Encoding Rules for Security Information Object ID Security Information consists of: Passenger Status 1-bit 0=non-selectee; 1 = selectee Screening Level 3-bits 000 = no screening done 001 = level = level = level = level = level 5 Screening Status 1-bit 0=cleared failed 1=failed cleared This information may be optimally encoded in 5 bits. ISO encoding is byte aligned, so this means that there will be 3 bits that can be used for new applications at a later date. These three bits shall always follow the security information. The position definition of each bit is as follows: Bit 8 Passenger Status Bit 7 Screening Status Bit 6 Reserved for future use Bit 5 Reserved for future use Bit 4 Reserved for future use Bits 1-3 for Screening Level MSB

140 1740c B8.12/P Insert a new paragraph: Encoding Rules for Internal Airport Status Object ID Internal Information consists of: Bit 8: ATL 1-bit 0=not-ATL; 1 = ATL Bits 7-1: Reserve for future use 1740c B8.13/P Encoding rules for the flight data Object ID The flight data is comprised from: Carrier Code e.g., KL 2 characters Flight Number e.g., numbers Date e.g. 8 th August- 2 numbers, 3 characters Annual Julian Date e.g., numbers (representing 8 th August) Arrival City Airport e.g., AMS 3 alpha-characters Passengers Class of travel e.g., (C) 1 alpha character representing Club Flight date would be encoded in Julian format: e.g., KL193008AUG220AMSC The flight data refers to the baggage, not to the passenger. This can be different to the passenger routing in some cases. The class of travel refers to the passenger s booked class of travel. Filing Period: Effective Date: 18 February June April 2008

141 1743a B8.7/P 0 RECOMMENDED PRACTICE 1743a TRACING PROCEDURE FOR MISSING CHECKED BAGGAGE (amending) PSC(29)1743a 1743a B8.7/P Baggage shall be delivered to its owner by following the provisions in Resolution 743a 780; except when baggage is delivered by a handling agent on behalf of the carrier handled by it (principal), the following shall apply; 6.1 the methods of baggage delivery and the settlement of any costs incurred in the delivery, shall be bilaterally agreed upon between the handling agent and the principal;. Filing Period: Effective Date: 18 February June April 2008

142 1743e B8.8/P 1743e B8.8/P 0 RECOMMENDED PRACTICE 1743e BAGGAGE IRREGULARITY REPORT (amending) PSC(29)1743e Recommended that when assessing a station responsible for a baggage mishandling(s), Members use the irregularity codes shown in Attachment A. Irregularity codes do not establish proof of responsibility for mishandlings and shall not be used for proration purposes. 1743e B8.8/P 1. PURPOSE 1.1 Irregularity Codes and station responsibility details, when established should be applied by users of baggage management systems to assist in assessing why baggage mishandlings occur. 1.2 Baggage mishandling management statistics should be compiled and regularly distributed according to airline and Regulatory requirements. 1.3 In order to improve baggage handling methods and systems including transfer baggage processes, the mishandled file creation airline or airline on whose behalf the mishandled baggage file is created, should review the processes used at the station at which the passenger joined its flights include the transfer baggage process of the airport or delivering carrier to establish any underlying cause. 1.4 Where possible, and in association with the airport, third party handler and/or other airlines discuss at Local Baggage Committee meetings what actions are necessary and seek to introduce procedures aimed at reducing baggage mishandlings. Attachment A IRREGULARITY CODES Legend: P = Primary code S = Secondary code P 10 Origin Station Errors Tagging Check In S 11 Incorrect or no entries on tag S 12 Not checked to final destination S 13 Checked to final destination 2 Separate Contracts S 14 Baggage not labelled S 15 Wrong bag labelled i.e. tag switch S 16 Bag received too late from check in S 17 Old tag not removed S 18 Baggage not reconcilable, no or wrong data in check-in systems Bag (s) not authorised to load P 20 Origin Station Errors Short-shipped Failed to Load S 21 Bag left at station of origin although /correctly labelled S 22 Bag received too late from check-in S 23 Standby baggage left behind S 24 Bag checked-in airside (intercepted at gate, security, etc.) S 25 Gate checked baggage left behind S 26 Off-loading due space/weight restrictions or resulting from unserviceable handling equipment (not weather see RL 60 s). S 27 Local passenger rerouted, bag not rerouted. A

143 1743e B8.8/P P 30 Any Station Errors Loading / Offloading S 31 Sorting or loading error wrong aircraft S 32 Off-loaded by error S 33 Not off-loaded S 34 Loaded behind cargo S 35 Sorting or loading error wrong container or / wrong compartment / behind cargo P 40 Station Errors Arrival Station S 41 Delivered to wrong area S 42 Delayed delivery to claim area S 43 Delayed delivery of oversized/odd sized baggage to claim area A P 50 Transfer Baggage Station S 51 Passenger rerouted, bag not rerouted S 52 Interline MCT (Minimum Connecting Time) available Left behind although correctly labelled and within MCT S 53 Interline MCT not available Sub MCT connection due late arrival of delivering carrier S 54 Interline Bag(s) not made available by inbound carrier per local agreement Failure of other carrier to deliver bag within agreed standard ( S 55 Online (own carrier) MCT available Transfer baggage not segregated into transfer container or hold S 56 Online (own carrier) MCT not available Missed on-line transfer (own carrier) S 57 Missed Interline transfer (alliance or codeshare partner) Alliance partner S 58 Codeshare partner S 58 Baggage not reconcilable, no or wrong data in check-in system S 59 Bag (s) not authorised to load P 60 Airport-General S 61 Congestion due Industrial dispute i.e. strike S 62 Congestion due to Other reasons (i.e. meteorological) S 63 Mishandling due Airport Security (B.R.S./X-Ray issue) S 64 Mishandling due u Unserviceable equipment Airport owned (belt/sortation system, etc.) S 65 Space/Weight restrictions due meteorological conditions S 66 Error by non aviation carrier, e.g. Cruise or ground transportation S 67 Congestion due to Ccustoms, police, immigration actions P 70 Miscellaneous S 71 Ticketing errors S 72 Bag correctly labelled, ppassenger off-loaded, bag not off-loaded S 73 Bag not claimed by passenger where required S 74 Bag switch, e.g. passenger takes wrong bag S 75 Security (not identified by passenger at security check, security removed item S 76 Found without tag S 77 Errors by other carrier, e.g. tagging, etc. S 78 Reason for mishandling not detectable S 79 Report Ccreated in error

144 1743e B8.8/P P 80 Damage S 81 Broken locks, zips or hinges S 82 Handle or strap or wheel broken or torn off S 83 Damage to security inspected baggage S 84 Bag dented/torn or ripped S 85 Bag crushed S 86 Frame broken S 87 Superficial damage including minor scratches S 88 Wet due rain or liquid spillage in hold S 89 Damaged contents A P 90 Pilferage S 91 Pilferage including bag damage S 93 Pilferage from security inspected baggage S 95 Pilferage from crew baggage S 96 Pilferage from crew baggage including bag damage S 98 Pilferage from security inspected crew baggage Note 1: For the purpose of reporting, a Handling Agent acting on behalf of a carrier shall be considered to be that carrier. Note 2: The station responsible for the mishandled shall be identified by the IATA approved three-letter location code. If the bag is not yet found, or if the responsible station cannot be identified, the code XXX shall be used instead of a location code. Filing Period: Effective Date: 18 February June April 2008

145 1745 B8.2/P B8.3/P B8.4/P B8.5/P 0 RECOMMENDED PRACTICE 1745 BAGGAGE INFORMATION MESSAGES (amending) PSC(29) B8.4/P 1.3 Additional Recommended Codes for Baggage Identification or Handling. CPY CPYA CPYD CPYN. PBHA. TGRQ. A copy tag is required or has been done for this baggage A copy tag is authorized for this baggage A copy tag will be performed by the DCS A copy tag is not authorized for this baggage Problem Baggage Handling Area Tag printing request 1745 B8.5/P 1.6 DELETE FUNCTION The DEL function should be used to delete, or mark a record as deleted on the outbound flight(s) and conditionally on the onward flights (.F, conditionally.o). (See for an example of the DEL function.) A tag number that has been deleted may be reused for the same passenger for the same flight and date. See Section 1.9 for Processing Of Duplicate Tag Numbers. Examples: 1745 B8.3/P (M) Baggage Source Indicator T (M) Local, Transfer or Terminating Airport Code ZRH (N) Part Number / show only oblique; no data (C) Message Reference Number / / (O) Acknowledgement Request /A (O) Encryption /123ABC456Z (O) MESSAGE ACKNOWLEDGEMENT DETAILS (M) Element Identifier.A (M) Sender s Message Reference Number /BA2190/123 (M) Type of Baggage Message and Status Indicator being acknowledged /BRQ (M) ACK or NAK /NAK (O) Free Text /COPY TAG (C) OUTBOUND FLIGHT INFORMATION (M) Element Identifier.F (M) Airline and Flight Number /SR10/1 (M) Date /16APR (M) Destination Or Transfer Airport Code /JFK (O) Class Of Travel Of Baggage /J (C) INBOUND FLIGHT INFORMATION (M) Element Identifier.I (M) Airline and Flight Number /AZ318 (M) Date Of Departure /16APR (M) Originating Airport Code /FCO (O) Class Of Travel Of Baggage /J

146 (C) ONWARD FLIGHT INFORMATION (M) Element Identifier.O (M) Airline and Flight Number /UA20/3 (M) Date /16APR (M) Destination Or Transfer Airport Code /DEN (O) Class Of Travel Of Baggage /J (C) BAGGAGE TAG DETAILS (M) Element Identifier.N (M) Baggage Tag Number /0/0/ (C) Number of Consecutive Tags 0/0/3 (M) HANDLING LOCATION (M) Element Identifier.H (C) Handling Terminal /T4 (C) Handling Bay/Pier /GREEN (C) Handling Gate/Stand /D B8.3/P (C) PASSENGER NAME (M) Element Identifier.P (M) Separator (oblique) / (O) Number Of Passengers With This Surname 2 (M) Passenger s Surname SMITH (O) Given Name and/or Initials and/or Title /TOMMR (O) Additional Given Name and/or Initials and/or Title /ALICE (C) FREQUENT TRAVELLER NUMBER (M) Element Identifier.Y (M) Frequent Traveller ID Number /KL66250/3 (O) Tier Information /GOLD (C) CORPORATE OR GROUP NAME (M) Element Identifier.C (M) Corporate Or Group Name /IATA TOUR (C) AUTOMATED PNR ADDRESS (M) Element Identifier.L (M) Automated PNR Address /XY1C3P (C) BAGGAGE TAG PRINTER ID (M) Element Identifier.T (M) Bag Tag Printer ID /321A4C (C) BAGGAGE EXCEPTION DATA (M) Element Identifier.E (M) Exception Type /CPY (M) END OF MESSAGE IDENTIFIER ENDBRQ

147 1745 B8.3/P 2.2 QUICK REFERENCE INDEX OF INFORMATION MESSAGE ELEMENTS Version 1 * ////////////////////MESSAGES BTM BSM BPM BUM BNS BCM BRQ ELEMENT IDENTIFIER TITLE EXAMPLES //////////////////// STANDARD MESSAGE BTM; BSM; BPM; BUM; BNS; BCM M M M M M M M IDENTIFIER (SMI) SECONDARY LEVEL MESSAGE BAM; FOM; FCM; FFM; DBM;BMM N/A N/A N/A N/A N/A M N/A IDENTIFIER CHANGE OF STATUS CHG or DEL N/A C N/A N/A N/A N/A N/A INDICATOR.A MESSAGE.A/QF006097/BSM/ACK N/A N/A N/A N/A N/A * O ACKNOWLEDGEMENT DETAILS or.a/lh /bsm/nak/flt DEPARTED.B BAGGAGE IRREGULARITIES.B/OFF/ N/A N/A C N/A N/A * N/A.C CORPORATE OR GROUP.C/SITA TOUR O O O O C * O NAME.D BAG CHECK IN DETAILS.D/TRST/QQP/07MAY/0845L/RA/ O O N/A N/A N/A N/A C TRAIN5 or.d/trst/qqp/07may/084533l.e BAGGAGE EXCEPTION DATA.E/RUSH O O O O N/A * C.F OUTBOUND FLIGHT.F/LH1274/05MAY/JFK/F M C C M M * C INFORMATION.G GROUND TRANSPORT.G///MARRIOT Alphen ad Rijn or N/A N/A N/A N/A N/A N/A N/A.G//25NOV2200/Willem de Zwijger laan 234 alphen ad Rijn.H HANDLING LOCATION.H/T4//16 or.h//green or.h///d46 N/A N/A N/A N/A N/A * M.I INBOUND FLIGHT.I/KL067/02APR/AMS/Y M C O O N/A * C INFORMATION.J PROCESSING INFORMATION.J/R/43S/120D32/02APR/1545L/B2 N/A N/A O N/A N/A N/A N/A.K DEFAULT MESSAGE PRINTER.K/69C626 N/A O O O N/A * N/A.L AUTOMATED PNR ADDRESS.L/QRE7Q6 O O O O C N/A C.M UNUSED N/A N/A N/A N/A N/A N/A N/A N/A.N BAGGAGE TAG DETAILS.N/ M M C M M * C.O ONWARD FLIGHT.O/UA423/02APR/DEN/F C C O O C * C INFORMATION.P PASSENGER NAME.P/1SMITH/HMR M O O O C * C.Q LOAD SEQUENCE NUMBER.Q/023 N/A N/A C C N/A * N/A.R INTERNAL AIRLINE DATA.R/FREE TEXT O O O O O * N/A.S RECONCILIATION DATA.S/Y/23A/C/234/333/Y N/A C O O N/A N/A N/A.T BAGGAGE TAG PRINTER ID.T/ N/A O N/A N/A N/A N/A C.U LOADING DATA.U/AVE12345NE/11R/T/Y/NRT/Y/ N/A N/A O O N/A * N/A NW009/04MAR/SEL.V VERSION AND.V/1TYYZ/PART1/ /A M M M M M M M SUPPLEMENTARY DATA.W PIECES AND WEIGHT DATA.W/K/2/38/8 or.w/l/2/84/16 or O O O N/A O * N/A.W/P/3.X BAGGAGE SECURITY.X/LEVEL1 or.x/handsearch O O O O N/A * N/A SCREENING.Y FREQUENT TRAVELLER.Y/BXJ2238 O O O O C * C NUMBER.Z UNUSED N/A N/A N/A N/A N/A N/A N/A N/A END OF MESSAGE IDENTIFIER ENDBTM, ENDBSM, ENDBPM, etc. M M M M M M M

148 1745 B8.2/P Y Frequent Traveller Number; 6 to 55 characters Construction Example Format Element identifier: Full stop (.), Y.Y.a Separator: oblique (/) / / Frequent Traveller ID Number BXJ2238 m(m..m) 1 to 25 characters Separator: oblique (/) / / Tier identifier GOLD m(m..m) 1 to 25 characters End of element delimiter < Example:.Y/BXJ2238/GOLD< 1745 B8.5/P To delete a record in a sortation or reconciliation system at JFK by SR BTM< DEL<.V/1TJFK////123ABC456Z<.I/SR10/1/18APR/JFK/C<.F/DL671/18APR/ATL/C<.N/0/0/ /0/1<.S/N< ENDBSM< Standard Message Identifier Delete Function Version; Transfer bag at JFK with Encryption Inbound from ZRH on SR101 Transfer to DL671 to ATL Bag Tag Number;Number of consecutive tags Reconciliation data; Auth. to load = No End of Message Identifier Renumber original with wording change Example of BTM on involuntary itinerary change (IROP) 1745 B8.2/P 4.8 CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BAGGAGE SOURCE MESSAGE (O) FREQUENT TRAVELLER NUMBER (M) Element Identifier.Y (M) Frequent Traveller ID Number /AZ150370/KL66250/3 (O) Tier Information /GOLD

149 1745 B8.5/P To delete a record in a sortation or reconciliation system at ZRH by SR BSM< Standard Message Identifier DEL<.V/1LZRH////123ABC456Z<.F/SR10/1/18APR/JFK/C<.N/0/0/ /0/1<.S/N< ENDBSM< Delete Function Version; Local bag at ZRH with Encryption Carrier/Flight Nbr; Date; Destination; Class Bag Tag Number; Number of consecutive tags Reconciliation data; Auth. to load = No End of Message Identifier To delete a record in a sortation or reconciliation system at JFK by SR BSM< Standard Message Identifier DEL<.V/1TJFK////123ABC456Z<.F/SR10/1/18APR/JFK/C<.O/SR1234/18APR/ATL/C<.N/0/0/ /0/1<.S/N< ENDBSM< Delete Function Version; Transfer bag at JFK with Encryption Carrier/Flight Nbr; Date; Destination; Class Onward Connection Bag Tag Number; Number of consecutive tags Reconciliation data; Auth. to load = No End of Message Identifier Example of BSM for re-routing process Example of BSM for re-flighting process BSM for terminating bag at PIT for US flight 817 from FRA Example of the Change Function Example of BSM with multiple usage of elements BSM for remote checked in bag from home BSM for remote checked in bag from Train Station BSM for remote checked in bag from a cruise ship at a Port BSM for Ground Transport at the destination BSM with copy tag authorization or not 1745 B8.2/P 5.8 CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BAGGAGE PROCESSED MESSAGE (O) FREQUENT TRAVELLER NUMBER (M) Element Identifier.Y (M) Frequent Traveller ID Number /BA /KL66250/3 (O) Tier Information /GOLD

150 1745 B8.2/P 6.8 CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BAGGAGE UNLOAD MESSAGE (O) FREQUENT TRAVELLER NUMBER (M) Element Identifier.Y (M) Frequent Traveller ID Number /BA /KL66250/3 (O) Tier Information /GOLD 7.8 CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BAGGAGE NOT SEEN MESSAGE (O) FREQUENT TRAVELLER NUMBER (M) Element Identifier.Y (M) Frequent Traveller ID Number /BXJ2238/KL66250/3 (O) Tier Information /GOLD 9.8 Construction of Elements and Data Items in the Baggage Manifest Message (O) FREQUENT TRAVELLER NUMBER (M) Element Identifier.Y (M) Frequent Traveller ID Number /BA /KL66250/3 (O) Tier Information /GOLD 1745 B8.3/P Members who transmit and receive Baggage Information Messages, including the Baggage Transfer Message (BTM), Baggage Source Message (BSM), Baggage Processed Message (BPM), Baggage Unload Message (BUM), Baggage Not Seen Message (BNS), Baggage Control Message, Baggage Manifest Message (BMM) and the Baggage Request (BRQ), shall apply the following definitions, formats and specifications for the creation, transmission, receipt and interpretation of those messages. Structure Of This Document Section 1 Introduction Section 2 Data Dictionary Section 3 Baggage Transfer Message (BTM) Section 4 Baggage Source Message (BSM) Section 5 Baggage Processed Message (BPM) Section 6 Baggage Unload Message (BUM) Section 7 Baggage Not Seen Message (BNS) Section 8 Baggage Control Message (BCM) Section 9 Baggage Manifest Message (BMM) Section 10 Baggage Request (BRQ)

151 1745 B8.3/P Section 10 Baggage Request Message (BRQ) 10.1 PURPOSE The BRQ is designed to request information for processing of baggage by automated baggage systems DISTRIBUTION PROCEDURES A BRQ is sent by an automated baggage system to the departure control system of a baggage from which it needs information and optionally permission to perform a specific process, like re-tagging (see chapter Re-tagging process in RP1800 for more details) or re-tagging MESSAGE ACKNOWLEDGEMENT The sender of a BRQ may request an acknowledgement to the message by adding a Message Reference Number and the Acknowledgement Request indicator to the.v element. The Reference Number can be up to 10 characters, formatted to the airline s discretion. Request for an Acknowledgement example:.v/1lsyd//qf620/0/98/a 10.4 PARTITIONING OF MESSAGES BRQs, whether single or batched, may not be partitioned ELEMENT SEQUENCE SUMMARY The following shows the sequence of elements in a BRQ. Element Requirement Definition BRQ Mandatory Standard Message Identifier.V Mandatory Version and Supplementary Data.A Optional Message Acknowledgement Details.F Conditional Outbound Flight Information.I Conditional Inbound Flight Information.O Conditional Onward Flight Information.N Conditional Baggage Tag Details.D Conditional Baggage Check-In Details.H Mandatory Handling Location.P Conditional Passenger Name.Y Conditional Frequent Traveller Number.C Conditional Corporate or Group Name.L Conditional Automated PNR Address.T Conditional Baggage Tag Printer ID.E Conditional Baggage Exception Data ENDBRQ Mandatory End of Message Identifier

152 1745 B8.3/P 10.6 MULTIPLE USE OF ELEMENTS The following schematic illustrates the multiple use of elements in the BRQ. Element Description.A Message Acknowledgement Details.F Outbound Flight (LAX NRT).I Inbound Flight (ORD LAX).O Onward Flight (NRT SIN).O Onward Flight (SIN SYD).N Baggage Tag Details.D Baggage Check-In Details.H Handling Location.P Passenger Name.Y Frequent Traveller Number.C Corporate or Group Name.L Automated PNR Address.T Baggage Tag Printer ID.E Baggage Exception Data 10.7 USE OF CONDITIONAL ELEMENTS AND DATA ITEMS The.F element (Outbound Flight Information) is mandatory when the data is available The.I element (Inbound Flight Information element) is mandatory when the data is available The.O element (Onward Flight Information) is mandatory when the data is available The.N element (Baggage tag details) is mandatory when the data is available The.P element (Passenger name) is mandatory when the data is available The.Y element (Frequent traveller number) is mandatory when the data is available The.C element (Corporate or Group name) is mandatory when the data is available The.L element (Automated PNR Address) is mandatory when the data is available The.T element (Baggage tag printer Id) is mandatory when the data is available The.E element (Baggage Exception Data) is mandatory for a copy tag request The.V element (version and Supplementary Data) may contain a conditional Message Reference Number and Acknowledgment Request Indicator CONSTRUCTION OF ELEMENTS AND DATA ITEMS IN THE BRQ Use Elements And Data Items (M) STANDARD MESSAGE IDENTIFIER Example BRQ (M) VERSION AND SUPPLEMENTARY DATA (M) Element Identifier.V (M) Data Dictionary Version Number /1

153 1745 B8.3/P 10.9 EXAMPLE MESSAGES BRQ with copy tag request BRQ<.V/1LZRH////123ABC456Z<.F/LH4210/18APR/JFK/Y.N/ <.H/T4/GREEN/K150.E/CPY ENDBRQ< Standard Message Identifier Version; Local bag at ZRH with encryption Outbound Carrier/Flight; Date; Destination; Class Bag Tag number; Number of consecutive tags Handling location Copy tag request End of Message Identifier 1745 B8.3/P BRQ with tag request BRQ<.V/1LZRH////123ABC456Z<.F/LH4210/18APR/JFK/Y.N/ <.H/T4/GREEN/K150.E/TGRQ ENDBRQ< Standard Message Identifier Version; Local bag at ZRH with encryption Outbound Carrier/Flight; Date; Destination; Class Bag Tag number; Number of consecutive tags Handling location Tag request End of Message Identifier Note: Other elements available from the 2D barcode or magstripe or other sources can be included on an optional or conditional basis. Filing Period: Effective Date: 18 February June April 2008

154 1746 B8.9/P 0 RECOMMENDED PRACTICE 1797b 1746 BAGGAGE SYSTEM INTERFACE (BSI) (amending) PSC(29)1797b 1746 Filing Period: Effective Date: 18 February June April 2008

155 1749 B8.10/P 0 RECOMMENDED PRACTICE 1749 CARRIAGE OF CARRY-ON BAGGAGE (amending) PSC(29)1749 RECOMMENDED that: (Secretary note: the verbiage below completely replaces the current text) 1749 B8.10/P SECTION 1 GENERAL For the purposes of this Recommended Practice the term carry-on baggage also means unchecked baggage, hand baggage and cabin baggage. 1.1 Members shall establish a control over carry-on baggage in order to facilitate passenger flow through security check points, to ensure the safety and comfort of passengers in flight, and facilitate on-time departures. Carry-on baggage shall be of a size, weight and shape to fit under a passenger seat or in an enclosed storage compartment. 1.2 For the guidance of passengers, Members shall publish a maximum carry-on baggage allowance applicable to their aircraft fleet. Such allowances may vary from carrier to carrier and by classes of service, therefore, when interline carriage is involved, the passenger should if possible be informed of the allowances of all the carriers in their itinerary to determine if their baggage is acceptable. Carry-on baggage may have a maximum length 56cm (22 in.), width 45 cm (18 in.) or depth 25 cm (10 in.). These dimensions include wheels, handles, side pockets, etc. Any item exceeding these dimensions may not be accepted as carry-on baggage. 1.3 In order to provide a means of demonstrating that a piece of carry-on baggage has been submitted to the carrier at the check-in or boarding point and detecting carry-on baggage which has not been so submitted, a carry-on baggage tag/label may be affixed to each piece of baggage accepted for carriage in the cabin. Alternatively, the baggage allowance carried by each passenger may be verified by such means as determined by the carrying Member(s). 1.4 After check-in, excessive carry-on baggage (including items purchased on departure) will be handled and labelled as checked baggage in accordance with Resolution 740.

156 1749 B8.10/P SECTION 2 INFORMING PASSENGERS ABOUT CARRY-ON BAGGAGE 2.1 It is recommended that Members establish a programme to inform passengers about carry-on baggage, in any of the following ways: timetables; tickets and/or printed itinerary; ticket envelopes or stuffers; ticket/check-in counter signs; inflight literature brochures announcements in Airport public areas, airline check-in/ticketing counters, frequent flyer clubs and departure lounges (see Section 3) Airline Website Any other electronic means any other appropriate means (See Section 4) 2.2 The information should be along the following lines: all baggage must be presented at time of check-in; baggage which is not presented at time of check-in may not be carried into the cabin items which can be carried free of charge; any restriction imposed by the Member on the number of pieces of carry-on baggage allowed carry-on baggage per passenger must not exceed dimensions for length, width and height reflected in section any restriction imposed by the Member on the weight of carry-on baggage allowed baggage that exceeds the above restrictions may not be carried into the cabin the following items should not be included in your checked baggage but should be carried with you at all times: medicine, jewellery, money, securities, keys, negotiable papers, documents and other valuables.

157 1749 B8.10/P SECTION 3 ANNOUNCEMENTS It is recommended that Members, when communicating carry-on baggage policies to the passengers, inform the passenger of the number and types of bags permitted as carry-on baggage, drawing attention to the sizes and weight. Shown below are examples of announcements that Members may use to communicate carry-on baggage information. Alternatively Members may use their own wording providing it contains the substance of the language shown below. 3.1 Airline Club Ladies and gentlemen, (airline or club name) welcomes all passengers travelling on flight xxx to xxx today. This flight is now boarding at gate xx. At this time we would like to remind all passengers that for your safety and comfort, limitations apply to carry-on baggage that can be taken on-board the aircraft. If you are uncertain of these limits, our staff at the service desk will be pleased to assist you. 3.2 General Club Ladies and gentlemen, (airline or club name) would like to remind all passengers that for your safety and comfort, limitations apply to carry-on baggage that can be taken on-board the aircraft. If you are uncertain of these limits, our staff at the service desk will be pleased to assist you. 3.3 Departure Gate Pre-boarding Ladies and gentlemen, in preparation for the boarding of flight xx, we would like to remind you that carry-on baggage is limited to (airline policy). Your carry-on piece must fit in the sizing unit located. Any carry-on that does not fit in the sizing unit will not be permitted on board. To ensure sufficient time to load any excess or oversize pieces, please see one of our agents now. Boarding Ladies and gentlemen, (airline name) welcomes all passengers travelling on flight xxx to xxx today. This flight will be boarding shortly at gate xx. At this time we would like to remind all passengers that for your safety and comfort, all carry-on baggage must be able to be stowed in an authorized stowage area on board the aircraft. If you are uncertain of the limits, please utilise the sizing unit placed near the boarding door, or contact any of our staff members who will be pleased to assist you. Option: Additional statement if more than 1 carry-on allowed: Please utilise the space under the seat in front of you before stowing a carry-on in the overhead bin. 3.4 Airport General For the safety and comfort of passengers, all airlines place limitations on carry-on baggage. Limitations vary by airline and it is recommended that you check with the airline you are travelling with today. 3.5 On-Board Ladies and gentlemen, please utilise the space under the seat in front of you for stowage of carry-on baggage before stowing any baggage in the overhead bin.

158 1749 B8.10/P SECTION 4 CARRY-ON BAGGAGE AWARENESS PROGRAMME A common issue that many carriers face relates to the size, number, and weight of passengers carry-on baggage. This is especially true as an itinerary may include changeof-gauge flights and thru-checked flights over various carriers that have differing baggage allowances. Passengers may not be aware of different policies for carry-on baggage, or may not always be made aware early enough before flight time, that is, before they come to the airport. Members may wish to identify the issues relating to the carriage of carry-on baggage with focus on different carrier rules, safety, passenger convenience and efficient airport operations, and develop plans to regularly communicate this information. Examples of how and what should be communicated are shown below. 4.1 Communications to the Customer What do we communicate? Comfort Health Punctuality Safety Carrier Related Information External Communication Channels Leaflets Ticket covers Frequent Flyer mailings Posters Time Tables Inflight Magazines Inflight entertainment Airline websites Announcements at airports Flight Information Display Systems (FIDS) Inflight announcements Carry-on nametags Signage at boarding gates Travel Agencies Airline Sales Department Airport Authorities Tour Operators Ground Handling Agencies Press travel pages in daily newspaper, travel magazines Other news media (TV and radio travel programs) Airline Hold Message Airport Information Channel

159 1749 B8.10/P Internal Communication Channels Through questions and answers (frequently asked questions) Briefings Staff publications Standard Training aids (staff bulletins, pocket guides, manuals, etc.) Sales meetings/conferences Message from the President In-house video show CRS DCS (Departure Control System) Intranet Staff travel reservation hold messages 4.2 COMMUNICATION WITH INDUSTRY RELATED PARTIES Airport Authorities What Overall information on hand baggage awareness including request for assistance and support Ease of passenger flow (e.g. security check points) Supports Minimum Connecting Time Safety (in general) Request to inform subcontractors (e.g. security companies) and authorities How Through Airport Operators Committee (AOC) Bilateral agreement airline/ airport authority Through Facilitation Through IATA Strategic Partnership Programme Luggage Manufacturers What Overall information on hand baggage awareness including request for support Guidelines for dimensions (overall dimensions = side pockets/wheels etc., included) How Through IATA Strategic Partnership Programme Regular ATA/IATA contacts Bilateral agreements Airline/manufacturers Ground Handling Service Providers What See Section 4.1 for details

160 1749 B8.10/P 1749 B8.10/P SECTION 5 VISUAL AIDS Examples of brochures, ticket stuffers, leaflets and posters/ counter cards that can be used as part of a cabin baggage awareness programme may be obtained from IATA. Ready to use coloured versions are available and these may also be customised as requested. SECTION 6 CABIN BAGGAGE SAFETY AND SECURITY GUIDELINES Carriers should inform their passengers of any safety and security restrictions pertaining to cabin baggage in effect. Filing Period: Effective Date: 18 February June April 2008

161 1771 R6.10/P 0 RECOMMENDED PRACTICE 1771 SELL AND REPORT OR FREE SALE AGREEMENTS (amending) PSC(29) R6.10/P 1 GENERAL RULES 1.6 When involuntary rerouted passengers are protected on other airlines flights, and the number of passengers to be protected on a specific flight/class/segment exceeds the quota sale permitted under an applicable Free Sale or Sell and Report agreement, send only one request message for all seats required, even though the bookings are for individuals or parties not exceeding the permitted sales quota. Free Sale or Sell and Report is not to be used for irregular operations protection, even though the bookings are for parties of 1, 2, 3 or 4. Space for irregular operations protection must be requested by telephone and/or AIRIMP message where local or toll-free telephone access is not available in accordance with AIRIMP irregular operations message procedures. Filing Period: Effective Date: 18 February June April 2008

162 1773 P10 0 RECOMMENDED PRACTICE 1773 SPECIAL MEAL DEFINITIONS AND CODES (amending) PSC(29)1773 Secretary note: the text below completely replaces the current text P10 RECOMMENDED that: In order to promote worldwide special meal definition standardisation, guidelines have been agreed as set out in Attachment A to this section. Whilst passengers special meal needs should be handled at the time of reservation, and reflected on the Passenger Information List (PIL), cabin crew should be familiar with the characteristics of the different meal types in order to be able to identify such meals and respond appropriately to passenger needs. Special meals should be identified by the caterer by attaching a special meal tag or label to the cart or container that the meals are in. The number and types of special meals are listed on the Aircraft Catering Order (ACO). Crew should verify that the appropriate numbers of meals have been delivered and the passenger s name(s) and seat number correspond to the information provided on the passenger information list. Due to variations in national and international food labelling standards, special meals cannot be generally guaranteed free of allergens. Similarly, the governing regulations applicable to flight catering are those in place in the country where meals are prepared and boarded. Therefore, local standards and controls on specific ingredients must be observed (e.g. transfats etc.). Note that foods and ingredients included in the allowed column are not intended to represent an exhaustive list, but are meant to clarify guidelines and provide examples. Every effort has been made to ensure the accuracy of the information set out in Attachment A to this section. The guidelines set out merely reflect the conclusions of IATA Members. Members should ensure that appropriate provisions are made; (1) in their Conditions of Carriage to mitigate any liability that may arise in respect of special meals delivered under these guidelines; (2) in their contracts with catering companies.

163 Page: 2 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE AVML VEGETARIAN HINDU MEAL Asian / Hindu vegetarians. Spicy vegetarian combinations Meat and meat products. High protein foods (milk, cheese, Products with added Omega 3 Asian Vegetarian with limited use of dairy products. Fish. yoghurt, lentils, beans, tofu). fatty acids normally use fish oil Hindu Vegetarian Fowl and products with lard or Foods rich in iron (dried peas, beans, and are therefore not suitable. gelatine. lentils, wholegrain products, dried Eggs. apricots) and calcium (broccoli, mustard greens, kale, tofu, navy beans, dried figs, almonds, ground or in paste sesame seeds, brazil nuts, pistachio nuts). BBML BABY MEAL Children < 2 years. Baby foods. Highly seasoned foods. Strained fruit. Commercially prepared foods Infant food Foods containing wheat, gluten, Strained vegetables. are usually boarded. Baby food fish, eggs and citrus fruit. Strained meats. Pork, veal and beef. Desserts. Solid food for children < 1 year. Meat with bone. BLML BLAND MEAL Passengers suffering from Omit foods / beverages causing Highly seasoned foods. Decaffeinated coffee and tea. Use moist heat, dry heat or stomach / intestinal problems. gastric discomfort. Black pepper. boiling cooking methods. Chili powder. Use SPML code if soft texture or "Gassy" vegetables, such as low fibre / residue is desired. cabbage and cauliflower. Caffeinated beverages. Fried foods. CHML CHILD MEAL 2 years < children < 5 years. Soft and easy to chew meals. Fish with bone. Carrot sticks. Several food items in individual Easily identified foods. Meat with bone. Cheese and crackers. wrappings will allow the child to Healthy choices. Nuts and seeds. Finger foods. save items to snack on later. Highly seasoned foods. Individual packaged fruit cups. Some airlines allow passengers to Hard candy. Fruit juices. order specific hot entrées Rich sauces. (e.g. hamburger) or cold entrées Whole grapes. for children over 5 years.

164 Page: 3 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE DBML DIABETIC MEAL Diabetic passengers. Increased complex carbohydrates. Fried foods. Lean meats. Availability of sugar substitutes Low sugar High fibre. Poultry (skinless). depends on local legislation. No added sugar Low fat. Fish (sea bass, tuna) and seafood. Sugar may be used by diabetics, No sugar added. Low fat dairy products. preferably in combination with 600 < calories < 800 per meal up Vegetables (potatoes, carrots, other foods, in order to improve to 2400 calories per 24-hour period. cauliflower, tomatoes, beans, glycaemic load. peppers). Wholegrain pasta, breads, rice and cereals. High fibre foods (fresh and dried fruit such as grapes, apples, pears, bananas and oranges). Packaged fruit if packed in water or in their own juices. Unsweetened fruit juices. Commercially prepared diabetic products. High intensity sweeteners (Acesulfame-K, Aspartame, Cyclamate, Neohesperidine, Acesulfam Aspartame salt, Saccharin, Sucralose, Stevia, Thaumatin, Neotame). FPML FRUIT PLATTER MEAL Passengers wishing to eat a meal Fruit. Additives. Prepared fresh fruit. Fruit selection depends on local with no additives / preservatives. Preservatives. Packaged unsweetened fruit. availability. Orange segments, apples, grapes, pineapples, melons, figs, strawberries. Dried fruit without sulfites.

165 Page: 4 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE GFML GLUTEN INTOLERANT MEAL Gluten intolerant passengers. Ensure gluten from any source Wheat, wheat flour, rye, oats Fruit, vegetables. Commercially prepared gluten-free Coeliac disease NOT SUITABLE FOR GLUTEN is not present in foods. and barley. Meat, fish, poultry. products may not be suitable if Non-tropical sprue ALLERGIC PASSENGERS. Do not provide foods where the Pasta, bread, bread crumbs Oil. wheat in ingredients. Dermatitis herpetiformis ingredients cannot be verified by and batter. Puffed rice, rice bubbles, corn Gluten intolerant passengers may Low wheat the manufacturer's label. Oat-based breakfast cereals. flakes (no malt in ingredients). also be lactose intolerant. Gluten-restricted Semolina. Potato flour, soy flour, rice flour. Low gliadin Soup, sauce, soya sauce and Corn flour (no wheat in ingredients). Low gluten gravy mixes that have been Sago, tapioca. made with flour. Rice, lentils, split peas. Cakes, muffins, pastries. Soy milk. Malt products, ovaltine. Dairy products. Startch derived from cereals containing gluten. Custard powder. Luncheon meats. Meat substitutes. Sausages. Confectionary with chocolate including cereals containing gluten. Nuts and nut products. HNML HINDU MEAL Passengers wishing to follow Foods prepared according to Beef. Lamb. Use AVML code if a vegetarian Hindu customs. Hindu customs and respecting Veal. Domestic fowl. Hindu meal is desired. Hindu dietary practices and Pork. Fish. beliefs. Raw and smoked fish. Milk products. Spicy foods and curry. KSML KOSHER MEAL Passengers wishing to follow Foods chosen, prepared and Foods prepared from approved Jewish customs. served in accordance with Jewish sources are usually boarded. dietary laws and customs.

166 Page: 5 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE LCML LOW CALORIE MEAL Passengers wishing to follow a Increased complex carbohydrates. Fried foods. Lean meats. Calorie-restricted calorie-restricted diet. High fibre. Added fats, oils and sugar. Low fat dairy products. Low fat. Gravies and sauces. Fresh fruit and vegetables. Calories < 400 per meal up to Rich desserts. High fibre wholegrain breads calories per 24-hour period. High fibre wholegrain cereals. Packaged fruit if packed in water or in their own juices. Unsweetened fruit juices. Commercially prepared low-calorie products. High intensity sweeteners (Acesulfame-K, Aspartame, Cyclamate, Neohesperidine, Acesulfam Aspartame salt, Saccharin, Sucralose, Stevia, Thaumatin, Neotame). LFML LOW FAT MEAL Passengers wishing to follow a Increased complex carbohydrates. Fried foods. Lean meats. Use poaching, steaming, broiling Low cholesterol fat-restricted diet. High fibre. Sauces high in fat (cheese or Poultry (skinless). or roasting cooking methods. Fat-restricted Fats high in unsaturated fatty acids. cream sauces). Fresh fruit and vegetables. Use vegetable or olive oil to Gall bladder diet Low dietary cholesterol. Egg yolks. High fibre wholegrain breads. prevent sticking. Low saturated fat Low in saturated fatty acids. Offal (kidneys, liver, tripe, heart, High fibre wholegrain cereals. Max. 3g of total fat per 100g of food, sweetbreads). Low fat dairy products. on average for the meal. Seafood (prawn, shrimp, squid, Mono or polyunsaturated margarine. Max. 1.5g of saturated fat per 100g crab, lobster). Mono or polyunsaturated oils of food, on average for the meal. Fish roe and caviar. (olive, peanut, canola, safflower, Added fats, oils. sunflower or soybean oil). Alcohol-refined sugars. Gravies with no cream/fat added. Processed meats. Processed cheeses.

167 Page: 6 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE LSML LOW SALT MEAL Passengers wishing to follow a No salt added. Salt substitutes, MSG, stocks, Salt-free margarine. No added salt sodium-restricted diet. Omit highly salted foods. bouillon cubes, commercial Low sodium breakfast cereals. Restricted sodium Max. of 120mg of sodium per soups and sauce mixes. Low sodium cheeses. 100g of food, on average for the Salted, smoked cured or Pepper, herbs, spices, vinegar, lemon meal. packaged foods. and lime juice, salt-free seasoning Items in brine (pickled meats / mixes. vegetables / sauerkraut). Garlic, onion, celery powders. Processed cheeses. Olives, anchovies. Bakery products using self-rising flour or baking soda. Most condiments (ketchup, mustard, BBQ sauce, soy sauce, Worcestershire sauce, seasoned salt). Gravies, sauces and dressings. Garlic, onion, celery salts. Breads. MOML MOSLEM MEAL Passengers wishing to follow Foods chosen, prepared and Pork and pig by-products. Halal produced meat / poultry from Use VLML if MOML not available. Moslem customs. served in accordance with Moslem Gelatine. approved sources. dietary laws and customs. Alcohol. Milk. Flavouring extracts with alcohol. Non-white fish meat from species without scales or fins.

168 Page: 7 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE NLML LOW LACTOSE MEAL Lactose intolerant passengers. Omit dairy products. Milk, yoghurt, cheese, ice Meat / poultry. Read all labels. Low dairy NOT SUITABLE FOR COW MILK cream, sherbet, puddings. Fresh vegetables. Low milk ALLERGIC PASSENGERS. Prepared mixes (muffins, Packaged / frozen fruit and vegetables Lactose intolerant biscuits, some breakfast not processed with lactose. cereals). Soy beverages as a substitute for milk. Creamed or breaded vegetables. Coffee creamers from non-dairy Breads prepared with dairy ingredients (no sodium casienate). products. Omelette, crepes, scrambled eggs with milk, cream, butter. Creamed or breaded meat / fish / eggs (no fillers containing dairy products). Commercial soups. Chocolate, toffee, butterscotch, caramels. Some instant coffees. Sugar substitutes. RVML VEGETARIAN RAW MEAL Raw vegetable vegetarians. Combination of raw fruit and Caffeinated beverages. Raw fruit and vegetables. Products with added Omega 3 vegetables. Highly processed foods. Pure fresh fruit / vegetable juices. fatty acids normally use fish oil Additives. and are therefore not suitable. Preservatives. Note that some vegetarians prefer foods grown and processed organically. SFML SEAFOOD MEAL Passenger preference. Fish and/or seafood prepared according to local specifications. SPML SPECIAL MEAL Passenger preference. Special meal request that the Details must be provided. Medical requirements. airline wishes to accommodate for Medical requirements must include which there is no specific meal specific details of ingredients code. to be included / avoided. Airlines should use this code with a very limited description of the special meal.

169 Page: 8 ATTACHMENT A IATA SPECIAL MEAL CODES MEAL MEAL NAME USE CHARACTERISTICS GUIDELINES NOTES CODE PROHIBITED ACCEPTABLE VGML VEGETARIAN VEGAN MEAL Vegans or pure vegetarians. Strict vegetarian foods. Products from animal sources. High protein foods (lentils, beans, Products with added Omega 3 Non-dairy, no-eggs Meat and meat products. tofu) fatty acids normally use fish oil Fish. Foods rich in iron (dried peas, beans, and are therefore not suitable. Fowl and products with lard or lentils, wholegrain products, dried Read all labels. gelatine. apricots) and calcium (broccoli, Note that some vegetarians Dairy products. mustard greens, kale, tofu, prefer foods grown and processed Eggs. navy beans, dried figs, almonds, organically. Honey. ground or in paste sesame seeds, brazil nuts, pistachio nuts). VJML VEGETARIAN JAIN MEAL Jain vegetarians. Vegetarian foods prepared Indian Meat, poultry, fish, seafood. Fruit and vegetables. Products with added Omega 3 style and according to Jain customs. Eggs. Spices. fatty acids normally use fish oil Root or bulbous vegetables. Tofu. and are therefore not suitable. Dairy products. Pulses and cereals. Rice. VLML VEGETARIAN LACTO-OVO MEAL Lacto-ovo vegetarians. Vegetarian foods. Meat and meat products. High protein foods (milk, cheese, Products with added Omega 3 Fish. yoghurt, eggs, lentils, beans, tofu). fatty acids normally use fish oil Fowl and products with lard or Foods rich in iron (dried peas, beans, and are therefore not suitable. gelatine. lentils, wholegrain products, dried Cheeses that may be produced apricots, egg yolks) and calcium with rennet include Parmesan and (mustard greens, kale, broccoli, tofu, Gruyere. navy beans, dried figs, almonds, ground or in paste sesame seeds, brazil nuts, pistachio nuts). Dairy products. Eggs. Vegetarian-type cheese without rennet. VOML VEGETARIAN ORIENTAL MEAL Oriental vegetarians. Vegetarian foods prepared Chinese Meat, poultry, fish, seafood. Fruit and vegetables. Products with added Omega 3 style. Eggs. Spices. fatty acids normally use fish oil Root or bulbous vegetables. and are therefore not suitable. Dairy products. Filing Period: Effective Date: 18 February June April 2008

170 1776 R6.5/P 0 RECOMMENDED PRACTICE 1776 SEAMLESS CONNECTIVITY (amending) PSC(29) R6.5/P. 4.2 Reduce Number in Party for all segments within a new booking Seamless Connectivity session The reduction of all new segments within a new booking session may be sent via the Seamless Connectivity Link to the booked airline/crs. When this reduction is performed and accepted, the participating airline/crs may return an acknowledgement message indicating that all inventory in this session has been adjusted accordingly. 4.3 Reduce Number in Party for selected segments within a new booking Seamless Connectivity session If a booking(s) has occurred via Seamless Connectivity and there is a reduction in number in party for one or multiple bookings within the same Seamless Connectivity booking session: a) A cancellation for the segment(s) booked in this session (i.e., affected/reduced segment(s) booked during this Seamless Connectivity session) must be sent to the booked airline/crs and; b) A new booking sell for the segment(s) with the new number in party must be sent to the booked airline/crs. This may be done in one or two messages to/from the booking airline/crs to/from the booked airline/crs.. Filing Period: Effective Date: 18 February June April 2008

171 1779 R6.3/P 0 RECOMMENDED PRACTICE 1779 JOURNEY DATA (amending) PSC(29) R6.3/P 4.2 Segment Content The air segments will include status code, based on the list of codes in Section 4.3. The segment data will include: carrier code flight number (one to four numerics or the word OPEN) flight number suffix reservation booking designator local departure date local arrival date city pair status code number in party local departure time local arrival time date variation married segment indicators block space indicator M M C M M M (if different from departure date) M M M M M C (the appropriate code will be used) C (See note below) C (See note below) (M = mandatory, must be sent; C = conditional, if present in segment, must be sent.) Filing Period: Effective Date: 18 February June April 2008

172 1790 P9 P9.1 0 RECOMMENDED PRACTICE 1790 ADDITIONAL SERVICES (new) PSC(29)1790 Recommended that: 1790 P9 Member Airlines and/or CRSs may use the following guidelines for the reservations, sales, and delivery of Additional Services; OBJECTIVES 1. General Additional Services standards and procedures allow airlines to better manage their range of products and services that they wish to provide to their passengers either free of charge or upon payment of a fee. 1.1 Scope This Recommended Practice recognises that a standardised process for Additional Services is required in all circumstances both for online and interline carriage. However, unless bilaterally agreed, the initial objective of this Recommended Practice will be on those services provided by a Member for travel on its own services and transacted using its own documents. The focus of this Recommended Practice shall therefore be limited to those transactions where the carrier providing the service is taking payment (when required) on one of its own electronic miscellaneous documents. 2. DEFINITIONS For the purpose of this Recommended Practice, the following definitions will apply; Additional Services means those services, other than passenger air transportation, provided to a passenger for which there may or may not be a charge. Electronic Miscellaneous Document (EMD) means an electronic record issued by a Member or its authorised agent, in accordance with applicable tariffs, for the collection of miscellaneous charges. Electronic Miscellaneous Document Associated EMD-A means an EMD issued for the collection of miscellaneous and excess baggage charges that are to be lifted with an ET flight coupon(s). The association between an EMD value coupon(s) and the corresponding ET flight coupon(s) requires that the coupon status of both remain synchronised Electronic Miscellaneous Document Stand Alone EMD-S means an EMD issued for residual value or the collection of miscellaneous charges that are not to be lifted with an ET flight coupon(s).

173 1790 P9 Optional Services means a data source provided by ATPCO for additional services an airline offers the customer for which the customer has a choice regarding whether to accept and/or purchase the service. A fee may or may not be charged for the service. The ATPCO Optional Services product can include data for required services such as unaccompanied minor services or oxygen onboard a flight. Concurrence means an agreement from one carrier to permit the assessment of another carrier s optional service in which the concurring carrier participates. Types of Service: Flight Related Services means those services filed in the ATPCO Optional Services database which are ticketed by means of an EMD-A, booked via a Special Services Request (SSR) and related to a specific flight segment (e.g. products that enhance the in-flight experience such as, but not limited to, seat selection, meals, blankets and drinks). Merchandising Related Service means the ability to purchase items from a catalogue such as, but not limited to, logo T-shirts and other items filed in the ATPCO Optional Services database. Refund/Reissue Override (Fare Related Service) means the pre-purchase of the ability to change an itinerary filed in the ATPCO Optional Services database. Ticket Related Services means those services filed in the ATPCO Optional Services database which are ticketed by means of an EMD-S cross-referenced to a ticket and booked via a Special Services Request (SSR) or Auxiliary Segment (SVC). This service may or may not be related to a flight segment (e.g. items associated to the purchase of a ticket such as, but not limited to, travel insurance, or flight related services such as, but not limited to, meals where the preferred ticketing method is not the EMD-A) P9 3. SCHEDULES FILING Members shall ensure that flight schedules shall reflect those flights that have Additional Services available by filing those services in accordance with SSIM standard rules.

174 1790 P9 4. RESERVATIONS PROCESS 4.1 Additional services shall be booked in accordance with the provisions of AIRIMP Chapter 3.19 Additional Services. All messages indicated in this section will use established teletype message formats. 4.2 The booking source shall send a request for the Additional Service to the Member. This request may be via a Special Service Request (SSR) for a flight related request, or via an auxiliary segment (SVC) for a non-flight related request On receipt of this request, the Member will respond to the booking source in one of three ways: Confirm the Additional service request and confirm that no EMD is required. No further action will be required by the booking source; Confirm the Additional service request with a request for the issuance of an EMD. The booking source shall issue an EMD and send confirmation of the EMD issuance to the Member Deny the Additional service request. No further action will be required by the booking source. 4.3 If the booking source is already aware that the Additional Service is offered by the Member and an EMD is required, they may send an SSR request for the service (e.g. UMNR) together with the Additional Service SSR identifying the specific service sub-code in the same teletype message. The Member will respond to the booking source in one of two ways: Confirm the Additional Service request with a request for the issuance of an EMD. The booking source shall issue an EMD and send confirmation of the EMD issuance to the Member Deny the Additional Service request. No further action will be required by the booking source P 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 calculation for additional services is required such fare calculation shall be in accordance with the provisions of Resolution 722 paragraph P9 6. AIRPORT PROCESS 6.1 Industry standard messages in accordance with the provisions of Recommended Practices 1708 (PNL/ADL), 1715 (PSM), 1716 (PIL), 1719 (PFS) and 1719b (PRL) shall be used to transmit data for Additional Services.

175 1790 P9 6.2 Members shall ensure that Departure Control Systems and third party ground handlers (where applicable) are able to handle such EMD-As for the purpose of check-in and ground handling in accordance with the provisions of 722f, 722h and 725f. 6.3 Members shall ensure that third party ground handlers are advised of any EMD-S required for the confirmation of payment for the provision of a service (e.g. Lounge access) P9 7. SERVICE DELIVERY 7.1 Carriers shall determine when the service has been consumed For those services that shall be considered as consumed upon check-in at the time the electronic ticket is lifted, an EMD-A shall be issued An EMD-S shall be issued for those services that are not to be considered as consumed at the same time the electronic ticket is lifted. Such EMD-S may be considered to be flight related, where the Member has determined that the preferred method of ticketing is an EMD-S (e.g. provision of on board meals, pre-reserved seating, in-flight entertainment etc), or non-flight related (e.g. the purchase of kennels, bike boxes, merchandise etc). 7.2 Members shall determine which EMD shall be issued. In the case of EMD-S, Members shall determine when the service paid for is to be considered as consumed and will be responsible for changing the coupon status to USED. 7.3 In order to deliver purchased in-flight services, cabin crew shall be provided with the information necessary to provide the service on board. Industry standard PIL may be used for this purpose in accordance with Recommended Practice 1716 or an airline s own proprietary list. Information shall include but not be limited to; the type of service to be provided, name of passenger and seat number P9 8. DISRUPTIONS AND IRREGULAR OPERATIONS 8.1 Where a Member experiences an irregular operation (e.g. a cancellation due to technical or weather reasons) and/or is unable to provide the service (for example due to an equipment change) Members may provide a refund in accordance with their conditions of carriage. 8.2 Members may not involuntary reroute Additional Services on to other Members unless bilaterally agreed. 8.3 In the case of schedule changes, Members shall determine whether the additional service can be provided for the new flight(s)/routing. 9. LACK OF SERVICE DELIVERY Where an EMD is in final status USED, thereby denoting that the service has been consumed, and the Member fails to deliver such service, the EMD may not be further used for refund. Members shall determine an appropriate response in accordance with their own customer relations policies.

176 1790 P9 10. INTERLINING Interlining is currently outside the scope of this Recommended Practice unless bilaterally agreed P REVENUE ACCOUNTING The Revenue Accounting Manual (RAM) provides detailed instructions for the interline billing and settlement of interlined passenger coupons and excess baggage. Interline billing of Additional Services is currently outside the scope of this Recommended Practice. Members shall not issue interline bills for settlement of EMDs issued for Additional Services unless bilaterally agreed. For the purposes of revenue accounting and interline billing, APTCO optional Services issued on an EMD do not constitute Sundry Charges as provided in Resolution 727a. Filing Period: Effective Date: 18 February June April 2008

177 1797 B3.1 0 RECOMMENDED PRACTICE 1797 COMMON USE TERMINAL EQUIPMENT (CUTE) PASSENGER PROCESSING SYSTEMS (CUPPS) (amending) PSC(29) B3.1 RECOMMENDED THAT: Following are the procedures and specifications for implementing a Common Use Terminal Equipment (CUTE) system. Members use the procedures and specifications for Common Use Passenger Processing Systems (CUPPS) as set forth in Attachments A, B and C. (Attachments A, B and C are published separately contact Manager Airport and Inflight Services, milesc@iata.org) B3.1 Secretary note: delete the rest of current RP Filing Period: Effective Date: 18 February June April 2008

178 1798 P8 0 RECOMMENDED PRACTICE 1798 CARRIAGE OF PASSENGERS WITH COMMUNICABLE DISEASES CONTACT OF AIR PASSENGERS EXPOSED TO A HEALTH HAZARD (amending) PSC(29) P8 (Secretary note: the verbiage below completely replaces the current text) Definition: a health hazard is defined in this context as an infectious or toxic agent that may constitute a public health risk. RECOMMENDED that, when it is determined by a Member that it unknowingly and/or unwittingly transported passengers under circumstances where they may have been exposed to a health hazard, the following guidelines be implemented. 1. When a Member is advised by a health authority that passengers may have been exposed to a health hazard, it shall co-operate with such health authority, with the understanding that it is not the Member s responsibility to trace and notify passengers who may have been exposed to the hazard. 2. The Member should notify its Medical Department or Medical Advisor. 3. If the health authority requests a list of passengers who may have been exposed to the health hazard, the health authority is to make a formal written request ( or fax is acceptable) to the airline Member and provide at least the following information: Full identification of the requesting health authority and response addresses If the health hazard is an infected passenger (index case) full name and permanent address of that passenger; names of other passengers who travelled in the index case s party, if known; the flight(s) and date(s) of travel, origin(s)/destination(s) of the index case the nature of the health hazard, including mode of transmission, incubation period, period of communicability, susceptibility, and control measures; distance from the index case within which other passengers could have been affected, e.g. number of rows in the aircraft, to the best knowledge of the health authorities; Note: It should be noted that seating proximity to the health hazard is relevant.

179 1798 P8 The health authority should include a statement that exonerates the Member of any liability, responsibility, or costs in notifying other passengers. 4. Where the health hazard is due to carriage of a passenger now known to have been suffering from a communicable disease, the Member should attempt to verify/confirm that it in fact carried the index case. 5. After the Member verifies that it did in fact transport the index case or health hazard, and if the health authority requests a list of other passengers who could have been affected, the Member should attempt to compile a list of such passengers, including the contact information which is available, and seat numbers. 6. The Member should deny disclosure to the health authority if disclosing passenger list/seat assignment data violates local, national or international laws and/or regulations (e.g. privacy/confidentiality laws, data protection laws, etc.). 7. The Member should make it clear to the health authority that the information provided is as accurate and timely as possible. 8. The Member s Medical Department or Medical Advisor could, depending on the circumstances and/or local regulations, contact the crew members who may have been exposed to the health hazard, and offer necessary diagnostic procedures and/or treatment, or handle as deemed appropriate by the Member concerned. Note 1: If the health hazard in question was a matter of international public health concern (epidemic or pandemic problem), more information would be available on the WHO web site at: and IATA would also be actively involved. Note 2: Members should inform passengers through their public relations, literature, inflight magazines, etc. that passengers who know they have a communicable disease should not travel by air, as they can expose other passengers and crew members to such communicable disease. Filing Period: Effective Date: 18 February June April 2008

180 1800 B8.1/P 0 RECOMMENDED PRACTICE 1800 AUTOMATED BAGGAGE HANDLING BASED ON THE IATA LICENSE PLATE CONCEPT (amending) PSC(29)1800 * I. INTRODUCTION/SCOPE Structure of This Document Section 1 Introduction/Scope Section 2 Purpose Section 3 Glossary of Terms in Automated Baggage Handling Environment Section 4 Generic Architecture Diagram for Baggage Systems Communication Business Overview of Baggage Processes Section 5 Process Descriptions Section 5.1 Intermodal Receipt Section 5.2 Sortation Section 5.3 Screening Section 5.4 Reconciliation Section 5.5 Tracking Section 5.6 Re-Routing Section 5.7 Re-Flighting Offloading/Reloading Section 5.8 Re-Tagging Tracing Section 5.9 Offloading/Reloading Intermodal Receipt/Intermodal Delivery Section Tracing Section Intermodal Receipt/Intermodal Delivery Section 6 Process Specific Baggage Codes Section 7 - References 2. PURPOSE It should serve as a guideline for following 'standard processes': Intermodal Receipt/Intermodal Delivery, Sortation, Screening, Reconciliation, Tracking, Re-Routing, Re-Flighting, Offloading/Re-Loading, and Tracing and Re-Tagging. Guidelines for 'specific processes' like 'Self Service Check-in' (CUSS, HOME) or 'RUSH Baggage' are under development and will be defined in this document at a later stage.

181 3. GLOSSARY OF 'TERMS IN AUTOMATED BAGGAGE HANDLING ENVIRONMENT' Industry Standard for Automated Baggage Handling LPC/LPN License Plate Concept/License Plate Number The industry standard for Automated Baggage Handling E enables the identification of a single bag by its License Plate Number (unique ten digit number, as defined in ATA/IATA RESO 30.35/740 and ATA/IATA RESO 30.69/769, commonly called 'tag number') and the access to data relevant to the processing of that bag. LPN License Plate Number BUM BCM-FCM Baggage Unload Message The Baggage Unload Message is a request to unload, or not to load specific baggage. Baggage Control Message Flight Close Message The Flight Close Message is sent by the Departing Carrier to advise an Automated Baggage System that a specific flight has been closed. The message can also be sent by an ABS to advise a DCS that it is has completed processing baggage for a specific flight. Generic Terms for Systems Enabling Automation in the Aviation Baggage Environment (in alphabetical order) ABS Automated Baggage System The generic term used to describe an automated system that uses the LPC in conjunction with the messages defined in the ATA/IATA RP30.45/1745. Example BRS, BSS, etc Specific Terms Involuntary Change NOC OOC. A decision to change flight made by the airline without influence of any passenger. New Operating Carrier The carrier(s) selected for onward carriage from the point where an involuntary reroute became necessary and any subsequent connecting carrier in the disrupted itinerary. The NOC can be online or interline. Original Operating Carrier Means the carrier on whose flight a passenger is originally scheduled to be carried and who is responsible for the condition which creates the need for an involuntary change in the passenger s journey.

182 PBHA. Problem Baggage Handling Area This is a specific location(s) at an airport where problem bags (e.g. bags without labels) are being handled (re-flighted, re-tagged), either by airline or non-airline staff. RUSH Bag Re-flighting Re-routed Bag UNAC A mishandled bag not travelling with the passenger on the original flight (RUSH). The process where the bag has missed its intended flight on the OOC and is typically referred to as mishandled baggage. The automated re-routing of baggage within an Automated Baggage System (ABS) after having been checked-in for a specific flight, as a result of a voluntary or involuntary change of the passenger and baggage itinerary. Unaccompanied Bag A bag which has been involuntarily re-routed, and not travelling on the same flight as the passenger (and is not a RUSH bag) because passenger did catch the original flight. Voluntary Change A decision made by the passenger to change the flight

183 4. GENERIC ARCHITECTURE DIAGRAM FOR BAGGAGE SYSTEMS COMMUNICATION BUSINESS OVERVIEW OF BAGGAGE PROCESSES To be completed. <<Business Event>> Revenue Or ID Passenger Request Acceptance Or Transfer Bag Data Transport Passenger And Baggage Baggage Screening Baggage Sortation Baggage Reconciliation Baggage Re-Route Baggage Offload/Reload Baggage Tracking <<Business Event>> Baggage has not been transported on booked Routing Baggage Re-Flighting Baggage Tracing <<Business Event>> Operating Crew request Baggage Registration Operating Crew Baggage Acceptance <<Business Event>> Found Untagged Baggage failed Re-Tagging Found Baggage Handling <<Business Event>> Untagged Baggage Found Baggage Re-Tagging Operating Crew Baggage Acceptance

184 5. PROCESS DESCRIPTIONS The following process descriptions relate to so-called standard processes. Specific processes such as automated handling of kiosk-checked-in (CUSS), and home-checked-in (HOME) or rush bags (RUSH) will be defined in this document at a later stage. 5.1 Intermodal Receipt See Section , Intermodal Receipt/Intermodal Delivery Relevant Messages 'Sortation ' From DCS View Specific Elements 'Sortation' Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table reflects the present status as mentioned in IATA RP1745/ATA RP30.45, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions Process Description Screening 1. Assign Security Screening Advice Instruction A security screening instruction can be assigned by the DCS to an item of baggage in the.x element, e.g..x/sel. This advice is derived from a combination of applicable regulations, the airports involved and a specific security status of passengers and/or bags. 2. Validate Confirmation of Screening Result The security screening method used is validated by the DCS in terms of meeting the required minimum level of screening. It reflects the technique and/or level of screening used. The security screening result and the security screening method are derived from an HBSS and communicated in a BPM in the.x element from an ABS to a DCS, e.g..x//clr//at, if available Relevant messages 'Screening' from DCS view Specific Elements 'Screening' Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table below reflects the present status as mentioned in IATA RP1745/ATA RP30.45, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions Goal 'Reconciliation' Avoid mishandled baggage in case of involuntary re-routings where passenger still catches the original flight This means that baggage of passengers who were re-booked involuntarily is authorized for transport on the new flight under the condition that the passenger boards the original flight.

185 5.4.4 Business Partners/Systems involved in 'Reconciliation' Departure Control System (DCS) Baggage Reconciliation System (BRS) Baggage Sortation System (BSS) Baggage System Interface (BSI) Check-in agents and/or handling agents/security staff performing passenger and baggage processing from acceptance to loading Validate boarding result. The DCS compares passengers checked-in versus passengers boarded to produce the final passenger list. At every boarding of a passenger, the DCS sets the Authority to Transport (ATT) to Y (yes). Insert after Notes on the Authority to Transport (ATT) Concept Concept Perspective ATT The concept of Baggage Transport Authorization is based on the process of Automated Passenger and Baggage Reconciliation. It extends the capabilities of this process in relating the status of a piece of baggage to the process and/or the specific characteristic of the passenger acceptance process (i.e. re-booking in case of flight irregularities or handling of baggage associated to a member of the operating crew). See also the related activity and status diagrams provided in Attachment A, Baggage Transport Authorization, Vision. Concept Features ATT - Provide the baggage handling system with a unique baggage attribute, which indicates, that the progress of passenger acceptance for a specific passenger has reached a specific final state and that the plausibility that the passenger boards the aircraft is nearly 100%. - Provide the airline with the possibility to handle the baggage and transport without the passenger in a safe and cost effective manner - Provide that airline with the possibility to handle transport of baggage associated to an operating crew member according to the legal requirements and in a cost-effective manner Authority to Load (ATL) Authority to Transport (ATT) Loading Advice N N Do not load Y N Load with caution N* Y Load in aircraft Y Y Load in aircraft N Not present or not supported Do not load Y Not present or not supported Load *Note: This may occur in case of involuntary re-routing situations when bags are authorized for transport as unaccompanied baggage without passenger.

186 This may occur when the communication of the system was lost and a human authorized decision has been made. The loading of these bags should be communicated by the BRS back to the DCS using BPMs including the.s element. Notes for Involuntary Re-Routing Situations: 1) Passenger accepts re-routing alternative If a passenger had been affected by an involuntary re-routing and he and his baggage had been rechecked to a new flight, the passenger and his baggage are cancelled on the original flight and accepted on the alternative flight. 2) Passenger does not accept re-routing alternative and catches the original flight When a passenger is re-accepted on the original flight but his baggage has been re-routed to the alternative flight, the DCS marks the BCR on the alternative flight as Unaccompanied (UNAC) and sets the Authority to Load to Yes. When the passenger has boarded the original flight the DCS sets the Authority to Transport to Yes for the baggage on the new flight Relevant messages 'Reconciliation' from DCS view Specific Elements 'Reconciliation' Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table below reflects the present status as mentioned in IATA RP1745/ATA RP30.45, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions Business Process Description Note from IATA/ATA BWG/PSG: New message BTR will be defined for IATA RP1745/ATA RP30.45 (IATA/ATA BWG/PSG work program2006/2007). As a precondition for baggage tracking a BTS must exist at the airport from which tracking data are requested. In principle there are two options to perform automated baggage tracking: Option 1: The BTS stores the tracking data received from the tracking points and sends the data to the DCS on request. 1. Request Baggage Processing Information Triggered by a Check-in agent a DCS requests tracking data from the ABS by using the BTR Baggage Tracking Request message. 2. Receive Baggage Processing Information The DCS receives tracking data from a BTS in a BPM message and stores it. 3. Determine and display physical location of baggage Depending on the existence of a station specific topology the DCS can determine the physical location where the bag has last been tracked and display it to the Check-in agent on request. 4. Determine and display remaining processing time

187 Depending on the existence of a station specific topology the DCS can determine the remaining physical processing time of a bag from the last seen at location to the expected handling or loading location. On request of the Check-in agent the DCS can display the remaining processing time. Option 2: A BTS sends continuously BPMs for each tracking point to the DCS. The DCS stores the tracking data and displays them on request. 1. Receive Baggage Processing Information continuously The DCS receives tracking data from a BTS in a BPM message and stores it. 2. Determine and display physical location of baggage Depending on the existence of a station specific topology the DCS can determine the physical location where the bag has last been tracked and display it to the Check-in agent on request. 3. Determine and display remaining processing time Depending on the existence of a station specific topology the DCS can determine the remaining physical processing time of a bag from the last seen at location to the expected handling or loading location. On request of the Check-in agent the DCS can display the remaining processing time. 1.Send Baggage Tracking data Tracking data is sent as a BPM. This can be either based on a subscription or on a request for a particular baggage item. 2.Receive Baggage Tracking Information Tracking data is received, stored and used for further processing, such as determining physical location or remaining processing time, reconciliation, measuring compliance to Service Level Agreements, determining flight readiness for departing flights etc Relevant Messages from DCS View Specific Elements Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table reflects the present status as mentioned in IATA RP1745/ATA RP30.45, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions 'Definition 'Re-Routing' General This is the process of changing the intended baggage routing resulting from a change in the passenger s itinerary, which may be voluntary or involuntary from the passenger s perspective. Where the bag has missed its intended flight and is carried on another flight without the passenger, the process is referred to as Re-Flighting, and is covered separately in this document. The implementation of the new itinerary may take place online, interline or when involving means of transport other than air (e.g. ground transport). It is critical the original baggage tag number should be retained for the complete journey as stated in IATA/ATA Resolution 740/ This procedure implies the availability of an ABS and the compliance with local airline and airport regulations. Automated Baggage Re-Routing is the automated re-routing of baggage within an Automated Baggage Systems (ABS) after having checked-in for a specific flight, as a result of a voluntary or involuntary change of the passenger and baggage itinerary. The new itinerary may include means of transport other than air (e.g. ground transport). Automated Baggage Re-Routing may be implemented in different ways and will require the electronic exchange of data between the Departure Control Systems (DCS) and the ABS.

188 Involuntary Re-Routing This process is initiated by the Original Operating Carrier (OOC) in accordance with IATA/ATA Resolution 735d/ This may occur as a result of flight delays or other irregular operations (IROP, except when caused by any passenger) causing the airline to change the passenger s itinerary. The following situations may occur: 1) Accompanied Baggage Re-Rerouting Process Passenger accepts new flight alternative, passenger and baggage travel together on the same flight. 2) Unaccompanied Baggage Re-Rerouting Process (UNAC) Passenger does not accept new flight alternative but baggage has been re-routed, passenger and baggage travel on different flights. i.e. the passenger decides to catch the original flight: if the passenger is re-accepted and has boarded, then the bag is authorized to travel unaccompanied (UNAC). The UNAC process does not apply if the new operating carrier is operated by a different airline (interline situation). Voluntary Re-Routing This process is initiated by the passenger in accordance with IATA Resolution Goal 'Re-Routing' To take a large proportion of bags which may go out of process, and bring them back into the regular baggage process by: Transport baggage on the same flight with the passenger Ensures that security and service requirements are observed. Additionally the re-screening of baggage and physical updating of the baggage tag should be avoided where applicable. If the passenger does not accept the new alternative flight and boards the original flight then the Unaccompanied Baggage Re-routing process (UNAC) goals are: Improve passenger satisfaction by delivering their bag to the final destination as early as possible Reduce the number of bags that will require unnecessary security processing should local regulatory authorities agree Improve baggage handling efficiency by reducing the volume of mishandled baggage and consequently costs. Transport baggage on the same flight with passenger. This means that baggage of passengers who were re-booked voluntarily or involuntarily is re-routed to the 'new flight' in an automated way. This includes the involvement of other automated baggage processes like 'Reconciliation', 'Sortation' and 'Screening' to ensure that security and service requirements are observed. Avoid physical updating of the baggage tag where applicable Generally, if bags are handled by an automated ABS this ABS has to route the bag to the chute of the new flight. If the ABS provides a facility for updating baggage tags it will route the bags to this facility depending on the necessity of updating the routing on the baggage tag according to the DCS instruction. If according to the new baggage routing only one segment is left to fly, the bag(s) can be re-directed to the new flight without stopping it for manual updating of the baggage tag. If more segments are left to fly, the DCS and/or the ABS have to ensure that baggage is directed to a manual handling area for updating the baggage tag. This procedure implies the availability of an ABS and the compliance with local airline and airport regulations.

189 Avoid re-screening where applicable Re-screening shall be avoided when baggage has been screened previously for the original flight with a 'CLR' (Clear) result. This shall only be applicable when the integrity of baggage is guaranteed during the physical baggage transfer from the old flight to the new flight. This procedure implies the availability of an ABS and the compliance with local airline and airport regulations Business Partners/Systems Involved in 'Re-Routing' - Airline Departure Control System (DCS) - BSS (Baggage Sortation System), conditionally BTS (Baggage Tracking System), BRS (Baggage Reconciliation System), HBSS (Hold Baggage Screening System) - Baggage System Interface (BSI) - Check-in agents and/or handling agents/security staff performing passenger and baggage acceptance.

190 5.6.5 Process Diagrams Re-Routing ABS Screening Airline DCS Passenger and Baggage Handling Passenger shows up at new flight ABS Sortation {Re-Screening NOT advised} (Re-Screening advised) Validate IROP Cancel Passenger/ Baggage on Original Flight BSM-DEL (.E/RRTE.E/IROP) (Cancellation requested) (Registration requested) Indicate Baggage as Re-Route CLR Validate BCR for Re-Screening (Re-screening NOT necessary) Indicate Baggage as Re- Route-(re)-Screening (Re-Screening necessary) BSM-CHG (.E/RRTE.E/IROP X=NON) BSM-CHG (.E/RRTE.E/IROP X=SEL) Register Passeger/ Baggage on New Flight Evaluate Baggage Routing ( Tag update necessary) Advice Re-Tagging Evaluate Baggage Security Screening Instruction And Results BSM (.E/RRTE.E/IROP) ( Tag update not necessary) Avoid Re-Tagging BSM (.E/RRTE.E/IROP.E/STCK) BPM (.E/RRTE.E/STCK) Cancel Baggage on Original Flight Set Baggage On Hold for Re-routing (Baggage Tag Update not necessary) Register Baggage on New Flight Validate Baggage for Manual Baggage Tag Update (Baggage Tag update necessary) Indicate Baggage for Manual Baggage Tag Update Update Baggage Tag Manually Re-Screen Baggage (Re-screening necessary) (Re-screening NOT necessary) BPM (.E/RRTE) Baggage Reruted Advice Re-Screening Avoid Re-Screening Direct Baggage to Flight (Conditional Transaction) Figure: Automated Baggage ReRouting -I Activity Diagram Automated Baggage Re-Routing

191 Airline DCS BRS Passenger And Baggage Handling - Passenger shows up at original flight after involuntary re -route BSM-CHG for New Flight (.E/UNAC. E/IROP.E/RRTE.S/Y) ATL=Y Re-accept Passenger on Original Flight Update Baggage Identification and Handling on New Flight Set Baggage Identification And Handling Code to UNAC on New Flight Authorise Baggage for Loading on New Flight PAX has boarded BSM-CHG for New Flight (.E/UNAC. E/IROP.E/RRTE.S/ / / / / / / Y) ATT=Y Authorise Baggage for Transport on New Flight Update Baggage Transport Authorisation on New Flight Activity Diagram Unaccompanied Baggage Re-routing Process

192 5.6.6 Process Description 'Involuntary Re-Routing' This process is initiated by the Departure Control System (DCS) and is performed within Automated Baggage Systems (ABS) involving the exchange of data between the Departure Control Systems (DCS) and the ABS. This process is applicable if the DCS is the same for both flights or if automated exchange of data is possible between the two DCSs involved. Accompanied Baggage Re-routing Process 1. Validate that there is an irregular operations situation (IROP) and an involuntary re-routing has been performed. 2. Cancel the BCR from original flight This occurs when baggage is cancelled from a flight for which it had been checked-in for. This information is conveyed to other systems by means of BSM DEL, conditionally by means of BTM/DEL in case of interline re-routing, with.e/rrte and.e/irop. 3. Register baggage for new flight This occurs when passenger and/or baggage are checked-in for a new flight. The DCS will indicate the rerouting request of a bag by sending a new BSM, conditionally BTM, for the original tag number with the new routing information (.F, if available.i and optionally.o) and a.e element using the bag message codes RRTE and IROP. 4. Evaluate if tag update is required. When baggage of passengers who were re-booked voluntarily or involuntarily is re-routed, the baggage has to be cancelled for the old flight and registered for the new flight. The information about the re-routing has to be communicated by the DCS to the involved baggage handling partners. Additionally the new baggage routing has to be validated against the old baggage routing in order to determine, whether the baggage tag has to be updated prior to loading on the new flight. The DCS will indicate the rerouting request of a bag by sending a new BSM for the original tag number with the new routing information (.F and optionally.o) and an.e element using the bag message code RRTE. If the routing of the tag has to be updated, the DCS will send an additional.e element using the bag message code STCK indicating that a Rerouting Sticker according to IATA RESO 740, Attachment J has to be used. If available, the updating of the routing section of the baggage tag may be performed at a dedicated baggage handling facility. If such a facility is not available it shall be performed manually by airline or handling agents before loading. 1. Cancel BCR from old flight This occurs when baggage is cancelled from a flight for which it had been checked-in for. This information is conveyed to other systems by means of BSM DEL, informing the business partner that the BCR has been deleted from the respective flight. 2. Register BCR for new flight. This occurs when passenger and/or baggage are checked-in for a new flight. This will trigger a new BSM including sortation criteria, loading priority, loading authority and conditionally a screening instruction.

193 3. Validate Baggage Routing The DCS has to validate whether the new baggage routing is a flight segment or not. If the new routing is flight segment, the DCS has to compare the old and the new baggage routing in order to determine whether the baggage has to be routed to a physical handling location for updating the baggage tag. Physical updating of the baggage tag is not necessary if the new baggage routing contained contains only one outstanding flight segment with one outbound flight and destination airport code the same as the original. E.g. Example: old Old routing: LH 400 JFK new New routing: LH 404 JFK or LH 402 EWR Physical updating of the baggage tag has to be performed if the new baggage routing contained onward flight segment(s) and the destination airport code of the outbound and/or the onward flight segment(s) has changed and/or the flight segment of the onward flight has changed. E.g. If the new baggage routing contains onward flight segment(s) and the destination airport code of the outbound and/or the onward flight segment(s) has changed and/or the flight segment of the onward flight has changed, physical updating of the baggage tag has to be performed. Example: Old routing: New routing: Old routing: New routing: or New routing: LH 400 JFK LH 972 MUC onto LH 410 JFK LH 972 MUC onto LH 410 JFK LH418 IAD onto UA7356 JFK LH972 MUC onto AA123 JFK If the routing of the tag has to be updated, the DCS of the OOC will send an additional.e element using the bag message code STCK indicating that a Rerouting Sticker according to IATA/ATA Resolution 740/30.35, Attachment J has to be used. If available, the updating of the routing section of the baggage tag may be performed at a dedicated baggage handling facility. If such a facility is not available it shall be performed manually be airline or handling agents before loading. Note: When baggage of passengers who were re-booked voluntarily or involuntarily is re-routed to an intermodal business partner, the baggage has to be cancelled for the old flight. In this case, a BTM can be sent to the ABS and/or intermodal business partner for the new travel segment, including the baggage handling location and transport medium. When baggage of passengers is re-routed to an interline partner or different airline, the updating of the tag is always initiated by the OOC. It can be performed by the OOC or a contracted handling agent, or asked to be done by the NOC or by baggage handling agents at a re-sticking facility.. When baggage of passengers who were re-booked voluntarily or involuntarily is re-routed to an intermodal business partner, the baggage has to be cancelled for the old flight. In this case, a BTM can be sent to the ABS and/or Intermodal business partner for the new travel segment, including the baggage handling location and transport medium and optionally the codes RRTE and IROP in the.e element.

194 4. Validate Baggage Security Screening Advice and Result 5. Evaluate Baggage Security Screening requirement The DCS has to validate the Baggage Security Screening Advice Instruction and the Baggage Security Screening Result for the original flight for each specific bag. If there was a security screening instruction that has already been confirmed with a screening result 'CLR', then repeated screening of this bag for the new flight may be avoided. The DCS will indicate this in the new BSM, or conditionally in the BTM, with a security screening instruction 'NON' meaning that no further screening action is required. However, this screening instruction may be overruled by local security screening regulations if the integrity of baggage cannot be guaranteed. If there was a security screening instruction that has not yet been confirmed with a screening result, then the outbound carrier s DCS will re-validate the screening instruction requirements for the new flight and communicate this in the BSM with the applicable instruction (e.g., SEL or default). If the security screening requirements for the new flight overrule the ones for the old flight, a new security screening instruction for the new flight has to be produced with the applicable instruction (e.g., SEL or default). Note: This procedure is subject to bilateral agreements between the airline, the ABS operator and/or the party responsible for loading. The latter two have has to guarantee the integrity of baggage during its physical transfer from the old flight to the new flight. 6. Receive the BPM with confirmation of re-route process and re-tagging, if requested. Unaccompanied Baggage Re-routing Process (UNAC) In exceptional situation, if the passenger does not accept the new alternative flight and instead decides to catch the original flight, then the following additional steps occur: 7. Re-accept passenger on original flight When the passenger is re-accepted on the original flight, the DCS generates a BSM-CHG for the new flight with the Authority to Load (ATL) set to Yes and the UNAC code in addition to the RRTE and IROP in the.e element. 8. Board passenger on original flight When the passenger has boarded the original flight, the DCS generates a BSM CHG for the new flight with the Authority to Transport (ATT) set to Yes and the UNAC code in addition to the RRTE and IROP in the.e element Process Description Voluntary Re-Routing This process is initiated by the passenger and is performed within Automated Baggage Systems (ABS) involving the exchange of data between the Departure Control Systems (DCS) and the ABS. This process is applicable if the DCS is the same for both flights or if automated exchange of data is possible between the two DCSs involved. 1. Validate that no involuntary re-routing has been performed and the change of the itinerary is initiated by the passenger. 2. Perform process steps 2 to 5 as stated in the Involuntary Re-Routing process description but without including the IROP code.

195 Relevant Messages 'Re-Routing' from DCS View i = incoming, o = outgoing BTM (o) BSM DEL (o) BSM (o) - contains the Baggage Identification and Handling code RRTE in the.e element, conditionally the code IROP in the.e element - conditionally the security screening instruction in the.x element - contains the Baggage Identification and Handling code RRTE, conditionally the code IROP in the.e element - contains the Baggage Identification and Handling code RRTE, conditionally the code IROP and optionally STCK in the.e element - contains Security Screening Instruction BSM CHG (o) - contains the Baggage Loading Authorization in the.s element - contains the Baggage Identification and Handling code RRTE, conditionally IROP, conditionally UNAC in the.e element - conditionally indicates that the baggage tag has to be updated by using a Rerouting Sticker according to IATA RESO Resolution 740/ATA RESO Resolution and by using the 'Baggage Identification and Handling' Code.E/STCK. BPM (i) - optionally the 'Baggage Security Screening StatusResult' by using the code.x/ - conditionally it confirms the updating of the baggage tag if done by using the Baggage Identification and Handling code.e/stck - conditionally it confirms the RRTE process by using the code.e/rrte Specific Elements Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table reflects the present status as mentioned in IATA RP1745/ATA RP30.45, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions Offloading/Reloading Automated Baggage Offloading and Re-Loading 5.7 Re-Flighting Automated Baggage Re-Flighting Definition Re-Flighting General This is the process where the bag has missed its intended flight on the Original Operating Carrier (OOC) and is carried on the flight of the New Operating Carrier (NOC) as RUSH baggage without the passenger. This is typically referred to as Mishandled Baggage, as stated in Resolution 780. When there is a change in the passenger s itinerary the Re-Routing process as described in this document is applied. The new itinerary may take place online or interline and may include means of transport other than air (e.g. ground transport). It is critical the original baggage tag number should be retained for the complete journey as stated in Resolution 740.

196 5.7.2 Goal Re-Flighting The goal is to deliver baggage to the passenger by the fastest possible means, using the services of any member, to the airport nearest to the passenger s address and to ensure that security requirements for Mishandled Baggage are observed Relevant References Re-Flighting IATA Resolutions Manual: Resolution 743, Section 2.1, Resolution 743a, Sections 3 and 3.1, Resolution 780, Article 1.20, 4, Resolution 735d, Article 3.2, Resolution 740, 3.2 and Attachment L, RP Business Partners/Systems Involved in Re-Flighting - Airline Departure Control System (DCS) - BSS (Baggage Sortation System), BTS (Baggage Tracking System), BRS (Baggage Reconciliation System), HBSS (Hold Baggage Screening System) - Baggage System Interface (BSI) - World Tracer Tracing System - Check-in agents and/or handling agents/security staff performing passenger and baggage acceptance

197 5,7,5 Process Diagrams Re-Flighting Re-Flighting - Same Airline Original Airline DCS Mishandled Baggage World Tracer BPM (.E/MIS) ABS Sortation/ Reconciliation Identify Mishandled Bag Identify Mishandled Bag Assign attribute MIS BSM-DEL (.E/MIS) (Registration requested) (Cancellation requested) Determine re-flight choice FWD message Receive FWD Message Assign Baggage on New Flight Evaluate Baggage Routing and perform retagging if required Evaluate Baggage Security Screening Instruction And Results BSM (.E/RUSH X=SEL or Default.S ATL & ATT = Y) BSM (.E/RUSH X=NON.S ATL & ATT = Y) BSM (.E/RUSH.E/STCK X=NON.S ATL & ATT = Y) BSM (.E/RUSH.E/STCK X=SEL or Default.S ATL & ATT = Y) Validate Baggage for Manual Baggage Tag Update (Baggage Tag Update not necessary) (Baggage Tag update necessary) Indicate Baggage for Manual Baggage Tag Update Cancel Baggage on Original Flight Update Baggage Tag Manually Advice Re-Screening & Advise Re-tag Avoid Re-Screening & Advise Re-tag Avoid Re-Screening & Avoid Re-tag Advice Re-Screening & Avoid Re-tag Direct Baggage to Flight & Screening as instructed Set Baggage On Hold for Re-flighting BPM (.E/RUSH.E/STCK) (Conditional Transaction) Activity Diagram Baggage Re-Flighting

198 Re-Flighting - Interline Original Airline DCS Mishandled Baggage World Tracer BPM (.E/MIS) ABS Sortation/ Reconciliation Identify Mishandled Bag Assign attribute MIS Determine re-flight choice BSM-DEL (.E/MIS) FWD message Receive FWD Message Identify Mishandled Bag (Registration requested) (Cancellation requested) Evaluate Baggage Routing and perform retagging options if required Assign Baggage on New Flight Validate Baggage for Manual Baggage Tag Update (Baggage Tag Update not necessary) Cancel Baggage on Original Flight BTM (.E/RUSH eg.x/clr) Re-flighted Airline DCS Mishandled Baggage FWD message (Baggage Tag update necessary) (Re-screening necessary) Advice Re-Screening Evaluate Baggage Security Screening Instruction And Results (Re-screening NOT necessary) Avoid Re-Screening BSM-CHG (.E/RUSH X=SEL or Default.S ATL & ATT = Y) BSM-CHG (.E/RUSH X=NON or Default.S ATL & ATT = Y) Indicate Baggage for Manual Baggage Tag Update Update Baggage Tag Manually Direct Baggage to Flight & Screening as instructed Set Baggage On Hold for Re-flighting BPM (.E/RUSH.E/STCK) (Conditional Transaction) Activity Diagram Baggage Re-Flighting

199 5.7.6 Process Description Re-Flighting This process is performed within Automated Baggage System (ABS) involving the exchange of data between the Departure Control Systems (DCS) and the ABS. This process is applicable if the DCS is the same for both flights or if automated exchange of data is possible between the two DCSs involved. 1. The process can be initiated in different ways: The DCS of the OOC detects mishandled baggage The DCS of the OOC receives information about mishandled baggage from the ABS. The DCS of the NOC receives information about mishandled baggage from WorldTracer in a FWD message. The DCS of the NOC receives information about mishandled baggage from the DCS of the OOC in a BTM with.e/rush. 2. The DCS of the OOC will validate that the baggage is mishandled baggage. 3. The DCS of the OOC will assign attribute MIS and send BSM DEL with.e/mis to ABS. 4. The DCS of the OOC will determine Re-Flight choice and send the FWD message to World Tracer. 5. Evaluate if tag update is required. The DCS of the OOC has to validate whether the new baggage routing is a single segment or not; Physical updating of the baggage tag is not necessary if the new baggage routing contains only one segment with one flight and destination airport code is the same as the original. E.g. old routing: LH 400 JFK, new routing LH 404 JFK or LH 402 EWR Physical updating of the baggage tag has to be performed if the new baggage routing contains onward flight segment(s) and the destination airport code of the outbound and/or the onward flight segment(s) has changed and/or the flight segment of the onward flight has changed. E.g.: Old routing: New routing: Old routing: New routing: Or New routing: LH 400 JFK LH 972 MUC onto LH 410 JFK LH 972 MUC onto LH 410 JFK LH 418 IAD onto UA7356 JFK LH 972 MUC onto AA 123 JFK

200 If the routing of the tag has to be updated, this can be performed by the DCS of the Delivering Airline or the ABS. If updating the tag is not necessary (because only one segment is left to fly or the tag has been updated already) or the DCS updates the tag, it will send the BSM with the code.e/rush and set the Authority to Load and the Authority to Transport to YES (.S ATL and ATT = Y). If ABS has to update the tag, the DCS will send the BSM with the code.e/rush and the additional code.e/stck indicating that a Re-Flighting Sticker according to IATA Resolution 740, Attachment L has to be used. If available, the updating of the routing section of the baggage tag may be performed at a dedicated baggage handling facility. If such a facility is not available it shall be performed manually by the OOC or contracted handling agents before loading. Note: When baggage of passengers is Re-Flighted to an interline partner or different airline, the updating of the tag is always initiated by the OOC. It can be performed by the OOC or a contracted handling agent. 6. Evaluate Baggage Security Screening requirement The DCS of the OOC has to validate the Baggage Security Screening Result for the original flight. If there was a local security screening instruction that has already been confirmed with a screening result CLR, then repeated screening of this bag for the new flight may be avoided. The DCS of the OOC will indicate this in the new BSM or conditionally in the BTM with a security screening instruction NON meaning that no further screening action is required. However, this screening instruction may be overruled by local security screening regulations if the integrity of baggage cannot be guaranteed. If there was a security screening instruction that has not yet been confirmed with a screening result, then the NOC s DCS will re-validate the screening requirements for the new flight and communicate this in the BSM with the applicable instruction (e.g. SEL or default). If the security screening requirements for the new flight overrule the ones for the old flight, a new security screening instruction for the new flight has to be produced by the NOC with the applicable instruction (SEL or default). Notes: A local emergency situation may lead to an overruling of the airline security screening instruction. This procedure is subject to bilateral agreements between the airline and the ABS operator and/or the party responsible for loading. The latter has to guarantee the integrity of the baggage during its physical transfer from the old flight to the new flight.

201 7. Receive the BPM with confirmation of re-flighting process and re-tagging, if requested Relevant Messages Re-Flighting from DCS i=incoming, o=outgoing BTM (o) BSM DEL (o) BSM (o) BPM (i) BCM-BAM(o) BCM-BAM(i) - 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 RUSH - conditionally the Security Screening Instructions in the.x element - 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.e/mis - provides information for processing of baggage by Automated Baggage Systems - contains the new flight Baggage Onward Flight Segment and the Baggage Class of Travel - conditionally contains the Baggage Onward Flight Segment; and/or the Baggage Inbound Flight Segment and/or the Baggage Loading Priority and/or Baggage Type - contains the Baggage Loading Authorization in the.s element - contains the Baggage Identification and Handling code RUSH in the.e element - conditionally contains re-tagging instruction with the code STCK in the.e element - conditionally contains the Security Screening Instruction - by bilateral agreement, a BPM confirms the physical loading and/or Baggage Loading Authorization for a specific Baggage Outbound Flight Segment ; - conditionally it confirms the Baggage Sortation Criteria; and/or the Baggage Loading Priority - optionally the Baggage Security Screening Result by using the code.x/ - conditionally it informs the mishandled bag by using the code.e/mis - conditionally it confirms the updating of the baggage tag if done by using the Baggage Identification and Handling code.e/stck - conditionally it confirms the RUSH process by using the code.e/rush - optionally, requests the acknowledgement of message receipt - confirms the receipt of a baggage service message receipt when message acknowledgement was requested by DCS

202 5.7.8 Specific Elements Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table below reflects the present status as mentioned in RP1745, 24 th Edition, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions. M Mandatory C Conditional O Optional.A - (M) BCM-BAM.C - (O) BTM, BSM, BPM.D - (O) BSM.E - (O) BTM, BSM, BPM.F - (M) BTM, BCM; (C) BSM, BPM.H - (O) BPM.I - (M) BTM; (C) BSM; (O) BPM.J - (O) BPM.N - (M) BTM, BSM; (C) BPM.O - (C) BTM, BSM; (O) BPM.P - (M) BTM, (O) BSM, BPM.R - (O) BTM, BSM, BPM, BCM-BAM.S - (C) BSM; (O) BPM.U - (O) BPM.V - (M) all messages.w - (O) BTM, BSM.X - (O) BTM, BSM, BPM 5.8 Tracing 5.8 Re-Tagging Automated Baggage Re-Tagging Definition Re-Tagging Automated Baggage Re-Tagging means the ability to re-print the original baggage tag of one piece of baggage and attach the new label on that baggage according to a local bilateral agreement and Airlines permission for baggage that has lost its tag or where the tag has been damaged during its transport. It is critical the original baggage tag number should be retained for the complete journey as stated in Resolution Goal Re-Tagging The goal of the Re-Tagging process is to avoid mishandled baggage. This is achieved by identifying baggage which may go out of process, and bringing it back into the regular baggage process by enabling re-tagging when the baggage can be uniquely identified. Automated Baggage Re-Tagging can be performed by airlines themselves or any ABS that were authorized by the Airlines according to a local bilateral agreement Relevant References Re-Tagging Resolutions Manual: IATA Resolution 780/ATA Resolution 5.65, IATA Resolution 740/ATA Resolution 30.35, and , IATA Resolution , IATA RP1745/ATA RP 30.45, IATA RP1774.

203 5.8.4 Business Partners/Systems Involved in Re-Tagging - Departure Control System (DCS) - BSS (Baggage Sortation System), BRS (Baggage Reconciliation System), BTS (Baggage Tracking System) - Baggage System Interface (BSI) - Check-in agents and/or handling agents/security staff performing passenger and baggage processing from acceptance to loading Process Diagram Re-Tagging Baggage handling staff ABS DCS Identify baggage attributes Not enough Attributes identified Attributes identified ABS internal interface Search baggage data with matching attributes and show result Evaluate local re-tagging agreement with airline delivering BRQ with.e/cpy.h/location Evaluate and conditionally update baggage attributes Evaluate re-tagging options Transmit baggage attributes Validate and optionally select baggage data displayed No re-tagging permission Re-tagging Permission without airline request Re-tagging permission with airline request Send Retag request to DCS with found attributes Only DCS re-tagging permission Re-tagging by DCS at a requested location BSM with.e/cpyd No re-tagging permission Re-tagging permission Baggage data do NOT matched with baggage attributes Baggage data matched with baggage attributes Re-tag with local equipment BPM with.e/cpy BSM with.e/cpya Send permission for re-tagging on a requested location No re-tagging, deliver baggage to a specific area (in-line or out of line), send a BPM with.j/location BSM with.e/cpyn Send not authorization for re-tagging Activity Diagram Automated Baggage Re-Tagging

204 5.8.6 Process Description Re-Tagging Typically the re-tagging process is initiated by the baggage handling agent and involves human interaction with Automated Baggage System (ABS) and conditionally the exchange of data between ABS and Departure Control Systems (DCS). Optionally the re-tagging process can be initiated by an airline agent and performed without any involvement of an ABS. This scenario is not part of this document. 1. Identify baggage attribute(s) Baggage handling staff identifies available baggage attribute(s) like Airline, Flight Number, Passenger Name, Tag Number, License Plate, Frequent Flyer Number, File Key (PNR), etc. and transmits them to the ABS. If not enough attributes can be found, re-tagging for this baggage is impossible and the baggage has to be delivered to a Problem Baggage Handling Area (PBHA), either in-line (i.e. transported inside automated baggage system) or out of line (i.e. transported by people to the PBHA). In this case the ABS sends the baggage processing information in a BPM indicating the sent to location in the.j element. Example for a problem bag seen at the T1 Main Hall Sorter (T1MHS) sent to T1 Problem Baggage Handling Area (T1PBHA):.J/G/43S/120D32/23NOV/154512/L/T1MHS/T1PBHA 2. Search baggage data with matching attributes and show result(s) ABS tries to match attributes with its own baggage data received from baggage messages and displays the data to the baggage handling staff, no matter if one or several sets of data were found. 3. Validate and optionally select baggage data displayed Baggage handling staff validates the matching data received from the ABS against the untagged bag and transmits the selected data to the ABS. If no matching data is found, re-tagging for this baggage is impossible and the baggage has to be delivered to a specific area either in-line (i.e. transported inside automated baggage system) or out of line (i.e. transported by people to a specific location). In this case the ABS sends the baggage processing information in a BPM indicating the sent to location in the.j element. 4. Evaluate local re-tagging agreement with Airline Delivering Different situations may occur: a) ABS has permission to perform re-tagging without Airline Delivering permission ABS initiates re-tagging based on ABS data, prints a baggage tag copy according to Resolution 740 and confirms it to the DCS by sending a BPM.E/CPY b) ABS has permission to perform re-tagging only with Airline Delivering permission 1. ABS sends a re-tagging request to the DCS using a BRQ Baggage Request (described in RP1745) indicating the retagging request in the.e element (.E/CPY) and including the found attributes and specifying the details of the re-tagging location Problem Baggage Handling Area in the.h element (.H/PBHA). 2. The DCS evaluates and conditionally updates the baggage attributes received from the ABS. 3. The DCS evaluates the re-tagging options: a. The DCS allows the ABS to re-tag and endorses the re-tagging request by the ABS by sending a BSM and including the re-tagging authorization in the.e element (.E/CPYA). ABS initiates re-tagging based on data received by DCS, prints a baggage tag copy according to Resolution 740 and confirms it to the DCS by sending a BPM (.E/CPY).

205 b. The DCS refuses the re-tagging request by sending a BSM and including the retagging refusal in the.e element (.E/CPYN). c. The DCS does not allow a third party to re-tag its bags. The re-tagging process will be performed by the DCS at a requested location and the DCS acknowledges its intention to perform the re-tagging by sending a BSM and including the confirmation with.e/cpyd. c) ABS has no permission to perform re-tagging for this Airline Delivering The Re-tagging for this baggage is impossible and the baggage has to be delivered to a specific area either in-line (i.e. transported inside automated baggage system) or out of line (i.e. transported by people to specific location). In this case the ABS sends the baggage processing information in a BPM indicating the sent to location in the.j element Relevant Messages Re-Tagging from DCS i=incoming, o=outgoing BSM (o) BPM (i) BRQ (i) - by bilateral agreement, a BSM will accept the BRQ received for re-tagging by authorizing the re-tagging request with.e/cpya or will refuse the BRQ received for retagging by not authorizing the re-tagging request with.e/cpyn - conditionally a BSM will inform the ABS that re-tagging will be performed by the DCS with.e/cpyd - by bilateral agreement, a BPM will confirm the physical re-tagging with.e/cpy - by bilateral agreement, a BRQ will be sent from an ABS to the DCS to ask for permission for re-tagging by using.e/cpy Specific Elements Re-Tagging Note from IATA/ATA BWG/PSG: The condition of the elements displayed in the table below reflects the present status as mentioned in RP1745, 24 th Edition, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions. M Mandatory C Conditional O Optional.A - (O) BRQ.C - (O) BSM, BPM; (O) BRQ.E - (O) BSM, BPM; (C) BRQ.F - (C) BSM, BPM; (C) BRQ.H - (O) BSM, BPM; (M) BRQ.I - (C) BSM; (O) BPM; (C) BRQ.J - (O) BPM.L - (O) BSM; (C) BPM; (C) BRQ.N - (M) BSM; (C) BPM; (C) BRQ.O - (C) BSM; (O) BPM; (C) BRQ.P - (O) BSM, BPM; (C) BRQ.R - (O) BSM, BPM.S - (C) BSM; (O) BPM.T - (C) BPM; (C) BRQ.V - (M) all messages.y - (O) BSM, BPM; (C) BRQ

206 5.9 Intermodal Receipt/Intermodal Delivery 5.9 Offloading/Reloading Automated Baggage Offloading and Re-Loading Definition Offloading/Reloading Goal Offloading/Reloading Offload baggage from a specific flight Route baggage to a specific handling location Re-Load baggage on a specific flight Validate 'Security Screening Result and Method' to avoid re-screening Relevant References Offloading/Reloading Offloading IATA Resolutions Manual: IATA RP1745/ATA RP 30.45, Attachment F; G; RP1780e, RP1797b Reloading IATA Resolutions Manual: IATA RP1745/ATA RP 30.45, Attachment A Business Partners/Systems Involved in Offloading/Reloading Process Diagram Offloading/Reloading Process Description Offloading/Reloading Initiate Baggage Offload and Assign Handling Location Advice Receive and Validate Loading Data Re-Load baggage on a specific flight Validate 'Security Screening Result and Method' to avoid re-screening Receive and Validate Loading Result Relevant Messages Offloading/Reloading from DCS View Specific Elements Offloading/Reloading

207 Tracing - Automated Baggage Tracing Business Process Definition Business Process Goal References Business Partners/Systems Involved Business Process Description Process Diagram Tracing Relevant Messages from DCS View Specific Elements Intermodal Receipt / Intermodal Delivery Business Process Definition Business Process Goal References IATA Resolutions Manual: Resolution 709/ATA 30.46, Resolution 743/ATA , Resolution 746, Resolution 769/ATA 30.69, Resolution 780/ATA 5.65, Attachment A, Resolution 780e, RP1740b, RP1740c/ATA RP 30.40, IATA RP1745/ATA RP 30.45, Attachment (to be updated in the next edition) RP1750, RP1780e, RP1797b Business Partners/Systems Involved Business Process Description.

208 Business Process Overview Intermodal Diagram Process Intermodal Receipt Airport/ABS Process Intermodal Delivery Summary Description Bag Acceptance by STP Bag Delivered by STP to ABS Bag Received by ABS Sorting, Tracking, Reconciling etc. Airline passes intermodal bags to STP Bags Received by STP Bags Tracked internally by STP Bags Delivered by STP to customer STPSurface Transport Provider (o) STP Pax Checks In Bags collected from customer (Proof of Acceptance) Bag handled and tracked by STP Message BTM (DCS & ABS) (o) BPM (DCS & ABS) (m) BPM (DCS & ABS) (c)bpm (DCS & STP) These process are described elsewhere in RP1800 Bag passed from airline/abs to STP, for transportation to customer. Bags received from airline by STP Bags tracked internally with STP logistics process, as bags are transported Bags handed over to customer by STP (Proof of Delivery) BTM (STP & ABS) BPM (DCS & ABS) (o)bpm (DCS & ABS) (m)bpm (DCS) Airline / ABS (o) DCS Pax Checked In DCS create bag record Update bag record Process BPM Update bag record Bag handled and tracked by ABS ABS sends BPM to STP. DCS sends BTMs to STP and ABS as required. STP sends BPMs to DCS and ABS as required, as bags accepted by STP from airline. STP sends BPMs to DCS and ABS as required. Bags are moving through Delivery process. Bags delivered to customer Relevant Messages from DCS View Specific Elements Note from IATA/ATA BWG/PSG: This will require following changes in IATA RP1745/ATA RP 30.45: 1) Condition of elements in messages:.d to be included in BTM and BPM and to become optional or conditional. 2) Change of BTM definition to allow an Intermodal partner to perform the same role as an OAL carrier. The condition of the elements displayed in the table below reflects the present status as mentioned in IATA RP 1745/ATA RP 30.45, June It will be reviewed by the IATA/ATA BWG/PSG after completion of all process descriptions.

209 6. Process Specific Baggage Codes according to IATA RP1745/ATA RP Note from IATA/ATA BWG/PSG: These codes are a summary of already existing codes in IATA/RP1745/ATA RP Additionally, some new codes have been included that were already agreed upon within the IATA/ATA BWG. Also some new codes are listed that are still on the work program of the IATA/ATA BWG/PSG. Work in progress Subject to revision of ATA RP30.45/IATA RP1745, Attachment A Note: X S= significant to process; XO = nice to have in process Secretariat note amend the table in section 6 to be landscape. Code Description Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging ID Intermodal Remark A AT AV AVIH Baggage Tag Status: Active Security Method: Advanced Technologies Carriage Medium: Airline Van Live animal in kennel to be loaded in belly.s XO XS XS.X XS.D XO XS XS XS.E XO XS XO XO XO XO XO B BIKE Passenger Status: Boarded Bicycle to be loaded in belly.s XS.E XO XS XO XO XO XO XO XO XO XO BULK Bulky baggage.e XO XS XO XO XO XO XO XO XO XO BUST C Bag Check-In Location Identifier: Bus Station Security Screening Result Reason combined with result indicator REJ: Combination of dark.d XS XO XO XO XO XO XO XO.X XO XS XO XO

210 Code Description alarm and explosives Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging ID Intermodal Remark C CBBG CKIN CLM CLR CO Passenger Status: Checked-In Bag transported as cabin baggage on extra seat Bag Check-In Location Identifier: Airport check-in desk Bags with assigned handling location Baggage Status in Security Screening: Cleared Carriage Medium: Courier CONV Bag Check-In Location Identifier: Convention Centre COUR Diplomatic/ Commercial Courier CPY Copy tag request or copy tag confirmation CPYA Copy tag request authorized CPYD Copy tag has been done CPYN Copy tag request not authorized CR Carriage Medium: Car Rental Van.S XS XS XO.E XO XS XO XS.D XS XS XO XO.H XO XO XO XS XS XO XO XO.X XO XO XS XO XO XO XO XO.D XO XO XO XO XO XO.D XS XO XO XO XS.E XO XS XO XO.E S.E S.E S.E O.D XS XO XO

211 Code Description Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging ID Intermodal Remark CREW Baggage Identification And Handling Code CRPK Bag Check-In Location Identifier: Car Park.E XO XS XO XO XO XO XO XO XO XO.D XO XO XO XO XO XO XS CRRT CS Bag Check-In Location Identifier: Car Rental Carriage Medium: Cruise Ship Van.D XO XO XO XO XO XO XO.D XO XO XO XO XO XO CURB Bag Check-In Location Identifier: Curb side D DAA DGR Security Screening Result Reason combined with result indicator REJ: Dark/shield alarm blockage of visual image Bag to be delivered at aircraft Dangerous goods in checked baggage.d XO XS XO XO.X XO XS XO XO.E XO XS XO XO XS XO XO XO XO XO XS XS XO XO XO XO XO XO DIPL Diplomatic courier.e XS XO DUPE Duplicate tag number for the same flight E Security Screening Result Reason combined with result indicator REJ: Explosives.E XS.X XO XS XO XO

212 Code EBD ETD Description Security Method: Explosive Bulk Detection Security Method: Explosive Trace Detection Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening.X XS.X XS RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging FIR Flight Irregularity.R X X X X X X X X FRAG Fragile Baggage.E XO XS XO XO XS XS XS XO ID Intermodal Remark FTL G Passenger Status Frequent Traveller Processing Information: Ground Tracking.R XO.J XO XO XO XO XS XO XO XO XO XO GATE Bags with assigned handling location GRND Bag transported on a ground connection.h XO XO XO XS XS XO XO.E,.G, H,.D XO XS XO XO XS XS XS XO GRP Baggage of a group.e XO XS XO XS XO XO XO XO XO XO H Processing Information: Hand Scanner.J XO XO XO XO XS XO XO XO XO XO HAJJ Pilgrim to Mecca.E XS XO XO HAND Security Method: Hand Search HOME Bag Check-In Location Identifier: Home HOTC Bag Check-In Location Identifier: Hotel.X XS.D XO XO XO XO XO XO XS.D XS XO XO XS

213 Code I HTLV HV HVY Description In case of Flight Irregularity and HTL Voucher issued Carriage Medium: Hotel Van Heavy Baggage Indicator Baggage Tag Status: Inactive IROP Irregular Operations Indicator in case of Involuntary Changes JUMP Passenger on JuMP Seat K L L L L M Pieces and Weight Indicator: Kilos Processing Information: Time Local Baggage Loading Result: Loaded Baggage Source Indicator: Local Pieces and Weight Indicator: Pounds Type of Baggage in Container/Location: Mixed MKTG Marketing Flight Indicator Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging.E XO XO.D XO XS XO XO.E.S XO XS XS.E XO XO XO XO XO XO XO XO.E XS.W XO XO.J XO XO XO XO XO XO XO XO XO XO X X X X X X.V XS XO XO XO XO XO XO XO XO.W XO XO.U XS XO XO XO XO XO.R XO XS XO XO XO MIS Mishandled Baggage.E O S O O O O O ID Intermodal Remark

214 Code Description Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging ID Intermodal Remark N Authority to Transport: N = no.s XO XS XO XO XO N Authority to Load:.S XO XS XO XO XO N Passenger Status: Not Checked-In.S XO XO XS XO N Passenger Profile Status: no.s XS XO XO XO N Security Screening Result Reason combined with result indicator UCL: No decision.x XO XS XO XO N Baggage Loading Result: Loaded X X X X X NAL Baggage Status Code: Loaded, but not authorized for loading NBRD Passenger Status: Not Boarded NON Baggage Status in Security Screening: No action.b XS XO XO XO.S X.X XS OFF OFFC ONA Baggage Loading Result: Offloaded Bag Check-In Location Identifier: Office Building Baggage Status Code: On hand; not loaded, authorised to.b XS XS XS XS XS.D XS XO XO XO XS.B XS XO XO

215 Code OND P PACK PBHA PORT PTY load Description Baggage Status Code: On hand; not loaded; not authorised for loading Pieces and Weight Indicator: Pieces only Inadequate Packaging of Baggage Problem Baggage Handling Area Bag Check-In Location Identifier: Sea Port Passengers checked in together without group booking Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing.B XS XO XO.W XO XO.E XS RR Re- Routing Re- Flighting.H O O O Re- Tagging.D XS XO XO XO XO XS.R X X X X X X X X X X PRIO Priority Baggage.E XS XO XO XO XO R R R RA REJ Processing: Information: Reconciliation Baggage Loading Result: Reloaded Baggage Source Indicator: Remote Carriage Medium: Rail Baggage Security Screening Status: Rejected.J XS XO XO XO XO.V XS XS XO XO XO X X X X X.D XS XS XO XS XS.X XO XO XS XO RELD Re-load indicator.e XS ID Intermodal Remark

216 Code RRTE Description Passenger Itinerary Changed /-Baggage Tag Not Updated RUSH Unaccompanied (expedited) Baggage RUSH WT S S S Unaccompanied (expedited) Baggage originating from a WorldTracer Message Processing Information: Sortation Passenger Status: Stand-by Type of Baggage in Container/Location: Short Connection SECU Airport Handling Location Classified as secured SCON Passenger with short connection Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging.E XO XO XO XO XS XO.E XO XO XS XO XO XO X S XO.R X X X X X X X X.J XS XO XO XO.S XS.U XS XO XO.H XS XS.E XS XO XO ID Intermodal Remark SELF SEL Bag Check-In Location Identifier: Self Service Check In Baggage Status in Security Screening: Selectee.D XS XS XO.X XO XS XO XO SPEQ Sports equipment:.e XO XS XO XO XO XO XO XO XO XO GLIDER,GOLF, SKI,SURF,DIVI NG, VAULTING POLES

217 Code Description Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging ID Intermodal Remark STCK T Instruction to update the routing information on the baggage tag Security Screening Result Reason combined with result indicator UCL: Time out.e XS O O.X XO XS XO XO T T Type of Baggage in Container/Location: Transfer Baggage Source Indicator: Transfer TOUR Baggage for a Specified Tour.U XS XO XO XO XO XS XO.V XS XO XO XO XO XO XO XO.E XO XS XO XS XO XO XO XO XO TRST Bag Check-In Location Identifier: Train Station.D XO XO XO XO XO XO XO XO USEC Airport Handling Location Classified as unsecured UCL Baggage Security Screening Status: Unclear.H XS XS.X XO XS XO XO UNAC UNS VFDB Unaccompanied Baggage in Irregular Operation when Involuntary Re-routing Baggage Status Code: Unseen Baggage of passenger who.e XO XO XO.B XO XO XS.E XO XO XS XO XO XO

218 Code Description Bag Message Element IR Intermodal Receipt SO Sortation SC Security Screening RE Security Transport Authorization TR Tracking OL Off- Loading RL Re- Loading TC Tracing RR Re- Routing Re- Flighting Re- Tagging ID Intermodal Remark Volunteered For Denied Boarding VOL Baggage rejected from transport due to insufficient volume in the aircraft.e WCHR.E XO XS XO XO XO XO XO XO XO XO WEAP Weapons, Firearms or Ammunition booked and carried as Checked Baggage.E XS XO XO XO XO XO XO XO WGHT Baggage rejected from transport due to insufficient available weight on the aircraft.e X X Type of Baggage in Container/Location: Terminating Baggage Source Indicator: Terminating.U XO XO XO XO.V XS XO XO XO XO XO XO XO XBAG Excess baggage.e XRAY Security Method: X- Ray Y Authority to Transport: Y = yes.x XS.S XO XS XO XO XO Y Authority to Load: yes.s XO XS XO XO XO Y Passenger Profile Status: yes.s XS XO XO XO Z Processing Information: Time UTC.J XO XO XO XO XO XO XO XO XO XO

219

220 7. References IATA Passenger Services Conference and ATA Passenger Council Resolutions IATA ATA Title Baggage Transfer Message (BTM) Baggage Security Control Form of Interline Baggage Tag Baggage Tag Issuer Codes (BTIC) Standardization of Traffic Handling Message Texts. 1740c Radio Frequency (RF) Specifications for Interline Baggage. Filing Period: Effective Date: 18 February June April 2008

221 MINUTES 27 th Joint ATA/IATA Passenger Services Conference (JPSC) 29 th IATA Passenger Services Conference (PSC) Toronto 9-10 October 2007

222

223 M E M O R A N D U M PSC/MINS/023 TO: COPY: FROM: All Members, Passenger Services Conference - Accredited Representatives All Members, Joint ATA/IATA Passenger Services Conference - Accredited Representatives (ATA members via Ms P. Edwards) IATA Strategic Partners Director, Passenger DATE: 8 February 2008 SUBJECT: MINUTES 27th Joint ATA/IATA Passenger Services Conference (JPSC) 29th IATA Passenger Services Conference (PSC) Toronto, 9-10 October 2007 Please find attached the Minutes of the 27th Joint ATA/IATA Passenger Services Conference (JPSC) and the 29th IATA Passenger Services Conference (PSC) as approved by the Chairman. The Expedited Resolutions and RPs were circulated under cover of Memorandum PSC/RESO/138 dated 30 October The Book of Finally Adopted Resolutions & RPs PART 1 (Resolution 724) PSC/RESO/140 was circulated on 31 January The Book of Finally Adopted Resolutions & RPs PART 2 referred to in these Minutes are issued under cover of Memorandum PSC/RESO/141 dated 8 February Michael Feldman International Air Transport Association Route de l Aeroport 33 PO Box 416 CH Geneva 15 Airport Switzerland Tel: Fax feldmanm@iata.org

224

225 M I N U T E S 27th Joint ATA/IATA Passenger Services Conference (JPSC) 29th IATA Passenger Services Conference (PSC) Toronto, 9-10 October 2007 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/26 and PSC/28 1 A4 Status of PSC Resolutions and RPs 1 A5 Effectiveness Date of Amendments to Industry Standards 2 A6 Any Other Business 2 A7 Date and Place of Next Meeting 2

226 II POLICY Agenda Item Subject Page Number P1 Report Status of Industry Coding Systems 2 P1.1 Assignment of Airline Designator for 2 Telecommunications (Resolution 762) P1.2 Assignment of Accounting Code for BSP Link 3 (Resolution 767) P1.3 Assignment Criteria for Codes (Resolution 762 and 767) 3 P1.4 Location Identifier Working Group (LIWG) 3 P2 Report - BSP Form Codes and Document Supply Chain 3 P2.1 Assignment of Additional Form Codes for Airlines 3 (RP 1720a) P2.2 Form Code 24 and P2.3 Transition to Full OPET Environment from 1 June and Requirement for Check Digit P2.4 Deletion of Electronic Excess Baggage Ticket From 5 Form Code 260 P3 Ratification of Special Fees and Charges Codes 5 (Resolution 728) P3.1 Tax Code Exhaustion 5 P4 Report Simplifying the Business (StB) 5 P4.1 Report Baggage Improvement Programme (BIP) 5 P4.2 Report The Future of Other Documents 6 P4.3 Automated MPD on Blank Paper 7 P4.4 ET only for MITA (Resolution 780) 7 P4.5 Removal of MITA Application Forms (Resolution 780) and Deletion of Reference to All Fares Product 7 P5 Ticket Notices 7 P5.1 Ticket Notices Consequential Changes 8

227 III Agenda Item Subject Page Number P6 Co-ordination with the Commission of European 8 Communities (CEC) on PSC Matters P6.1 Airport Lists for Passengers with Reduced Mobility 8 (PRM) P6.2 Acceptance and Carriage of Incapacitated Passengers 8 (Resolution 700) P7 Anti-Trust Immunities Australia 9 P8 Contact of Air Passengers Exposed to a Health Hazard 9 (RP 1798) P9 Optional Service Task Force (OSTF) 9 P9.1 Additional Services RP P9.2 OSTF Mandate 10 P10 Meal Definitions and Codes (RP 1773) 10 P11 Reduced Rate Transportation (Resolution 788) 11

228 IV AIRPORT SERVICES Agenda Item Subject Page Number B1 Report of Airport Services Committee (ASC) 11 B2 Report of the IATA Ground Handling Council 11 (IGHC) B3 Report of Common Use Self Service Management Group 11 (CUSSMG) B3.1 Report of RP 1797 Review Sub-Group 11 B4 Report of BCBP Working Group 12 B5 Report of the DCS Working Group 12 B6/P Package Items (DCS) 12 B6.1/P Editorial Changes to RP 1719c 12 B6.2/P Editorial Changes to RP B6.3/P Editorial Changes to RP 1707b 12 B6.4/P DCS Provisions for Additional Services 13 B6.5/P Necessity of Group Identifier for Block Seats Indicator ZZ, 13 RP 1707b B6.6/P Use of Passenger Level, RP B6.7/P Format for ADL Elements, RP B6.8/P Party/Group/Tour Field Name, RPs d 13 B6.9/P Editorial Changes to RP B6.10/P Discrepancy in Automated PNR Address Element with No 14 Company Designator, RP 1707b B6.11/P Changes to RP 1707b to Match AIRIMP 14 B6.12/P PSM and PTM: Show Operating Carrier and Flight 14 Number for a Code Share Flight, RP 1715 and RP 1718 B7 Report of the Baggage Working Group (BWG) 14

229 V Agenda Item Subject Page Number B8/P Package Items (BWG) 14 B8.1/P Editorial Changes Plus Additions to RP B8.2/P Editorial Changes to RP B8.3/P New Message to RP 1745 BRQ 15 B8.4/P Amend RP 1745, Attachment A Section B8.5/P Amend RP B8.6/P Amend Resolution B8.7/P RP 1743a, Tracing Procedure for Missing Checked 16 Baggage B8.8/P RP 1743e, Baggage Irregularity Report 16 B8.9/P RP 1797b Baggage System Interface (BSI) 16 B8.10/P RP 1749 Carriage of Carry-On Baggage 16 B8.11/P RP 1740c Radio Frequency Identification (RFID) 16 Specifications for Interline Baggage B8.12/P RP 1740c New IATA Objective ID for Internal Airport 16 Status B8.13/P RP 1740c Replace the Date in Object Identifier 12.6 in 17 Julian Format B9 Adoption of New Bilateral Code ETLP for Identifying Ticketless Travel Product in RP 1707/1708 and Proposal of New RP 1719d 17 B10 Responsibility for Delivery of Interline Checked Baggage 17 B11 Multi-Passenger Country in SSR FOID in DCS Messages 17

230 VI TICKETING Agenda Item T1 Subject Report of Ticketing Committee Selection of Committee Membership for PFPC Page Number 18 T2/P Ticketing Package 18 T2.1/P EMD Amendment to Disassociation 18 T2.2/P EMD Amendments to Matrix in Resolution 722g and 19 ATA Resolution T2.3/P EMD Glossary Definition for Validating Carrier 19 T2.4/P EMD Amendments to Data Elements Glossary and 19 Matrices T2.5/P Display from the Operating Carrier to the Ground 19 Handler T2.6/P Change of Status Out-of Sync Condition 20 T2.7/P Net Fare Component Information 20 T2.8/P EMD Series of Amendments 20 T2.9/P Pricing Indicator for Carrier Fees 20 T2.10/P Matrix Updates for Category T2.11/P Commission Type Text Correction 21 T2.12/P Fare Calculation Entries for Ticket Discounts 21 T2.13/P Tax Audit Data Elements 21 T2.14/P Proration Data Elements 21 T2.15/P Fare Audit Data Elements 22 T2.16/P Amendment to Fare Component Ticket Designator 22 T2.17/P Unique Fare Basis Code for IATA Fares Established by 22 Flex Fare Process T2.18/P Rescission of Neutral Paper Tickets Resolutions and Related Amendments 22

231 VII Agenda Item Subject Page Number T2.19/P Flight Prefix/Suffix 23 T2.20/P Rescission of IATA Resolution 738 Agents Refund 23 Voucher and Reserve of Form Code 303 T2.21/P EMD Deduction Method 23 T2.22/P EMD Group Deposit 23 T2.23/P EMD Matrix Amendments 24 T2.24/P EMD Itinerary Receipt and Ticket Notices for EMD 24 T2.25/P Passenger Names on Tickets with Single Letters 24 T2.26/P Deletion of Eurocard (EC) from Resolution 728/ATA T2.27/P Addition of Presto to Resolution T2.28/P Transition to Full Tax Breakout 25 T2.29/P Clarification for 99 Occurrences of Tax, Fee, Charge 25 Data T2.30/P Add ET Only to Resolution 722a 25 T2.31/P Updates to Resolution 722h/ATA Matrix 26 T3 Block Space Codeshare Amendment to Resolution f and Glossary T4 Data Elements for Fare Related Optional Services 26 T5 Bar Coded Boarding Pass (BCBP) Deadline Mandate 26 T6 Responsibility for a Delay Causing Involuntary Change of 27 a Passenger s Journey T7 Amendments to Recommended Practice T8 Cabin Baggage Dimensions Disconnect between RP 1749 and Tariff Composite Resolutions 300/301 Precedence of Composite Resolutions vs. PSC Recommended Practice 27

232 VIII Agenda Item Subject Page Number T9 Deletion of Ticketing Instructions for Minimum Fare Checks T10 Rescission of IATA Resolution 725d Automated Neutral MCO T11 Counterpart Changes to Matrices in Resolutions 722f, 722g and 722h as a result of Matrices Changes to Resolutions 725f and 725g T12 2D Barcode to Store Ticketing Information on the 28 Electronic Ticket Itinerary Receipts T13 Code Designators for Passenger Ticket and Baggage 29 Check Resolution 728 T14 Amendments to Resolution 735 Re-routing to Exchange

233 IX RESERVATIONS Agenda Item Subject Page Number R1 Report - ATA/IATA Reservations Committee (ResCom) 29 R2 Report - Reservations Working Group (RESWG) 29 R3 AIRIMP Editorials 29 R4 Deletion of Incorrect Example in AIRIMP R5 Intentionally Left Blank R6/P Reservations Package 30 R6.1/P AIRIMP Updates Items for Parking Lot 30 R6.2/P Clarification to AIRIMP System Cancel Message 30 R6.3/P Journey Data for Block Space 30 R6.4/P AIRIMP Format Section R6.5/P Booking and Reduce Number in Party in One Booking 31 Session R6.6/P SSR CHLD Construction Rules 31 R6.7/P SSR CHLD Update 31 R6.8/P AIRIMP Editorial R6.9/P Editorial Change to AIRIMP R6.10/P Obtaining Reservations for Involuntary Rerouting 32 R6.11/P Infant Date of Birth in SSR INFT 32 R6.12/P JPTC Verbiage for ET Exchange 32 R6.13/P AIRIMP Description of SSR TKNR 32 R6.14/P AIRIMP Reference to Plating Carrier 32 R6.15/P Code Share NRL Message Format 32 R6.16/P Exchange of NRSA Messages in AIRIMP 32 R6.17/P New Seat Location Code 33

234 X MISCELLANEOUS Agenda Item Subject M1 Report - PSC Steering Group (PSCSG) 33 M1.1 Airport and Inflight Services Structure 33 M2 Report - PADIS Board (PADIS) 33 M3 Report - Cargo Services Conference (CSC) 33 M3.1 Third Party Logistics Companies New 3PL Code 33 M4 Report Scheduling Services 33 M4.1 Report Schedules Information Standards Committee 34 (SISC) M4.2 Interline Connecting Time Intervals Passenger and 34 Checked Baggage Resolution 765 M5 Report Fraud Prevention Working Group (FPWG) 34 M6 Report BSP Data Interchange Standards Group 34 (BDISG) M7 Report Strategic Partnerships 35 M8 Report Dot Aero 35 M9 Report Dot Travel 35 M10 Report ZED-MIBA Forum 35 M10.1 Staff Travel 35 M11 Report Tariff Composite Interline Baggage Working Group 35 Close of Meeting 35

235

236 1 MINUTES 27 TH Joint ATA/IATA Passenger Services Conference (JPSC) 29 th IATA Passenger Services Conference (PSC) Toronto, 9-10 October 2007 ADMINISTRATION A1 Opening of Meeting 1. The Chairman, Mrs Patricia George (AF), opened the 27 TH Joint ATA/IATA Passenger Services Conference (JPSC) and the 29 th IATA Passenger Services Conference (PSC) at 0900 hours on 9 October She introduced Peggy Kessler (DL) as Chairperson of the ATA Passenger Council. The attendance list is shown in Attachment A. 2. Conference noted the anti-trust warning regarding discussion on competitively sensitive topics. A2 Examination of Credentials of Accredited Representatives 3. Conference noted the list of IATA PSC accredited representatives and ATA Passenger Council representatives. A3 Approval of Minutes JPSC/26 and PSC/28 4. Conference approved as published the Minutes from the 26 th meeting of the JPSC and 28 th meeting of the PSC. A4 Status of PSC Resolutions and RPs 5. Conference noted the status of IATA resolutions and RPs. The Secretary advised that in meetings with the US DOT it had become apparent that they had little interest in addressing the changes to RP 1724 (conditions of carriage) which were adopted in 2000 because they believe this to be largely a competitive issue. Therefore the Secretary requested guidance from Conference as to what action to take on RP It was agreed to refer this matter to the PSC Steering Group (PSCSG). ACTION: PSCSG Secretary note: for an up-to-date status of PSC resolutions and RPs, please refer to the PSC extranet site in the folder files

237 2 A5 Effectiveness Date of Amendments to Industry Standards 6. Conference confirmed that the general effective date of 1 June 2008 would apply to all amendments regarding resolutions, RPs and AIRIMP unless otherwise agreed. A6 Any Other Business 7. No new items were raised. A7 Date and Place of Next Meeting 8. Conference endorsed the proposal to hold the next meeting in Geneva on October Secretary note 1: due to hotel accommodation constraints, the meeting has subsequently been re-scheduled for 8-9 October as part of a Passenger Week of events refer to Attachment B. Secretary note 2: for online information on future IATA meetings, refer to: POLICY P1 Report Status of Industry Coding Systems 9. Conference noted the status report regarding the most important industry coding systems that are administered by IATA together with a copy of the procedures used for controlled duplication of airline designators. P1.1 Assignment of Airline Designator for Telecommunications (Resolution 762) 10. AvFinity, an IATA Strategic Partner company, proposed that Resolution 762 be amended to provide them with an airline designator code to allow them to offer their customers a service whereby they can transmit and receive Type B messages for communications purposes, flight plan filing and APIS requirements. Conference did not support this proposal because it was believed that AvFinity could meet their customers needs without the assignment of a unique airline designator code. Conference requested IATA and ATA staff to liaise with AvFinity to seek a solution to their business need. ACTION: ATA/IATA/AvFinity Secretary note: the ATA and IATA have started to modernise the procedures to request the assignment of a unique seven-character teletype address for communications purposes. The draft application form and draft description for the IATA Airline Coding Directory is shown in Attachment C.

238 P1.2 Assignment of Accounting Code for BSP Link (Resolution 767) IATA requested the assignment of a unique accounting code for the billing and settlement of BSPlink agent charges from agents. It was confirmed that the code would not interface with the normal airline revenue accounting process. The PSC agreed to amend Resolution 767 as shown in the book of finally adopted resolutions and RPs (published separately). P1.3 Assignment Criteria for Codes (Resolutions 762 and 767) 12. The Secretary suggested that there was an inconsistency in the provisions of Resolutions 762 and 767 because they provided automatic access to codes for airlines that are members of the ATA or IATA. In recognition that membership criteria to join the ATA and IATA had changed over the years, it was proposed to delete the provision regarding automatic access to codes. Conference agreed to amend Resolutions 762 and 767 as shown in the book of finally adopted resolutions and RPs. P1.4 Location Identifier Working Group (LIWG) 13. The Secretary proposed the establishment of a Location Identifier Working Group (LIWG) to review all airport codes with a view to eliminate inconsistencies and standardise the names within the various categories. Conference agreed to this with Terms of Reference as shown in Attachment D. The following companies indicated interest to participate in the work of the LIWG: AA, ATPCO, DL, KL, LH, Sabre, SITA, UA and Unisys. 14. DL urged the Secretary to provide the industry with a minimum of 2 months of advance notice of agreed changes due to the likely large volume of changes to be implemented. P2 Report BSP Form Codes and Document Supply Chain 15. Conference noted the report of IATA Supply Chain Management (SCM). In recognition of the urgent need for more form codes for the V-MPD, the PSC agreed to amend RP 1720a regarding form codes 201, 261 and 271 with an early effective date of 1 January 2008 as shown with the expedited resolutions and RPs (published separately). The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes. P2.1 Assignment of Additional Form Codes for Airlines (RP 1720a) 16. Due to the significant increase of electronic tickets issued by airlines over the past couple of years, the Ticketing Committee proposed that additional form codes be assigned to airlines. Accordingly, the PSC agreed to amend RP 1720a regarding form codes and with an early effective date of 1 January 2008 as shown with the expedited resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes.

239 4 P2.2 Form Code 24 and The Ticketing Committee proposed an editorial amendment to form code 24 and suggested that form code 290 be reserved for future industry allocation. Accordingly, the PSC agreed to amend RP 1720a regarding form codes 24 and 290 with an early effective date of 1 January 2008 as shown with the expedited resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes. P2.3 Transition to Full OPET Environment from 1 June 2008 and Requirement for Check Digit 18. The Ticketing Committee proposed that Resolution 722g be amended to specify that the form code for ETs issued by travel agents would be uniquely an off premise ET (OPET) form code as of 1 June 2008 in recognition of the deadline date for 100% ET in BSPs. Accordingly the PSC agreed to amend Resolution 722g as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes. 19. Whereas a check-digit for ETs is not required for interline messages between airlines, it was recognised that a check digit calculation is an integral part of GDS processing for BSP reporting tapes. Therefore it was agreed that OPET form codes would use method 3 for check digit calculation (i.e. the current method for OPATB2). It was confirmed that whereas the change to RP 1720a would be effective 1 January 2008, the application would not start before 1 June 2008 in recognition that until that date some markets have been allocated ET form codes in formally OPTAT markets which use method 2 for check digit calculation. Accordingly, the PSC agreed to amend RP 1720a regarding form codes , 199, , 49, 56 and 57 with an early effective date of 1 January 2008 as shown with the expedited resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes. 20. In recognition of the deadline date for 100% ET in BSPs, it was proposed to reclassify all IATA travel agency (BSP) ticket form codes as from 1 June 2008 to be Standard Neutral Electronic Ticket (OPET) Only. The Secretary advised that a special note would be appended to those form codes that had been previously allocated to OPTAT markets. This would facilitate recognition that such new assignments would have to change the check digit routine to method 3. The PSC agreed to amend RP 1720a accordingly as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes.

240 5 P2.4 Deletion of Electronic Excess Baggage Ticket From Form Code The Secretary proposed that the description of form code 260 be amended by deleting reference to an electronic excess baggage ticket because this is no longer supported by industry standards. The PSC, noting one abstention, agreed to amend RP 1720a accordingly with an early effective date of 1 January 2008 as shown with the expedited resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes. P3 Ratification of Special Fees and Charges Codes (Resolution 728) 22. Conference unanimously agreed to ratify the list of codes shown in Attachment E that has been assigned on a provisional basis since the last meeting of the JPSC in October P3.1 Tax Code Exhaustion 23. The 2006 meeting of the JPSC had requested the Ticketing Committee to explore amending the standards for ticket tax/fee/charge codes (currently twoalpha) in anticipation of depleting the remaining stock by about The Secretary advised that there were two obvious options to expand the amount of codes: expand to three-character or amend to allow alpha/numeric combinations. In his view the latter option would be the least complex and most cost-effective. Conference requested the Ticketing Committee to develop new standards for ticket tax codes based on the concept of alpha/numeric combinations. ACTION: TICKETING COMMITTEE P4 Report Simplifying the Business (StB) 24. Conference noted this report. Secretary note: after formal close of business, the JPSC delegates were provided with a presentation on ET and StB by Yngvar Sundsfjord of IATA. His presentation has been posted to the PSC extranet site in folder PSC 29 P4.1 Report Baggage Improvement Programme (BIP) 25. Conference noted this report. Secretary note: after formal close of business, the JPSC delegates were provided with a full presentation by Andrew Price of IATA. His presentation has been posted to the PSC extranet site in the folder PSC 29

241 6 P4.2 Report The Future of Other Documents 26. Conference agreed conceptually that to realise maximum benefits from electronic ticketing it is necessary to find a methodology to make all other remaining paper documents (e.g. MCOs, MPDS) electronic as well. This would be consistent with the BSP best practice to remove all remaining paper documents as soon as feasible. 27. The Chairman noted that the obvious solution would be full implementation of the Electronic Miscellaneous Document (EMD), however, she recognised that little had been achieved due to airline and GDS resources having been focussed on 100% implementation of ET by 1 June Thereafter it was agreed to form an informal industry oversight group to accelerate implementation of the stand-alone version of the EMD, known as EMD-S. Volunteers for this group are: AA, AF, Amadeus, ARC, ATPCO, Axess, BA, DL, EDS, Galileo, Infini, ITA Software, JL, KL, LH, Sabre, SITA, UA, Unisys and Worldspan. ACTION: EMD INDUSTRY OVERSIGHT GROUP 28. The Chairman noted that IATA was implementing a product in all BSP markets known as the virtual MPD (V-MPD) to provide an electronic methodology to enable travel agents to record pre-payment for a service (e.g. air transportation, excess baggage, etc.). She recognised that the V-MPD was not a perfect solution in that it had no automatic link to the PNR or an agent s back office systems, however, it should be a good interim methodology in anticipation of full implementation of the EMD. Noting some negative comments from carriers, the Chairman urged IATA to continue improving the functionality of the V-MPD to meet the airlines needs for an acceptable interim solution. ACTION: IATA 29. There was some discussion regarding a GDS product known as MD50 which would no longer be viable in its current form due to the removal of all OPATB2 stock on 1 June. One carrier requested that the GDSs explore the continuation of their MD50 product but without the necessity to issue a value coupon on OPATB2 paper stock. The Chairman concluded that industry resources would be better focussed on full implementation of the EMD rather than diverted on an interim product that would compete with the V-MPD. 30. Having said that, the Chairman urged the Secretary to provide clear information as soon as possible to airlines, GDSs and travel agents regarding the transition to 100% ET and the situation for other documents in BSPs due to significant confusion regarding the options available. Secretary note: in mid December IATA circulated two documents containing a summary sheet of key issues regarding the cutover to 100% ET one aimed at airlines and one for travel agents. Refer to Attachments F and G.

242 7 P4.3 Automated MPD on Blank Paper 31. This subject was addressed during discussion under agenda item P4.2. P4.4 ET only for MITA (Resolution 780) 32. The Secretary advised that he had been contacted by some carriers who wished to have a provision in MITA (Resolution 780) that would provide an option to advise interline parties that from a certain date no more paper tickets should be issued for them. Noting 6 negative votes and 4 abstentions, the Chairman declared this proposal defeated. P4.5 Removal of MITA Application Forms (Resolution 780) and Deletion of Reference to All Fares Product 33. The Secretary proposed that Resolution 780 be amended to remove the application forms and reference to the All Fares product that does not exist. The PSC agreed to amend Resolution 780 as shown in the book of finally adopted resolutions and RPs. P5 Ticket Notices 34. IATA Legal, under the leadership of Colin Flynn, had established a working group in 2006 with an ambitious goal to develop a single ticket notice to incorporate the new liability provisions of Resolution 724c together with some outdated ticket notices (Resolutions 724, 724a, 724b) and include a suitable summary on dangerous goods per Resolution 745. It was noted that some dialogue had occurred with the US DOT in recognition of their keen interest in ticket notices due to various longstanding US regulations in this area. 35. The new ticket notice (to be published as revamped Resolution 724) was presented to the PSC as endorsed by the IATA Legal Forum. The PSC, noting one abstention, agreed to adopt the new ticket notice to completely replace current Resolution 724 and at the same time rescind Resolutions 724a, 724b and 724c as shown in the book of finally adopted resolutions and RPs (Part 1). 36. Mr Flynn extended his thanks to the legal working group and specifically cited John Parkerson (DL) and Jim Casey (ATA) for their invaluable help. The Chairman requested the Secretary to send the compliments of the Conference to Connie O Keefe of Squire, Sanders & Dempsey who had done an outstanding job as outside counsel for IATA on this issue.

243 8 P5.1 Ticket Notices Consequential Changes 37. The Secretary proposed several consequential amendments to ticketing resolutions to bring them in line with the provisions of the new ticket notice adopted under agenda item 5. The PSC, noting one abstention, agreed to amend Resolutions 720, 720b, 722, 722a, 722c, 722f and 722g as shown in the book of finally adopted resolutions and RPs. P6 Co-ordination with the Commission of European Communities (CEC) on PSC Matters 38. Conference noted this report. P6.1 Airport Lists for Passengers with Reduced Mobility (PRM) 39. Conference noted that ACI and AEA had requested IATA s help to develop industry standards regarding PRM communications from airlines to airports to meet the provisions of EU Regulation 1107/2006. Accordingly, IATA working groups developed guidelines for new PRM airport lists to comprise a recap of the message rules and examples of the new lists as shown in Attachment H. 40. The working groups also developed a new RP 1708a for message standards for a passenger assistance list (PAL) and a change assistance list (CAL) together with consequential changes to the data dictionary in RP 1707b. The PSC, noting two abstentions, agreed to establish RP 1708a and amend RP 1707b with an early effective date of 1 May 2008 as shown with the expedited resolutions and RPs. 41. A new SSR code for AIRIMP had been developed (DPNA) to cater for disabled passengers with intellectual or developmental disability needing assistance. This new code DPNA was adopted by Conference as shown in Attachment I. The ATA Passenger Council adopted counterpart amendments to SIPP as shown in Section II of the ATA Minutes. 42. Conference also ratified the Standard Message Identifier (SMI) codes CAL and PAL as shown in Attachment J. P6.2 Acceptance and Carriage of Incapacitated Passengers (Resolution 700) 43. The Secretary proposed that Conference consider the establishment of a working group to modernise the language of Resolution 700. There was some support for this, however, the conclusion was to await the proposed amendments being developed by the IATA Medical Advisory Group (MAG). ACTION: MAG

244 9 P7 Anti-Trust Immunities - Australia 44. Mr Colin Flynn (IATA) reported that following a thorough review of PSC resolutions and RPs, it had been concluded that no changes were required in reaction to the loss of an authorisation for PSC activities from the Australian authorities effective 31 August P8 Contact of Air Passengers Exposed to a Health Hazard (RP 1798) 45. The IATA Medical Advisory Group (MAG) proposed a complete re-write of RP 1798 to broaden the scope from communicable diseases to any health hazard to bring it in line with the International Health Regulations (IHR). The PSC agreed to amend RP 1798 as shown in the book of finally adopted resolutions and RPs. P9 Optional Service Task Force (OSTF) 46. The OSTF developed a new Recommended Practice 1790 and new reservations procedures to allow Members to automate the pricing, booking and payment of ancillary services such as prepaid meals, priority seating, lounge access and inflight entertainment amongst others. 47. The PSC agreed, noting one abstention, to establish RP 1790 (Additional Services) as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council established counterpart RP as shown in Section II of the ATA Minutes. 48. Conference agreed, noting one abstention, to amend AIRIMP with new reservations procedures as shown in Attachments K and L. The ATA Passenger Council adopted counterpart amendments to SIPP as shown in Section II of the ATA Minutes. P9.1 Additional Services RP Subsequent to the establishment of RP 1790, the ATPCO optional services meeting proposed minor amendments to paragraphs 5 and 11. The PSC, noting three negative votes, agreed to amend RP 1790 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council agreed to counterpart changes to RP as shown in Section II of the ATA Minutes. 50. ATPCO advised that they were seeking guidance on the method of rounding amounts calculated for additional services. Conference agreed to send the question to the passenger tariff Resolutions Advisory Panel (RAP) to develop a formal proposal for subsequent adoption by the Composite Conference. ACTION: RAP

245 10 P9.2 OSTF Mandate 51. ATPCO proposed that the mandate of the OSTF be extended for a further 12 months. This was agreed. P10 Meal Definitions and Codes (RP 1773) 52. Recognising that the IATA guidelines for meal definitions had not been updated since 1994, a special meal definition task force was formed to revamp RP 1773 to provide clearer guidance to airline caterers. The task force was mindful of stringent labelling laws so as to provide increased levels of food safety to passengers whilst decreasing carrier liability. The proposal included the addition of two new special meals (vegetarian Jain/VJML and vegetarian oriental/voml) as well as the deletion of five meals (low protein, low purin, high fibre, oriental and seafood) which were considered no longer necessary because of medical advances or because they were not required by major religious groups. 53. Some airlines expressed disappointment that this important agenda item had not been submitted to the Reservations Committee (ResCom) who would need to study the significant implications for airline and GDS reservations systems. The Secretary acknowledged that this proposal would normally pass through the ResCom, however, noted that the task force did not finalise their work in time and so had submitted their proposal directly to Conference. The Chairman urged attendees to resolve any major issues of concern otherwise the proposal would be delayed until next year s meeting. 54. While Conference could accept the amended special meal definitions and names, it could not accept proposed amendments to meal codes because they would be costly and complex to implement. Conference agreed to delete four meals but retained the seafood meal. 55. Conference had significant concerns on how to implement the new/amended/deleted meals in view that most systems accept reservations about 300 days in advance. As a consequence, it was agreed that whilst the new standards would come into effect on 1 June 2008, they would only apply to bookings for travel on/after 1 June Secretary note: airlines and GDSs should plan to advise their agents that four meals will cease to be available for travel on/after 1 June 2009 (low protein, low purin, high fibre and oriental) and therefore codes LPML, PRML, HFML, ORML will need to be deleted from the meal preference section of the passenger profile in their systems by that date. 56. Accordingly the PSC, noting three negative votes, agreed to completely new wording and format for RP 1773 as shown in the book of finally adopted resolutions and RPs. 57. Conference agreed to amend AIRIMP as shown in Attachment M on the understanding that the new/amended/deleted meals would apply to bookings for travel on/after 1 June The ATA Passenger Council adopted counterpart amendments to SIPP as shown in Section II of the ATA Minutes.

246 11 P11 Reduced Rate Transportation (Resolution 788) 58. The International Civil Aviation Organisation (ICAO) proposed an amendment to Resolution 788 to include ICAO staff as eligible for free and reduced rate travel. Noting 7 negative votes, this proposal was declared defeated. The Chairman noted that ICAO is at liberty to contact any carrier on an individual basis to request a consideration for their staff when travelling on vacation. AIRPORT SERVICES B1 Report of Airport Services Committee (ASC) 59. Conference noted this report and elected JL, UA, AF and LH to the IATA Airport Services Committee as shown in Attachment N. B2 Report of the IATA Ground Handling Council (IGHC) 60. Conference noted this report. B3 Report of Common Use Self Service Management Group (CUSSMG) 61. Conference noted this report. B3.1 Report of RP 1797 Review Sub-Group 62. Conference noted this report and re-established the RP 1797 Review Sub- Group for a further 12 months. This group has held several meetings and has produced a comprehensive document that will serve as guidance for the industry as it moves towards a new common use platform. This document will be available for reference on the CUSS extranet page. 63. The PSC agreed to amend RP 1797 as shown in the book of finally adopted resolutions and RPs to change the name from CUTE to CUPPS (Common Use Passenger Processing Systems). The entire text was deleted and replaced with reference to CUPPS documentation regarding procedures and specifications. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes.

247 12 B4 Report of BCBP Working Group 64. Conference noted this report and re-established the BCBP working group for another 12 months. The BCBP working group presented changes to the Resolution 792 that will facilitate the acceptance of bar codes on electronic devices such as PDA s and mobile phones. These changes included the adoption of 3 different symbologies that will allow a variety of choice and not force any particular matrix code on any airline. 65. The PSC agreed to amend Resolution 792 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to Resolution as shown in Section II of the ATA Minutes. B5 Report of the DCS Working Group 66. Conference noted this report and re-established the DCSMWG for a further 12 months with terms of reference as shown in Attachment O. B6/P Package Items (DCS) 67. This package contained miscellaneous items that had been approved at committee level with no opposition noted. Agenda items B6.1/P through B6.12/P were unanimously adopted by PSC as proposed. B6.1/P Editorial Changes to RP 1719c 68. The ASC proposed to clarify the time of dispatch in the Electronic Ticket List RP. The PSC agreed to amend RP 1719c as shown in the book of finally adopted resolutions and RPs. B6.2/P Editorial Changes to RP The ASC proposed an editorial change for clarity in the Remarks Elements for child information. The PSC agreed to amend RP 1708 as shown in the book of finally adopted resolutions and RPs. B6.3/P Editorial Changes to RP 1707b 70. The ASC proposed an editorial change to harmonize the definition of the code RG as seen in RP 1788 with the definition as seen in the Data Element Dictionary for DCS messages. The PSC agreed to amend RP 1707b as shown in the book of finally adopted resolutions and RPs.

248 13 B6.4/P DCS Provisions for Additional Services 71. The ASC proposed counterpart changes to several RPs as a result of the changes adopted to reservations standards as proposed by the Optional Services Task Force (OSTF) refer to agenda item P9. The PSC agreed to amend RP 1708, RP 1715, RP 1716, RP 1719 and RP 1719b as shown in the book of finally adopted resolutions and RPs. B6.5/P Necessity of Group Identifier for Block Seats Indicator ZZ, RP 1707b 72. The ASC proposed changes to the examples of block seat indicator as the current ones in use lead to a variety of interpretations prompting confusion. Editorial changes were made to RP 1707b; Data Element Dictionary for DCS Passenger Messages as well as the examples contained in RP 1708 Passenger name List (PNL) and Additions and Deletions (ADL). The PSC agreed to amend RP 1707b and RP 1708 as shown in the book of finally adopted resolutions and RPs. B6.6/P Use of Passenger Level, RP The ASC proposed editorial changes to RP 1708 Passenger name List (PNL) and Additions and Deletions (ADL). The PSC agreed to amend RP 1708 as shown in the book of finally adopted resolutions and RPs. B6.7/P Format for ADL Elements, RP The ASC proposed editorial changes to RP 1708 Passenger name List (PNL) and Additions and Deletions (ADL). The PSC agreed to amend RP 1708 as shown in the book of finally adopted resolutions and RPs. B6.8/P Party/Group/Tour Field Name, RPs d 75. The ASC proposed editorial changes to all DCS messages as it found that there are no instances of a tour PNR. PSC agreed to amend RP s d as shown in the book of finally adopted resolutions and RPs. B6.9/P Editorial Changes to RP The ASC proposed editorial changes to RP 1708 Passenger name List (PNL) and Additions and Deletions (ADL). The PSC agreed to amend RP 1708 as shown in the book of finally adopted resolutions and RPs.

249 14 B6.10/P Discrepancy in Automated PNR Address Element with No Company Designator, RP 1707b 77. The ASC proposed changes to RP 1707b, Data Element Dictionary for DCS Passenger Messages, as the text contradicted existing text in a subsequent paragraph. The PSC agreed to amend RP 1707b as shown in the book of finally adopted resolutions and RPs. B6.11/P Changes to RP 1707b to Match AIRIMP 78. The ASC proposed changes to RP 1707b, Data Element Dictionary for DCS Passenger Messages, to ensure that the DCS messages were consistent with AIRIMP. The PSC agreed to amend RP 1707b as shown in the book of finally adopted resolutions and RPs. B6.12/P PSM and PTM: Show Operating Carrier and Flight Number for a Code Share Flight, RP 1715 and RP The ASC proposed changes to RP 1715 and RP 1718 to ensure that the operating flight is always transmitted in the flight element. This agenda item also reinforced that for the onward connecting flight that the operating flight was to be reflected as well as per RP The PSC agreed to amend RP 1715 and RP 1718 as shown in the book of finally adopted resolutions and RPs. B7 Report of the Baggage Working Group (BWG) 80. Conference noted this report and re-established the Baggage Working Group for a further 12 months. New terms of reference were also provided for the BWG and a Process Sub Group (PSG) that looks at processes within the automated handling environment as shown in Attachments P and Q. B8/P Package Items (BWG) 81. This package contained miscellaneous items that had been approved at committee level with no opposition noted. Accordingly, agenda items B8.1/P through B8.13/P were unanimously adopted by PSC as proposed. 82. The ATA Passenger Council adopted counterpart amendments as shown in Section II of the ATA Minutes.

250 15 B8.1/P Editorial Changes Plus Additions to RP The ASC proposed editorial changes as well as the addition of new text to promote clarity in the RP definitions and examples. The PSC agreed to amend RP 1800 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council, noting one abstention, adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B8.2/P Editorial Changes to RP The ASC proposes editorial changes to RP The PSC agreed to amend RP 1745 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B8.3/P New Message to RP 1745 BRQ 85. The ASC proposed an additional message to RP 1745 called the BRQ or Baggage Request Message. This new message is necessary to enable the automated baggage re-tagging as described in the IATA RP The PSC agreed to amend RP 1745 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B8.4/P Amend RP 1745, Attachment A Section The ASC proposed several new codes to be added to the table so as to ensure consistency between RP 1745 and RP The PSC agreed to amend RP 1745 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B8.5/P Amend RP The ASC proposed to add a new example and editorial changes to RP The PSC agreed to amend RP 1745 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B8.6/P Amend Resolution IATA management proposed an editorial change to Resolution 740 to clarify existing text and ensure manufacturers compliance. The PSC agreed to amend Resolution 740 as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes.

251 16 B8.7/P RP 1743a, Tracing Procedure for Missing Checked Baggage 89. The ASC proposed editorial changes to RP 1743a to ensure that the correct resolutions are reference when the settlement of a claim is undertaken. The PSC agreed to amend RP 1743a as shown in the book of finally adopted resolutions and RPs. B8.8/P RP 1743e, Baggage Irregularity Report 90. The ASC proposed editorial changes to RP 1743e. The PSC agreed to amend RP 1743e as shown in the book of finally adopted resolutions and RPs. B8.9/P RP 1797b - Baggage System Interface (BSI) 91. The ASC proposes the renumber the RP1797b to RP The PSC agreed to renumber RP 1797b to RP 1746 as shown in the book of finally adopted resolutions and RPs. B8.10/P RP Carriage of Carry-On Baggage 92. The ASC undertook a complete rewrite of the RP concerning carry on baggage, as much of the content was out of date and no longer relevant. The PSC agreed to amend RP 1749 as shown in the book of finally adopted resolutions and RPs. B8.11/P RP 1740c - Radio Frequency Identification (RFID) Specifications for Interline Baggage 93. The ASC proposed an editorial change to change the default result from 0 to 1 in the security information in RP 1740c. The PSC agreed to amend RP 1740c as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B8.12/P RP 1740c - New IATA Objective ID for Internal Airport Status 94. The ASC proposed to add a new IATA Objective ID for Internal Airport Status in RP 1740c. The PSC agreed to amend RP 1740c as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes.

252 17 B8.13/P RP 1740c - Replace the Date in Object Identifier 12.6 in Julian Format 95. The ASC proposed to replace the date in object identifier 12.6 in Julian format rather than in the current day and month format in RP 1740c. The PSC agreed to amend RP 1740c as shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council adopted counterpart amendments to RP as shown in Section II of the ATA Minutes. B9 Adoption of New Bilateral Code ETLP for Identifying Ticketless Travel Product in RP1707/1708 and Proposal of New RP 1719d 96. ASC proposed the establishment of bilateral standards to allow industry systems to process ticketless products. It was explained that the proposal would have no impact on interline standards and was simply designed to facilitate a standard process between an operating carrier and its ground handling company for ticketless products. 97. LH expressed disappointment at how this item had developed, as she believed it only addressed one part of the problem. She proposed that Conference endorse a multi-disciplinary approach to develop comprehensive industry standards for ticketless products. However, this ambitious proposal was not supported in view that the original proposal came from ground handlers who were seeking guidelines for their DCS systems. 98. Noting 3 negative votes, the PSC agreed to establish RP 1719d (Ticketless Product List) and endorsed consequential changes to RPs 1707a, 1707b and 1708 as shown in the book of finally adopted resolutions and RPs. B10 Responsibility for Delivery of Interline Checked Baggage 99. The ATA Baggage Committee proposed to rescind ATA resolution due to the fact that members no longer felt there was a business need for it. The ATA Passenger Council agreed to rescind ATA resolution as shown in Section II of the ATA Minutes. B11 Multi-Passenger Count in SSR FOID in DCS Messages 100. Unisys Corporation proposed an editorial change to provide clarity so that the rule can be expressly stated to avoid any confusion. This would represent a technical change to those companies that were not following the implied rule as currently illustrated in RPs 1707b, 1708 and 1719c. PSC agreed to amend RPs 1707b, 1708 and 1719c as shown in the book of finally adopted resolutions and RPs.

253 18 TICKETING T1 Report of Ticketing Committee Selection of Committee Membership for PFPC 101. Conference noted the report of the Joint Passenger Ticketing Committee (JPTC) as presented. PSC noted the appointment of Mr. Johan Lodewijckx (KL) to the position of Chairman of the IATA PFPC. Ms. Dawn Jetchick (NW) was appointed by acclamation to the position of Vice-Chair to the IATA PFPC. Chairman thanked the Committee for its work done throughout the year Conference was advised that the terms of office for BA, KL, LH, ME, MS and OS were expiring and that seven Ticketing Committee members would need to be selected. The Chairman asked if there were any other Members that wished to be considered There being no more than six nominations, by acclamation BA, EK, KL, LH, MS, and US were elected for a three year period. A copy of the updated membership is shown in Attachment R. Conference noted that there is one place vacant Conference extended the mandate of the Exchange and Reissues Working Group (EARWG) for a further 12 months. T2/P Ticketing Package 105. This package contained miscellaneous items that had been approved at Committee level with no opposition noted. Agenda items T2.19/P and T2.25/P were removed from the package for separate consideration. Agenda items T2.1/P through T2.31/P were unanimously adopted as proposed. Amendments to the IATA Resolutions and RPs are published with the finally adopted resolutions and RPs or expedited resolutions and RPs as noted below. ATA Members unanimously adopted as proposed, amendments to the ATA resolutions for agenda items T2.1/P through T2.31/P as shown in Section II of the ATA Minutes with the exception of items T2.17/P, T2.18/P, T2.24/P and T2.30/P that were for IATA action only. T2.1/P EMD Amendment to Disassociation 106. Conference unanimously agreed to add procedures that indicate, in the case of an associated Electronic Miscellaneous Document (EMD-A), when it is disassociated, a record of the document number that was associated to it shall be maintained in the electronic ticket record. This requires a new qualifier indicating whether the EMD is associated or has been disassociated. Amendments to IATA Resolution 725f are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes.

254 19 T2.2/P EMD Amendments to Matrix in Resolution 722g and ATA Resolution Conference unanimously agreed to add new data elements to the neutral ticketing matrices that were identified as required when creating the matrix for the new Electronic Miscellaneous Document. Amendments to IATA Resolution 722g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. Secretary note: The title of this agenda item should read ATA Resolution and not as shown. T2.3/P EMD Glossary Definition for Validating Carrier 108. Conference unanimously agreed to clarify the definition of the data element Airline Designator (Validating Carrier) since it was found that there were two similar definitions in the data elements glossary and it was difficult to determine the differences. Amendments to IATA Resolution 722f are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T2.4/P EMD Amendments to Data Elements Glossary and Matrices 109. Conference unanimously agreed to clarify in the data elements glossary the difference between certain data elements referencing the fare basis and ticket designator. Amendments to IATA Resolutions 722f, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution 20.60, and are published in Section II of the ATA Minutes. T2.5/P Display from the Operating Carrier to the Ground Handler 110. Conference unanimously agreed to add a new transaction action code J to the electronic ticketing resolutions to address the situation whereby an Operating Carrier requests an electronic ticket display to an airline acting as a ground-handler and that airline is also the Validating Carrier of the electronic ticket. This is because in these scenarios the Validating Carrier does not know whether they should return information in the response as the Validating Carrier or as the ground-handler acting on behalf of the Operating Carrier. Amendments to IATA Resolutions 722f and 722h are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution and are published in Section II of the ATA Minutes.

255 20 T2.6/P Change of Status Out-of-Sync Condition 111. Conference unanimously agreed to add procedures to address the issue that arises when a database out-of sync condition exists when the Validating Carrier of the electronic ticket requests the return of control from the Marketing or Operating Carrier resulting in the carrier believing the other party is in control of the coupon. This results in continuous looping of messages. Amendments to IATA Resolution 722f are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T2.7/P Net Fare Component Information 112. Conference unanimously agreed to add new data elements into the electronic ticketing data elements glossary that will allow the identification of different net fares when combined on one ticket. Amendments to IATA Resolution 722f are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T2.8/P EMD Series of Amendments 113. Conference unanimously agreed to add a series of new data elements into the electronic ticketing data elements glossary for the issuance of the EMD as an excess baggage ticket in addition to identifying a series of sub codes for the specific type of excess baggage being collected and the related amendments to the matrices. In addition, amendments to the data element Bank Exchange Rate identifying that the rate to be used is the selling rate and not the buying rate as well as adding various references for the EMD were adopted. Amendments to IATA Resolutions 722f, 722g, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, 20.61, and are published in Section II of the ATA Minutes. T2.9/P Pricing Indicator for Carrier Fees 114. Conference unanimously agreed to add a new data element Carrier Fee Reporting Indicator in order to differentiate the pricing methodology of any carrier fee from the pricing methodology of the ticket. Amendments to IATA Resolutions 722f, 722g, 722h, 725f and 725g. are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution 20.60, 20.61, 20.62, and are published in Section II of the ATA Minutes.

256 21 T2.10/P Matrix Updates for Category Conference unanimously agreed to changes to the electronic ticket and electronic miscellaneous documents matrices to complete the agenda item adopted under T2.7/P. Amendments to IATA Resolutions 722f, 722g, 722h, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, 20.61, 20.62, and are published in Section II of the ATA Minutes. T2.11/P Commission Type Text Correction 116. Conference unanimously agreed to amend the wording for the data element Commission Type to reflect what is published in the Data Interchange Standards Handbook (DISH). Amendments to IATA Resolution 722f, are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution 20.60, are published in Section II of the ATA Minutes. T2.12/P Fare Calculation Entries for Ticket Discounts 117. Conference unanimously agreed to amend the data element Fare Component Construction Principle Indicator to incorporate a code to denote the inclusion of a ticket discount. Amendments to IATA Resolution 722f are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T2.13/P Tax Audit Data Elements 118. Conference unanimously agreed to adopt the addition of a series of new data elements to identify tax data at the coupon level that will facilitate the auditing of taxes, fees and charges (as amended onsite). Amendments to IATA Resolutions 722f, 722g, 722h, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, 20.61, 20.62, and are published in Section II of the ATA Minutes. T2.14/P Proration Data Elements 119. Conference unanimously agreed to adopt the addition of a new data element to identify Around-the-World fares considered necessary for proration in revenue accounting. Amendments to IATA Resolutions 722f, 722g, 722h, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, 20.61, 20.62, and are published in Section II of the ATA Minutes.

257 22 T2.15/P Fare Audit Data Elements 120. Conference unanimously agreed to adopt the addition of a new data element Fare Component Coupon Priced Reservations Booking Designator which is considered necessary to audit that the correct level of fare was collected on the ticket sale. Amendments to IATA Resolutions 722f, 722g, 722h, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, 20.61, 20.62, and are published in Section II of the ATA Minutes. T2.16/P Amendment to Fare Component Ticket Designator 121. Conference unanimously agreed to adopt changes to the data element Fare Component Ticket Designator and the addition of a new data element Fare Component Ticket Designator Qualifier which will allow multiple ticket designators to be identified and reported at the fare component level. Amendments to IATA Resolutions 722f, 722g, 722h, 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, 20.61, 20.62, and are published in Section II of the ATA Minutes. T2.17/P Unique Fare Basis Code for IATA Fares Established by Flex Fare Process 122. Conference unanimously agreed to adopt a new fare basis code to identify IATA flex fares with an early effectiveness date of 1 February Amendments to IATA Resolution 728 are published in the book of expedited resolutions and RPs. T2.18/P Rescission of Neutral Paper Tickets Resolutions and Related Amendments 123. Conference unanimously agreed to rescind IATA Resolutions 721a and 722d, related to BSP neutral ticket stock since as a result of 100 percent electronic ticketing in BSPs they will no longer be issued on/after 1 June In addition Conference agreed to amend Resolution 722a to remove any references to BSP supplied neutral tickets to Members. Resolution 728 was also amended to delete references to Resolution 722d. Rescission of IATA Resolutions 721a and 722d and amendments to IATA Resolutions 722a and 728 are published in the book of finally adopted resolutions and RPs. There was no ATA proposal.

258 23 T2.19/P Flight Prefix/Suffix 124. This item was withdrawn from the package of items submitted under agenda item T2/P. This proposal sought to include a series of data elements in the electronic ticket data elements glossary and related matrices that would enable the storage of the flight prefix/suffix whenever sent by a DCS system when it is used to differentiate between a new operating flight and an old operating flight that has been reinstated after a flight cancellation. A reservations and ticketing system supplier queried the use of the definition prefix as they noted that although there is a clear definition of a flight suffix, there was no definition of a flight prefix in scheduling nor reservations standards. A Member confirmed in reply that they do use a flight prefix to identify these flights and needed to have this information recorded in the electronic ticket record and not in schedules nor reservations On a formal vote Conference unanimously agreed to amend IATA Resolutions 722f, 722g and 722h as shown in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, and are published in Section II of the ATA Minutes. T2.20/P Rescission of IATA Resolution 738 Agents Refund Voucher and Reserve of Form Code Conference unanimously agreed to rescind Resolution 738 Agents Refund Voucher since it is no longer distributed. In addition Conference agreed to amend Recommended Practice 1720a reserving form code 303 allocated for this purpose, for future industry allocation with an early effectiveness date of 1 January Rescission of IATA Resolution 738 and amendments to Recommended Practice 1720a can be found in the book of expedited resolutions and RPs. Counterpart changes to ATA Resolution are published in Section II of the ATA Minutes. T2.21/P EMD Deduction Method 127. Conference unanimously agreed to adopt changes to resolutions to clarify that the deduction method used where paper miscellaneous charges orders (MCOs) are issued as unspecified MCOs shall not apply to the EMD. Amendments to IATA Resolutions 720a, 725a, 725f, 725g and 726f are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions and are published in Section II of the ATA Minutes. T2.22/P EMD Group Deposit 128. Conference unanimously agreed to adopt changes to the EMD resolutions to clarify that an EMD Stand-Alone (EMD-S) can be issued for more than one passenger when a group deposit is collected. Amendments to IATA Resolutions 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions and are published in Section II of the ATA Minutes.

259 24 T2.23/P EMD Matrix Amendments 129. Conference unanimously agreed to adopt changes to the EMD messaging matrices to correct several anomalies that had been discovered since the original matrices were adopted. Amendments to IATA Resolutions 725f and 725g are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions and are published in Section II of the ATA Minutes. T2.24/P EMD Itinerary Receipt and Ticket Notices for EMD 130. Conference unanimously agreed to adopt a standard approach to incorporate a notice which will be imprinted on the receipt and one generic terms and conditions notice that shall be provided to the passenger or sponsor instead of the choice of two notices. Amendments to IATA Resolutions 725f and 725g are published in the book of finally adopted resolutions and RPs. There was no counterpart motion to amend ATA Resolutions since the ATA advised that all legal notices were under review. T2.25/P Passenger Names on Tickets with Single Letters 131. This item was withdrawn from the package of items submitted under agenda item T2/P. This proposal sought to have a standard approach to the ticketing of passengers with a single letter family name since it was acknowledged that not all systems could accommodate a single character in the family name element of the Passenger Name Record (PNR). Previously, reservations procedures had been adopted in AIRIMP to allow for two possible options but ticketing procedures had not been amended to reflect such options allowed under AIRIMP rules It was queried as to why there were two options presented. In response, it was noted that the Reservations Committee had taken a pragmatic approach to adopting new AIRIMP standards based on what was already being done in the marketplace and concluded that there would not be a general consensus to agree on one methodology On a formal vote, Conference unanimously agreed to adopt changes to IATA Resolutions 720a, 722, 722c, 722f, 725a, 725b, 726a, 726e and 726f as published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.12, 20.13, 20.51, 20.52, 20.60, , and are published in Section II of the ATA Minutes.

260 25 T2.26/P Deletion of Eurocard (EC) from Resolution 728/ATA Conference unanimously agreed to delete the code EC (denoting Eurocard) from the list of card vendor codes used in the form of payment of a ticket with an early effectiveness date of 1 January 2008 since the brand no longer exists. Amendments to IATA Resolution 728 are published in the book of expedited resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T2.27/P Addition of Presto to Resolution Conference unanimously agreed to the adoption of a new card vendor code PR (denoting the Presto card used in Chile) with an early effectiveness date of 1 January Amendments to IATA Resolution 728 are published in the book of expedited resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T2.28/P Transition to Full Tax Breakout 136. Conference unanimously agreed, with an early effectiveness date of 1 January 2008, to extend the deadline for the removal of combined tax/fee/charge data (denoted with code XT ) and the XT tax/fee/charge breakdown to 1 February 2009 but on the understanding that this extension will not stop carriers implementing it before the deadline if they are ready to do so. Amendments to IATA Resolutions 720a, 722, 722f and 722g are published in the book of expedited resolutions and RPs. Counterpart amendments to ATA Resolutions 20.10, and are published in Section II of the ATA Minutes. T2.29/P Clarification for 99 Occurrences of Tax, Fee, Charge Data 137. Conference unanimously agreed to add wording to the airline and neutral electronic ticketing resolutions with an early effectiveness date of 1 January 2008 to clarify that there can be 99 occurrences of new and 99 occurrences of paid tax/fee/charge data in accordance with standard PADIS EDIFACT messages. Amendments to IATA Resolutions, 722f and 722g are published in the book of expedited resolutions and RPs. Counterpart amendments to ATA Resolutions and are published in Section II of the ATA Minutes. T2.30/P Add ET Only to Resolution 722a 138. Conference unanimously agreed to add wording to IATA Resolution 722a making electronic tickets mandatory for electronic ticketing eligible itineraries. Amendments to IATA Resolution 722a are published in the book of finally adopted resolutions and RPs. There is no equivalent ATA resolution requiring amendment.

261 26 T2.31/P Updates to Resolution 722h/ATA20.63 Matrix 139. Conference unanimously agreed to correct inconsistencies identified in the electronic ticket ground handling resolutions as a result of the work done to develop the XML messages for ground handling. Amendments to IATA Resolution 722h are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes. T3 Block Space Codeshare Amendment to Resolution 722f and Glossary 140. With no discussion, on a formal vote Conference unanimously agreed to add a new data element to the electronic ticketing data elements glossary and corresponding matrices, Billing Carrier Indicator so that the billing carrier can be easily identified in the information only Unsolicited Airport Control message sent from the operating carrier to the marketing carrier for the purposes of billing in a block space code share scenario. Amendments to IATA Resolutions 722f, 722g and 722h are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, and are published in Section II of the ATA Minutes. T4 Data Elements for Fare Related Optional Services 141. With no discussion, on a formal vote, Conference unanimously agreed to add a series of new data elements to the electronic ticketing data elements glossary and corresponding matrices which will enable the collection of fare related optional services. Amendments to IATA Resolutions 722f, 722g and 722h are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions 20.60, and are published in Section II of the ATA Minutes. T5 Bar Coded Boarding Pass (BCBP) Deadline Mandate 142. With no discussion, on a formal vote, Conference unanimously agreed to sunset the provision for an ATB2 magnetic stripe encoded boarding pass in accordance with the decision made by the IATA Board of Governors (see agenda item P4). Amendments to IATA Resolution 722c are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolution are published in Section II of the ATA Minutes.

262 27 T6 Responsibility for a Delay Causing Involuntary Change of a Passenger s Journey 143. With no discussion, on a formal vote, Conference unanimously agreed to amend the provisions for the Absorption of Passenger Expenses in an involuntary rerouting situation, specifically the provision that if a carrier operating a domestic service causes the disruption then they may be absolved of any responsibility to reimburse the passenger. Amendments to IATA Resolution 735d are published in the book of finally adopted resolutions and RPs. There was no counterpart ATA proposal. T7 Amendments to Recommended Practice IATA Management proposed to amend Recommended Practice 1775 relating to the provision of hotel accommodation, meals and surface transport, by replacing references to the EEC with either the EU or the ECAA whichever was appropriate since the EEC no longer exists. Conference could not reach a conclusion and asked this item to be forwarded to the IATA Tariff Composite Conference and IATA Legal for review. Secretary note: IATA has discussed this internally and has concluded that all references to the EEC in the Passenger Services Conference Resolution Manual can be amended as an editorial to read EU. T8 Cabin Baggage Dimensions Disconnect between RP 1749 and Tariff Composite Resolutions 300/301 Precedence of Composite Resolutions vs. PSC Recommended Practice 145. IATA Management brought to the attention of Conference the fact there were differing cabin baggage dimensions noted between those published in Recommended Practice 1749 and the Tariff Composite Resolution 300/301 and asked Conference to determine which of these resolutions took precedence It was suggested that the Tariff Composite resolution overrides the provisions of the recommended practice. It was acknowledged, however, that this discrepancy was not helpful and that different carriers adopted different approaches to cabin baggage allowances. A Member noted that with respect to the United Kingdom there were even smaller baggage allowances and that it was extremely unhelpful to have the overall dimensions not exceeding 115cms remain in the Tariff Composite resolutions. It was concluded that this discussion should be forwarded to the Tariff Composite Baggage Working Group (TCBWG) for further review. ACTION: IATA TCBWG

263 28 T9 Deletion of Ticketing Instructions for Minimum Fare Checks 147. Conference unanimously agreed to the deletion of ticketing instructions related to fare calculation entries which are no longer required as a result of the deletion of the fare construction steps from the Tariff Composite Resolutions manual. Amendments to IATA Resolutions 720a and 722 are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions and and are published in Section II of the ATA Minutes. T10 Rescission of IATA Resolution 725d Automated Neutral MCO 148. With 12 IATA Members opposed the Chairperson declared this proposal to rescind IATA Resolution 725d defeated. This resolution relates to the issuance of the Automated Neutral Coupon by Coupon MCO known as the MD50 and is imprinted on OPATB2 paper ticket stock. Even though IATA has confirmed that the OPATB2 stock will no longer be available on/after 1 June 2008 Members had concerns about rescinding this resolution until the EMD is deployed in the marketplace. There was no counterpart ATA proposal. T11 Counterpart Changes to Matrices in Resolutions 722f, 722g and 722h as a result of Matrices Changes to Resolutions 725f and 725g 149. Conference unanimously agreed to amend the electronic ticketing matrices as a result of the adoption of agenda item T2.23/P. Amendments to IATA Resolutions 722f, 722g and 722h are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions and are published in Section II of the ATA Minutes. T12 2D Barcode to Store Ticketing Information on the Electronic Ticket Itinerary Receipts 150. Conference unanimously agreed to add a provision for the imprinting of a 2D bar code on the passenger itinerary receipt for electronic tickets in order for the self service devices to be able to read the ticketing information so that the customer does not need to enter this information manually. Amendments to IATA Resolutions 722f, 722g and 792 are published in the book of finally adopted resolutions and RPs. Counterpart amendments to ATA Resolutions and are published in Section II of the ATA Minutes.

264 29 T13 Code Designators for Passenger Ticket and Baggage Check Resolution This proposal submitted by a Member sought to add a series of new fare and passenger type codes that correspond more specifically to the complexity of the ticket being purchased with regard to ticket refunds and/or changes. IATA advised that should this proposal go forward that some of the codes could not be used because Resolution 728 prohibits the use of some of the alpha characters proposed in the position requested. This item was deferred to the Ticketing Committee for further review. ACTION: TICKETING COMMITTEE T14 Amendments to Resolution 735 Re-routing to Exchange 152. This item was submitted onsite by the Resolutions Advisory Panel to amend Resolution 735 to bring it line with the Tariff Composite manual. Noting 3 Members opposed, this item was declared defeated. RESERVATIONS R1 Report - ATA/IATA Reservations Committee (ResCom) 153. Conference noted this report and re-elected AF, BA and LH to the IATA Reservations Committee as shown in Attachment AA. R2 Report - Reservations Working Group (RESWG) 154. Conference noted the report and re-established the group for a further 12 months with a work plan shown in Attachment BB. R3 AIRIMP Editorials 155. Conference adopted a series of editorial changes to AIRIMP as shown in Attachment CC. Conference extended a vote of thanks to Mr Art Kourajian (Unisys) who had done a tremendous job in reviewing the AIRIMP manual Conference noted that there were still some remaining editorials to be addressed later in the year. Conference agreed that mail vote procedures could be used to attempt to include these change in time for the next edition of the AIRIMP manual effective 1 June ACTION: RESWG/ResCom

265 30 R4 Deletion of Incorrect Example in AIRIMP The Secretary provided on site minor changes to AIRIMP procedures regarding family names of a single letter, e.g. Mr U. Conference agreed with the changes as shown in Attachment DD to keep AIRIMP in line with changes agreed to ticketing resolutions (agenda item T2.25 refers). R5 Intentionally left blank R6/P Reservations Package 158. This package contained miscellaneous items that had been approved at Committee level with no opposition noted. Accordingly, agenda items R6.1/P through R6.17/P were unanimously adopted as proposed. Amendments to AIRIMP are shown in Attachments EE through RR. Counterpart amendments to SIPP (where appropriate) are shown in Section II of the ATA Minutes The PSC agreed to change Resolution 766 and RPs 1771, 1776, 1779 as shown in the book of finally adopted resolutions and RPs. R6.1/P AIRIMP Updates Items for Parking Lot 160. Conference agreed to various editorial amendments in AIRIMP to improve clarity and provide some examples to match the text as shown in Attachment EE. The ATA Passenger Council agreed to counterpart changes to SIPP Resolutions and as shown in Section II of the ATA Minutes. R6.2/P Clarification to AIRIMP System Cancel Message 161. Conference agreed to various editorial amendments in AIRIMP to improve clarity as shown in Attachment FF. The ATA Passenger Council agreed to counterpart changes to SIPP Resolution as shown in Section II of the ATA Minutes. R6.3/P Journey Data for Block Space 162. The PSC agreed to add a new element in RP 1779 to reflect an already existing data element in PADIS. Amendments to RP 1779 are shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council agreed to counterpart changes to SIPP Resolution as shown in Section II of the ATA Minutes.

266 31 R6.4/P AIRIMP format Section Conference agreed to various editorial amendments in AIRIMP to improve clarity as shown in Attachment GG. There were no counterpart changes to SIPP. R6.5/P Booking and Reduce Number in Party in One Booking Session 164. The PSC agreed to amend RP 1776 to provide guidelines for situations when there is a reduction in number of party for some, but not all, segments in a booking session. Amendments to RP 1776 are shown in the book of finally adopted resolutions and RPs. The ATA Passenger Council agreed to counterpart changes to SIPP Resolution as shown in Section II of the ATA Minutes. R6.6/P SSR CHLD Construction Rules 165. Conference agreed to amend the SSR CHLD construction rules in AIRIMP to clarify that only one child is allowed in each SSR as shown in Attachment HH. The ATA Passenger Council agreed to counterpart changes to SIPP Resolution as shown in Section II of the ATA Minutes. R6.7/P SSR CHLD Update 166. Conference agreed to amend AIRIMP in recognition that the OSI CHD standard will terminate on 31 May 2008 as shown in Attachment II. The ATA Passenger Council agreed to counterpart changes to SIPP Resolution as shown in Section II of the ATA Minutes. R6.8/P AIRIMP Editorial Conference agreed to various editorial amendments in AIRIMP to improve clarity as shown in Attachment JJ. There were no counterpart changes to SIPP. R6.9/P Editorial Change to AIRIMP Conference agreed to a minor editorial amendment in AIRIMP as shown in Attachment KK. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes.

267 32 R6.10/P Obtaining Reservations for Involuntary Rerouting 169. The PSC agreed to update Resolution 766 and RP 1771 to reflect changes adopted last year regarding involuntary rerouting. Amendments to Resolution 766 and RP 1771 are shown in the book of finally adopted resolutions and RPs. There were no counterpart changes to SIPP. R6.11/P Infant Date of Birth in SSR INFT 170. Conference agreed to amend AIRIMP to clarify the date of birth standards for infants as shown in Attachment LL. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes. R6.12/P JPTC Verbiage for ET Exchange 171. Conference agreed to amend AIRIMP to clarify procedures for ET exchange as shown in Attachment MM. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes. R6.13/P AIRIMP Description of SSR TKNR 172. Conference agreed to amend AIRIMP to clarify the description of SSR TKNR as shown in Attachment NN. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes. R6.14/P AIRIMP Reference to Plating Carrier 173. Conference agreed to amend AIRIMP to replace all references to Plating Carrier to Validating Carrier as shown in Attachment OO. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes. R6.15/P Code Share NRL Message Format 174. Conference agreed to amend AIRIMP to include a message format for code share NRL messages as shown in Attachment PP. R6.16/P Exchange of NRSA Messages in AIRIMP 175. Conference agreed to a new code in AIRIMP to allow carriers to exchange cancellation of meal listed or NRSA type space as shown in Attachment QQ. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes.

268 33 R6.17/P New Seat Location Code 176. Conference agreed to amend AIRIMP to indicate an exit row seat in a seat request or sell as shown in Attachment RR. The ATA Passenger Council agreed to counterpart changes to SIPP as shown in Section II of the ATA Minutes. MISCELLANEOUS M1 Report - PSC Steering Group (PSCSG) 177. Conference noted this report. M1.1 Airport & Inflight Services Structure 178. The PSC agreed in principle that the Inflight Services Committee should report to the PSC. Regarding the proposed structure of task forces and working groups, it was agreed that this would be studied in more detail by the PSC Steering Group. ACTION: PSCSG M2 Report - PADIS Board (PADIS) 179. Conference noted this report that highlighted the first version release of XML schemas (I.e. messages). It was advised that private pages for XML schemas and Type X messages had been set up under the PADIS extranet site: Conference agreed to establish a Type X Technical Working Group with terms of reference as shown in Attachment SS. M3 Report - Cargo Services Conference (CSC) 181. Conference noted this report. M3.1 Third Party Logistics Companies New 3PL Code 182. Conference noted this report. M4 Report Scheduling Services 183. Conference noted this report.

269 34 M4.1 Report - Schedules Information Standards Committee (SISC) 184. Conference noted this report. M4.2 Interline Connecting Time Intervals Passenger and Checked Baggage - Resolution The Secretary had proposed changes to Resolution 765 to align it with current practices. However, the PSC was not prepared to address this item until it had been reviewed and endorsed by the SISC. ACTION: SISC M5 Report Fraud Prevention Working Group (FPWG) 186. The Chairman reported that the FPWG had undergone radical change since the JPSC in In view that most of the reported fraud on tickets was still focussed on paper tickets, IATA had devolved day-to-day fraud action to the local and regional level where IATA staff were being provided with tools and training (e.g. blacklisting) It was noted that Mr Scott McIntosh (UA) is the new FPWG Chairman and its Secretary is Mr Dave McEwen. The Chairman wished to record her thanks to Mr Pierre Briant of IATA who had been IATA s valued central source for fraud issues over several years The Tickets Service Steering Group (TSSG) had concluded that IATA would not need to blacklist BSP tickets that had been destroyed after 1 June However the TSSG did recommend that an audit be performed to look for gaps between reported destruction and what IATA believes should have been the remaining agent stock. Such gaps should be blacklisted by IATA. ACTION: IATA 189. The TSSG recommended changes to Resolution 781a to address the issue of BSP tickets that may erroneously (or fraudulently) been issued after 1 June Noting opposition from two airlines, the Chairman directed the Ticketing Committee and the Passenger Agency Conference (PAConf) to address this issue before returning the proposal to Conference. ACTION: JPTC/PAConf M6 Report BSP Data Interchange Standards Group (BDISG) 190. Conference noted this report.

270 35 M7 Report Strategic Partnerships 191. Conference noted this report. M8 Report Dot Aero 192. Conference noted this report. M9 Report Dot Travel 193. Conference noted this report. M10 Report ZED-MIBA Forum 194. Conference noted this report. M10.1 Staff Travel Secretary note: following the close of meeting, several airlines held informal discussions regarding the viability of a single industry recommendation regarding interline staff travel procedures. The conclusion was that certain airlines had already chosen divergent methods of dealing with staff travel for their interline partners. Consequently there was no consensus on how to move forward, recognising that some airline had already invested considerable sums in their own systems or third party systems. M11 Report Tariff Composite Interline Baggage Working Group 195. Conference noted this report. Close of Meeting 196. With no other items to address, the Chairman closed the meeting at hours.

271 Attachment A ATTENDANCE LIST 27th JOINT IATA/IATA PASSENGER SERVICES CONFERENCE (JPSC) 29th IATA PASSENGER SERVICES CONFERENCE (PSC) TORONTO, 9-10 OCTOBER Organisation (Country) Name Title 1. Air Canada Ellen Lageveen Manager Airport Processes, & Product Development 2. Air Canada Craig Milner Manager, Product Development - Airport Technology 3. Air France Patricia George Industry Affairs (Chairman) 4. Air France Hugo Rousset Fare Quote & Customers Data Tools Manager 5. Air France Stéphane Vanovermeir New Distribution Process Manager Telephone / Fax Alaska Airlines Sharla Gibson Manager, Technology Development Aloha Airlines Michael Coffman Sr. Vice President Airline Operations Aloha Airlines Inc Alitalia Flavio Ghiringhelli Distribution Director Alitalia Nicoletta Ceci GDS Affairs Alitalia Luigi Orrù GDS Affairs Manager Air Transport Association Patty Edwards Managing Director, Passenger Services Air Transport Association Jim Casey Vice President, Industry Services and Deputy General Counsel All Nippon Airways Takashi Imabayashi Deputy Director All Nippon Airways Sawako Oda Assistant Manager, Procedures & Regulations 15. All Nippon Airways Kuniko Miyazaki Assistant Manager of Procedures & Regulations ellen.lageveen@aircanada.ca craig.milner@aircanada.ca pageorge@airfrance.fr hurousset@airfrance.fr stvanovermeir@airfrance.fr sharla.gibson@alaskaair.com mcoffman@alohaairlines.com ghiringhelli.flavio@alitalia.it ceci.nicoletta@alitalia.it orru.luigi@alitalia.it pedwards@airlines.org jcasey@airlines.org waka@ana.co.jp s.oda@ana.co.jp ku.miyazaki@ana.co.jp. S:\JPSC_07\Minutes\JPSC 2007 Minutes Attachement A.doc 1 08-Feb-2008

272 Organisation (Country) Name Title 16. All Nippon Airways Taku Hashimoto Passenger Services Planning Operations & Airport Services Telephone / Fax tak.hashimoto@ana.co.jp Attachment A 17. Amadeus Santiago Iglesias Manager, Ticketing siglesias-lucas@amadeus.com Amadeus Cayetano Damas Product Strategist cdamasalcala@amadeus.com 19. Amadeus Stephen Corking Global Core A Airline Reservation Services 20. Amsterdam Airport Schiphol Mark van Gaalen Principal Consultant scorking@amadeus.com gaalen@schiphol.nl 21. American Airlines Anne Champney Manager Airport Services Airlines Reporting Keith Venzke Senior Manager, Industry Corporation Standards & Settlement Plan Mgt Airlines Reporting Corporation Les Tucker Senior Manager Accreditation & Agency Training 24. ATPCO David Smith Product Specialist Product Marketing & Development anne.champney@aa.com kvenzke@arccorp.com ltucker@arccorp.com dsmith@atpco.net 25. ATPCO Carrie Demoss Manager, Industry Solutions cdemoss@atpco.net Austrian Airlines Renate Lukasek Manager Passenger Handling renate.lukasek@austrian.com Procedures Austrian Airlines Marcus Lenk Head of Reservations & Ticketing marcus.lenk@austrian.com Methods & Support Axess Int. Network Inc. Tomoko Igawa Senior Manager, Product Planning igawa.tomoko@axess.co.jp BPS, LLC (TSA) Anthony (Buzz) Cerino BPS\TSA Technical bpsllc@comcast.net Representative British Airways Martin Ryan Manager, Industry Affairs +44 (0) martin.ryan@ba.com +44 (0) British Airways Jane Watkins Senior Project Executive +44 (0) jane.watkins@ba.com Electronic Ticketing 32. British Airways Steve Drake Senior Project Executive +44 (0) steve.drake@ba.com +44 (0) Brock Solutions Mark Stokes Manager IT Projects x 108 mstokes@brocksolutions.com Continental Airlines Craig Thomas Senior Manager, Airport Services Technology cthoma@coair.com 35. Continental Airlines Kathy Ellis Manager Airport Administration Field Services kellis@coair.com S:\JPSC_07\Minutes\JPSC 2007 Minutes Attachement A.doc 2 08-Feb-2008

273 Organisation (Country) Name Title Telephone / Fax 36. Continental Micronesia Desmond Fullerton Senior Manager, Technology Croatia Airlines Ivana Janusic Customer Relations Manager Czech Airlines Michal Hajek Regulations Specialist Czech Airlines Robert Cerny Operational Regulations & Standards Director Delta Air Lines Peggy Kessler General Manager, Industry Affairs Delta Air Lines Linda Cappelletti Analyst, Interline & Industry Affairs Delta Air Lines Len Blalock Project Manager, Electronic Ticketing Delta Air Lines Lorraine Marchetti Manager, Baggage Delta Air Lines Steve Jensen Manager, Interline & Industry Affairs DFW Dallas/Fort Worth International Airport 46. EDS Information Business GmbH Theresa Weiss Terminal System Coordinator Lucia Gerber Product Manager Airline Reservation Systems & Electronic Fares Services 47. Egyptair Nahed Hassan Manager Industry Affairs Emirates Richard Pearl Industry Affairs Superintendent Passenger & Cargo 49. Finnair Marko Haaksiala Manager, Passenger & Baggage Procedures Ground Operations 50. Galileo International Andrew Greskovich Product Specialist - Application Support Services 51. IATA Michael Feldman Director, Passenger (Secretary) 52. IATA Mike Muller Assistant Director, Passenger Services 53. IATA David McEwen Manager, Ticketing Services & Fraud Prevention 54. IATA Yngvar Sundsfjord Manager, Reservations & Ticketing Standards des.fullerton@coair.com Attachment A ivana.janusic@croatiaairlines.hr michal.hajek@csa.cz robert.cerny@csa.cz peggy.kessler@delta.com linda.a.cappelletti@delta.com len.blalock@delta.com lorraine.marchetti@delta.com steve.jensen@delta.com tweiss@dfwairport.com lucia.gerber@eds.com nahedh@egyptair.com.eg richard.pearl@emirates.com marko.haaksiala@finnair.com andrew.greskovich@galileo.com feldmanm@iata.org mullerm@iata.org mcewend@iata.org sundsfjory@iata.org S:\JPSC_07\Minutes\JPSC 2007 Minutes Attachement A.doc 3 08-Feb-2008

274 Organisation (Country) Name Title Telephone / Fax 55. IATA Colin Flynn Senior Legal Counsel IATA Chris Miles Manager Airport & Inflight Services 57. IATA Benoit Pilon Manager Airport & Inflight Services IATA Laetitia Neuhaus Assistant, Passenger Services Iberia Mary Jo Reviejo Project Co-ordination & Industry Relations Icelandair Björn Olafsson Project Manager, Customer Services 61. Infini Travel Information, Inc. 62. Infini Travel Information, Inc Mayumi Okazaki Manager, Product Planning Group Masahiro Sumimoto Senior Executive, Product Planning Group ITA Software Inc. Eric E. Atotubo Travel Industry Specialist Japan Airlines Ross Leggett Director, Procedures Planning International Sales Planning & Marketing 65. JAT Airways Dusica Stankovic Manager Passenger Fares KLM Royal Dutch Airlines Johan Lodewijckx Manager IATA & Industry Affairs KLM Royal Dutch Airlines Gemma Winnubst Functional Application Manager Lan Airlines S.A. Silvana Moletto Commercial Procedures Manager Las Vegas McCarran Int. Samuel Ingalls Assistant Director of Aviation, Airport Information Systems LOT Polish Airlines Beata Knobelsdorf-Kocepup IATA Rules & Regulations Adviser Lufthansa Gisela Golombowski-Hofmann Manager Revenue Integrity Fraud Prevention +49 (0) (0) Attachment A flynnc@iata.org milesc@iata.org pilonb@iata.org neuhausl@iata.org mjreviejo@iberia.es bao@icelandair.is okazaki0123@infini-trvl.co.jp sumimoto0239@infini-trvl.co.jp erica@itasoftware.com ross.leggett@jal.com stankovicdusica@jat.com johan.lodewijckx@klm.com gemma.winnubst@klm.com silvana.moletto@lan.com sami@mccarran.com b.knobelsdorf-kocepup@lot.pl gisela.hofmann@dlh.de 72. Lufthansa Michelle Bryant Manager, Distribution & IATA Industry Affairs 73. Lufthansa Danjela Janke Project Manager Global Ground Processes +49 (0) (0) (0) (0) michelle.bryant@dlh.de danjela.janke@dlh.de S:\JPSC_07\Minutes\JPSC 2007 Minutes Attachement A.doc 4 08-Feb-2008

275 Organisation (Country) Name Title 74. Malaysia Airlines Yusop Jaridi General Manager Airport Operations 75. Malaysia Airlines Sabiah Ismail Manager Standards & Procedures, Airport Operations 76. Middle East Airlines Salim Kharrat In Charge of Agency & Procedures / Cargo Tarrifs Industry Affairs 77. Northwest Airlines Stephen Mahon Senior Specialist, Customer Service Telephone / Fax Attachment A yusopj@mas.com.my sabiah@mas.com.my kharrats@mea.com.lb stephen.mahon@nwa.com 78. Northwest Airlines Dawn Jetchick Senior Business Analyst dawn.jetchick@nwa.com 79. Qantas Airways Dayle Vaughan Agency Program Manager daylevaughan@qantas.com.au Sabre Holdings Roger Hawkins Industry Affairs Director +44 (0) roger.hawkins@sabre.com +44 (0) Scandinavian Airlines Anita Sundén Manager Industry Affairs anita.sunden@sas.se System Siemens Heinz-Peter Peters Industry Manager Transportation +49 (911) heinz-peter.peters@siemens.com & Logistics +49 (911) SITA Adrianna Colbath Senior Business adrianna.colbath@sita.aero Consultant SITA Larry Kretz SITA Airport and Desktop larry.kretz@sita.aero Services 85. Southwest Airlines Co. Pamela Graham Director, Ticketing Services pam.graham@wnco.com 86. Swiss Patrick Graf Senior Manager, Head of Revenue Management Solutions & Distribution patrick.graf@swiss.com 87. Swiss Patrick Schmid Passenger Handling Policies patrick.schmid@swiss.com TACA Evelyn Bolaños Training Analyst lbolanos@taca.com TAP Portugal Mario Soares Manager, Reservations & DCS msoares@tap.pt Systems TAP Portugal Alfredo Pedro Manager, Customer Services fpedro@tap.pt 91. Thai Airways Ratree Kham-Iam Commercial Procedure Department Manager 92. Thai Airways Napassawan Boon-Long Manager, Reservation & Ticketing System Service Division 93. Turkish Airlines Kübra Eroğlu-Bingöl IATA Ticketing Regulation Specialist 94. Turkish Airlines Emine Yücel Manager IATA Ticketing & Regulations S:\JPSC_07\Minutes\JPSC 2007 Minutes Attachement A.doc / ratree.k@thaiairways.com napassawan.b@thaiairways.com keroglubingol@thy.com eyucel@thy.com 08-Feb-2008

276 Organisation (Country) Name Title Telephone / Fax 95. Turkish Airlines Sacide Hiziroglu IT Programmer Unisys Arthur Kourajian Manager Airline Industry United Airlines Rosalie Crabbe Project Manager Partnerships & International Planning US Airways Teri Martin Sr. Analyst Airport Services, International Virgin Atlantic Airways Andrew Biggin Head of Commercial Systems +44 (0) Ltd. +44 (0) Worldspan James Erickson Product Strategist Zebra Technologies Corporation John Fini Air Transport Business Development Manager Attachment A shiziroglu@thy.com arthur.kourajian@unisys.com rosalie.crabbe@united.com teri.martin@usairways.com andrew.biggin@fly.virgin.com jim.erickson@travelport.com jfini@zebra.com S:\JPSC_07\Minutes\JPSC 2007 Minutes Attachement A.doc 6 08-Feb-2008

277 Passenger Week At a Glance Geneva, October 2008 Attachment: B Mon, 6 Oct Tue, 7 Oct Wed, 8 Oct Thu, 9 Oct Fri, 10 Oct PSG PACONF PSC PSC COMPOSITE PACONF COMPOSITE PSC agenda review meeting COMPOSITE PSG Version 1.4

278 JPSC/27 PSC/29 Oct 07 Attachment: C Page: 1 of 2 IATA Airline Coding Directory Section 7 Auxiliary Codes Auxiliary codes are used for communications purposes only and such codes designate the type of service the customer provides. These codes are defined in IATA Resolution 762 as follows: Code CR HL XD XH 7X 8X Commercial Category Car Rental /Miscellaneous Hotel/Motel Airline Industry Functions Ground Handling Service Miscellaneous Miscellaneous Construction of a unique teletype address Auxiliary codes are used in positions 6 and 7 of a seven-character teletype address, for example MIAALCR is for Alamo rent a car company based in Miami. Positions 1-3 designate the geographical location based on location identifier codes per IATA Resolution 763. In some cases the generic code HDQ is used to specify the company headquarters. Positions 4 and 5 designate the office function designator which could indicate a specific department within a company. Assignment of a teletype address Assignment of a teletype address using auxiliary codes is made by: Air Transport Association of America 1301 Pennsylvania Avenue N.W. Washington, D.C USA Teletype: WASCHXD bbley@airlines.org Requests for a teletype address should be made using the application form in Attachment D or in a similar format if made by teletype.

279 JPSC/27 PSC/29 Oct 07 Attachment: C Page: 2 ASSIGNMENT OF TELETYPE ADRESS FOR COMMUNICATIONS PURPOSES To be submitted to: a) for ARINC customers: gsiscoe@arinc.com or b) for SITA customers: messaging.ordering.support@sita.aero or c) for others: bbley@airlines.org APPLICATION FORM For Teletype Address Based on Auxiliary Codes 7X, 8X, CR, HL, XH, XD (Type or print in block letters) Customer Name: Street Address: Post Office Box Number: City: State/Province: Country: Postal/Zip Code: Contact Name: Title: Date: Request: Communications (indicate which is applicable) ARINC SITA Other Date of Entry: Type of Organization (briefly describe your operation)

280 JPSC/27 PSC/29 Oct 07 Attachment: D Page: 1 of 1 TERMS OF REFERENCE Location Identifier Working Group (LIWG) The Location Identifier Working Group is established by the JPSC to: Review proposed changes to location identifiers for Areas TC1 and TC2; Reach agreement on: editorial changes to correct the spelling of location names consolidation of city names/codes deletion of city names/codes rationalisation of metropolitan areas review of railway stations as part of metropolitan areas Develop implementation timetable; Coordinate with industry data suppliers, e.g. ATPCO, Innovata, OAG, SITA, etc.; Develop industry guidelines for sourcing the correct spelling of names for location identifiers; Propose appropriate improvements to Resolution 763; Consist of representatives from interested organisations including the UN, ACI, members of IATA s Strategic Partners programme and ATA/IATA airlines with expertise of reservations, cargo, tariffs, ticketing DCS and SISC; Report progress to the JPSC including a recommendation for action regarding the database for TC3.

281 JPSC/27 PSC/29 Oct 07 Attachment: E Page: 1 of 4 NEW TAX CODES CODE NAME COUNTRY REQUESTED BY DATE PURPOSE / DETAILS -JK- DEPARTURE FEE FOR EGYPT EGYPT EGYPTAIR 08/11/06 GOVERNMENT TAX ON DEPARTING PASSENGERS. -JG- PASSENGER SERVICE CHARGE BARBADOS AMERICAN AIRLINES 14/11/06 COST FOR PROCESSING DEPARTING PASSENGERS AT BGI. -JH- SECURITY FEE BARBADOS AMERICAN AIRLILNES 14/11/06 SECURITY SCREENING OF DEPARTING PASSENGERS CARRY-ON LUGGAGE & CHECKED LUGGAGE AT GRANTLEY ADAMS INTERNATIONAL AIRPORT (BGI). -TA- PASSENGER SERVICE CHARGE FOR KOH SAMUI, TRAT AND SUKHOTHAI AIRPORTS THAILAND BANGKOK AIRWAYS CO. LTD, 15/11/06 FOR THE PROVISION OF PASSENGER SERVICE FACILITIES AT KOH SAMUI, TRAT & SUKHOTHAI. -JF- CONCOURSE FEE GRENADA BRITISH AIRWAYS 15/11/06 TO COVER CHARGES FOR INTRODUCTION OF CUTE (COMMON USE TERMINAL EQUIPMENT) AND OTHER AIRPORT INFRASTRUCTURAL DEVELOPMENTS AT POINT SALINES INTERNATIONAL AIRPORT. (GND) -JI- -JJ- AIR PASSENGER SERVICE CHARGE (APSC) SECURITY FEE AT LJUBLJANA AIRPORT ZAMBIA KENYA AIRWAYS 11/12/06 FOR THE PROVISION & DEVELOPMENT OF PASSENGER AIRPORT FACILITIES. SLOVENIA ADRIA AIRWAYS 14/12/06 COST OF PERFORMING THE SECURITY SERVICE AT THE AIRPORT.

282 JPSC/27 PSC/29 Oct 07 Attachment: E Page: 2 -JN- TAX CODE FOR SERVICE TAX ON FIRST & BUSINESS CLASS TRAVEL FOR TRAVEL EX INDIA INDIA AIR-INDIA LIMITED 19/12/06 REQUIREMENTS OF THE INDIAN GOVERNMENT MINISTRY OF FINANCE TO IMPOSE A SERVICE TAX ON INTERNATIONAL TRAVEL FOR FIRST AND BUSINESS CLASS TRAVEL FROM INDIA ACCORDING TO THE BUDGET STATEMENT FEBRUARY JQ- SECURITY CHARGE MOLDOVA AIR MOLDOVA 10/01/07 SECURITY. -JL- -JU- AZERBAIJAN FLIGHT SECURITY TAX AIR PASSENGER SOLIDARITY TAX AZERBAIJAN AZERBAIJAN AIRLINES 16/01/07 ENHANCED FLIGHT SECURITY LEVEL REQUIREMENTS. BENIN AIR FRANCE 19/03/07 CONTRIBUTION TO WORLDWIDE SOLIDARITY AID FOR DEVELOPMENT IN UNDER DEVELOPED COUNTRIES. -JX- PASSENGER SERVICE CHARGE CYPRUS CYPRUS AIRWAYS PUBLIC LTD. 21/03/07 PASSENGER SERVICE CHARGE AT LARNACA AND PAFOS AIRPORTS. -JW- SECURITY CHARGE CYPRUS CYPRUS AIRWAYS PUBLIC LTD. -ME- DEPARTURE TAX FROM TIVAT (TIV) AND PODGORICA (TGD) AIRPORTS MONTENEGRO MONTENEGRO AIRLINES -JV- SOLIDARITY TAX MADAGASCAR AIR MADAGASCAR 21/03/07 PROVIDE SECURITY MEASURES AT AIRPORTS IN CYPRUS. 13/04/07 DEPARTURE FEES. 16/04/07 PARTICIPATION OF MADAGASCAR IN THE UNITAID TO FIGHT AGAINST HIV/AIDS, MALARIA AND TUBERCULOSIS. -JR- SOLIDARITY TAX NIGER AIR FRANCE 20/04/07 LEVIED ON PASSENGERS DEPARTING ON DOMESTIC & INTERNATIONAL FLIGHTS TO ASSIST THE STRUGGLE AGAINST POVERTY IN UNDER DEVELOPED COUNTRIES. -JY- VALUE ADDED TAX NIGERIA VIRGIN NIGERIA 24/04/07 VAT ON DOMESTIC FLIGHTS. -GF- EMBARKATION TAX FRENCH GUIANA AIR FRANCE 24/04/07 TO FACILITATE AIRLINE INDUSTRY IN FRENCH GUIANA. -JZ- STAMP TAX NIGER AIR FRANCE 26/04/07 TO DEVELOP AIRPORT FACILITIES. -IW- AIRPORT IMPROVEMENT FEE NETHERLANDS ANTILLES US AIRWAYS, INC. 09/05/07 TO HELP MEET THE INCREASE IN FINANCIAL OBLIGATIONS AS A RESULT OF INVESTMENTS TO IMPROVE THE AIRPORT INFRASTRUCTURE.

283 JPSC/27 PSC/29 Oct 07 Attachment: E Page: 3 -KA- FLIGHT SECURITY CHARGE KOREA, DEMOCRATIC PEOPLE S REPUBLIC OF AIR KORYO 29/05/07 TO ENSURE SAFETY OF STATE & PASSENGER IN THE OPERATION OF THE INTL. FLIGHTS AND TO RAISE MATERIAL AND TECHNICAL STANDARD OF NEWLY ORGANIZED CIVIL AVIATION SECURITY AGENCY. -KP- PASSENGER SERVICE CHARGE KOREA, DEMOCRATIC PEOPLE S REPUBLIC OF AIR KORYO 30/05/07 DEVELOPMENT OF ALL FACILITIES IN PYONGYANG INT. AIRPORT TO PROVIDE PASSENGERS WITH SAFE & SIMPLIFIED GROUND HANDLING SERVICES. -JS- TOURISM TAX COLOMBIA AVIANCA 01/06/07 CONTRIBUTION FOR THE PROMOTION AND INVESTMENT IN THE COMPETITIVENESS OF TOURISM IN COLOMBIA. -TM- PASSENGER AIRPORT TAX INT. TURKMENISTAN TURKMENISTAN AIRLINES 14/06/07 STATE TAX -KB- DEVELOPMENT LEVY GAMBIA DAT, TRADING AS BRUSSELS AIRLINES 06/07/07 TO PROMOTE, MARKET AND DEVELOP THE TOURISM PRODUCT. -KK- PASSENGER SERVICE CHARGE (PSC) NEW ZEALAND AIR NEW ZEALAND 31/07/07 PROVISION OF PASSENGER SERVICES AT AUCKLAND AIRPORT. -KJ- CIVIL AVIATION FEE TRANSIT PASSENGERS JORDAN ROYAL JORDANIAN 14/08/07 TRANSFER PASSENGER FEE IMPOSED BY JORDAN CIVIL AVIATION. -TO- SECURITY LEVY & AIRPORT DEVELOPMENT CHARGE TONGA AIR NEW ZEALAND 17/08/07 TO COVER THE COSTS OF AVIATION SECURITY, PASSENGER FACILITATION, TERMINAL AND INFRASTRUCTURE MAINTENANCE & IMPROVEMENTS.

284 JPSC/27 PSC/29 Oct 07 Attachment: E Page: 4 CODE NAME COUNTRY REQUESTED BY DATE PURPOSE / DETAILS -KF- VALUE ADDED TAX EQUATORIAL GUINEA AIR FRANCE 24/08/07 THE VAT IS APPLICABLE TO ALL PASSENGERS DEPARTING FROM GQ (EQUATORIAL GUINEA) WITH TICKETS SOLD/ISSUED IN GQ REGARDLESS OF TRAVEL AND TYPE OF FARE. -UG- SECURITY CHARGE UGANDA SN BRUSSELS AIRLINES (DELTA AIR TRANSPORT DBA SN BRUSSELS AIRLINES) 10/09/07 CONTRIBUTION TOWARDS SEVERAL SECURITY EXPENSES. -KL- VALUE ADDED TAX ESTONIA ESTONIAN AIR 12/09/07 A VAT OF 18PCT HAS TO BE COLLECTED ON ALL TICKETS, MCO'S AND PTA'S FOR TRAVEL WITHIN ESTONIA AS WELL AS FOR DOMESTIC TRAVEL IN CONNECTION WITH INTERNATIONAL TRAVEL. -KQ- CIVIL AVIATION CHARGE SENEGAL AIR SENEGAL INTERNATIONAL 14/09/07 ENHANCE CAPACITY OF CIVIL AVIATION. -KO- TERRITORIAL DEVELOPMENT TAX HAITI AMERICAN AIRLINES 18/09/07 CONTRIBUTION TO THE FUNDS AND MANAGEMENT OF TERRITORIAL DEVELOPMENT. (CFGCDT) Secretary note: the above-mentioned codes are published in the IATA Airline Coding Directory

285 JPSC/27 PSC/29 Oct 07 Attachment: F Page: 1 of 8 Electronic Ticketing and Other Documents in BSPs on/after 1 June 2008 Dear BSP participating airline, You will be aware that the IATA Annual General Meeting set a deadline of eliminating paper tickets from our BSPs at the end of this year. This deadline was subsequently extended to 31 May 2008 to provide airlines with more time to complete their work. This is the final deadline and there will be no further extensions. What does this mean for you as a BSP airline user? Very simply - on 1 June 2008, IATA will withdraw all paper ticket stock from the BSPs and you will either have to use BSP Electronic Tickets, or provide agents with an alternative method of using your own paper ticket stock. We are working very closely with the Global Distribution System providers (GDSs) to ensure a smooth cutover to ET, but each GDS is handling the cutover in a different way and we would therefore urge you to liaise with the GDSs so they fully understand your plans. We appreciate that the BSPs also handle 3rd party users such as railways and we are working on solutions to accommodate this type of business. We are receiving many enquiries on the cutover to ET and have therefore developed the attached summary sheet of key issues which provides more information on topics such as: Specific actions required on the part of BSP participating airlines Use of the V-MPD and EMD by BSP participating airlines Consequences if an agent issues a neutral paper ticket on/after 1 June 2008 Status of Neutral Ticket Stock Global Stock Recovery Impact of the Elimination of Neutral Paper Tickets on 3 rd Parties in the BSP Acceptance of neutral paper tickets issued prior to 1 June 2008 Other consequences for interline itineraries I encourage you to circulate the attached summary sheet widely in your companies for information and action. Should you have any questions or comments please forward these by to: eticket@iata.org Yours sincerely,

286 Summary Sheet of Key Issues for Airlines Electronic Ticketing and Other Documents in BSP on/after 1 June Specific actions required on the part of BSP participating airlines Each BSP participating airline must inform their appointed agents that on/after 1 June 2008 paper tickets must not be issued on the BSP neutral paper ticket stock using your airline accounting code. Such action must be done in writing and addressed to each appointed Agent in each concerned BSP. BSP participating airlines must communicate to their agents their procedures for interline itineraries that are not eligible for ticketing on an electronic ticket. The options include, but are not limited to the following: 1. Issuance of another document in the form of a Virtual MPD (V-MPD) which airlines may wish to use to follow their internal PTA process. Airlines need to ensure that they continue to have interline agreements in place that permit paper ticketing. 2. Through local arrangements, the agent may request the ticket to be issued by the airline on its own paper ticket stock. This is a ticketing solution that may be provided by an airline but is not mandated by any IATA rule or procedure. 3. Where an airline elects, it may place its own paper ticket stock in an agent location and ticketing may be done on that stock. In this instance the entire transaction is subject to the bilateral agreement between the airline and the agent. These transactions are outside the IATA Agency Programme and the BSP administrative rules including default procedures and reporting and remittance schedules. 2. Use of the V-MPD and EMD by BSP Participating Airlines Whilst Members have already adopted standards for an Electronic Miscellaneous Document (EMD) that will replace all other non-ticket documents, it is not anticipated that this will be fully available for use until 2009 at the earliest. During the interim period all other documents can be issued by means of a virtual version of the MPD known as the V-MPD. Airlines should therefore ensure that all of their offices are familiar with the V-MPD process and the actions they will need follow upon receipt. On/after 1 June 2008 the value coupon of the OPATB2 coupon-by-coupon MCO (known as the MD50) will no longer be available for the issuance of MCOs. IATA will monitor and evaluate the use of all other paper documents including the manual paper carbonised Multiple Purpose Document (MPD), the automated neutral carbonised MPD and the neutral carbonised excess baggage ticket in those markets where they are still distributed. Where these documents are currently used in a BSP, IATA will maintain their availability and will process any sales. BSP best practice is for the elimination of these documents as soon as possible in consultation with the BSP airlines. The IATA Country Manager will work with the BSP airlines to expedite the removing of all other paper documents and closing any remaining local data processing centres as endorsed by the IATA Settlement Systems Advisory Committee (ISSAC).

287 Overview of the V-MPD The V-MPD is: - A virtual representation of the paper MPD/auto MCO; An instrument of exchange; A record of a transaction of payment for a service or collection of a fee; Issued in BSPlink; Drop down menu boxes look like a manual document; Originally using the manual document form code delivering a short record; Now enhanced with its own unique form code (180), transaction type (MV50); and added features (now a SLR) similar to MD50 (airline option); message upon completion to the airline service point; Airlines see their copy and act in accordance with their standard internal procedures for processing Prepaid Ticket Advices (PTAs). It should be noted that IATA is continuing to examine additional functionality that meets the needs of travel agents and airlines in order to minimise disruptions to agency and airline operations and welcomes feedback and comment. The V-MPD is a viable alternative to paper MPDs and is available globally for airlines to deploy market by market. Airlines should liaise with their local BSP office to ensure that the V-MPD function is available in BSPlink in the BSPs in which they participate. IATA has prepared presentation material, user guides and a list of Frequent Asked Questions (FAQs) that are available for download in the Download Centre of the BSPlink Portal at (refer to BSPlink Customer Manuals ) Effect on Travel Agents Ticket Issuance It is expected that PTAs and tickets on departure will continue to decrease rapidly whilst airlines continue to expand their electronic ticketing capabilities. However, there may be some tickets that agents will be unable to issue as electronic tickets and, on/after 1 June 2008, will no longer have the fallback of issuing a paper ticket. Some of the reasons for this could be identified as follows (depending on individual airline policy): Interline journeys where the particular mix of Marketing/Operating Carriers does not allow one carrier to be selected as the Validating Carrier because no one carrier has IET with all other carriers; Passive bookings; Groups; Journeys over 16 segments; Infants; Open segments; Ineligible sectors because the ground-handling infrastructure at some airports is not capable of processing electronic tickets. Should an airline choose to maintain its own paper tickets, such paper tickets can still be issued for these journeys at their own offices. Airlines should communicate their procedures to their travel agents.

288 Effect on Travel Agents Other Documents IATA anticipates that the main reasons for agents to issue other documents will relate to the receipt for amendment fees and for issuance of non-air services (e.g. tours, hotel, car hire) where an interline electronic ticket agreement is not in place. The EMD will be the ideal solution to support the issuance of other documents. However there will be an interim period during which no EMD solution will be available and as such it will be necessary to maintain alternative methods of issuing other documents. IATA has deployed the V-MPD but, acknowledging that there will not be a value coupon produced, this will add an additional burden to airline resources where a value coupon is required. It should be noted that the V-MPD should only be seen as an interim measure until such time as the EMD is fully deployed. An industry oversight group has been set up by IATA to ensure that the first phase of the EMD implementation is in production as soon as is practicable. Currently some travel agents receive data supplied by their GDS from miscellaneous transactions to manage back office functions. In addition some GDS, but not all, have a certain level of interactivity into the Passenger Name Record (PNR). The problem however is that, looking at the V-MPD, there is a deficiency since a value or exchange coupon is not produced and there are no automatic updates into the PNR. It is therefore important for airlines to develop procedures to deal with this. An airline may wish to ensure that, upon receipt of an V-MPD for an amendment fee, it is confirmed to the check-in agent through a Special Service Request (SSR) or Other Services Information (OSI) placed into the PNR and passed to the check-in system through the Passenger Name List (PNL). Airlines may also wish to ensure their customers receive valid documentation for non-air services. Airlines should communicate their procedures to their travel agents. Agents should be encouraged to input the prepaid information into the GDS PNR and queue the booking to the airline for servicing following the standard procedures that applied for paper documents. Should a GDS wish to develop the functionality to suppress printing the value coupon for the existing MD50 product for their customers, IATA will support this by continuing to allocate number ranges for this purpose and (should they be required) Stock Control Numbers (SCNs). IATA however will not collectively ask the GDSs to develop such a product since the Passenger Services Conference has determined that resources should not be diverted away from the industry solution EMD. However, IATA is evaluating whether it will be in a position to source the OPATB2 blank magnetic-stripe encoded card should it be requested. Any costs that IATA would incur for the procurement and distribution of blank cards would be borne by the requesting party.

289 Effect on Travel Agents Remote Ticketing Facilities. With the withdrawal of paper ticket stocks, travel agent use of Satellite Ticket Printers (STPs) will no longer be supported. As a consequence of the electronic ticketing deadline, it has been agreed that all related resolutions providing for Satellite Ticket Delivery Offices (STDOs), Special Event Locations (SELs), European Union Satellite Ticket Printers (EUSTPs) and Satellite Ticket Printers will no longer be applicable on/after 1 June A travel agent operating an approved STP, EUSTP, SEL or STDO and in possession of a valid IATA numeric code for such operation will be entitled to retain such IATA code for At the end of 2008 IATA will not process any renewal application for any of these ticketing facilities as an STP, EUSTP, STDO or SEL. Should a travel agent wish to convert any of these locations to another category of IATA sales location this can be done at any time. Any conversion will be assessed as per applicable IATA resolution requirements and against the fees paid. 3. Consequences if an agent issues a neutral paper ticket on/after 1 June 2008 Inevitably some agents may hold residual paper ticket stock on/after 1 June 2008 if not yet destroyed. It is possible that a GDS may not yet have inhibited the use of that stock to produce a paper ticket after that date. If a neutral paper ticket is erroneously issued on/after 1 June, it will not be accepted for normal sales reporting and travel. The following should be noted: - 1. The IATA systems will be adjusted to reject a BSP reported sale where a paper ticket has been erroneously issued on/after 1 June This will result in the transaction not being reported to the issuing airline in the standard reporting process and will be classified in the BSP as an unreported sale by the agent. 2. As this erroneous sale will be unreported in the BSP, the ticket will not be shown on the BSP Billing Statement and as a result, the airline will not be paid for the ticket through the BSP. 3. A passenger holding such a ticket may be stopped at check-in by an airline agent noting the issuance date of the ticket. The airline may allow the passenger to travel, or as this is a document that was incorrectly issued, request the passenger to purchase a new ticket and seek a refund from the agent, which issued the neutral paper ticket. 4. In the instance where the passenger is allowed to travel on the paper BSP ticket, the airline will not be able to account for this document in its revenue accounting system and this will result in an ADM being issue to the agent for the unreported sale. Continued failure on the part of the agent may lead to bilateral action by the BSP airline regarding the agent s appointment.

290 4. Status of Neutral Ticket Stock Global Stock Recovery Linked to the elimination of neutral paper tickets is the accounting for, recovery and destruction of all stock on hand in agent locations, warehouse locations and undelivered stock at manufacturers. The following process, which has been endorsed by ISSAC and is being reviewed by IATA s internal auditor, has been developed by IATA to ensure the cost effective and secure management of this process across the approximately 100,000 sales locations issuing BSP documents: 1. IATA Country Managers in January 2008 will undertake a high level stock take exercise to confirm the stock on hand in agent and other locations. This exercise will establish the baseline for managing the recovery and destruction of ticket stock in June IATA Country Managers will be asked to assess the agents in their areas of responsibility and identify not more than 10% as agents who may require direct assistance in the stock recovery exercise, i.e. these agent locations will be monitored from January 2008 and the amount of stock they have on hand will be kept to the minimum required to facilitate their anticipated ticketing activity. On 1 June 2008, a physical stock accounting and recovery will take place. The stocks recovered will be reconciled against the baseline established by the Country Manger in January to confirm all stocks are recovered and the Country Manager will take responsibility to confirm recovered stocks are destroyed. 3. The remaining 90% of agent locations confirmed by Country Managers as not needing IATA s direct assistance in the accounting for and destruction of on hand ticket stock will be instructed to undertake the following on 1 June 2008; complete a stock on hand declaration and submit this to the IATA Country Manager, undertake to destroy the stock on hand and report the destruction using a specific form provided by IATA for this purpose. This stock destruction and reporting will take place no later than 15 June Agents will be obliged to complete the stock destruction form and return it with the signature of the responsible office of the agency and the agent s stamp. The form will confirm the agents understanding that the agent is responsible for the destruction of the BSP neutral tickets and assumes full responsibility for the wrongful use of this stock on/after 1 June In those cases where an agent is unwilling to assume the responsibility for the recovery and destruction of the BSP tickets on hand, the BSP Manager will undertake this activity.

291 5. Impact of the Elimination of Neutral Paper Tickets on 3 rd Parties in the BSP: 1. In some BSPs, non-airline companies are participating as a BSP Participant. In these instances the companies are using the IATA neutral Standard Traffic Document in OPATB2 or OPTAT format. 2. The elimination of neutral paper tickets will impact on these operations as no physical neutral paper tickets will be available for issuance by agents for these 3 rd party services. 3. In some instances, these 3 rd party participants have adapted their business models to address this, for example, a rail company has effectively ceased participation in the BSP and is now operating a Web based low cost ticketless model. 4. There are instances where BSP Airlines have interline agreements with 3 rd party and/or surface operators. Where these interline agreements exist, the BSP airlines are required to ensure their surface interline partner(s) can accept a passenger holding a neutral electronic ticket and conclude the appropriate interline electronic ticketing agreement. In those instances where this is not possible, a local solution involving the issuance of a transportation document by the BSP participating airline and/or the surface operator is required outside of the BSP process. This will need to be bilaterally developed. 5. In those cases where the surface operator and BSP participating airline are operating a code share service, the surface operator and airline must agree bilateral procedures to confirm the entitlement of the passenger to travel on the surface segment. There is no formal IATA process for this. 6. IATA Country Managers will have informed all 3 rd Parties in their markets of these developments and confirm to IATA BSP Operations that there are no expectations on the part of the 3 rd party users of continued neutral paper ticketing in the BSP on/after 1 June Acceptance of neutral paper tickets issued prior to 1 June 2008 Airlines should continue to accept neutral paper tickets issued prior to 1 June 2008 for travel on/after 1 June 2008 in accordance with their standard conditions of contract. Should a neutral paper ticket be presented for exchange or reissue at an IATA accredited travel agency then such paper ticket should be exchanged for an electronic ticket if the airline concerned allows this transaction by the agent.

292 7. Other consequences for interline itineraries 1. Many airlines in future may wish to prohibit their interline partners from issuing paper tickets for travel on them. Airlines are free to confirm that they themselves will no longer issue paper tickets if they choose. 2. Resolution 735d clarifies that airlines under irregular operations situations (IROPS) must exchange and reissue electronic tickets to new operating carriers rather than issue a Flight Interruption Manifest (FIM). 3. The IATA Clearing House (ICH) will continue to support the interline billing of paper tickets on/after 1 June 2008.

293 JPSC/27 PSC/29 Oct 07 Attachment: G Page: 1 of 6 Electronic Ticketing and Other Documents in BSPs on/after 1 June 2008 Dear IATA Agent, The 2007 IATA Annual General Meeting reconfirmed the goal of eliminating paper tickets from the BSPs. At the same time, the AGM recognised that some airlines are experiencing difficulty in meeting the deadline of 31 December In recognition of this fact, and to assist airlines to complete their work to eliminate paper tickets, the deadline was extended to 31 May This is the final deadline and no further extension will be made. What does this mean for you as an Agent and BSP user? Very simply that after 1 June 2008, you will not be able to issue a BSP supplied neutral paper ticket. We will be issuing separate instructions with respect to the destruction and/or recovery of our paper ticket stock next month. We are working closely with the Global Distribution System providers (GDSs) to ensure a smooth transition to ET and you can expect to receive instructions directly from individual airlines on their own plans beyond 1 June We are conscious of the fact that the BSPs also handle 3 rd Party users such as railways and we are working on solutions to handle this business. We are receiving many questions on the transition to ET and have therefore developed the attached summary sheet of key issues that you may find useful. It covers topics such as: Specific actions required Use of the Virtual Miscellaneous Document (V-MPD) and Electronic Miscellaneous Document (EMD) Consequences if a neutral paper ticket is issued on/after 1 June 2008 Impact of the elimination of neutral paper tickets on 3 rd parties in the BSP ET eligible itineraries on/after 1 June 2008 Should you have any questions or comments please forward these by to: eticket@iata.org. Yours Sincerely,

294 Summary Sheet of Key Issues for Travel Agents Electronic Ticketing and Other Documents in BSP on/after 1 June Specific actions required Each BSP participating airline should be communicating to you their procedures for itineraries that are not eligible for ticketing on an electronic ticket. These options include, but are not limited to the following: 4. Issuance of another document (e.g. Virtual MPD (V-MPD)) that could be used as a Prepaid Ticket Advice (PTA). Airlines will advise you if they will accept the use of the V-MPD as a PTA for this purpose. 5. Airlines may wish to enter into local arrangements with you whereby you may request the ticket to be issued by the airline on its own paper ticket stock. Agents should inform themselves of specific airline policy on this procedure. 6. Subject to agreement with you, a BSP participating airline may place its own paper ticket stock in an agency location and ticketing may be done on that stock. It should be noted however that in this instance the entire transaction is subject to the bilateral agreement between you and the airline since these transactions will be outside the IATA Agency Programme and the BSP administrative rules including default procedures and reporting and remittance schedules. 7. You should ensure that during the remaining time until 1 June 2008 that you become informed of each individual airline s policy for the issuance of tickets that you are unable to issue directly as electronic tickets on/after 1 June 2008 because individual carrier policy may vary. 2. Use of the V-MPD and EMD. IATA s Member airlines have already adopted standards for an Electronic Miscellaneous Document (EMD) that will replace all other non-ticket documents and which works in a similar manner to an electronic ticket. However, it is not anticipated that this will be fully available for use until 2009 at the earliest. In those BSPs where the automated coupon-bycoupon MCO (known as the MD50) is in use it should be noted that on/after 1 June 2008 the value coupon will no longer be available for the issuance of MCOs. IATA will monitor and evaluate the use of all other paper documents in those remaining BSPs where paper other documents including the manual paper carbonised MPD, the automated neutral carbonised MPD and the neutral carbonised excess baggage ticket are still distributed. As soon as is practicable, IATA will migrate these remaining BSPs to the already well established BSP best practice of removing all other paper documents. During the interim period all other documents can be issued by means of a virtual version of the MPD known as the V-MPD. You should therefore ensure that all of your offices are familiar with the V-MPD process and the actions they will need to follow for issuance.

295 Overview of the V-MPD The V-MPD is: - A virtual representation of the paper MPD/auto MCO; An instrument of exchange; A record of a transaction of payment for a service or collection of a fee; Issued in BSPlink; Drop down menu boxes look like a manual document; message upon completion to the airline service point; Airlines see their copy and act in accordance with their standard internal procedures for processing Prepaid Ticket Advices (PTAs). It should be noted that IATA is continuing to examine additional functionality that meets your needs in order to minimise disruptions to your operations and welcomes feedback and comment. The V-MPD is a viable alternative to paper MPDs and is available globally for BSP participating airlines to deploy market by market. IATA has prepared presentation material, user guides and a list of Frequently Asked Questions (FAQs) that are available for download in the Download Centre of the BSPlink Portal at (refer to BSPlink Customer Manuals ) Effect on Travel Agents Ticket Issuance It is expected that PTAs and tickets on departure will continue to decrease rapidly and airlines will continue to expand their electronic ticketing capabilities. However, there may be some tickets that you will be unable to issue as electronic tickets and, on/after 1 June 2008, you will no longer have the fallback of issuing a paper ticket. Some of the reasons for this could be identified as follows (depending on individual airline policy): Interline journeys where the particular mix of Marketing/Operating Carriers does not allow one carrier to be selected as the Validating Carrier because no one carrier has IET with all other carriers; Passive bookings; Groups; Journeys over 16 segments; Infants; Open segments; Ineligible sectors because the ground-handling infrastructure at some airports is not capable of processing electronic tickets. Should an airline choose to maintain its own paper tickets they can still be issued for these journeys at their own offices. Each airline should advise you whether they allow this and what their procedures are.

296 Effect on Travel Agents Other Documents IATA anticipates that the main reasons for agents to issue other documents will relate to the receipt for amendment fees and for issuance of non-air services (e.g. tours, hotel, car hire) where an interline electronic ticket agreement is not in place. The EMD will be the ideal solution to support the issuance of other documents. However there will be an interim period during which no EMD solution will be available and as such it will be necessary to maintain alternative methods of issuing other documents. IATA has deployed the V-MPD but, acknowledging that there will not be a value coupon produced, this will add an additional burden to industry resources where a value coupon is required. It should be noted that the V-MPD should only be seen as an interim measure until such time as the EMD is fully deployed. IATA is aware that some travel agents receive data supplied by their GDS from these transactions to manage back office functions. In addition some GDSs, but not all, have a certain level of interactivity into the Passenger Name Record (PNR). The problem however is that, looking at the V-MPD, there is a deficiency since a value or exchange coupon is not produced and there are no automatic updates into the PNR. It is therefore important that you liaise closely with your airlines because procedures for advising the airline of the issuance of another document may vary. For example an airline may request you to ensure that the information pertaining to the issuance of the other document is entered through a Special Service Request (SSR) or Other Services Information (OSI) placed into the PNR and queued to the airline for servicing following the standard procedures that applied for paper documents. Any interim solutions developed by the GDSs (e.g. suppressing the printing of a value coupon an OPATB2 markets) would be based on the fact that the GDSs have been approached by their airline/travel agency customers directly. Until such time as the remaining paper other documents in some BSPs have been withdrawn, airlines may allow you to continue to issue them beyond 31 May 2008 where it is practical. In those markets where these documents (manual MPD and MCO) are presently in place, and where the local market has agreed to continue the issuance of these documents, IATA will continue to provide stock and processing. Effect on Travel Agents remote ticketing facilities With the withdrawal of paper ticket stocks, travel agent use of Satellite Ticket Printers (STPs) will no longer be supported. As a consequence of the electronic ticketing deadline, all related standards and resolutions providing for Satellite Ticket Delivery Offices (STDOs), Special Event Locations (SELs), European Union Satellite Ticket Printers (EUSTPs) and STPs will no longer be applicable on/after 1 June If you are operating an approved STP, EUSTP, SEL or STDO and in possession of a valid IATA numeric code for such operation, you will be entitled to retain such IATA code for At the end of 2008 IATA will not process any renewal application for any of these ticketing facilities as an STP, EUSTP, STDO or SEL. Should you wish to convert any of these locations to another category of IATA sales location this can be done at any time. Any conversion will be assessed in accordance with applicable IATA resolution requirements and against the fees paid.

297 3. Consequences if you issue a neutral paper ticket on/after 1 June 2008 Inevitably some of you may hold residual paper ticket stock on/after 1 June 2008 if not yet destroyed. It is possible that a GDS may not yet have inhibited the use of that stock to produce a paper ticket after that date. If a neutral paper ticket is erroneously issued on/after 1 June it will not be accepted for normal sales reporting and travel. It is therefore vital that at the close of business on 31 May 2008 all remaining paper tickets be removed from the ticket imprinter machines. The following should also be noted: - 5. The IATA systems will be adjusted to reject a BSP reported sales where a paper ticket has been erroneously issued on/after 1 June This will result in the transaction not being reported to the issuing airline in the standard reporting process and will be classified in the BSP as an unreported sale. 6. As this erroneous sale will be unreported in the BSP, the ticket will not be shown on the BSP Billing Statement and as a result, the airline will not be paid for the ticket through the BSP. 7. A passenger holding such a ticket may be stopped at check-in by an airline agent noting the issuance date of the ticket. The airline may request the passenger to purchase a new ticket and seek a refund from the agent, which issued the neutral paper ticket. 8. Should an airline transport the passenger on the paper BSP ticket in error, the airline will not be able to account for this document in its revenue accounting system and this will result in an ADM being issue to you for the unreported sale. Should you continue to issue paper tickets on/after 1 June 2008 this may lead to bilateral action by the BSP participating airline regarding your appointment. 4. Impact of the elimination of neutral paper tickets on 3 rd parties in the BSP: 7. In some BSPs, non-airline companies are participating as a BSP Participant. In these instances the companies are using the IATA neutral Standard Traffic Document in OPATB2 or OPTAT format. 8. The elimination of neutral paper tickets will impact on these operations as no physical neutral paper tickets will be available for issuance by agents for these 3 rd party services. 9. In some instances, these 3 rd party participants have adapted their business models to address this, for example, a rail company has effectively ceased participation in the BSP and is now operating a Web based low cost ticketless model. 10. Should you sell transportation on these 3 rd party BSP participants you should ensure that they have communicated to you their plans.

298 5. ET eligible itineraries on/after 1 June 2008 Travel agents should enquire with their system provider(s) to determine if at time of pricing and any subsequent modification(s) to the reservation when re-pricing may be required, there is a feature to alert you when the itinerary cannot be issued on a single electronic ticket. This is in recognition of the fact that whilst each flight segment individually may be ET eligible, the particular mix of marketing/operating carriers in the itinerary would not allow you to issue the electronic ticket on any of those carriers with whom your have been granted the ticketing authority because interline ET does not exist with all participants in the itinerary.

299 JPSC/27 PSC/29 Oct 07 Attachment: H Page: 1 of 6 Guidelines for New PRM airport lists 1. Develop new airport lists for Passengers with Reduced Mobility (PRM) for dispatch to EU airports. 2. Pattern the PRM lists after IATA PNL/ADL concept, that is, by flight/date and with data element formats similar to the PNL/ADL. 3. Call the initially sent notification list, the PAL for Passenger Assistance List (comparable to the PNL). 4. Call the subsequently sent update list the CAL for Change Assistance List (comparable to the ADL). 5. Develop new Recommended Practice for the PAL/CAL, which will be numbered amongst the current DCS messages in the PSC Manual. The new RP will use the same data dictionary and data directory as used by the DCS messages. 6. Recommended Practice 1707b Section 1 should be updated to include a reference to the new RP for PRM lists. 7. The header of the PAL/CAL will contain information similar to the PNL/ADL. 8. Passengers will be ordered alphabetically based on airport of arrival and class of service (RBD/reservation booking designator), as is done for the PNL/ADL. 9. A PAL will be created for each flight departure based on the principle that the flight is either departing from an EU airport or will arrive (downline) at an EU airport. 10. The PAL and CAL is addressed only to EU airports, even if the flight itinerary includes non-eu airports. For example, a flight that operates DEN-JFK-ORY-ATH- DEL will have four PALs created: One PAL for the DEN departure, but addressed only to ORY and ATH showing DENORY, DENATH and DENDEL PRM passengers. One PAL for the JFK departure, but addressed to ORY and ATH showing JFKORY, JFKATH, and JFKDEL PRM passengers. One PAL for the ORY departure, addressed to ORY and ATH showing ORYATH and ORYDEL PRM passengers. One PAL for the ATH departure, addressed to ATH showing the ATHDEL PRM passengers. 11. The PAL/CAL lists will be sent via standard teletype, and addressed as specified by each EU airport, and only to EU airports, even if the flight itinerary includes non-eu airports. An EU airport may specify one or more addresses for an airport to receive a PAL/CAL.

300 JPSC/27 PSC/29 Oct 07 Attachment: H Page: A PAL is always multi-addressed, to include the departure airport (if it is an EU airport) and all downline airports (that are EU airports). This will show: to the flight s EU departure airport: their departing passengers to downline/mid-route EU airports: their arrival, transiting, and transferring passengers to the downline/final EU airport: their arrival and transferring passengers It is the responsibility of the EU airports receiving a PAL or CAL to parse their messages for the passengers they must serve locally. 13. Similar to PNL/ADL, transfer information will be contained on the PAL/CAL by use of the.i/ (inbound) and.o/ (outbound) elements; only one (adjacent).i/ and one (adjacent).o/ are to appear. 14. The lists will contain passenger s name, selected SSR codes that apply to the PRM requirements, one inbound connection, and one outbound connection. 15. Each passenger entry will be for a single passenger. 2SMITH/A/B, both blind, will be shown: 1SMITH/A.R/BLND and 1SMITH/B.R/BLND 2GREEN/A/B with GREEN/A as deaf will be shown only as: 1GREEN/A.R/DEAF on the lists) 16. Passengers with multiple PRM elements will have one entry showing all of their PRM elements. 1ERICKSON/J who has a wheelchair, is blind, and requires to be met will be shown as: 1ERICKSON/JAMESMR.R/WHCH.R/BLND.R/MAAS. 17. Free text that appears within any of the PRM SSR elements will also appear on the PAL/CAL. 18. A PAL will show the boarding airport and all downline EU airports. 19. If no PRM passengers exist for a PAL, the required PAL message will be sent indicating NIL PRM passengers, per airport and RBD. If no airport on the flight out of the boarding airport has PRM passengers, all (applicable) airports are shown, each showing the word NIL per RBD. 20. A CAL includes only those airports and RBDs that have PRM passengers. The word NIL does not appear on a CAL. 21. The following SSR codes from the IATA AIRIMP are PRM qualifying codes for the PAL/CAL in.r/ Remarks Elements. This list of codes is not exhaustive and other codes may be included according to the business practices of each carrier. The codes are shown in this table in alphabetical order by code:

301 JPSC/27 PSC/29 Oct 07 Attachment: H Page: 3 BLND Blind passenger (specify if accompanied by seeing eye dog) DEAF Deaf passenger (specify if accompanied by service animal) DPNA Disabled passenger with intellectual or developmental disability needing assistance (specify details) MAAS Meet and Assist (specify details) WCBD Wheelchair (dry cell battery): to be transported by a passenger which may require advance notification, preparation, or (dis)assembly. Weight and dimensions may be specified (required for use only by/between U.S. carriers) WCBW Wheelchair (wet cell battery): to be transported by a passenger which may require advance notification, preparation, or (dis)assembly. Weight and dimensions may be specified (required for use only by/between U.S. carriers) WCHC Wheelchair (C for Cabin Seat): passenger completely immobile; requires wheelchair to/from aircraft or mobile lounge and must be carried up/down steps and to/from cabin seat. When service animal is accompanying passenger, specify the type of animal in free text of SSR Item. WCHR Wheelchair (R for Ramp): passenger can ascend/descend steps and make own way i.e. across ramp, finger dock or to/from mobile lounge, as applicable. When service animal is accompanying passenger, specify the type of animal in free text of SSR Item. WCHS Wheelchair (S for Steps): passenger cannot ascend/descend steps, but is able to make own way to/from cabin seat; requires wheelchair for distance to/from aircraft or mobile lounge and must be carried up/down steps. When service animal is accompanying passenger, specify the type of animal in free text of SSR Item. WCMP Wheelchair (manual power): to be transported by a passenger. Weight and dimensions may be specified (required for use only by/between U.S. carriers) 22. No other data elements as defined for the PNL/ADL will be included in this list, for example, Totals Information will not be included. 23. The procedures and actions by the airports for each of these codes will be documented in a procedures manual that will be written and held by the ACI/AEA. 24. The PAL will be dispatched at a time determined by EU regulation to airports as indicated by the EU regulation. 25. The CAL is sent only as needed, but always after the PAL has been dispatched. 26. If Change Assistances have occurred, the CAL may be sent either one at a time at each affected PNR change or at one or more scheduled times, to include all changed PNRs during that block of time. 27. The PAL/CAL are subject to be sent in multiple parts the same as the PNL/ADL. 28. The ENDPARTn or ENDPAL/ ENDCAL will be used on the messages as appropriate. 29. For code share flights, the operating carrier is always used.

302 JPSC/27 PSC/29 Oct 07 Attachment: H Page: 4 Example 1A: PASSENGER ASSISTANCE LIST A PAL for the BRU boarding of a flight that travels BRU/ORY/MAD/LIS with two classes of service. BRUSPCR BRUPACR ORYPACR MADPACR LISCAPR.MSPRCUW PAL UW234/12NOV BRU PART1 -ORY F 1KLEG/JOHNMR.R/WHCR HK1.I/AA123F12CDG -ORY Y 1BIGAPPLE/BILLMR/MARYMRS.R/WHCS HK1.O/US432F12YYZ 1THOMPSON/ERNESTMR.R/DEAF HK1 -MAD F NIL -MAD Y 1SHULTZ/JANEMRS.R/BLND HK1 NEEDS ASSISTANCE ON STAIRS 1ZIMMER/EMMAMRS.R/DPNA HK1 DIZZY SPELLS -LIS F NIL -LIS Y NIL ENDPAL Example 1B: CHANGE ASSISTANCE LIST A CAL for the BRU boarding of the same flight as in Example 1A, when after the PAL was sent one passenger makes a new booking (or adds wheelchair information to an existing booking) and another passenger cancels his booking. BRUSPCR BRUPACR ORYPACR MADPACR LISCAPR.MSPRCUW CAL UW234/12NOV BRU PART1 -ORY ADD 1BROWN/WILLIAM MR.R/WHCS NEEDS ASSISTANCE FOR ALL MOVEMENTS.O/US432F12YYZ -MAD DEL 1ZIMMER/EMMAMRS.R/DPNA DIZZY SPELLS ENDCAL

303 JPSC/27 PSC/29 Oct 07 Attachment: H Page: 5 Example 2: PASSENGER ASSISTANCE LIST A PAL for the JFK boarding of a flight that travels JFK-AMS- CPH that has PRM passengers for some segments, but not others. The PAL is addressed to only the EU airports. AMSSPCR CPHPACR.MSPRCUW PAL JM555/01DEC JFK PART1 -AMS C 1TORRES/JOSEDR.R/DEAF.R/MAAS/HELP THRU CUSTOMS AND IMMIGRTION -AMS Y NIL -CPH C NIL -CPH Y 1PETERSON/ROBERTMR.R/BLND.R/DPNA NERVOUS FLIER 1THERENCE/ANITAREV.R/WCBD ALL DOCS COMPLETE FOR BATTERY 1ULMER/KARLMR..R/WCHR TRVL WITH TWO ATTENDENTS BOOKED AS ROBERT MILLER AND JOHN JANSON 1WILSON/ROBERTMR.R/MAAS ELDERLY FIRST FLIGHT ESCORT TO BORDER CONTROL AND BAGGAGE CLAIM ENDPAL Example 3A: PASSENGER ASSISTANCE LIST A PAL for the DEN boarding of a flight that travels DEN-ATL- MAD-ZRH-SVO that has NO PRM passengers boarding at DEN for any of the downline airports. The PAL is sent naming all downline airports. The airport SVO is included because passengers for SVO are transit passengers at MAD and ZRH airports. MADPACR ZRHPACR.MSPRCUW PAL PT8800/08AUG DEN PART1 -MAD C NIL -MAD Y NIL -ZRH C NIL -ZRH Y NIL -SVO C NIL -SVO Y NIL ENDPAL

304 JPSC/27 PSC/29 Oct 07 Attachment: H Page: 6 Example 3B: PASSENGER ASSISTANCE LIST A PAL for the same flight in Example 3A for the MAD boarding of the flight. PRM passengers will board at MAD for both of the downline airports, including SVO who are transit passengers at ZRH. MADPACR ZRHPACR.MSPRCUW PAL PT8800/09AUG MAD PART1 -ZRH C 1ABLES/MARLENEMS.R/WCHC TRAVELLING WITH HUSBAND 1BAKER/HILDADR.R/DEAF -ZRH Y NIL -SVO C NIL -SVO Y 1QUILLER/ARTHURMR.R/WCHR.R/DEAF.R/MAAS TO BE MET BY FAMILY AT BAGGAGE CLAIM 1ROGOTZKE/KARLDR.R/BLND NEEDS ASST DEBOARDING AND THRU AIRPORT TO TAXI STAND.R/MAAS SPEAKS ONLY ARMENIAN ENDPAL Example 4: CHANGE ASSISTANCE LIST A CAL for the same flight in Example 3 for the MAD boarding, adding two new PRM passengers, changing one (a complete replacement), and deleting one. MADPACR ZRHPACR.MSPRCUW CAL PT8800/09AUG MAD PART1 -ZRH C ADD 1ABLES/ANDREWMR.R/BLND TRAVELLING WITH WIFE IN WHEELCHAIR 1LARSON/SUSANMRS.R/MAAS NEEDS A PLACE TO LIE DOWN FOR FIVE MINUTES -SVO Y DEL 1ROGOTZKE/KARLDR.R/BLND NEEDS ASST DEBOARDING AND THRU AIRPORT TO TAXI STAND.R/MAAS SPEAKS ONLY ARMENIAN CHG 1QUILLER/ARTHURMR.R/WCHR.R/DEAF.R/MAAS TO BE MET BY FAMILY RIGHT AFTER BORDER CONTROL STATION ENDCAL

305 JPSC/27 PSC/29 Oct 07 Attachment: I Page: 1 of 1 AIRIMP changes: Matrix Instructions for Transmission of SSR Codes SSR Code Action Code Reply Automated Format Free Text In Request Free Text In Reply/Can cel DPNA Mandatory Mandatory Mandatory Mandatory Optional Special Service Requirement Codes Disabled passenger with intellectual or developmental disability needing assistance (specify details) DPNA 7.2 PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (DECODING) DPNA. Disabled passenger with intellectual or developmental disability needing assistance (specify details) Examples of SSR Request Items (refer to for appropriate reply). (b) Automated Format Examples. Example 20 - Message from booking source to Member requesting assistance for a passenger with reduced mobility whose disability is non-physical and therefore not covered by existing SSRs MUCRM1A.HDQRM1P HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1JACKSON/MELVYNMR BA2582M30JAN LGWVCE HK1 SSR DPNA BA NN1 LGWVCE2582M30JAN.ALZHEIMERS DISEASE

306 JPSC/27 PSC/29 Oct 07 Attachment: J Page: 1 of 1 CHAPTER 12 STANDARD MESSAGE IDENTIFIER (SMI) CODES STANDARD MESSAGE IDENTIFIER (SMI) CODES Code Title Footnote: SMT Reference CAL Change Assistance List PP PAL Passenger Assistance List PP. 12.3STANDARD MESSAGE IDENTIFIER (SMI) CODES CROSS REFERENCE Footnote: PP Cross References for Related SMTs: IATA Recommended Practice 1708a

307 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 1 of 21 AIRIMP 2.10 AUXILIARY SERVICE ELEMENT SVC Additional Service Non-Segment-Associated TUR - Tour (sightseeing, etc.) Additional Services Non-Segment-Associated These services are requested with an auxiliary service element using the code SVC Element Construction Request: Components Number and type of Characters Examples (a) Service Identifier 3 a SVC (b) Airline designator to whom the service is 2 an or 3a BA requested (3 character codes are preceded with an oblique) (c ) Action code 2a NN (d) Number of services requested 1 3 n 1 (e) Location 3 a MAD (f) Service date 2 n 3 a 17OCT (g) Reason for Issuance Code (RFIC) sub 3 an /E23 code preceded by an oblique (/) (h) Commercial Name of Service, preceded 1 30an /LOUNGE ACCESS by an oblique (/) (i) EMD number including coupon number (if as defined / C1 applicable) preceded by an oblique (/) (j) Name (preceded by /NM-) Refer to name element paragraph (f) /NM-1BIGGIN/ANDREW

308 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 2 Reply: Components Number and type of Characters Examples (a) Service Identifier 3 a SVC (b) Airline designator 2 an or 3a BA (c ) Reply code 2a KD (d) Number of services 1 3 n 1 (e) Location 3 a MAD (f) Service date 2 n 3 a 17OCT (g) Reason for Issuance Code (RFIC) sub 3 an /E23 code preceded by an oblique (/) (h) Commercial Name of Service preceded 1 30an /LOUNGE ACCESS by an oblique (/) (i) Name (preceded by /NM-) Refer to name /NM-1BIGGIN/ANDREW element paragraph (f) (j) EMD number including coupon number (if as defined / C1 applicable) preceded by an oblique (/) (k) Free Text (preceded by a period) 1 90 an.lounge AT GATE Positioning The Auxiliary Each Auxiliary General Construction Rules When requesting seat(s) using SSR codes NSST or SMST the following location codes may be combined and must be shown in free text or specify seat number(s) in free text: C Chargeable seat (bilateral agreement); E Exit Row seat; F Non-chargeable seat (bilateral agreement);

309 JPSC/27 PSC/29 Oct 07 Attachment: K Page: Instructions (d) Action Code and number in party (a one, two or three digit number or an oblique(/) character): (i) a special service for a passenger must be cleared on a request and confirm basis, unless selling facilities have been bilaterally agreed, except as follows: the Action/Advice Code "XX" is used in an SSR item advising cancellation of a special service requirement, the Action/Advice Codes used with SSR ASVC are detailed in ; Matrix - Instructions for Transmission of SSR Codes (note to editor: add ASVC in alphabetic sequence.) SSR Code Action Code Reply Automated Format Free Text In Request Free Text In Reply/Cance l ASVC Mandatory Mandatory Mandatory See 3.19 See Additional Services Segment - Associated Airline Tariff Publishing Company (ATPCO) maintains a database of Additional Services offered by Members that may require an electronic miscellaneous document (EMD) to be issued. These services are requested using SSR ASVC. The SSR may be sent as an independent SSR for a segment associated request or in addition to an existing SSR currently defined in AIRIMP (e.g., PETC). The format for the SSR is as follows: When an EMD is required, the following rules apply: a. Construction and Sequence of components of SSR ASVC

310 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 4 i. Initial request message Components Number and type of Examples Characters (a) Element Identifier 3 a SSR (b) SSR Service Code 4 a ASVC (c ) Airline Designator (3 character codes are 2 an or 3 a BA preceded with an oblique) (d) Action Code 2 a NN (e) Number in Party (without leading zeros) 1 3 n 1 (f) Departure Airport 3 a NCL (g) Arrival Airport 3 a LHR (h) Flight number (with leading zeros) 4 n 1321 (i) Reservation Booking Designator 1 a J (j) Date 2n3a 30JUN (k) If applicable, Name element, preceded by a hyphen Refer to name element paragraph -1BIGGIN/ANDREW (l) Formatted text. Reason for Issuance Code (RFIC) sub code (/), SSR code (/), Commercial Name of Service (f) As defined.e23/vgml/ VEGETARIAN MEAL ii. Reply to an SSR ASVC Replies are standard SSR ASVC replies using the codes listed in iii. Transmission of EMD in an SSR ASVC Components Number and type of Examples Characters (a) Element Identifier 3 a SSR (b) SSR Service Code 4 a ASVC (c ) Airline Designator (3 character codes are 2 an or 3 a BA preceded with an oblique) (d) Action/Status Code (Must be HS) 2 a HS (e) Number in Party (without leading zeros) 1 3 n 1 (f) Departure Airport 3 a NCL (g) Arrival Airport 3 a LHR (h) Flight number (with leading zeros) 4 n 1321 (i) Reservation Booking Designator 1 a J (j) Date 2n3a 30JUN (k) If applicable, Name element, preceded by a hyphen Refer to name element paragraph -1BIGGIN/ANDREW (l) Formatted text. Reason for Issuance Code (RFIC) sub code (/), SSR code (/), Commercial Name of Service (/), EMD Number including coupon number (f) As defined. E23/VGML/ VEGETARIAN MEAL/ C1

311 JPSC/27 PSC/29 Oct 07 Attachment: K Page: Location Codes (optional) C Chargeable Seat (bilateral agreement) E Exit Row Seat F Non-chargeable Seat (bilateral agreement) 3.19 ADDITIONAL SERVICES (bilateral agreement) Airline Tariff Publishing Company (ATPCO) maintains a database of Additional Services offered by Members that may require an electronic miscellaneous document (EMD) to be issued. There are two types of additional services. One type is segment-associated and the other is standalone Segment-Associated Additional Services These services are requested using SSR ASVC. The SSR may be sent as an independent SSR for a segment-associated request or in addition to another SSR defined in AIRIMP (e.g., PETC) Rules of Usage i. Unless otherwise specified standard SSR rules apply. ii. An SSR ASVC is used to indicate that an EMD may be required and is typically used in conjunction with a standard SSR element which requests the service. If no standard SSR code (refer to ) exists for the type of service being requested, an SSR ASVC is used to request the service and to indicate an EMD is required. 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 may be name associated only to a single passenger. In a multi-name PNR, the SSR and its associated SSR ASVC elements must be name associated. 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 name. vi. SSR ASVC must be segment related. vii. If the additional service is filed in the industry database with a fee, even if no fee is collected, an EMD must be issued and therefore an SSR ASVC must be included in a message. viii. One passenger may purchase multiple services of the same type on the same flight segment, e.g., two bicycles (BIKE). ix. When including the EMD number, include the appropriate coupon number. x. When an SSR is cancelled, any associated SSRs pertaining to that service must also be cancelled and included in the message. xi. When sending messages, use one of the action/reply/advice/status codes as listed in :

312 JPSC/27 PSC/29 Oct 07 Attachment: K Page: Action/Reply/Advice/Status Codes Action codes NN Service Requested HS EMD issued for confirmed service (only to be used following KD) XX Service cancelled Reply/Advice codes UN Unable - special service not provided UC Unable to confirm/unable to wait list KD Service Confirmed subject to receipt of EMD issue or reissue KK Confirmed no EMD required for service. NO No Action taken plus free text HX Have cancelled SD Schedule change/rebooking; EMD already issued. Document number must be included in the SSR. Status Codes HK Holding confirmed; no EMD required HD Holding confirmed; EMD required HI Holding confirmed; EMD issued (EMD can only be issued if the Ticket is issued). HN Holding need Examples Example 1 Message from booking source to Member requesting an additional service. HDQRMBA.HDQRM1S HDQ1SQWERTY89D1/ /CBB/1S/T/BO/BOB 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG HK2 SSR ASVC BA NN1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT Example 1(a) - Message sent from the Member to the booking source advising no action has been taken on the request with free text explaining the reason. HDQRM1S.HDQRMBA HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG HK2 SSR ASVC BA NO1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT/NO IFE THIS FLIGHT

313 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 7 Example 1(b) - Message from the Member to the booking source confirming the additional service (ASVC) with KK as no EMD is required. This optional service message is sent as a reply to an NN request or as follow-up message to a previously sent KD reply. HDQRM1S.HDQRMBA HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG HK2 SSR ASVC BA KK1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT Example 1(c) - Message from the Member to the booking source confirming the additional service (ASVC) with KD as an EMD is required. This additional service message is sent as a reply to an NN request or as follow-up message to a previously sent KK reply. HDQRM1S.HDQRMBA HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG HK2 SSR ASVC BA KD1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT Example 1(d) - Message from the booking source to the Member advising the EMD has been issued. This message is sent in response to a KD or SD. HDQRMBA.HDQRM1S HDQ1SQWERTY/89D1/ /CBB/1S/T/BO/BOB 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG HK2 SSR ASVC BA HS1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT/ C3 Example 2 - Message from the member advising a schedule change where additional service has not been rebooked. HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG UN2 BA 0204Y14MAY LHRCDG TK2/

314 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 8 Example 2(a) - Message from the member advising a schedule change where additional service has been rebooked; no EMD is required even if one had been previously issued. HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG UN2 BA 0204Y14MAY LHRCDG TK2/ SSR ASVC BA KK1 LHRCDG 0204Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT Example 2(b) - Message from the member advising a schedule change where additional service has been rebooked; EMD was not previously issued but is now required. HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG UN2 BA 0204Y14MAY LHRCDG TK2/ SSR ASVC BA KD1 LHRCDG 0204Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT Example 2(c) - Message from the member advising a schedule change where additional service has been rebooked; EMD was previously issued and subsequent EMD action may be required. Send EMD and coupon number in message. HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG UN2 BA 0204Y14MAY LHRCDG TK2/ SSR ASVC BA SD1 LHRCDG 0204Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT/ C3

315 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 9 Example 2(d) - Message from the member advising a schedule change where segment(s) and additional service(s) have been rebooked to a different number of segments than the original booking; EMD was previously issued; EMD action (reissue) is required. Member may choose whether to include 0, 1 or 2 SSRs. The previously issued EMD and coupon number are not included in the message. HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG UN2 BA 0204Y14MAY LHRMAN TK2/ BA 0206Y14MAY MANCDG TK2/ SSR ASVC BA KD1 LHRMAN 0204Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0202Y14MAY LHRCDG UN2 BA 0204Y14MAY LHRMAN TK2/ BA 0206Y14MAY MANCDG TK2/ SSR ASVC BA KD1 LHRMAN 0204Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT SSR ASVC BA KD1 MANCDG 0206Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT or Example 2(e) - Message from the member advising a schedule change where segment(s) and additional service(s) have been rebooked to a fewer number of segments than the original booking; EMD was previously issued. EMD action (reissue) is now required. The previously issued EMD and coupon number are not included in the message. HDQRM1S.HDQRMBA ASC HDQ1SQWERTY 2SMITH/WALTERMR/MARYMRS BA 0204Y14MAY LHRMAN UN2 BA 0206Y14MAY MANCDG UN2 BA 0202Y14MAY LHRCDG TK2/ SSR ASVC BA KD1 LHRCDG 0202Y14MAY-1SMITH/WALTERMR.E23//IN FLIGHT SSR ASVC BA /// ENTERTAINMENT

316 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 10 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 HDQ1SQWERTY/89D1/ /CBB/1S/T/BO/BOB 1SMITH/WALLYMSTR BA 0202Y14MAY LHRCDG HK1 SSR UMNR BA NN1 LHRCDG 0202Y14MAY.UM07 SSR ASVC BA NN1 LHRCDG 0202Y14MAY.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 is required. HDQRM1S.HDQRMBA HDQ1SQWERTY 1SMITH/WALLYMSTR BA 0202Y14MAY LHRCDG HK1 SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07 SSR ASVC BA KD1 LHRCDG 0202Y14MAY.L04/UMNR/ SSR ASVC BA /// UNACCOMPANIED MINOR Example 3(b) Message from the booking source to Member requesting unaccompanied minor handling; no ASVC is sent. HDQRMBA.HDQRM1S HDQ1SQWERTY/89D1/ /CBB/1S/T/BO/BOB 1SMITH/WALLYMSTR BA 0202Y14MAY LHRCDG HK1 SSR UMNR BA NN1 LHRCDG 0202Y14MAY.UM07 Example 3(c) Message from the Member to the booking source confirming unaccompanied minor handling; ASVC is sent with KD indicating an EMD is required. HDQRM1S.HDQRMBA HDQ1SQWERTY 1SMITH/WALLYMSTR BA 0202Y14MAY LHRCDG HK1 SSR UMNR BA KK1 LHRCDG 0202Y14MAY.UM07 SSR ASVC BA KD1 LHRCDG 0202Y14MAY.L04/UMNR/ SSR ASVC BA /// UNACCOMPANIED MINOR

317 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 11 Example 4 Message from booking source to Member requesting a non-smoking aisle seat assignment; no ASVC is sent. MUCRM1A.HDQRM1P HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSSA KL NN1 NCLAMS1234S30JAN Example 4(a) Message from the Member to the booking source confirming the seat assignment; no EMD is required, therefore no ASVC is sent. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSSA KL KK1 NCLAMS1234S30JAN.24C Example 4(b) - Message from the Member to the booking source confirming the seat assignment; ASVC is sent with KD as EMD is required. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSSA KL KK1 NCLAMS1234S30JAN.24C SSR ASVC KL KD1 NCLAMS1234S30JAN.S23/NSSA/CHARGEABLE SEAT Example 5 Message from the booking source to Member requesting chargeable aisle (CA) seat assignment; no ASVC is sent. MUCRM1A.HDQRM1P HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSST KL NN1 NCLAMS1234S30JAN.CA

318 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 12 Example 5(a) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KK indicating no EMD is required, as Member will not charge for the seat. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSST KL KK1 NCLAMS1234S30JAN.24C SSR ASVC KL KK1 NCLAMS1234S30JAN.S23/NSST/CHARGEABLE SEAT Example 5(b) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KD indicating an EMD is required. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSST KL KK1 NCLAMS1234S30JAN.24C SSR ASVC KL KD1 NCLAMS1234S30JAN.S23/NSST/CHARGEABLE SEAT Example 6 Message from the booking source to the Member requesting a seat assignment; ASVC is also sent denoting agent is aware an EMD is required. MUCRM1A.HDQRM1P HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSSA KL NN1 NCLAMS1234S30JAN.C SSR ASVC KL NN1 NCLAMS1234S30JAN.S23/NSSA/CHARGEABLE SEAT Example 6(a) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KD indicating an EMD is required. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSSA KL KK1 NCLAMS1234S30JAN.24C SSR ASVC KL KD1 NCLAMS1234S30JAN.S23/NSSA/CHARGEABLE SEAT

319 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 13 Example 6(b) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KK indicating an EMD is not required, as Member will not charge for the seat. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR NSSA KL KK1 NCLAMS1234S30JAN.24C SSR ASVC KL KK1 NCLAMS1234S30JAN.S23/NSSA/CHARGEABLE SEAT Example 7 Message from the booking source to the Member requesting chargeable seat assignments; ASVC is not sent. MUCRM1A.HDQRM1P HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 2WALKER/JOHNMR/SARAH MRS KL1234S30JAN NCLAMS HK2 SSR NSST KL NN2 NCLAMS1234S30JAN Example 7(a) Message from the Member to the booking source confirming seat assignments; two ASVCs are sent with KD indicating EMD is required for each passenger. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 2WALKER/JOHNMR/SARAHMRS KL1234S30JAN NCLAMS HK2 SSR NSST KL KK2 NCLAMS1234S30JAN.24B24C SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/JOHNMR.S23/NSST/ SSR ASVC KL /// CHARGEABLE SEAT SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/SARAHMRS.S23/NSST/ SSR ASVC KL ///CHARGEABLE SEAT Example 8 Message from the booking source to the Member requesting chargeable seat assignments; two ASVCs are sent. MUCRM1A.HDQRM1P HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 2WALKER/JOHNMR/SARAHMRS KL1234S30JAN NCLAMS HK2 SSR NSST KL NN2 NCLAMS1234S30JAN SSR ASVC KL NN1 NCLAMS1234S30JAN-1WALKER/JOHNMR.S23/NSST/ SSR ASVC KL /// CHARGEABLE SEAT SSR ASVC KL NN1 NCLAMS1234S30JAN-1WALKER/SARAHMRS.S23/NSST/ SSR ASVC KL /// CHARGEABLE SEAT

320 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 14 Example 8(a) Message from the Member to the booking source confirming seat assignments; two ASVCs are sent with KD indicating EMD is required for each passenger. HDQRM1P.MUCRM1A HDQ1P 7YHAWB 2WALKER/JOHNMR/SARAHMRS KL1234S30JAN NCLAMS HK2 SSR NSST KL KK2 NCLAMS1234S30JAN.24B24C SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/JOHNMR.S23/NSST/ SSR ASVC KL /// CHARGEABLE SEAT SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/SARAHMRS.S23/NSST/ SSR ASVC KL /// CHARGEABLE SEAT Examples of Request and Reply Messages for Pre-reserved seats in SSR SEAT elements in conjunction with SSR ASVC elements. When seat reservations involve chargeable seats, the SSR ASVC may be used. See rules for construction of the SSR ASVC in Example 1 Message from booking source to Member requesting a non-smoking aisle seat assignment; no ASVC is sent. MUCRM1A.HDQRM1P BPR HDQ1P 7YHAWB/K32/ /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 BPR HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS

321 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 15 Example 1(b) - Message from the Member to the booking source confirming the seat assignment; ASVC is sent with KD as EMD is required. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS SSR ASVC KL KD1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT Example 2 Message from the booking source to Member requesting chargeable seat assignment; no ASVC is sent. MUCRM1A.HDQRM1P BPR HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL NN1 NCLAMS1234S30JAN.NC Example 2(a) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KK indicating no EMD is required, as Member will not charge for the seat. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS SSR ASVC KL KK1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT Example 2(b) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KD indicating an EMD is required. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS SSR ASVC KL KD1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT

322 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 16 Example 3 Message from the booking source to the Member requesting a seat assignment; ASVC is sent denoting agent is aware an EMD is required. MUCRM1A.HDQRM1P BPR HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL NN1 NCLAMS1234S30JAN.NA SSR ASVC KL NN1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT Example 3(a) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KD indicating an EMD is required. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS SSR ASVC KL KD1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT Example 4 Message from the booking source to the Member requesting a seat assignment; ASVC is also sent denoting agent is aware an EMD is required. MUCRM1A.HDQRM1P BPR HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL NN1 NCLAMS1234S30JAN.NA SSR ASVC KL NN1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT Example 4(a) Message from the Member to the booking source confirming seat assignment; ASVC is sent with KK indicating an EMD is not required. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 1WALKER/JOHNMR KL1234S30JAN NCLAMS HK1 SSR SEAT KL KK1 NCLAMS1234S30JAN.24CN/RS SSR ASVC KL KK1 NCLAMS1234S30JAN.S23/SEAT/CHARGEABLE SEAT

323 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 17 Example 5 Message from the booking source to the Member requesting chargeable seat assignments; ASVC is not included in the message. MUCRM1A.HDQRM1P BPR HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 2WALKER/JOHNMR/SARAH MRS KL1234S30JAN NCLAMS HK2 SSR SEAT KL NN2 NCLAMS1234S30JAN.NEAC Example 5(a) Message from the Member to the booking source confirming seat assignments; two ASVCs are sent with KD indicating that an EMD is required for each passenger. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 2WALKER/JOHNMR/SARAH MRS KL1234S30JAN NCLAMS HK2 SSR SEAT KL KK2 NCLAMS1234S30JAN.24BN24CN/RS SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/JOHNMR.S23/SEAT/ SSR ASVC KL /// CHARGEABLE SEAT SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/SARAHMRS.S23/SEAT/ SSR ASVC KL /// CHARGEABLE SEAT Example 6 Message from the booking source to the Member requesting chargeable seat assignments; two ASVCs are sent. MUCRM1A.HDQRM1P BPR HDQ1P 7YHAWB/K32/ /NCL/1P/T/GB//GS 2WALKER/JOHNMR/SARAHMRS KL1234S30JAN NCLAMS HK2 SSR SEAT KL NN2 NCLAMS1234S30JAN.NC SSR ASVC KL NN1 NCLAMS1234S30JAN-1WALKER/JOHNMR.S23/SEAT/ SSR ASVC KL ///CHARGEABLE SEAT SSR ASVC KL NN1 NCLAMS1234S30JAN-1WALKER/SARAHMRS.S23/SEAT/ SSR ASVC KL ///CHARGEABLE SEAT

324 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 18 Example 6(a) Message from the Member to the booking source confirming seat assignments; two ASVCs are sent with KD indicating EMD is required for each passenger. HDQRM1P.MUCRM1A BPR HDQ1P 7YHAWB 2WALKER/JOHNMR/SARAHMRS KL1234S30JAN NCLAMS HK2 SSR SEAT KL KK2 NCLAMS1234S30JAN.24BN24CN/RS SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/JOHNMR.S23/SEAT/ SSR ASVC KL ///CHARGEABLE SEAT SSR ASVC KL KD1 NCLAMS1234S30JAN-1WALKER/SARAHMRS.S23/SEAT/ SSR ASVC KL ///CHARGEABLE SEAT Additional Services Non-Segment-Associated Services These services are requested with an auxiliary service element using the code SVC. (Refer to 2.10) Examples Example 1 Message from booking source to Member requesting one service per passenger. HDQRMDL.MUCRM1A MUC1A 2GLYIP/NCL7X2063/ /NCL/1A/N/GB//GS 2ARENA/BRUNOMR/MARINAMRS SVC DL NN1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR SVC DL NN1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/MARINAMRS OSI YY CTCT NCL TRAVEL AGENT Example 1(a) Message from the Member to the booking source advising no action has been taken with a reason included in free text for one additional service per passenger. MUCRM1A.HDQRMDL MUC1A 2GLYIP 2ARENA/BRUNOMR/MARINAMRS SVC DL NO1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR.LOUNGE NOT AVAILABLE SVC DL NO1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/MARINAMRS.LOUNGE NOT AVAILABLE OSI YY CTCT NCL TRAVEL AGENT

325 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 19 Example 2 Message from booking source to Member requesting one service per passenger. HDQRMDL.MUCRM1A MUC1A 2GLYIP/NCL7X2063/ /NCL/1A/N/GB//GS 2ARENA/BRUNOMR/MARINAMRS SVC DL NN1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR SVC DL NN1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/MARINAMRS OSI YY CTCT NCL TRAVEL AGENT Example 2(a) Message from the Member to the booking source confirming the one additional service per passenger with KD as an EMD is required. Free text with additional information is included in the reply. MUCRM1A.HDQRMDL MUC1A 2GLYIP 2ARENA/BRUNOMR/MARINAMRS SVC DL KD1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR.LOUNGE AT GATE 43 SVC DL KD1 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/MARINAMRS.LOUNGE AT GATE 43 OSI YY CTCT NCL TRAVEL AGENT Example 2(b) Message from booking source to Member advising the EMDs have been issued for one additional service per passenger. HDQRMDL.MUCRM1A MUC1A 2GLYIP/NCL7X2063/ /NCL/1A/N/GB//GS 2ARENA/BRUNOMR/MARINAMRS SVC DL HS1 ORD 30JUN/E23/LOUNGE ACCESS/ C1/NM-1ARENA/ BRUNO MR.LOUNGE AT GATE 43 SVC DL HS1 ORD 30JUN/E23/LOUNGE ACCESS/ C1/NM-1ARENA/ MARINA MRS.LOUNGE AT GATE 43 OSI YY CTCT NCL TRAVEL AGENT

326 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 20 Example 3 Message from booking source to Member requesting multiple services for a passenger. HDQRMDL.MUCRM1A MUC1A 2GLYIP/NCL7X2063/ /NCL/1A/N/GB//GS 2ARENA/BRUNOMR/MARINAMRS SVC DL NN2 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR OSI YY CTCT NCL TRAVEL AGENT Example 3(a) Message from the Member to the booking source advising no action has been taken with a reason included in free text for multiple services for one passenger. MUCRM1A.HDQRMDL MUC1A 2GLYIP 2ARENA/BRUNOMR/MARINAMRS SVC DL NO2 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR.LOUNGE NOT AVAILABLE OSI YY CTCT NCL TRAVEL AGENT Example 4 Message from booking source to Member requesting multiple services for a passenger. HDQRMDL.MUCRM1A MUC1A 2GLYIP/NCL7X2063/ /NCL/1A/N/GB//GS 2ARENA/BRUNOMR/MARINAMRS SVC DL NN2 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR OSI YY CTCT NCL TRAVEL AGENT Example 4(a) Message from the Member to the booking source confirming two additional services for one passenger with KD as an EMD is required. Free text with additional information is included in the reply. MUCRM1A.HDQRMDL MUC1A 2GLYIP 2ARENA/BRUNOMR/MARINAMRS SVC DL KD2 ORD 30JUN/E23/LOUNGE ACCESS//NM-1ARENA/BRUNOMR.LOUNGE AT GATE 43 OSI YY CTCT NCL TRAVEL AGENT

327 JPSC/27 PSC/29 Oct 07 Attachment: K Page: 21 Example 4(b) Message from booking source to Member advising the EMD has been issued for multiple services for a passenger. HDQRMDL.MUCRM1A MUC1A 2GLYIP/NCL7X2063/ /NCL/1A/N/GB//GS 2ARENA/BRUNOMR/MARINAMRS SVC DL HS2 ORD 30JUN/E23/LOUNGE ACCESS/ C1/NM-1ARENA/ BRUNO MR.LOUNGE AT GATE 43 OSI YY CTCT NCL TRAVEL AGENT Auxiliary Service Identifiers Air Taxi. Additional Services Non-Segment-Associated.SVC Car Rental Special Service Requirement Codes Additional Service (bilateral agreement) ASVC 7.2 PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (DECODING) (Editor: please add codes below in alphabetic sequence.) ASVC Additional Services (bilateral agreement) C Chargeable Seat (bilateral agreement) E Exit Row Seat F Non-Chargeable Seat (bilateral agreement) SVC. Additional Service Non-Segment-Associated

328 JPSC/27 PSC/29 Oct 07 Attachment: L Page: 1 of Instructions (e) Action Code the Action/Advice Code "XX" is used in an SSR item advising cancellation of a special service requirement, other than XX, the only code allowed in an SSR ESVC is HK and the number 1; Matrix - Instructions for Transmission of SSR Codes (note to editor: add ESVC in alphabetic sequence.) SSR Code Action Code Reply Automated Format Free Text In Request Free Text In Reply/Cancel ESVC Mandatory Not Permitted Mandatory See 3.20 See Notification of EMD for Additional Services Other than Optional Services When it is necessary to issue an EMD for Additional Services (other than Optional Services as specified in AIRIMP 3.19) use SSR ESVC. This is for airline use only. See 3.20 for rules of usage. The following rules apply for the construction of SSR ESVC. Components Number and type of Examples Characters (a) Element Identifier 3 a SSR (b) SSR Service Code 4 a ESVC (c ) Airline Designator (3 character codes are preceded 2 an or 3 a CX with an oblique) (d) Advice Code HK or Action Code XX 2 a HK (e) Number in Party 1 n 1 (f) Departure Airport 3 a HKG (g) Arrival Airport 3 a PEK (h) Flight number (with leading zeros) 4 n 0456 (i) Reservation Booking Designator 1 a J (j) Date 2n3a 15SEP (k) If applicable, Name element, preceded by a hyphen Refer to name element -1CHEN/KAIYADR paragraph (f) (l) Formatted text. Reason for Issuance Code (RFIC) sub code (/), Commercial Name of Service (/), EMD number including coupon number As defined.x99/ EXCESS BAGGAGE / C1

329 JPSC/27 PSC/29 Oct 07 Attachment: L Page: NOTIFICATION OF EMD FOR ADDITIONAL SERVICES OTHER THAN OPTIONAL SERVICES Use SSR ESVC for EMD notifications for Additional Services (other than Optional Services, as specified in AIRIMP 3.19). The SSR ESVC is flight-related, always contains the status code HK, and is used only to advise that an EMD has been issued. An EMD in an SSR ESVC is issued only by an airline. Note: SSR ESVC is mutually exclusive of the SSR ASVC process Rules of Usage i. Unless otherwise specified, standard SSR rules apply. ii. An SSR ESVC is used to indicate that an EMD has been issued for other than Additional Services. iii. Each SSR ESVC element may be name associated and only to a single passenger. In a multi-name PNR, the SSR and its associated SSR ESVC elements must be name associated. iv. If an SSR ESVC service would apply to more than one passenger name, there must be a separate SSR ESVC for each passenger name. v. SSR ESVC must be segment related. vi. The SSR ESVC includes the EMD number and the appropriate coupon number. vii. An SSR ESVC always contains an HK status code Example Message from Member issuing EMD for excess baggage on connecting fights. HDQRMCX.HDQRMSQ HDQSQQWERTY82B9/ /CTD/1S/T/BO/RAY 2TAYLOR/GEORGEMR/JANEMRS SQ987Y14MAY SINPEK HK2 CX 0202Y14MAY PEKCDG HK2 / SSR ESVC CX HK1 PEKCDG 0202Y14MAY-1TAYLOR/GEORGEMR.X99/EXCESS BAGGAGE/ SSR ESVC CX /// C Special Service Requirement Codes Notification of EMD for Additional Services Other than Optional Services ESVC 7.2 PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (DECODING) ESVC.Notification of EMD for Additional Services Other than Optional Services

330 JPSC/27 PSC/29 Oct 07 Attachment: M Page: 1 of 3 AIRIMP changes Instructions for Transmission of SSR Codes SSR CODE ACTION CODE REPLY AUTOMATED FORMAT FREE TEXT IN REQUEST FREE TEXT IN REPLY/CANCEL AVML (5) Mandatory Mandatory Mandatory Not permitted Not permitted BBML (5) Mandatory Mandatory Mandatory Not permitted Not permitted BLML (5) Mandatory Mandatory Mandatory Not permitted Not permitted FPML (5) Mandatory Mandatory Mandatory Not permitted Not permitted GFML (5) Mandatory Mandatory Mandatory Not permitted Not permitted HFML (3) Mandatory Mandatory Mandatory Not permitted Not permitted LFML (5) Mandatory Mandatory Mandatory Not permitted Not permitted LPML (3) Mandatory Mandatory Mandatory Not permitted Not permitted LSML (5) Mandatory Mandatory Mandatory Not permitted Not permitted NLML (5) Mandatory Mandatory Mandatory Not permitted Not permitted ORML (3) Mandatory Mandatory Mandatory Not permitted Not permitted PRML (3) Mandatory Mandatory Mandatory Not permitted Not permitted RVML (5) Mandatory Mandatory Mandatory Not permitted Not permitted SPML (5) Mandatory Mandatory Mandatory Mandatory Optional VGML (5) Mandatory Mandatory Mandatory Not permitted Not permitted VJML (4) Mandatory Mandatory Mandatory Not permitted Not permitted VLML (5) Mandatory Mandatory Mandatory Not permitted Not permitted VOML (4) Mandatory Mandatory Mandatory Not permitted Not permitted (3) (4) (5) Not valid for flights departing on/after 1 June 2009 Valid for flights departing on/after 1 June 2009 See encode/decode section and 7.2 for updated meal definitions for flights departing on/after 1 June 2009

331 JPSC/27 PSC/29 Oct 07 Attachment: M Page: Special Service Requirement Codes... (1) (3) Asian vegetarian meal. AVML... (1) (4) Baby Meal BBML... (1) (4) Bland meal BLML (1) (3) Bland/soft meal.blml... (1) (3) Fruit platter... FPML (1) (4) Fruit platter meal.. FPML (1) (3) Gluten free meal.. GFML (1) (4) Gluten intolerant meal.. GFML (1) (3) High Fibre meal HFML... (1) (3) Infant/Baby food... BBML... (1) (3) Low-cholesterol, low fat meal... LCML (1) (4) Low fat meal. LCML (1) (4) Low lactose meal. NLML (1) (3) Low protein meal...lpml (1) (3) Low purin. PRML (1) (3) Low sodium no salt added meal...lsml (1) (4) Low salt meal LSML... (1) (3) Non lactose meal. NLML... (1) (3) Oriental mealorml... (1) (3) Raw vegetarian meal... RVML... (1) (4) Special meal SPML Special meal requirement not covered by specific code (to (1) (3) be followed by details).spml... (1) (4) Vegetarian Hindu meal.avml (1) (4) Vegetarian Jain meal VJML (1) (3) Vegetarian meal (lacto-ovo)..vlml (1) (3) Vegetarian meal (non dairy).vgml (1) (4) Vegetarian lacto-ovo meal VLML (1) (4) Vegetarian Oriental meal. VOML (1) (4) Vegetarian Raw mealrvml (1) (4) Vegetarian vegan meal VGML... (1) (3) (4) Only requests for SPML may contain specific food items Not valid for flights departing on/after 1 June 2009 Valid for flights departing on/after 1 June 2009

332 JPSC/27 PSC/29 Oct 07 Attachment: M Page: PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (DECODING)... (1) (3) AVML.Asian vegetarian meal (1) (4) AVML Vegetarian Hindu meal... (1) (3) BBML.Infant/baby food (1) (4) BBML.Baby meal... (1) (3) BLML.Bland/soft meal (1) (4) BLML.Bland meal... (1) (3) FPML.Fruit Platter (1) (4) FPML.Fruit Platter meal... GFML (1) (3)..Gluten free meal GFML (1) (4)..Gluten intolerant meal... (1) (3) HFML.High fibre meal... LFML (1) (3)...Low cholesterol, low fat meal LFML (1) (4)...Low fat meal... LPML (1) (3)..Low protein meal... (1) (3) LSML.Low sodium, no salt added meal (1) (4) LSML.Low salt meal... NLML (1) (3)..Non lactose meal NLML (1) (4)..Low lactose meal... (1) (3) ORML.Oriental meal... (1) (3) PRML.Low purin meal... (1) (3) RVML.Raw vegetarian meal (1) (4) RVML.Vegetarian raw meal... (1) (3) SPML.Special (1) (4) SPML.Special... (1) (3) VGML.Vegetarian (1) (4) VGML.Vegetarian (1) (3) VLML.Vegetarian (1) (4) VLML.Vegetarian (1) (4) VJML.Vegetarian (1) (4) VOML.Vegetarian meal requirement not covered by specific code (to be followed by details) meal meal (non-dairy) vegan meal meal (lacto-ovo) lacto-ovo meal Jain meal oriental meal (1) (3) (4) Only requests for SPML may contain specific food items Not valid for flights departing on/after 1 June 2009 Valid for flights departing on/after 1 June 2009

333 JPSC/27 PSC/29 Oct 07 Attachment: N Page: 1 of 1 Airport Services Committee (ASC) Membership 2008 Airline Traffic Conference Area Term of Office Expires Air France Alitalia American Airlines (Chairman) Austrian Airlines British Airways Egyptair El Al Iberia Japan Airlines KLM Lufthansa (Vice Chairman) Malev Northwest Airlines Qantas Saudia Arabian South African USAirways United Airways

334 JPSC/27 PSC/29 Oct 07 Attachment: O Page: 1 of 1 DCS Messages Working Group (DCSMWG) Terms of Reference Evolving DCS related Electronic Ticketing and Reservations issues require that DCS experts meet with the following terms of reference, which set out the objectives, and scope of the DCS Message Working Group. The Working Group will: review, amend, and synchronise DCS messages in Recommended Practices c with the work in other, associated IATA passenger and baggage working groups, such as the Reservations Committee and the Joint ATA/IATA Passenger Ticketing Committee; monitor and support industry security related activities to include APIS requirements and AVSEC/WG; continue to refine and update the documentation of DCS messages in Recommended Practices c to fully utilise the DCS Message Dictionary and Message Directory documented in Recommended Practices 1707a and 1707b; continue to review the editorial process of the DCS messages and continually edit them for precision; seek expanded airline participation in the DCSMWG by experts in across the fields of DCS and reservations; report their progress to the Airport Services Committee (ASC) once a year and seek approval of their work for subsequent submission to each year s PSC.

335 JPSC/27 PSC/29 Oct 07 Attachment: P Page: 1 of 1 ACI/IATA/ATA Baggage Working Group Terms of Reference The Baggage Working Group (BWG) shall: Consist of representatives from ATA/IATA carriers, ACI Airport members and participants in the IATA Partnership Programme with an interest in baggage management. Review and develop recommendations in the form of amended or new Resolutions and Recommended Practices. Report to the Airport Services Committee that will consider proposed amendments to current ATA/IATA Resolutions and Recommended Practices as well as new submissions Review and develop messages for baggage handling. Review and develop processes for baggage handling. Review and improve relevant Resolutions and Recommended Practices, especially relating to baggage messages and baggage processes. Review and improve relevant Resolutions and Recommended Practices with respect to reducing interline baggage mishandling. Identify any cross-functional issues related to baggage handling that need to be resolved outside the BWG. Align and cooperate with other industry working groups that are touching on baggage issues. Identify gaps in industry standards related to baggage handling that need to be resolved outside the BWG. Utilise electronic and/or other means of communication wherever possible and meet only when necessary. Such formal meetings should not exceed two per year. The IATA contact for BWG matters is the IATA Manager, Airport Services

336 JPSC/27 PSC/29 Oct 07 Attachment: Q Page: 1 of 1 Process Sub Group (PSG) Terms Of Reference The Process Sub Group (PSG) will report to the Baggage Working Group. The PSG will: Describe the Automated Baggage Handling Processes and process steps and their information requirements in RP1800 in relation to baggage messages as stated in RP1745 Address any cross-functional issues related to RP1800 as directed by the Baggage Working Group Address gaps in industry standards related to RP 1800 as directed by the Baggage Working Group. The BWG will prioritize the PSG workload. Participation in the PSG is per IATA/ATA rules and regulations.

337 JPSC/27 PSC/29 Oct 07 Attachment: R Page: 1 of 1 TICKETING COMMITTEE (PFPC) MEMBERSHIP Airline Traffic Conference Area Year Term of Office Expires at Conclusion of Passenger Services Conference: Air Canada Air France American Airlines British Airways Continental Delta Air Lines Egyptair Emirates Icelandair Japan Airlines KLM Lufthansa SAS South African Airways United Airlines US Airways Virgin Atlantic vacant

338 JPSC/27 PSC/29 Oct 07 Attachment: AA Page: 1 of 1 IATA Reservations Committee Membership Airline TC area Year Term of Office Expires Air Canada (AC) Air France (AF) All Nippon Airways (NH) British Airways (BA) Continental Airlines (CO) Delta Air Lines (DL) Egyptair (MS) Iberia (IB) Japan Airlines (JL) KLM (KL) Lufthansa (LH) Northwest Airlines (NW) Scandinavian Airlines System (SK) United Airlines (UA) Virgin Atlantic (VS) vacant- -vacant- -vacant-

339 JPSC/27 PSC/29 Oct 07 Attachment: BB Page: 1 of 1 RESWG Work plan Topic Progress Next Steps Action by 1 AIRIMP Audit and Clean-up 2 Standard Construction Rules for SSR Elements 3 Optional Services Ongoing item Ongoing item layout of the chapter and the matrix of the SSR codes is outstanding Completed Future RESWG and ResCom meetings as appropriate. Should any member have additional suggestions for amendments, to IATA. Future RESWG meeting Invite members of EMDWG to discuss the use of EMD for payment of something other than an Optional Services. RESWG to develop a message for the PNR to advise EMD number. All All EMDWG & RESWG Target Date RESWG/7

340 JPSC/27 PSC/29 Oct 07 Attachment: CC Page: 1 of 26 Editorial amendments to the AIRIMP manual Item 2 Change: AIRIMP 30th Edition / Page Spaces shown in message formats examples in this book are meant.. Item 3 Change: AIRIMP 30th Edition / Page When airlines and/or CRS Suppliers bilaterally or multilaterally agree to exchange information in interline messages, it is recommended that those standard formats be established as message standards or exceptional message standards in AIRIMP. for usage by these airlines or CRS Suppliers. Item 4 Change: AIRIMP 30th Edition / Page RULES FOR BOOKING A MEMBER S SPACE Item 5 Change: AIRIMP 30th Edition / Page (b) if you do not havedetails in accordance with the rules outlined diagrammed in Diagrammatic Rules Diagram for... Item 8 Change: AIRIMP 30th Edition / Page RULES FOR CANCELLING ALL OF ANOTHER MEMBER S SPACE

341 Item 9 Change: AIRIMP 30th Edition / Page RULES FOR ITINERARY CHANGING Item 11 Change: AIRIMP 30th Edition / Page Action by Member Changing Schedule Action by Member when Space is Held Item 12 Change: AIRIMP 30th Edition / Page Action by Member Changing Schedule Action by Member when Space is Not Previously Confirmed or Reported Item 13 Change: AIRIMP 30th Edition / Page or an oblique M (/M) if negative, use negative. Use the appropriate. Item 14 Change: AIRIMP 30th Edition / Page Action by Member or CRS Supplier Action when Receiving Advice of Schedule Change Upon advice of schedule change.and/or ticketing purposes will and take the following action actions. Item 16 Change: AIRIMP 30th Edition / Page 9 CHAPTER 2 STANDARD MESSAGE COMPOSITION PROCEDURES CHAPTER 2 STANDARD MESSAGES: COMPOSITION

342 Item 17 Change: AIRIMP 30th Edition / Page The Standard Message Composition Procedures apply to all types of reservation messages except for the availability status and PTA messages applies to the messages described in AIRIMP Sections 2, 3, 8 and 9. Item 18 Change: AIRIMP 30th Edition / Page Diagrammatic Illustration of Reservations Message Elements and Sequence: Note: These standard elements appear, when applicable, in the sequence shown in this list. Item 19 Change: AIRIMP 30th Edition / Page Reference Receiving System s Record Locator (as bilaterally agreed): Secondary Record Locator (as bilaterally agreed): Item 21 Change: AIRIMP 30th Edition / Page MESSAGE IDENTIFIER ELEMENT Message Identifiers, when required, must appear as the first line of the message text. For rules Refer to Sections 7 and 8 for lists of Message Identifiers used in AIRIMP messages. Rules and examples, see Message Identifiers and Chapter 4 Availability Status Messages. examples are shown in individual AIRIMP Sections. Message Identifiers are administered by the IATA Systems and Communications Reference (SCR) Manual. Item 22 Change: AIRIMP 30th Edition / Page Construction The first basic element of the message text is the Record Locator. and it consists of the Booking Office (mandatory) Location of Record and Point of Sale Information. It consists of the Booking Office (mandatory), Location of Record, and Point of Sale Information. A message may contain a primary record locator (mandatory) and a secondary record locator (as bilaterally agreed). The A complete Record Locator may not exceed 69 characters Construction Note to Editor: note that commas are included in the underlined portion.

343 Item 23 Change: AIRIMP 30th Edition / Page Receiving System s Record Locator Element Secondary Record Locator Secondary Record Locator (Bilateral) (Note: bilateral agreement required.) Item 24 Change: AIRIMP 30th Edition / Page The office having to reply/refer/respond to a message. The receiving/replying replying/referencing/responding system can transmit its own Record Locator as a secondary record locator together with the. Item 25 Change: AIRIMP 30th Edition / Page When.. A child will always require requires a seat......for an infant not occupying a seat (see 3.16)...for a child (see 3.17). Item 27 Change: AIRIMP 30th Edition / Page Sequence of Components Construction Item 28 Change: AIRIMP 30th Edition / Page When an itinerarysegment continuity (see Message Illustrating an see 3.1.6, Incomplete Itinerary ). Item 29 Change: AIRIMP 30th Edition / Page AUXILIARY SERVICE ELEMENT The Auxiliary Service three-letter.. (a) Note 1: All Members.. (b) Note 2: A scheduled Air Taxi.. (c) Editor: move para here, as point (c) (d) Editor: move para here, as point (d) (e) Seven formats are acceptable for transmitting Auxiliary Service elements: ATX Air Taxi CAR Car Rental CCR Car Rental HTL Hotel Accommodation HHL Hotel Accommodation CAR Car Rental CCR Car Rental SUR Surface (ship, rail, bus, etc.) TUR Tour (sightseeing, etc.) Note to Editor: after you move and into this new location, then delete the para header for

344 Item 35 Change: AIRIMP 30th Edition / Page OSI should only be used only if an SSR code is not available. Item 36 Change: AIRIMP 30th Edition / Page General Construction Rules Item 37 Change: AIRIMP 30th Edition / Page Construction and Sequence of Components (see Matrix in for specific guidelines applying to each SSR code) Construction of SSR Note: See Matrix of SSR Codes in for specific guidelines applicable to each SSR code. Item 38 Change: AIRIMP 30th Edition / Page Matrix Instructions for Transmission of SSR Codes Matrix of SSR Codes Item 46 Change: AIRIMP 30th Edition / Page 65 CHAPTER 3 RULES AND EXAMPLES CHAPTER 3 STANDARD MESSAGES: PROCEDURES AND EXAMPLES The examples, rules All categories of messages are composed as with the Elements outlined in Chapter 2 Standard Message Messages: Composition Procedures (a) For rules (b) For rules (c) For rules Note to Editor: Delete paragraphs / / Item 47 Change: AIRIMP 30th Edition / Pages SOLD OR REQUEST SELL/SOLD/REQUEST MESSAGES Sold/Request Message Involving Two Segments Message Illustrating Separate Arrival Element and Supplementary Element Sold Arrival Element with Request, and a Supplementary Element Multiple Segment Sold/Sell Message Segments

345 Item 48 Change: AIRIMP 30th Edition / Page Messages Illustrating the Use of an Action Identifier Segments Message Illustrating a Gap in an Itinerary Message Illustrating an Incomplete Itinerary Message Requesting Request Specific Alternative Flights Message Requesting FRAV First Available (FRAV) Segments Message Illustrating Flight Reconfirmation (See Recommended Practice 1762) Flight Reconfirmation Note: See Recommended Practice Advice of Ticket Number Automated and Manual (bilateral agreement only) Advice of Ticket Number Automated and Manual (Bilateral) (Note: bilateral agreement required.) Item 49 Change: AIRIMP 30th Edition / Page (c) Message to American Airlines: Item 50 Change: AIRIMP 30th Edition / Page Example 14: Ticketed by CRS/GDS Item 52 Change: AIRIMP 30th Edition / Pages REPLY MESSAGES 3.2 REPLIES TO SELL OR REQUEST MESSAGES Message Confirming Space Message Replying to Request for Specific Alternative Flights

346 3.2.4 Message Confirming Alternative Space or in reply to a message requesting FRAV Confirming Alternative Space or Replying to a Request for FRAV Message Advising Space Unable and Volunteering FRAV Message Advising Flight Not Operating Message Advising Unable to Accept Sale Message Advising that Part of a Group may be Confirmed (optional procedure) Advising that Part of a Group may be Confirmed Note: this is an optional procedure Message Replying to an SSR Request Message Referring to an OSI Message Confirming from Waitlist New Booking Message Confirming Waitlist Segment in a New Booking Message Including the Receiving System s Record Locator Item 53 Change: AIRIMP 30th Edition / Pages When only an SSR Request is to be cancelled, the automated SSR format should be used Message Combining Cancel and Sell Message Adding Message Cancelling Space and Involving New First Boarding Point Message Combining Cancel and Sold (or Request) Involving New First Boarding Point Combining Cancel/Sold/Sell/Request and New First Boarding Point Message Combining a Conditional Cancellation and a Request with the same Boarding Point Message Cancelling Messages Booking Space and Cancelling/Booking SSR Elements by a Member (bilateral agreement only) Booking Space and Cancelling/Booking SSR Elements by a Member (Bilateral) (Note: bilateral agreement required.) Partial Cancellation of Services (where bilaterally agreed) Partial Cancellation of Services (Note: bilateral agreement required.)

347 Item 54 Change: AIRIMP 30th Edition / Page Examples of Dividing Party Messages Examples of Messages Dividing Party Existing reservations... 1 CLARK/R 1GRANT/U 1LEE/R 1THOMPSON/H 1CLARK/R 1GRANT/U 1LEE/R 1THOMPSON/H Item 55 Change: AIRIMP 30th Edition / Pages MESSAGES CHANGING NAME AND/OR NUMBER OF PASSENGERS (OPTION 1) 3.5 CHANGING NAME AND/OR NUMBER OF PASSENGERS OPTION 1 Note to Editor: delete the 2-line Note: which appears beneath the para 3.5 title Message Involving a Change in the Passenger Names(s) Non-Group PNR (nongroup) Message Involving Segment Status Change Message Involving an Increase in the Number of Passengers Message Involving a Decrease in the Number of Passengers Decrease Number in Party by Member (Bilateral agreement only) Decrease Number in Party by Member (Bilateral) Note: bilateral agreement required Message Providing Individual Message Involving a Change in the Passenger Message Involving an Increase Message Involving a Decrease Message Involving a Change in Itinerary Message Involving Change of Itinerary

348 Item 56 Change: AIRIMP 30th Edition / Pages MESSAGES CHANGING NAME AND/OR NUMBER OF PASSENGERS (OPTION 2) 3.6 CHANGING NAME AND/OR NUMBER OF PASSENGERS OPTION Message Involving a Change in the Passenger Name(s) Message Involving Segment Status Message Involving an Increase in the Number of Passengers Message Involving a Decrease in the Number of Passengers without Name Change Reduce Decrease Number in Party Transactions Name Change and Adding/Cancelling a Segment(s) Item 57 Change: AIRIMP 30th Edition / Pages Message Identifiers (for reservations use) Message Identifiers for Reservations Use AVC...Car availability status message (see , Availability Status Messages (Cars) ) AVC...Car availability status message (see , Car Availability Status Messages ) Message Identifiers (inserted by communications only) Message Identifiers for Communications Use Note: these message identifiers are inserted into messages only by Communications processors Message Identifiers (for PTA messages) Message Identifiers for PTA Use Record Locator Change For PNR(s) Transferred From One System to Another System (NRL) New Record Locator (NRL) in PNR Migration

349 Item 58 Change: AIRIMP 30th Edition / Page Client Identification Procedures (bilateral agreement only) Client Identification Procedures (Bilateral) Note: bilateral agreement required. 3.9 GENERAL RULES FOR SENDING A REQUEST FOR CLARIFICATION. Item 60 Change: AIRIMP 30th Edition / Pages FORM OF IDENTIFICATION INFORMATION (as bilaterally agreed) 3.10 FORM OF IDENTIFICATION INFORMATION (Bilateral) Note: bilateral agreement required AUTHORISE PNR FOR TICKETING (as bilaterally agreed) 3.11 AUTHORISE TICKETING OF PNR (Bilateral) Note: bilateral agreement required MANDATROY FARE QUOTE AND ENFORCED TICKET TIME LIMIT TIME LIMIT AUTO CANCEL (for Exemption) 3.12 TIME LIMIT AUTO-CANCEL EXEMPTION 3.13 ADVANCED PASSENGER INFORMATION API Information should be. The supplementary element Special Service Requirement (SSR) follows the general construction rules as stated in through Item 61 Change: AIRIMP 30th Edition / Page ELECTRONIC PAYMENT AUTHORISATION (as bilaterally agreed) 3.14 ELECTRONIC PAYMENT AUTHORISATION (Bilateral) Note: bilateral agreement required.

350 Item 62 Change: AIRIMP 30th Edition / Page AUTOMATED BLOCK SPACE (for bilateral use only) 3.15 AUTOMATED BLOCK SPACE (Bilateral) Note: bilateral agreement required. Provides messaging between a Member s reservation system and a Block Owner to automate and control request made by wholesalers (consolidators, tour operators, cruise lines, etc.), giving them the capability to manage the Member s seats in block allocations. Provides messaging between a Member s reservation system and a Block Owner to automate and control requests for space, and to manage block allocations. The following are the message identifiers used in automated block space messaging: 1. AAK Reply from Member 2. AKD Message from.. 3. AKI Message from. 4. AKK Message from.. 5. ASA Message from.. 6. CRA Request to Member.. 7. DEC Request to Member.. 8. INC Request to Member.. 9. UPD Request to Member.. The following message identifiers (with AIRIMP references) are used in automated block space messaging: AAK Response to Block Owner Requests (see ) AKD Decrease Block Space Allocation by Member (see ) AKI Increase Block Space Allocation by Member (see ) AKK Create Block Space Allocation by Member (see ) AKK Update Block Space Allocation by Member (see ) ASA Re-accommodation of Block Space Allocation by Member (see ) CRA Create Block Space Allocation by Block Owner (see ) DEC Decrease Block Space Allocation by Block Owner (see ) INC Increase Block Space Allocation by Block Owner (see ) UPD Update Block Space Allocation by Block Owner (see )

351 Item 63 Change: AIRIMP 30th Edition / Pages AAK Reply from Member AAK Response to Block Owner Requests Definition An AAK reply message is sent by the Member to the Block Owner in response AKD Message from AKD Decrease Block Space Allocation by Member An AKD message is sent by the Member to the block owner to advise of a decrease of an existing block space allocation, as initiated by the Member AKI Message from AKI Increase Block Space Allocation by Member Definition An AKI message is sent by the Member to the Block Owner to advise of an the increase of an existing block space allocation, as initiated by the Member AKK Message from AKK Create Block Space Allocation by Member Definition An AKK message is an advisory message sent by the Member to the Block Owner at the time AKK Message from AKK Update Block Space Allocation by Member Definition An AKK message is sent by the Member to the Block Owner to advise of subsequent updates to an existing block space allocation ASA Message from ASA Re-accommodation of Block Space Allocation by Member Definition An ASA message is an advisory message sent by the Member to the Block Owner when an existing block space allocation has been affected by a schedule change reaccommodation re-accommodated as the result of the Member s schedule change CRA Request to Member CRA Create Block Space Allocation by Block Owner Definition A CRA request message is sent to the Member by a Block Owner to the Member at the time of an initial block space allocation request. A CRA message is never sent by the Member but is only sent sent only by a Block Owner.

352 Item 64 Change: AIRIMP 30th Edition / Pages DEC Request to Member DEC Decrease Block Space Allocation by Block Owner Definition A DEC request message is sent to the Member by a Block Owner to the Member to request a decrease in the size of an existing block space allocation. A DEC message is sent only sent by the Block Owner INC Request to Member INC Increase Block Space Allocation by Block Owner Definition An INC request message is sent to the Member by a Block Owner to the Member requesting to request an increase in the size of an existing block space allocation. An INC message is sent only sent by the Block Owner UPD Request to Member UPD Update Block Space Allocation by Block Owner Definition A UPD request message is sent to the Member by a Block Owner to the Member to request an update of optional parameters for an existing block space allocation. A UPD message is sent only sent by the Block Owner Message Exchange Examples Booking message from Block Owner to the Member: Message Examples: Block Owner to Member Message Exchange Examples Booking message from Block Owner to the Member: Message Examples: Member to Block Owner Item 66 Change: AIRIMP 30th Edition / Page Irregular Operations Messages (IRP) (bilateral agreement only) 3.18 IRREGULAR OPERATIONS MESSAGES (IRP) (Bilateral) (This is valid only for Member-to-Member communication) Note 1: bilateral agreement required. Note 2: this is valid only for Member-to-Member communication.

353 Item 67 Change: AIRIMP 30th Edition / Pages COMPONENTS AND SEQUENCE OF SEGMENT STATUS MESSAGES 4.3 COMPONENTS AND SEQUENCE OF FIRST CLOSING MESSAGES Meaning of C Status Code Meaning of AS Status Codes AS Status Code Meaning of L Status Codes Meaning of LA Status Code Item 68 Change: AIRIMP 30th Edition / Pages NUMERIC AVAILABILITY STATUS MESSAGES (BILATERAL AGREEMENT ALTERNATIVE 1) 4.5 NUMERIC AVAILABILITY STATUS MESSAGES OPTION 1 (Bilateral) Note: bilateral agreement required Numeric Availability Status Message Identifier Construction Components and Sequence of Numeric Status Messages Meaning of A Numeric Meaning of L Numeric Numeric Availability Status Messages Examples

354 Item 69 Change: AIRIMP 30th Edition / Pages NUMERIC AVAILABILITY STATUS MESSAGES (BILATERAL AGREEMENT ALTERNATIVE 1) 4.6 NUMERIC AVAILABILITY STATUS MESSAGES OPTION 2 (Bilateral) Note: bilateral agreement required Construction Components and Sequence of Numeric Status Messages The above example shows that on KL641 0 (zero) seats are available in B class while five seats were available. In C class seven seats are available while three seats were available. In F class two seats are available while one seat was available and in M class five seats are available while four seats were available. The above example shows that on KL641 zero (0) seats are available in B class, while five (5) seats were previously available. In C class, seven (7) seats are available while three (3) seats were previously available. In F class, two (2) seats are available, while one (1) seat was available. In M class, five (5) seats are available, while four (4) seats were previously available. Other numeric examples: 26.now 2 seats available; previously 6 34.now 3 seats available; previously 4 82.now 8 seats available; previously 2 Item 70 Change: AIRIMP 30th Edition / Pages CODE-SHARE NUMERIC AVAILABILITY STATUS MESSAGES (BILATERAL AGREEMENT ALTERNATIVE 3) 4.7 NUMERIC AVAILABILITY STATUS MESSAGES OPTION 3 Option 3 is for code share flights. There are three (3) message types: Components and Sequence of the Construction of an AVA Status Message Components and Sequence for Construction of an AVA Cancellation Message Components and Sequence for Recap Request Message (RVR) Sent by the Marketing Carrier to the Operating Carrier Construction of an RVR Recap Request Message This message is sent by the Marketing Carrier to the Operating Carrier. An RVR message Components and Sequence for a AVR Recap Response Message (AVR) Sent by the Operating Carrier to the Marketing Carrier Construction of an AVR Recap Response Message This message is sent by the Operating Carrier to the Marketing Carrier. AVR messages shall

355 Item 71 Change: AIRIMP 30th Edition / Pages SELECTIVE QUERY AVAILABILITY STATUS MESSAGES (bilateral agreement only) 4.8 SELECTIVE QUERY AVAILABILITY STATUS MESSAGES (Bilateral) Note: bilateral agreement required Definition of Selective Query Availability Components and Sequence of Segment Status Messages Construction Examples of Selective Query Availability Status Messages Components and Sequence of Enhanced Availability Data Messages Construction Update Message Enhanced AVS Data Delete Message Enhanced AVS Data Item 72 Change: AIRIMP 30th Edition / Pages CONSTRUCTION OF PREPAID TICKET ADVICE MESSAGE (PTA) Components Construction 5.2 CONSTRUCTION OF ACKNOWLEDGEMENT MESSAGE Components Construction 5.3 CONSTRUCTION OF MESSAGE INVOLVING PARTIAL REFUND OR OVER COLLECTION MESSAGE Components Construction 5.4 CONSTRUCTION OF MESSAGE INVOLVING FULL REFUND MESSAGE Components Construction 5.5 CONSTRUCTION OF MESSAGE REQUESTING FURTHER INFORMATION/ACTION REQUEST MESSAGE Components Construction 5.6 CONSTRUCTION OF MESSAGE SUPPLYING SUPPLEMENTARY INFORMATION OR REPLY TO REQUEST FOR SUPPLY FURTHER INFORMATION/ACTION Components Construction Prepare a message supplying further information in the following sequence using block format, starting each element on a new line. This can be an unsolicited message or a reply to a request for further information/action (see 5.5). 5.7 CONSTRUCTION OF MESSAGE SENDING AN ADDITIONAL COLLECTION PTA MESSAGE Components Construction 5.8 PREDESIGNATED PTA POINTS FOR PTA

356 Item 73 Change: AIRIMP 30th Edition / Page 217 CHAPTER 6 SCHEDULE EXCHANGE DATA MESSAGE MESSAGES Item 74 Change: AIRIMP 30th Edition / Pages CHAPTER 7 CODES AND ABBREVIATIONS FOR STANDARD AIRIMP MESSAGES CHAPTER 7 STANDARD MESSAGES: CODES AND ABBREVIATIONS Note: Refer to Sections 8.20 and 8.21 for Codes and Abbreviations for Exceptional AIRIMP Messages. 7.1 PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (CODING) 7.1 ENCODING Reservations Booking Designators (RBD) Advice Codes (these advice codes are to be initiated exclusively by the company who is in control of the inventory) Advice Codes Note: advice codes are to be initiated exclusively by the company who is in control of the inventory. Item 75 Change: AIRIMP 30th Edition / Page 220, star footnote at bottom of page. Note to Editor: note italics within the footnote. When any segment specified in message commences on your airline at your city and you have no record immediately no record, immediately reserve.clearing subsequent HK, HN and HL segments) and notify sender of message this action. accordingly. Item 76A Change: AIRIMP 30th Edition / Page Message Identifiers (for PTA messages) Message Identifiers Note: Message Identifiers are administered by the IATA Systems and Communications Reference (SCR) Manual Communications Note: refer to Section and the IATA SCR Manual. Correction to previous message.. COR Possible duplicate message. PDM

357 PTA Note: refer to Chapter 5. Acknowledgement... ACK Message Identifiers (for reservations use) Reservations Note: refer to Chapters 2 and 3. Advice of medical case Message Identifiers (for block space management) Correction to previous message.. COR Message from Member Message form Member. Message from Member Message form Member. Possible duplicate message Reply from Member Reply to Member Reply to Member Reply to Member Reply to Member CRA Correction to previous message.. COR Note to Editor: Replace above deleted lines with: Block Space Note: refer to Section 3.16 Create Block Space Allocation by Block Owner. CRA Create Block Space Allocation by Member AKK Decrease Block Space Allocation by Member... AKD Increase Block Space Allocation by Member. AKI Re-accommodation of Block Space Allocation by Member... ASA Decrease Block Space Allocation by Block Owner... DEC Increase Block Space Allocation by Block Owner INC Update Block Space Allocation by Block Owner.. UPD Response to Block Owner Requests... AAK Update Block Space Allocation by Member... AKK Item 76B Change: AIRIMP 30th Edition / Page Auxiliary Service Identifiers Auxiliary Service Note: refer to Section 2.10 Air Taxi Electronic Ticket (Note: refer to Chapter 9.) Electronic ticket/miscellaneous document exchange/re-issue.. ETE Electronic ticket/miscellaneous document issuance. ETK Availability Status (Note: refer to Chapter 4) Enhanced availability data AVO First closing... AVS Numeric Option 1.. AVN Numeric Option 2.. MAS RBDs by compartment.. AVA Recap request RVR Recap response.. AVR Segment. AVS

358 Item 78 Change: AIRIMP 30th Edition / Page Supplementary Item Identifiers and Element Codes Identifiers Special Service Requirement (SSR) Codes Frequent traveller mileage program FQTV 5 Frequent traveller service benefit FQTS 5 Note to Editor: Change all footnotes from stars to numerical footnotes. Item 79 Change: AIRIMP 30th Edition / Page 223, add this footnote beneath the two-star footnote. Note to Editor: this is a copy the footnote from page 237 (30 th Edition). 5 If code FQTS is not advised, FQTV may be assumed to be for both mileage accrual and service benefit. Item 80 Change: AIRIMP 30th Edition / Pages 223/224/225/234/235/236/237/238/239/240/241/242/243/244/245 Note to Editor: Change the text of footnote #2 on all pages in Section 7. Make all footnotes a numerical reference instead of stars. On all pages in Section 7, re-arrange the listed footnotes in numerical order. Only requests for SPML may contain specific food items. 2 Only SPML elements may contain specific food items. Item 81 Change: AIRIMP 30th Edition / Page Special Service Requirement Codes Stretcher passenger... STCR System cancel for electronic ticket (Refer to Chapter 9) TKNX Ticket numbers for automatically..

359 Item 82 Change: AIRIMP 30th Edition / Pages Hotel Abbreviations Element Codes General Codes Room Type/Rate/Room Qualifier Codes (directed to another airline) Room Type/Rate/Qualifier Codes Note: these codes are for use between airlines Room Type/Rate/Room Qualifier Codes ((directed to a hotel/motel operator unless otherwise agreed) Room Type/Rate/Qualifier Codes Note: these codes are for use between an airline/crs Supplier and a hotel/motel operator, unless otherwise agreed. Item 83 Change: AIRIMP 30th Edition / Page Car Rental Element Codes General Codes Car type codes (to be used in conjunction with Option 1) Note: to be used as Option-1 Car Type Codes Car type codes (to be used in conjunction with (b) Option 2, by selecting one character from each of the following sub-lists (a) through (d) in the order presented) Note: to be used as Option-2 Car Type Codes, by selecting one character from each of the following sub-lists (a) through (d) in the order presented Car rate types Item 84 Change: Pages Seat Month Miscellaneous. Traffic. TFC Transmission control number (ticketing)... TCN Travel Agent General SSR FOID Codes

360 Note to Editor: completely replace current sections / / / with all new text: Advanced Passenger Information (API) Codes SSR DOCS Codes Travel Document Type Codes Passenger Gender Codes SSR DOCO Codes Travel Document Type Codes SSR DOCA Codes Type of Address Codes Item 85 Change: AIRIMP 30th Edition / Pages PASSENGER RESERVATIONS CODES AND ABBREVIATIONS (DECODING) 7.2 DECODING Note: this section is an alphabetical listing of the codes that are listed by subject in Section 7.1. See Section 8.21 for the decoding of codes for Exceptional Messages. A.Aisle (seat request) AVN...Availability Status message identifier for Numeric Availability AVO...Availability Status message identifier for Enhanced Availability Data AVR...Availability AVSAvailability... AVSAvailability Status message identifier for First Closing messages AVTTour availability ETDEstimated time of departure ETESystem Cancel for electronic ticket exchange/re-issue (see Section 9) ETK...System Cancel for electronic ticket issuance (see Section 9) EWGN...Economy Stationwagon EWGN...Economy station wagon EXThe new carrier may use the electronic ticket coupon(s), exchange recommended FQTS 5..Frequent traveller service..