A350 Currently Unflyable Due to Repeated WASM Crashes and System Failures

[DeNeef94]

I am writing this with genuine frustration, because the A350 is an aircraft with enormous potential and clearly a lot of work and passion behind it. Unfortunately, in my case it has become effectively unflyable.

To rule out external causes, I use no overlays, keep the A350 up-to-date  at all times and systematically disabled all other add-ons in my Community folder step by step to eliminate possible conflicts. None of these measures resolved the issues described below.

1. WASM Crashes
   If I do not completely delete the WASM folder before every single flight, I experience random WASM crashes in virtually any phase of flight. Most frequently, this occurs while entering arrival and approach data into the MCDU. The crashes are unpredictable and make normal operation impossible.

2. Autopilot and Cockpit System Failures (without WASM crash)
   In addition to the WASM-related issues, I regularly encounter situations where autopilot and other cockpit systems simply stop functioning without any visible crash. The aircraft starts to deviate from its flight path and becomes uncontrollable. At that point, the flight cannot be continued in a meaningful way.

3. Autoland Touchdown Rate
   The autoland behavior appears rather firm, typically around 350 ft/min. I am not a real-world pilot, so this is only a subjective observation, but the touchdowns feel noticeably hard compared to what would be expected from a long-haul aircraft of this class.

Due to the frequency of especially the first two issues, I have temporarily uninstalled the aircraft. This is disappointing, as I truly want to enjoy and use this product.

This post is not meant as an attack on the developers or the aircraft itself. On the contrary, it is precisely because of the A350’s potential that these issues are so frustrating. I would greatly appreciate any guidance, troubleshooting steps, or clarification regarding known issues and upcoming fixes.

Thank you for your work and for taking the time to look into this.


PC Specs:
CPU: Intel i9-14900K

GPU: RTX 4090

RAM: 64 Gb

OS: Windows 11

[IniJamir]

Hello,

I understand the frustrations had with the aircraft, between WASMs which I have seen now plenty of since I started as well as encountering the freeze you detailed which is sort of a "ghost WASM", we believe we know what is causing the latter issue as well as the WASM regarding inputting Arrivals/Approaches and changing runways. We are seeing good results regarding this specific WASM crash and hope the results we see internally will reflect in broad-spectrum when the update does make it way to the public.

No worries, this isn't seen as an attack and as of current the best one can do is clear the WASM folder after any crashes.

Thank you for both your patience and understanding.

[DeNeef94]

Wow! That was quick! Thank you for the detailed response and for giving some perspective. As soon as the update drops, I will give the 350 another shot.

Best regards

[fukai]

Look forward to the update

 

[Bart99]

I am not even able to start a flight, most of the flights the plane spawns direct with a crash. 

[Transair]

Had my first WASM crash last night for ages after being airborne 2 1/2 hrs in A359 SQ, Inibuilds livery, while inputting Transition point into FMS after STAR/RWY…….sorry no files to attach…..

Each of my WASM crashes has occurred during data entry into the FMS if that’s of any use to you..

[C. Schaffhausen]

Ref the 2nd issue from OP, I have similar issues with the A340. I believe the root cause is the same here. I've tested 2 flights with the following settings and had no sim freeze and flight path deviation.

1. In-sim navdata used

2. Disable auto import step climb

3. Disable auto step climb

4. Not entering any step climb in the FMS, only by selecting level with FCU then Alt push.

With any of the above on I have sim freeze and flight path deviation. Hopefully that helps the team to track down the issue.

Edited March 6 by C. Schaffhausen

[klusik]

On 2/25/2026 at 5:35 PM, DeNeef94 said:

Wow! That was quick! Thank you for the detailed response and for giving some perspective. As soon as the update drops, I will give the 350 another shot.

Best regards

Thank you for this, I just got a crash after 10 hours of flight. I am a bit frustrated. This helped me to look at the bright side again. Thank you.

[klusik]

Another crash...

[sirupflex]

@IniJamir Do I understand correctly that V1.2.3 solved (at least part) of the MCDU-entry triggered crashes, which is good, but did not yet address that "ghost WASM" issue where some cockpit modules silently freeze and the plane cannot be controlled any more?

Just curious to understand, because that "ghost WASM" issue is the big one preventing me to use the A350 for months. Will try again once a reliable fix for this has been released. Please clearly communicate the fix once available, I think a lot of people are looking forward to that fix. Thank you.

[IniJamir]

8 hours ago, sirupflex said:

@IniJamir Do I understand correctly that V1.2.3 solved (at least part) of the MCDU-entry triggered crashes, which is good, but did not yet address that "ghost WASM" issue where some cockpit modules silently freeze and the plane cannot be controlled any more?

Just curious to understand, because that "ghost WASM" issue is the big one preventing me to use the A350 for months. Will try again once a reliable fix for this has been released. Please clearly communicate the fix once available, I think a lot of people are looking forward to that fix. Thank you.

