So everything is in order in my FMC, I take off, turn on VNAV and LNAV go to click on CMD to turn on the AP and it doesn't want to come on. It seems like it takes a while for it to activate. Anyone know why this is? Like I will click the CMD button and it wont turn on, until about a two three minutes of flying.

First, it's worth reading the manual. Even the quick Introduction Manual explains briefly why this occurs.Second, it could be a number of things, but I'm guessing a few things are your cause:-There are limitations in terms of how close to the ground CMD will take over (you may be trying too soon after departing)-There are limitations on control forces applied before CMD will take command (it won't take over if you haven't trimmed the aircraft properly)All of this could be made moot by:-Reading the manual and observing the limitations-Turning off the REALISTIC AP ENGAGEMENT feature (OPTIONS menu of the FMC, explained in the Intro manual)

Edited February 21, 201214 yr by scandinavian13

Thanks, Kyle... Yeah, I guess reading a manual would be helpful. Sometimes I really feel like I could kick myself it the butt at times. I have ADD, so having the patience with reading is pretty difficult for me. But I believe that I should take the time to go ahead and give it a go... LoL.. Thanks!

I'm terrible at sitting down and reading, but there's something to be said for being able to go in and read the part that you're troubled with at the moment. Just open it up and CTRL+F to search for the term you need. Read that section and that's it. There's no need to sit and read the whole thing like you'd read a novel. I know people here do it, but I certainly didn't (even though I'm one of the 'read the manual' group).

I'm reading it more and more in bed these days. Having lots of ahhhh! moments (no, not for that reason - performance tables just don't do it for me :( )It is so worth it. And so boring.bestjake