Aircraft would not descend after passing TOD

[Brenchen]

Hi all,

I couldn't get the aircraft to descend post TOD.  Here are what I think are relevant:

• Used Pause at 30nm from TOD
• Set altitude dial to a lower altitude
• Didn't pull the altitude dial until past TOD

The FMA shows "DES" but the altitude doesn't change, I tried "OP DES" as well, also no response from the aircraft.

I had a look through the forum posts here, but no one have mentioned this issue it looks like, begs the question what am I missing/doing wrong?

Thanks!

[Rene Feijen]

I had sort of the same. I could get it to manual VS mode. But then at Cardiff it overshot the ILS in APPROACH mode, did a go around, and then the A350 came in sort of a holding pattern at a random point over the sea, and did not react on any inputs anymore. So ended the flight mid-air. MSFS2020.

Edited March 5 by Rene Feijen

[jaybird]

Not sure I've ever paused right at TOD, maybe it does something funny, try a flight where you don't pause, just initiate a descent at the appropriate time. I've never had a descent fail to start when doing it that way. Do let us know if that is it.

[Brenchen]

3 hours ago, Rene Feijen said:

I had sort of the same. I could get it to manual VS mode. But then at Cardiff it overshot the ILS in APPROACH mode, did a go around, and then the A350 came in sort of a holding pattern at a random point over the sea, and did not react on any inputs anymore. So ended the flight mid-air. MSFS2020.

I couldn't even get it to go into manual VS mode...  I could disengage AP and hand-fly it...

[Hron960]

I confirm the problem. This is the third time this has happened, and the aircraft does not respond to the start of the descent. It really pisses me off. Developers, when will you fix the problem?

Edited March 8 by Hron960

[retrotex]

Same issue.  Since updating to 1.0.2, I can only get the aircraft to descend by disengaging the autopilot.  DES, OP DES, and VS all seem unresponsive.  It appears that the throttle will not retard to slow the aircraft and allow the descent to begin.

[mehmet.dogan]

MSFS 2024 I just bought it and installed it. I am having the same problem.

Edited March 9 by mehmet.dogan

[jaybird]

Simple flow, and it works for me every time, so find what you are doing differently:  Start at cruise, whatever it is right, then adjust altitude setting to something lower, in many cases I just set it all the way to my ILS capture point. Watch your flight display, look for the TOD symbol, when you are oh 10 miles before it, but the exact amount doesn't matter, however what does matter is you're BEFORE it, now position cursor over altitude knob so you see an UP arrow, left click mouse.  That's it. It may not be an instant response, but it will start descent.  Remember - up arrow is push to computer,  down arrow is pull to pilot. So, you push, and now flight computer controls descent, it will not only start descent but it will adjust it and respect constraints on the RNAV descent path you might be on.

I updated the plane, the sim, they are the latest, and I just did a flight this morning, it works. 

[Hron960]

These are all basic actions that everyone performs before starting the descent. But it doesn't always work. Otherwise, people wouldn't be writing here.

Edited March 11 by Hron960

[Ed Moore]

I’ve had this a couple times and when it happened today I noticed the auto throttle had disconnected for some reason, and the engines were stuck at cruise power. As soon as I re engaged the AT with the button on the FCU, the aircraft was able to spool down to idle and begin the decent.

Might not be the same issue but worth a check.

[mehmet.dogan]

V.1.0.4 update result OK.

LTBA-YSSY Long range no problem.Thank You.

[bhorv67]

I had this same issue. what resolved it for me (or a workaround) was to move throttles out of managed mode. Plane then begins to descend. Then move throttles back to managed. 

[Transair]

yes I've also encountered no descent when the a/c should.  Moving the throttles helped that too!

There's some coding that's not right, I think. 

[bhorv67]

Was able to resolve this issue by completely uninstalling the a350 and all associated folders. Then install fresh with the 1.0.4 update. Plane will now descend as expected.