Hi there
Sometimes when I click the autopilot button it won’t turn on , i get the following sounds 4 bleeps and a few clicks , so guessing something is not set right but can’t see what I am doing different
It’s the development version
Thanks
Douglas
Sorry. Can’t help without a lot more information
1 Like
My guess is that your PFD shows A.THR . That means you are in Auto Throttle lock. When you take off, you have to put your throttle back to CLB otherwise you will be be lock.
A.THR doesn’t mean that thrust/throttle is ‘locked’ and it doesn’t have anything to do with the ability to engage the AP.
Those sounds are probably the autopilot disconnecting immediately.
The airplane at that point isn’t in the right configuration and the AP does not want to take responsibility for your piloting skills 
But what that wrong configuration is exactly is hard to tell. I’ve had the AP scolding me like that numerous times. It only wants to switch on when the plane is a bit towards ‘stable’. Usually when this happens to me I am in some kind of really steep bank, hoping for the AP to save me. But it’s like one of those crazy parents and just pushes me back into the swimming pool.
4 Likes
If only there were some way for us to avoid guessing what the situation is… Oh well.
This is something that was implemented recently that people are not used too. Basically, If you take off on MAN TOGA and you don’t set your throttle back to CLB after 3000 Ft, you will get into A.THR Lock situation where you can’t engage AP. you need to reset your A/T button and put the Throttle back to CLB than you can re-enage A/T and AP. It will work after.
1 Like
Thank you all that makes sense now
After the updates yesterday 6/8 the managed heading was automatically trying to BC the flight plan… it started working normally after GS capture. The LOC was captured and was in APP mode, was within 15NM but far from 10 degrees of any other runway for LOC BC… This was at Flightbeam KDEN though, it might have been an issue with their scene. I read on their support page that KDEN has some ILS issues. Haven’t tried today’s FBW update yet. I guess either way when using dev versions we’re bound run into some issues.
Is that how it works IRL? The FCOM states that AP/FD can be operated independent of AT.
Thrust lock only occurs with the thrust levers in the CLB detent (MCT OEI ops) and an amber flashing THR LK message on the FMA.
1 Like
I don’t fly A320 in real life but this is how FSlabs or Aerosoft A320 product works. It wasn’t in the FBW A32NX until recently.
I did fly it, but thinking about it this is behavior seems to be wrong since you can engage the AP at very low altitude, e.g. 200ft.
That’s way below thrust reduction altitude.
The autopilot can be engaged after: 1) reaching 100 feet, and 2) no less than 5 seconds after becoming airborne.
Difficulties in engaging the autopilot we’ve seen are usually due to the sim pilot pitching too high and getting into an alpha floor situation. Generally, a pitch to about 18 degrees, taking about 5 seconds should work well. Do not pitch so high or fast that you reduce speed to less than V2 speed (target V2+10 or higher) and definitely not so much that the speed is less than the top of the yellow band on the speed tape.
hahahahahaha nice
Makes much more sense. I loved engaging the AP at 200ft and watching the AP doing a nice clean up on its own.
If you tried that with the CRJ (which theoretically could do the same) the first thing that happened during the acceleration phase was the DON’T SINK warning 
That is not how it’s implemented.
I even don’t know what you mean by A.THR Lock. There is only TOGA LK and THR LK.
But I make it short: fly the plane properly 
I meant THR LK. I had a brain fart. Thanks for the correction.
how to unlock the auto throtle? if i push the button is still engaged and can’t do nothing
Also, make sure your speed is not set to a manual value and you heading next to it or you may find that the aircraft is still not doing what you want it to do on autopilot.