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.

Inibuilds A300 Master WASM Crash Thread v1.0.8 FS24

Featured Replies

  • 2 weeks later...
On 6/1/2026 at 6:46 PM, Cotton_EJ said:

Hi, I want to add that I don't seem to get this issue when not using Navigraph and instea the Microsoft AIRACS. I haven't been flying that much lately, so I might have just been lucky. But after uninstalling Navigraph AIRAC I have had no WASM crashes, so far.

Again to add an update, at least to the STAR WASM crash;

Been flying quite a lot recently on default MSFS Airacs, some shorter hauls, some longer hauls. Adding STAR and changing them has not been an issue after uninstalling Navigraph Airacs.

While not a fix, it seems to be a temporary solution. For those that still struggles and want to fly this aircraft, I suggest trying this.

Ok, I'll give it a shot.

How do you do it? Just change the source in the EFB? I don't want to uninstall Navigraph AIRACs in general...

On 6/21/2026 at 11:35 PM, theglideslope said:

Ok, I'll give it a shot.

How do you do it? Just change the source in the EFB? I don't want to uninstall Navigraph AIRACs in general...

I believe you have to uninstall the Navigraph AIRACs. Note that Default MSFS AIRRACs do update, so should be no difference

I think I found a way without uninstalling. I just reset the Navigraph credentials for the plane and made a test flight. Seems to have worked. The only downside with that is that I have to use the LIDO charts and the enroute maps don't work. So far, no crash, but let's not be too optimistic.

This is definitely just a workaround. This is not a fix. What is the hold up for a fix in this plane?

Honestly this is ongoing for too long. At some point, however, it's not even about the time it's taking for you to realise the above. It's the silence around the users complaining about the lack of a fix. Please understand this frustration as a desire to get our money worth. I purchased this plane, I wasn't given when it was launched, made a video/stream and forgot about it. I was invested in using this plane for my livestreams. I still am... as long as you release that fix...

Edited by theglideslope

  • Staff

Hello. We are working on a code update to release soon (actually soon, not "dev speak", you'll get it in 6 months, soon)
Good news is we have been trying to reproduce the reported WASM crashes with approaches with little success. We speculate the main issue causing these is outdated/bad nav data. In over 40 attempts in the last 24 hours we've had exactly 0 crashes when spamming approaches including all these ones called out here with the latest sim default and Navigraph replacement datasets. While I wont say it's outright fixed, I will say the results are promising.

12 minutes ago, IniSteve said:

Hello. We are working on a code update to release soon (actually soon, not "dev speak", you'll get it in 6 months, soon)
Good news is we have been trying to reproduce the reported WASM crashes with approaches with little success. We speculate the main issue causing these is outdated/bad nav data. In over 40 attempts in the last 24 hours we've had exactly 0 crashes when spamming approaches including all these ones called out here with the latest sim default and Navigraph replacement datasets. While I wont say it's outright fixed, I will say the results are promising.

Those are awesome news. Why not release that fix you have and we can help with testing?

Thanks in advance.

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.