Red4282

Thanks for the detailed response and videos. Im assuming same is true for when in a managed descent and the throttle is in idle mode?

I think I found my answer. This is correct logic as it appears something similar has happened in real life! https://www.flightglobal.com/easyjet-incident-highlights-open-descent-mode-risk/121478.article

So just did a quick flight and tested some things. Took off from christchurch NZ headed for NZQN. Leveled off at FL320. Disconnected autopilot, pitched up and down and throttle adjusted accordingly. Began an early managed deacent, at 1k fpm, same thing, disconnected, and pitched up and down. Same result. Then began the more moderate descent where engines went to idle, and bam there it is. Disconnect and pitch up (or even just level off) and the engines just stay idle and speed plummets. Back to autopilot engaged and nothing. Manually dove down to get speed back up to magenta triangle then engaged autopilot and auto throttle came back to life. It seems as if you disconnect autopilot at any time the engines are in idle, the autothrottle becomes non responsive UNLESS you dive to get speed up to the magenta triangle and re-engage autopilot. At least thats what i think is happening. Again, im not sure if this is actually how the plane is supposed to be or not.

Thanks for the reply. Good info to know as far as way points and such. All Ai pilot settings are disabled. As for selecting a speed, i use the "x" button to go into selected, and do this all the time. In this case, the blue triangle speed indicator, shows up but is totally ignored. I know the auto throttle shouldnt be affected by mountainous ones. However, "normal" approaches, I usually disconnect autopilot at 1000 ft, usually fully configured and on glideslope. Where as mountainous, there is a good chance I may disconnect way early, even before Im fully configured for landing. Thought maybe there was a correlation. Next time it happens I will attempt to grab some screenshots.

Hello all, new member here. I primarily fly the Inibuilds a320 v2 on Xbox, and have enjoyed it quite a bit. As a new simmer, I obviously had some hiccups here and there as I was learning more about the systems and procedures. However, I feel after hundreds of hours, I'm fairly familiar and comfortable flying. I am having one issue occasionally that Im not sure if its something I'm doing, or if there is something wrong with the aircraft/programming. On difficult approaches with terrain, (examples: NZQN, Paro, etc), I have had several instances where the auto thottle just stops working. The most recent event, I can describe very detailed what happened, as I was watching it very carefully. I was coming into NZQN runway 23. I had my flightplan loaded from simbrief. However, for whatever reason, none of the SIDS and transitions will load properly. I select them on the MCDU and insert, but none of the waypoints show up. I tried them all. None work. So as I was about to begin the descent, manually inserted all my waypoints from Simbrief into the MCDU. This seemed to work, as it accepted them and had what looked to be a good approach path. I took the Descent nice and easy, just to make sure terrain was not to be an issue, so i slowed my plane down early. At about 6500 feet or so, right before my last waypoint and final turn into the runway heading, I was at 180 knots (or flaps 1 speed). Approach mode activated. I could see one issue though, there was one last mountain top I needed to clear before I could descend any further, and on my current trajectory, It was going to be very close. So, I Disconnected the autopilot to flight manually, same way i would the last thousand feet or so into landing, and basically just level off to clear the mountain. As I did this, I noticed my speed starting to drop. Engines were at Idle. I made it over the mountain, and started troubleshooting the lack of auto throttle. Still in clb detent, autothrottle still shows its active and engaged. Tried to do selected speed, and still no response. Selected flaps two, as I was getting close to stall speed. Speed keeps dropping. I tried the auto throttle disconnect button, the autothrottle button on the dash, moving the throttle to idle and back to clmb, and there is just nothing. Engines still Idle. Finally, the inevitable happens, and i hit stall speed, AFLOOR triggers and goes into TOGA. It is at this point when I can get the autothrottle back working. This only seems happens when I disconnect the autopilot early, to fly manually. Which is usually a difficult approach. My question is, like I mentioned before, I disconnect the Autopilot every single time I land at about 1000 ft AGL and the autothrottle never drops out. So why would this be any different? Is it because Im not at final landing speed? Is this some kind of bug? Also for clarity, Im using an Xbox controller. No yoke or throttles. Also not using the simple "y" button to turn off autopilot, I made my own key to disengage Autopilot, as that chime on landing was annoying. Thanks for any help!