In the old NG (SU2 600/700), when descending in LNAV and VNAV path, the A/T would hold the speed. So if the FMC stated 300 knots above 10,000 on the DES page, the speed would drop if needed, thus resulting in the engines spooling down. Now before, it wouldn't allow the speed to drop much below that speed and spool the engines back up if it did drop. With the 800/900 installed, the -700 (all I've really flown so far) I noticed the speed will drop 10 or 15 knots below the FMC indicated speed on path descent. Is this normal? Was the prior behavior wrong? If so, can someone explain what the speed descent option will do differently. I tried it once with SU2, but it didn't even come close to descending fast enough altitude-wise. The tutorials I've read aren't clear as to when this is useful.By the way, I've yet to experience very many bugs that I can say are bugs and not possible user error. The baro/altimeter slection via the MCP is the only real problem area. I have the registered version of FSUIPC and don't use the cold start option, rather I just let it load and turn the few switches necessary overhead and on the panel before FMC programming. Just wonder if a lot of these problems are related to cold starts and non-registered FSUIPC apps?Either way, I'm very happy with the new NG!Thanks,Chris

Actually I have the exact same problem. The bird will hold the speed 10 or 15 knots below the FMC Commanded speed, despite the FMC Speed notification in the PFD. Any word on this would be appreciated.

In the old NG (SU2 600/700), when descending in LNAV and VNAV path, the A/T would hold the speed. No it was never like this. PATH never keeps speed unless you are very slow then it will add some thrust but no it never kept any speed and never should. That belongs to VNAV SPEED descents. If you find you are too slow and for some reason desire to keep the target close simply hit the F4 button during descent, this will add some thrust (A/T is at ARM so is realistic) or if you are too fast bring oout the boards. A reason can be winds on descent or unforecasts winds either head or tail.[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | WD SATA 80 GIG | 512 DDR 400 |

A few more words on this,1] A VNAV PATH Descent is not slaved to ANY speed but only to PATH.2] A descent speed a for reference purposes only, the AFS will make no attempt to keep this speed unless it becomes significant (Not sure WHEN but think 30 IAS or there abouts but do not quote me) it will add some thrust and then PATH again becomes the target.3] If you are too fast (within a few knots of the barber poll) the AFS will revert to LVL CH.4] If you desire a set speed simply choose a SPEED DESCENT (VNAV PATH is default descent mode) and SPD DESCENT is slaved to SPEED and NOT PATH although it will keep restrictions thence resume SPD DESCENT.[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | WD SATA 80 GIG | 512 DDR 400 |

I could have sworn it spooled up to the barber poll before. Needless to say, I'm not concerned if it is working the way it should now. :)Also, in ARM does this mean I can use the throttle control on my CH Yoke? I don't use the keyboard for throttle except F1 to idle sometimes.Thanks,Randy

No I do not think the throttle works here (although the real one does of course) so a simple F4 is needed here. Maybe you can map it as a special key ;-) You know F4 is full thrust but in this case it only applies thrust as long as you hold it down which gives good control..[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/forum/betaimg.jpgAMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | WD SATA 80 GIG | 512 DDR 400 |

Cool, I didn't know I could do this. Learn something new everyday!Thanks,Chris