Why are FS2004 default airports missing and how do I fix it?

Default airports usually go missing in FS2004 because a required regional scenery layer is inactive, an add-on has excluded or overridden the stock airport, the scenery index is stale, or default scenery files were deleted. Restore the library first, test without add-ons, rebuild the index, then repair FS2004 only if the files are genuinely absent.

What does “missing” mean in FS2004?

The exact symptom identifies which part of FS2004’s scenery system has failed.

FS2004’s airport list comes from airport records inside active scenery BGLs. Terrain textures and 3D buildings are separate, so an airport can remain searchable even when it looks empty or is hidden beneath the ground.

How do I restore missing default airports in FS2004?

Restore FS2004 in stages so that an add-on conflict is not mistaken for damaged stock files.

1. Confirm that the airport existed in stock FS2004. Its database reflects the early-2000s aviation world. A newer airport, a later runway, or an identifier introduced after that period will not appear without add-on scenery. Search using the airport’s older identifier, name and nearby city before repairing anything.
2. Back up the active configuration. Copy scenery.cfg and make a record of the enabled Scenery Library areas. Also back up user-added scenery before running an installer repair.
3. Check the default Scenery Library areas. Open the Scenery Library from FS2004’s Settings screen. Make sure the broad default, terrain and regional areas are present and active. Stock layers normally sit below higher-priority add-ons. If all the default entries are absent, do not reconstruct them by guessing paths; use a known-good backup or the original installer.
4. Disable suspect add-ons. Start with the newest airport, landclass, mesh or regional package affecting the location. Untick its library area, close FS2004 completely and restart it. If the airport returns, the add-on contains an exclusion, replacement airport or conflicting elevation data. Our FS2004 scenery installation checks explain folder nesting, inactive areas and priority problems in more detail.
5. Rebuild the scenery indexes. With FS2004 closed, find the generated files named scenery.dat beneath the active installation and rename them with an .old suffix. Do not delete or rename any .bgl files. FS2004 should recreate its indexes on the next start; allow that process to finish before checking the airport list.
6. Repair genuinely missing default files. If a required regional area points to an empty or damaged folder, run FS2004 Setup from the original media and use its repair option if offered. Otherwise, back up add-ons and reinstall a clean copy. Restore the same official update level used previously before returning aircraft, gauges and scenery.
7. Re-enable add-ons one at a time. Restart and check the affected airport after each package. Reinstall only the package that caused the failure, following its intended folder structure and scenery-priority instructions.

One stock regional BGL may contain records for numerous airports. An add-on installer that renames or removes that file can therefore make a whole cluster disappear, not just the airport the package was designed to replace.

Which scenery.cfg file is FS2004 actually using?

FS2004 uses scenery.cfg to control scenery areas and layer priority; FS9.cfg is a different file and will not restore airports.

Multiple FS2004 installations and Windows file virtualisation can leave more than one copy of scenery.cfg. Check the FS2004 shortcut’s target to identify the executable being launched. If necessary, make a reversible Scenery Library change, close the simulator and see which configuration file received the new modification time. Edit only that active copy.

Why is the airport listed but buried, floating or empty?

A listed airport with misplaced ground geometry usually has a terrain, flatten or elevation conflict rather than a missing airport record.

Disable recently added mesh, landclass and airport-elevation corrections covering the area. Our guidance on diagnosing terrain mesh and ground-texture installations covers incorrect folders and elevation clashes. If the runway geometry remains but surfaces are black, transparent or replaced by obviously wrong textures, follow the safe process for backing up and restoring FS2004’s default textures.

An empty-looking minor airport may be normal. Many stock fields have basic runways and little custom modelling. Check the scenery complexity setting before assuming that files are missing.

Can an AFCAD file restore a missing default airport?

No; an AFCAD enhancement can improve or replace facility data, but it does not repair missing regional scenery files.

Use AFCAD additions only after the stock airport and its region load correctly. For example, extra parking and taxiway data for minor FS2004 airports can make basic fields more useful, but it is not a substitute for repairing the underlying default scenery. Duplicate or badly placed AFCAD files can also cause conflicts, so move a suspect file to a temporary folder rather than deleting it.

How can I prevent default airports disappearing again?

Keep every add-on in its own clearly named scenery folder and avoid overwriting stock BGLs.

• Back up scenery.cfg before installing regional or airport scenery.
• Record any stock file that an add-on instructs you to rename or disable.
• Install and test one scenery package at a time.
• Use the Scenery Library to disable add-ons instead of deleting files from default folders.
• After a clean repair, reintroduce old scenery areas gradually rather than copying a possibly corrupted configuration wholesale.