`Brief description of the issue:
Since recent update out of the 4 times I have flown this aircraft, on 2 occasions after take off and getting to cruising altitude, the aircraft has a mind of its own all of a sudden and commences to roll side to side building up momentum to the degree where its almost upside down and then it dives and crashes to the ground. It occurs during normal flight whilst I have auto pilot engaged. It happen just out of the blue.
Does anyone else have this same issue and is there a way to resolve it.
Hi there,
was your autopilot on? Or has it turned off?
Yesterday I was flying and at cruising altitude, it switched itself off and could no longer be turned on.
Then I took a break (Esc) and after a minute I went back to the flight and I was able to switch the autopilot on again. (Strange)
PS. At another post people report about autopilot problems (Issues with autopilot)
I always use the latest Developer Mode (is loaded before MSFS starts).
The frame rate at 35-40 (Glass Cockpit) is not optimal but acceptable and sufficient for me.
I fly live without time copression.
Only one thing struck me, it happened during a North Atlantic overflight (Shottland-Iceland) shortly after leaving the Shottic airspace between AKIVO and 6112N.
So I had to fly a large part of the flight manually (tried to switch on the autopilot 6 times).
At ASRUN everything worked again.
So far, I’ve never had any problems with overland flights
I will pay attention to it next time.
But when I had to fly manually yesterday, I didn’t notice that the angle of attack was too high. The flight speed was about 0.780 Mach and the cruising altitude was FL380 and later FL360.
Even when going down (to FL360) with VS at -1500, I couldn’t turn the autopilot back on.
As I said, I’ll pay attention to it next time and thanks for the suggestion
The AP of the FBW A320 Dev version recently demonstrated a few problems in my case too.
Yesterday after taking off from Tenerife Sur, the SID although properly set before takeoff was deleted in part, the next waypoint in white on the ND was different (second WP) than the one on the MCDU (which was the first WP), I let the flight proceed without change to see what would happen. The flight leveled off at its FL350 correctly, still tracking the second WP (indicated on the ND) before reaching the first waypoint (MCDU white), the AP disconnected, the flight continued on a heading that could not be corrected, and the plane climbed slowly well beyond its FL. No way to reconnect the AP or correct any of these parameters, I had to abort the flight. That never happened to me before with the same plane.
It would be helpful if you make a screenshot when this situation again happens. You can also provide me the FDR file of that flight than I can take a more deep look what happened. You can additionally press the DFDR button to mark an event.
I just checked the code again and the AP disconnects if:
sidestick input > 50% (after calibration)
rudder input > 40% (after calibration)
any protection active (high speed protection, high angle of attack protection)
Pitch is > 25°
Pitch is < -13°
Bank angle is > 45°
on ground and go around is initiated
ROLL OUT mode is disengaged on ground (in case of Autoland)
As an additional hint keep in mind that the dev version right now still uses the default flight plan manager with all its glory of issues. I encourage you to try experimental version.
Today I would like to start another North Atlantic flight, if this happens again I will mark the event with the DFDR button.
Thank you for the tip. After this flight with the developer version, I’ll try the experimental version.