You got it Mikkel!Glenn

Yes I see what you are saying. So right now the time should be, if placed in Copenhagen at local time 22:22, UTC 20:22? Because Copenhagen is one hour ahead with respect to heathrow local time and heathrow local time is UTC+1.edited for clarification...

Phew. :) I thought I was going crazy. :)

Let me try and make another table:For heathrow:Local time: 22:22GMT: 21:22UTC: 21:22For Copenhagen:Local time: 23:22 (because it's Heathrow local time +1)GMT: 21:22UTC: 21:22...this I cannot get to work in fs9. It says GMT is 22:22.

hey--wierd question though, where'd u get those pages that describe all of the options available for the 737? Is that available online or are those brochures/purchasing information which you had that you scanned in?Thanks a ton

That's the Continental AOM...

ok thanks a ton

If you need to read what the GMT/UTC is in your fl sim situation, just look at the fmc init page.

>When summer time is effect in the UK GMT is one hour ahead of>UTC. So no, GMT is not UTC in reality. Typical of the POMS. Obviously upset that the YANKS decided to obliterate reference to some outdated reference to Greenwich. The prime meridian still traverses this hallowed (at least in the POMS eyes)land but at the end of the day UTC is a more recognised term. Anyway, if GMT moves forward an hour - why the heck did they come up with BST?Andy b

Just as a FYI, there seems, to me atleast, to be bug in fs9 about the time zone Denmark is supposed to be in. I downloaded FS Real Time to see if there is anything that program could do about it. Unfortunately I haven't been able to fix this. According to this program my System UTC is, right now 01:31, my flight simulator UTC is 01:31 but my local time is 02:31...where as it should be 03:31....is there any fix for this?

So what is Zulu time?;-)

Wow.. what a lot of discussion over a fairly simple thing :DFolks, UTC = GMT = ZULUGMT is what it was called because old fashioned navigators needed a reference from which to measure their angular displacement around the world and our English brothers got in first and laid claim to the Prime Meridian of longitiude.The way they used to measure that longitude was to have a very accurate clock set to GMT and then observe what local time the sun was directly overhead on it wherever they happened to be colonising or plundering that day. If the sun was directly overhead at 1300hrs on the good old clock they brought from Mother England then they were 1 hr WEST of Greenwich and this can then be calculated as a distance. This is why time also is measured from that reference.UTC is what the Frogs insisted we call it .. not really.. just taking the #### but UTC is what we now call it.ZULU is used because in all operational communications all time references are to be in UTC and are so denoted by the addition of the letter Z after the Date Time Group {DTG) usually expressed as 6 figures eg. 230610Z is 0610 UTC on the 23rd day of the month at the prime Meridian.For greater definition we could use 0410230610Z which is 23rd OCT 2004 at 0610 UTC at the Prime Meridian. Got the picture?Pilots should forget about local time and whether it is light or dark, all time references are in UTC (ZULU) (apart from what time the pub opens and closes so you can beat the rush :-outtaNavigation is where it all started and it is a fascinating subject.. So guys... in which direction does the Earth rotate?;)That should keep us going for a while :DEdited for my abysmal typing

To add some more confusion: I agree with Mikkel that FS9 is not showing the correct localtime/UTC-time differences since (haven't tested) October. I live in The Netherlands, we are still in summertime meaning UTC+2. I always fly with my PC's local time. Indeed since some weeks FS9 shows me an UTC time of 'local time minus 1', while it should be 'local time minus 2'. There is an international (European only??) convention that says when summertime starts and ends. Summertime starts on the last sunday of March. Wintertime starts (IE summertime ends) on the last sunday of October. FS9 does not adhere to that. If in FS9 I currently want to have the same lighting conditions (sunrise/sunset) as in actual Netherlands local time, I have to move the FS clock 1 hour backward. This way the UTC time in FS9 matches the UTC time in real life. Or am I confusing myself here... :-roll :-hmmm Anyway, one week to go till last sunday of October, so all this time stuff will be 'solved' then. :-jumpy :+Henk-Jan

FMC=GMTCLOCK=LMT

And what the **** is LMT now? Mr. Speight? :DCheers,