Baggage

 

Step 1: Determine the Baggage Trips (BT)

The Baggage Trip is created from origin to first stopover point (BT1); next Baggage Trip (BT2) is created from arrival of BT1 to next stopover point; process continues until end of itinerary is reached.

 

Step 2: Determine Most Significant Carrier (MSC) for each Baggage Trip (BT)

For wholly domestic itineraries, the Most Significant Carrier for each Baggage Trip will be the first marketing carrier on the checked portion.

For journeys within Canada and USA, when determining whose rules apply, use the rules of the first marketing carrier on the journey.

 

Step 1: Establish the furthest point of travel

The furthest checked point is the furthest point by mileage/TPM from the journey origin that meets the definition of a checked point.

 

Step 2: Is the origin, destination or furthest checked point in USA and/or Canada?

• YES – US DOT mandate applies for USA and CTA mandate applies for Canada

• NO – IATA Resolution 302 applies when determining the Baggage Trips and whose baggage rule applies (MSC)

 

Step 3: Identify Baggage Trip (BT) and Most Significant Carrier (MSC)

DOT/CTA RESERVATION (Baggage rules for origin, destination or furthest point in USA/Canada)

Only 2 Baggage Trips are created

• Outbound Baggage Trip: from origin to furthest checked point

• Inbound Baggage Trip: furthest checked point to destination

The marketing carrier defines the Most Significant Carrier on a Baggage Trip.

ATPCO maintains a list of US DOT respectively CTA carriers that file general rule tariffs applicable for travel to/from the United States and Canada. These lists should be used by subscribers of ATPCO’s Baggage product for determining baggage selection rules for travel to/from the United States.

Carriers must use the first marketing carrier’s baggage rules for the entire journey, provided the first marketing carrier is specified in the DOT’s, respectively CTA’s published list of DOT/CTA carriers.

If the first marketing carrier is not specified in DOT’s respectively CTA’s published list of carriers for journeys to/from USA or Canada, then use the rules of the next consecutive marketing carrier on the journey and continue until processing finds the next “first” marketing carrier who is specified in DOT/CTA’s list of carriers. Once the first marketing carrier is identified, their baggage rules apply to the entire journey.

IATA RESOLUTION 302 (Baggage rules for origin, destination or furthest point not in US/CA)

The number of Baggage Trips (BTs) varies by the number of stopovers taken.

• First BT: from origin to first stopover

• Next BT: from arrival point of previous BT to next stopover

• Continues until last point of itinerary is reached

The marketing carrier defines the Most Significant Carrier on each Baggage Trip. In accordance with the IATA Resolution 302, the Most Significant Carrier is:

• the carrier performing carriage on the first sector that crosses from one area to another (travel between two or more IATA Areas) Exception: IATA Area 1/2/3 only, the carrier providing carriage on the first sector that crosses between IATA Area 1 and IATA Area 2.

• the carrier performing carriage on the first sector that crosses from one sub-area to another (travel between IATA Tariff sub-areas).

• the carrier performing carriage on the first international sector (travel within a IATA Tariff sub-area).

• the first carrier on the checked portion (travel within a single country).

In the below scenario, the system is processing the baggage allowance and charges by using US DOT mandate. The system is creating two baggage trips from the point of origin (BUD) to the furthest point (LAX) outbound and inbound. The free baggage allowance for BAG 1 as well an applicable baggage charges for BAG 2 are assessed only once per baggage trip and shown in the pricing response as follows.

1. YY 8454 K 06SEP BUDCDG AK1 <<<<CDG = connection

2. YY 8395 K 06SEP CDGLAX AK1 <<<<LAX = furthest point

3. YY 1500 V 11SEP LAXDFW AK1 <<<<DFW = stopover

4. YY 1954 L 16SEP DFWATL AK1 <<<<ATL = connection

5. YY 2173 L 16SEP ATLMIA AK1 <<<<MIA = stopover

6. YY 8345 L 22SEP MIACDG AK1 <<<<PAR = connection

7. YY 8638 L 23SEP CDGBUD AK1 <<< arrival

BAGGAGE ALLOWANCE

ADT

(outbound baggage trip BUD-LAX)

=checked portion=

DL BUDLAX 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 22000 HUF UPTO50LB/23KG AND UPTO62LI/158LCM <<<<Charges are applicable per Baggage trip to furthest point

 

(inbound baggage trip LAX-BUD)

=checked portion=

YY LAXDFW 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 22000 HUF UPTO50LB/23KG AND UPTO62LI/158LCM <<<<Charges are applicable per Baggage trip to furthest point

 

=checked portion=

YY DFWMIA 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 0.0 HUF UPTO50LB/23KG AND UPTO62LI/158LCM

 

=checked portion=

YY MIABUD 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 0.0 HUF UPTO50LB/23KG AND UPTO62LI/158LCM

 

The baggage charges for Bag 2 are applied only once per baggage trip hence on the inbound baggage trip the charges are not shown with all intermediate stopovers within the baggage trip. The above display indicates that the fee should not be charged again on the last two checked potions (DFWMIA; MIABUD) if these were already charged on the first checked potion LAXDFW.

