Data Application for Category 12 – Surcharges

DATA APPLICATION CATEGORY 12 – SURCHARGES

All rights reserved The information contained in this document is the property of ATPCO. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical, photocopying, recording, or otherwise, without the prior written permission of ATPCO. Under the law, copying includes translating into another language or format. Legal action will be taken against any infringement

DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

1.0 OVERVIEW ...... 4 1.1 DATA REQUIREMENTS ...... 4 1.2 BASIC PROCESSING OVERVIEW ...... 5 2.0 DEFINITIONS AND ASSUMPTIONS ...... 6 2.1 DEFINITIONS ...... 6 2.2 ASSUMPTIONS ...... 6 3.0 DETAILED FIELD PROCESSING ...... 7 4.0 PROCESSING ...... 10 4.1 APPLICATION OF DATA FOR SURCHARGE PROCESSING ...... 15 4.1.1 Date Range – Start Date (Bytes 14-19), Stop Date (Bytes 20-25) ...... 15 4.1.2 Time of Day – Start Time (Bytes 26-29), Stop Time (Bytes 30-33) ...... 17 4.1.3 Appl (Byte 34) ...... 19 4.1.4 Day of Week (Bytes 35-40) ...... 20 4.1.5 Surcharge Type (Byte 41) ...... 22 4.1.6 Equipment (Bytes 42-44) ...... 24 4.1.7 Surcharge Appl – Travel Portion (Byte 45) ...... 27 4.1.7.1 Fare Component (Value 1) ...... 35 4.1.7.2 Round Trip (Value 2) ...... 36 4.1.7.3 Transfer (Value 3) ...... 37 4.1.7.4 Ticket (Value 4) ...... 38 4.1.7.5 Coupon (Value 5) ...... 39 4.1.7.6 Direction (Value 6) ...... 40 4.1.7.7 Combination of Different Travel Portion Byte 45 Values ...... 42 4.1.8 Sector/Portion (Byte 46) ...... 43 4.1.9 From/To/Via – Geographic Specification Table No. 995 (Bytes 47-54) ...... 44 4.1.10 Between/And Geographic Specification Tables No. 995 (Bytes 55-62 and 63-70) ...... 50 4.1.10.1 Side Trip Surcharge (Surcharge Type byte 41 = value I) ...... 52 4.1.10.2 All Other (non-side trip) Surcharges (Surcharge Type byte 41 is NOT value I) ...... 55 4.1.11 Charges - Appl (Byte 71) ...... 59 4.1.12 Charges - 1st Currency Charge: Amount, First Currency, Decimal (Bytes 72-78, 79-81, 82) ...... 60 4.1.13 Charges - 2nd Currency Charge: Amount, Second Currency, Decimal (bytes 83-89, 90-92, 93) ...... 61 4.1.14 Charges - Percent (Bytes 94-100) ...... 62 4.1.15 Charges - Base (Byte 101) ...... 63 4.1.16 Override Date Table Number 994 (Bytes 102-109) ...... 64

Page E.03.12.2 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.17 Text Table Number 996 (Bytes 110-117) and Unavailable Data Tag (Byte 118) ...... 64 4.1.18 RBD (Bytes 119-120) ...... 65 4.1.19 Carrier/Flight Table 986 (Bytes 121-128) ...... 68 4.2 RECONCILIATION BETWEEN GENERAL AND FARE RULE LEVELS ...... 73 4.3 CATEGORY 12 VERSUS IF TO CATEGORY 4 ...... 74 5.0 TRAVEL SEGMENT INDICATOR (TSI) ...... 76 6.0 CODING CONVENTIONS ...... 78 6.1 WAIVER OF ADVANCED PURCHASE REQUIREMENTS OR MAXIMUM STAY ...... 78 6.2 WAIVER OF MINIMUM STAY ...... 82 6.3 SURCHARGE FOR PAPER TICKET ...... 83 6.4 PEAK TRAVEL TIME SURCHARGE TYPE ...... 85 6.5 TSIS ...... 85 6.6 BYTE 45 VALUE 2 (PER RT) ...... 85 7.0 TICKETING: Q PLACEMENT FOR CATEGORY 12 DATA ...... 86 7.1 POSITIVE SURCHARGES ...... 87 7.1.1 Travel Portion Value Blank, 1, or 2: “Per Fare Component” Surcharge ...... 88 7.1.2 Travel Portion Value 3: “Per Transfer” Surcharge ...... 98 7.1.3 Travel Portion Value 4: “Per Ticket” Surcharge...... 107 7.1.4 Travel Portion Value 5: “Per Segment” Surcharge ...... 112 7.1.5 Travel Portion Value 6: “Per Direction” Surcharge ...... 123 7.2 REDUCTIONS (NEGATIVE SURCHARGES) ...... 130

Page E.03.12.3 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

1.0 OVERVIEW

The surcharge category (Category 12) is used to define conditions when surcharges are applicable to the fare being validated as well as the corresponding charge. The following conditions may be used to define surcharge applicability: airport/terminal, business class, peak travel time, equipment, fuel, peak, holiday, side trip, seasonal, weekend, sleeperette, waiver for advance purchase requirements, security, maximum stay waiver, Reservation Booking Designator (RBD), navigation, miscellaneous/other.

If the category is not present or there are no provisions applicable to the given fare (as described by Record 2 match processing), either in the fare rule or general rule then there are no surcharges for the fare being validated.

1.1 Data Requirements

In order to validate Surcharges, it may be essential to know:

• All ticketed points on the fare component. • Day/Time of departure of each flight within the fare component. • Date of departure of each flight within the fare component. • Reservation Booking Designator (RBD) for the marketing carrier on each sector of the fare component. • Marketing carrier for each sector of the fare component. • Operating carrier for each sector of the fare component. • Flight number for each sector of the fare component. • Date of Ticket Issuance. • Equipment type for each flight within the fare component. • Type of passenger (adult or child). • Tariff applicable to the fare component being processed (for RTW/CT fares)

Page E.03.12.4 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

1.2 Basic Processing Overview

Match to the Category 12 Record 2 as described in Record 2 Processing.

Process all Category 12 tables in a subset, attempting to match the tables based on: • Override Date Table • Geographic Specification Table • Date of Travel • Time of Travel • Day of Week • Equipment • RBD • Marketing carrier • Operating carrier Yes • Flight number • Charges - Appl (byte 71) Is there a match to at least one Category 12 table in the subset?

Yes No

Accumulate and apply surcharges for all tables in the subset that match. Continue processing to the next subset. Do not continue processing to any Is there another subset? other subsets at this level.

Apply system assumption for this level - no surcharges.

Page E.03.12.5 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

2.0 DEFINITIONS AND ASSUMPTIONS

2.1 Definitions

Side Trip Travel from and/or to an enroute point of a fare component. Such travel is not charged separately. Routing restrictions or MPM must permit the side trip. Also know as Embedded Side Trip.

2.2 Assumptions

In the absence of Category 12 (Record 2 for Category 12 does not exist or no Record 3 is applicable at the fare rule or general rule level), the system assumption is that there are no surcharges for the fare being validated.

The application of surcharge data in Category 12 is based on the data in the Between/And Geographic Specification Tables (bytes 55- 70) and the value in Travel Portion Byte 45. The Between/And Geographic Specification Table indicate the match criteria validates within the specified geography. Travel Portion byte 45 indicates where to validate the match criteria (on the fare component or within the specified geography) and how to apply the surcharge amount. Dependent upon the value in Byte 45 and the Between/And Geographic Specification Tables: • Match criteria validates against the departure from the origin of the fare component or specified geography or the departure from intermediate points within the fare component or specified geography. • Surcharge amount applies to: • Per fare component; • Per Coupon or transfer (within the fare component); or • Per ticket or direction on the journey (for the same carrier, surcharge type, and geography).

Once a Category 12 data table is matched at either the fare rule or general rule level, then surcharges apply based on the Travel Portion value in Byte 45.

The absence of applicable Category 12 for side trips [Surcharge Type value I with data in the Between/And Geographic Specification Tables (Bytes 55-62, 63-70)] indicates that a side trip cannot be assessed as part of the through fare with a surcharge. Normal side trip fare construction principles apply.

Page E.03.12.6 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

3.0 DETAILED FIELD PROCESSING

Byte Location Match / Action Definition / Processing Byte 1 Key Match Indicates the Record number for which the data is formatted. RECORD TYPE Byte 2 Key Match Indicates the type of processing to be taken in connection with the transaction - either ACTION new data or cancelled data. Bytes 3-5 Key Match Indicates to what rule or footnote category the data applies. For Surcharges, it will CAT. NO. always be Category 12 (for fare or general rules). Bytes 6-13 Key Match Indicates a number that links the Category 12 Record 3 to the associated Category TBL. NO. Control Records (Record 2). Bytes 14-19 Match Indicates the earliest travel date for which the surcharge applies. START DATE Bytes 20-25 Match Indicates the latest travel date for which the surcharge applies. STOP DATE Bytes 26-29 Match Indicates the earliest flight departure time for which the surcharge applies. START TIME Bytes 30-33 Match Indicates the latest flight departure time for which the surcharge applies. STOP TIME Byte 34 Match Indicates whether the start/stop times apply daily or to the range of the days of the APPL week in bytes 35-40. Bytes 35-40 Match Indicates the day(s) of week for which the surcharge applies. DAY OF WEEK Byte 41 Match/Action Indicates the type of surcharge applicable to the fare being validated. SURCHARGE TYPE Bytes 42-44 Match Indicates the equipment type for which the surcharge is applicable. EQPT Byte 45 Action Identifies to which portion of travel the match fields are validated and the surcharge TRAVEL PORTION amount is assessed.

Page E.03.12.7 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Byte Location Match / Action Definition / Processing Byte 46 Match/Action Specifies whether the data in the Between/And Geo Spec Tables (bytes 55-70) applies SECTOR/PORTION to a sector or a portion of travel. (Data in this field is only applicable when Surcharge Type is not value I.) Bytes 47-54 Match/Action Identifies the surcharge applies to travel from/to/via a specific geographic point(s) or FROM/TO/VIA GEO portion(s) of travel. SPEC TABLE #995 Bytes 55-62 Match/Action For side trip surcharges (Surcharge Type value I): Identifies the terminal point (or BETWEEN GEO SPEC portion of travel) from which a side trip surcharge applies. TABLE #995 For all other surcharges (other than Surcharge Type value I): Identifies one end point of a portion of travel to which the surcharge applies. Bytes 63-70 Match/Action For side trip surcharges (Surcharge Type value I): Identifies the terminal point (or AND GEO SPEC portion of travel) to which a side trip surcharge applies. When used with Bytes 55-62 TABLE #995 (Between Geo Spec Table), the side trip surcharge applies between the portion of travel specified in the Bytes 55-62 and the portion of travel specified in Bytes 63-70. For all other surcharges (other than Surcharge Type value I): This is used in conjunction with the Between Geo Spec Table to identify the end points of a portion of travel to which the surcharge applies. Byte 71 Match Indicates to which passenger the surcharge applies. APPL Bytes 72-78 Action Indicates the amount of the surcharge to be assessed. AMT Bytes 79-81 Action Indicates the currency of the surcharge amount in bytes 72-78. 1st CURR Byte 82 Action Indicates the number of decimal places for the surcharge amount in bytes 72-78. DEC Bytes 83-89 Action Indicates the amount of the surcharge to be assessed. AMT Bytes 90-92 Action Indicates the currency of the surcharge amount in bytes 83-89. 2nd CURR Byte 93 Action Indicates the number of decimal places for the surcharge amount in bytes 83-89. DEC

Page E.03.12.8 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Byte Location Match / Action Definition / Processing Bytes 94-100 Action Indicates the percentage to be surcharged. PERCENT Byte 101 Action Indicates whether the percentage in Bytes 94-100 is to be applied to the fare. BASE Bytes 102-109 Match Refers to a number that defines reservation, ticketing and/or travel dates to which the OVERRIDE DATE surcharge applies. The Override Date Table data must match the reservation, ticketing TABLE #994 and/or travel dates of the itinerary being priced in order for the surcharge to be applied. Bytes 110-117 Action Refers to a table containing free-form text regarding Category 12. The information TXT TABLE #996 within this table is not priceable data. Byte 118 Action Identifies that this fare cannot be used for autopricing or that this Record 3 contains UNAVAIL only free-form text. Bytes 119-120 Match Indicates the Reservation Booking Designator (RBD) for which the surcharge is RBD applicable. Bytes 121-128 Match Refers to a table specifying the marketing carrier, operating carrier, and/or flight Carrier/Flight Table 986 number for which the surcharge is applicable

Page E.03.12.9 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.0 PROCESSING

Prior to processing the Surcharge Category, a Record 2 must be matched in order to determine the applicable Category 12 provisions for the fare being validated. After a Record 2 has been matched, the next step is to match to a Category 12 Record 3 Table based on all match fields. The relationship among all match fields is AND. When data is present in the following match fields, match validation must be against the same point on the fare component being validated: • Start/Stop Dates (bytes 14-25) • Start/Stop Time (bytes 26-33) • Appl (Byte 34) • Day of Week (Bytes 35-40) • Equipment Code (Bytes 42-44) • From/To/Via Geo Spec Table (Bytes 47-54) • RBD (bytes 119-120) • Carrier/Flight Table 986 (bytes 121-128)

Whether the match field data validate against the origin or intermediate points on the fare component being validated is dependent upon the value in Travel Portion Byte 45 and may be further defined by values in Equipment Code (Bytes 42-44), RBD (bytes 119- 120), Carrier/Flight Table 986 (bytes 121-128), and Geo Spec Tables (Bytes 47-54, 55-62, 63-70).

Category 12 processing steps: 1. Validate any external IF condition (matching the Record 2 and matching and validating the Record 3). 2. When an external IF condition exists and is matched (“passed”), then processing must live or die on the THEN portion of the set. Within the THEN/IF set, validate all Category 12 tables in a subset, accumulating and applying surcharges for all tables in the subset that match. a. If there is not a match to the subset, processing will attempt to validate another subset within the THEN portion of the THEN/IF set. If no further subsets exist or are matched, then apply system assumption (no surcharges). b. If at least one table in a subset has been matched, do not read on to any other subsets. 3. When an external IF condition exists but is not matched, then continue processing to another subset within the IF portion of the THEN/IF set. When no further subsets within the IF portion exist or are matched, continue processing to the next set. a. If no further subsets or sets exist or are matched, then apply system assumption (no surcharges). b. If a further subset or set exists and is matched, then process the Category 12 tables, accumulating and applying surcharges for all tables in a subset that match.

Page E.03.12.10 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

c. If there is not a match to the subset, continue processing to the next subset or set. d. If at least one table in a subset has been matched, do not read on to any other subsets. 4. When an external IF condition does not exist, then validate all Category 12 tables within a subset, accumulating and applying surcharges for all tables in the subset that match. a. If there is not a match to the subset, continue processing to the next subset. b. If at least one table in a subset has been matched, do not read on to any other subsets.

These steps are further explained and illustrated below.

Processing THEN/OR Sets When validating a THEN/OR set, once a table is matched, processing will apply the surcharge in the matched table and will not read on any other tables (no further surcharges will be applied). If a table is not matched, processing will continue to the next table.

When the fare being validated does match (according to the value in Byte 45) to all match fields, apply the surcharge conditions specified within the Category 12 Record 3 to the fare being validated (based on the value in Byte 45). If the next table is strung with relational indicator OR, processing will not read on to the next table. Once a Category 12 subset has been matched and the surcharge data applied, processing will not read on to any further subsets and will not apply any further surcharges from the string.

When the fare being validated does not match (according to the value in Byte 45) to all match fields in all tables in the subset, this Category 12 subset is considered a no-match and processing should continue to the next OR Table or to the next Set. If another OR table or Set is not found, or also does not match, then apply the system assumption, no surcharges apply for the fare being validated at this level. If another OR table or Set is found, then processing will attempt to match the next table or set. Once a Category 12 subset has been matched and the surcharge data applied, processing will not read on to any further subsets.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document. Processing THEN/AND Sets When validating THEN/AND sets, processing will read all tables in the set and apply surcharges for all tables that are matched. Processing may no match a portion of the set and only apply surcharges for the tables that are matched. Once any portion of a THEN/AND set has been matched, processing will not read on to any further sets. If no tables in a THEN/AND set are matched, processing will read on to the next set.

Page E.03.12.11 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES set, then no further surcharge applies. If additional tables exist in the THEN/AND set, processing will continue to read all tables in the set and attempt to match and apply the surcharges. For all tables that are matched, processing will accumulate and apply all surcharges.

When the fare being validated does not match (according to the value in Byte 45) to all match fields, then this Category 12 table is considered a no-match and processing should continue to the next table in the THEN/AND set. Processing will continue to read all tables in the set and attempt to match and apply the surcharges (based on the value in Byte 45). When one or more data tables within a THEN/AND set are not matched, processing will still read all other tables in the set and apply any applicable surcharges from the tables that are matched. If processing cannot match any table in the set, then this set is considered a no-match, and processing will read on to the next Set. If another Set is not found or also does not match, then apply the system assumption, no surcharges apply for the fare being validated at this level.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.12 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Processing THEN/IF Sets Once an external IF condition is matched and passed, validate all Category 12 tables in the subset, accumulating and applying surcharges for all tables that match. Do not continue processing to another set. When Category 12 Record 3 tables reside in a set containing an IF condition to an external category, processing will attempt to match the IF condition. Once the IF condition is matched and “passed”, processing must live, die, or no match on the THEN portion and cannot read on to another set. If multiple Category 12 tables exist in the THEN portion strung with relational indicator OR, processing will apply the surcharge conditions for the first table that matches and will not read any further tables within the THEN portion. If multiple Category 12 tables exist in the THEN portion strung with relational indicator AND, processing will read all tables in the THEN portion and apply surcharge conditions for all tables that match. When processing matches an IF condition for any category, the surcharge amount applies according to the value in Byte 45. The fare component/pricing unit/journey application of the IF category does not alter the fare component/pricing unit/journey application of the surcharge data in the THEN portion of the set.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.13 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Unbooked Sectors When a sector(s) of an itinerary is not booked, the validation of such sector is optimistic but not unrealistic. Processing will validate all known information pertaining to the fare and may apply a surcharge if there is enough information to ascertain that the unbooked portion would incur a surcharge. For surcharges that require booking information, the surcharge for unbooked sectors will be assessed at the time the booking is made.

Page E.03.12.14 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1 Application of Data for Surcharge Processing

4.1.1 Date Range – Start Date (Bytes 14-19), Stop Date (Bytes 20-25)

The date range fields specify the travel period when a surcharge is applicable. The Start Date field indicates the earliest travel date to which the surcharge applies, and the Stop Date field indicates the latest travel date to which the surcharge applies. The Start Date begins on the first minute of that date (12:01 a.m.), and the Stop Date ends on the last minute of that date (12:00 midnight). When a Start Date is entered without a Stop Date, edits automatically enter the Stop Date to be the same as the Start Date. Edits prevent a Stop Date from being entered without a Start Date. Dates may be indicated with a specific year or without a specific year (indicating any year). If no data is entered in these fields, the surcharge applies for travel on any day/all year.

Validation of the Start/Stop Dates is dependent upon the value in Travel Portion Byte 45 and the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70) as follows: Travel Portion Start/Stop Dates Validate Against: Byte 45 Value When Betw/And Geo Spec Tables are value When Betw/And Geo Specs Tables contain data 00000000 (blank) Blank, 1, 2, 4, 6 Departure date from the origin of the fare Departure date from the origin of the travel that component being validated. matches the Between/And Geo Spec Tables 3 Departure date from each intermediate ticketed point Departure from each intermediate ticketed point on on the fare component being validated. Only the the travel that matches the Between/And Geos departure from one intermediate ticketed point on (excluding end points of the matched travel). Only the fare component must match the Start/Stop dates the departure from one intermediate ticketed point in order to match the table. If the departure from on the matched travel must match the Start/Stop multiple points matches the Start/Stop dates, the dates in order to match the table. If the departure surcharge is applied for each matched intermediate from multiple points matches the Start/Stop dates, ticketed point. the surcharge is applied for each matched intermediate ticketed point.

Page E.03.12.15 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Travel Portion Start/Stop Dates Validate Against: Byte 45 Value When Betw/And Geo Spec Tables are value When Betw/And Geo Specs Tables contain data 00000000 (blank) 5 Departure date from the origin of each sector on the Departure date from the origin of each sector on the fare component being validated. Only the departure travel that matches the Between/And Geos. Only of one sector on the fare component must match the the departure of one sector on the matched travel Start/Stop dates in order to match the table. If the must match the Start/Stop dates in order to match departure from multiple sectors matches the the table. If the departure from multiple sectors Start/Stop dates, the surcharge is applied for each matches the Start/Stop dates, the surcharge is matched sector. applied for each matched sector. NOTE 1: The presence of match data in Equipment (Bytes 42-44), RBD (bytes 119-120), Carrier/Flight Table 986 (bytes 121-128), and/or From/To/Via Geographic Specification Table (Bytes 47-54) may alter the point on the fare component/travel (as specified by Travel Portion Byte 45 and the Between/And Geo Spec Tables) where validation occurs. NOTE 2: Edits prevent data in Start/Stop Dates when Surcharge Type (byte 41) is value I (Side Trip).

