Archived

This topic is now archived and is closed to further replies.

adamant365

Time Prediction Way Off

Recommended Posts

Hey everyone,I'm cruising along in the beautiful 737-600 (WestJet 571, CYHM to CYYC), and I just went to check my PROG page for an ETA at CYYC, and it says that I'm going to arrive at 0655Z. The problem is, the current time is 2239Z. I know it's not going to take another 8hrs, 16 mins to get there from where I am (somewhere over Lake Superior). Also, even though the current time is 2239Z, it says I will arrive at the DLH VOR at 0442Z. But DLH is only 160NM from my current location.I've checked my flightplan for any waypoints that are way off course but there are none. And yes, I've double-checked that my NGX clock is displaying zulu and not local time. The fuel prediction looks spot on based on the winds I entered and the distance/payload in that I planned for 4200 LB reserve and it is predicting arrival at CYYC with 4600.Has anyone else noticed this issue? I think this is the first I've noticed it. A lot of times when I'm flying, I check what's on the PROG page to know how long it is going to take me to get there and I don't recall such a discrepancy before. This is also the first I've flown the -600 so maybe it is A/C specific??Thanks,

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I have no such issues with the 800/900 NGX models after several test flights. Unfortunately I have not yet purchased the add-on.

Share this post


Link to post
Share on other sites

What time are you looking at? Your system (pc) time or the sim time. The fmc will be referencing the time in relation to the time that has been set for the sim time.

Share this post


Link to post
Share on other sites

Get FS Real Time and you will not have this problem again.

Share this post


Link to post
Share on other sites
What time are you looking at? Your system (pc) time or the sim time. The fmc will be referencing the time in relation to the time that has been set for the sim time.
I am looking at the time on the NGX clock to the left of the PFD. I always set the FSX sim time to the departure time of the real flight I'm simulating, minus about 15 minutes for cockpit prep. So, for this flight WS571, the departure time is 1625ET. So, from the free flight menu, I changed my location to CYHM gate 5, selected the 736 WS livery, and then changed the LOCAL TIME in FSX to 1610ET. FSX showed 2010Z at that point which is correct for eastern daylight time. Then I loaded up the sim, did my preflight prep, taxied, took off, and it wasn't until about an hour into my flight when I wanted to check my ETA in YYC that I noticed the big discrepancy.I never sync my Sim to PC time or anything like that...would FS Real Time alleviate an issue with time prediction in the NGX if my FSX time is not synced to real-world time??Another example...I'm coming up on GFK VOR. The NGX says I will arrive there at 0419.9Z but my current NG clock time says 2336Z and I'm only 10NM from the VOR. As soon as I passed the VOR, The ATA on the PROG page shows that I arrived at 2337Z and the "Data" on the Nav display changed to reflect the actual time I crossed it instead of the predicted 0419Z.

Share this post


Link to post
Share on other sites
I am looking at the time on the NGX clock to the left of the PFD. I always set the FSX sim time to the departure time of the real flight I'm simulating, minus about 15 minutes for cockpit prep. So, for this flight WS571, the departure time is 1625ET. So, from the free flight menu, I changed my location to CYHM gate 5, selected the 736 WS livery, and then changed the LOCAL TIME in FSX to 1610ET. FSX showed 2010Z at that point which is correct for eastern daylight time. Then I loaded up the sim, did my preflight prep, taxied, took off, and it wasn't until about an hour into my flight when I wanted to check my ETA in YYC that I noticed the big discrepancy.I never sync my Sim to PC time or anything like that...would FS Real Time alleviate an issue with time prediction in the NGX if my FSX time is not synced to real-world time??Another example...I'm coming up on GFK VOR. The NGX says I will arrive there at 0419.9Z but my current NG clock time says 2336Z and I'm only 10NM from the VOR. As soon as I passed the VOR, The ATA on the PROG page shows that I arrived at 2337Z and the "Data" on the Nav display changed to reflect the actual time I crossed it instead of the predicted 0419Z.
I had similar concerns last night. It was proposed that you set the time to GMT time... I haven't tested, but there was also a suggestion of a utility that fixes FSX time issues... Hope this helps!

Share this post


Link to post
Share on other sites

Another interesting note...from my original post, while I was out over Lake Superior, the FMC was reporting a prediction of 0655Z at CYYC. Now that I'm another hour into the flight, the FMC is reporting a prediction at CYYC of 0552Z. So there is something funny going on with the prediction logic itself. At least with this flight anyway...

I had similar concerns last night. It was proposed that you set the time to GMT time... I haven't tested, but there was also a suggestion of a utility that fixes FSX time issues... Hope this helps!
Thanks, I'm not quite sure what you mean by set the time to GMT. When I set up my flight, I'm setting the local time which also changes the GMT in the sim. As for the utilty, "FS Real Time," I may try it out. Of course, the strangeness of FSX issues dictates that I may never see this issue again.

Share this post


Link to post
Share on other sites
Thanks, I'm not quite sure what you mean by set the time to GMT. When I set up my flight, I'm setting the local time which also changes the GMT in the sim. As for the utilty, "FS Real Time," I may try it out. Of course, the strangeness of FSX issues dictates that I may never see this issue again.
In the time of day screen selected at the free flight screen... When I set my local time to be accurate, Zulu time (or GMT... Greenwich Mean Time) showed 1 hour fast... So the solution was to set an accurate Zulu time, regardless of what the local time says... For instance right now it's 14:39 local/19:39Z... On FSX it would show 20:39ZAs for the crossing zones and having inaccurate arrival times, I cannot verify at this time.

Share this post


