I can't imagine what has happened but it seems I can't climb any faster that 600fpm past 10,000FT.I havent changed anything at all and just recently noticed yhis about a week ago.At present,I have about 60% fuel enroute to KORD from KDFW..This is very strange. Right now as I type this message, my climb speed has dwindle to less than 100fpm..At this rate it will take me all night to reach FL350...I have both LNAV and VNAV activated, both appear to be working just fine..I've activated the togo button as I normally do but I just can't figure out whats wrong..I have restarted the flight and even tried CLB2, but no change...Please help,..Need a little help explaining thisTroy

BUMP!

Post a screenshot of your main panel while your problem is happening.- Bill

These are the best I have...I'm now at 1100FPM, but this is inconsistent..http://forums.avsim.net/user_files/49710.jpghttp://forums.avsim.net/user_files/49711.jpghttp://forums.avsim.net/user_files/49712.jpghttp://forums.avsim.net/user_files/49713.jpghttp://forums.avsim.net/user_files/49714.jpgI hope these can help...ThanksTroy

Hi TroyAs far as I can tell, you are not receiving full climb thrust. The FMA should annuciate N1 where it is showing MCP SPD. It is also odd that MCP SPD is annuciated with the speed window blank. The last screen shot shows ARM which really isn't an active auto throttle mode. I can't really provide a solution to you, however maybe I've helped address the problem.Hans

It's simple why it was showing MCP SPD with the window blank, he LEVELED OFF at FL230 with a CRZ ALT of FL350 while climbing in VNAV. N1 should not be there in this case, it should show FMC SPD insted of MCP SPD in this situation and is fixed in SU2. [h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-5/196432/winglets_lg.jpg

Randy I can't make out the altitude in any of the screen shots. Your scenario makes sense if he has reached FL 230, but like I said I can't read the altitude with any certainty. Regardless to help with the initial problem perhaps if he would just select N1 on the MCP he would get the performance he was expecting.Hans

Thanks for your responses guys...I guess I'll have to wait for SU2...It puzzles me though that everyhting work fine before and without any issues until now...HANS said:"Regardless to help with the initial problem perhaps if he would just select N1 on the MCP he would get the performance he was expecting."However, when VNAV is selected, N1 I beleive is disabled..I think...If not, I'll try that scenario and see what happens...Thanks again guysTroy

Hey guys, I figured it outSupposedly my climb speed in the FMC was programmed to climb at 315 and not 290..After I made the adjustment, my nose climbed up to 2500fpm then gradually climbed at 1800fpm. :-)Looks like my finger accidentallly made the changes when I sneezed.Well, I'm up and flying again and DESPERATELY awaiting the release for SU2...sometime this weekend..right guys..:)Wishful thinking :DTroy

Simpel sulution, after reach first altitude and leveled off, just hit Level change and then re engage vnav, then it start climbing as it should again.Mads