When the Start/Stop Dates validate against the fare component being validated as specified by Travel Portion Byte 45 and data in the Between/And Geo Spec Tables (and other conditions within the category are met), then the surcharge applies according to the value in Byte 45.

Date, time, and day of week requirements specified in the following fields must match against the same point on the fare component (as specified by Travel Portion Byte 45 and data in the Between/And Geo Spec Tables) in order to match the Category 12: • Start/Stop Dates (bytes 14-19, 20-25) • Start/Stop Time (bytes 26-29, 30-33) • Day of Week (bytes 35-40), validation.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.16 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.2 Time of Day – Start Time (Bytes 26-29), Stop Time (Bytes 30-33)

The time fields specify the travel time during which a surcharge is applicable. When a Start Time is entered without a Stop Time, edits automatically enter the Stop Time to be 2400 (12:00 midnight). When a Stop Time is entered without a Start Time, edits automatically enter the Start Time to be 0001 (12:01 a.m.). When no data is entered in these fields, the surcharge applies for travel at any time.

Validation of the Start/Stop Times is dependent upon the value in Travel Portion Byte 45 and the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70) as follows: Byte 45 Value Start/Stop Dates Validate Against: When Betw/And Geo Spec Tables are value When Betw/And Geo Spec Tables contain data 00000000 (blank) Blank, 1, 2, 4, 6 Departure time from the origin of the fare Departure time from the origin of the travel that component being validated. matches the Between/And Geo Spec Tables. 3 Departure time from each intermediate ticketed Departure time from each intermediate ticketed point point on the fare component being validated. on the travel that matches the Between/And Geo Spec Only the departure from one intermediate Tables (excluding the end points of the matched ticketed point on the fare component must match travel). Only the departure from one intermediate the Start/Stop Times in order to match the table. ticketed point on the matched travel must match the If the departure from multiple points matches the Start/Stop Times in order to match the table. If the Start/Stop Times, the surcharge is applied for departure from multiple points matches the Start/Stop each matched intermediate ticketed point. Times, the surcharge is applied for each matched intermediate ticketed point. 5 Departure time from the origin of each sector on Departure time from the origin of each sector on the the fare component being validated. Only the travel that matches the Between/And Geo Spec Tables. departure of one sector on the fare component Only the departure of one sector on the matched travel must match the Start/Stop Times in order to must match the Start/Stop Times in order to match the match the table. If the departure from multiple table. If the departure from multiple sectors matches sectors matches the Start/Stop Times, the the Start/Stop Times, the surcharge is applied for each surcharge is applied for each matched sector. matched sector. NOTE 1: The presence of match data in Equipment (Bytes 42-44), RBD (bytes 119-120), Carrier/Flight Table 986 (bytes 121-128), and/or From/To/Via Geographic Specification Table (Bytes 47-54) may alter the point on the fare component/travel (as specified by Travel Portion Byte 45 and the Between/And Geo Spec Tables) where validation occurs. NOTE 2: Edits prevent data in Start/Stop Times when Surcharge Type (byte 41) is value I (Side Trip).

Page E.03.12.17 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

When the Start/Stop Times validate against the fare component being validated as specified by Travel Portion Byte 45 and data in the Between/And Geo Spec Tables (and other conditions within the category are met), then the surcharge applies according to the value in Byte 45.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.18 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.3 Appl (Byte 34)

The Application field denotes the application of the Start/Stop Time (bytes 26-33) regarding whether the Day of the Week data entered in Bytes 35-40 apply as individual days or as a range of days. When Start/Stop Times (bytes 26-33) are entered in conjunction with the Appl field (Byte 34) and Day of Week fields (Bytes 35-40), the Appl field indicates whether the Time applies on each day or to a range of days. The Appl field is a required field (by edits) when Day of Week data is entered.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.19 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.4 Day of Week (Bytes 35-40)

The Day of Week fields specify the days of the week when a surcharge is applicable. Up to six days of the week may be specified. When data is entered in these fields, the Appl field (Byte 34) must indicate whether the days apply daily or as a range. If no data is entered in Bytes 35-40, then the surcharge applies for travel on any day and the Start/Stop Times (bytes 26-33), if entered, apply daily.

Validation of the Day of Week is dependent upon the value in Travel Portion Byte 45 and the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70) as follows: Travel Portion Day of Week Validates Against: Byte 45 Value When Betw/And Geo Spec Tables are value When Betw/And Geo Spec Tables contain data 00000000 (blank) Blank, 1, 2, 4, 6 Departure day from the origin of the fare component Departure day from the origin of the travel that being validated. matches the Between/And Geo Spec Tables 3 Departure day from each intermediate ticketed point Departure day from each intermediate ticketed point on the fare component being validated. Only the on the travel that matches the Between/And Geo Spec departure day from one intermediate ticketed point on Tables (excluding end points of the matched travel). the fare component must match the Day of Week in Only the departure day from one intermediate ticketed order to match the table. If the departure day from point on the matched travel must match the Day of multiple points matches the Day of Week, the Week in order to match the table. If the departure day surcharge is applied for each matched intermediate from multiple points matches the Day of Week, the ticketed point. surcharge is applied for each matched intermediate ticketed point. 5 Departure day from the origin of each sector on the Departure day from the origin of each sector on the fare component being validated. Only the departure travel that matches the Between/And Geo Spec day from one sector on the fare component must Tables. Only the departure day from one sector on the match the Day of Week in order to match the table. If matched travel must match the Day of Week in order the departure day from multiple sectors matches the to match the table. If the departure day from multiple Day of Week, the surcharge is applied for each sectors matches the Day of Week, the surcharge is matched sector. applied for each matched sector. NOTE 1: The presence of match data in Equipment (Bytes 42-44), RBD (bytes 119-120), Carrier/Flight Table 986 (bytes 121-128), and/or From/To/Via Geographic Specification Table (Bytes 47-54) may alter the point on the fare component/travel (as specified by Travel Portion Byte 45 and Between/And Geo Spec Tables) where validation occurs. NOTE 2: Edits prevent data in Day of Week when Surcharge Type (byte 41) is value I (Side Trip).

Page E.03.12.20 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

When the Day of Week validates against the fare component being validated as specified by Travel Portion Byte 45 (and other conditions within the category are met), then the surcharge applies according to the value in Byte 45.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.21 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.5 Surcharge Type (Byte 41)

This field indicates the type of surcharge applicable for the fare being validated. Data is always required in Surcharge Type Byte 41, unless the only data entered in the Record 3 table is Text Table #996 (Bytes 110-117). Edits prevent entering data in Byte 41 without also entering data in surcharge amount bytes 72-81 (note that the surcharge amount may be 0.00).

Surcharge Type byte 41 functions as an action field. . Applicable Surcharge Type values follow: Value Definition Comments A Airport/Terminal B Business Class Edits require data in RBD (bytes 119-120). D Peak Travel Time Usually entered in combination with data in the time of day (bytes 26-33), day of week (Bytes 35-40) fields. E Equipment Edits require data in the equipment type field (Bytes 42-44). F Fuel G Peak Usually used when surcharge is dependent on a fare class or type. H Holiday Usually entered with a date range (Bytes 14-19, 20-25). I Side Trip Edits require data in Betw Geo Spec Table (Bytes 55-62). J Seasonal Usually entered with a date range (Bytes 14-19, 20-25). K Weekend Usually entered with day of week data (Bytes 35-40). L Sleeperette Edits require data in RBD (bytes 119-120). M Waiver for Adv Purchase Set should also contain an IF condition to Cat 5 (Adv Res/Tkting). Requirements N Navigation Usually entered with data in From/To/Via Geo Spec Table (bytes 47-54) and/or Between/And Geo Spec Tables (bytes 55-70) O Security P Maximum Stay Waiver Set should also contain an IF condition to Cat 7 (Max Stay). Q Miscellaneous/Other Z Reservation Booking Edits require data in RBD (bytes 119-120). Designator (RBD)

The Surcharge Type is only used as follows:

Page E.03.12.22 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

• To compare like surcharge types when validating Surcharge Appl Travel Portion (Byte 45) value 4 (per ticket) and value 6 (per direction); • To modify the application of the Between/And Geographic Specification Tables (bytes 55-70). Application of data in the Between/And Geo Spec Tables is dependent upon whether Surcharge Type (byte 41) is value I (side trip surcharge) or another value (non-side trip surcharge). For further information, refer to a later section of this document regarding the Between/And Geo Spec Tables. The data in Byte 41 is not used in any other processing.

For further information on comparing like surcharges based on data in Surcharge Type byte 41 and applying the actual surcharge amount based on the data in Travel Portion byte 45, refer to Section 4.1.7 Surcharge Appl – Travel Portion (Byte 45) of this document.

Page E.03.12.23 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.6 Equipment (Bytes 42-44)

The Equipment field is used to indicate that a surcharge is applicable on a specific type of equipment (refer to Section C Appendix F for valid equipment codes). If no data is entered in these fields, then the surcharge applies for travel on any type of equipment.

Validation of the Equipment is dependent upon the value in Travel Portion Byte 45 and the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70) as follows: Byte 45 Value Equipment Validates Against: When Betw/And Geo Spec Tables are value When Betw/And Geo Spec Tables contain data 00000000 (blank) Blank, 1, 2, 4, 6 Any sector on the fare component being validated. Any sector on the travel that matches the Between/And Only one sector on the fare component must satisfy the Geo Spec Tables. Only one sector on the travel must equipment type in order to match the table. If multiple satisfy the equipment type in order to match the table. flight sectors satisfy the equipment type, the surcharge If multiple flight sectors satisfy the equipment type, the is still applied only once per fare surcharge is still applied only once per fare component/ticket/direction (dependent upon the value component/ticket/direction (dependent upon the value in Byte 45). in Byte 45). 3 Each sector into and/or out of each intermediate Each sector into and/or out of each intermediate ticketed point on the fare component being validated. ticketed point on the travel that matches the Only one sector into or out of an intermediate ticketed Between/And Geo Spec Tables. Only one sector into point on the fare component must satisfy the equipment or out of an intermediate ticketed point on the travel type in order to match the table. If multiple flight must satisfy the equipment type in order to match the sectors into or out of a ticketed point satisfy the table. If multiple flight sectors into or out of a ticketed equipment type, the surcharge is applied for each point satisfy the equipment type, the surcharge is intermediate ticketed point that is matched. applied for each intermediate ticketed point that is matched. 5 Each sector on the fare component being validated. Each sector on the travel that matches the Only one sector on the fare component must satisfy the Between/And Geo Spec Tables. Only one sector on the equipment type in order to match the table. If multiple travel must satisfy the equipment type in order to flight sectors satisfy the equipment type, the surcharge match the table. If multiple flight sectors satisfy the is applied for each matched sector. equipment type, the surcharge is applied for each matched sector.

Page E.03.12.24 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

NOTE 1: The presence of match data in RBD (bytes 119-120), Carrier/Flight Table 986 (bytes 121-128), , and/or From/To/Via Geographic Specification Table (Bytes 47-54) may alter the point on the fare component/travel (as specified by Travel Portion Byte 45 and Between/And Geo Spec Tables) where validation occurs. NOTE 2: Edits prevent data in Equipment when Surcharge Type (byte 41) is value I (Side Trip).

When validating Equipment against a sector of the fare component, if the sector contains unticketed points, all travel on the sector must be on the specified Equipment in order to match (all equipment code/s on the sector must match the Equipment code specified in Category 12).

When the Equipment validates against the fare component being validated as specified by Travel Portion Byte 45 and the Between/And Geo Spec Tables (and other conditions within the category are met), then the surcharge applies according to the value in Byte 45.

Match criteria in the following fields are validated against the sector specified by the value in Equipment Bytes 42-44 (within the confines of Travel Portion Byte 45 and the Between/And Geo Spec Tables): - Start/Stop Dates (bytes 14-25) - Start/Stop Time (bytes 26-33) - Appl (Byte 34) - Day of Week (Bytes 35-40) - From/To/Via Geo Spec Table (Bytes 47-54) - RBD (bytes 119-120) - Carrier/Flight Table 986 (bytes 121-128) NOTE: There is an edit which prevents the presence of data in the Equipment (Bytes 42-44) field when Surcharge Type is value I (Side Trip Surcharge).

Match validation for Equipment Bytes 42-44 and the fields above must be against the same point on the fare component being validated. Validation of Start/Stop Dates (bytes 14-25), Start/Stop Time (bytes 26-33), and Day of Week (Bytes 35-40) requires a departure validation unless otherwise specified by the use of an arrival TSI in a From/To/Via Geo Spec Table (Bytes 47-54).

Example: • Travel Portion Byte 45 is value Blank (per fare component) • Equipment Bytes 42-44 is value JET (jet aircraft) • Day of Week Bytes 35-40 is Mon.

Page E.03.12.25 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Processing will validate any sector on the fare component being validated where travel on the sector is on jet aircraft and where departure of the sector is on Monday. Although Byte 45 value Blank indicates that Day of Week validation is against the departure from the origin of the fare component being validated, the Equipment field further restricts this validation and causes Day of Week to validate against the departure from the origin of the sector on jet aircraft. (Match data validates against the same point.) NOTE: If the intent is that the Day of Week validates against the origin of the fare component being validated rather than the sector on jet aircraft as specified by Bytes 42-44, then Day of Week data should be entered in an IF Cat 02 table rather than in Cat 12 (e.g. THEN Cat 12 Bytes 42-44 JET IF Cat 2 Mon).

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.26 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7 Surcharge Appl – Travel Portion (Byte 45)

The Travel Portion field in Byte 45 indicates to what portion of travel the surcharge applies and to what portion of travel within the fare component being validated that the match fields apply. Processing will read the value in Byte 45 to determine how to apply the remainder of the data in the Category 12 Record 3 table.

Travel Portion Byte 45 causes the surcharge to apply according to one of the values below.

Application of the Travel Portion Values

Value Application BLANK On each fare component that has the applicable surcharge within the itinerary (same application as value 1). 1 Fare On each fare component that has the applicable surcharge within the itinerary (same application as BLANK). Component 2 Round Trip Apply half the surcharge amount on each fare component that has the applicable surcharge within the itinerary. If the fare is used on a half-round trip basis on a single fare component, then half of the surcharge amount will be applied on the fare component being validated. 3 Transfer On all ticketed intermediate points within the fare component being validated (applies to connections and stopovers). A transfer is a change of aircraft (stopover or connection) that does not include direct flights.

Exception: When data is present in Between/And Geo Spec Tables (bytes 55-62, 63-70) and Surcharge Type (byte 41) is not value I (not a Side Trip Surcharge):

The application is on all ticketed intermediate points within the travel that matches the Between/And Geo Spec Tables (applies to connections and stopovers). 4 Ticket Once for the entire ticket for the identical Record 2 carrier, surcharge type value in Byte 41, and geographic specification. Apply highest amount on the ticket per carrier for the identical surcharge type and travel portion.

Page E.03.12.27 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Value Application 5 Coupon For each flight coupon within the fare component being validated (for ticketless travel, each sector/segment represents a flight coupon).

Exception: When data is present in Between/And Geo Spec Tables (bytes 55-62, 63-70) and Surcharge Type (byte 41) is not value I (not a Side Trip Surcharge):

The application is for each flight coupon within the travel that matches the Between/And Geo Spec Tables (for ticketless travel, each sector/segment represents a flight coupon). 6 Direction To be applied once for each direction of travel on the journey for the identical Record 2 carrier, surcharge type value in Byte 41, and geographic specification. Apply highest amount per carrier for the identical surcharge type and travel portion.

In addition to indicating how to apply the surcharge amount, the value in Byte 45 indicates how to apply the data in the match fields to the fare component being validated. • When the value in Byte 45 is Blank, 1, 2, 4, or 6 then processing will apply the data in the match fields to the origin of the fare component being validated [unless further qualified by data in the Equipment field (Bytes 42-44), and/or Geographic Specification Tables (Bytes 47-54, 55-62, 63-70 )]. • When the value in Byte 45 is 3 (per transfer), then processing will apply the data in the match fields to each transfer point on the fare component being validated [unless further qualified by data in the Equipment field (Bytes 42-44), and/or Geographic Specification Tables (Bytes 47-54, 55-62, 63-70)]. • When the value in Byte 45 is 5 (per coupon), then processing will apply the data in the match fields to each coupon on the fare component being validated [unless further qualified by data in the Equipment field (Bytes 42-44), and/or Geographic Specification Tables (Bytes 47-54, 55-62, 63-70)]. Exception: Travel Dates in Override Date Table #994 (Bytes 102-109) validate against the departure date of the first flight of the fare component being validated, regardless of the value in Byte 45. Refer to Data Application for Table 994 for further information. NOTE: There is an edit which prevents Travel Portion (Byte 45) value is 2, 3, 4, or 6 when Surcharge Type is I (Side Trip).

Page E.03.12.28 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Processing Steps NOTE: These steps are for illustrative purposes only and do not imply how, or in what order, any subscriber will validate the data.

1. Establish Travel Portion value in Byte 45.

2. If Byte 45 is value Blank, 1, or 2 (per fare component), then validate the data in the match fields against the fare component being processed (see NOTE). When data is present in multiple match fields, validation of the match fields must be against the same point. a. If all match data are found at a single point on the fare component, then apply the surcharge once for the fare component. b. If any of the match data is not found, then the surcharge does not apply.

3. If Byte 45 is value 3 (per transfer), then validate the data in the match fields against each intermediate ticketed point (each transfer) within the fare component being processed (see NOTE). When data is present in multiple match fields, validation of the match fields must be against the same point. a. If all match data are found at a ticketed point, then apply the surcharge for that point (for each ticketed point that is matched, apply the surcharge). b. If any of the match data is not found at a ticketed point, then the surcharge does not apply for that point. c. If no intermediate ticketed points exist on the fare component, then no surcharge applies. NOTE: Match data does not need to validate against all intermediate points of a fare component in order to match the table. Processing matches the table once all match fields validate against a single intermediate point. The surcharge will be applied for each intermediate point at which the match data validates.

4. If Byte 45 is value 4 (per ticket), then validate the data in the match fields against the fare component being processed (see NOTE). When data is present in multiple match fields, validation of the match fields must be against the same point. a. If all match data are found at a single point on the fare component: i. Group all surcharges on the journey for the identical Record 2 carrier with the identical Byte 41 Surcharge Type value, with the identical Geographic Specification Data (Bytes 47-54, 55-62, 63-70), and with Byte 45 Travel Portion value 4. ii. Apply the highest surcharge amount from the group above once for the entire ticket for each carrier iii. Note the following: • Processing must first identify the total per ticket surcharge for the fare component being validated, then compare this total across the other fare components on the ticket (based on identical carrier, Byte 41 Surcharge Type value, Geographic Specification, and Byte 45 Travel Portion value). • When the fare component being validated matches multiple Category 12 tables strung with relational indicator AND, sum the total surcharge amount for the matched tables with the identical Byte 41 Surcharge Type value,

Page E.03.12.29 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

identical Geographic Specification, and identical Byte 45 Travel Portion value (4). Use this total as the surcharge amount for comparing against other fare components. • Determination of the higher amount is based on amount and currency. When a reduction (negative surcharge) is specified (byte 71 value A, B, C, D, or E), processing still identifies the higher amount which will be the lowest reduction. Example: Reduction of -5.00 vs. -10.00, processing identifies -5.00 has the highest amount (lowest reduction). b. If any of the match data is not found, then the surcharge does not apply.

5. If Byte 45 is value 5 (per coupon), then validate the data in the match fields against each coupon (each sector/segment) within the fare component being processed (see NOTE). When data is present in multiple match fields, validation of the match fields must be against the same point. a. If all match data are found on a sector, then apply the surcharge for that sector (for each sector that is matched, apply the surcharge). b. If any of the match data is not found on a sector, then the surcharge does not apply for that sector. NOTE: Match data does not need to validate against all sectors of a fare component in order to match the table. Processing matches the table once all match fields validate against a single sector. The surcharge will be applied for each sector on which the match data validates.

