Originally Posted by
cricketer
I'm basically reading it as:
When you booked an award ticket before Feb 3rd, you locked yourself into:
1. A trip between two regions
2. A particular class of service (which you may or may not be already seated in based on availability)
Therefore you can essentially change your airports for origin and destination, change your dates, change your carrier as long as you stay travelling between Europe and North America in F (or whatever your ticket was)
Originally Posted by
enki
I also hope that's true. I'm assuming that I can't do the following:
Orig: SFO-IAH-IST-FRA-BKK in TK J, TG F
New: SFO-FRA-IST-BKK in LH F, TK J
But...the regions are NA->SE Asia, it's been ticketed in F. So those are my two parameters. If I have latitude to travel between these regions in F in any way I want, that changes the plan (for next June).
Again, I'm assuming I'm locked in and not expecting to be able to change much. But I very much hope that you're right, cricketeer.
I also hope that
cricketer is right and I could see it being interpreted that way. It would essentially boil down to - "If it would have caused a recalculation of miles under the old award chart, it will cause a recalculation now". And that even covers where you change regions with the same number of miles required - that still would have caused a recalculation of miles, even if the number of miles that resulted from the calculation was the same number - so it causes a reprice.
SFOvacations earlier posted about award codes and that may be the key. The speculation would be that if the award code doesn't change, then the award doesn't reprice. Any change to region, overall cabin type or award type (standard vs saver and probably OW vs RT) causes the award code to change which triggers the reprice.
From a programming perspective it even makes sense. There is a lookup table with the award code and the number of miles required. If you change award codes (a whole new set has been developed for post 2/3 award apparently) the lookup table points to the new number. As long as the award code stays the same, the table continues to direct the software to the old number.
If this turns out to be the case, we may have to stop bashing UA for just a bit
This is a bit self serving since I am hoping to change my convoluted routing to FRA in J into a more direct route in J or F since it is an overall F award to BKK (without jumping to the new obscene mileage levels)