Stop MSFS 2024 crashing on landing with targeted fixes for airport add-ons, rolling cache, aircraft modules, traffic, VRAM and drivers.
MSFS 2024 usually crashes on landing because the approach suddenly loads detailed airport scenery, traffic, streamed world data and aircraft systems at the same time. Fix it by isolating the aircraft and airport, removing add-ons, clearing the rolling cache, reducing memory-heavy settings, updating drivers and checking crash evidence for the failing module.
Why does MSFS 2024 crash during approach or landing?
A landing crash is usually a load or content failure exposed by the approach, not a problem with the act of landing itself. Detailed terminals, ground traffic, nearby aircraft, photogrammetry and complex avionics can all become active within the final few miles.
| Crash pattern | Likely cause | Best first test |
|---|---|---|
| Only at one airport | Airport add-on, duplicated scenery or streamed world data | Remove that airport package and repeat the arrival |
| Only with one aircraft | Aircraft package, livery, avionics or WASM module | Fly the same approach in a stock aircraft |
| At the exact moment of touchdown | Weight-on-wheels event, external utility, mission script or aircraft damage logic | Close external tools and land the stock aircraft elsewhere |
| Only after a long flight | RAM or VRAM pressure, accumulated traffic or aircraft-state problem | Repeat the arrival from a short final |
| Only in Career or an activity | Mission data, activity package or service state | Recreate the landing in Free Flight |
| At many large airports | Graphics load, traffic, driver instability or insufficient memory headroom | Disable traffic and lower airport-heavy settings |
How do I fix MSFS 2024 crashing on landing?
The fastest fix is to reproduce the crash with a stock aircraft and no third-party content, then add complexity back in controlled stages.
Build a repeatable test. Save or recreate a short approach using clear weather and no live traffic. Test the problem aircraft at a default airport, then a stock aircraft at the problem airport. This separates aircraft faults from scenery faults without changing several variables at once.
Run without add-ons. On PC, rename or temporarily empty the
Communityfolder, or use Safe Mode when the simulator offers it. Also disable downloaded third-party packages through the content library; emptyingCommunitydoes not remove every installed aircraft, livery or airport.If the crash stops, restore packages in batches and test after each batch. Start with the destination airport, nearby scenery, the aircraft, its livery and traffic tools.
Clear the rolling cache. Delete it through the simulator's data settings, restart MSFS 2024 and test with the cache disabled before recreating it. Temporarily turn off photogrammetry and other streamed scenery options as a diagnostic step. Our streamed World Data and rolling-cache checks cover this branch in more detail.
Reduce the arrival load. Turn off live and AI traffic, airport vehicles and multiplayer traffic for the test. Lower Terrain Level of Detail, Object Level of Detail and texture resolution if dedicated GPU memory is close to full. A sustainable frame-rate cap can also preserve headroom during the busiest part of the approach.
Test the aircraft package. Remove custom liveries, update or reinstall the aircraft, and avoid restoring a saved panel state until a clean flight works. If a complex aircraft alone causes the crash, use our aircraft-specific WASM troubleshooting rather than reinstalling the entire simulator.
Close touchdown-sensitive utilities. Exit landing-rate monitors, replay tools, telemetry programs, traffic injectors, camera utilities, overlays and motion or force-feedback software. These can remain harmless throughout the flight and fail only when MSFS sends the landing event.
Return the PC to stable settings. Install a stable graphics driver, remove GPU or CPU overclocks and leave the Windows page file system-managed. If the fault began directly after a driver change, a clean installation or rollback is more useful than repeatedly changing simulator settings.
Inspect evidence before reinstalling. PC users should locate and interpret MSFS crash logs on Windows. A third-party module points towards that add-on; a graphics or device-removed fault points towards the driver, GPU tuning or VRAM pressure. A generic Windows module name alone does not prove Windows is damaged.
Use the platform's file verification or repair function only after the controlled tests above. Reinstall the suspect aircraft or airport before downloading the whole simulator again, and do not delete cloud saves or configuration data without a backup.
PC and console differences
PC allows direct access to the Community folder, crash records, drivers and external utilities; Xbox Series X|S, PS5 and PS5 Pro do not. On consoles, fully quit MSFS 2024, restart the console, remove the suspect downloaded package and test without traffic or streamed scenery.
On Xbox, do not resume the troubleshooting flight through Quick Resume. On every platform, install simulator and system updates before repeating the controlled test.
Why does it crash at touchdown or at one airport?
A crash tied to one place points to scenery or streamed data, while a crash at touchdown everywhere points to the aircraft or software reacting to the weight-on-wheels event.
If the same stock aircraft crashes over one runway threshold, remove every optional package affecting that airport or surrounding city. Test another runway as well: a failure over one small area can reveal a bad scenery object or world-data tile rather than an airport-wide problem.
If every aircraft works except one, remove its livery and reset any saved aircraft state. If that aircraft crashes at multiple airports only when its wheels touch, its systems or damage logic are the stronger suspect.
Career missions and Landing Challenges add another layer. Recreate the aircraft, runway and weather in Free Flight; if Free Flight works, troubleshoot the mission or activity package rather than graphics settings. A normal “you crashed” or aircraft-stress message is also not an application crash—it means the simulator registered damage, excessive force or a collision.
Is it a true crash or severe landing stutter?
A return to the desktop or console dashboard is a crash; very low frame rate, delayed textures or a temporary freeze near the runway is usually a performance or streaming problem.
If MSFS remains open, audio continues or the picture eventually recovers, follow the checks that separate landing-area performance collapse from a true crash. Large airports can overwhelm the main thread or VRAM without terminating the simulator, and reinstalling MSFS will not correct that bottleneck.