A32NX: non respect of settings

flight, the airplane no longer respects the speed and heading of the “managed” mode, we must return to the “selected” mode?

Yes, that’s one way to do it, especially when you get a waypoint skip bug on approach, where the aircraft just ignores the next waypoint and turn straight for the runway. That’s when you switch the Managed NAV mode to Selected heading mode, and manually trace the original flight path.

Or, you can still keep it on managed mode but use the DIR function in your MCDU to go to the previously selected waypoint, then it would restore the previous heading in managed NAV mode.

1 Like

This is not what I want to do.Let me explain: the anemometer is set to 300 kt, the altitude is 25000 f, the heading is determined by the SimBrief plan entered in the MCDU. Everything is in “managed” mode. The take-off is correct, the AP is then connected and the aircraft follows the path of the plan. Suddenly, after a few minutes, the aircraft deviated and the speed dropped to a certain level. The aircraft no longer follows the flight conditions decided upon on departure. We come back to piloting it according to the “selected” mode, acting on the heading manually at each change of direction according to the plane and by fixing the speed.
Is this a bug or a bad setting?

It’s difficult to know if you don’t share a screen recording of it happening. I can only imagine, based on your writing. But I can’t think of what’s causing the issue or to help you with the problem without an actual screen recording of it happening.

My only guess is, maybe you have AI Copilot taking control, or even you have some Assists settings set to on, AI Copilot control should be set to Off at all times, and Assists need to be Hard/True to Life. Basically turn off all assists.

You might also need to check on your Flight model, making sure it’s modern, and your Flight controls axis have at least 5%-10% Deadzone on them, to make sure your controls don’t conflict with the AutoPilot.

I send you three screen shots:

See these texts in your Upper ECAM (red arrows)… That’s already telling you something is wrong before taking off… It shows that you’re not Configured for take off. I bet there’s a warning sound that you can hear when this appears.

The one pointed by the blue arrow also looks wrong, it looks like you’re in Reverse thrust.

Will you tell me if you type a speed on the dashboard anemometer or not, when you prepare for the flight and if you check “managed” or “selected” and if you leave the white point next to it?

am sending you one photo. Just after “take off” is with the settings for flight LFPG-LGAV, no problem; just before the usual problem . Nothing can be seen on the board, only the AP is off and an increase in speed and the warning sounding . I stopped the flight.

Sorry, I made a mistake and the photo was not sent. I will do it again tomorrow and if the phenomenon occurs again, I will take pictures. Tonight I have it over my head.

As promised, I will give you this screenshot after take off from the A32NX from Nice LFPG to Athens LGAV. The speed is stuck at 180. It should go up to 300.

The speed has just unlocked.

I am attaching again another screen shot showing the anemometer; the speed is well over the limit.

Excuse me I have forgotten to send the screen shot.

Capture.PNG

You are in manual thrust and in V/S, hence it’s your responsibility to keep the speed under control!

The AP has just disconnected and the aircraft is no longer following the plan. Screen shot attached.

Of course it disconnected automatically. You are well above Vmo!

That is NOT an anemometer. Please stop using the wrong terms.

didnt i see somewhere a vid of how to properly do it?
to me the op seems a bit chaotic.

1 Like

Excuse me, but in French, the device that measures speed is an anemometer, even if it measures speed. Anyway, I’m not asking you to take language lessons.