Restore deleted FS2004 scenery by re-adding library entries, recovering add-on files, repairing scenery.cfg or replacing missing default files.
In Microsoft Flight Simulator 2004 (FS9), deleting an area from the Scenery Library usually removes only its registration, not its files. Re-add the existing parent folder. If the files were erased, restore them from the Recycle Bin, a backup or the original package; repair or reinstall FS2004 only for missing default scenery.
Was the scenery actually deleted or only removed from the library?
The Delete Area command normally removes the area's entry from scenery.cfg without deleting its BGL files or textures.
| What you find | Correct recovery |
|---|---|
| The package folder and BGL files still exist | Re-add or re-enable the area in the Scenery Library. |
Files are inside the shared Addon Scenery folders | Enable the existing Addon Scenery layer; do not create an unnecessary second entry. |
| The whole add-on folder is gone | Restore it from the Recycle Bin, backup, original archive or installer. |
| Default folders exist, but several stock areas have disappeared | Repair the active scenery.cfg rather than reinstalling all the scenery. |
| Original default BGL files are genuinely absent or damaged | Use the original FS2004 installation media to repair or reinstall the simulator. |
How do I re-add scenery that is still on the drive?
Register the package's parent folder again, then restart FS2004 so it can rebuild its scenery database.
- Close FS2004. Do not move scenery files while the simulator is running.
- Locate the package. Start with
Addon Scenery, then check any custom scenery locations used by the installer. If FS2004 is under Program Files on a newer Windows system, inspect the corresponding per-user VirtualStore as well. - Check the folder structure. A normal self-contained package has a parent folder containing a
scenerysubfolder and, where required, a siblingtexturesubfolder. Select the parent, not the innersceneryfolder. - Account for shared folders. Some older packages place their BGL files directly in the standard
Addon Sceneryscenery folder. In that case, ensure the standard Addon Scenery area is enabled instead of registering a new package folder. - Add the area. Open FS2004, go to Settings, open the Scenery Library, choose Add Area and select the correct parent folder.
- Set its priority and restart. The restored area must be enabled and have higher priority than any scenery it is intended to replace. Let FS2004 finish rebuilding the scenery database before loading the airport or region.
Our detailed folder-structure and library-registration procedure explains the correct package layout and layer ordering.
How do I restore genuinely deleted add-on scenery files?
Recover or reinstall the complete scenery package rather than replacing one BGL with a similarly named file.
- Check the Recycle Bin. Restore the package to its original location if Windows retained it.
- Use a known-good backup or original package. If an incomplete copy remains, rename it before reinstalling. Mixing files from different releases can leave obsolete airport layouts, exclusions and textures active.
- Protect personal changes. Copy aside any BGL, AFCAD or texture files that you edited yourself.
- Restore every component. Airport scenery may depend on accompanying textures, object libraries, terrain files and exclusions. Reinstall those dependencies from their original packages as well.
- Verify the active FS9 installation. With multiple installations or VirtualStore redirection, an installer can write to a different folder from the one FS2004 is loading. Confirm the destination before adding the restored area to the library.
A mistake we see often is restoring the visible airport BGL but omitting its textures or shared object library. The airport then loads with missing buildings, black surfaces or incomplete ground detail even though its library entry is correct.
How do I restore default FS2004 scenery?
Repair the scenery configuration when the stock files still exist; use the original FS2004 media only when those files are actually missing or corrupt.
- Back up custom content. Preserve
Addon Scenery,scenery.cfg, edited airport files and any add-ons installed inside the default scenery tree. - Check the scope of the failure. If many regions disappeared together, suspect a damaged configuration or invalid paths. If only one airport is missing, first check for an add-on exclusion or conflicting airport BGL.
- Repair the registrations. When the default folders and BGL files remain on disk, follow the safer process to rebuild the active scenery.cfg without deleting scenery files. Do not manually add every regional default folder in an arbitrary order.
- Replace missing stock files. Run setup from the original FS2004 media and use its repair option if one is offered. Otherwise reinstall the same simulator edition. Do not substitute scenery from FSX, Prepar3D or another simulator.
- Restore the previous update state. Reapply the same official FS2004 update level and relevant add-on patches before enabling custom scenery again.
If a full reinstall is unavoidable, use our procedure for preserving add-ons and configuration before reinstalling FS2004.
Why is the restored scenery still not showing?
Invisible restored scenery is usually caused by the wrong folder being registered, an inactive layer, an incomplete package or a conflicting BGL elsewhere.
| Symptom | Likely cause and fix |
|---|---|
| The default airport still appears | Confirm that the add-on is enabled, its airport BGL is inside the active scenery folder and its layer has sufficient priority. |
| The area is accepted but nothing changes | Look for an extra nested folder. The registered parent must directly contain the package's scenery folder. |
| Buildings or textures are missing | Restore the complete package and any required object libraries. Also check FS2004's scenery-complexity setting. |
| Runways or buildings are duplicated | Another copy of the airport, often an older AFCAD-style BGL, is active elsewhere. Disable suspected areas one at a time rather than deleting files at random. |
| Trees and generic buildings are absent everywhere | Check the autogen-density setting and autogen files; this is not normally fixed by re-registering an airport package. |
| FS2004 reports that a scenery path or file cannot be found | The library probably contains an obsolete path. Use the steps for diagnosing stale paths and missing scenery file errors. |
Should I delete scenery.dat?
Only reset the generated scenery index after confirming that the folder path, BGL files and library entry are correct. Close FS2004, rename the affected scenery.dat file rather than permanently deleting it, then restart the simulator so the index can be rebuilt. This cannot recover BGL or texture files that are genuinely missing.