Airlines aren't without their flaws. I did see a flight that was magically 1h shorter than all the others. Reason: DST to ST switchover was occurring during the flight and the reservation system didn't take that into account in their computation of the time of flight. That said, you would think that scheduling is an area where airlines pay particular attention.

So it doesn't really matter if you store the meeting time in UTC, local time + TZ or Julian Dates, these are all monotonic. The question is if you have the all the needed information to convert from one form to the next correctly so that this UTC flight time correspond to the correct arrival time in local time.



On 06/09/2013 6:03 PM, Clive D.W. Feather wrote:
random832@fastmail.us said:

Yeah, but if you've got a flight that takes a set amount of time, and
one of the endpoints switches zones and the other doesn't, you'd have to
reschedule one of them anyway. Airlines are the one place I think it
_would_ make sense to schedule everything in UTC. The only situation it
wouldn't is if both endpoints make the same change (as when the whole US
changed its daylight saving rules).

Do we have any airline people here who can comment?

Back when you could visit the flight deck on trans-Atlantic flights, I
often did so. Sometimes I'd look at the flight planning printout, which
gave scheduled times at various checkpoints en route (from memory these are
about every 5 degrees of longitude). All times were in Zulu.


--


Oracle Email Signature Logo
Patrice Scattolin | Principal Member Technical Staff | 514.905.8744
Oracle WebCenter Mobile applications
600 Blvd de Maisonneuve West
Suite 1900
Montreal, Quebec