Learn why duplicate or ghost airports appear in FS2004, how to identify conflicting AFCAD/BGL files, and safely remove the unwanted airport.
Duplicate or ghost airports in FS2004 usually mean that two airport-definition BGL files are active for the same location, or that an add-on moved an airport without excluding the original. Conflicting AFCADs, scenery-layer priority, changed ICAO codes and separate flatten or object files can each leave duplicate runways, buildings or map entries.
What creates a ghost airport in FS2004?
A ghost airport is normally an old or competing airport definition that FS2004 is still loading alongside the airport you intended to use.
- Duplicate AFCAD files: an airport scenery package and an AI traffic package may each install an AFCAD-style BGL for the same ICAO code.
- Two versions of one add-on: files from an older release may remain active after a newer version is installed elsewhere.
- A relocated or renamed airport: the add-on places the new airport correctly but does not suppress the original default location or old identifier.
- Overlapping scenery areas: a detailed airport, regional package and broad scenery layer may all provide airport data.
FS2004 may merge some airport elements rather than treating one file as a clean replacement. This can produce offset runways, duplicated parking, AI aircraft using the wrong surface or ATC recognising an airport that should no longer exist.
How can I identify the type of duplicate?
The visible symptom usually reveals which kind of BGL conflict needs attention.
| Symptom | Likely cause | What to check |
|---|---|---|
| Two offset runways or taxiway layouts | Competing airport-definition or AFCAD files | Airport scenery, AI packages and older versions |
| Old airport remains beside a relocated one | Missing deletion or exclusion data | Whether every BGL supplied with the new airport was installed |
| Buildings appear twice but runways do not | Duplicate object-placement files | Old scenery layers and separate object BGLs |
| Apron or runway surfaces flicker | Ground polygons occupying the same position | Our diagnosis for overlapping FS2004 ground layers |
| Airport sits on a plateau or has a displaced flat area | Flatten, elevation or terrain-mesh conflict | How to separate terrain and flatten faults from airport-definition faults |
| Duplicate appears only in the airport list or GPS | Two facility records, possibly with different identifiers | Both the old and new ICAO codes |
How do I remove a duplicate airport safely?
The safe fix is to identify the competing add-on file and disable it while leaving FS2004's regional default scenery files intact.
- Back up the scenery configuration and suspect files. Record the present Scenery Library order before changing anything.
- Disable one scenery area at a time. Start with old airport packages, regional scenery and AI traffic add-ons associated with the affected location. Close and restart FS2004 after each change so the scenery database is loaded again.
- Narrow the search to individual BGL files. Airport files are often named in a form such as
AF2_KXXX.bgl, but naming is not consistent. If searching for the ICAO code finds nothing, temporarily move groups of suspect add-on BGLs outside every activeSceneryfolder, then restore them in smaller groups. Our method for isolating suspect airport BGL files explains this process in more detail. - Keep only the intended airport definition. Move the unwanted file to a backup folder or change its extension so FS2004 cannot load it. Do not overwrite or permanently delete it until the airport, ATC and AI traffic have all been checked.
- Choose the file that matches the scenery. When an airport package conflicts with a generic AI AFCAD, retain the airport package's own definition unless its documentation specifically requires the replacement. Its runways, parking and taxiways are more likely to align with the visual scenery.
- Correct the layer order. Put the detailed airport above broad regional or base scenery. Priority alone cannot remove an old airport with a different identifier or location; the package must also contain suitable deletion or exclusion data. See our FS2004 scenery installation guidance on layer order and competing AFCADs.
- Test the whole airport. Check the runway position, parking stands, AI movements, ATC frequencies, GPS entry and night lighting. A visually correct runway does not prove that the conflicting facility record has gone.
Should I delete FS2004's default airport BGL files?
No; deleting a default regional airport BGL can remove or damage many airports, not just the duplicate you are investigating.
Default files often contain data for a large geographical area. Disable the conflicting add-on definition instead, or reinstall the complete airport package if its exclusion file was omitted. Never remove a broad default file merely because its name appears related to the affected region.
Why does the ghost airport remain after disabling the AFCAD?
A remaining outline, building group or raised platform usually comes from another component of the package rather than the AFCAD you disabled.
FS2004 scenery packages commonly separate airport facilities, object placement, ground textures, exclusions and flattens into different BGL files. Disable the entire suspect scenery area as a diagnostic test. If the ghost then disappears, restore the files gradually until the specific component returns.
If disabling the whole area changes nothing, another installed package contains a second copy. Check broad regional scenery and AI add-ons as well as the airport's own folder; a mistake we see constantly is searching only Addon Scenery\scenery when the competing BGL belongs to a separately registered scenery area.
Why is the duplicate visible only in the GPS or airport list?
A GPS- or menu-only duplicate means FS2004 is loading an additional airport facility record, often under an old or alternative ICAO identifier.
Search for both identifiers and disable the obsolete airport-definition BGL. AI flight plans can expose the problem by sending traffic to the old code, but they do not create airports themselves. If the unwanted entry survives a full restart, another active BGL still defines it; scenery priority alone will not reliably hide a differently coded airport.