I would like to have a DS or Phone so I can use it when I travel.

Not sure that it works for long flights that span over the date line and more than one date. The flight to Hong Kong last over 15 hours, FlightAware claims:

5 hours 21 minutes

http://flightaware.com/live/flight/UAL895/history/20070526/1852ZZ/KORD/VHHH

There is a disclaimer:
"At least part of this flight occurs outside of FlightAware's service area. Information on this page may be unreliable."

Could it be that it left FlightAware's service area after 5 hours and 21 min, this is the reason why the web pages states:
"Arrived over 8 hours ago"

meaning "left FlightAware's service area 8 hours ago"...

http://www.flytecomm.com/ seems to have correct information on their web site, but not on their mobile solution:

http://mobile.flightstats.com/go/Mobile/

But it has a good UI since I want to track a flight that left the day before, not the flight that is leaving today. Since I track a flight from CEST time zone, leaving from a CDT and landing in HKT, date is an important input.

BenT

Worked fine for a United Airlines flight from Chicago O'Hare to Hong Kong. A bit confusing that the airlines is not sorted in alfabetical order, you should use a header in the pulldown.

Pressing the update button should result in an update of the current data, not resetting them :-(

And the map might be good enough for the route, this is what I get in the Route field:
PETTY GRB 5000N 09100W 5500N 09300W
6000N 09600W 6500N 09900W 7000N 10500W
7500N 12000W OMEKA ORVIT G494 UESO G495
KU 5216N 11814E DIBOR G496 NAREM B161
SULOK G218 TMR B458 WXI A461 LIG R473
WYN W18 NLG W23 ZUH R473

You should put information about what kind of desitnations it covers, since SAS is not even on the list, it does not seem to cover SAS flights that starts in the US.

But it is a very good start, we need more realtime widgets :-)

BenT

Yeah, at least for now you can get to international airports via links in the arrival/departure tabs, but searching doesn't work. The reason is that there's actually a 4th letter that goes in front of most airports (or at least, on this flightaware.com). In the US it's K, but elsewhere it varies, so I haven't come up with a good way yet to deal with that.

Good catch on the error after a first failed search. I changed the structure after I wrote the code to display the "No match found" message, and forgot to update that. Should be working now.

I'm a little confused about your "don't know the code" window complaint. If you click an airport link the widndow will close, and there is also a close button in the top right that you can use. Are either of those not working for you?

I do see a problem with the flight search, that also should be fixed now. Please let me know if you still have problems with it. Thanks for your comments!

Nice start, but there are some issues:

- "dont know the code" window doesn't close when doing something else and obstructs view. Might just be me being nitpicky though
- Doesn't find the Oulu (OUL) or the Helsinki (HEL) airports.
- Getting JavaScript errors after one failed search when trying to search again
message: Statement on line 217: Could not convert undefined or null to object
Backtrace:
Line 217 of linked script FlightTracker.js
document.getElementById("diagramPane").innerHTML = "Loading...";

The error effectively breaks the search. Try searching for OUL and then LAX for example. You won't get any results at all, but if you reload and search for LAX it works.

Might have more JS errors, I didn't really get the flight number thingysearch working.

From what it appears, not finding OUL and HEL is by design because it seems that the tracking is only for airports in the US.