Originally Posted by
hillrider
It means that when originating from LHR, AA is willing to open up a lower fare bucket (e.g. D/I) than for those originating from JFK, based on various factors, including total ticket value, competitive fares/availability on the LON-RIO market, etc. etc.
Even though it probably doesn't make much sense, C availability seems to be implemented by linking it to those lower-fare buckets, so you get the effect that you see.
This is not an EF issue, it's the way AA works.
Thanks for attempting to explain but it seems an unlikely explanation as there is no availabilty showing in D or I on the JFK-GIG leg when I do a LHR-(JFK)-GIG search, only J4 on the JFK-GIG leg fro all flight combinations from LHR
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.