6. If Byte 45 is value 6 (per direction), then validate the data in the match fields against the fare component being processed (see NOTE). When data is present in multiple match fields, validation of the match fields must be against the same point. a. If all match data are found at a single point on the fare component: Outbound: i. Group surcharges all surcharges on outbound fare components on the journey for the identical Record 2 carrier with the identical Byte 41 Surcharge Type value, with the identical Geographic Specification Data (Bytes 47-54, 55-62, 63-70), and with Byte 45 Travel Portion value 6. ii. Apply the highest surcharge amount from the group above once for all outbound fare components on the journey for each carrier.

Page E.03.12.30 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES iii. Note the following: • Processing must first identify the total per direction surcharge for the fare component being validated, then compare this total across the other outbound fare components on the journey (based on identical carrier, Byte 41 Surcharge Type value, Geographic Specification, and Byte 45 Travel Portion value). • When the fare component being validated matches multiple Category 12 tables strung with relational indicator AND, sum the total surcharge amount for the matched tables with the identical Byte 41 Surcharge Type value, identical Geographic Specification, and identical Byte 45 Travel Portion value (6). Use this total as the surcharge amount on the outbound fare component being validated for comparing against other outbound fare components. • Determination of the higher amount is based on amount and currency. When a reduction (negative surcharge) is specified (byte 71 value A, B, C, D, or E), processing still identifies the higher amount which will be the lowest reduction. Example: Reduction of -5.00 vs. -10.00, processing identifies -5.00 has the highest amount (lowest reduction).

Page E.03.12.31 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Inbound: i. Group surcharges all surcharges on inbound fare components on the journey for the identical Record 2 carrier with the identical Byte 41 Surcharge Type value, with the identical Geographic Specification Data (Bytes 47-54, 55-62, 63-70), and with Byte 45 Travel Portion value 6. ii. Apply the highest surcharge amount from the group above once for all inbound fare components on the journey for each carrier. iii. Note the following: • Processing must first identify the total per direction surcharge for the fare component being validated, then compare this total across the other inbound fare components on the journey (based on identical carrier, Byte 41 Surcharge Type value, Geographic Specification, and Byte 45 Travel Portion value). • When the fare component being validated matches multiple Category 12 tables strung with relational indicator AND, sum the total surcharge amount for the matched tables with the identical Byte 41 Surcharge Type value, identical Geographic Specification, and identical Byte 45 Travel Portion value (4). Use this total as the surcharge amount on the inbound fare component being validated for comparing against other inbound fare components. • Determination of the higher amount is based on amount and currency. • When a reduction (negative surcharge) is specified (byte 71 value A, B, C, D, or E), processing still identifies the higher amount which will be the lowest reduction. Example: Reduction of -5.00 vs. -10.00, processing identifies - 5.00 has the highest amount (lowest reduction). b. If any of the match data is not found, then the surcharge does not apply.

NOTE: When Between/And Geo Spec Tables (bytes 55-62, 63-70) contain data and Surcharge Type (byte 41) is not value I (not a side trip surcharge), then the match data validates against the travel that matches the Between//And Geo Spec Tables. Refer to applicable sections for each match field for further information.

Page E.03.12.32 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Comparison of data for Value 4 (per ticket) and Value 6 (per direction) When determining the “per ticket” or “per direction” surcharge to apply, processing compares carrier, surcharge type, travel portion, and geographic specification fields. Comparison of the carrier is based on the Record 2 carrier; comparison of the Surcharge Type is based on the value in Byte 41; and comparison of the Travel Portion is based on the value in Byte 45. When comparing Geographic Specification data, processing will compare the data in the From/To/Via Geographic Specification Table in Bytes 47-54 and the Between/And Geographic Specification Tables (bytes 55-62, 63-70) on the Record 3. Processing will not consider any geographic data on the Record 2. For each Geo Spec Table, the comparison is based on a specific data match of the TSI value and the geographic location value being validated. The Geo Spec Table numbers do not have to be an exact match; however, the geographic data that incurs a surcharge must be identical (e.g. NYC equals NYC, but NYC does not equal the United States; see additional examples below). Processing will not apply any extended location logic when matching the geographic data. The data in Location 1 of the Geo Spec Table may be an exact match to the data in either Location 1 or Location 2 of the Geo Spec Table being compared, and the data in Location 2 of the Geo Spec Table may be an exact match to the data in either Location 1 or Location 2 of the Geo Spec Table being compared. When comparing the Between/And Geo Spec Tables, processing must find an exact match for both tables for the specified sector/portion of travel. Processing will attempt to find a match for the data in the Between table against the other Between table(s), and the And table against the other And table(s), or processing will “flip” and attempt to match the data in the Between against the And and the And against the Between (refer to the example below).

From/To/Via Geographic Specification Comparison Examples: Geographic Data Bytes 47-54 Compared to Geo Data Bytes 47-54 Comparison Match or No Match? TSI Loc 1 Loc 2 TSI Loc 1 Loc 2 Blank Blank Blank Blank Blank Blank Match 42 Blank Blank 42 Blank Blank Match Blank C PAR Blank Blank N FR Blank No match. (PAR and FR are not an exact match) Blank C PAR Blank Blank Z 210 Blank No match. (PAR and 210 are not an exact match) Blank C PAR Blank Blank C NYC C PAR Match for PAR Blank C PAR C LON Blank C CHI C PAR Match for PAR. 48 C PAR Blank 42 C PAR Blank No match. (TSIs are not an exact match) Blank C CHI Blank Blank C ORD Blank No match. (CHI and ORD are not an exact match)

Page E.03.12.33 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Between/And Geographic Specification Comparison Examples: Geographic Data Compared to Geographic Data Comparison Match or No Match? (bytes 55-62, 63-70) (bytes 55-62, 63-70) Betw Table And Table Betw Table And Table C PAR C BKK C PAR C BKK Match C PAR C BKK C BKK C PAR Match C PAR C BKK C BKK SYD C LON PAR Match for PAR-BKK C PAR C BKK C PAR C SYD No match Z 210 C BKK C PAR C BKK No match (PAR and 210 are not an exact match)

Page E.03.12.34 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.1 Fare Component (Value 1) Value 1 indicates that the surcharge applies per fare component. This is the same application as value Blank.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.35 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.2 Round Trip (Value 2) Value 2 indicates that half the surcharge amount applies on the fare component being validated. If the fare is only used as a half round trip fare within the pricing unit, then only half of the surcharge amount will apply for that fare component. If the fare is only used as a one way fare, then only half of the surcharge amount will apply for that fare component (ATPCO’s Coding Convention holds that Byte 45 value 2 should not be used for OW fares). If the fare is a RTW/CT fare (in a RTW/CT Tariff), then only half of the surcharge amount will apply for that RTW/CT fare component.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.36 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.3 Transfer (Value 3) Value 3 indicates that the surcharge applies at each ticketed intermediate point within the fare component being validated (applies at each transfer point), unless further qualified by other fields (e.g. match fields) within the category. Validation will be against any connection or stopover where there is a change of aircraft (excluding direct flights). Validation will not be against fare break points.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.37 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.4 Ticket (Value 4) Value 4 indicates that the surcharge applies once for the entire ticket. For each Record 2 carrier, processing must establish all surcharges on the ticket with the identical Surcharge Type value (Byte 41), with the identical Geographic Specification data (Bytes 47- 54, 55-62, 63-70), and with Travel Portion value 4 (Byte 45). The highest surcharge amount for the identical Byte 41 value, identical Geographic Specification data, and identical Byte 45 value will apply for each Record 2 carrier. (For additional information regarding comparison of carrier, Byte 41 value, geographic specification data, and Byte 45 value, refer to Section 4.1.7 of this document under Comparison of Data for Value 4 and Value 6.)

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.38 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.5 Coupon (Value 5) Value 5 indicates that the surcharge applies for each sector/segment within the fare component being validated, unless further qualified by other fields (e.g. match fields) within the category.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.39 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.6 Direction (Value 6) Value 6 indicates that the surcharge applies once for each outbound or inbound direction on the journey.

The application is dependent upon whether or not the fare component being processed is a RTW/CT fare (in a RTW/CT tariff) as described below.

NON RTW/CT fares. For each Record 2 carrier, processing must establish all surcharges for each direction with the identical Surcharge Type value (Byte 41), with the identical Geographic Specification data (Bytes 47-54, 55-62, 63-70), and with Travel Portion value 6 (Byte 45). The highest surcharge amount for the identical Byte 41 value and identical Byte 45 value will apply for each Record 2 carrier in each direction. (For additional information regarding comparison of carrier, Byte 41 value, geographic specification data, and Byte 45 value, refer to Section 4.1.7 of this document under Comparison of Data for Value 4 and Value 6.)

Determination of outbound or inbound fare components is based on whether the fare is directional or non-directional. Refer to the following explanation of outbound/inbound or Data Application for Record 2 for further information.

Directional Fares Determination of outbound and inbound is based on fare selection. Outbound = All fare components selected in the direction of travel. Inbound = All fare components selected in the opposite direction of travel. Exception: For Open Jaw pricing units consisting of two fare components, the second fare component is always considered an inbound fare component.

Non Directional Fares To establish outbound or inbound application, review all fare break points within the pricing unit and measure each of those points from the point of origin of the pricing unit to determine the furthest geographical fare break point (point of turnaround). Outbound = All fare components within the pricing unit prior to the furthest geographical fare break point (point of turnaround). Inbound = All fare components within the pricing unit after the furthest geographical fare break point (point of turnaround) are considered Inbound.

Page E.03.12.40 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

RTW/CT fares

RTW/CT fares are a single fare component priced as a single pricing unit and are not considered outbound vs. inbound fare components for the purposes of Travel Portion Value 6 validation. Therefore, when processing Category 12 data for a RTW/CT fare, Travel Portion Value 6 has the same application as Travel Portion Value Blank or 1 (per fare component). Processing applies the data in Value 6 as if it is value Blank or 1.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.41 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.7.7 Combination of Different Travel Portion Byte 45 Values When multiple surcharges are applicable, the processing steps stated previously in section 4.1.7 apply. The surcharge amount applies per Record 2 carrier based on the Surcharge Type (Byte 41) and the corresponding Surcharge Appl – Travel Portion (Byte 45).

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.42 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.8 Sector/Portion (Byte 46)

The Sector/Portion field indicates whether the geography specified in the Between and And Geographic Specification Tables (bytes 55-70) applies to a single sector or a portion of travel. Following is a n explanation of applicable values:

Value S: Sector. Data in the Between/And Geo Spec Tables applies to a single sector on the fare component. Processing will match a sector where one end point of the sector matches the data in the Between Geo Spec Table (bytes 55-62) and the other end point matches the data in the And Geo Spec Table (bytes 63-70).

Value P: Portion of Travel. Data in the Between/And Geo Spec Tables applies to portion of travel on the fare component (where “portion of travel” is defined as one or more consecutive sectors on the fare component). Processing will match a portion of travel where one end point of the portion matches the data in the Between Geo Spec Table (bytes 55-62) and the other end point matches the data in the And Geo Spec Table (bytes 63-70).

Value Blank: No Application. Edits only allow Blank when one of the following is true: • Surcharge Type (byte 41) is value I, indicating the data in the record applies to a Side Trip Surcharge; or • Surcharge Type (byte 41) is not value I and Between/ And Geo Spec Tables (bytes 55-70) are both value 00000000.

Data in this field is only applicable for non-side trip surcharges (only applicable when the Surcharge Type byte 41 is not value I). Edits prevent data in the Sector/Portion field when Surcharge Type (byte 41) is value I.

For further explanation and examples illustrating the application of the Sector/Portion field, refer to a later section of this document regarding the Between/And Geo Spec Tables.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.43 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.9 From/To/Via – Geographic Specification Table No. 995 (Bytes 47-54)

The From/To/Via Geographic Specification Table indicates the geographic restrictions that must be matched in order to apply the surcharge. Processing will compare the points on the fare component being validated to the data in the Geo Spec Table. Any ticketed points on the fare component (including fare break points) are possible matches to the Geo Spec Table data. Processing will not validate the Geo Spec Table data against unticketed points. If any of the ticketed points on the fare component match the data in the Geo Spec Table, then the surcharge applies.

Within the Geographic Specification Table is the ability to enter a TSI and/or up to two geographic locales of the same locale type. The TSI specifies a point or portion of travel that must be present on the fare component being validated in order to match the table and the geographic locales specify points that must be present on the fare component being validated in order to match the table.

The relationship between Loc 1 and Loc 2 is OR. The ability to indicate a between/and relationship between Loc 1 and Loc 2 is not provided with this Geo Spec Table. (If the surcharge is applicable to a sector/portion of travel between specific points, the applicable between/and geographic locales should be specified in the Between/And Geo Spec Tables bytes 55-70.) The application of each locale in the From/To/Via Geo Spec Table is from/to/via (unless further modified by a TSI or Byte 45). “From/to” validation is against the origin or destination point of a fare component and “via” validation is against intermediate ticketed points of a fare component (processing will attempt to validate any portion of travel that “touches” the specified point). NOTE: The presence of match data in Between/And Geographic Specification Tables (bytes 55-70) may alter the point on the fare component (as specified by Travel Portion Byte 45) where validation occurs.

A TSI may be entered alone or in combination with a geographic locale. When the TSI is used in conjunction with geographic locales, the TSI further modifies the from/to/via application of the geographic location. Example • TSI 01 (departure from fare origin) with Loc 1 France indicates that processing should validate departure from fare origin in France. • TSI 18 (international sectors) with Loc 1 France indicates that processing should validate all international sectors from/to/via France.

The TSI application may be fare component (FC), fare component/pricing unit (FC/PU), pricing unit (PU), or journey (J); however, validation of the TSI is always against the fare component being validated and is not against the pricing unit or journey. Processing will attempt to validate the portion of travel specified by the TSI against the fare component being validated.

Page E.03.12.44 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Example • TSI 42 (departure of each transatlantic sector) indicates that processing should attempt to validate the departure of transatlantic sectors on the fare component being validated. • TSI 01 (departure from fare origin) indicates that processing should attempt to validate the departure from the origin of the pricing unit encompassing the fare component being validated (if the pricing unit origin is on another fare component, then no match the table for the fare component). • TSI 59 (departure of journey origin) indicates that processing should attempt to validate the departure from the point of origin of the journey on the fare component being validated (if the journey origin is on another fare component, then no match the table for the fare component).

Determination of which portion of the fare component being validated is used to validate the data in the From/To/Via Geo Spec Table is dependent upon the value in Travel Portion Byte 45, the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70), and the Surcharge Type (byte 41) as follows: Travel Portion Geo Spec Table Validates Against: Byte 45 Value When Betw/And Geo Spec Tables are value 00000000 (blank) When Betw/And Geo Spec Tables contain data OR AND Surcharge Type (byte 41) is value I (Side Trip) Surcharge Type (byte 41) is not value I (not a Side Trip surcharge) Blank, 1, 2, 4, 6 All points/portions of travel (including fare break points) on the All points/portions of travel on the travel that matches the fare component being validated. Between/And Geo Spec Tables. • Loc1/Loc 2 validate from/to/via all ticketed points on the • Loc1/Loc 2 validate at all intermediate ticketed points on the fare component (unless otherwise specified by a TSI). matched travel (unless otherwise specified by a TSI). Validation • Departure/Arrival TSI validates against departure or arrival, of Loc1/Loc2 is not against the end points of the portion of travel. as specified, at all ticketed points on the fare component . • Departure/Arrival TSI validates against departure or arrival, as If Loc 1/Loc 2 are present, then validate departure or arrival specified, at all ticketed points on the matched travel . Validation at Loc 1/Loc 2. of the TSI is against the end points and/or intermediate ticketed • Sector TSI validates against any sector on the fare points on the matched travel, unless Loc1 or Loc 2 are present. If component. If Loc 1/Loc 2 present, then validate sectors Loc 1/Loc 2 are present, then validate departure or arrival only at specified by the TSI from/to/via Loc 1/Loc 2. intermediate ticketed points that match Loc 1/Loc 2. • Sector TSI validates against any sector on the matched travel. If Loc 1/Loc 2 are present, then validate sectors specified by the TSI where the origin point of the sector is in Loc 1 or Loc 2 and/or the destination point of the sector is in Loc 1 or Loc 2 (where Loc 1 and Loc 2 match against intermediate ticketed point on the portion of travel).

Page E.03.12.45 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Travel Portion Geo Spec Table Validates Against: Byte 45 Value When Betw/And Geo Spec Tables are value 00000000 (blank) When Betw/And Geo Spec Tables contain data OR AND Surcharge Type (byte 41) is value I (Side Trip) Surcharge Type (byte 41) is not value I (not a Side Trip surcharge) 3 All intermediate ticketed points on the fare component being All intermediate ticketed points on the travel that matches the validated. Between/And Geo Spec Tables. • Loc1/Loc 2 validate at all intermediate ticketed points on • Loc1/Loc 2 validate at all intermediate ticketed points on the the fare component (unless otherwise specified by a TSI). matched travel (unless otherwise specified by a TSI). • Departure/Arrival TSI validates against all intermediate • Departure/Arrival TSI validates against all intermediate ticketed ticketed points on the fare component where the departure points on the matched travel where the departure or arrival from/to or arrival from/to the point is as specified by the TSI. the point is as specified by the TSI. Example – TSI 42 (departure of each transatlantic Example – TSI 42 (departure of each transatlantic sector): sector): validate all intermediate ticketed points on the validate all intermediate ticketed points on the matched travel fare component where the departure from the point is where the departure from the point is on a transatlantic sector. on a transatlantic sector. If Loc 1/Loc 2 are present, then validate intermediate ticketed If Loc 1/Loc 2 are present, then validate intermediate points Loc 1/Loc 2 where the departure or arrival from/to Loc ticketed points Loc 1/Loc 2 where the departure or arrival 1/Loc 2 is as specified by the TSI. from/to Loc 1/Loc 2 is as specified by the TSI. Example – TSI 48 (departure of first international sector) with Example – TSI 48 (departure of first international Loc 1 US: on the matched travel, validate all intermediate sector) with Loc 1 US: validate all intermediate ticketed points in the US where the departure from the point is ticketed points in the US where the departure from the on the first international sector of the fare component. point is on the first international sector of the fare • Sector TSI validates against any intermediate ticketed point on the component. matched travel where travel into and/or out of the point is on the • Sector TSI validates against any intermediate ticketed point sector specified by the TSI. on the fare component where travel into and/or out of the Example – TSI 18 (international sectors): validate all point is on the sector specified by the TSI. intermediate ticketed points on the matched travel where Example – TSI 18 (international sectors): validate all travel into and/or out of the point is on an international sector. intermediate ticketed points on the fare component If Loc 1/Loc 2 are present, then validate intermediate ticketed where travel into and/or out of the point is on an points Loc 1/Loc 2 where travel into and/or out of Loc 1/Loc 2 is international sector. on the sector specified by the TSI. If Loc 1/Loc 2 are present, then validate intermediate Example – TSI 18 (international sectors) with Loc 1 US: on ticketed points Loc 1/Loc 2 where travel into and/or out of the matched travel, validate intermediate ticketed points in the Loc 1/Loc 2 is on the sector specified by the TSI. US where travel into and/or out of the point is on an Example – TSI 18 (international sectors) with Loc 1 international sector. US: validate intermediate ticketed points in the US NOTE: ATPCO’s coding convention holds that when Byte 45 is where travel into and/or out of the point is on an value 3, the TSI should reference a specific point. international sector. NOTE: ATPCO’s coding convention holds that when Byte 45 is value 3, the TSI should reference a specific point.

