no repro WASM Crash Report - Entering APP with NO VIAS transition

[JRHorse]

Reporting a WASM crash on the iniBuilds A340 when inputting the arrival into the FMS.

Steps to reproduce
-Load plane at gate, power on, turn on APU
-Load flight plan in tablet then via FMS
-Enter Departure and Arrival procedure

While putting in the arrival procedure, select the runway, approach, arrival and arrival transition. WASM crash occurred when I clicked on "NO VIAS" in the ILS approach for runway 27C at KORD.

• Aircraft: A340 EIS 1 Passenger
• Simulator: FS2024
• Version: 1.0.7 Inimanager
• Navdata Method: Navigraph
• Specs: AMD Ryzen 7 7800X3D, 64 GB Ram, RTX 4070 Ti SUPER 16GB

The Autosave file was not available in the folder indicated in the post about making WASM reports. I am enclosing all other screenshots and the flight plan.

Not a good way to start off my first flight in the A340, but I hope this information helps.

Thanks,
Jose

KJFKKORD_PDF_1768609824.pdf

Edited January 17 by JRHorse
remove tag

[Blaster254]

Delete the WASM folder and let it rebuild 

[richboy2307]

Hi

On 1/17/2026 at 9:14 AM, JRHorse said:

Not a good way to start off my first flight in the A340, but I hope this information helps.

Sorry you experienced this, but appreciate the report! Hopefully your other flights have gone more successfully.

On 1/17/2026 at 9:14 AM, JRHorse said:

The Autosave file was not available in the folder indicated in the post about making WASM reports. I am enclosing all other screenshots and the flight plan.

The autosaves are only created if the option is enabled in the settings and engine is running. As you crashed before start, its likely why.

On 1/17/2026 at 9:14 AM, JRHorse said:

Steps to reproduce
-Load plane at gate, power on, turn on APU
-Load flight plan in tablet then via FMS
-Enter Departure and Arrival procedure

While putting in the arrival procedure, select the runway, approach, arrival and arrival transition. WASM crash occurred when I clicked on "NO VIAS" in the ILS approach for runway 27C at KORD.

Based on the screenshots, it looks like T7 Gate 4 (F4) at KJFK. We’ve tried spawning there ourselves. We also tested this multiple times on different PCs internally, but we haven't been able to reproduce the WASM crash with the information provided as yet. Attached is a video from one of our attempts.

We have also tried with variations such as
- No fuel & payload loaded
- IRS still in alignment
- IRS not aligned

It would be helpful if you notice anything we could try differently, or if you could provide a similar video showing the console window open at the moment the WASM crash occurs for you. This information is essential for us to try to reproduce the crash and work towards a solution.

Thanks!

 

[JRHorse]

4 hours ago, richboy2307 said:

Based on the screenshots, it looks like T7 Gate 4 (F4) at KJFK. We’ve tried spawning there ourselves. We also tested this multiple times on different PCs internally, but we haven't been able to reproduce the WASM crash with the information provided as yet. Attached is a video from one of our attempts.

Hi and thanks so much for your reply and video. I do need to make a correction, the navdata method for this was the in-sim nav, instead of navigraph.

Today I tried another flight from KJFK to KLAS, and there were no WASM crashes. Everything was pretty much as expected. Before this attempt I cleared the WASM folder, and after loading into the sim I changed to Navigraph and updated the data before switching on the electrical power.