FlyerTalk Forums - View Single Post - AA ignores oneworld protection when mech causes delay
Old Sep 2, 2019, 3:13 pm
  #11  
DMPHL
 
Join Date: Jul 2009
Location: NYC
Programs: AA EXP
Posts: 1,372
The confusing thing to me is what AA is supposed to do with the "same connecting point" language. It would seem to be within policy not to route the passenger PHX-PHL-DBV, for example, or PHX-LHR-DBV, because the original itinerary, taken together, is PHX-HNL-etc...Are they supposed to re-route the passenger from the origin of the first ticket as directly as possible to the connecting point on the second ticket? Or treat the origin of the second ticket as the connecting point?
DMPHL is offline