Link to post
Share on other sites
In the time of day screen selected at the free flight screen... When I set my local time to be accurate, Zulu time (or GMT... Greenwich Mean Time) showed 1 hour fast... So the solution was to set an accurate Zulu time, regardless of what the local time says... For instance right now it's 14:39 local/19:39Z... On FSX it would show 20:39ZAs for the crossing zones and having inaccurate arrival times, I cannot verify at this time.
Thanks for the reply. I see what you are saying now...but there is a simple fix (I think) for what you are describing. The Time and Season screen defaults local time GMT offset to that of the DEFAULT FLIGHT. So, since I'm near KLEX and am in Eastern time, it was always 3 hours off of the actual offset no matter where I moved my aircraft to. So, I simply changed the default situation to be the trike at KLEX instead of Friday Harbor. I haven't had GMT offset issues since then. You may try changing the default situation to start in your time zone and see if it fixes your hour-off situation. Are you in US Mountain Time by any chance??I don't know where I read about this fix, but it worked for me.Anyway, back to the issue I'm seeing...now that I'm almost 3 hours into the flight, the ETA has moved back further to 0511Z (current NG time is 0029Z). Even though that is still quite a bit off (~3.5 hours by my estimate), it is getting closer to accurate. I will simply have to do the exact same preflight again (after I land this one of course) and see if the issue persists.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
Thanks for the reply. I see what you are saying now...but there is a simple fix (I think) for what you are describing. The Time and Season screen defaults local time GMT offset to that of the DEFAULT FLIGHT. So, since I'm near KLEX and am in Eastern time, it was always 3 hours off of the actual offset no matter where I moved my aircraft to. So, I simply changed the default situation to be the trike at KLEX instead of Friday Harbor. I haven't had GMT offset issues since then. You may try changing the default situation to start in your time zone and see if it fixes your hour-off situation. Are you in US Mountain Time by any chance??I don't know where I read about this fix, but it worked for me.Anyway, back to the issue I'm seeing...now that I'm almost 3 hours into the flight, the ETA has moved back further to 0511Z (current NG time is 0029Z). Even though that is still quite a bit off (~3.5 hours by my estimate), it is getting closer to accurate. I will simply have to do the exact same preflight again (after I land this one of course) and see if the issue persists.
I'm CST, and I did setup the default flight to load at KOKC (CST)... The problem for me was/is that despite the local time being accurate, the Zulu time was still an hour fast... Resetting to an accurate Zulu time yields an hour earlier than the actual local time... but! The sim seems to like it a bit better :). I'd crosscheck Zulu time for inaccuracies at your free flight screen and see if there are any discrepancies between that and local.In my case, I think it may have something to do with daylight savings time.... During the summer, local time is -0500 GMT while the winters are -0600 GMT... We'll find out on Saturday!Cheers!

Share this post


Link to post
Share on other sites
I'm CST, and I did setup the default flight to load at KOKC (CST)... The problem for me was/is that despite the local time being accurate, the Zulu time was still an hour fast... Resetting to an accurate Zulu time yields an hour earlier than the actual local time... but! The sim seems to like it a bit better :). I'd crosscheck Zulu time for inaccuracies at your free flight screen and see if there are any discrepancies between that and local.In my case, I think it may have something to do with daylight savings time.... During the summer, local time is -0500 GMT while the winters are -0600 GMT... We'll find out on Saturday!Cheers!
Gotcha. I check the offset before just about every flight to make sure it is accurate and it has always been accurate. Strange...

Share this post


Link to post
Share on other sites

Everytime I set it to the Zulu time if I look at the local time it is correct. I think maybe you dont have the right time zone selected in your Windows setup or else you did not enable the auto daylight savings time option?Example. I set mine to (GMT-5:00) Eastern Time (USA & Canda) and Check the Box below that for Automatically adjust clock for Daylight Savings Time. (I'm on the East Coast)It will start doing the -5 hours again when we go back to Standard Time. But for now its only -4:00 for Daylight Savings time. But if you have that Automatic Adjust Clock for Daylight Savings Time it will always be right.FSX just uses whatever your system clock is using in windows.

Share this post


Link to post
Share on other sites

Be careful with FS Real Time if you use lots of AI aircraft. If you let it regularly update the internal FS clock automatically, it can create swarming clusters of AI aircraft off in the distance, which you may not even see - except with a map utility that shows all AI aicraft around you. This is a very old FS problem that was never addressed by the FS Real Time devs. This large-scale spawning of AI can kill your FPS and may not even know why.

Share this post


Link to post
Share on other sites
Hey everyone,I'm cruising along in the beautiful 737-600 (WestJet 571, CYHM to CYYC), and I just went to check my PROG page for an ETA at CYYC, and it says that I'm going to arrive at 0655Z. The problem is, the current time is 2239Z. I know it's not going to take another 8hrs, 16 mins to get there from where I am (somewhere over Lake Superior). Also, even though the current time is 2239Z, it says I will arrive at the DLH VOR at 0442Z. But DLH is only 160NM from my current location.I've checked my flightplan for any waypoints that are way off course but there are none. And yes, I've double-checked that my NGX clock is displaying zulu and not local time. The fuel prediction looks spot on based on the winds I entered and the distance/payload in that I planned for 4200 LB reserve and it is predicting arrival at CYYC with 4600.Has anyone else noticed this issue? I think this is the first I've noticed it. A lot of times when I'm flying, I check what's on the PROG page to know how long it is going to take me to get there and I don't recall such a discrepancy before. This is also the first I've flown the -600 so maybe it is A/C specific??Thanks,
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...

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites