Learn how to exclude a default airport in FS2004 safely, replace its AFCAD, remove stock objects, set scenery priority and reverse the change.
To exclude a default airport in FS2004, leave the stock scenery files untouched. Create a higher-priority add-on scenery area containing an exclusion BGL for default objects and, when replacing the airport, an AFCAD with the same ICAO code. An exclusion alone does not remove every part of the airport database.
What does an FS2004 airport exclusion remove?
An exclusion rectangle suppresses specified scenery objects from lower-priority layers inside its boundaries. Depending on how it was compiled, that can include terminals, hangars, library objects, windsocks, beacons and taxiway signs.
It does not necessarily remove the airport facility data used for runways, taxiways, parking, starts, frequencies and the GPS. FS2004 treats these elements differently, so the correct method depends on what you are trying to achieve.
| Goal | Required method |
|---|---|
| Hide stock buildings and signs | Use a tightly drawn exclusion BGL. |
| Install a replacement airport | Use an exclusion BGL for stock objects plus a higher-priority AFCAD or airport BGL with the same ICAO code. |
| Remove runways and taxiways | Compile an airport replacement or deletion record with an FS2004-compatible airport design tool. |
| Remove the airport from GPS or airport lists | An object exclusion cannot do this; the stock airport header may remain even when its physical facilities are suppressed. |
How do I create and install the exclusion?
- Identify everything that must disappear. Check for stock buildings, runway surfaces, taxiways, signs, approach lights, navigation aids and an airport background or flatten. A single exclusion may not affect all of them.
- Create a small exclusion rectangle. Use an FS2004-compatible scenery design tool or the FS2004 scenery compiler. Draw the rectangle only around the stock objects you need to suppress; an oversized exclusion can remove unrelated scenery several miles away.
- Create the replacement airport if required. Open the stock airport by ICAO code, edit a copy and compile it as an add-on AFCAD. Our explanation of editing FS2004 airport layouts with AFCAD covers the airport-layout side of the process.
- Keep the add-on files separate from stock scenery. A practical structure is
Addon Scenery\Airport Exclude\sceneryfor the exclusion and another scenery area for the replacement. Put only compiled BGL files in the activesceneryfolders. - Set the Scenery Library order. From highest to lowest priority, arrange the replacement airport, the exclusion layer and then the default scenery. The exclusion must sit above the stock layer, while the replacement should sit above the exclusion.
- Restart FS2004 and inspect the site. Check the airport from both the air and ground, then test the airport-selection list, GPS, ATC frequencies and AI traffic. A visually empty site can still contain parking or start positions in the airport database.
If you already have a replacement AFCAD, follow the normal FS2004 AFCAD installation process, but inspect the package first. Some airport downloads already contain an exclusion BGL, and installing a second broad exclusion can hide wanted objects.
Why is part of the default airport still visible?
Remaining scenery usually means the exclusion covers the wrong area, excludes the wrong object class or does not address airport facility and terrain data.
- Runways or taxiways remain: install a valid replacement airport definition with the same ICAO code rather than relying on an object exclusion.
- Buildings remain: expand the exclusion slightly or include the relevant library and generic-building object classes.
- Flat ground or airport-coloured terrain remains: this is likely an airport background, flatten or landclass feature. It requires compatible terrain scenery; an ordinary object exclusion does not restore the surrounding terrain automatically.
- Duplicate parking or AI behaviour appears: search active scenery folders for another AFCAD using the same ICAO code. Two replacement airport files are a common source of conflicts.
- Your replacement objects disappear too: move the replacement layer above the exclusion layer or tighten the exclusion boundaries.
Never delete a regional stock airport BGL from FS2004's default scenery folders. Those files normally contain many airports, so removing one can make an entire group disappear. If that has already happened, use our guide to recover missing FS2004 default airports and resolve scenery conflicts.
Can I reverse the exclusion safely?
Yes. Disable the custom exclusion and replacement areas in the FS2004 Scenery Library, restart the simulator and confirm that the stock airport has returned. Once verified, you can remove those custom folders without touching any default BGL files.
If the airport does not return, another active AFCAD or exclusion is still overriding it. Search add-on scenery folders by ICAO code, disable suspect layers one at a time and restart FS2004 after each Scenery Library change.