Why does FSX close immediately after loading an aircraft?

FSX usually closes immediately after loading an aircraft because that aircraft has a broken panel or gauge, missing dependency, malformed configuration, or incompatible module. If every aircraft crashes, suspect the saved flight, departure scenery, FSX configuration, graphics driver, or memory pressure instead. Testing a default aircraft first identifies the correct branch.

In FSX and FSX: Steam Edition, this unexplained exit is commonly called a crash to desktop, or CTD. The point at which it happens matters: crashing while previewing an aircraft suggests different files from crashing after the cockpit appears.

Is one aircraft or every aircraft causing FSX to close?

The fastest diagnosis is to reproduce the crash with a stock aircraft, stock airport and newly created Free Flight.

How do I isolate the aircraft-loading crash?

A controlled comparison will show whether the aircraft, location or simulator itself is failing.

1. Restart FSX completely. This clears memory retained from the previous flight.
2. Create a fresh Free Flight. Choose a default aircraft such as the stock Cessna 172, a stock airport, daytime and fair weather. Do not use a saved flight.
3. Load the default aircraft. If it works, change only the aircraft to the suspect add-on while keeping the same airport and conditions.
4. Change the departure airport. If the suspect aircraft works elsewhere, investigate scenery or AI traffic rather than the aircraft package.
5. Check Windows Event Viewer. Open Windows Logs and then Application after the crash. A named third-party gauge or module is useful evidence; generic entries such as ntdll.dll or KERNELBASE.dll do not by themselves identify the cause.

How do I fix one add-on aircraft that crashes FSX?

If only one aircraft closes FSX, repair that package before changing Windows or reinstalling the whole simulator.

1. Undo the latest modification. Remove a newly added repaint, panel, sound set or edited configuration and restore your backup. A malformed aircraft.cfg or incorrect panel reference can stop the aircraft loading.
2. Check the folder structure. The aircraft's main folder should sit beneath SimObjects\Airplanes, with aircraft.cfg and the associated model, panel, sound and texture folders at the expected level. Nested duplicate folders are a mistake we see frequently; our aircraft installation checklist shows the correct layout and required files.
3. Install the correct FSX release. An FS2004 package, Prepar3D build or aircraft requiring an external module may appear in the selector yet crash during loading. Steam users should also follow our Steam Edition compatibility checks, particularly when an installer has used the boxed-FSX path.
4. Reinstall every supplied dependency. Missing gauges, effects and support modules can leave a panel unusable. Follow the aircraft's included instructions rather than placing every file in the main FSX directory.
5. Inspect aliases and references. Entries in panel.cfg, sound.cfg and model.cfg may point to another aircraft that is not installed. Incorrect model or texture references are covered in our guide to broken model and texture references.
6. Isolate suspect gauges. If Event Viewer identifies a gauge DLL, use an updated compatible version or remove that gauge from a backed-up copy of the panel configuration. Do not download random replacement DLLs or replace Windows system files.

Test the clean base aircraft before restoring optional repaints and panel modifications. Add them back one at a time so the failing component is obvious.

Why does FSX crash only at one airport?

A location-specific crash usually comes from scenery or traffic loaded around that airport, not from the selected aircraft.

Set airline, general aviation, road and boat traffic to zero, then test a default aircraft at the same location. If the crash remains, temporarily disable the local add-on scenery and retry. Saved flights can also retain problematic weather, location and aircraft data, so build a new flight rather than overwriting the old one.

What if default aircraft also crash?

If stock aircraft fail at multiple stock airports, reset FSX's configuration and isolate modules loaded for every flight.

1. Regenerate FSX.cfg. Close FSX, back up and rename %APPDATA%\Microsoft\FSX\FSX.cfg, then launch the simulator so it creates a clean file. Record any important settings first.
2. Disable global add-on modules temporarily. With FSX closed, back up and rename dll.xml and exe.xml in the same application-data area. Restore them after testing; this procedure temporarily prevents dependent add-ons from loading.
3. Reset graphics options. Turn off DirectX 10 Preview if enabled and test conservative display settings. A crash log naming a graphics-driver file points towards the driver or rendering configuration.
4. Repair the installation last. Steam Edition users can verify installed files through Steam; boxed-FSX users can run the installer repair option. Back up modified default files because repair may restore original copies.

For crashes that are not tied to one aircraft, work through our wider FSX crash checklist rather than repeatedly reinstalling aircraft.

Can FSX memory limits cause this crash?

Yes, especially when a detailed aircraft is combined with dense scenery, large textures and heavy AI traffic.

FSX is a 32-bit application even on 64-bit Windows. When its available address space is exhausted, it may close with an out-of-memory warning or simply disappear. Restart FSX, lower texture resolution, autogen, scenery complexity and traffic, then test the aircraft at a simple stock airport. Memory is less likely to be the cause when a default aircraft crashes immediately after a fresh launch.