Default A320neo altitude error in autopilot

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

no

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

A320neo

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

Last

Brief description of the issue:

Correct autopilot altitude, correct qnh result 300ft above the desired altitude, randomly append on the same route one flight is ok, next one wrong

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Simpli insert altitude in autopilot and apply

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

Last


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Yesterday for no apparent reason default a320 start randomly to stop follow correct auto pilot setting. Correct qnh, correct autopilot altitude, correct engine trust, autopilot set the altitude stop climb 300ft over designed one. For example I put fl300 in auto pilot, FL change or v/s mode, aircraft start climbing, correct qnh. In PFD I see the blue indicator set to 30000 ft but autopilot continue climb to 30300 so ATC constantly said I’m 300ft above. I must set FL to 297 to stay at 300. This append randomly. One fly is ok, one not. Everything is setting right. When append I found that turn off SEC 1 resolve the problem because when I engaging autopilot again, is now ok.

Hi @stefanozab , I moved your topic to the User Support Hub Aircraft & Systems that is more appropriate to receive support from other users. Hopefully some will be able to provide guidance around that issue. If it is a proven bug that can be replicated we can always move back your report to the bug section.

1 Like

Just to make sure, the correct QNH at FLs is always 1013.2 / 29.92.

1 Like

every value of qnh i apply autopilot ignore it and stay at 300ft above

When this happens to me I just press “B” on the keyboard and the plane goes up or down to reach the right alt.

The altimeter is already set correctly and press b doing nothing :frowning:

I don’t see this problem following your procedure. Is there anything you are leaving out?

No, I simply had the problem from yesterday. Everything the same

Probably a conflict in your install somewhere

Could you start in safe mode and test again ?

FYI, it shouldn’t do that either. IRL the autopilot uses the QNH you have set.
E.g. if you set 30000ft in the altitude window, the AP should fly at 30000ft, regardless of set QNH.

Same problem in safe mode. I also find that the plane share airbus system also had problems. For example Latin vfr product now had same issue

Well,from what I’ve understood at FL300 you have the standard 29.92 and this shouldn’t cause the problem highlighted by the OP. However if you are at,let’s say,
at 5000fts climbing to 10000fts in accordance to the Atc request, you should also update the qnh when the Atc tell you about this change.If you forget to do that (it happens to me sometime) you reach 10000fts but these are not real…after a few minutes the Atc urge you to reach the right alt. Then I realize that I didn’t update the pressure communicated by he Atc so I press “B” and update the pressure…the plane moves up or down and reach the correct alt making the Atc happy.I press “B” because sometimes is difficult to read all the ATC messages back and retrace the ones with the pressure data.Doing this way works for me.The OP might have a different problem.

no, the problem is that at any altitude, qnh, with or without atc ifr vfr everithing the autopilot go wrong so press b shortcut for correct setting altitude here doesnt work

I don’t know how ATC in MSFS handles this, but IRL ATC doesn’t issue a QNH during climb. It’s your responsibility to set standard QNH when climbing through the transition level.

Good to know,thanks. I have no IRL piloting experience so I can only rely on the “simulations” offered by the sim and try to comply with the sim Atc requests to mock the IRL flying …LOL

Stupid question, the a320 avionics is server dependent?

This bug is not about ATC. It’s totally irrelevant what QNH you set. If you ask the autopilot to bring you to 20000 ft it should bring you to 20000 ft (on the PFD), not 20300 ft. What your actual physical altitude is (which one?) is beyond the point.