Fix an MSFS 2024 crash when loading Free Flight. Isolate aircraft and scenery add-ons, clear cache, test streaming and repair game files.
Microsoft Flight Simulator 2024 usually crashes while loading Free Flight because an aircraft, livery, airport or avionics add-on fails as the session initialises; damaged rolling or streamed world data is another common cause. Test a stock aircraft at a stock airport with add-ons disabled, then clear the rolling cache and repair the installation.
What causes MSFS 2024 to crash at the flight loading screen?
The flight loading screen is where MSFS 2024 assembles the selected aircraft, airport, local scenery, weather and streamed world data. The main menu can therefore work perfectly even when one of those components crashes the simulator.
- Aircraft or livery conflicts: an outdated livery, missing dependency, duplicate installation or incompatible aircraft package may fail only when that aircraft is loaded.
- Avionics and WASM modules: complex aircraft initialise additional systems shortly before the cockpit appears. If that is the trigger, follow our focused steps for isolating an aircraft or WASM module crash.
- Airport and scenery conflicts: two packages covering the same airport, an old scenery package or nearby object libraries can crash every flight started at one location.
- Damaged world data or rolling cache: stale terrain and photogrammetry data can produce a late loading-screen crash, particularly when the problem follows a location rather than an aircraft.
- Memory, graphics driver or hardware instability: loading a flight creates a sharp increase in RAM, VRAM and GPU use. Unstable overclocks, disabled or undersized paging files, overlays and driver faults may surface at this point.
- Damaged simulator content: an interrupted update or corrupt package can make even default aircraft and airports fail.
How can I tell what is causing the crash?
Change one part of the flight at a time; the pattern usually identifies the faulty component faster than reinstalling the entire simulator.
| Test result | Likely cause | Next action |
|---|---|---|
| A default aircraft and default airport load | Third-party aircraft, livery or scenery | Restore add-ons in small groups until the crash returns |
| One aircraft crashes at every airport | Aircraft, livery, dependency or avionics module | Use its default livery and reinstall only that package |
| Every aircraft crashes at one airport | Airport scenery, nearby scenery or cached world data | Disable scenery covering that area and clear the rolling cache |
| The flight loads with online data disabled | Streaming, cached data or network path | Reset the cache, then re-enable online features individually |
| Default content crashes everywhere | Core files, driver, memory or hardware stability | Repair the installation and test the PC at standard clock speeds |
How do I fix a Free Flight loading crash?
Start with a clean, repeatable flight and add complexity only after that baseline loads successfully.
- Finish all updates and restart. Check the platform and simulator content library for unfinished updates, close MSFS completely, and restart the PC or console. A suspended console session is not the same as a fresh launch.
- Disable third-party content. On PC, move packages out of the
Communityfolder or temporarily rename that folder. Use Safe Mode if MSFS offers it after a crash. A blank Community folder does not disable Marketplace or other library content, so deactivate suspect packages there as well. On Xbox Series X|S and PlayStation 5, remove or disable optional add-on content through the simulator's content-management screens. - Create a stock test flight. Select an aircraft supplied with the simulator, its default livery and an ordinary airport not replaced by an add-on. Use preset weather and temporarily turn off live traffic and multiplayer. Avoid testing the same aircraft and airport combination that already failed.
- Change one variable per test. Try the same aircraft at another airport, then another aircraft at the original airport. This separates an aircraft problem from an airport or scenery problem.
- Reset the rolling cache. Delete it using the simulator's own data settings, restart MSFS and either recreate it or leave it disabled for the next test. Our rolling-cache reset instructions cover the available choices and when disabling it is useful.
- Test without streamed world features. Temporarily disable online world data and photogrammetry. If the flight now loads, the aircraft is probably not the cause; work through the world-data and scenery-streaming fixes before turning each online feature back on.
- Check PC stability. Install a stable graphics driver, disable overlays and hardware-monitoring hooks, return CPU, GPU and memory overclocks to standard settings, and allow Windows to manage the paging file. Confirm that both the system drive and the simulator's package drive have free space. If memory pressure is evident, reduce texture resolution and Terrain Level of Detail for the test.
- Repair simulator files. Use the platform's verify or repair facility where available. On a console, perform a full shutdown and power cycle before reinstalling any suspect optional package.
Why does only one aircraft crash while loading?
If other aircraft load at the same airport, the failing aircraft, its livery or one of its dependencies is responsible. Test its default livery first, remove duplicate copies, and confirm that every required base package is installed and enabled.
A mistake we see constantly is removing the aircraft but leaving an old livery or compatibility package active. Those packages can still reference files or systems that changed during an update. Restore only the base aircraft, test it, and then add liveries back individually.
If the loading bar completes and the crash occurs as the cockpit or avionics wake up, concentrate on aircraft systems and WASM modules rather than scenery. If it fails before the cockpit appears only at one location, test the same aircraft at a simple default airport before changing the aircraft installation.
Should I reinstall Microsoft Flight Simulator 2024?
Reinstallation should be the last step, not the first. It will not necessarily remove Community packages, repair a third-party aircraft or solve a streaming-service problem, and restoring every add-on immediately can reproduce the same crash.
Reinstall only if default aircraft fail at multiple default airports with third-party content disabled, the cache has been reset and the platform repair has found no usable fix. Before doing so, work through our broader MSFS crash checks for drivers, memory and hardware stability. Do not delete cloud saves or profiles as an early troubleshooting step, because that can remove progress and settings without touching the actual faulty package.