Page E.03.12.46 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Travel Portion Geo Spec Table Validates Against: Byte 45 Value When Betw/And Geo Spec Tables are value 00000000 (blank) When Betw/And Geo Spec Tables contain data OR AND Surcharge Type (byte 41) is value I (Side Trip) Surcharge Type (byte 41) is not value I (not a Side Trip surcharge) 5 All points/portions of travel on each sector (including fare break All points/portions of travel on each sector on the travel that matches points) on the fare component being validated. the Between/And Geo Spec Tables. • Loc 1/Loc 2: validate all sectors where the origin point of • Loc 1/Loc 2: validate all sectors on the matched travel where the the sector is in Loc 1 or Loc 2 or the destination point of the origin point of the sector is Loc 1 or Loc 2 and/or the destination sector is in Loc 1 or Loc 2 (unless otherwise specified by a point of the sector is in Loc 1 or Loc 2 (unless otherwise specified TSI). by a TSI). Validation of Loc1/Loc2 is against intermediate • Departure/Arrival TSI validates against departure or arrival ticketed points on the portion of travel and not against the end sector, as specified, on all sectors on the fare component. points of the portion. Example – TSI 42 (departure of each transatlantic • Departure/Arrival TSI validates against departure or arrival sector, sector): validate departure of each transatlantic sector as specified, on all sectors on the matched travel. on the fare component. Example – TSI 42 (departure of each transatlantic sector): If Loc 1/Loc 2 present, then validate departure or arrival validate departure of each transatlantic sector on the on the sector as specified at Loc 1/Loc 2. matched travel . Example – TSI 11 (arrival at first point of stopover) Validation of the TSI is against the end points and/or intermediate with Loc 1 US: validate each sector where the ticketed points on the matched travel, unless Loc1 or Loc 2 are destination point of the sector arrives at a stopover present. If Loc 1/Loc 2 are present, then validate departure or point in the US. arrival sector, as specified, only at intermediate ticketed points that • Sector TSI validates against any sector on the fare match Loc 1/Loc 2. component. Example – TSI 11 (arrival at first point of stopover) with Loc Example – TSI 18 (international sectors): validate each 1 US: validate each sector on the matched travel where the international sector of the fare component. destination point of the sector arrives at a stopover point in the If Loc 1/Loc 2 are present, then validate sectors specified by US that is an intermediate point on the matched travel.. the TSI where the origin point of the sector is in Loc 1 or • Sector TSI validates against any sector on the matched travel. Loc 2 and/or the destination point of the sector is in Loc 1 Example – TSI 18 (international sectors): validate each or Loc 2. international sector on the matched travel. Example – TSI 18 (international sectors) with Loc 1 If Loc 1/Loc 2 are present, then validate sectors specified by the US: validate each sector where the origin and/or TSI where the origin point of the sector is in Loc 1 or Loc 2 and/or destination point of the sector is in the US. the destination point of the sector is in Loc 1 or Loc 2 (where Loc 1 and Loc 2 match against intermediate ticketed point on the portion of travel). Example – TSI 18 (international sectors) with Loc 1 US: on the matched travel , validate each sector where the origin and/or destination point of the sector is in the US and the US point is an intermediate point on the matched travel.

Page E.03.12.47 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Match criteria in the following fields are validated against the point/portion of travel specified by the From/To/Via Geo Spec Table (within the confines of Travel Portion Byte 45): - Start/Stop Dates (bytes 14-25) - Start/Stop Time (bytes 26-33) - Appl (Byte 34) - Day of Week (Bytes 35-40) - Equipment Code (Bytes 42-44) - RBD (bytes 119-120) - Carrier/Flight Table 986 (bytes 121-128) NOTE: There is an edit which prevents the presence of data in these match fields when Surcharge Type is value I (Side Trip).

Match validation for the Surcharge From/To/Via Geo Spec Table and the fields above must be against the same point on the fare component being validated. If multiple points/portions of travel are matched, then validate the match criteria against all matched points portions of travel, and apply the surcharge according to the value in Byte 45. When data is present in both the From/To/Via Geo Spec Table (Bytes 47-54) and one or both of the Between/And Geo Spec Tables (Bytes 55-62, 63-70), the data in the match fields above still validate against the point/portion of travel specified by the From/To/Via Geo Spec Table (Bytes 47-54).

Example 1: • Travel Portion Byte 45 is value Blank (per fare component) • From/To/Via Geo Spec Table (Bytes 47-54) is N US (the United States) • Day of Week Bytes 35-40 is Mon. Processing will validate any sector from/to/via a point in the United States on the fare component being validated where departure of the sector is on Monday. Although Byte 45 value Blank indicates that Day of Week validation is against the departure from the origin of the fare component being validated, the Geo Spec Table further restricts this validation and causes Day of Week to validate against the departure from the origin of the sector from/to/via the US. (Match data validates against the same point.) NOTE: If the intent is that the Day of Week validates against the origin of the fare component being validated rather than the sector from/to/via the US, then Day of Week data should be entered in an IF Cat 02 table rather than in Cat 12 (e.g. THEN Cat 12 within the US IF Cat 2 Mon).

Example 2: • Travel Portion Byte 45 is value Blank (per fare component) • From/To/Via Geo Spec Table (Bytes 47-54) is N US (the United States) • Between/And Geo Spec Tables (bytes 55-62, 63-70) are GB – A3

Page E.03.12.48 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

• Day of Week Bytes 35-40 is Mon. On a portion of travel between GB and A3, processing will validate any sector via an intermediate ticketed point in the United States where departure of the sector is on Monday. Although Byte 45 value Blank indicates that Day of Week validation is against the departure from the origin of the fare component being validated, the From/To/Via Geo Spec Table (bytes 47-54) further restricts this validation and causes Day of Week to validate against the departure from the origin of the sector via the US. (Match data validates against the same point.)

Validation of Start/Stop Dates (bytes 14-25), Start/Stop Time (bytes 26-33), and Day of Week (Bytes 35-40) requires a departure validation unless otherwise specified by a use of an arrival TSI. When a TSI is entered that does not specify “departure” or “arrival”, and the remainder of the match criteria in the Record 3 table requires a departure validation, then the application of the TSI is a departure application.

Example: TSI 19 (domestic sectors) with Start/Stop dates: validate Start/Stop dates against the departure of all domestic sectors on the fare component or matched portion of travel being validated (depending upon the presence or absence of data in the Between/And Geo Spec Tables).

When a TSI is entered that specifies “arrival”, and the remainder of the match criteria in the Record 3 table requires a departure validation, the arrival TSI overrides the departure validation. Match criteria will validate against the arrival as specified by the TSI.

Example: TSI 44 (arrival of each transatlantic sector) with Start/Stop dates: validate Start/Stop dates against the arrival date of each transatlantic sector on the fare component or matched portion of travel being validated (depending upon the presence or absence of data in the Between/And Geo Spec Tables)..

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.49 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.10 Between/And Geographic Specification Tables No. 995 (Bytes 55-62 and 63-70)

The Between/And Geographic Specification Tables specify geographic travel to which the surcharge applies. Processing must match the data in the Between/And Geo Spec Tables against the fare component being validated in order to match the Category 12 table. The application of the Between/And Geographic Specification tables is dependent upon the value in Surcharge Type (byte 41). • When Surcharge Type is value I, the data in the Category 12 Record 3 applies for a Side Trip surcharge and the Between/And Geo Spec Tables specify the end points of a side trip embedded within the fare component. • When Surcharge Type is not value (in other words, Surcharge Type is any value except I), the data in the Category 12 Record 3 does not represent a Side Trip surcharge. The Between/And Geo Spec table specify the end points of a sector/portion of travel on the fare component. The is further defined below in Sections 4.1.10.1 and 4.1.10.2.

TSI and Loc Fields within Each Table – Applicable for all Surcharge Types Within each Geo Spec Table is the ability to enter a TSI and/or up to two geographic locales of the same locale type. The TSI specifies a point or portion of travel that must be present on the fare component being validated in order to match the table. The geographic locales specify points that must be present on the fare component being validated in order to match the table.

The relationship between Loc 1 and Loc 2 in each table is OR (the relationship between the two tables is between/and). The application of each locale is from/to (unless further modified by a TSI). A TSI may be entered alone or in combination with a geographic locale. When the TSI is used in conjunction with geographic locales, the TSI further modifies the from/to application of the geographic location. Example TSI 18 (international sectors) with Loc 1 France indicates that processing should validate all international sectors from/to France.

Page E.03.12.50 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

• TSI 40 (departure of outbound transatlantic sector) indicates that processing should attempt to validate the departure of a transatlantic sector when the fare component being validated is outbound. If the fare component is inbound, then processing would no match the TSI (and no match the Geo Spec Table 995). • TSI 76 (all domestic sectors on the journey) indicates that processing should attempt to validate all domestic sectors on the fare component being validated.

The following sections detail the differing application of the Between/And Geo Spec Tables depending upon the Surcharge Type.

Page E.03.12.51 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.10.1 Side Trip Surcharge (Surcharge Type byte 41 = value I) The Between/And Geographic Specification Tables indicate that a side trip (embedded side trip) is permitted as part of the through fare with a surcharge. The two Geo Spec Tables specify the end points of the portion of travel that defines the side trip. As a side trip is travel from and/or to an enroute point of a fare component, the specified points must be within the fare break points of the fare component being validated (must be intermediate points on the fare component). Additionally, the geographic points in the side trip must be permitted by the MPM or routing.

When Geo Spec Table 1 is used and Geo Spec Table 2 is blank, the data in Geo Spec Table 1 applies from/to the specified points to any other point within the fare component being validated. Processing will compare the intermediate ticketed points on the itinerary to the data in the Geo Spec Table 1 and apply the following: • If there is a match, then determine if one of the points that matches the table is transited twice on that fare component. If the point has been transited twice, then the surcharge will apply. • If there is not a match, then no surcharge applies (note that normal fare construction still applies).

When both Geo Spec Table 1 and Geo Spec Table 2 are used, the data applies between the specified points in Geo Spec Table 1 and Geo Spec Table 2. Processing will compare the intermediate ticketed points on the fare component to the data in the Geo Spec Tables and apply the following: • If there is a match to a sector, then determine if one of the end points of the sector that matches the Geo Spec Tables is transited twice on the fare component. If the point has been transited twice, then the surcharge will apply. • If there is not a match, then no surcharge applies (note that normal fare construction still applies).

Determination of which portion of the fare component being validated is used to match the data in the Side Trip Geo Spec Tables is dependent upon the value in Travel Portion Byte 45 as follows: Byte 45 Value Side Trip Geo Spec Table Validates Against: Blank, 1 All intermediate ticketed points/portions of travel on the fare component being validated. • Loc1/Loc 2 validate all intermediate ticketed points on the fare component (unless otherwise specified by a TSI). • Departure/Arrival TSI validates against departure or arrival, as specified, at all intermediate ticketed points on the fare component (excludes sectors into or out of a fare break point) . If Loc 1/Loc 2 present, then validate departure or arrival at Loc 1/Loc 2. • Sector TSI validates against all intermediate sectors on the fare component (excludes sectors into or out of a fare break point). If Loc 1/Loc 2 present, then validate sectors specified by the TSI from/to Loc 1/Loc 2.

Page E.03.12.52 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Byte 45 Value Side Trip Geo Spec Table Validates Against: 2, 3, 4, 6 Not valid for use in a Record 3 table that contains data in the Side Trip Geo Spec tables. Edits prevent the input of these Byte 45 values when Side Trip Geo table (Bytes 55-62) is used. 5 All points/portions of travel on each sector on the fare component being validated (excluding fare break points). • Loc 1/Loc 2: validate all sectors where the origin point of the sector is in Loc 1 or Loc 2 or the destination point of the sector is in Loc 1 or Loc 2 (unless otherwise specified by a TSI and excluding fare break points). • Departure/Arrival TSI validates against departure or arrival, as specified, at all intermediate sectors on the fare component (excludes sectors into or out of a fare break point). If Loc 1/Loc 2 present, then validate departure or arrival sector as specified at Loc 1/Loc 2. • Sector TSI validates against all intermediate sectors on the fare component (excludes sectors into or out of a fare break point). If Loc 1/Loc 2 present, then validate sectors specified by the TSI where the origin point of the sector is in Loc 1 or Loc 2 and/or the destination point of the sector is in Loc 1 or Loc 2.

Match criteria in the following fields are not valid for use in a Record 3 table that contains Side Trip Geo Spec Tables (edits prevent input): • Start/Stop Dates (bytes 14-25) • Start/Stop Time (bytes 26-33) • Appl (Byte 34) • Day of Week (Bytes 35-40) • Equipment Code (Bytes 42-44) • RBD (Bytes 119-120) • Carrier/Flight Table 986 (bytes 121-128)

When data is present in the From/To/Via Geo Spec Table (Bytes 47-54) and the Side Trip Geo Spec Tables (bytes 55-70), then this data does not have to validate at the same point on the fare component. Processing must validate the From/To/Via Geo Spec Table data anywhere on the fare component being validated (based on the data in Byte 45) and the Side Trip Geo Spec Table anywhere on the fare component being validated (excluding fare break points). If data in all geo spec tables is validated on the fare component, then the surcharge will be applied for the portion of travel specified by the Side Trip Geo Spec Tables. Refer to examples later in this section for further clarification.

Side Trip Fare Construction vs. Category 12 Surcharge When a portion of travel is identified as a side trip, then processing will assess the lower of either a side trip charge based on fare construction principles or a surcharge based on Category 12 data (note that Category 12 side trip data essentially applies a surcharge

Page E.03.12.53 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES for transiting the same point twice within the fare component). Processing will not assess both a side trip charge based on fare construction rules and a Category 12 surcharge for transiting the same point twice within the fare component. When a side trip charge is assessed based on fare construction principles, then this portion of travel is no longer considered part of the through fare and would not match any side trip geo spec data contained in Category 12. When a side trip is surcharged based on Category 12 data, then this portion of travel is considered part of the through fare with a surcharge and would not be considered a separate side trip based on fare construction.

Example: Category 12 = Charge USD 100.00 for side trip between LON and AMS. DFW-PAR OW fare component = DFW—LON—AMS—LON—PAR Side Trip Fare construction: • Asses a side trip for LON-AMS-LON. • LON-AMS-LON is separate from the through DFW-PAR fare. • DFW-PAR fare component will not match the Category 12 data as there is not a portion of travel between LON and AMS on the fare component. Category 12 validation: • Processing identifies a portion of travel between LON and AMS. • Apply USD 100.00 surcharge. • LON-AMS-LON is part of the through DFW-PAR fare (with a surcharge) and will not be assessed as a separate side trip.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.54 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.10.2 All Other (non-side trip) Surcharges (Surcharge Type byte 41 is NOT value I) The Between/And Geographic Specification Tables specify travel between ticketed points on the fare component to which the surcharge applies. The Geo Spec Tables have a between/and application and do not imply a direction of travel. Whether the data in the Between/And Geo Spec Tables must match against a single sector or a portion of travel is dependent upon the data in Sector/Portion (byte 46) as follows:

Sector/Portion Value S: Sector. Data in the Between/And Geo Spec Tables applies to a single sector on the fare component. Validation is against ticketed points only. Processing will match a sector where one end point of the sector matches the data in the Between Geo Spec Table (bytes 55-62) and the other end point matches the data in the And Geo Spec Table (bytes 63-70). It is possible that multiple sectors on the fare component will match the data in the Between/And Geo Tables. For example, if the Between/And tables specify “within Europe”, it is possible the fare component may contain multiple sectors where the end points of each sector are in Europe. Processing will attempt to match all possible sectors.

Sector/Portion Value P: Portion of Travel. Data in the Between/And Geo Spec Tables applies to portion of travel on the fare component (where “portion of travel” is defined as one or more consecutive sectors on the fare component). Validation is against ticketed points only. Processing will match a portion of travel where one end point of the portion matches the data in the Between Geo Spec Table (bytes 55-62) and the other end point matches the data in the And Geo Spec Table (bytes 63-70). It is possible that multiple portions on the fare component will match the data in the Between/And Geo Tables. For example, if the Between/And tables specify “within Europe”, it is possible the fare component may contain multiple portions where the end points are in Europe. Processing will attempt to match all possible portions.

When the Between Geo Spec Table contains data, edits require data in the And Geo Spec Table. Processing will compare all ticketed points on the fare component to the data in the Geo Spec Table. If processing matches a sector/portion of travel (depending upon the Sector/Portion value) to the data in the Between and And Geo Spec Tables, then match the Category 12 Record 3 (provided a match is also made to all other match fields). If processing does not match a sector/portion of travel (depending upon the Sector/Portion value) to the data in the Between and And Geo Spec Tables, then no match the Category 12 Record 3.

Last Point Out/First Point In Application Data has a “last point out” and “first point in” application. Processing matches the last point out of the geographic location specified in the Between Geo Spec to the first point into the geographic location specified in the And Geo Spec Table – or – the last point out of

Page E.03.12.55 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES the geographic location specified in the And Geo Spec table to the first point into the location specified in the Between Geo Spec Table.

Example 1 Betw/And Geo Spec Tables = z 210 – A 3 Application: last point out of Europe to first point into Area 3 (and vice versa) Travel on the fare component is: LON-PAR-FRA-BKK-SIN-SYD. Match: FRA-BKK travel

Example 2 Betw/And Geo Spec Tables = S US FL – N US Application: last point out of Florida to first point into US (and vice versa)

A. Travel on the fare component is: MIA-TPA-LAX-SIN. Match: TPA-LAX travel

B. Travel on the fare component is: MIA-TPA-TYO-SIN. Match: no match any travel (there is no last point out of Florida to first point into US)

C. Travel on the fare component is: MIA-DFW-LAX-SIN. Match: MIA-DFW travel

D. Travel on the fare component is: ATL-TPA-DFW. Match: ATL-TPA and TPA-DFW travel

E. Travel on the fare component is: MIA-TPA-DEN-SEA. Match: TPA-DEN travel

Page E.03.12.56 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Example 3 Betw/And Geo Spec Tables = A 1 – N US Application: last point out of Florida to first point into US (and vice versa)

Travel on the fare component is: MIA-TPA-DEN-SEA. Match: no match any travel (there is no last point out of the US to first point into Area 1)

Within When both Geo Spec Tables specify the same location, this has a “within” application.

Example Betw/And Geo Spec Tables = N GB – N GB Application: within the United Kingdom. .

TSIs Because the Geo Spec Tables have to match against a specific sector/portion of travel on the fare component, any TSI used in either Table must identify a specific point, rather than a portion of travel. If a TSI is used in one or both tables that do not identify a specific point(s) (e.g. TSI 18 international sectors), then processing will automatically no match the Category 12 Record 3.

When a specified TSI can match to more than one point on the fare component, then processing will use the first matched point when validating the Between/And travel. Example 1 Betw Geo Spec Table = TSI 19 (domestic sectors) And Geo Spec Table = TSI 42 (departure of each transatlantic sector) Application: No match the Category 12 Record 3 because TSI 19 does not identify a specific point.

Example 2 Betw Geo Spec Table = TSI 48 (departure of first international sector) And Geo Spec Table = TSI 42 (departure of each transatlantic sector) Application: Attempt to match a sector/portion of travel between the departure of the first international sector on the fare component and the departure of a transatlantic sector.

Page E.03.12.57 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Travel Portion (byte 45) Data in the Between/And Geo Spec Tables has the same match application to the fare component regardless of the Travel Portion value. The match application does not vary based on Travel Portion value. However, the application of the Travel Portion values 3 (per transfer) and 5 (per coupon) changes when data is present in Between/And Geo Spec Tables, as follows:

Travel Portion value 3 (Transfer): Applies on all ticketed intermediate points within the travel that matches the Between/And Geo Spec Tables (applies to connections and stopovers).

Travel Portion value 5 (Coupon): Applies for each flight coupon within the travel that matches the Between/And Geo Spec Tables (for ticketless travel, each sector/segment represents a flight coupon). If there are multiple matches on the fare component to the Between/And Geo Spec Tables, then the surcharge applies to each flight coupon within each matched Between/And travel.

Application of Other Match Criteria Data in the Between/And Geo Spec Tables alters the match application for all other match fields in the Category 12 Record 3 in that the other match fields will validate against the travel that matches the Between/And Geo Spec Tables. Rather than validating against the entire fare component, data in the following fields validates against the travel that matches the Between/And Geo Spec Tables: • Start/Stop Dates (bytes 14-25) • Start/Stop Time (bytes 26-33) • Appl (Byte 34) • Day of Week (Bytes 35-40) • Equipment Code (Bytes 42-44) • From/To/Via Geo Spec Table (bytes 47-54) • RBD (Bytes 119-120) • Carrier/Flight Table 986 (bytes 121-128)

Refer to applicable sections for each of the above match fields for further information.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.58 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.11 Charges - Appl (Byte 71)

The Appl field is a match field and indicates to whom the surcharge applies as well as the positive or negative application of the surcharge amount specified in Charges (bytes 72-93). Validation of the Appl value is based on the Passenger Type Code (PTC) of the passenger traveling at the fare on the fare component being validated. Valid Appl Byte 71 values and their application follow:

Positive Negative Application Processing Processing Blank A Surcharge applies to any passenger (same application as value 2) 1 B Child/Infant surcharge. Surcharge applies to any child or infant passenger (refer to the PTC hierarchy for a list of PTCs that map to child). If the intent is that the surcharge apply to only a child or only an infant, then the data may be entered with an IF to Category 1 table with Byte 71 value Blank. 2 C Both Adult and Child/Infant surcharge. Surcharge applies to any passenger (same application as BLANK) 3 D Both Adult and Child/Infant surcharge, but child/infant is discounted. Surcharge applies to any passenger. Surcharge amount is discounted for any child or infant PTC according to the discount percentage in Category 19 (applicable Category 19 data may be at any level). If there is no Category 19 or if Category 19 does not specify a percentage (e.g. Category 19 indicates a specified amount), then there is no discount and the full surcharge amount applies. 4 E Adult surcharge. Surcharge applies to any adult passenger. Surcharge does not apply to any child or infant passenger. (Refer to the PTC hierarchy for a list of PTCs that map to adult/blank.)

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.59 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.12 Charges - 1st Currency Charge: Amount, First Currency, Decimal (Bytes 72-78, 79-81, 82)

