- Joined
- Jun 24, 2008
- Posts
- 4,726
- Qantas
- Gold
- Virgin
- Red
Now here's a thought. Your flight from CLT to LAS is showing the flight number as AA1323. When I put AA1323 into Google or FlightAware, it comes up as a flight from DFW to DTW. This also shows up on the AA website:If the arrival port of a surface sector counts as a stopover then what I'm requesting would indeed be over the stopover limit. I didn't realise this. I thought only the arrival port of flights in the itinerary were counted as stopovers (if not flying out of that port within 24 hours).
Ie. I was under the impression that after landing in a stopover city (say NYC), you could make your "own" way to another city (say LAX) to catch a flight without LAX itself being counted as another stopover (and only the destination city of the flight from LAX being counted as a stopover were you to stay there >24hr).
This is our itinerary on the Qantas manage booking page, they have added the "New York" EWR-CLT-LAS segment but its not yet ticketed
View attachment 405370
I was banking on the stopovers in the above itinerary only being Helsinki, NYC, Las Vegas and London (with a view to add LHR-HKG in the future). If I wrongly interpreted the surface segment stopover rule, then I might just gun for LHR-HKG instead of the transcontinental US flight..
Addit: I have emailed rewards escalation and hopefully get a result
Thanks for the help so far!

I know flight numbers get reused for different routes from time to time and presumably this is the case here; at some time between now and May 2025, the flight number is being reassigned from DFW-DTW to CLT-LAS.
If that is the case, maybe the QF backend is picking up the current route (and distance) from DFW to DTW, plus surface sectors from CLT to DFW and DTW to LAS. If so, the total milage would be calculated as 36,230.
Try adding a different flight (different flight number) for the CLT-LAS sector and see if that solves the issue. Alternatively, pick a different routing from NYC to LAS.
Good luck.
