Last edit by: seawolf
AA Passenger Protection for Itineraries Using Separate AA / oneworld Tickets in SAME PNR
(applies to AA, not other oneworld carriers' policies)
(applies to AA, not other oneworld carriers' policies)
American Airlines policy: Changes to itineraries for passengers holding separate tickets in the SAME PNR:
COLOR]
. . . Link for a printable PDF; (see "oneworld Reaccommodations: Separate Tickets" within).
NOTE: as oneworld have changed their policy to not require through-checking and misconnect protection of member airlines as of 1 Jun 2016 (AY, BA, QF, QR have already changed their policies and no longer offer these prior alliance passenger services), be aware AA could potentially change their policies at any time if they choose to.
COLOR]
. . . Link for a printable PDF; (see "oneworld Reaccommodations: Separate Tickets" within).
NOTE: as oneworld have changed their policy to not require through-checking and misconnect protection of member airlines as of 1 Jun 2016 (AY, BA, QF, QR have already changed their policies and no longer offer these prior alliance passenger services), be aware AA could potentially change their policies at any time if they choose to.
AA to/from Non-oneworld® Carrier in the Same or Separate PNRs
Schedule Irregularity procedures and AA Conditions of Carriage do not apply to separate tickets purchased by the customer as part of their journey. Example: customer holds a ticket from ABQ-ORD-ABQ on AA (001 ticket stock) and a separate ticket on another carrier for continuing travel from ORD. If the AA flight is late or cancelled, AA has no responsibility for onward travel on a separate ticket for travel on a non- oneworld carrier. Advise customers who may be affected that they will need to work separately with the other airline for assistance.
AA to/from AA or a oneworld® Carrier in the Same PNR
Customers should be treated as through ticketed customers. In the event of a disruption on the originating ticket, the carrier responsible for the disruption will be required to reroute the customer to their final destination. The ticket stock of the second ticket must be of a oneworld carrier, eligible under the Endorsement Waiver Agreement. You may contact AA Reservations 1-800-433-7300 (U.S. and Canada) or outside the U.S. and Canada, reference Worldwide Reservations Numbers for additional information if the separate ticket is for travel on a oneworld carrier.
AA - Updated 8 APR 2020
2018 link link as of 11 May 2018.
24 June 2019 link https://saleslink.aa.com/en-us/docum...ty_(irops).pdf
3 October 2019 link
If the ticket was issued on/after April 8, 2020 – see Schedule Irregularity/IROPS on/after 08APR2020
This Wikipost is up to date as of Sept 2021
OLD links (dead)
https://ssc.aa.com/prmportal_enu/AgencyReferenceFiles/Booking%20and%20Ticketing%20Index.pdf
https://ssc.aa.com/prmportal_enu/AgencyReferenceFiles/Baggage%20-%20Through%20Checked%20Baggage%20with%20Separate%2 0Tickets.pdf
https://ssc.aa.com/prmportal_enu/AgencyReferenceFiles/Booking%20Index.pdf
AA Protection for OSO / IROPS / IRROPS / Misconnect on Separate AA / oneworld Tickets
#301
Join Date: Nov 2010
Programs: AA EXP (owe), BA Silver (ows), AB Silver (owr), WN A+/CP, IHG Spire AMB, Avis First
Posts: 1,414
Can someone please put a disclaimer at the top (like maybe the title) of this thread that this policy is very YMMV? It seems that some people have been screwed over even with policy in hand, especially when the second ticket is not issued by AA, and apparently AA even denies the existence of this policy. From what I can tell, there seem to be some conflicts about what JonNYC and others report about what the policy supposedly is, and actual experiences in case of IRROPS.
The other baggage thread needs to be modified as well to not talk about connection protection.
The last positive report was from post #253 back in late 2016 (shortly after the bag policy changed)
OTOH, there was one negative report, but it was at MAD, where there was likely contract staff...
This is particularly relevant to me as I have a LAX-SFO (AA) and SFO-HKG (CX) on seperate tickets, and SFO seems to be experiencing a lot of delays.
A SFO AAngel basically told me that I wouldn't be protected today (flight is tommorow). But I didn't pressure her very hard. Perhaps I will have better luck tommorow at LAX, where agents are probably deal with this sort of thing more often.
The other baggage thread needs to be modified as well to not talk about connection protection.
The last positive report was from post #253 back in late 2016 (shortly after the bag policy changed)
OTOH, there was one negative report, but it was at MAD, where there was likely contract staff...
This is particularly relevant to me as I have a LAX-SFO (AA) and SFO-HKG (CX) on seperate tickets, and SFO seems to be experiencing a lot of delays.
A SFO AAngel basically told me that I wouldn't be protected today (flight is tommorow). But I didn't pressure her very hard. Perhaps I will have better luck tommorow at LAX, where agents are probably deal with this sort of thing more often.
Last edited by no2chem; Jan 9, 2019 at 9:45 am
#302
Join Date: Jul 2015
Location: New York, NY
Programs: AA, CX, AS, DL / Hilton, SPG
Posts: 153
Can someone please put a disclaimer at the top (like maybe the title) of this thread that this policy is very YMMV? It seems that some people have been screwed over even with policy in hand, especially when the second ticket is not issued by AA, and apparently AA even denies the existence of this policy. From what I can tell, there seem to be some conflicts about what JonNYC and others report about what the policy supposedly is, and actual experiences in case of IRROPS.
The other baggage thread needs to be modified as well to not talk about connection protection.
The last positive report was from post #253 back in late 2016 (shortly after the bag policy changed)
OTOH, there was one negative report, but it was at MAD, where there was likely contract staff...
This is particularly relevant to me as I have a LAX-SFO (AA) and SFO-HKG (CX) on seperate tickets, and SFO seems to be experiencing a lot of delays.
A SFO AAngel basically told me that I wouldn't be protected today (flight is tommorow). But I didn't pressure her very hard. Perhaps I will have better luck tommorow at LAX, where agents are probably deal with this sort of thing more often.
The other baggage thread needs to be modified as well to not talk about connection protection.
The last positive report was from post #253 back in late 2016 (shortly after the bag policy changed)
OTOH, there was one negative report, but it was at MAD, where there was likely contract staff...
This is particularly relevant to me as I have a LAX-SFO (AA) and SFO-HKG (CX) on seperate tickets, and SFO seems to be experiencing a lot of delays.
A SFO AAngel basically told me that I wouldn't be protected today (flight is tommorow). But I didn't pressure her very hard. Perhaps I will have better luck tommorow at LAX, where agents are probably deal with this sort of thing more often.
#303
Join Date: Aug 2015
Location: The FT AA forum, until it no longer wants me.
Programs: CK or bust
Posts: 1,913
It's awesome to keep it handy but for hopefully a select few ground agents, it's their word against a screenshot/PDF (and that's proving that MCT requirements were satisfied as well).
#305
Join Date: Oct 2005
Location: TLV now - formerly LAS
Programs: King of Rental Cars, BA Gold, Virgin Gold, AA MM Gold, A3 Gold, SK Gold, Hotel SuperElite
Posts: 7,357
#306
Join Date: Sep 2002
Location: Thousand Oaks, Ca., USA
Programs: AA Lifetime Plat; Bonvoy Titanium Lifetime Elite;Hyatt Globalist; HHonors Diamond; United Silver
Posts: 8,315
A two year old screen shot when there may have been changes in the policy since (and definitely changes in the wording).
#307
FlyerTalk Evangelist
Join Date: Dec 2003
Location: Not here; there!
Programs: AA Lifetime Gold
Posts: 29,587
I'm not a Twitter user, but it would be interesting if someone Tweeted AA nowadays, and asked whether AA still protects on separate AA-oneworld tickets that are on separate PNRs.
#308
Join Date: Aug 2015
Location: The FT AA forum, until it no longer wants me.
Programs: CK or bust
Posts: 1,913
#309
Join Date: Jul 2015
Location: New York, NY
Programs: AA, CX, AS, DL / Hilton, SPG
Posts: 153
Obviously I wouldn't try to use a 2 year old screenshot, that was an example of a conversation I've had. In the past if I thought I would need to use this rule I would DM them with my PNR so that the message was case specific to confirm that I was protected in writing and would use that if needed/if the airport agent was unaware of the rule. I don't see a problem with that, it was backup from the often very knowledgeable folks on their Twitter team.
#310
Suspended
Join Date: Mar 2001
Location: FIND ME ON TWITTER FOR THE LATEST
Posts: 27,730
This seems to be a major change and would be a huge devaluation. This rule was virtually the only the only reason I still flew AA TPAC. I reached out to AA for clarification.
Obviously I wouldn't try to use a 2 year old screenshot, that was an example of a conversation I've had. In the past if I thought I would need to use this rule I would DM them with my PNR so that the message was case specific to confirm that I was protected in writing and would use that if needed/if the airport agent was unaware of the rule. I don't see a problem with that, it was backup from the often very knowledgeable folks on their Twitter team.
Obviously I wouldn't try to use a 2 year old screenshot, that was an example of a conversation I've had. In the past if I thought I would need to use this rule I would DM them with my PNR so that the message was case specific to confirm that I was protected in writing and would use that if needed/if the airport agent was unaware of the rule. I don't see a problem with that, it was backup from the often very knowledgeable folks on their Twitter team.
#311
Join Date: Jul 2015
Location: New York, NY
Programs: AA, CX, AS, DL / Hilton, SPG
Posts: 153
Still officially protected:
https://twitter.com/xJonNYC/status/1143924722968801283
https://twitter.com/xJonNYC/status/1143924722968801283
#312
Join Date: May 2013
Location: LHR
Programs: AA EXP, DL DM, Marriott Titanium
Posts: 1,033
Still officially protected:
https://twitter.com/xJonNYC/status/1143924722968801283
https://twitter.com/xJonNYC/status/1143924722968801283
Also (as you point out on Twitter), that "same connecting point" is a stealth deval of this perk, especially since most of the use-cases would be connecting from AA onto once-a-day flights from the connection city...
#314
Suspended
Join Date: Mar 2001
Location: FIND ME ON TWITTER FOR THE LATEST
Posts: 27,730
But, in any case, for AA-AA connection point not static, for AA<->OW it says to maintain connection point of the 2 tickets.