This is indeed a very strange bug for you guys.
Nevertheless, it cannot be stressed enough, that you all check your Hardware controllers for ANY key binds that may conflict. Important ! Some binds are set AUTOMATICALLY for your attached hardware inside MSFS. HC Alpha and Bravos especially.
Since i am using SPAD.Next, I've cleared out ANY of them and kept only the Nosewheel steering assignment, since that is common for most of my aircraft.
NEXT: Whenever i update an aircraft or 3rd party tool, i am also clearing the "m-files" which are compiled by some of them.
They will be (automatically) recompiled on the next load of the addon. No harm is done by deleting these files.!
You can find them here for the respective addon:
C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages
DO NOT TOUCH the "work" folder, unless you want to loose your settings for that addon and start setting up from scratch.
Important !: Once you have loaded into the addon, bail out of MSFS again and reload for your flight - DONE.
It has become a habit and so far i have not had any issues. Especially now with the ini A300.
Next thing i noticed: If you leave MSFS via //42 FLOW Pro - EXIT, the A300 (only one i noticed that) may CTD.
If MSFS is exited the normal way via its Menus - no CTD.
Maybe this helps ...
Oliver