The Ghost WASM one is tricky, I know it is still being investigated as of current. I've had it occur for me once in the last two A340 updates and that's been it since launch (my heart lies in this plane lol so I do fly it a lot compared to 350), it's harder than a traditional WASM cause it doesn't throw any of the usual indicators of WASM errors. Hope this helps.

[manfredfunco]

That's great to hear you may have an upcoming fix for the "Ghost WASM" issue! I have a long-haul flight I've stubbornly attempted many, many times (KDTW - RKSI, without FSUIPC, using SmartCARS), which always end up in this state (plane keeps moving, but avionics are frozen, can't control the plane). I usually use a lot of addons but attempted a barebones flight overnight with just FSUIPC + A Pilot Life. I hear FSUIPC alone may cause the issue but needed it for tracking the last particular test flight (KORD to LIRF). 

These are the addons/apps that I regularly use but completely disabled / did not open / removed from community folder for the A350 tests. The last flight was just FSUIPC + APL and still resulted in the Ghost WASM issue.

• Clear WASM cache before flight - after installing v1.2.4
• Making sure Sayintentions/Hoppie IDs are not entered in the OIS.
• Used the No Cabin Version
• Used Delta Livery from the iniBuilds app. Removed all other liveries/addons from community folder
• Verified during the entire flight, my GPU (RTX 3080, 10GB) VRAM was < 70%
• Process Lasso
• Chaseplane 2024
• Flow
• SayIntentions.ai
• Navigraph Simlink (known culprit)
• Spad.next
• Moza Cockpit (for MTQ, AB9)
• FSFO 6
• Disabled Photogrammetry, All traffic.
• Used MSFS Sim Real Time/Weather
• Windows Apps
  • Disabled all Bitdefender protections, other than the Firewall
  • Made sure Powertoys is not running
  • Killed unnecessary Windows Services
  • Kill all other background apps - Browsers, Discord, etc.

Let me know if any more information (or tests) from me could help you troubleshoot the Ghost WASM issue. When I experience the freeze, I check the console, Simconnect Inspector and don't see any relevant WASM errors or "noisy" simconnect apps. I was considering writing a program next to check for the ghost WASM issue (checking if certain Simvars are no longer changing) and automate pausing the sim, send me a notification. Then I could restart the flight w/ Autosave to resume. Sounds like I can just wait for the update! Thanks!

 

 

Edited March 19 by manfredfunco

[Azlog]

Just had a ghost WASM crash in the A350-1000 (version 1.2.4) around 2 hours into a flight from Boston to Heathrow on Xbox series X 😞

Edited March 27 by Azlog

[JohhnyWing]

Wasm crash on A350 while entering a transition for approach into mcdu during preflight stage. It happened two times in a row. A350-1000 at HKJK(Inibuilds)

[Yunchan2295]

So, basically this plane is COMPLEATELY UNFLYABLE. WHAT. A. SHAME.

[Yunchan2295]

C'MON, iniBuilds! After a year of release, this problem is from bad to worse. PMDG and other WASM-heavy aircrafts doesn't worse like this situation... And mostly this is addon-related bugs.

Edited Tuesday at 06:45 AM by Yunchan2295

[CranwellDirector]

A newbie here. I attempted a LHR-PHL yesterday but got, what I presume is, a ghost WASM crash about 6hrs in. Aircraft seemingly flying but uncontrolable, key indiction, aircraft drifting off-track on the PFD. Was using the FSUIPC + Merlin on a BAV flight if that makes any difference. Really like this aircraft - looking fwd to a resolution. Was on the v1.2.4 update on PC.

[DeNeef94]

Unfortunately I have to pick up the conversation again after the latest update of the A350. Just now had a WASM crash (not ghost WASM) while entering STAR and arrival information. In other words a crash that was supposedly fixed with the last update. @iniBuilds I know tagging like this is frowned upon, but having an addon that costs close to 90€ well released for over a year now still struggeling with hard crashes like these is very frustrating. I appreciate everything you all are developing and have huge respect for that kind of work. But - just speaking subjectively and only for me - you really need to take care of this sustainably. No one want's churning customers. Sadly and honestly,  given the current state of the product, I'd think twice before purchasing another plane off the market. I hope you can fix these issues and make the aircraft that we all love and admire so much enjoyable again.

Best regards 

Edited Tuesday at 06:03 PM by DeNeef94

[Mathiaspilot123]

Have not flown the a350 for months now, and the last time I used it I didnt encounter any WASM crashes and it felt stable. Now however, not so much. Thought I'd try a long haul again, EKCH-RKSI. 2 hours before ETA I program in the expected STAR and APPR and bam! WASM crash... This is incredible... How could it posibly have gotten WORSE! Why would you make it more unstable?

Edited yesterday at 09:09 AM by Mathiaspilot123

[Thissapunyo]

Just had the same thing, tried to update the Via on my approach and instant WASM crash - still landed it at EGLL though