Why does FS2004 crash after installing scenery?

FS2004 usually crashes after a scenery installation because it is loading an incompatible or corrupt BGL, a duplicate airport file, an incorrect folder structure, or an overwritten default file. Disable the new scenery first, then reactivate its files in small groups; the crash point usually reveals which component needs removing or replacing.

What does the FS2004 crash point tell you?

The point at which FS2004 fails is the fastest way to narrow the fault before changing configuration files or reinstalling anything.

If the crash occurs only when approaching the newly installed airport, use our location-specific airport crash checks alongside the isolation process below.

How do I fix FS2004 scenery crashes?

The reliable fix is to remove the new scenery, confirm that FS2004 is stable, and then isolate the exact file or conflict.

1. Back up before removing anything. Keep the original download or installer, make a copy of scenery.cfg, and note every destination used by the package. Do not delete unfamiliar stock BGL files.
2. Disable the newest scenery area. If FS2004 opens, untick or remove that area through the Scenery Library, exit the simulator and restart it. If it crashes before the menu, temporarily rename the add-on's top-level folder so its BGL files cannot load; FS2004 may report a missing scenery path, which is expected.
3. Confirm that the package is for FS2004. FSX, Prepar3D and newer Microsoft Flight Simulator scenery cannot be assumed to work in FS9. A scenery package may look structurally similar while containing airport, model or texture formats that FS2004 cannot load safely.
4. Check the folder level. A conventional package uses ...\Addon Scenery\Package Name\scenery\*.bgl with an optional sibling texture folder. Add the package's root folder to the Scenery Library, not the inner scenery folder. Our FS2004 folder and Scenery Library walkthrough covers the correct structure and priority order.
5. Verify where an installer actually wrote its files. Old installers may target another FS2004 installation or be affected by permissions under a protected Windows folder. If files appear to vanish or configuration changes do not stick, see our guidance for running FS2004 under modern Windows.
6. Restore overwritten default files. Some older packages copy files directly into shared Scenery or Texture folders instead of using a separate add-on directory. Removing the package folder will not undo those changes. Restore replaced files from a known backup or the original FS2004 media.
7. Test the BGL files in batches. Move half of the suspect package's BGL files to a temporary folder outside every active scenery path, then test the same flight. If the crash stops, the faulty file is among those removed; if it continues, it is among those still active. Repeat until one file or related group remains.
8. Look for duplicate airport definitions. Search all active add-on folders for other files covering the same ICAO airport. Keep one principal airport layout active while testing. Scenery priority can control deliberately layered components, but it does not make every pair of competing airport definitions compatible.
9. Let FS2004 rebuild its scenery data. Exit and restart after each library change. If the package remains disabled but the crash continues, inspect the backed-up scenery.cfg for a duplicated or malformed entry associated with that package rather than deleting unrelated stock areas.

Is the scenery file bad, or is another add-on conflicting?

A scenery package that crashes FS2004 when it is the only third-party area active is probably damaged, incompatible or incomplete; one that works alone but fails when another local package is enabled has a conflict.

Reactivate other scenery areas one at a time, beginning with packages covering the same airport or region. Airport layouts, exclusion files, landclass, mesh and object libraries can overlap. Do not remove a shared object library merely because it is geographically broad: disabling it may replace the crash with missing buildings or generic objects.

Settings can provide another useful distinction. Temporarily reduce scenery complexity, autogen and AI traffic. If that alone prevents the crash at a highly detailed airport, FS2004's 32-bit process is probably under resource pressure. If it always fails at the same coordinate regardless of settings, a local BGL or conflict is more likely.

Can missing textures make FS2004 crash?

Missing textures more often produce grey, black or untextured objects than an immediate crash, but a corrupt or incompatible texture can still upset the renderer.

Check that the package's texture folder sits beside its scenery folder and that any required object-library package is installed for FS2004. Do not copy a whole texture folder from another simulator to silence missing-file errors; that can introduce incompatible files and obscure the original fault.

If the problem began with mesh, landclass or replacement ground textures rather than an airport, follow our mesh and ground-texture conflict checks. Terrain spikes and airport elevation errors indicate layering or elevation conflicts, while a repeatable crash at one coordinate points more strongly to a malformed terrain BGL.

Reinstalling FS2004 is the last resort

A full reinstall is rarely necessary when FS2004 runs normally after the new scenery is disabled. Reinstall only if third-party scenery has been removed, configuration backups have been restored, and the simulator still crashes with stock scenery at multiple locations. If an installer overwrote default files, repairing those files is usually quicker and safer than rebuilding the entire installation.