These fields are used to specify the actual surcharge amount, currency and decimal places in the amount. The surcharge amount may be a positive or negative amount. A positive amount indicates that the charge amount is a surcharge and must be added to the applicable fare. A negative amount indicates that the charge amount is a reduction and must be subtracted from the applicable fare. The amount fields do not carry the +/- sign. Positive or negative amount is determined by the value in Charge-Appl Byte 71. Please refer to the section for Charges-Appl where the values indicate positive/negative processing.

When processing has matched the applicable fields in Category 12 and determined that a surcharge is applicable, processing will attempt to search for a surcharge currency and amount that is the same as the currency of the fare being validated. If 1st Currency Charge is present and 2nd Currency Charge is not present, if a currency and amount that is the same as the currency of the fare being validated is not found in the Category 12 Record 3, then convert the available amount and currency to the currency of the fare being validated (refer to the following section for an explanation if both 1st Currency Charge and 2nd Currency Charge are present).

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.60 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.13 Charges - 2nd Currency Charge: Amount, Second Currency, Decimal (bytes 83-89, 90-92, 93)

These fields are used to specify the actual surcharge amount, currency and decimal places in the amount in a second currency. These fields are only used if the currency differs from the First Currency (Bytes 79-81). The surcharge amount may be a positive or negative amount. A positive amount indicates that the charge amount is a surcharge and must be added to the applicable fare. A negative amount indicates that the charge amount is a reduction and must be subtracted from the applicable fare.

When processing has matched the applicable fields in Category 12 and determined that a surcharge is applicable, processing will attempt to search for a surcharge currency and amount in the First and Second Currency fields that is the same as the currency of the fare being validated. If a currency and amount that is the same as the currency of the fare being validated is not found in the Category 12 Record 3, then convert both available amounts and currencies to the NUC level, take the lowest, and convert to the currency of the fare being validated.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.61 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.14 Charges - Percent (Bytes 94-100)

These fields specify the surcharge as a percentage amount. When a percent is entered, the Base field (Byte 101) must specify that the percentage should be applied to the fare amount. The percentage is calculated based on full the published fare amount specified on the Fare Record or the full calculated fare amount created via Fare by Rule (Category 25). If the fare amount is specified as RT then the percent is based on the RT amount (it is not based on the half RT amount). If the fare amount is specified as OW, then the percent is based on the OW amount.

Example Surcharge = 10%

LON-NYC FARE1 = 800.00 GBP RT LON-NYC FARE2 = 600.00 GBP RT

Travel is: LON-NYC-LON Round Trip pricing unit Outbound: LON-NYC on FARE1 (1/2 RT amount = 400.00) Inbound: NYC-LON on FARE2 (1/2 RT amount = 300.00)

Surcharge application:

Outbound Surcharge: 80.00 GBP (10% x 800.00) Inbound Surcharge: 60.00 GBP (10% x 600.00)

Edits prevent entering a percentage if a surcharge amount is entered in bytes 72-82. Additionally, edits prevent entering a percentage as a reduction (negative surcharge). See section 4.1.15 Charges – Base below for examples of the use of the Percent (Bytes 94-100) with Base (Byte 101).

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.62 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.15 Charges - Base (Byte 101)

The Base field is used to specify that the surcharge percentage applies to the fare. Whenever the Percent field (Bytes 94-100) is populated, the Base field (Byte 101) value F must also be entered.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.63 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.16 Override Date Table Number 994 (Bytes 102-109)

A number referring to a table containing dates on which travel, ticketing and/or reservations are valid for the data in this category. When present, it further defines the specific date range within Effective/Discontinue dates of the Record 2. If the reservation, ticketing and/or travel dates of the fare being processed are not within the dates specified in the Override Date Table, no-match and continue processing. If no further tables/sets or all other tables contain 994 tables that do not match, apply the system assumption for this category. Refer to 994 Data Application for further details.

4.1.17 Text Table Number 996 (Bytes 110-117) and Unavailable Data Tag (Byte 118)

When the Unavailable Data Tag is set to value ‘X’ (unavailable data), then no surcharge applies for the fare being created. Value “X” causes a “fail” condition for the subset, but the fare being validated will not fail processing. Processing will read on to the next subset. When the Unavailable Data Tag is set to value ‘Y’(text data only), retrieve the referenced 996 Text Table for text display. The 996 table has no impact on itinerary pricing; therefore, treat the table as not applicable and continue processing. If a single table is coded with an Unavailable Data Tag set to ‘Y’, the table would not be applicable and processing would apply the system assumption for this category. If a ‘Then, And’ set is coded and the ‘Then’ table has an Unavailable Data Tag set to ‘Y’, only the ‘And’ table would need to be satisfied.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.64 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.18 RBD (Bytes 119-120)

The RBD field indicates a surcharge is applicable when the travel is booked in a specific Reservation Booking Designator (RBD). Data in this field validates against the marketing carrier’s RBD as booked on sector(s) of the fare component being validated. If this field is blank, then the surcharge applies for travel on any RBD.

Validation of the RBD is dependent upon the value in Travel Portion Byte 45 and the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70) as follows: Byte 45 Value RBD Validates Against: When Betw/And Geo Spec Tables are value When Betw/And Geo Spec Tables contain data 00000000 (blank) Blank, 1, 2, 4, 6 Any sector on the fare component being validated. Any sector on the travel that matches the Between/And Only one sector on the fare component must satisfy the Geo Spec Tables. Only one sector on the travel must RBD in order to match the table. If multiple flight satisfy the RBD in order to match the table. If sectors satisfy the RBD, the surcharge is still applied multiple flight sectors satisfy the RBD, the surcharge is only once per fare component/ticket/direction still applied only once per fare (dependent upon the value in Byte 45). component/ticket/direction (dependent upon the value in Byte 45). 3 Each sector into and/or out of each intermediate Each sector into and/or out of each intermediate ticketed point on the fare component being validated. ticketed point on the travel that matches the Only one sector into or out of an intermediate ticketed Between/And Geo Spec Tables. Only one sector into point on the fare component must satisfy the RBD in or out of an intermediate ticketed point on the travel order to match the table. If multiple flight sectors into must satisfy the RBD in order to match the table. If or out of a ticketed point satisfy the RBD, the multiple flight sectors into or out of a ticketed point surcharge is applied for each intermediate ticketed satisfy the RBD, the surcharge is applied for each point that is matched. intermediate ticketed point that is matched. 5 Each sector on the fare component being validated. Each sector on the travel that matches the Only one sector on the fare component must satisfy the Between/And Geo Spec Tables. Only one sector on the RBD in order to match the table. If multiple flight travel must satisfy the RBD in order to match the table. sectors satisfy the RBD, the surcharge is applied for If multiple flight sectors satisfy the RBD, the each matched sector. surcharge is applied for each matched sector.

Page E.03.12.65 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

NOTE 1: The presence of match data in Equipment (bytes 42-44), Carrier/Flight Table 986 (bytes 121-128), and/or From/To/Via Geographic Specification Table (Bytes 47-54) may alter the point on the fare component/travel (as specified by Travel Portion Byte 45 and Between/And Geo Spec Tables) where validation occurs. NOTE 2: Edits prevent data in RBD when Surcharge Type (byte 41) is value I (Side Trip).

When validating RBD against a sector of the fare component, if the sector contains unticketed points, all travel on the sector must be on the specified RBD in order to match (all RBDs on the sector must match the RBD specified in Category 12).

When the RBD validates against the fare component being validated as specified by Travel Portion Byte 45 and the Between/And Geo Spec Tables (and other conditions within the category are met), then the surcharge applies according to the value in Byte 45.

Match criteria in the following fields are validated against the sector specified by the value in the RBD field (within the confines of Travel Portion Byte 45 and the Between/And Geo Spec Tables): - Start/Stop Dates (bytes 14-25) - Start/Stop Time (bytes 26-33) - Appl (Byte 34) - Day of Week (Bytes 35-40) - Equipment Bytes 42-44 - From/To/Via Geo Spec Table (Bytes 47-54) - Carrier/Flight Table 986 (bytes 121-128) NOTE: There is an edit which prevents the presence of data in RBD (Bytes 119-120) field when Surcharge Type is value I (Side Trip Surcharge).

Match validation for RBD and the fields above must be against the same point on the fare component being validated. Validation of Start/Stop Dates (bytes 14-25), Start/Stop Time (bytes 26-33), and Day of Week (Bytes 35-40) requires a departure validation unless otherwise specified by the use of an arrival TSI in a From/To/Via Geo Spec Table (Bytes 47-54).

Example: • Travel Portion Byte 45 is value Blank (per fare component) • Day of Week Bytes 35-40 is Mon. • RBD bytes 119-120 is F Processing will validate any sector on the fare component being validated where the sector is booked in RBD F and where departure of the sector is on Monday. Although Byte 45 value Blank indicates that Day of Week validation is against the departure from the origin of the fare component being validated, the RBD field further restricts this

Page E.03.12.66 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

validation and causes Day of Week to validate against the departure from the origin of the sector booked in RBD F. (Match data validates against the same point.) NOTE: If the intent is that the Day of Week validates against the origin of the fare component being validated rather than the sector booked in RBD F, then Day of Week data should be entered in an IF Cat 02 table rather than in Cat 12 (e.g. THEN Cat 12 RBD F IF Cat 2 Mon).

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.67 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.1.19 Carrier/Flight Table 986 (Bytes 121-128)

The Carrier/Flight Table 986 field indicates a surcharge is applicable for travel on specific marketing/operating carriers and/or flight numbers/ranges. If this field is value 00000000 (blank), then the surcharge applies for travel on any carrier and flight.

Table 986 consists of up to 50 recurring segments. The relationship among the fields within a single segment is AND. The relationship among the segments is AND/OR. Processing must match at least one segment. A match of any one segment within the table is a match for the travel being validated. Additionally, a match to multiple segments within the table is a match for the travel being validated.

The following fields exist within each recurring segment in Table 986: • Marketing Carrier (Table 986 bytes 10-12) • Operating Carrier (Table 986 bytes 13-15) • Flight No. 1 (Table 986 bytes 16-19) • Flight No. 2 (Table 986 bytes 20-23)

Marketing/Operating Carrier Fields The marketing carrier and/or the operating carrier can be a specific carrier code or a generic Alliance carrier code (such as *A signifying Star Alliance, *O signifying One World, or *S signifying Sky Team) Refer to Appendix M for a list of applicable alliance codes and the participating carriers in each code. The participating carriers in the alliance code have an AND/OR relationship. At least one participating carrier must be matched in order to satisfy the Table 986 segment requirement

The carrier code in the Marketing Carrier field(or the participating carriers in the specified generic alliance carrier code ) matches against the carrier code on the flight coupon(s) on the fare component travel (as specified by Travel Portion byte 45 and data in the Between/And Geo Spec Tables) being validated. Edits require that the marketing carrier must always be entered whenever a Table 986 segment is entered. If a generic alliance carrier code is specified, then at least one of the participating carriers must match against the carrier code on the flight coupon(s) on the fare component travel in order to constitute a match to the Marketing Carrier field on the Table 986 segment

The carrier code in the Operating Carrier field (or the participating carriers in the specified generic alliance carrier code) validates against the carrier that provides flight service on the fare component travel (as specified by Travel Portion byte 45 and data in the Between/And Geo Spec Tables) being validated. The operating carrier for a specified travel may be the same or different from the marketing carrier for that same travel. For example, in a schedule that shows a flight published under an

Page E.03.12.68 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

‘LH’ code from FRA to WAS, LH will appear on the flight coupon; however, UA may actually provide the flight service from FRA to WAS, in this case LH is the marketing carrier, and UA is the operating carrier. If a generic alliance carrier code is specified, then at least one of the participating carriers must match against the operating carrier code that provides flight service in order to constitute a match to the Operating Carrier field on the Table 986 segment. Operating Carrier is defined as:

Operating Carrier = The carrier who owns the schedule record (SSIM file) unless that record contains a value in the DEI050 field which identifies the operating carrier of the segment. DEI050 is a data element found in a SSIM file (Standard Schedules and Information Manual). In order to use this product, carriers should file the operating carrier (and operating carrier flight number) in the DEI050 of the schedules record (as opposed to the DEI027). ATPCO will add this recommended practice to the reference manual for this product. If carriers do not file a value in DEI050, systems will assume the marketing carrier and flight number is the same as the operating carrier and flight number.

Flight No. 1/Flight No. 2 Fields Flight No. 1 may be a specific flight number or value ‘****’ indicating “any flight number.” Flight No. 2 may be a specific flight number or blank.

When data is present in both flight number fields, the relationship between the two fields is THROUGH (apply as a range of flights between Flight No. 1 and Flight No. 2). Example: Flight No. 1 = 1000 Flight No. 2 = 1999 The data indicates that the travel being validated (as specified by Travel Portion byte 45 and data in the Between/And Geo Spec Tables) must be on flight number 1000 through 1999.

When data is present in Flight No. 1 and Flight No. 2 is blank, Flight No. 1 applies as a single flight. Example: Flight No. 1 = 1000 Flight No. 2 = blank The data indicates that the travel being validated (as specified by Travel Portion byte 45 and data in the Between/And Geo Spec Tables) must be on flight number 1000.

Page E.03.12.69 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Validation of the Carrier/Flight Table 986 is dependent upon the value in Travel Portion Byte 45 and the presence or absence of data in the Between/And Geo Spec Tables (bytes 55-62, 63-70) as follows: Byte 45 Value Carrier/Flight Table 986 Validates Against: When Betw/And Geo Spec Tables are value When Betw/And Geo Spec Tables contain data 00000000 (blank) Blank, 1, 2, 4, 6 Any sector on the fare component being validated. Any sector on the travel that matches the Between/And Only one sector on the fare component must satisfy Geo Spec Tables. Only one sector on the travel must Carrier/Flight Table 986 in order to match the table. If satisfy Carrier/Flight Table 986 in order to match the multiple flight sectors satisfy the Carrier/Flight Table table. If multiple flight sectors satisfy Carrier/Flight 986, the surcharge is still applied only once per fare Table 986, the surcharge is still applied only once per component/ticket/direction (dependent upon the value fare component/ticket/direction (dependent upon the in Byte 45). value in Byte 45). 3 Each sector into and/or out of each intermediate Each sector into and/or out of each intermediate ticketed point on the fare component being validated. ticketed point on the travel that matches the Only one sector into or out of an intermediate ticketed Between/And Geo Spec Tables. Only one sector into point on the fare component must satisfy Carrier/Flight or out of an intermediate ticketed point on the travel Table 986 in order to match the table. If multiple must satisfy Carrier/Flight Table 986 in order to match flight sectors into or out of a ticketed point satisfy the table. If multiple flight sectors into or out of a Carrier/Flight Table 986, the surcharge is applied for ticketed point satisfy Carrier/Flight Table 986, the each intermediate ticketed point that is matched. When surcharge is applied for each intermediate ticketed matching multiple sectors, all sectors do not have to point that is matched. When matching multiple sectors, match the same Table 986 segment, rather each sector all sectors do not have to match the same Table 986 must match at least one segment. segment, rather each sector must match at least one segment. 5 Each sector on the fare component being validated. Each sector on the travel that matches the Only one sector on the fare component must satisfy Between/And Geo Spec Tables. Only one sector on the Carrier/Flight Table 986 in order to match the table. If travel must satisfy Carrier/Flight Table 986 in order to multiple flight sectors satisfy Carrier/Flight Table 986, match the table. If multiple flight sectors satisfy the surcharge is applied for each matched sector. Carrier/Flight Table 986, the surcharge is applied for When matching multiple sectors, all sectors do not each matched sector. When matching multiple sectors, have to match the same Table 986 segment, rather each all sectors do not have to match the same Table 986 sector must match at least one segment segment, rather each sector must match at least one segment

Page E.03.12.70 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

NOTE 1: The presence of match data in Equipment (bytes 42-44), RBD (bytes 119-120), and/or From/To/Via Geographic Specification Table (Bytes 47-54) may alter the point on the fare component/travel (as specified by Travel Portion Byte 45 and Between/And Geo Spec Tables) where validation occurs. NOTE 2: Edits prevent data in Carrier/Flight Table 986 when Surcharge Type (byte 41) is value I (Side Trip).

When validating Table 986 against a sector of the fare component, if the sector contains unticketed points, all travel on the sector must match Table 986 in order to match (all carriers/flights on the sector do not have to match the same Table 986 segment, but all must match at least one Table 986 segment in order to match the Category 12).

When Carrier/Flight Table 986 validates against the fare component being validated as specified by Travel Portion Byte 45 and the Between/And Geo Spec Tables (and other conditions within the category are met), then the surcharge applies according to the value in Byte 45.

Match criteria in the following fields are validated against the sector specified matched to Carrier/Flight Table 986 (bytes 121-128) (within the confines of Travel Portion Byte 45 and the Between/And Geo Spec Tables): - Start/Stop Dates (bytes 14-25) - Start/Stop Time (bytes 26-33) - Appl (Byte 34) - Day of Week (Bytes 35-40) - Equipment Bytes 42-44 - From/To/Via Geo Spec Table (Bytes 47-54) - RBD (bytes 119-120) NOTE: There is an edit which prevents the presence of data in Carrier/Flight Table 986 (Bytes 121-128) field when Surcharge Type is value I (Side Trip Surcharge).

Match validation for Carrier/Flight Table 986 and the fields above must be against the same point on the fare component being validated. Validation of Start/Stop Dates (bytes 14-25), Start/Stop Time (bytes 26-33), and Day of Week (Bytes 35-40) requires a departure validation unless otherwise specified by the use of an arrival TSI in a From/To/Via Geo Spec Table (Bytes 47-54).

Example: • Travel Portion Byte 45 is value Blank (per fare component) • Day of Week Bytes 35-40 is Mon. • Carrier/Flight Table 986 bytes 121-128 is marketing carrier XX Flight 100 Processing will validate any sector on the fare component being validated where the sector is on marketing carrier XX flight 100 and where departure of the sector is on Monday. Although Byte 45 value Blank indicates that Day of Week

Page E.03.12.71 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

validation is against the departure from the origin of the fare component being validated, the Carrier/Flight Table 986 field further restricts this validation and causes Day of Week to validate against the departure from the origin of the sector that matches Table 986. (Match data validates against the same point.) NOTE: If the intent is that the Day of Week validates against the origin of the fare component being validated rather than the sector that matches Table 986, then Day of Week data should be entered in an IF Cat 02 table rather than in Cat 12 (e.g. THEN Cat 12 Carrier/Flight Table 986 IF Cat 2 Mon).

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.72 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.2 Reconciliation between General and Fare Rule Levels

When Category 12 data is present in a fare rule and general rule, the data from both the fare rule and general rule will apply (unless Record 2, General Rule Application (Byte 102) is coded ‘X’).

When Byte 45 is value 4 (per ticket) or value 6 (per direction), processing will compare within each level; processing will not compare across levels. Value 4 applies per ticket per level. Value 6 applies per direction per level.

Processing will take the following steps: • Run through all fare rule surcharge data and arrive at an amount. • Run through all general rule surcharge data and arrive at an amount. • Add the amounts from the 2 levels and apply. NOTE: The above steps are for illustrative purposes and do not reflect the order in which any subscriber must process the data.

Refer to the example(s) under this same section number in the Data Application for Category 12 – Examples document.

Page E.03.12.73 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

4.3 Category 12 versus IF to Category 4

Sucharges can be qualified based on geographic specification and carrier/flight data within Category 12 and/or Category 4. When specifed using Category 12, surcharge amount is applied based on the combined application of the geographic specification data, the carrier/flight data, and the Travel Portion byte 45 (as well as all other Category 12 match criteria). When specified using an IF to Category 4 condition, the Category 4 data is simply matched and does not alter or impact the application of the data within Category 12. Refer to the examples below:

Example: Geo and Flight data in Category 12

THEN Category 12:

Surcharge = 10.00 USD Travel Portion = 5 (Per Coupon) Cxr/Flight Table 986 = Carrier XX Flight 1000-1999 Sector/Portion = Sector Between/And Geos = LON-DXB

The data indicates a surcharge of USD 10.00 applies for each coupon between LON-DXB on carrier XX flight 1000- 1999.

NYC-DXB fare component where travel is:

NYC---XX flt 2000---LON---XX flt 1000---DXB

Result: Apply 10.00 surcharge for LON-DXB coupon

Page E.03.12.74 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Example: Geo and Flight data in IF to Category 4

THEN Category 12:

Surcharge = 10.00 USD Travel Portion = 5 (Per Coupon)

IF Category 4 Cxr/Flight Table 986 = Carrier XX Flight 1000-1999 Between/And Geos = LON-DXB

