Hi, I have a big issue with the a330 aircraft. Whenever I am doing a flight at some point (seemingly random) the autopilot disconnects, so does the autothrottle and sometimes it banks hard left. Toga LK is then shown on the pfd. Once i have the aircraft back under control I have to set the flight directors and put back on the managed speed heading and altitude. On a long haul flight this happens about 5 times. I have all assists off ans the turbulence on the low setting. The flight model is on modern. Any help would be appreciated.

 

Thanks,

Jack

I have similar problem, except on Xbox with A320 and mostly on short final. I’m suspecting either a problem with the new airac cycle (no problems prior to last update) and/or some conflict with addon airport data and sim software. Other possibilities are sudden insert of weather data that throws the plane out of AP or drift on your flight controller that suddenly registers beyond a critical point and might require some increase in dead zone. Still working the problem at this end. 

Just had another issue on the same flight, both engines cut off and only basic power remaining no matter how hard i tried to relight both engines nothing happened. After spending around 7 and a half hours for nothing can someone from the team please take a look into this. The previous post i made contains issues that occured during the very same flight!

Hi @Jorrallcorrall

We're not able to reproduce such issues (flight control or engines cut off) on long or short segments across the A330 fleet (or other default airbus aircraft) internally or through any of our testers. So the issue is likely client side, please take a look at the suggestions below to see if you can find the cause:

On 1/5/2025 at 3:44 AM, Jorrallcorrall said:

Whenever I am doing a flight at some point (seemingly random) the autopilot disconnects, so does the autothrottle and sometimes it banks hard left.

Sorry you're experiencing this, please also take screenshots of when this happens (A screenshot that shows PFD/ND/FCU in clear view + a screenshot of your pedestal (MCDU till rudder trim) + a screenshot of your overhead panel), so we can see if there are any clues as to why this may be happening.

The AP/AT disconnection is usually caused by control inputs, which could be caused by conflicting keybinds from any of your connected devices. These can include primary flight controls (axis/buttons for Aileron/Elevator/Rudder) and trim for those controls. For the throttles these keybinds could also be nudging the them out of the relevant detents, and thereby leading to AT disconnection.

The banking left is indicative of inputs on aileron or rudder (or their respective trim). Alot of these are assigned to common keys (e.g. Enter for RUDDER YAW RIGHT) on the default profiles for keyboard. So it is possible these are being inadvertently registered by the sim as you're using your keyboard outside of flight sim as well.

On 1/5/2025 at 3:44 AM, Jorrallcorrall said:

Toga LK is then shown on the pfd. Once i have the aircraft back under control I have to set the flight directors and put back on the managed speed heading and altitude. On a long haul flight this happens about 5 times.

TOGA LK will usually engage when aircraft has entered a low speed regime to prevent stall (ALPHA FLOOR PROTECTION), so that is just the result of an AT/AP disconnect situation leading to a degradation of your speed.

On 1/5/2025 at 5:21 AM, Jorrallcorrall said:

Just had another issue on the same flight, both engines cut off and only basic power remaining no matter how hard i tried to relight both engines nothing happened.

This also seems a keybind issue related to MIXTURE (axis or set rich/lean) or CONDITION. Alot of users who have reported such issues have resolved after ensuring any bindings related to these are unassigned from all connected devices, except for the switches/axis where you want it to be assigned. 

You should also be wary of the control profiles, as these can be assigned individually per aircraft now so you want to ensure the correct ones are assigned and active. Some users have also reported that even though a profile was showing active on UI, it wasn't the case until the changed to default profile, and then back to their custom profile and hit save after.

The last thing (particularly PC related) is that if your PC has power saving enabled on USB ports. It is possible that after a few hours of non-usage, it enters a power-saving state, which causes device to reconnect.

MSFS2024 loads the "default" controller profile initially when a device is connected, before reverting to custom profiles if the device is recognized again. So its possible that is what is happening in these instances.

So spend some time looking into these to see if you can resolve the issues.

Thanks!

I have the same issue specifically with the A330. The auto pilot disconnects and the plane begins to bank to the left. This only occurs on flights longer than 6 hours. Flights shorter than 6 hours do not have this issue. 

