Restore missing FSX airports by fixing scenery entries, isolating add-on conflicts, rebuilding indexes and repairing default APX files.
Airports usually go missing in FSX or FSX: Steam Edition because a default scenery area is disabled, an airport APX file was removed or renamed, scenery indexes are corrupt, or an add-on exclusion is suppressing it. Restore the library entry first, isolate conflicting add-ons, rebuild indexes, then repair stock files if necessary.
Which missing-airport symptom identifies the cause?
The number of affected airports is the quickest way to distinguish damaged default scenery from a local add-on conflict.
| Symptom | Likely cause | First check |
|---|---|---|
| One airport is absent | Conflicting airport BGL, exclusion, or renamed default APX file | Disable scenery add-ons covering that location |
| An entire country or region is missing | Disabled or broken default regional scenery entry | Inspect the FSX Scenery Library |
| Many or all airports are absent from the selection list | Damaged scenery.cfg, scenery indexes, or stock files | Rebuild indexes, then the scenery configuration |
| Runways remain but terminals and objects are gone | Low Scenery Complexity or a missing object-library layer | Check display settings and add-on dependencies |
| The airport is present but empty | AI traffic problem rather than missing airport scenery | Use our steps for restoring missing FSX AI aircraft |
A real-world airport may also be absent because it opened, moved or changed identifier after FSX's airport database was created. Repairing the simulator will not add such an airport; it requires compatible scenery, which may be available in our FSX freeware scenery library.
How do I restore missing airports in FSX?
Work from reversible scenery-library changes towards file repair, testing FSX after each stage so that you know which action solved the problem.
Confirm the airport and its identifier. Search using both the expected ICAO code and the nearest city. FSX may retain an older code, while an airport built after the simulator's database snapshot will not exist in the default installation.
Back up the active configuration. Save
scenery.cfgand any airport files you intend to change. Boxed FSX and Steam Edition can use different configuration folders, especially when installed together; our FSX backup and configuration-location guide explains what to preserve.Check the Scenery Library. Open the library from FSX settings and make sure the default regional scenery areas are present, enabled and pointing to valid locations. Add-on airports normally sit above default scenery; Priority 1 is the highest. Do not randomly reorder the numbered default areas.
Disable scenery covering the affected region. Start with the most recently installed airport, regional package or terrain add-on. Restart FSX after each library change because exclusions and airport records are compiled when scenery loads. If the default airport returns, the disabled package contains the conflict.
Rebuild the scenery indexes. Close FSX, then rename the active
SceneryIndexesfolder so it can be restored if needed. It is normally beneath%PROGRAMDATA%\Microsoft\FSXor the correspondingFSX-SEfolder. Start FSX and allow the scenery database to rebuild fully.Rebuild a damaged scenery configuration. If whole regions remain missing, close FSX and rename the active
scenery.cfgto a backup name. FSX should create a clean default configuration on its next launch. Custom scenery layers will then need to be added again; if no new file is created, restore the backup and continue to repair.Repair the stock installation last. For FSX: Steam Edition, run Steam's file-integrity verification. For boxed FSX, use the repair option from the original installation media and repair the installed expansion or update components where applicable. Verification can replace modified core files, so keep the backup made earlier.
How do I restore one missing default airport?
A single missing default airport usually points to a local add-on BGL or a disabled stock APX file, not a broken global scenery library.
Default FSX airport records are stored in files beginning with APX inside numbered regional folders under [FSX installation]\Scenery. One APX file can contain several airports, so deleting or replacing an entire file to fix one location may remove others in the same tile.
- Look for stock APX files renamed with extensions such as
.off,.bakor.disabledby an airport installer. - Disable the associated add-on before restoring the original filename.
- Keep only one active copy of a BGL. Duplicate stock files commonly produce doubled runways, parking spots and windsocks.
- Do not copy an APX file from another FSX edition or installation unless its source and patch state match. Use installation repair when the original file is genuinely missing.
A properly packaged replacement airport normally uses exclusions and its own airport record rather than requiring permanent deletion of default regional files.
Why is the airport listed but not visible?
If FSX lists the airport but some scenery is absent, the airport database is loaded and the remaining fault is usually an object, surface or texture problem.
Raise Scenery Complexity in the display settings if runways are present but terminals, jetways or smaller objects are missing. For add-on airports, confirm that every supplied object-library layer is active and above the default scenery.
White, black or transparent surfaces indicate missing texture assets rather than a missing airport record. Follow our dedicated procedure for diagnosing and repairing missing FSX textures instead of rebuilding the airport database.