Kiwi Flyer

*A RTW Mileage Calculator is available for download from www.staralliance.com

A number of FTers have posted bugs in the calculator. I think it may be useful to note them in one place so we can easily see if the tool returns an error if it is a bug or trying to break a RTW rule.

By having in one place it also may be easier for *A to support the useful tool as we can reference this thread in notifying them of bugs.

Kiwi Flyer

The tool doesnt handle the international date line correctly.

Eg put a flight from NZ to US, connecting to another flight that leaves at an earlier time on the date of departure isnt allowed. This bug also affects the stopover counter (if onward flight is between 24 & 48 hours after arrival).

Markmat

It still appears to be treating Scandinavia as a single country, even though the recent rule changes have apparently changed this.

tfung

Mileage calculations seem to be a bit buggy too. It keeps giving me mileage about 12k more than what it actually is.

Also does not treat JFK/EWR/LGA/NYC as a single city.

Kiwi Flyer

12000 miles error in total mileage? First I've seen any mention of error that big. What routing(s) gives such a big error?

I've had issue with incorrect mileage on direct flights that are not non-stop but only a few hundred mile error.

RWY02KTM

The new TG - JFK-BKK is not correctly identified as Transpac, rather it's still reported as Transatlantic.

wideman

Many flights to/from Manchester, NH (USA) are actually calculated as if they were to/from Manchester, England (UK). Exceptions include MHT-ORD and MHT-CLT routings, which are calculated correctly.

Markmat

Now what would be really great would be if you could get them to price MHT-LHR as if it were MAN-LHR

Markmat

I've had a reply back from Star Alliance confirming that the rule change is correct and the issue with the calculator has been forwarded to the developers.

FF#1

Regarding mileage error, It seems that land miles is also calculated, thereby the ”error” could be quite large if you for an example go to from somewhere to NewYork and next flight is from opposite side of USA.

Markmat

Apologies if I've misunderstood your post, but I don't think this is actually an error.

For example, if your route includes LHR-JFK and then SFO-AKL then the mileage from JFK-SFO is included in your total. This is in the rules:

"Surface Sectors: Intermediate surface sectors permitted at passenger’s expense. Mileage for surface sectors must be included in the maximum permitted mileage calculation"

FF#1

Exactly, it is not a bug but many people misunderstand the way mileage is calculated. I would have been good if the land sectors were listed, now are the just added to the mileage

tfung

I have since deleted that itinerary with the incorect mileage, but it went something like:

BKK-SIN-ICN-SIN-HKG-SFO-LAX-JFK
LGA-BOS-DCA-LGA
JFK-FRA-LHR-SIN-BKK

If I added up all the individual mileages listed per sector, it came out to be something like 34,800 miles, but the total mileage box showed 47,000 miles and told me it was illegal. Only thing I could think of is that it somehow treated JFK and LGA as being thousands of miles apart.

Kiwi Flyer

Did you have more than one option selected for a sector? I have seen that do strange things sometimes.

ph-ndr

Another bug:

After getting the tool to warn about excessive stopovers at an airport on a long itn it will refuse to scroll down the segment list, and always reset to select the first sector in the itn continuosly. Entering an itn with too many stopovers, select validate and then double-click the given error in the lower pane and voila, it will go to sector one and there is no talking it out of having sector one selected.

Also, I have not been able to find a legend of the meal codes used for the various airlines when a meal is mentioned on the sector.

Manually keying in the date in the search function will always result in an invalid date error, it has to be selected from the calendar.

Edit: correction to the first issue