@richboy2307 Had the exact same issue as @Jorrallcorrall on my first long haul flight from EDDF to RJAA. Woke up in the morning to my AP Disconnected, Full TOGA and my Plane banking to the left. From the steps listed above i already had everything set up correctly, so intercepting keybinds should not have been the issue. Only thing i did now was adjust my power saving settings for my usb ports although i`m not sure that was the cause. Maybe someone else here was able to find a solution ?

Same issue... after 6h perfect flight without touching anything, the autopilot suddenly disconnects

Edited January 18, 20251 yr by Argonox

Hi @CptFerox @Argonox

Most users have made changes to the controller profiles, having unbound unnecessary controls from keyboard/mouse and other connected devices so we recommend the same. As a last resort, you may also try a sim re-install, especially if the initial sim install was within first few weeks when server issues were prevalent as it is possible some core files were improperly installed.

Currently we do not have any other suggestions other than those above at this time.

As also mentioned on the previous post, currently we have not seen any issues aircraft-code wise that would cause AP disconnection issues, nor have we been able to reproduce this on our end (having done multiple "AFK" flights, longer than 6h as well).

Thanks!

This keeps happening as of 20th Feb. 
I've had the FD disconnect about 3 times during my flight today. 
As recommended, Ive unbounded all the keyboard controls, including flight control surfaces bindings.

Please look into this. 

I hope this doesn't happen to the a350 as well.🙏

It happens to the 350 as well, no extra binds or anything ini said, simply decides mid flight to go crazy

I can confirm the issue, and I can't imagine that it's caused by any control bindings. The aircraft behaved this way for me at night.

I took off, engaged the autopilot, and went to bed. During the night, I heard the sound of the autopilot disconnecting, and the aircraft started turning left.

I've experienced this on other flights as well, even though I didn’t make any inputs. I even monitored my joystick axes, and there was no movement. Yet, the same issue kept occurring—AP disconnects, followed by a nice left turn.

After one landing, while taxiing to the gate, I noticed that the left wing’s flaps were still up, even though I had only been steering with the rudder pedals.

It's the random extreme wind shift during cruise that causes the AP to go on the fritz.

I was at .82 and the wind shift hit me to .99 and that was it. No more AP or AT.

You might get lucky no extreme wind shift during cruies. I had a nice 9h flight from SAEZ to KMIA no problem, even with time acceleration.

I experienced it few minutes ago. Flight is OCN80/EDDM-KMCO. MCDU - fine, ENG startup - fine, taxiing - fine, take-off - fine, climbing - fine etc. The aircraft is cruising and following the flight plan, heading to the USA. BUT above the UK an AP just disconnects randomly buy itself (I don't know why, because I even turned OFF turbulence at all few months ago and also OFF "crash simulating"), I "escaped" the crash of my flight and an aircraft, but in a few minutes (maybe 20) the situation repeated again and my aircraft crashed due to overloading. The MSFS24 reload that all automatically to my last position but the aircraft continued to fly straight to the ground.
I really don't know what was changed to the aircraft, because I already did lots of flights on "ini" A330 (for example: EDDF-OMDB-EDDF, EDDF-KLAS-EDDF, UUEE-KJFK-UUEE, UUEE-KIAD-UUEE, UUEE-EDDM-UUEE etc.) and now I try "to flight" EDDM-KMCO and have a plan to make a return flight "KMCO-EDDM" using the same aircraft. A330 is my favorite, lovely aircraft especially with "RR Trent" engines. And I see that the development team is working on that aircraft, the team is trying to improve it, to make a fully simulated to the real one.
So please FIX that issue, it's very annoying and make the aircraft is UNUSABLE/UNFLYABLE (unfortunately).

Just the fragment of my situation in the video below. Screenshots are also presented: https://imgur.com/a/AKdplnl

 

iniBuilds,
It isn't really funny at all...
What is happening to your product?
After ~1 hour after that AP disconnecting issue (2 times) my aircraft even decided to stop working or working very strangely... just look at the video

 

Same issue with me and also read this topic please: 

 

 

Thank you, ini. My time wasted...
https://fly.volanta.app/flights/de57703a-2457-459b-9a33-662804d2dab6

This has happened to me too, didn’t happen in the a330 300 with GE and aer Lingus livery from Manchester to Barbados but it did happen using the a330 300 RR in a virgin livery!  Heathrow to Barbados.  It was as reported to, about 5 hrs into the flight.  I ended up quitting the flight it was too annoying!

The auto pilot turned itself off, flight directors turned off, lost cruise level in the fms…

kept happening after that 

 

It’s not the wind shift issue, this was a bug.  I’ve experienced that wind shift issue, causes oddities in any aircraft.

 

 

 

Edited February 16Feb 16 by grahamm

Hi, I'm just starting to fly the default Inibuilds A330 in MSFS 2024 on PC (MS Store). Having done a few very short flights just to learn how the systems work, I've found that on almost all longer flights, the Auto Pilot, and or the Flight Directors, will spontaneously disconnect, resulting in chaos and it's very difficult to regain control of the plane. 

The first instance, I was simply pausing (in MSFS hitting the keyboard ESC key) to change a Setting. When I resumed flight, it was in a dive. Not starting a dive, it had gone from steady cruise to full dive. The next instanct, also a couple of hours in to the flight, I had been in the exterior camera view looking around, and switching back to cockpit view, the FD and AP were both off and the plane was climbing to a stall. And so on.

Neither was caused by "wind" or "inputs". I fly plenty of long haul flights in the default Boeing, and PMDG Boeing, and other planes. This seems to be unique to the Inibuilds Airbus, unfortunately.

I think there might be multiple threads on this topic, sorry I'm not familiar with the Inibuilds Forum yet. 

I'm just starting to fly the default A330 fleet in MSFS 2024 on PC (MS Store) and after learning to fly them on some short flights, I'm finding in longer flights, after a couple of hours, the plane will spontaneously disconnect Auto Pilot and/or Flight Directors. Once was after pausing the sim (Esc key to go to Settings, and then Resume Flight), the next was returning to cockpit view from external view, the 3rd was just sitting there watching the scenery go by doing nothing. And NO it was not wind, or unintended "input". It just disconnects itself. I don't think I'm alone, and I hope it can be fixed. Maybe put some telemetry in the next update to record what triggers AP or FD disconnect when it happens?

On 1/9/2025 at 12:06 AM, CaptBmckay said:

I have the same issue specifically with the A330. The auto pilot disconnects and the plane begins to bank to the left. This only occurs on flights longer than 6 hours. Flights shorter than 6 hours do not have this issue. 

Same here, NOT A LIENT SIDE issue, all other aircraft working perfectly well.
ALMOST Anytime you do a long haul, the same thing happens and makes the aircraft UNUSABLE.
Looking for a substitute, maybe start flying 777 PMDG or a 787 Horizon trouble free.
Cheers INIBUILDS your support is weak.

On 4/3/2025 at 2:35 PM, iv_aviation said:

I experienced it few minutes ago. Flight is OCN80/EDDM-KMCO. MCDU - fine, ENG startup - fine, taxiing - fine, take-off - fine, climbing - fine etc. The aircraft is cruising and following the flight plan, heading to the USA. BUT above the UK an AP just disconnects randomly buy itself (I don't know why, because I even turned OFF turbulence at all few months ago and also OFF "crash simulating"), I "escaped" the crash of my flight and an aircraft, but in a few minutes (maybe 20) the situation repeated again and my aircraft crashed due to overloading. The MSFS24 reload that all automatically to my last position but the aircraft continued to fly straight to the ground.
I really don't know what was changed to the aircraft, because I already did lots of flights on "ini" A330 (for example: EDDF-OMDB-EDDF, EDDF-KLAS-EDDF, UUEE-KJFK-UUEE, UUEE-KIAD-UUEE, UUEE-EDDM-UUEE etc.) and now I try "to flight" EDDM-KMCO and have a plan to make a return flight "KMCO-EDDM" using the same aircraft. A330 is my favorite, lovely aircraft especially with "RR Trent" engines. And I see that the development team is working on that aircraft, the team is trying to improve it, to make a fully simulated to the real one.
So please FIX that issue, it's very annoying and make the aircraft is UNUSABLE/UNFLYABLE (unfortunately).

Just the fragment of my situation in the video below. Screenshots are also presented: https://imgur.com/a/AKdplnl

 

TOTTALY AGREE, almost all LONG HAUL flights this will happen, and it will climb crazy and put into a stall if not flown by hands.
On long hauls flights, the A330 is no longer a option as inbuilds IS NOT REALLY RESPONDING TO REQUESTS AND PROVIDING A SOLUTION.
Sad...

Hi, ultimately the aircraft is a Microsoft aircraft and as such any actionable requests will come from Microsoft and as such through their forums. That being said every so often I fly both A332/3 and do not find myself having these issues, not to say they don't occur, but that I can't reproduce the issue. Thank you
https://forums.flightsimulator.com/