SYD
Senior Member
- Joined
- Oct 5, 2009
- Posts
- 8,435
- Qantas
- Platinum
- Virgin
- Silver
- Oneworld
- Emerald
I had something similar a few months ago. Revenue J booking YUL-ORD-LAX-SYD, all QF code, all AA metal. Many months out, AA had a schedule change / cancelled(?) / aircraft change on the ORD-LAX sector that meant no F/J cabin. The fare difference was probably going to be $1.55 if we accepted the alternative option with a whY only sector, so we opted for YUL-DFW-SYD. Which I did online and it was reticketed immediately and I’m sure at the time, online all looked fine in both QF and AA systems.Flying Alaska from SNA-SEA in January. There was a schedule change a couple of months ago (and then a slight adjustment a few days after that) which I accepted through the automated system. Went to check all was good with the booking tonight but saw an error message on the AS MMB: "We're unable to verify your reservation. Please contact your travel coordinator for more information."
Speaking to AS, it seems that Qantas' automated schedule change system has managed to create three etickets on my AS PNR in January meaning I won't be able to check in until QF sorts it out (the opposite problem of what used to occur). So the usual 20+ minute wait on hold awaits. Sigh...
A week or so prior to actual travel, I noticed that the original YUL-ORD sector departing 4 hrs earlier than the new YUL-DFW flight reappeared in the AA app (replete with original seat selection!). A few days out I rang AA and they said speak to QF. Spoke to QF and they agreed that the old placeholder was there but we were only ticketed on the new flight.
Either way, OLCI didn’t work…
I assumed that when the original booking was made, the corresponding AA booking ref had that first flight as an anchor and was updated with new flights but retained V1.0 info.
All fine checking in at the airport - except we arrived super early (concerned by the evil dead sector) and there’s no trans border lounge….
