APPR Mode -- and Autopilot in General is BROKEN

On approach to SKBO this morning in the A320, capturing the localizer on a 30 degree angle, below the glideslope, and the aircraft begins to wildly over-correct for altitude, speed, and heading.

How… HOW is this not fixed by now? Why is the autopilot not smart enough to know that it needs to reduce the thrust when I’m approaching the set speed, instead waiting for me to GET TO THAT SPEED before reducing, and vice versa for descents? Why does the throttle shoot up to 100% when I set climb speed after departure? Why does LNAV wait SO LONG to initiate a turn on path to a waypoint, so that I end up shooting wide and having to turn back on myself? Why, when capturing the glideslope, does it wait for me to be above the glidepath before beginning the descent down it? Why isn’t there more anticipation programmed in… (I know it is programmed in, otherwise we would be turning right when we’re on top of waypoints!) why does autopilot seem so STIFF?! Why isn’t it more SMOOTH?

I understand that not all of the planes have correct physics but COME ON. This plane was updated not too long ago – and even newer planes have this issue as well, including the 772 and A350. I don’t always want to hand fly the approach, especially when I need to intercept the localizer 15nm away from the threshold.

If this seems rant-y, that’s because it is. I’m very disappointed that these issues haven’t been addressed yet, especially with how much pilots are relying on VNAV and LNAV now with the introduction of SIDs and STARs. I love this game, I hit 1,000,000 XP recently… but more and more, I’m beginning to understand all of the complaints that I see regularly on this community forum.

Discuss below. Lol.


Well, IT IZ What IT IZ

for the APPR if you use a lot of trim and slowdown manually it might help, and for LNAV make sure you don’t have too much charp turns


That’s the problem. I’m not satisfied with “It is what it is.” This is a glaring issue that I am positive affects more people than me.

My trim was no purple.

As for LNAV, what about generated flight plans, or even some published STARs and SIDs? Sometimes, they’re unavoidable.

Adding on to what you said here…

I shouldn’t have to slow down manually. This topic is about the autopilot and it’s issues.


Personally I don’t experience the issues you wrote at all. I only experience the APPR one. Other aspecta of the autopilot for me are all good. And for the throttle going 100% monitor it manually then

Edit: well then make a feature request for an improved A/P

I am having an issue right now! my AP is sending me to hdg 230, and the LNAV is around 170, and it doesnt matter what I do, it is broken

Honestly I could copy paste this or change the topic to features and I wouldn’t need to change anything except maybe the “Discuss below. Lol.” part and maybe be a bit more definitive in what I’m asking for.

1 Like

This might be because you have NAV1 enabled instead of GPS…


That was it, idk how it happened, thx

1 Like

I do agree with what you have said here. APPR has definitely improved recently, but I found LNAV has got worse. I find that I end up flying in circles way too much. And no, I haven’t got too sharp turns. I can do it fine myself in heading select, but LNAV waits too long. Autothrottle has always been like that.

I think we should continue discussion here though:



that last i used APPR was like 3 months ago
I pretty much always do a RNAV or Visual

Never noticed that topic, thanks.

I get that development takes time but… jeez. Almost three years and nothing from devs about implementing a feature that is highly voted for. :(

Some people like to use ILS approaches, like me.

1 Like

I think they have smoothed out APPR. It’s just a few glitches here and there. As for LNAV, I think they “smoothed it out” in V20.1 but it didn’t work as intended.

1 Like

The biggest issues I have are LNAV throwing you way wide of your path instead of turning you sooner. VNAV has worked awesome for me, it’s my favorite new feature besides SIDs and STARs. APPR is definitely smoother than it used to be but it still isn’t enough in my opinion.

1 Like

Do your planes turn very violently during cruising from waypoint to waypoint?

1 Like

It depends. Sometimes, yes, with lighter aircraft like 737s, A3–s, etc. Not so much with the heavier planes, but I have had that issue with the A350 and 772. Also depends on the angle, usually the more acute the angle, the more harsh and wide the turn.

I’ve found that reducing the sensitivity of the roll in controls settings can help with that – but that is a cludgy solution at best.

1 Like

See this is why I don’t trust computers. But in today’s world they are unavoidable, so I was forced to make a compromise. I don’t use autopilot below 3000ft AGL, unless I am confident that the aircraft will keep stable and not make any aggressive maneuvers (which is why I am phasing out using infinite flight’s APPR feature because it really really sucks and it needs a ton of work). I am more confident with some aircraft than others to fly safely and comfortably, but regardless, I try to use the airplane’s computers (autopilot and APPR) as little as possible, because like I said you shouldn’t trust computers.

I have had no problems with APPR mode for months…so clearly you are doing something that you shouldn’t be (ie going too fast, too high etc…)


I might just address a few of your points here, because I use APPR each time I fly an ILS approach to capture the localizer and I have not had any issues with it aside from when I had not configured it correctly.

Yes 30 is the limit but I try to aim for no more than 15 to be super sure.

First of all, APPR cannot control speed. There must have been something else going on here. Perhaps a replay share is in order? Furthermore, APPR will not correct altitude until it is established on the glideslope.

I understand your frustration, however take a step back here. The people who code these systems are fantastic at what they do, there is no doubt about that. However they are not aircraft engineers, and they are working on a mobile simulator here - performance has to be considered.

Consider the alternative. If autopilot needs to throttle back as it approaches it’s target speed, then aircraft performance needs to be taken into account to avoid over compensation. That means individually programming the autopilot for each aircraft which is very time consuming.

As above. Doing this would need to consider aircraft performance meaning each aircraft’s autopilot needs to be made individually leading to an even longer time from starting to create an aircraft to release.

Same issue. See above.


Please remember these functions do work. And the alternative is an even longer development process. Laura has said before autopilot was one of the hardest things to make, so this could well add a month plus to aircraft production.

If you’re sure it’s a consistent issue, see Maxim’s post below.

I hope I’ve answered some questions and if not excused the quality of the current autopilot then at least explained the likely reasoning behind its current state.


You post a topic about an issue that is bothering you, yet I can’t find any details like your replay, flight parameters etc. I’m not sure how you want us (and the developers) to help you without including this information? For all we know it might be you who is incorrectly using APPR (you have to admit, this is a possibility from our side).

If you want something to be done about this, more details are needed. In particular, can you reproduce this issue with certain settings? For example:

  1. Select thisApproach at thisAirport
  2. Have thisAmountOfWeight
  3. Fly at thisSpeed KIAS
  4. etc etc…

By reproduce, I mean can you consistently (every time) fly the same approach, with the same settings and get APPR to ‘mess up’? If you can, post below and that’ll be of great value to the developers. Saying that “APPR is broken” isn’t very valuable as a statement by itself.