The data indicates if the fare component contains travel between LON and DXB on carrier XX flight 1000-1999, then the data in Category 12 applies. Category 12 indicates a surcharge of USD 10.00 applies per coupon.

NYC-DXB fare component where travel is:

NYC---XX flt 2000---LON---XX flt 1000---DXB

Result: Match the Category 4 (travel between LON and DXB is on the specified carrier and flight). Apply 10.00 surcharge per coupon: 10.00 for NYC-LON plus 10.00 for LON-DXB. Total surcharge = 20.00

Page E.03.12.75 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

5.0 TRAVEL SEGMENT INDICATOR (TSI)

The Travel Segment Indicator (TSI) field is in the Surcharge Appl Geographic Specification Table (Bytes 47-54) and in the two Side Trip Geographic Specification Tables (Bytes 55-62 and 63-70) . When a TSI is entered, processing will attempt to match the portion of travel specified by the TSI(s) to the portion of the fare component being validated specified by Travel Portion Byte 45. If the fare component travel matches the specified TSI(s), then a surcharge will be applied according to the value in Byte 45.

The TSI application does not have to be within the confines of the category application. When a Pricing unit or Journey TSIs is entered, then processing will attempt to validate the specified point/portion of travel against the fare component being validated and may no match fare components that do not contain the specified point/portion of travel.

Following is a list of TSIs currently used in Category 12 and the amount of usage as of March 2007. The table is arranged by usage in descending order beginning with the most commonly used TSI. Usage is based on the number of Record 2 sequences with a Category 12 Record 3 table containing the specified TSI.

TSI Definition Application Usage 42 Departure of each transatlantic sector FC 5,097 18 All international sectors FC/PU 4,921 19 All domestic sectors FC/PU 4,902 31 Transatlantic sector(s) FC/PU 2,211 50 Departure from the following geographic locale FC/PU 845 49 Arrival at the following geographic locale FC/PU 755 43 Departure of each transpacific sector FC 484 89 On each intercontinental sector FC/PU 343 32 Transpacific sectors(s) FC/PU 309 55 Departure of inbound transpacific sector PU 233 21 Departure from stopover FC/PU 171 48 Departure of first international sector FC/PU 153 03 Departure of each trip FC 77 41 Departure of outbound transpacific sector PU 38 82 Departure from gateway FC/PU 23 01 Departure from fare origin PU 16

Page E.03.12.76 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

TSI Definition Application Usage 40 Departure of outbound transatlantic sector PU 15 56 Departure of inbound transatlantic sector PU 13 54 All Sectors FC/PU 6 08 Departure of last segment FC/PU 3 58 Departure of last international sector FC/PU 3 36 Departure from last international stopover point FC/PU 2 47 Overwater segment(s) FC/PU 2 88 Departure of first inbound intercontinental PU 2 05 Departure from last stopover FC/PU 1

Page E.03.12.77 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

6.0 CODING CONVENTIONS

6.1 Waiver of Advanced Purchase Requirements or Maximum Stay When the surcharge applies for a waiver of the advanced purchase requirements or the maximum stay requirements, the Surcharge Type (Byte 41) value should be M (Waiver for Advance Purchase Requirements) or P (Maximum Stay Waiver), respectively. The Category 12 data string must address qualifying information in Category 5 or Category 7 as applicable. Additionally, the data in Category 5 or Category 7 must address the permissible (surcharged and non-surcharged) advanced purchase or maximum stay requirements in order for processing to pass the Category 5 or Category 7 data tables.

When different surcharges apply based on different maximum stay restrictions, the more restrictive maximum stay qualifying condition should be entered first. Example: Maximum stay is 30 days. Except, may be extended to 6 months for a surcharge of USD 100.00 and may be extended to 12 months for a surcharge of USD 200.00. Data in Category 12 = THEN Cat 12 USD 0.00 IF Cat 07 Max Stay 30 days THEN Cat 12 USD 100.00 IF Cat 07 Max Stay 06 months THEN Cat 12 USD 200.00 IF Cat 07 Max Stay 12 months

Example – Waiving the Maximum Stay Carrier Intent: Maximum stay is 30 days, except, the maximum stay may be extended to 6 months for a surcharge of USD 100.00 ATPCO will enter this carrier instruction as follows:

CATEGORY 7 THEN Category 7 Record 3 Byte 14 Bytes 19-21 Bytes 22-23 Bytes 25-32 Bytes 33-40 Retn Trvl Code Max Stay Unit of Time From Geo Spec Table To Geo Spec Table C 030 Db TSI 01 TSI 05 OR Category 7 Record 3 Byte 14 Bytes 19-21 Bytes 22-23 Bytes 25-32 Bytes 33-40 Retn Trvl Code Max Stay Unit of Time From Geo Spec Table To Geo Spec Table C 006 Mb TSI 01 TSI 05

Page E.03.12.78 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

The data indicates that travel from last stopover must begin no later than 30 days after the day after departure from the fare origin, OR that travel from last stopover must begin no later than 6 months after the day after departure from the fare origin

CATEGORY 12 THEN Category 12 Record 3 Byte 41 Byte 45 Bytes 72-78 Bytes 79-81 Sur Type Trvl Prt Amt Curr P BLANK + 0.00 USD IF Category 7 Record 3 Byte 14 Bytes 19-21 Bytes 22-23 Bytes 25-32 Bytes 33-40 Retn Trvl Code Max Stay Units of Time From Geo Spec Table To Geo Spec Table C 030 Db TSI 01 TSI 05 ELSE Category 12 Record 3 Byte 41 Byte 45 Bytes 72-78 Bytes 79-81 Sur Type Trvl Prt Amt Curr P 1 + 100.00 USD The data indicates that if travel from last stopover begins no later than 30 days after the departure from the fare origin, then there is no surcharge. Otherwise, a surcharge of USD 100.00 applies to the fare component being validated for waiving the maximum stay requirements.

Page E.03.12.79 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

A – Round Trip between LAX-CHI Depart 01Jan 99 LAX CHI Return 20Jan 99 When pricing the LAX-CHI fare component that resolves to the Record 3 above: No surcharge applies. Processing will pass the first Category 7 table. When validating Category 12, travel from last stopover (CHI) is not later than 30 days after departure from fare origin (LAX). Processing will match the IF table and apply the data in the THEN table.

When pricing the CHI-LAX fare component that resolves to the Record 3 above: No surcharge applies. Processing will pass the first Category 7 table. When validating Category 12, travel from last stopover (CHI) is not later than 30 days after departure from fare origin (LAX). Processing will match the IF table and apply the data in the THEN table.

B – Round Trip between LAX-CHI Depart 01Jan 99 LAX CHI Return 15Mar 99

When pricing the LAX-CHI fare component that resolves to the Record 3 above: A surcharge of USD 100.00 applies to the fare component being validated. Processing will pass the second Category 7 data table. When processing Category 12, processing will no match (fail) the IF and apply the data in the ELSE table. Travel from last stopover (CHI) is later than 30 days after departure from fare origin (LAX), and a surcharge applies.

When pricing the CHI-LAX fare component that resolves to the Record 3 above: A surcharge of USD 100.00 applies to the fare component being validated. Processing will pass the second Category 7 data table. When processing Category 12, processing will no match (fail) the IF and apply the data in the ELSE table. Travel from last stopover (CHI) is later than 30 days after departure from fare origin (LAX), and a surcharge applies.

Page E.03.12.80 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Category 5 – Open Returns

Information concerning surcharges paid to allow open returns on fares which normally require that all sectors be confirmed should be coded in Category 5. Note that depending upon the nature of the restrictions, the Category 5 data may need to be entered in Table No. 996 (Free Form Text) which is not automated.

Example Restriction = The ticket must show confirmed reservations for the entire journey, except from/to Belgium the ticket must show confirmed reservations for the outbound journey and the ticket may be issued with an open return for an additional charge of USD 100.00. Coding: Category 5 Record 2 = from/to Belgium Category 5 Record 3s = THEN All sectors must be confirmed (byte 37 value X) OR Confirmed Geo Spec Table with TSI 54 (all sectors) (byte 37 value BLANK, bytes 38-45 value TSI 54) Note: According to data application for Category 5, when data is present in the Confirmed Geo Spec Table and the Confirmed Sector field byte 37 is blank, validate Geo Spec Table on fare components prior to point of turnaround and apply confirmed sector requirement to that portion of travel. Category 12 Record 2 = from/to Belgium Category 12 Record 3s = THEN No surcharge IF Cat 05 all sectors confirmed (byte 37 value X) ELSE Surcharge USD 100.00

Page E.03.12.81 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

6.2 Waiver of Minimum Stay When the surcharge applies for a waiver of the minimum stay requirements, the Surcharge Type (Byte 41) value should be Q (miscellaneous) as there is no corresponding Surcharge Type for a waiver of minimum stay. The Category 12 data string must address qualifying information in Category 6. Additionally, the data in Category 6 must address the permissible (surcharged and non- surcharged) minimum stay requirements in order for processing to pass Category 6 (see Category 7 example in section 6.1 of this document)

Page E.03.12.82 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

6.3 Surcharge for Paper Ticket When the surcharge applies for a paper ticket, the Surcharge Type (Byte 41) value should be Q (miscellaneous) and the Travel Portion (Byte 45) value should be 4 (per ticket). The Category 12 data string must address qualifying information in Category 15. Additionally, Category 15 must address the permissible means of ticket issue in order for processing to pass Category 15.

Example – Surcharge for Paper Ticket Carrier Intent: There are no ticket issuance restrictions; however, when a paper ticket is issued, a surcharge of USD 100.00 applies per ticket. ATPCO will enter this carrier instruction as follows:

CATEGORY 15 Unless additional sales restrictions are instructed by the carrier, no data will be entered in Category 15 (system assumption of no sales restrictions applies for this level). If any data is entered in Category 15 at any level, then Ticket Issuance Fields (bytes 60-68) must permit Electronic Ticketing (ET) Byte 68 and any or all other types of ticket issuance (bytes 60-67). Refer to Data Application for Category 15 for further information on processing the Ticket Issuance fields.

CATEGORY 12 THEN Category 12 Record 3 Byte 41 Byte 45 Bytes 72-78 Bytes 79-81 Sur Type Trvl Prt Amt Curr Q BLANK + 0.00 USD IF Category 15 Record 3 Byte 60 Byte 61 Byte 62 Byte 63 Byte 64 Byte 65 Byte 66 Byte 67 Byte 68 Mail PTA Mech Self PTA=TKT ATM Sat Printer SATO/CATO Elec Tktg Blank Blank Blank Blank Blank Blank Blank Blank R ELSE Category 12 Record 3 Byte 41 Byte 45 Bytes 72-78 Bytes 79-81 Sur Type Trvl Prt Amt Curr Q 4 + 100.00 USD The data indicates that if ticket is issued by Electronic Ticketing, there is no surcharge. Otherwise, a surcharge of USD 100.00 will apply per ticket.

Page E.03.12.83 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

A – Round Trip between LAX-CHI Ticket Issued by ET LAX CHI

When pricing the LAX-CHI and CHI-LAX fare components that each resolve to the Record 3s above: No surcharge applies. • Ticket is issued by ET; therefore, match the IF table, and read the THEN table. • Match the THEN table. No surcharge applies.

B – Round Trip between LAX-CHI Ticket Issued by PTA LAX CHI

When pricing the LAX-CHI and CHI-LAX fare components that each resolve to the Record 3s above: USD 100.00 surcharge applies. • Ticket is issued by PTA; therefore, no match (fail) the IF table, and read the ELSE table. • Match the ELSE table. Apply USD 100.00 surcharge per ticket.

Page E.03.12.84 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

6.4 Peak Travel Time Surcharge Type The “Peak Travel Time” Surcharge Type value (Byte 41) refers to a ‘time of day’ as opposed to ‘time of year’.

6.5 TSIs When Travel Portion Byte 45 is value 3 (per transfer) and a TSI is entered in the From/To/Via Geographic Specification Table (Bytes 47-54), the TSI should reference a specific point because Byte 45 value 3 causes the surcharge to apply per each ticketed point on the fare component being validated and causes the match criteria to validate at this point(s). For example: Byte 45 Value 3 with TSI 21 (departure from stopover) is permitted. Byte 45 Value 3 with TSI 31 (transatlantic sectors) should not be permitted. Rather than using TSI 31, the carrier should be contacted to determine if another TSI would be more accurate [e.g. departure of each transatlantic sector (TSI 42) from an intermediate ticketed point (Byte 45 value 3) may be more accurate]. NOTE: There is an edit which prevents the presence of data in the Side Trip Geo Spec Tables (Bytes 55-62 and 63-70) when the Travel Portion (Byte 45) is value 3.

6.6 Byte 45 Value 2 (per RT) Value 2 should not be used when specifying surcharge amounts on a OW fare.

Byte 45 value 2 indicates that ½ of the surcharge amount applies to the fare component being validated. If value 2 is used in a surcharge provision for a OW fare, then processing will only apply ½ the amount to the OW fare component being validated. ATPCO should contact the carrier instructing the data to determine if another Byte 45 value better reflects the intent (e.g. Byte 45 value Blank or value 1, specifying per fare component, may better reflect the carrier’s intent).

Page E.03.12.85 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

7.0 Ticketing: Q Placement for Category 12 Data

Category 12 charges are reflected in the fare calculation on the ticket based on the Joint Passenger Service Conference (JPSC) Resolutions. Where and how they are reflected in the fare calculation is dependent upon whether the Category 12 charge is expressed as a positive (surcharge) or negative (reduction) charge amount. This application is defined in the following sections.

When reviewing the Examples in this section, the following assumptions apply: • All examples are provided for illustrative purposes only. They do not in any way reflect if or how any carrier will enter data in Category 12. • The itineraries provided in each example reflect possible pricing solutions. ATPCO recognizes multiple pricing solutions may be applicable for the itineraries provided. • Assume all points specified on the itineraries are ticketed points unless otherwise specified. Fare break, stopover, and connection points will be defined as necessary. • Assume all carriers specified on the itineraries are marketing carriers unless otherwise specified. The operating carrier will be defined as necessary. • For illustrative purposes only and to alleviate conversion processes in the examples, all Category 12 surcharge data is reflected in NUCs. In reality, the surcharge data in Category 12 will be in a specified currency (usually the currency of the fare) and then converted as applicable. • The Category 12 data reflected for each example is the only data that exists in the string (unless otherwise specified).

Page E.03.12.86 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing

7.1 Positive Surcharges All Category 12 surcharges expressed as a positive charge amount (based on Appl byte 71 value blank, 1, 2, 3, or 4) are reflected with the letter “Q” in the fare calculation (regardless of the Surcharge Type). The Q placement reflects the travel against which the surcharge applies and is expressed in the fare calculation under the standards set forth in the JPSC Resolution 722.3.16.7.

The travel against which the surcharge applies is determined based on the Category 12 Match fields (defined in Section 3.0 of this document) and the Travel Portion value (byte 45). As defined earlier in this document, the Category 12 Match fields and the Travel Portion value are used in conjunction to determine where to validate the match data and how to assess the surcharge. Additionally, this combined application is used to determine the travel against which the surcharge applies and the resulting Q placement on the fare calculation, within the standards set forth in the Ticketing Resolutions.

The Ticketing Resolutions provide standards for Q placement based on whether the Q applies to: • Single segment (coupon). Refer to JPSC 3.16.7.1 • Multiple consecutive segment (coupons). Refer to JPSC 3.16.7.2

Additionally, the Ticketing Resolutions specify standards when more than one surcharge (more than one Q) applies. Refer to JPSC 3.16.7.3. (Note this essentially indicates the multiple surcharges will be shown in the fare calculation one after the other within the “single segment” or “multiple consecutive segment” standards.)

The Q placement is detailed below for each Travel Portion value and based upon the “single segment” or “multiple consecutive segment” ticketing standards.

Pending Page E.03.12.87 Revised February 2013

DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

7.1.1 Travel Portion Value Blank, 1, or 2: “Per Fare Component” Surcharge

When the Travel Portion is value Blank, 1, or 2, the surcharge amount is assessed once per fare component provided processing matches the Category 12 data. The surcharge (Q) actually applies to the matched travel, defined as the travel that is matched against the qualifying criteria (match data) within Category 12. Processing will place the Q so that it applies to the matched travel. Where and how the Q is placed is dependent upon whether the matched travel is a single segment (sector) or multiple consecutive or non- consecutive segments (sectors) as follows:

Single segment: If the surcharge applies to a single sector (segment), imprint “Q” followed by the amount immediately after the matched sector to which it applies. Refer to JPSC 3.16.7.1

Consecutive segments: If the surcharge applies to multiple consecutive sectors (segments) within the fare component, imprint “Q” followed by the first and last cities of the consecutive sectors to which the surcharge applies, in the direction of travel, and the amount. This entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs. Refer to JPSC 3.16.7.2

Non-consecutive segments: If the surcharge applies to multiple non-consecutive sectors (segments) within the fare component, imprint “Q” followed by the first and last cities of the non-consecutive sectors to which the surcharge applies, in the direction of travel, and the amount. This entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs. Refer to JPSC 3.16.7.2

Page E.03.12.88 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Example 1 – No specific match criteria Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank J Blank 100.00 NUC The data indicates that a seasonal surcharge of USD 100.00 applies per fare component

Itinerary A: MNL-TYO-MNL RT Pricing Unit - ONLINE

Cxr XX Cxr XX SEL MNL TYO Cxr XX

Pricing: MNL-TYO fare component: Apply 100.00 for the fare component TYO-MNL fare component: Apply 100.00 for the fare component

Ticketing: MNL XX SEL XX TYO Q MNLTYO100.00M500.00 XX MNL Q100.00M500.00NUC1200.00

Itinerary B: MNL-TYO-MNL RT Pricing Unit - INTERLINE

Cxr ZZ Cxr XX SEL MNL TYO Cxr XX

Pricing: MNL-TYO fare component: Apply 100.00 for the fare component TYO-MNL fare component: Apply 100.00 for the fare component

Ticketing: MNL ZZ SEL XX TYO Q MNLTYO100.00M500.00 XX MNL Q100.00M500.00NUC1200.00

Page E.03.12.89 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Example 2 – Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr 01 Jan 31 Jan Blank Blank Blank Blank Blank Blank J Blank 100.00 NUC The data indicates that a seasonal surcharge of USD 100.00 applies per fare component where the departure from the origin of the fare component commences on 01Jan through 31Jan of any year

Itinerary A: MNL-TYO-MNL RT Pricing Unit

Dept 02Jan 11 Dept 03Jan 11 Cxr XX Cxr XX SEL MNL TYO Cxr XX Dept 30Jan 2011

Pricing: MNL-TYO fare component: Apply 100.00 for the fare component TYO-MNL fare component: Apply 100.00 for the fare component

Ticketing: MNL XX SEL XX TYO Q MNLTYO100.00M500.00 XX MNL Q100.00M500.00NUC1200.00

Page E.03.12.90 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Itinerary B: MNL-TYO-MNL RT Pricing Unit

Dept 30Jan 11 Dept 03Feb 11 Cxr XX Cxr XX SEL MNL TYO Cxr XX Dept 316 Feb 2011

Pricing: MNL-TYO fare component: Apply 100.00 for the fare component TYO-MNL fare component: No surcharge applies

Ticketing: MNL XX SEL XX TYO Q MNLTYO100.00M500.00 XX MNL M500.00NUC1100.00

Page E.03.12.91 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Example 3 – Equipment Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E Blank 100.00 NUC The data indicates that an equipment surcharge of NUC 100.00 applies per fare component when the fare component contains travel on equipment 380.

Itinerary A: SIN-PAR-SIN RT Pricing Unit – single and consecutive sectors

Equip 380 Equip 320 Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Equip 380 Equip 380

Pricing: SIN-PAR fare component: Apply 100.00 for SIN-LON PAR-SIN fare component: Apply 100.00 (collected once) based on PAR-LON and LON-SIN

Ticketing: SIN XX LON Q100.00XX PAR M500.00 XX LON XX SIN Q PARSIN100.00M500.00NUC1200.00

Itinerary B: SYD-LON OW Pricing Unit – non-consecutive consecutive sectors

Equip 380 Equip 777 Equip 380 Equip 320 Cxr XX Cxr XX Cxr ZZ Cxr ZZ SYD SIN DXB PAR LON

Pricing: SYD-LON fare component: Apply 100.00 for SYD-SIN and DXB-PAR

Ticketing: SYD XX SIN XX DXB ZZ PAR ZZ LON Q SYDPAR100.00M1000.00NUC1100.00

Page E.03.12.92 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Example 4 – RBD Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank R Blank Blank Blank Blank Z Blank 100.00 NUC The data indicates that an RBD surcharge of NUC 100.00 applies per fare component when the fare component contains travel in RBD R.

