Engine shuts down on approach after long flights

I’ve been having this issue almost constantly whenever I do long flights. Over an hour I would say.

I’ll be cruising just fine. Start descending. And on descent. Usually as I get to the final 3000ft or so. My engines will stop responding correctly. They will just slowly start ramping down. And I’ll add power and they will surge to life. Then continue spoiling down and this will repeat a couple times until finally one completely just shuts down and then the second one will eventually.

This happens on any aircraft I use. From the Baron. To the 787, to the new Aerosoft CRJ.

I have made sure to use anti-ice systems. But it even happens on clear hot days.

And since it happens on every aircraft. I don’t think it’s related to doing a procedure wrong. Especially as I fly some of them in real life. I have also triple checked that I have fuel and even made sure to keep fuel in the center tank all the time when there is one. And I even re-installed the game at one point. It also doesn’t seem to be a control issue as I have changed to new throttles and the issue still happens.

Only seems to happen on descent with low power settings.

Nothing is more frustrating than doing a long cross country or a commercial flight and then just having the engines going crazy and shutting down on final approach.

If anyone has any ideas. Let me know. Thank you.

I’ve never had it but the only thing I can suggest is fly the CRJ and when it occurs again hit active pause and go through the displays to see if you can see something. fuel, electrical and engine displays are the obvious ones but go through everything you can.

I’m increasingly convinced that the always-on switch bug causes a lot of weird bugs. With the CRJ especially I had to make sure every one of them was unmapped and replaced with a spad.next macro.

The problem is that you may not find a hint in the UI. Eg. in the CRJ i had to enable avionics bus 1 on my alpha yoke for AP to work. The aircraft setup was fine but a ga aircraft config caused the jet problems. This was because it is an always on switch so it was always forcing avionics bus 1 to off even though it looked ok on the jet.

Seriously annoying! And a hard to spot bug generate for years to come if it remains unfixed.

Hm. Interesting possibility. I will double check that. But my initial thought is that is probably not the case as I have changed the yoke and the throttles and the problem still happened after. I also have different profiles for the airliners, single engine, and multi engine controls. So even a different control profile didn’t work. But maybe there might be something hidden. I’ll have to look through it. I just find it odd that it only happens in one specific phase of the flight if it’s a constant things as you mentioned.

Yeah, it is weird. But there has to be something in either your setup or your procedure or we would all have the issue. So the issue is clearly something we would never expect!

One super stab in the dark, but, are your USB ports set to power down if a stick isn’t used? That is Windows’s default behaviour. I turn off power savings to all my devices, but I’m sure most don’t so like I say. I know it causes funny stuff in other games but not heard anything concerning MSFS.

I noticed that when playing with just a keyboard, when throttling down using F2, I sometimes accidentally went into reverse thrust. Perhaps check if your throttle bind for thrust axis is set to (-100, 100) instead of (0,100), or a reverse-thrust toggle is somewhere double-bound.

Not sure if this is possible with the aircraft you mentioned, but the Cessna Caravan at least has no objection of you reversing thrust during flight.

As you say it happens to all of your aircraft and only on approach, my guess is that’s the first time in each flight that you’re throttling to idle or near it.
If that’s the case I’d be looking at my throttle axis binding range. You might find minimum throttle is actually somewhere other than your control minimum stop.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.