In the below scenario, the system is also processing the baggage allowance and charges by using US DOT mandate, creating one Baggage trip from the point of origin (EWR) to the furthest point (BRU). The free baggage allowance for BAG 1 is assessed only once per baggage trip in the journey, but the applicable baggage charges for BAG 2 are assessed per each checked portion and shown as follows.

 

BAGGAGE ALLOWANCE

ADT

(one baggage trip EWRBRU)

=checked portion=

YY EWRYHZ 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 100.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM

 

=checked portion=

YY YWGBRU 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 100.00 USD UPTO50LB/23KG AND UPTO62LI/158LCM

 

If there is no applicable baggage data filed by the airline within ATPCO, the system response is BAGGAGE CHARGES DATA NOT AVAILABLE which indicates the baggage details are unknown.

Only free baggage allowance is considered within the scope of the Travelport Fare Guarantee Policy.

This refers to the Free Baggage Allowance included in the ticket record/filed fare, which is considered within scope of the Fare Guarantee Policy.

INFO text relating to 1st and 2nd baggage allowances is not within scope of the Fare Guarantee Policy. The text is presented as INFO only.

As opposed to free baggage allowance, the carry-on allowance is processed for the operating carrier on each sector of the ticket.

If there is no applicable carry-on data filed by the airline within ATPCO, the system response is CARRY ON ALLOWANCE DATA NOT AVAILABLE which indicates the carry-on baggage allowance is unknown.

The baggage information returned when requesting ancillary services (DAS*) may be the discounted price for that same excess baggage when the passenger purchases it in advance. Users can sell the service from ancillary catalogue display.

Airlines may have different baggage policies depending on the moment the service is purchased. Therefore, sometimes the amounts displayed in the pricing response may not be the same with the ones displayed in the ancillary (DAS) catalogue.

Please refer to the below example where a 70.00EUR fee is applicable if the first additional bag is purchased at the airport and 45.000EUR fee is applicable if the service is purchased in advance before departure.

 

BAGGAGE ALLOWANCE

ADT

AF VCEPAR 1PC

BAG 1 - NO FEE UPTO50LB/23KG AND UPTO62LI/158LCM

BAG 2 - 70.00 EUR UPTO50LB/23KG AND UPTO62LI/158LCM

 

ADDITIONAL SVC FOR DETAIL >DAS*L·

LN VEN DESCRIPTION PTC AMNT CUR SEG F

1 AF 1ST ADDITIONAL BAG ADT 45.00 EUR 01

 

Airlines may also have different Advance Purchase – Reservations / Ticketing restrictions filed, hence the applicable baggage charges displayed may vary based on the time the request is made.

Functional entries - DAS* as opposed to /DAS* or /DASO used with fare quote entries?

Current system response to DAS* requests are generic info for generic sequences which have no specific fare validation requirements. A warning massage is also being displayed on the top advising to request additional services at the pricing time:

 

>DAS*

*SVCS REQUIRING FARE DATA MAY EXIST - REQ SVCS AT PRICING TIME*

In case the carrier has filed a fare class or exception for specific fare basis, the system needs to validate the fare to assess correct price for the ancillary services. It is recommended to always use /DAS* or /DASO options with the pricing entry for validated fare ancillary services.

In the below example the carrier has filed a fare class exception with amount of EUR15.00 for the 1st Additional Bag. Since the entry DAS* does not validate the fare used it returns the generic amount of EUR45.00. When fare validation is made by using the DAS* modifier in the pricing entry the amount of EUR15.00 is offered instead.

 

>DAS*

*SVCS REQUIRING FARE DATA MAY EXIST - REQ SVCS AT PRICING TIME*

ADDITIONAL SVC FOR DETAIL >DAS*L·

LN VEN DESCRIPTION PTC AMNT CUR SEG F

1 AF 1ST ADDITIONAL BAG ADT 45.00 EUR 01

2 AF 2ND ADDITIONAL BAG ADT 45.00 EUR 01

 

>FQ/DASO

ADDITIONAL SVC FOR DETAIL >DAS*L·

LN VEN DESCRIPTION PTC AMNT CUR SEG F

1 AF 1ST ADDITIONAL BAG ADT 15.00 EUR 01

2 AF 2ND ADDITIONAL BAG ADT 45.00 EUR 01

 

/DAS* or /DASO modifies should be used along with the fare entry validating the ticketed fare basis.

 

You may use FQ/DAS* to display validated ancillary services along with the pricing details or FQ/DASO to display validated ancillary services without the pricing details.

FQ/DAS* or FQ/DASO These entries are validating ancillary services for private/public fares (whichever is lower)

FQ:N/DAS* or FQ:N/DASO These entries are validating ancillary services for the lowest public fare

FQ.TDDMMMYY/DAS* or FQ.TDDMMMYY/DASO In case the ancillary services are requested, at a later date after the ticket has been issued and the applicable fare is no longer returned with current pricing date (e.g. no longer within the advance purchase, etc.), you may need to use historical pricing option to accordingly validate the pricing at the time of ancillary service request.

 

If FQ returns NO VALID FARE FOR INPUT CRITERIA, FQ/DASO will subsequently return SYSTEM ERROR DURING ADDITIONAL SERVICES INPUT since the system is unable to validate the fare to request ancillary services.

>FQ

NO VALID FARE FOR INPUT CRITERIA

>FQ/DASO

SYSTEM ERROR DURING ADDITIONAL SERVICES INPUT