Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Archived

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

Zimmerbz

Destination estimated times

Recommended Posts

I've noticed that in the mcdu the estimated destination time for the arrival airport is always wrong. The flight plan times seem ok but not destination.  For example, it is 23:37 and I am expected to hit my next waypoint at 23:48. That makes sense but it shows KDEN (my destination) at 14:59. Is this a known bug or did I make a mistake somewhere?  Thanks

 

ps. I've noticed this on a majority of my flights so I don't think it's the route. 

Share this post


Link to post

Would need some screenshots of the Mcdu f-plan page to see. Why don't you scroll through the plan and find out where the discrepancy lies? KDEN may be showing incorrectly, but perhaps the error is actually somewhere downroute. I can say I've ever had a problem with it. As I say, screenshots would help.

Share this post


Link to post

Sounds good.  I'll try a flight tonight and see if it happens again and try to get some pics.

Share this post


Link to post
5 hours ago, HAL-9000 said:

Would need some screenshots of the Mcdu f-plan page to see. Why don't you scroll through the plan and find out where the discrepancy lies? KDEN may be showing incorrectly, but perhaps the error is actually somewhere downroute. I can say I've ever had a problem with it. As I say, screenshots would help.

 

IMG_0220.JPG

Share this post


Link to post

It isn't the clearest pic but you can see the times don't add up. My next fix is HVE at 23:27 and it is 23:08. It says my eta to KLAS is 14:44

Share this post


Link to post

I haven't flown the buses for quite a while but I will soon get back to flying them, I noticed this much more when flying across the pond with the A318s, I believe the aerosoft buses calculate the time using nautical ground miles rather than nautical air miles, in basic words calculating the time without wind prediction etc (soon to come in the update), now I can't remember if this was the only cause, but it did play a huge part in the discrepancy.

Simbrief and PFPX will calculate fuel using nautical air miles so it will account for the wind data it recieves from your route.

Share this post


Link to post

even if calculation is on somehow wrong data/dimension that should not lead to hours of difference from TOD to landing.

 

maybe it's a problem if arrival is on the next (UTC) day? - you could try a flight that ends (planned) on the same day (KDEN-KLAS starting at 1700 UTC)

Share this post


Link to post

I've noticed this periodically myself and in fact today it happened again.  It would indeed seem to be some math error being caused by the time of day.

 

Flight plan was jetBlue 711 KJFK-KLAS; JFK3 GAYEL Q818 WOZEE KENPA CESNA Q138 DKOTA RAP J158 DDY J107 MLF GRNPA1

 

Just before UTC 00:00:

 

2017-4-20_21-23-43-668.thumb.jpg.10824a86a41c9b3cf2c338e17b8f48ce.jpg

 

and just after:

 

2017-4-20_21-23-51-258.thumb.jpg.6a9afff99edb92f93e7f16c19deba0fd.jpg

 

Note that the MCDU PERF CRZ page reflects the same erroneous time for both arrival and T/D (taken earlier than the above):

 

2017-4-20_20-19-36-104.thumb.jpg.8267598a6e591b942b0a86a439bd0402.jpg

 

I'll make sure to check it the next time I fly within the same UTC day (which is most of the time, to be honest).

 

 

Share this post


Link to post

I've run a few more flights in the meantime and the pattern of "corrupted" estimated arrival times certainly seems to fit the pattern of only occurring during flights spanning UTC 00:00.  Here's my latest, showing a flight within the same UTC day:

 

jetBlue 1412 TNCA-KFLL; TOVOL UA315 JOSES A315 ZBV WAVUN2

 

2017-5-2_20-33-14-615.thumb.jpg.370862d645407a77b080251bab403f2b.jpg

 

I guess the only thing left to test now is to see if a flight originally within the same UTC day "corrupts" if the ETA drifts past 00:00 (for example due to wind)?

Share this post


Link to post

I believe there was an issue when you cross the 0z time.

 

It is fixed in our A330 builds, so with the next A320 this will also be fixed.

Share this post


Link to post

×
×
  • Create New...