Dear FT:

Well, as those with Preview access noticed, UA made changes to their website on Friday that broke this script. Fortunately, it was easy to fix! Please update your script if you've already downloaded it, and remember to update your configuration variables before use, per the instructions. Version 1.15 is now the current version.

If you haven't downloaded, you can get more information and do so here:
http://gallery.theopalgroup.com/UAFareEval/

NOTE: UA's website is now broken in more interesting ways than before, and this will affect the script.

1) For non-*A flights, UA is no longer displaying the distance of the flight in question. So rather than not computing the mileage correctly, such flights are not included in the mileage calculation at all, because UA no longer tells you how long the flight is! This shouldn't be a huge problem, since it appears that the flights affected by this bug would not earn mileage anyhow.

2) Because they no longer display the percentage earning value for PQMs, we can no longer make assumptions about the earning ratio. Instead, we simply assume 100% for codeshare/partner flights, and 0% for non-partner flights. Not quite as accurate as before, but as noted, not that much more inaccurate either. The earning ratios on the website were always pretty bad, and so now they're just a tad worse!

Anyhow, for most itineraries on UA.com this should still work pretty well. At very least, it still displays more accurate earning detail than UA themselves!!

We have the ability to compute partner flights based on the earning tables, but neither the time nor inclination to hand-code them all in, and then keep them continuously up-to-date. If anybody in the community has free time and wants to volunteer to participate in that, just PM me, and we can talk if/when we get a critical mass of support!

Good luck, and happy searching!