Originally Posted by
hillrider
This is not an EF issue, it's the way AA works.
Originally Posted by
inlanikai
This looks like a married segment logic issue. This happens a lot with AA (and I suspect other carriers) and is not limited to upgrade and award inventory.
Correct, this is married segment logic (also called Journey Control). In order to maximize their inventory, and revenue, airlines can show different inventory for fare/upgrade/award classes on a flight depending on what other flights it is paired (married) with.
Originally Posted by
3544quebec
And as an additional question - if EF shows this C availability somehow based on POS/origination then how does the alert feature work with this? If a C becomes available JFK-GIG for a search originating LHR who does it notify if an alert is in place? Note that the C is available for connections from the AA-coded BA flights LHR-JFK where no C is available on these flights, only on the JFK-GIG sector.
Right now, Flight Alerts looks at the segment the alert is set for by itself. One of the improvements we are going to make in the coming months is to build into Flight Alerts the ability to handle married segment logic by factoring in the full itinerary.