Aircraft System Malfunction after GSX Pushback

[Worldworms]

Hello,

 

This happens after every pushback with GSX with the A340. Who can help me?

 

Edited October 12 by Worldworms

[jaimecar]

I found exactly the same problem a couple of flights. After pushback I recieve this mesage (aircraft system malfunction- landing gear malfunction) was unable to turn nose gear and unless 60 % of higher thrust is applied the plane does not move.

[mijoe74]

I had this problem too on my first flight from ESZH after pushback with the EFB-integrated GSX menu. 

On a second flight from KDEN gsx pushback didn‘t cause the malfunction - not 100% sure but maybe I used the native GSX menu on this one…

[Matthias0412]

Found out that in my case it only happens after a pushback with „pushback raise“ enabled in the Aircraft GSX settings.

[Eddie]

Hello,

Do any of you have any assistance options enabled via the MSFS settings? 

Thank you 🙂

[jaimecar]

Dear Eddie,

Not in my case. I have not assistance activated in the MSFS settings.

 

 

[mijoe74]

14 hours ago, Eddie said:

Do any of you have any assistance options enabled via the MSFS settings?

Me neither

[Eddie]

Are any failures enabled? (Also MSFS settings) 

[AERIV47]

I am have been experiencing this. This is really annoying. Is there a solution from anyone?

[AERIV47]

The error with the iniBuilds A340 and GSX is typically a "System Malfunction" or "Landing Gear Malfunction" that occurs after pushback. This is caused by a conflict between GSX's pushback sequence and the A340's custom system logic. The issue is a known bug, and iniBuilds and GSX developer FSDreamTeam have provided official workarounds. 

 

Workarounds for the GSX pushback malfunction

• Use the iniBuilds EFB settings: On the Electronic Flight Bag (EFB) in the cockpit, turn off the GSX integration and automatic services. When GSX is disconnected, you can use the default pushback feature or manually trigger GSX using its own menu.
• Force a towbar connection: Some users have reported that the issue is tied to the "tug that lifts the nose wheel." In the GSX editor, you can force the pushback to use a standard towbar instead.
• Release brakes correctly during pushback: For a smooth pushback, release the parking brakes only when GSX prompts you to do so. If you have wheel chocks engaged, ensure they are removed last.
• Tap your toe brakes after pushback: Some users have found that tapping the toe brake pedals (if you use them) as the tug detaches can reset the parking brake status and resolve the "stuck" condition.
• Use the GSX menu manually: If the EFB integration is causing issues, use the main GSX drop-down menu in the Microsoft Flight Simulator toolbar instead. This has been reported to work when the EFB's confirmation button fails. 
• Common GSX recognition problems
  If GSX does not recognize the iniBuilds A340 at all, you may encounter an error when loading fuel and payload via GSX. This is typically caused by a file encryption issue. To fix it: 
• Download the latest profile: Get the most recent A340 GSX profile from a trusted source like Flightsim.to.
• Manually install the profile: Place the unzipped profile folder in your GSX aircraft profile directory, located at C:\Users\(Your user)\AppData\Roaming\Virtuali\Airplanes.
• Restart GSX: Restart the Couatl engine to load the new profile. 
•  
  How to install a new GSX aircraft profile
• Navigate to your %AppData%\Roaming\Virtuali\GSX\MSFS folder.
• Delete any existing .ini files that correspond to the iniBuilds A340 to avoid conflicts.
• Copy the new, unzipped A340 profile folder into your %AppData%\Roaming\Virtuali\Airplanes folder.
• Restart the Couatl engine by reloading the GSX menu. Your aircraft should now be recognized correctly. 
•  

[AERIV47]

This is the source below:

