Hi,

Is anyone having issues with this?  I'm doing a flight right now, where my current fuel onboard is like 50000lbs.  It's saying, I'll arrive at my next way point at "right now" and that, I'll be at my destination (still 1000nm away) in 12 minutes, and I'll burn 2000lbs of fuel.

Any ideas on what's going on?  Thanks?!

Also, any chance of getting fuel quantity gauges in Lbs?

Thanks

Not sure about your problems, but the fuel is in pounds.

Yep.

I've seen that one quite a lot. I think it has to do with the ARRIVAL and TRANS you select. I'm not 100% sure why it does this but it seems to have something to do with removing or changing a waypoint. Sometimes I've had it happen when I copy and paste the next waypoint to fix the route discontinuance. It can certainly be annoying.

My attempts at fixing it require me to copy the route to RTE2 (before adding SID, STAR and TRANS), just in case it messes up, then adding them again.

Mark

EDIT: To get the gauge to show the fuel in pounds instead of kilograms, you need to modify 2 gauges in the CS_B767-300\panel folder. Check out this Topic HERE in the 757 Captain forum. The idea is exactly the same for the 767. I done it to both my CS757 and CS767! ;D

THORmx wrote on Aug 12^th, 2010 at 12:15pm:

It's saying, I'll arrive at my next way point at "right now"...

The FMC is informing you "Now" a 'step climb' may be performed. You will notice on your map display a green 'S/C' is moving along with you. The FMC has calculated you may increase you altitude by 4000 ft. You may also notice that optimum altitude (VNAV page CRZ) is below what your new altitude would be. I prefer to use 2000 for my step value. Using step climbs is very common on long flights. As you burn off more fuel the aircraft get lighter then you can increase your altitude. This is absolutely essential if your trying manage fuel consumption.

Hi fsxpaul.

I don't believe that this problem is not about needing a Step Climb. When I have this problem, it will tell me my ETA (to my arrival airport!) will be in about 1 or 2 minutes EVEN when it is still thousands of miles away. Something goes wrong with the FMC calculations. I have never seen anything displayed in the PROG page or VNAV CRZ page showing a Step Climb NOW message during this problem.

If I can do a route where this error occurs, I will post some pictures of what happens. When it happens, I often either try redoing the route, or will fly to another destination!

@THORmx. Can you post your route here so I can give it a try?

Mark

@ AABoeing - I'm talking about the overhead fuel quantity indicators.

@Markoz - It appears more than one of use are having this problem, and it is annoying.  I hope that maybe CS catches this and looks into it!  THANK you for the gauge edit, that will be awesomely helpful!

My route was PHNL - KSEA.  mkk4.apack.zoulu.a331.sedar.(some vor).olm.olm6 arr.  (check flightaware for Hawaiian 22) :)

@ FSXPaul - Thanks, but I think I may have incorrectly talked about it.  Basically, I'm saying on PROG Pg 1, that my arrival time at my next fix is like the current time in the sim, or 1 minute from that.  The problem is, that, the fix is like 400nm away.  Furthermore, it shows I'll be at my destination in 12 minutes, when it's still 1300nm away.

Oh yes, I have that issue with ETA. What usually helps is to delete/modify a waypoint (somewhere in the end of the route, if possible, whilst airborne) and type it again in the same place. It forces the FMC to recalculate the times and it often does it right.

mbucholski wrote on Aug 13^th, 2010 at 9:32am:

I used 25 for T/O CG on my last flight and it gave a ridiculous (in my belief) trim of 4 and something. The acft basically took off itself after Vr. I really don't think the 767 needs ANU settings close to a MD-11 (and I like to rotate when I want to, not when the acft does...).

I was thinking of an issue that was discussed in the 757 forum, HERE, where the solution a T/D issue was to literally copy and paste one of the waypoints (part of the STAR or TRANS) in the FMC, and rather than pressing EXEC, just click on the LSK beside ERASE AND It was all looking perfect. It is similar to what your solution is. Definitely worth a try.

Mark

Thought I understood the problem...but apparently not!   :-[
I can say that I've never experienced this oddity.

The overhead in the VC is wrong, when it comes to fuel. It is correct in the 2D though.

AABoeing wrote on Aug 13^th, 2010 at 4:25pm:

The overhead in the VC is wrong, when it comes to fuel. It is correct in the 2D though.

It is? That's strange, because the fuel quantity for all tanks in the VC fuel panel, 2D OH panel and on the individual 2D popup Fuel Control Panel are identical.

Mark

The Total Fuel is incorrect. I got -17.6 or something like that before. It was correct in the 2D panel though.

THORmx wrote on Aug 13^th, 2010 at 2:50am:

@ My route was PHNL - KSEA.  mkk4.apack.zoulu.a331.sedar.(some vor).olm.olm6 arr.  (check flightaware for Hawaiian 22) :) @ FSXPaul - Thanks, but I think I may have incorrectly talked about it.  Basically, I'm saying on PROG Pg 1, that my arrival time at my next fix is like the current time in the sim, or 1 minute from that.  The problem is, that, the fix is like 400nm away.  Furthermore, it shows I'll be at my destination in 12 minutes, when it's still 1300nm away.

I now know what the issue is...T/D was not calculated!       You can see here FL330 @ OLM
http://i823.photobucket.com/albums/zz155/fsxpaul/FSX/Final_ETA_err.jpg http://i823.photobucket.com/albums/zz155/fsxpaul/FSX/NullT_D.jpg

To correct this problem place NEEAL in the scratchpad...      then overwrite OLM (LSK2) then press 'Erase' (LSK6)
http://i823.photobucket.com/albums/zz155/fsxpaul/FSX/Scratch_NEEAL.jpg http://i823.photobucket.com/albums/zz155/fsxpaul/FSX/Overwrite_OLM2.jpg

T/D has been recalculated...                                               And the ETA and remaining fuel have been corrected
http://i823.photobucket.com/albums/zz155/fsxpaul/FSX/ReCalc_T_D.jpg http://i823.photobucket.com/albums/zz155/fsxpaul/FSX/Final_Corrected.jpg

Thanks for that fsxpaul.

When I tried THORmx's route the only problem I had with it, was the T/D not being placed in the route. As you probably know, the fix is the same. I did not see the problem with the FMC giving me my ETA at KSEA being only a couple of minutes from the time it is now, when I am barely out of PHNL.

At least the work-around for this really easy to do. :)

Mark

Thanks everyone for your help on this matter.  fsxpaul, it seems like your suggestion worked!  Thanks again!!!!