Itinerary A: SIN-PAR-SIN RT Pricing Unit – single and consecutive sectors

RBD R RBD Q Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX RBD R RBD R

Pricing: SIN-PAR fare component: Apply 100.00 for SIN-LON PAR-SIN fare component: Apply 100.00 (collected once) based on PAR-LON and LON-SIN

Ticketing: SIN XX LON Q100.00XX PAR M500.00 XX LON XX SIN Q PARSIN100.00M500.00NUC1200.00

Itinerary B: SIN-PAR OW Pricing Unit

RBD Q RBD R Cxr XX Cxr ZZ SIN LON PAR

Pricing: SIN-PAR fare component: Apply 100.00 for LON-PAR

Ticketing: SIN XX LON XX PAR Q100.00M500.00NUC600.00

Page E.03.12.93 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Itinerary C: SYD-LON OW Pricing Unit – non-consecutive consecutive sectors

RBD R RBD F RBD R RBD F Cxr XX Cxr XX Cxr ZZ Cxr ZZ SYD SIN DXB PAR LON

Pricing: SYD-LON fare component: Apply 100.00 for SYD-SIN and DXB-PAR

Ticketing: SYD XX SIN XX DXB ZZ PAR ZZ LON Q SYDPAR100.00M1000.00NUC1100.00

NOTE: Based on Ticketing Resolutions, a Q applicable to non-consecutive sectors is reflected as applicable between the start (SYD) and end (PAR) of the matched non-consecutive travel.

Itinerary D: SYD-PAR OW Pricing Unit – consecutive sectors

RBD R RBD R RBD F Cxr XX Cxr XX Cxr ZZ SYD SIN DXB PAR

Pricing: SYS-PAR fare component: Apply 100.00 for SYD-SIN and SIN-DXB

Ticketing: SYD XX SIN XX DXB ZZ PAR Q SYDDXB100.00M1000.00NUC1100.00

Page E.03.12.94 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Example 5 – Side Trip (Surcharge Type value I) Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank C SIN C BKK I Blank 100.00 NUC The data indicates that a side trip surcharge of USD 100.00 applies to the fare component being validated when the following occurs: • The fare component contains travel between intermediate ticketed points SIN and BKK; and • One end point of the SIN-BKK sector is transited twice on the fare component

Itinerary A: SYD-LON-SYD RT Pricing Unit

Cxr XX Cxr XX Cxr XX Cxr XX SYD SIN BKK SIN LON

SIN Cxr XX Cxr XX

Pricing: SYD-LON fare component: Apply 100.00 for SIN-BKK-SIN travel LON-SYD fare component: No surcharge

Ticketing: SYD XX SIN XX BKK ZZ SIN ZZ LON Q SINSIN100.00M1000.00XX SIN XX SYD M1000.00NUC2100.00

Page E.03.12.95 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Itinerary B: SYD-LON-SYD RT Pricing Unit

Cxr XX Cxr XX Cxr XX OPEN Cxr XX Cxr XX SYD SIN BKK SEL SIN LON

SIN Cxr XX Cxr XX

Pricing: SYD-LON fare component: Apply 100.00 for SIN-BKK (based on SIN transited twice) travel LON-SYD fare component: No surcharge

Ticketing: SYD XX SIN XX BKK Q100.00//SEL XX SIN ZZ LON M1000.00XX SIN XX SYD M1000.00NUC2100.00

Page E.03.12.96 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value Blank, 1, or 2: Per Fare Component Surcharges

Example 6 – Multiple Surcharges THEN Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E Blank 100.00 NUC The data indicates that an equipment surcharge of NUC 100.00 applies per fare component when the fare component contains travel on equipment 380. AND Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank F Blank 50.00 NUC The data indicates that a fuel surcharge of NUC 50.00 applies per fare component.

Itinerary: SYD-LON OW Pricing Unit

Equip 380 Equip 777 Equip 777 Cxr XX Cxr XX Cxr ZZ SYD SIN PAR LON

Pricing: SYD-LON fare component: Apply 100.00 for SYD-SIN plus 50.00 for SYD-LON

Ticketing: SYD XX SIN Q100.00XX DXB ZZ PAR ZZ LON Q SYDLON50.00M1000.00NUC1150.00

Page E.03.12.97 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing

7.1.2 Travel Portion Value 3: “Per Transfer” Surcharge

When the Travel Portion is value 3, the surcharge amount is assessed once per each matched transfers point. The surcharge (Q) actually applies to the consecutive segments into and out of the matched transfer point(s) (the transfer/s that matches the Category 12 data). Processing will place the Q so that it applies to the matched consecutive segments (sectors), as follows:

Imprint “Q” followed by the first city of the segment into the transfer point and the last city of the consecutive segment out of the transfer point, in the direction of travel, and the amount. This entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs . Refer to JPSC 3.16.7.2

Pending Page E.03.12.98 Revised February 2013

DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Example 1 – Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr 01Jan 31Jan Blank Blank Blank Blank Blank Blank J 3 100.00 NUC The data indicates that a seasonal surcharge of USD 100.00 applies to each transfer (each intermediate ticketed point) departing 01Jan through 31Jan of any year on the fare component being validated.

Itinerary A: MNL-TYO-MNL RT Pricing Unit

Dept 02Jan 11 Dept 03Jan 11 Cxr ZZ Cxr XX SEL MNL TYO Cxr XX Dept 28Jan 2011

Pricing: MNL-TYO fare component: Apply 100.00 for SEL (based on departure from SEL) TYO-MNL fare component: No surcharge

Ticketing: MNL XX SEL XX TYO Q MNLTYO100.00M500.00 XX MNL M500.00NUC1100.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.99 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Itinerary B: MNL-TYO-MNL RT Pricing Unit

Dept 02Jan 11 Dept 02Jan11 Dept 03Jan 11 Cxr ZZ Cxr XX Cxr XX TPE SEL MNL TYO Cxr XX Dept 28Jan 2011

Pricing: MNL-TYO fare component: Apply 100.00 for TPE plus 100.00 for SEL TYO-MNL fare component: No surcharge

Ticketing: MNL XX TPE XX SEL XX TYO Q MNLSEL100.00Q TPETYO100.00M500.00 XX MNL M500.00 NUC1200.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Itinerary B: MNL-TYO OW Pricing Unit

Dept 30Dec 10 Dept 03Jan 11 Cxr XX Cxr XX MNL SEL TYO

Pricing: MNL-TYO fare component: Apply 100.00 for SEL (based on departure from SEL)

Ticketing: MNL XX SEL XX TYO Q MNLTYO100.00M500.00 NUC600.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.100 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Example 2 – Equipment Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E 3 100.00 NUC The data indicates that an equipment surcharge of NUC 100.00 applies to each transfer (each intermediate ticketed point) where the sector into and/or out of the transfer is on equipment 380 on the fare component being validated.

Itinerary A: SIN-PAR-SIN RT Pricing Unit

Equip 380 Equip 320 Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Equip 380 Equip 380

Pricing: SIN-PAR fare component: Apply 100.00 for LON (based on SIN-LON matched sector) PAR-SIN fare component: Apply 100.00 for LON (based on PAR-LON and LON-SIN matched sectors)

Ticketing: SIN XX LON XX PAR Q SINPAR100.00M500.00 XX LON XX SIN Q PARSIN100.00M500.00NUC1200.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.101 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Itinerary B: SIN-PAR-SIN RT Pricing Unit

Equip 380 Equip 380 Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Equip 380 Equip 320

Pricing: SIN-PAR fare component: Apply 100.00 for LON (based on SIN-LON and LON-PAR matched sectors) PAR-SIN fare component: Apply 100.00 for LON (based on LON-SIN matched sector)

Ticketing: SIN XX LON XX PAR Q SINPAR100.00M500.00 XX LON XX SIN Q PARSIN100.00M500.00 NUC1200.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.102 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Itinerary C: SIN-PAR-SIN RT Pricing Unit

Equip 320 Equip 320 Equip 380 Cxr XX Cxr XX Cxr XX SIN BKK LON PAR

Cxr XX Cxr XX Equip 380 Equip 320

Pricing: SIN-PAR fare component: Apply 100.00 for LON (based on LON-PAR matched sector) PAR-SIN fare component: Apply 100.00 for LON (based on LON-SIN matched sector)

Ticketing: SIN XX BKK XX LON XX PAR Q BKKPAR100.00M500.00 XX LON XX SIN QPARSIN100.00M500.00 NUC1200.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.103 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Example 3 – From/To/Via Geo Spec Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank LON Blank Blank Q 3 100.00 NUC The data indicates that a surcharge of NUC 100.00 applies to each transfer (each intermediate ticketed point) in LON on the fare component being validated.

Itinerary: SIN-PAR-SIN RT Pricing Unit

Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX

Pricing: SIN-PAR fare component: Apply 100.00 for LON PAR-SIN fare component: Apply 100.00 for LON

Ticketing: SIN XX LON XX PAR Q SINPAR100.00M500.00 XX LON XX SIN Q PARSIN100.00M500.00 NUC1200.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.104 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Example 4 – From/To/Via Geo Spec with Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr 01Jan 31Jan Blank Blank Blank LON Blank Blank Q 3 100.00 NUC The data indicates that a surcharge of NUC 100.00 applies to each transfer (each intermediate ticketed point) departing from LON on 01Jan-31Jan on the fare component being validated.

Itinerary: SIN-PAR-SIN RT Pricing Unit

Dept 31Dec Dept 12Jan Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Dept 01Feb Dept 31Jan

Pricing: SIN-PAR fare component: Apply 100.00 for LON (based on LON-PAR matched sector) PAR-SIN fare component: No surcharge

Ticketing: SIN XX LON XX PAR Q SINPAR100.00M500.00 XX LON XX SIN M500.00NUC1100.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.105 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 3: Per Transfer Surcharges

Example 5 – Between/And Geo Spec (Portion) Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Sector/ Between And Surch Trvl Amt/ Date Date Flight Geo Spec Portion Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank P LON BKK F 3 100.00 NUC The data indicates that a fuel surcharge of NUC 100.00 applies to each transfer on a portion of travel between LON and BKK on the fare component being validated.

Itinerary: SIN-LON-SIN RT Pricing Unit

Cxr XX Cxr XX Cxr ZZ Cxr ZZ DXB PAR SIN BKK LON Cxr XX Cxr XX

Pricing: SIN-LON fare component: Apply 100.00 for DXB plus 100.00 for PAR LON-SIN fare component: No surcharge

Ticketing: SIN XX BKK XX DXB ZZ PAR ZZ LON Q BKKPAR100.00Q DXBLON100.00M500.00 XX BKK XX SIN M500.00 NUC1200.00

NOTE: The surcharge for the transfer applies to the consecutive sectors both into and out of the transfer.

Page E.03.12.106 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing

7.1.3 Travel Portion Value 4: “Per Ticket” Surcharge

When the Travel Portion is value 4, the surcharge amount is assessed once for the ticket (for the same carrier, surcharge type, travel portion, and geographic specification), provided processing matches the Category 12 data. (Refer to explanation earlier in this document regarding pricing/assessing “per ticket” surcharges.) The surcharge (Q) actually applies to all travel (all segments) on the ticket. Where and how the Q is placed is dependent upon whether the ticket consists of a single segment or multiple segments, as follows:

Single segment ticket: If the entire ticket consists of a single sector (segment),imprint “Q” followed by the amount immediately after the sector. Refer to JPSC 3.16.7.1.

Multi-segment ticket: If the entire ticket consists of multiple sectors (segments), imprint “Q” followed by the first and last cities of the ticket (journey origin and journey destination), in the direction of travel, and the amount. • When all travel on the ticket consists of a single fare component , this entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs. • When all travel on the ticket consists of multiple fare components, this entry shall be made at the end of the itinerary preceding the total amount in NUCs. Refer to JPSC 3.16.7.2.

Pending Page E.03.12.107 Revised February 2013

DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 4: Per Ticket Surcharges

Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank F 4 200.00 NUC The data indicates that a fuel surcharge of NUC 200.00 applies per ticket.

Itinerary A: NYC-LON-NYC RT Pricing Unit

Carrier XX FARE1 Cxr XX NYC LON Cxr ZZ Carrier ZZ FARE8

Pricing: NYC-LON fare component: Apply 100.00 per ticket (this is the highest, and only, per ticket surcharge for the same carrier and surcharge type) LON-NYC fare component: No surcharge

Ticketing: NYC XX LON M500.00ZZ NYC M500.00Q NYCNYC100.00NUC1100.00

Page E.03.12.108 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 4: Per Ticket Surcharges

Itinerary B: PAR-TYO-SYD-PAR CT Pricing Unit Carrier XX FARE2

Cxr XX Cxr BB PAR SIN TYO Cxr ZZ

DXB Carrier ZZ FARE8 Carrier XX FARE1 Cxr XX SYD Cxr XX

Pricing: PAR-TYO fare component: Apply 200.00 per ticket (this is the highest per ticket surcharge for the same carrier and surcharge type) TYO-SYD fare component: No surcharge SYD-PAR fare component: Apply 100.00 per ticket (eliminated since this is not the highest per ticket surcharge for the same carrier and surcharge type)

Ticketing: PAR XX SIN BB TYO M500.00 ZZ SYD M200.00 XX DXB XX PAR M500.00Q PARPAR200.00NUC1400.00

Page E.03.12.109 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 4: Per Ticket Surcharges

Example 2 – Equipment Carrier XX’s Category 12 Record 3 for FARE1 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E 4 100.00 NUC The data indicates that an equipment surcharge of NUC 100.00 applies per ticket when the fare component contains travel on equipment 380.

Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E 4 200.00 NUC The data indicates that an equipment surcharge of NUC 200.00 applies per ticket when the fare component contains travel on equipment 380.

Itinerary A: NYC-LON-NYC RT Pricing Unit

Carrier XX FARE1 Equip 380 Cxr XX NYC LON Cxr ZZ Equip 380 Carrier ZZ FARE8

Pricing: NYC-LON fare component: Apply 100.00 per ticket based on NYC-LON travel (this is the highest per ticket surcharge for the same carrier and surcharge type) LON-NYC fare component: No surcharge

Ticketing: NYC ZZ LON M500.00ZZ NYC M500.00Q NYCNYC100.00NUC1100.00

Page E.03.12.110 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 4: Per Ticket Surcharges

Itinerary B: PAR-TYO-SYD-PAR CT Pricing Unit Carrier XX FARE2

Equip 777 Equip 380 Cxr XX Cxr BB PAR SIN TYO Cxr ZZ

DXB Carrier ZZ FARE8 Carrier XX FARE1 Cxr XX Equip 777 SYD Cxr XX Equip 380

Pricing: PAR-TYO fare component: Apply 200.00 per ticket based on SIN-TYO travel (this is the highest per ticket surcharge for the same carrier and surcharge type) TYO-SYD fare component: No surcharge SYD-PAR fare component: Apply 100.00 per ticket based on SYD-DXB travel (eliminated since this is not the highest per ticket surcharge for the same carrier and surcharge type)

Ticketing: PAR XX SIN BB TYO M500.00 ZZ SYD M200.00 XX DXB XX PAR M500.00Q PARPAR200.00NUC1400.00

Page E.03.12.111 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing

7.1.4 Travel Portion Value 5: “Per Segment” Surcharge

When the Travel Portion is value 5, the surcharge amount is assessed once per each matched segment (coupon). The surcharge (Q) applies to the matched coupon (the coupon matched against the Category 12 data). Processing will place the Q as follows:

Imprint “Q” followed by the amount immediately after the matched sector (segment) to which it applies. Refer to JPSC 3.16.7.1

Pending Page E.03.12.112 Revised February 2013

DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 1 – Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr 01Jan 31Jan Blank Blank Blank Blank Blank Blank J 5 100.00 NUC The data indicates that a seasonal surcharge of USD 100.00 applies to each segment (each sector) on the fare component being validated where the departure from the origin point of the sector commences on 01Jan through 31Jan of any year

Itinerary A: MNL-TYO-MNL RT Pricing Unit

Dept 02Jan 11 Dept 03Jan 11 Cxr XX Cxr XX SEL MNL TYO Cxr XX Dept 30Jan 2011

Pricing: MNL-TYO fare component: Apply 100.00 for MNL-SEL and 100.00 for SEL-TYO TYO-MNL fare component: Apply 100.00 for TYO-MNL

Ticketing: MNL XX SEL Q100.00XX TYO Q100.00M500.00 XX MNL Q100.00M500.00NUC1300.00

Itinerary B: MNL-TYO OW Pricing Unit

Dept 30Dec 10 Dept 03Jan 11 Cxr XX Cxr XX MNL SEL TYO

Pricing: MNL-TYO fare component: Apply 100.00 for SEL-TYO

Ticketing: MNL XX SEL XX TYO Q100.00M500.00NUC600.00

Page E.03.12.113 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 2 – Equipment Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E 5 100.00 NUC The data indicates that an equipment surcharge of NUC 100.00 applies to each segment (each sector) on equipment 380 on the fare component being validated

Itinerary: SIN-PAR-SIN RT Pricing Unit

Equip 380 Equip 320 Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Equip 380 Equip 380

Pricing: SIN-PAR fare component: Apply 100.00 for SIN-LON PAR-SIN fare component: Apply 100.00 for PAR-LON and 100.00 for LON-SIN

Ticketing: SIN XX LON Q100.00XX PAR M500.00 XX LON Q100.00XX SIN Q100.00M500.00NUC1300.00

Page E.03.12.114 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 3 – RBD Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank R Blank Blank Blank Blank Z 5 100.00 NUC The data indicates that an RBD surcharge of NUC 100.00 applies to each segment (each sector) on RBD R on the fare component being validated

Itinerary: SIN-PAR-SIN RT Pricing Unit

RBD R RBD Q Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX RBD R RBD R

Pricing: SIN-PAR fare component: Apply 100.00 for SIN-LON PAR-SIN fare component: Apply 100.00 for PAR-LON and 100.00 for LON-SIN

Ticketing: SIN XX LON Q100.00XX PAR M500.00 XX LON Q100.00XX SIN Q100.00M500.00NUC1300.00

Page E.03.12.115 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 4 – From/To/Via Geo Spec Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank LON Blank Blank Q 5 100.00 NUC The data indicates that a surcharge of NUC 100.00 applies to each segment (each sector) from/to/via LON on the fare component being validated

Itinerary A: SIN-PAR-SIN RT Pricing Unit

Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX

Pricing: SIN-PAR fare component: Apply 100.00 for SIN-LON and 100.00 for LON-PAR PAR-SIN fare component: Apply 100.00 for PAR-LON and 100.00 for LON-SIN

Ticketing: SIN XX LON Q100.00XX PAR Q100.00M500.00 XX LON Q100.00XX SIN Q100.00M500.00NUC1400.00

Itinerary B: SIN-LON-SIN RT Pricing Unit

Cxr XX Cxr XX SIN DXB LON Cxr XX Cxr XX

Pricing: SIN-LON fare component: Apply 100.00 for DXB-LON LON-SIN fare component: Apply 100.00 for LON-DXB

Ticketing: SIN XX DXB XX LON Q100.00M500.00 XX DXB Q100.00XX SIN M500.00NUC1200.00

Page E.03.12.116 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 5 – From/To/Via Geo Spec with Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr 01Jan 31Jan Blank Blank Blank LON Blank Blank Q 5 100.00 NUC The data indicates that a surcharge of NUC 100.00 applies to each segment (each sector) commencing from LON on 01Jan-31Jan on the fare component being validated

Itinerary: SIN-PAR-SIN RT Pricing Unit

Dept 31Dec Dept 12Jan Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Dept 01Feb Dept 31Jan

Pricing: SIN-PAR fare component: Apply 100.00 for LON-PAR PAR-SIN fare component: No surcharge

Ticketing: SIN XX LON XX PAR Q100.00M500.00 XX LON XX SIN M500.00NUC1100.00

Page E.03.12.117 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 6 – From/To/Via Geo Spec with Equipment Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank LON Blank Blank Q 5 100.00 NUC The data indicates that a surcharge of NUC 100.00 applies to each segment (each sector) from/to/via LON on equipment 380 on the fare component being validated

Itinerary: SIN-PAR-SIN RT Pricing Unit

Equip 380 Equip 320 Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Equip 380 Equip 380

Pricing: SIN-PAR fare component: Apply 100.00 for SIN-LON PAR-SIN fare component: Apply 100.00 for PAR-LON and 100.00 for LON-SIN

Ticketing: SIN XX LON Q100.00XX PAR M500.00 XX LON Q100.00XX SIN Q100.00M500.00NUC1300.00

Page E.03.12.118 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 7 – Between/And Geo Spec (Sector) Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Sector/ Between And Surch Trvl Amt/ Date Date Flight Geo Spec Portion Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank S PAR LON F 5 100.00 NUC The data indicates that a fuel surcharge of NUC 100.00 applies to each segment (each sector) between PAR and LON on the fare component being validated