https://www.google.com/search?q=gsx+inibuilds+a340+aircraft+malfunction+error&sca_esv=06680e941bb4b5b6&ei=35juaKyOL-GrhbIPxNzH8QI&ved=2ahUKEwiqqeatq6SQAxWHUEEAHfXlCEIQ0NsOegQIMBAA&uact=5&sclient=gws-wiz-serp&udm=50&fbs=AIIjpHxU7SXXniUZfeShr2fp4giZ1Y6MJ25_tmWITc7uy4KIeoJTKjrFjVxydQWqI2NcOha3O1YqG67F0QIhAOFN_ob1qe64vywgsVdIjTT28-5UDOHpI7IJbq8O03gE15S7dm98EqwwZSq_XfC3NU25aWo3wOrO5AWiSALHMUhGq3-9z6duanA7cRWfzjGDm8F1G_x_5_K8neK7XNDHezBaIFJQ7e803g&aep=10&ntc=1&mstk=AUtExfAll6buu_GY11UsC03uY1RV9sBCgAdpcb73itVnJZBAgMMsw6oyOYq4aowyhQdwce9Prrrxc1GgvX-nFw6BCWJZKTcQt1VL57SS0CciddIgUJIC0GQAZDSzMrRbOWu3GcxVtmDlBSIpt_XCTGROrQgD_-iyPmQ_Ab0&csuir=1

[mijoe74]

7 hours ago, Eddie said:

Are any failures enabled? (Also MSFS settings) 

No failures enabled.

But I can confirm the problem arises when pushed back by a lifting tug

After confirmation of good engine start and tug disconnect, the malfunction occurs

Parking break released, thrust over 40% -> no taxi, groundspeed 0

[mijoe74]

Same airport, same gate but parking position in GSX customized for towbar tug

no probs on disconnect

taxis fine on idle (or slightly above)

[jaimecar]

I can confirm, I´ve changed aircraft profile in the GSX menu to ensure towbar is used for pushback and the faiulure message dont appear anymore. Seems to be lifting-pushback related issue.

[Eddie]

Hello,

Please ensure your settings look like this:

 

If your settings look like this and you're still having the same issue; ensure you follow this profile guide (linked below). MSFS may be having a hard time reading the already included GSX-profile. 

 

[jaimecar]

I undestand this is not the  final solution. Crash, stress or engine stress damage settings should not be affected by the normal operations regardless the pushback is performed by lifting the aircraft or not in my opinion.

[Tomcat11]

On 10/16/2025 at 5:20 PM, Eddie said:

Hello,

Please ensure your settings look like this:

 

If your settings look like this and you're still having the same issue; ensure you follow this profile guide (linked below). MSFS may be having a hard time reading the already included GSX-profile. 

 

This can't be the final solution, sorry! I hope you will fix this issue in one of the next updates. Thanks!

[Farlis]

14 hours ago, Tomcat11 said:

This can't be the final solution, sorry!

Why not? The damage and crash detection within flightsim has always been spurious and is best set to off in all cases.

 

Just as an example of how spurious it is, when I did a bank angle protection test with the A350 and started to pull up the nose to prevent losing altitute my sim reset, telling me that I had just overstressed the aircraft. 

I very much doubt that a simple 67° bank will rip the wings off the A350 in real life. 😉

Edited yesterday at 10:40 AM by Farlis

[iniSteven]

22 hours ago, Tomcat11 said:

This can't be the final solution, sorry! I hope you will fix this issue in one of the next updates. Thanks!

The crash and stress damage in the base simulator is extremely simple, and often triggered by the sorts of workarounds devs use to accurately simulate complex aircraft. We are not the only developer who encourage you to turn off the base simulation damage as they only harm complex aircraft - as proven by the issues here 🙂

[Tomcat11]

23 hours ago, iniSteven said:

The crash and stress damage in the base simulator is extremely simple, and often triggered by the sorts of workarounds devs use to accurately simulate complex aircraft. We are not the only developer who encourage you to turn off the base simulation damage as they only harm complex aircraft - as proven by the issues here 🙂

Thank you very much for the clarification.👍