Can we get the timestamps to show correct time zones or maybe just show GMT in Alerts.

The enroute time is unreliable will sometimes show the ETA instead.

It would be nice to have a User Setting to select time zone for all of your Alerts.

Overall the Timestamps for arrival and departure in both Local and GMT and Dates takes up to much of the message.

I don't think we need the date since you cannot file a flight plan much more than 24 hours ahead anyways.

Mike

I got this Alert yesterday, I think we can expect better Alerts...

Flight *** (*) has filed a flight plan from CYKF to KPTK,

departing at 03/24/2008 12:45 PM MDT (1845Z),

ETA 03/24/2008 08:44 PM EDT (0044Z).

Anyone see a problem with this Alert I guess I'm flying a time machine...

This is what I receive all the time and I pay money for this???

Alot of cool feature on this site but take care of your paying customers first!

Mike

Hi Mike;  the FAA has been tinkering with their data feed, and in short - some data centers were supplying an Actual Time of Arrival, others were supplying an Estimated Time Enroute, and there was no flag set to determine the distinction between the two.  What you're seeing is the product of that bug;  the flight was only supposed to take 44 minutes, when the system interpretted that to mean it was going to arrive at 0044 Zulu.

We are now using a different method for determining the flight times, and expect to have a patch in place to use the new method by the end of the weekend.

Andy

We originally included the dates to help provide some clarity in flights that crossed over the midnight boundry.  The new alert lengths have proven too long for some smaller displays to show, so we're going to eliminate them from the smaller alerts with this weekends afformentioned patch.

Andy