Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Inoperable System: AP1 & AP2

Featured Replies

My first flight after purchasing the A340 on 10/7/25 was from KMDT to KCLT.  The aircraft and all it's systems worked perfectly.  Since then, I've tried flying out of nearly 200 airports worldwide with the same result: "Inoperable Systems - AP1 & AP2."  After taking off, I try to engage the autopilot, and it engages momentarily before disconnecting and crashing the aircraft directly into the ground.  Upon restarting the flight, the AP is not available at all.

So, I restart the sim, try flying out of KMDT, and the aircraft works perfectly.

Why am I only able to fly out of KMDT with a flawless A340 but completely disfunctional everywhere else in the world?

Hello,

Sounds very odd. Can you double check that no failures or assistance options are enabled via the MSFS settings?

Thank you 

Eddie
Community Manager 
iniBuilds Ltd. | inibuilds.com

  • Author

Hey cinnamon21: How did you resolve that issue?  I have the same issue.

 

Original report: "When I start the aircraft in 'cold+dark', or 'on APU', I am unable to get the INOP SYS 'AP 1+2, CAT 2' message to go away."

  • Author
On 10/15/2025 at 6:42 AM, Eddie said:

Hello,

Sounds very odd. Can you double check that no failures or assistance options are enabled via the MSFS settings?

Thank you 

I have double checked and no failures or assistance options are enabled.  Every flight I try from KMDT is a successful flight, whether I start "cold and dark" or at a runway ready for departure.  Attempted flights from KSEA, KSFO, KLAX, KSAN, KORD, KIND, KMCO, KCLT, EHAM (to name a few of the hundreds I have tried) have resulted in failed attempts.  On these failed attempts, either the autopilot does not engage or it does engage and sends me crashing into the ground.  i have no idea what I'm doing wrong at other airports...

  • Author
5 hours ago, Eddie said:

Thank you for the follow-up. Are you able to record us a quick video showing what you're describing? 

Hello Eddie.  Thanks for responding to my messages.  I may have fixed my issue with Autopilot not engaging and disengaging as soon as it engages after take off from any airport other than KMDT. 

I followed these three steps to fix my issue.  First, I "repaired" MSFS 2024.  Then, I deleted the "rollingcache.ccc" file and increased the default size of 16gb to 32gb.  Finally, I followed the A340 Manual to a "T," and that included setting the TRIM and pushing the "AP" button on the dashboard instead of the "Y" button on my HOTAS One.

So far, I have successfully departed KSEA, KSFO, KLAX, and KSAN with no issues.

Thanks again for responding to my initial and follow-up messages.

sgb478.

Create an account or sign in to comment

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.