Change of underlying AA flight on BA codeshare causes MMB issues
Hi everyone!
I'm hoping someone has had experience of this issue before and can advise if it's actually an issue or not, since it has so far proven impossible to tidy up.
At the beginning of the year I booked an itinerary with BA (BA ticket purchased through BA.com) which included BA1517, JFK - LHR, which at that point in time was AA100 departing JFK at 18:10. At the end of January I received an email from BA saying the departure time for BA1517 had changed to 19:15. No problem I thought, so left it a few days before checking MMB. When I checked, MMB had updated to show the new flight time, and the seats I had originally chosen on the AA site also showed. I then checked the AA site and noticed that both the old flight and new flight were showing against the AA PNR, in other words AA100 was showing as well as AA106. My previously chosen seats were showing against AA100, while no seats were selected for 106. I chose seats on 106 without any trouble, however BA MMB continued to show the seats from AA100.
I thought time is all that's necessary for AA's system to catch up and remove the extra sector (AA100), so I left it some weeks. No change unfortunately, and I continue to be able to select seats on both AA100 and 106, even though according to BA I'm only flying on 106 (BA1517).
Fast forward to today when I thought I should try to speak to BA about this (for what it's worth this itinerary is over Easter), which resulted in an hour of going round in circles, since BA's system only shows one flight and the agent can't see any problems.
Should I be concerned about the extra flight showing on the AA PNR? Should I be concerned that BA MMB continues to show the seat assignments from the original underlying AA100 flight, instead of the new AA106 flight?
Thanks in advance for any advice, even if it's just that I don't need to worry!