Why does FSX crash on final approach?

FSX and FSX: Steam Edition usually crash on final approach because the simulator is loading airport scenery, AI traffic, weather, textures and aircraft systems at once. The common causes are faulty local scenery or add-ons, exhausted 32-bit virtual address space, incompatible gauges or modules, and a damaged configuration—not the approach procedure itself.

Common causes of final-approach crashes

A crash tied to final approach is usually identified by when and where it happens.

Scenery is the leading suspect when FSX closes at almost the same distance from one runway every time. Airport add-ons can contain duplicate facility files, often called AFCADs, while regional packages may add conflicting terrain, objects or libraries.

If the failure moves between airports and appears mainly after a long sector, memory pressure is more likely. FSX remains a 32-bit application even on 64-bit Windows, so smooth frame rates do not prove that sufficient address space remains.

How do I isolate the cause?

Use a controlled approach test and restore one component at a time.

1. Record the exact pattern. Note the airport, runway, aircraft, weather, traffic level and approximate distance from touchdown. After the crash, check Windows Event Viewer under Windows Logs and Application for the faulting module. A named aircraft gauge or add-on DLL is useful evidence; ntdll.dll, KERNELBASE.dll or exception code 0xc0000005 usually identifies only a generic access violation.
2. Create a clean baseline. Start a new flight 15–20 NM from the airport with a default aircraft, clear weather, daytime conditions, all traffic at zero and the destination add-on scenery disabled. Do not use the original saved flight, because a damaged situation file can preserve faulty aircraft or weather state.
3. Test the scenery layers. If the clean approach works, enable the airport, regional scenery and object libraries one at a time, restarting FSX after each Scenery Library change. Check for two packages modifying the same airport. Do not delete every BGL containing the airport code; filenames are inconsistent, and an unrelated file may be required elsewhere. If the crash persists with default scenery, review the documented coverage of our corrections for known FSX scenery errors rather than installing them as a universal fix.
4. Restore traffic and weather separately. Increase AI traffic first, then test custom weather. A single defective AI model may crash FSX only when it enters visual range, so the failure can seem intermittent or occur on one arrival but not another.
5. Retest the original aircraft. If only that aircraft crashes, remove panel modifications, replacement gauges and added liveries one at a time. A crash that occurs precisely when selecting APR, displaying weather radar or changing a cockpit page points more strongly to the aircraft than to the airport.
6. Rebuild the configuration. Close FSX and rename fsx.cfg instead of deleting it. Boxed FSX normally keeps it under %APPDATA%\Microsoft\FSX; Steam Edition may use either the FSX or FSX-SE folder depending on installation history and whether boxed FSX is also installed. Launch FSX to generate a clean file, then restore settings gradually rather than copying old tweaks back wholesale.
7. Disable external modules in reverse installation order. Use each add-on's installer or configurator where possible, and back up dll.xml or exe.xml before editing either file. Steam users should also check whether the aircraft, scenery or utility was designed for their installation layout using our FSX: Steam Edition add-on compatibility guidance.

Is the ILS or autopilot causing FSX to crash?

Usually not; the localiser intercept often coincides with the point where detailed airport scenery and nearby traffic are loaded.

If every aircraft crashes near the same runway even while hand-flying, investigate scenery first. If only one aircraft fails exactly when APR is pressed, its autopilot gauge, flight-management system or panel module becomes the primary suspect. An incorrect ILS setup may produce poor guidance or an unstable approach, but it should not close FSX.

Why does FSX crash only after a long flight?

A long-flight-only crash strongly suggests exhausted or fragmented virtual address space.

Detailed aircraft, high-resolution liveries, cloud textures, AI fleets and several overlapping destination sceneries can consume the available space without producing an explicit out-of-memory warning. FSX may instead freeze briefly and disappear to the desktop.

Repeat the arrival as a short flight after restarting FSX. If that works, reduce global texture resolution, scenery complexity, autogen, cloud detail and AI traffic, prioritising the settings that affect the destination. Our FSX performance and load-reduction guidance explains which settings provide useful savings. Restarting the simulator between demanding flights also releases allocations that may not have been reclaimed cleanly.

Should I reinstall FSX?

No—reinstallation should be the last step because it often leaves the actual scenery conflict, add-on file or AppData configuration untouched.

For Steam Edition, verify the installed files only after backing up deliberate modifications; verification can restore altered core files. For boxed FSX, use the installation media's repair option before attempting a complete removal. Reinstall only if a default aircraft still crashes at multiple default airports with clear weather, zero traffic, a newly generated fsx.cfg and all third-party modules disabled.

If the crash is not tied to one destination or approach, follow our broader FSX crash-isolation process for add-ons, configuration files and core installation faults.