Why does FS2004 crash after installing scenery?

FS2004 usually crashes after installing scenery because FS9 is loading a corrupt or incompatible BGL, conflicting airport definition, broken Scenery Library entry, or overwritten stock file. Disable the new area first, restart the simulator, and then restore its files in batches; the first failing batch normally identifies the component to remove or replace.

What does the FS2004 crash point tell you?

Where FS2004 fails is the quickest way to distinguish a local airport problem from a global configuration or resource fault.

A Windows crash report naming an FS2004 rendering or terrain component does not prove that the named simulator file is damaged. Bad scenery data can make a stock component fail while it is reading that data. For a CTD that occurs reliably on approach to one field, use our checks for a repeatable crash near an add-on airport.

How do I fix an FS2004 scenery crash?

The safest fix is to establish a clean baseline, then restore the package in controlled stages rather than deleting files or reinstalling FS2004 immediately.

1. Preserve the original state. Keep the downloaded archive or installer, copy the active scenery.cfg, and record every destination used by the package. Its location can vary with the FS2004 installation and Windows file virtualisation, so identify the active copy by its contents and modification time rather than assuming a path. Move suspect files to a temporary folder; do not delete them.
2. Disable the new scenery area. If FS2004 reaches the menu, disable or remove that area through the Scenery Library, then exit and restart FS9. Removing a library entry does not normally delete the physical files. If FS2004 cannot reach the menu, close it, back up scenery.cfg, locate the add-on's section by its Title= and Local= lines, and change only that entry to Active=FALSE. Do not alter stock areas or edit the file while FS2004 is running.
3. Confirm the clean baseline. Load the same airport, route, aircraft and approximate conditions with the new area disabled. If the crash disappears, the package or an interaction with it is responsible. If it remains, the installer may have placed files in a shared folder, replaced a default file, or exposed an unrelated in-flight CTD.
4. Check that the scenery is genuinely for FS2004. FS2004 and FS9 are the same simulator, but FSX, Prepar3D and newer Microsoft Flight Simulator packages are not interchangeable with it. Similar folder names do not make their BGL, model or texture formats compatible. Also check the package instructions for required FS2004 object libraries or companion areas.
5. Correct the folder structure. A conventional area has a root such as ...\Addon Scenery\Package Name, containing scenery and, when needed, texture subfolders. BGL files belong under scenery; the package root, not the inner scenery folder, is added to the library. Some releases contain several separate areas, so preserve their supplied structure. Our FS9 scenery folder and library installation procedure explains the correct layout, activation and priority order.
6. Find every file the installer added. Older self-installers can target another FS2004 installation, write into a virtualised Windows location, or copy files into shared Scenery, Texture, Effects or Modules folders. Disabling the package's library area will not disable those files. Compare the installer manifest or original archive with the installation; do not delete files solely by date because archived timestamps can be misleading.
7. Test the BGL files by halves. Move half of the package's BGL files to a temporary folder outside every active scenery path, restart FS2004 and repeat the same test. If the crash stops, the implicated file is in the removed half; if it continues, it is in the active half. Repeat until one file or related group remains. The BGL that triggers the crash may be calling a corrupt model or texture, so it is not necessarily the only damaged file.
8. Remove competing airport definitions. Disable other add-ons covering the same ICAO airport or immediate region, especially alternative airport layouts, older AFCAD-style files, elevation corrections and exclusion files. Keep one principal airport definition active during testing. Filenames often contain an ICAO code, but that convention is not guaranteed; check package documentation and every active regional area.
9. Use display settings as diagnostic switches. Test Scenery Complexity first, then Autogen Density and AI traffic, changing one variable at a time. If reducing Scenery Complexity prevents a crash at exactly the same point, either an object at the higher complexity level is faulty or the airport is exhausting resources. A crash that develops after visiting several detailed areas is more characteristic of address-space pressure in FS2004's 32-bit process.

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

A package that crashes FS2004 with all other third-party scenery disabled is probably corrupt, incompatible or incomplete; one that works alone but fails when another local area is enabled has a conflict.

• Fails when used alone: replace the implicated file or obtain the correct FS2004 edition of the package.
• Works until another regional area is enabled: compare their airport, exclusion, mesh, landclass and elevation coverage.
• Always fails at one coordinate: concentrate on the local BGLs loaded there rather than global graphics settings.
• Fails only after extended flying: reduce detailed scenery and AI traffic, then test for cumulative resource pressure.
• Stops failing at a lower Scenery Complexity setting: isolate the object BGL associated with the higher setting before assuming memory alone is responsible.

Will changing Scenery Library priority fix duplicate airports?

Scenery priority can control intended layering, but it cannot repair a malformed BGL or make every pair of duplicate airport definitions compatible.

Place the detailed airport above broader regional mesh or landclass where the developer's instructions require it. If two packages both redefine the runways, taxiways or airport elevation, disable one while testing rather than relying on priority to suppress every conflict.

Can missing textures make FS2004 crash?

Missing textures usually cause grey, black or untextured objects rather than an immediate CTD, although a corrupt or incompatible texture can still crash the renderer when its model appears.

Confirm that the package's texture folder is beside its scenery folder and that any required object library is the FS2004 version. A missing shared library more commonly produces absent buildings than a crash. Do not copy an entire texture folder from FSX or another simulator to hide missing-file errors; that can introduce incompatible assets and make the original fault harder to identify.

Why does FS2004 still crash after the scenery is disabled?

If disabling the library area does not stop the crash, the package probably installed files elsewhere, left a broken configuration entry, overwrote stock data, or was not the original cause.

• Check scenery.cfg for a second entry pointing to the same package or a path that no longer exists.
• Use the package's archive or manifest to identify BGLs, effects, textures or modules copied into shared folders.
• Restore known overwritten default files from a verified backup or the original FS2004 media.
• Test with third-party aircraft, AI traffic and non-essential modules disabled if the crash also occurs away from the new scenery.

Moving or renaming a referenced folder can produce a scenery directory warning without causing the original CTD. Our guide to repairing stale and missing FS2004 scenery paths covers that configuration problem. If the simulator still crashes during ordinary flights with the scenery removed, continue with the broader FS2004 in-flight CTD isolation process.

Do I need to reinstall FS2004?

A complete reinstall is unnecessary when FS2004 becomes stable as soon as the new scenery is disabled.

Consider a repair or reinstall only after all third-party scenery has been deactivated, the backed-up configuration has been restored, known shared-folder additions have been removed, and stock FS2004 still crashes at several unrelated locations. Back up aircraft, gauges, effects, modules and scenery first because a repair can replace modified files without identifying which add-on caused the original problem.