Itinerary A: SIN-PAR-SIN RT Pricing Unit

Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX

Pricing: SIN-PAR fare component: Apply 100.00 for LON-PAR PAR-SIN fare component: Apply 100.00 for PAR-LON

Ticketing: SIN XX LON XX PAR Q100.00M500.00 XX LON Q100.00XX SIN M500.00NUC1200.00

Itinerary B: SIN-PAR-SIN RT Pricing Unit

Cxr XX Cxr ZZ FRA SIN PAR Cxr XX Cxr XX LON

Pricing: SIN-PAR fare component: No surcharge PAR-SIN fare component: Apply 100.00 for PAR-LON

Ticketing: SIN XX FRA ZZ PAR M500.00 XX LON Q100.00XX SIN M500.00NUC1100.00

Page E.03.12.119 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 8 – Between/And Geo Spec (Portion) Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Sector/ Between And Surch Trvl Amt/ Date Date Flight Geo Spec Portion Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank P LON BKK F 5 100.00 NUC The data indicates that a fuel surcharge of NUC 100.00 applies to each segment on a portion of travel between LON and BKK on the fare component being validated

Itinerary: SIN-LON-SIN RT Pricing Unit

Cxr XX Cxr XX Cxr ZZ PAR SIN BKK LON Cxr XX Cxr XX

Pricing: SIN-LON fare component: Apply 100.00 for BKK-PAR and 100.00 for PAR-LON LON-SIN fare component: Apply 100.00 for LON-BKK

Ticketing: SIN XX BKK XX PAR Q100.00ZZ LON Q100.00M500.00 XX BKK Q100.00XX SIN M500.00NUC1300.00

Page E.03.12.120 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 9 – Between/And Geo Spec (Portion) with Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Sector/ Between And Surch Trvl Amt/ Date Date Flight Geo Spec Portion Geo Spec Geo Spec Type Prt Curr 01Jan 31Jan Blank Blank Blank Blank P LON BKK Q 5 100.00 NUC The data indicates that a surcharge of NUC 100.00 applies to each segment departing 01Jan-31Jan on a portion of travel between LON and BKK on the fare component being validated

Itinerary: SIN-LON-SIN RT Pricing Unit

Dept 31Dec Dept 31Dec Dept 02Jan Cxr XX Cxr XX Cxr ZZ PAR SIN BKK LON Cxr XX ROM Cxr XX Dept 16Jan Dept 15Jan Dept 15Jan

Pricing: SIN-LON fare component: Apply 100.00 for PAR-LON LON-SIN fare component: Apply 100.00 for LON-BKK

Ticketing: SIN XX BKK XX PAR ZZ LON Q100.00M500.00 XX BKK Q100.00XX SIN M500.00NUC1200.00

Page E.03.12.121 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 5: Per Coupon Surcharges

Example 10 – Between/And Geo Spec (Portion) with RBD Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Sector/ Between And Surch Trvl Amt/ Date Date Flight Geo Spec Portion Geo Spec Geo Spec Type Prt Curr Blank Blank Blank R Blank Blank P LON BKK Z 5 100.00 NUC The data indicates that an RBD surcharge of NUC 100.00 applies to each segment in RBD R on a portion of travel between LON and BKK on the fare component being validated

Itinerary: SIN-LON-SIN RT Pricing Unit

RBD R RBD F RBD R Cxr XX Cxr XX Cxr ZZ PAR SIN BKK LON Cxr XX Cxr XX RBD F RBD F

Pricing: SIN-LON fare component: Apply 100.00 for PAR-LON LON-SIN fare component: No surcharge

Ticketing: SIN XX BKK XX PAR ZZ LON Q100.00M500.00 XX BKK XX SIN M500.00NUC1100.00

Page E.03.12.122 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing

7.1.5 Travel Portion Value 6: “Per Direction” Surcharge

When the Travel Portion is value 6, the surcharge amount is assessed once for the outbound/inbound direction of travel on the ticket (for the same carrier, surcharge type, travel portion, and geographic specification), provided processing matches the Category 12 data. (Refer to explanation earlier in this document regarding pricing/assessing “per direction” surcharges.).

Processing must take the following steps: 1. Identify all fare components in the direction of travel (outbound or inbound) on the journey.

2. For each direction (outbound or inbound), identify the fare components that match applicable Category 12 “per direction” data (for the same carrier, surcharge type, travel portion value 6, and geographic specification) that are being compared to determine the highest surcharge.

a. If there is only one matched fare component, then the surcharge (Q), applies to all travel on the fare component, as follows:

Single segment: If the fare component consists of a single sector (segment), imprint “Q” followed by the amount immediately after the sector. Refer to JPSC 3.16.7.1.

Multiple segments: If the fare component consists of multiple sectors (segments), imprint “Q” followed by the first and last cities of the fare component, in the direction of travel, and the amount. This entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs. Refer to JPSC 3.16.7.2.

b. If there are multiple matched fare components and the fare components are consecutive, then the surcharge (Q) applies to all travel on these fare components, as follows:

Imprint “Q” followed by the origin city of the first fare component and the destination city of the last fare component, in the direction of travel, and the amount. This entry shall be made at the end of the itinerary preceding the total amount in NUCs. Refer to JPSC 3.16.7.2.

Pending Page E.03.12.123 Revised February 2013

DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 6: Per Direction Surcharges

c. If there are multiple matched fare components and the fare components are not consecutive, then determine the fare component that resolves to the Category 12 data with the highest surcharge (this is referred to as the “applicable” fare component. The surcharge (Q) actually applies to the “matched travel” [defined as the travel that is matched against the qualifying criteria (match data) in Category 12], on the “applicable” fare component (the fare component whose Category 12 surcharge amount is applied). The Q placement is dependent upon whether the “matched travel” is a single segment or multiple consecutive or non-consecutive segments on the “applicable” fare component, as follows:

Single segment: The surcharge applies to the single matched segment (sector). Imprint “Q” followed by the amount immediately after the matched sector to which it applies. Refer to JPSC 3.16.7.1.

Consecutive segments: The surcharge applies to the multiple consecutive matched segments (sectors) within the fare component. Imprint “Q” followed by the first and last cities of the consecutive sectors to which the surcharge applies, in the direction of travel, and the amount. This entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs. Refer to JPSC 3.16.7.2.

Non-consecutive segments: The surcharges applies to the travel encompassing the matched non-consecutive segments (sectors) within the fare component. Imprint “Q” followed by the first and last cities of the non-consecutive sectors to which the surcharge applies, in the direction of travel, and the amount. This entry shall be made at the end of the fare component to which the surcharge applies, preceding the fare component amount in NUCs. Refer to JPSC 3.16.7.2.

Page E.03.12.124 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 6: Per Direction Surcharges

Example 1 – No specific match criteria Carrier XX’s Category 12 Record 3 for FARE1 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank F 6 300.00 NUC The data indicates that a fuel surcharge of NUC 300.00 applies per direction. Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank F 6 200.00 NUC The data indicates that a fuel surcharge of NUC 200.00 applies per direction .

Itinerary: SIN-PAR-SIN RT pricing unit on FARE1 End-on-End with PAR-NYC-PAR RT pricing unit on FARE2 Carrier XX FARE1 Carrier XX FARE2 SIN LON PAR NYC Carrier XX FARE1 Carrier XX FARE2

Pricing: Outbound fare components: SIN-PAR fare component: Apply 300.00 per direction (this is the highest per direction surcharge for the same carrier and surcharge type) PAR-NYC fare component: Apply 200.00 per direction Inbound fare components: NYC-PAR fare component: Apply 200.00 per direction PAR-SIN fare component: Apply 300.00 per direction (this is the highest per direction surcharge for the same carrier and surcharge type)

Ticketing: SIN XX LON XX PAR M1000.00XX NYC M500.00 XX PAR M500.00XX LON XX SIN M1000.00 Q SINNYC300.00Q NYCSIN300.00NUC3600.00

Page E.03.12.125 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 6: Per Direction Surcharges

Example 2 – Equipment Carrier XX’s Category 12 Record 3 for FARE1 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E 6 300.00 NUC The data indicates that an equipment surcharge of NUC 300.00 applies per direction when the fare component contains travel on equipment 380.

Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 380 Blank Blank Blank Blank Blank E 6 200.00 NUC The data indicates that an equipment surcharge of NUC 200.00 applies per direction when the fare component contains travel on equipment 380.

Itinerary A: SIN-PAR-SIN RT pricing unit on FARE1 End-on-End with PAR-NYC-PAR RT pricing unit on FARE2 Carrier XX FARE1 Carrier XX FARE2 Equip 380 Equip 320 Equip 380 SIN LON PAR NYC Equip 380 Equip 320 Equip 380 Carrier XX FARE1 Carrier XX FARE2

Pricing: Outbound fare components: SIN-PAR fare component: Apply 300.00 per direction – match based on SIN-LON sector (this is the highest per direction surcharge for the same carrier and surcharge type) PAR-NYC fare component: Apply 200.00 per direction

Inbound fare components: NYC-PAR fare component: Apply 200.00 per direction PAR-SIN fare component: Apply 300.00 per direction – match based on LON-SIN sector (this is the highest per direction surcharge for the same carrier and surcharge type)

Page E.03.12.126 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 6: Per Direction Surcharges

Surcharge applies to multiple consecutive fare components:

Ticketing: SIN XX LON XX PAR M1000.00XX NYC M500.00 XX PAR M500.00XX LON XX SIN M1000.00 Q SINNYC300.00Q NYCSIN300.00NUC3600.00

Page E.03.12.127 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 6: Per Direction Surcharges

Itinerary B: SIN-PAR-SIN OW pricing unit on FARE1 End-on-End with PAR-NYC OW pricing unit on FARE2 Carrier XX FARE1 Carrier XX FARE2 Equip 380 Equip 320 Equip 777 SIN LON PAR NYC

Surcharge applies to a single fare component (SIN-PAR):

Ticketing: SIN XX LON XX PAR Q SINPAR300.00M1000.00XX NYC M500.00NUC1800.00

Page E.03.12.128 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing – Travel Portion Value 6: Per Direction Surcharges

Itinerary C: SIN-LON OW PU on FARE1 EoE with LON-PAR OW PU on FAR25 EoE with PAR-NYC OW PU on FARE2 Carrier XX FARE1 Carrier ZZ FAR25 Carrier XX FARE2 Equip 380 Equip 320 Equip 380 SIN LON PAR NYC

Pricing: Outbound fare components: SIN-LON fare component: Apply 300.00 per direction – match based on SIN-LON sector (this is the highest per direction surcharge for the same carrier and surcharge type) LON-PAR fare component: No surcharge PAR-NYC fare component: Apply 200.00 per direction

Surcharge applies to multiple non-consecutive fare components (SIN-LON and PAR-NYC, but SIN-LON is the matched travel and applicable fare component):

Ticketing: SIN XX LON Q300.00M500.00 ZZ PAR M200.00XX NYC M500.00NUC1500.00

Page E.03.12.129 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

7.2 Reductions (Negative Surcharges)

Reductions are charges expressed in Category 12 as an amount that is subtracted from the fare (based on Appl byte 71 value A, B, C, D, or E). The pricing application relative to qualifying criteria and surcharge application is the same as the application for positive surcharges. However, the ticketing application differs due to the fact that the current ticketing resolutions do not specifically address reductions (negative surcharges).1 Therefore, industry working groups agreed that Joint Passenger Services Conference Resolution 3.16.12.2 applies for reductions (negative surcharges). This resolution directs processing to imprint LESS followed by the amount. This entry shall be made at the end of the itinerary preceding the total amount in NUCs. This ticketing application applies regardless of the Category 12 Travel Portion value and qualifying criteria

NOTE: Using LESS as the ticketing solution does not permit the Q to be shown in the fare calculation with the travel to which is applies. The surcharge cannot be ticketed in a manner that reflects the pricing application.

1 Changes to Ticketing Resolutions were proposed at the Joint Passenger Service Conferences (JPSC), but were ultimately defeated.

Page E.03.12.130 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 1 – Travel Portion value Blank (per fare component) with no specific match criteria Category 12 Record 3 Start Stop Equip Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank 777 Blank Blank Blank Blank E Blank A - 100.00 NUC The data indicates that an equipment reduction of NUC 100.00 will be subtracted from the fare when the fare component contains travel on equipment 777.

Itinerary A: SIN-PAR-SIN RT Pricing Unit

Equip 777 Equip 320 Cxr XX Cxr XX SIN LON PAR Cxr XX Cxr XX Equip 380 Equip 380

Pricing: SIN-PAR fare component: Subtract 100.00 from the fare for SIN-LON PAR-SIN fare component: No reduction

Ticketing: SIN XX LON XX PAR M500.00 XX LON XX SIN M500.00LESS 100.00NUC900.00

Page E.03.12.131 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Itinerary B: SIN-PAR-SIN RT Pricing Unit – different fare owning carriers

Equip 777 Equip 320 Cxr XX Cxr XX SIN LON PAR Cxr ZZ Cxr ZZ Equip 380 Equip 380

Pricing: SIN-PAR fare component: Subtract 100.00 from the fare for SIN-LON PAR-SIN fare component: No reduction

Ticketing: SIN XX LON XX PAR M500.00 ZZ LON ZZ SIN M500.00LESS 100.00NUC900.00

NOTE: The resulting fare calculation is the same for the LESS value regardless of the fare owning carrier.

Page E.03.12.132 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 2 – Travel Portion value Blank (per fare component) Start/Stop Dates Category 12 Record 3 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr 01 Jan 31 Jan Blank Blank Blank Blank Blank Blank J Blank A -100.00 NUC The data indicates that a seasonal reduction of USD 100.00 will be subtracted from the fare when the departure from the origin of the fare component commences on 01Jan through 31Jan of any year

Itinerary A: MNL-TYO-MNL RT Pricing Unit

Dept 02Jan 11 Dept 03Jan 11 Cxr XX Cxr XX SEL MNL TYO Cxr ZZ Dept 30Jan 2011

Pricing: MNL-TYO fare component: Subtract 100.00 from the fare TYO-MNL fare component: Subtract 100.00 from the fare

Ticketing: MNL XX SEL XX TYO M500.00 ZZ MNL M500.00LESS100.00LESS100.00NUC800.00

Page E.03.12.133 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Itinerary B: MNL-TYO-MNL RT Pricing Unit

Dept 19Dec 10 Dept 29Dec 10 Cxr XX Cxr XX SEL MNL TYO Cxr ZZ Dept 15Jan 2011

Pricing: MNL-TYO fare component: No reduction TYO-MNL fare component: Subtract 100.00 from the fare

Ticketing: MNL XX SEL XX TYO M500.00 ZZ MNL M500.00LESS100.00NUC900.00

Page E.03.12.134 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 3 – Travel Portion value 3 (per transfer) Category 12 Record 3 Start Stop Equip Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Type Prt Curr Spec Blank Blank Blank Blank SIN Blank Blank Q 3 A - 50.00 NUC The data indicates that a reduction of NUC 50.00 will be subtracted from the fare for each transfer (each intermediate ticketed point) in SIN on the fare component being validated.

Itinerary: KUL-JKT-KUL RT Pricing Unit

Cxr XX Cxr XX KUL SIN JKT Cxr XX Cxr XX

Pricing: KUL-JKT fare component: Subtract 50.00 from the fare for SIN JKT-KUL fare component: No reduction

Ticketing: KUL XX SIN XX JKT M500.00 XX SIN XX KUL M500.00LESS50.00NUC950.00

Page E.03.12.135 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 4 – Travel Portion value 4 (per ticket) Carrier XX’s Category 12 Record 3 for FARE1 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank Q 4 A -100.00 NUC The data indicates that a reduction of NUC 100.00 applies per ticket.

Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank Q 4 A -200.00 NUC The data indicates that a reduction of NUC 200.00 applies per ticket.

Itinerary: NYC-LON-NYC RT Pricing Unit

Carrier XX FARE1 Cxr XX NYC LON Cxr XX Carrier XX FARE8

Pricing: NYC-LON fare component: Subtract 100.00 per ticket (this is the highest per ticket surcharge amount for the same carrier and surcharge type) LON-NYC fare component: No reduction (the -200.00 amount is a lower amount than -100.00)

Ticketing: NYC XX LON M500.00XX NYC M500.00LESS100.00NUC900.00

Page E.03.12.136 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 5 – Travel Portion value 4 (per ticket) – Mix of Negative and Positive Amounts Carrier XX’s Category 12 Record 3 for FARE1 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank Q 4 A -100.00 NUC The data indicates that a reduction of NUC 100.00 applies per ticket.

Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank Q 4 Blank +200.00 NUC The data indicates that a surcharge of NUC 200.00 applies per ticket.

Itinerary: NYC-LON-NYC RT Pricing Unit

Carrier XX FARE1 Cxr XX NYC LON Cxr XX Carrier XX FARE2

Pricing: NYC-LON fare component: No surcharge. (The 200.00 surcharge is a higher amount than the 100.00 reduction.) LON-NYC fare component: Apply 200.00 surcharge per ticket (this is the highest per ticket surcharge amount for the same carrier and surcharge type )

Ticketing: NYC XX LON M500.00XX NYC M500.00Q NYCNYC200.00NUC1200.00

Page E.03.12.137 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 6 – Travel Portion value 5 (per coupon) Category 12 Record 3 Start Stop Equip Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Type Prt Curr Spec Blank Blank PRO Blank Blank Blank Blank E 5 A - 50.00 NUC The data indicates that an equipment surcharge of NUC 50.00 will be subtracted from for each coupon on the fare component that contains travel on propeller equipment.

Itinerary A: KUL-JKT-KUL RT Pricing Unit – single and consecutive sectors

Equip PRO Equip PRO Cxr XX Cxr XX KUL SIN JKT Cxr XX Cxr XX Equip PRO Equip 777

Pricing: KUL-JKT fare component: Subtract 50.00 from the fare for KUL-SIN plus subtract 50.00 from the fare for SIN-JKT JKT-KUL fare component: Subtract 50.00 from the fare for SIN-KUL

Ticketing: KUL XX SIN XX JKT M500.00 XX SIN XX KUL M500.00LESS50.00LESS50.00LESS50.00NUC850.00

Page E.03.12.138 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Itinerary B: KUL-JKT-KUL RT Pricing Unit – different fare owning carriers

Equip PRO Equip PRO Cxr XX Cxr XX KUL SIN JKT Cxr ZZ Cxr ZZ Equip PRO Equip 777

Pricing: KUL-JKT fare component: Subtract 50.00 from the fare for KUL-SIN plus subtract 50.00 from the fare for SIN-JKT JKT-KUL fare component: Subtract 50.00 from the fare for SIN-KUL

Ticketing: KUL XX SIN XX JKT M500.00 ZZ SIN ZZ KUL M500.00 LESS50.00LESS50.00LESS50.00NUC850.00

NOTE: The resulting fare calculation is the same for the LESS value regardless of the fare owning carrier.

Page E.03.12.139 Revised February 2013 DATA APPLICATION FOR CATEGORY 12 – SURCHARGES

Ticketing - Reductions

Example 7 – Travel Portion value 6 (per direction) Carrier XX’s Category 12 Record 3 for FARE1 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank Q 6 A -300.00 NUC The data indicates that a reduction of NUC 300.00 applies per direction. Carrier XX’s Category 12 Record 3 for FARE2 Start Stop Equip RBD Carrier/ From/To/Via Between And Surch Trvl Appl Amt/ Date Date Flight Geo Spec Geo Spec Geo Spec Type Prt Curr Blank Blank Blank Blank Blank Blank Blank Blank Q 6 A -200.00 NUC The data indicates that a reduction of NUC 200.00 applies per direction.

Itinerary: SIN-PAR-SIN RT pricing unit on FARE1 End-on-End with PAR-NYC-PAR RT pricing unit on FARE2 Carrier XX FARE1 Carrier XX FARE2 SIN LON PAR NYC Carrier XX FARE1 Carrier XX FARE2

Pricing: Outbound fare components: SIN-PAR fare component: No reduction. (The -200.00 amount is higher than -300.00) PAR-NYC fare component: Subtract 200.00 per direction (this is the highest per direction surcharge for the same carrier and surcharge type) Inbound fare components: NYC-PAR fare component: Subtract 200.00 per direction (this is the highest per direction surcharge for the same carrier and surcharge type) PAR-SIN fare component: No reduction. (The -200.00 amount is higher than -300.00)

Ticketing: SIN XX LON XX PAR M1000.00XX NYC M500.00 XX PAR M500.00XX LON XX SIN M1000.00LESS200.00LESS200.00NUC2600.00

Page E.03.12.140 Revised February 2013