Did you thoroughly check the flightplan to make sure that a erroneous waypoint was not included in the plan? I have seen this happened where a waypoint with same name is used but is located on the other side of the world, thus giving you the time difference...

Yes I did. Not only was my FMC predicted destination fuel accurate within 300Lbs during the entire flight (which if there were very far away waypoints, I would have gotten INSUFFICIENT FUEL), but I always double-check what I've entered in the FMC during flight planning to make sure there's no erroneous waypoints.Final note until I can test again....even when I was on short final at about 0015Z, the FMC was predicting my arrival at CYYC at after 0400Z...some 3.5+ hours off the actual time. At this point, I'm just going to have to assume there was something that just didn't load correctly with the NGX internals when I started the flight. I've never had this issue in 50+ flights before and after the SP until now. The only reason I bring it up is because it was my first flight with the -600 and I was wondering if maybe anyone else had seen this before. If I'm the only one with the issue, I'll just let it die.I'll report more when I get a chance to preflight this exact routing again...maybe later tonight or tomorrow.

Before you push back you should set your time to the link. http://www.zulutime.net/ This way you always will always depart at the actual time of day it is at your location. Zulu is pretty much used by everyone and if your not using it I have no clue why not.So instead of using the Top Local Time Set it using the Bottom GMT Time and whatever the link above says use that.

That's not always possible. The VA I fly for requires that flights be based on the actual schedules used by the airline(s) being emulated, and the FS local time must be set to match the local time at the departure airport.In other words, if I am flying a Delta flight scheduled to depart Detroit at 18:55 local, I need to set the FSX local time such that my off blocks time will occur at 18:55 in the sim.In any case, I have always noted that there is a +/- 1 hour discrepancy between local and zulu time in FSX in the spring and autumn when flying from U.S. airports. I believe it stems from the change in the start and end dates of DST that took effect in the United States in 2007 - which happened after FSX was released. Prior to that date, DST ended on the last Sunday in October... after 2007, the end date switched to the first Sunday in November. Sure enough, my FSX showed a 1-hour local vs. zulu error beginning last Sunday (Oct 30th). It appears that FSX is internally coded to stop applying DST based on the pre-2007 end date for DST. It should correct itself this coming Sunday, Nov 6th.A similar issue happens in the Spring, when FSX does not apply the DST offset to U.S. local time until the old start date on the first Sunday in April, though since 2007, DST actually starts on the second Sunday of March.

I actually just experienced what you described for the first time tonight from STL-MSP. My ETA was 1725z and current time was like 2230z, I was using fs real time and everything was set to the correct time, even the FMC said the current time was correct however my ETA was totally off.

I actually just experienced what you described for the first time tonight from STL-MSP. My ETA was 1725z and current time was like 2230z, I was using fs real time and everything was set to the correct time, even the FMC said the current time was correct however my ETA was totally off.

Same here. Might need PMDG to look at this. Did not have this problem pre-SP1.

Hello AllI have just landed on another Boeing 737-600 flight and I have had no such problems with my FMC ETA time – I have clocked up 32hours and 52minutes in the 600 series alone (many night flights) and never had any issue with the FMC giving me a crazy ETA time – it tends to be dead on.Did you uninstall the base package and then reinstall before running SP1? Or just run SP1 over the top of your NGX base package?Kimberly

Hello AllI have just landed on another Boeing 737-600 flight and I have had no such problems with my FMC ETA time – I have clocked up 32hours and 52minutes in the 600 series alone (many night flights) and never had any issue with the FMC giving me a crazy ETA time – it tends to be dead on.Did you uninstall the base package and then reinstall before running SP1? Or just run SP1 over the top of your NGX base package?Kimberly

Yes, I did a full uninstall, deleted everything NGX related, reinstalled the base pack, installed SP1, installed the 6700, the installed liveries. I won't get a chance to test it tonight (watching a Sabres game) but I should have a chance tomorrow.

Hello AllI have just landed on another Boeing 737-600 flight and I have had no such problems with my FMC ETA time – I have clocked up 32hours and 52minutes in the 600 series alone (many night flights) and never had any issue with the FMC giving me a crazy ETA time – it tends to be dead on.Did you uninstall the base package and then reinstall before running SP1? Or just run SP1 over the top of your NGX base package?Kimberly

I did a fresh re-install with a new download link which didn't require the SP1 since it was packaged in. Again this was a first time event for me tonight, I'll have to keep an eye out again for this. Also this was my 3rd leg of the day without leaving FS just the standard turnaround, and the previous two legs were fine.

Ok, just doing a flight from EGKK to EKRN. (Easyjet 737-700) Local time depart is 0918. prog page shows ETA @ EKRN of 1648 which is +13 GMT on my system clock, not FSX. So is the ngx reading the system time, and not the time in fsx ?EDIT After departing and arr at end of star, ETA now says 0947Z. I am using FS Realtime, but not auto update

This is a screenshot taken on climb out Dep in post above is a typo, should be about 0900 at chocks off.

Gents-We'll take a look and see if there is something goofy going on here. The theory about the change in DST start/stop dates is interesting... but on the face of it I would expect to see at MOST a 2hr delta between the actual ETA and the predicted ETA (1hr for the known FSX GMT bug and one hour for the DST start/stop date shift.)At any rate- I've flagged this in the system for review... It will give me an excuse to run a quick domestic hop over the weekend...

Thanks Robert. Strange part was it corrected itself during climb out. As the ETA @ EKRN was exactly the same as my system clock, was interesting, we have been on daylight saving in NZ since September.Thank you fro checking this out.

Gents-We'll take a look and see if there is something goofy going on here.The theory about the change in DST start/stop dates is interesting... but on the face of it I would expect to see at MOST a 2hr delta between the actual ETA and the predicted ETA (1hr for the known FSX GMT bug and one hour for the DST start/stop date shift.)At any rate- I've flagged this in the system for review... It will give me an excuse to run a quick domestic hop over the weekend...

Thanks Robert. I do trust that if there is something untoward going on here, you all will find it.Please keep us updated either way.Thanks,

The time issue has nothing to do with CST or GMT. It is a bug. When you set the AOT in the REF page then you have this problem. I hope PMDG will fix this soon.

Current time automatically will display in the POS REF page AFTER alignment. Make sure that you do not have "use system time" option enabled in the FSX general options menu. This option needs to be unchecked as shown in the image below otherwise your ETA times will not follow your input FSX time but rather the real current system time. Could this be contributing to your issue? Best to custom set the time/date for the flight directly into the FSX menu. You need to do this for VA flights. See the image below:

After having the sim for about a month and doing countless flights, I am currently experiencing this problem en route to EKCH. As soon as I cross the waypoint the ATA shows the correct time, but all ETAs are a little over 5 hours off?Adam