Ok. I'm really confused and worried about this. For some reason, the aircraft will not climb. I have tried disabling autothrottle, and increasing N1 to see if the autopilot will climb to reduce my speed, I have checked FMC CrzAlt, MCP altitude, waypoint constraints and still the aircraft decends. I have flown this on routes on FSX at least several times. Images included below:

 

 

 

Here is my FMC PROG with 0.0 fuel predictions.

 

 

Any idea on what could be causing both this phenomena? 

Regards

Nick

UPDATE:

Disabling VNAV and using a reasonable V/S if 2000+ doesn't work too.

What is The TAT? (temperature, indicated on the EICAS screen)

+12. Why do you ask?

SAT temp would be a better indicator. Tom is asking because high SAT will cripple your performance which can lead to an inability to climb. You can find SAT on one of the progress pages IIRC, but can't check as I'm not at my gaming PC.

 

However, I don't think this is your issue. I can see that your pitch mode is VNAV ALT. If you're climbing in VNAV and you reach the altitude dialed in the MCP window at any point, it'll revert to VNAV ALT and won't climb until you've dialed in a higher level and pressed the altitude dial in to confirm the climb.

 

As for the FMC fuel strangeness, I can't give a solution but I can see that it's a symptom of something else being wrong. Check out the ETA for WSSS; it's only 25mins after your ETA for BOR, despite being 3106nm further away.

SAT is at the 2nd prog page.

On the FMC, hit prog, and click NEXT PAGE.

If your sat is also + something, there lies your problem.
Ofter a weather engine restart would fix it all.

Hi, Nick,

 

I suggest you run through your flight plan, both by scrolling through the LEGS page, looking at the distances and direction from waypoint to waypoint, and in STEP mode (don't use the lower EICAS to do STEP mode  -- it will cause a CTD.  Use the left or right HSI).  Something is wrong, as your CDU shows plenty of fuel for your destination, over 3000 miles away, but no fuel for your next two waypoints.  Also, it shows you are at the TOD now, more than 3000 miles from your destination.   If the FMCs "think" you are at TOD, VNAV will make you descend to the altitude set in the MCP window, which is what it appears to be doing. 

 

Temperature shouldn't be a problem as you are at a low altitude where ambient temperature can be very high.

 

Mike

Thank you for all the suggestions. I'll give it a go tonight.

 

As for the FMC fuel strangeness, I can't give a solution but I can see that it's a symptom of something else being wrong. Check out the ETA for WSSS; it's only 25mins after your ETA for BOR, despite being 3106nm further away.

 

Oh wow I didn't see this. Cheers.

Thank you for all the suggestions. I'll give it a go tonight.

 

Nick,

 

If you are using an external flight planner, it can throw in wrong waypoints.  I used a well-known one to plan a flight from KLAX to YSSY.  Near Sydney is a waypoint SHARK.  The planner threw one in with the same name from somewhere in Siberia.  Only an extra 6000 miles

 

EDIT: If you have saved the flight plan to a PMDG file I would be curious to look at it.

 

Mike

Nick,

 

If you are using an external flight planner, it can throw in wrong waypoints.  I used a well-known one to plan a flight from KLAX to YSSY.  Near Sydney is a waypoint SHARK.  The planner threw one in with the same name from somewhere in Siberia.  Only an extra 6000 miles

 

EDIT: If you have saved the flight plan to a PMDG file I would be curious to look at it.

 

Mike

Hi Mike,

Yes this seems logical as I just bought PFPX last and this was my first flight using it.

Thanks for the input.

 

 

Disabling VNAV and using a reasonable V/S if 2000+ doesn't work too.

 

If you're asserting that 2000+ is unreasonable, this is a common simism.  Vertical speeds are actually commonly 2000+.  I think this simism comes from two things:

1. The default FS aircraft used to (might still - I don't fly them) default to a V/S of 1800 for some reason.
2. Passenger programs flag you for upsetting the passengers at high vertical speeds.  Apparently they forgot their physics lessons: people feel acceleration, not speed.  Vertical speed is...well...a speed.

The only way it would be truly uncomfortable is if the pilot pushed the nose over, or pulled back sharply to achieve a high V/S, but once established, people would only be able to tell by their ears popping more frequently.

 

 

but once established, people would only be able to tell by their ears popping more frequently.

 

Not even that as long as pressurization can keep the same cabin speed.

If you're asserting that 2000+ is unreasonable, this is a common simism. Vertical speeds are actually commonly 2000+. I think this simism comes from two things:

• The default FS aircraft used to (might still - I don't fly them) default to a V/S of 1800 for some reason.
• Passenger programs flag you for upsetting the passengers at high vertical speeds. Apparently they forgot their physics lessons: people feel acceleration, not speed. Vertical speed is...well...a speed.

The only way it would be truly uncomfortable is if the pilot pushed the nose over, or pulled back sharply to achieve a high V/S, but once established, people would only be able to tell by their ears popping more frequently.

Apologies Kyle, this was a actually a typo. I meant to type of* 2000 not if*. I agree with you on your points

Marking this as solved. Redid my flight last night with the same route and it went perfect.

 

 

Marking this as solved. Redid my flight last night with the same route and it went perfect.

 

Glad it's fixed.  Did you figure out what went wrong the first time?

 

Mike