FS2004 crashes after installing an add-on aircraft? Isolate incompatible models, panel gauges, modules, folder errors and overwritten shared files.
FS2004 usually crashes after an add-on aircraft installation because the package contains an incompatible model or compiled gauge, sits in the wrong folder, or has overwritten a shared Gauges or Modules file. Remove the aircraft, confirm FS2004 runs with a default aircraft, then reinstall only the components explicitly made for FS2004.
How do I find which aircraft file is crashing FS2004?
The quickest diagnosis is to remove the new aircraft and test FS2004 with an unmodified default aircraft before changing anything else.
- Back up the add-on and its instructions. Keep the original archive, readme and installer. Note whether the crash occurs at startup, when selecting the aircraft, while loading the cockpit or only after the flight begins.
- Move the complete aircraft folder out of FS2004. The folder to remove temporarily is the one containing
aircraft.cfg, usually found beneath<FS2004>\Aircraft. Move it to a holding folder rather than deleting it. - Load a default aircraft. Start a fresh flight with one of the aircraft supplied with FS2004. Do not use a saved flight that refers to the removed add-on.
- Interpret the result. If FS2004 now works, the problem is inside the aircraft folder or one of its dependencies. If it still crashes before reaching the main screen, the installer probably added or replaced something in
Gauges,Modulesor another shared folder. - Compare the archive with the live installation. Remove only files uniquely supplied by that package and restore overwritten files from a known backup. Never empty the entire Gauges or Modules folder; other aircraft and FS2004 itself may depend on those files.
- Reinstall one component at a time. Begin with the base aircraft and a known-working default panel and sound set. Restore the add-on sound, panel, gauges and effects separately, testing after each change.
Our FS2004 add-on folder and backup procedure explains where Aircraft, Gauges, Effects and Modules files belong and how to reverse an installation safely.
What does the timing of the crash reveal?
The point at which FS2004 closes usually identifies the type of file at fault.
| When FS2004 crashes | Most likely cause | First test |
|---|---|---|
| Before the main screen opens | A newly installed module, an overwritten shared file or a startup flight referencing the aircraft | Remove package-supplied module files and test with a fresh FS9 configuration |
| When the aircraft is selected or previewed | An incompatible or damaged model, texture set or aircraft configuration | Move the aircraft folder out and test a default aircraft |
| As the cockpit loads | A faulty panel, compiled gauge or virtual-cockpit model | Substitute a default FS2004 panel |
| After starting the engine or operating a system | A gauge triggered by that system, an effect or faulty flight-model data | Repeat the action with the default panel and effects disabled |
| Only when the aircraft appears as AI traffic | An unsuitable AI model, texture or traffic assignment | Remove that aircraft from the traffic plan |
Is the aircraft actually compatible with FS2004?
An aircraft must contain an FS2004-compatible model and configuration; being designed for another Microsoft simulator is not enough.
- FSX and Prepar3D aircraft are not backwards-compatible. Their models, gauges and configuration features may fail in FS2004 even if the folders look similar.
- FS2002 aircraft need caution. Some work in FS2004, but older compiled gauges and certain models can fail. Use an FS2004 update when the developer supplied one.
- A repaint is not a complete aircraft. It needs the specified base model and a correct
[fltsim.x]entry. Missing repaint dependencies more often make the aircraft disappear than cause a crash, but malformed configuration entries can stop it loading. - Folder depth matters. FS2004 should find
aircraft.cfgdirectly inside the aircraft's main folder, not beneath an extra archive or package directory.
If the folder structure or base-aircraft dependency is unclear, use these aircraft compatibility and folder-depth checks before changing FS2004 itself.
Can a panel gauge crash FS2004?
Yes—a defective or incompatible compiled gauge can close FS2004 when the panel loads, although a merely missing gauge normally leaves a blank instrument position rather than crashing the simulator.
Temporarily replace the add-on's panel with an alias to a known-working default FS2004 panel. If the aircraft then loads, the model and basic configuration are probably usable, and the fault lies in panel.cfg or one of the gauges it calls. Our panel installation and faulty-gauge checks cover the correct panel folder structure and gauge dependencies.
Restore panel entries in small groups until the crash returns. Pay particular attention to package-supplied .gau files and XML gauges stored in CAB archives. Do not unpack, rename or relocate a gauge archive unless the package instructions explicitly require it.
Why does FS2004 still crash after the aircraft is removed?
If removing the aircraft folder does not fix the crash, its installer probably changed files outside that folder or left FS2004 trying to load the aircraft at startup.
Check the package contents for files installed into Modules, Gauges, Effects or the main FS2004 directory. A DLL in Modules can load when FS2004 starts, so one incompatible module can prevent the simulator from reaching its menus. Restore overwritten files only from your backup or original FS2004 media rather than downloading an unrelated replacement.
You can also close FS2004 and rename %APPDATA%\Microsoft\FS9\FS9.cfg to preserve it as a backup. FS2004 creates a fresh configuration file at the next launch. This resets simulator preferences and can remove a bad startup situation, but it cannot repair a damaged model, gauge or module.
Old installers may write to the wrong location when FS2004 is under a protected Windows folder, leaving some files in the real installation and others in Windows' virtualised storage. Installing to a temporary folder first is safer because every file can be inspected before copying. If permissions or split installations are involved, follow our clean FS2004 troubleshooting process for modern Windows.
What should I avoid while repairing the crash?
A controlled rollback is safer than replacing files at random.
- Do not delete every shared gauge or module because one package added a bad file.
- Do not install several proposed fixes together; test after each single change.
- Do not use the broken aircraft in the startup or saved flight while diagnosing it.
- Do not assume every missing texture or gauge causes a crash; missing resources often produce grey textures, blank instruments or warning messages instead.
- Do not reinstall the aircraft until FS2004 is stable with its default aircraft.