Fix a missing runway in FS2004 by checking AFCAD conflicts, scenery priority and stock airport BGLs, then installing the correct replacement.
A runway is usually missing in FS2004 because a higher-priority AFCAD or scenery BGL deletes or replaces the stock airport data. It may also be a real-world runway built after FS9’s database was compiled. Disable duplicate airport files, verify scenery priority, then install or create one complete, compatible AFCAD for that airport.
First check what is actually missing
The quickest diagnosis is to compare the airport’s visible scenery with its Map, GPS and available starting positions. FS2004 treats the visual airport and its facility data as related but separate elements, so an apparent missing runway is not always an AFCAD problem.
| Symptom | Likely cause | What to check |
|---|---|---|
| Runway is absent visually and from Map, GPS and starting positions | Missing or overridden airport facility data | Duplicate AFCADs, scenery priority or a damaged stock airport BGL |
| Runway appears in Map or GPS but not on the ground | Missing custom ground scenery, an intentional transparent runway or an exclusion conflict | The airport’s visual scenery files and their library entry |
| A runway shape is visible but FS2004 does not recognise it | The surface is part of a scenery model without matching facility data | The airport’s required AFCAD file |
| Only a newer real-world runway is absent | FS2004’s release-era airport database predates it | An updated airport-specific AFCAD or scenery package |
If the runway lights, aircraft or markings are buried below the ground or floating above it, the runway is probably present. That points instead to an airport elevation or terrain-flatten conflict.
How do I fix an AFCAD conflict in FS2004?
Fix an AFCAD conflict by temporarily disabling every add-on definition for the airport, confirming that the stock layout returns, and then enabling only the intended replacement.
- Back up the files. Close FS2004 and copy any BGLs you intend to change, along with
scenery.cfg, to a safe location. - Test without the add-on airport. Disable its Scenery Library area, plus any regional scenery or AI traffic package known to include airport files. Restart FS2004 and check the runway again.
- Locate duplicate layouts. Search active scenery folders for likely airport BGLs. Names such as
AF2_XXXX.bglare common, whereXXXXis the ICAO code, but authors do not always follow that convention. - Disable candidates one at a time. Rename an add-on file’s extension from
.bglto something FS2004 will not load, such as.off, then restart the simulator. Do not rename or delete stock regional BGLs during this test. - Keep the correct airport definition. Use one main layout AFCAD that matches the visual scenery. Retain documented companion files for approaches or navaids, but remove obsolete layout duplicates.
- Correct the scenery priority. Give the intended airport package a higher library priority than broad regional scenery covering the same location. Removing an unnecessary duplicate is safer than relying on priority alone.
- Retest every part of the airport. Check the runway in the outside view, Map, GPS, starting-position list and ATC. Allow FS2004 to rebuild its scenery indexes when prompted.
Airport BGLs are not always merged harmlessly. A later-loading definition can contain instructions that remove the existing runways before adding its own, so an old or incomplete AFCAD may leave one runway missing. Our explanation of duplicate AFCAD and navdata behaviour in FS2004 covers this relationship in more detail.
When filenames do not identify the culprit, inspect candidate BGLs with the FS2004-compatible AFCAD 2.21 editor. Compare the ICAO code, runway designators, coordinates and airport elevation before deciding which file belongs with the scenery.
What if the default FS2004 runway is still missing?
If the runway remains absent with all relevant add-ons disabled, either the runway was never included in FS2004 or the stock regional scenery is damaged.
Compare the airport with information from FS2004’s own era rather than assuming its layout should match the modern airport. A runway constructed, extended or redesignated after the simulator’s scenery database was compiled needs an updated AFCAD; reinstalling FS2004 will not add it.
If the runway definitely belonged to the original FS2004 airport, repair the stock scenery rather than downloading an unrelated replacement BGL. Follow our stock-airport restoration checklist to identify missing regional files without deleting working default scenery.
Can I add the missing runway with AFCAD?
You can add a runway with AFCAD, but the new BGL should be stored as a separate add-on rather than overwriting Microsoft’s stock scenery.
- Open or import the correct airport definition and preserve its ICAO code and elevation.
- Add the runway with the correct position, heading, dimensions, surface and designators.
- Add runway starts and connect the runway to the taxi network if AI aircraft must use it.
- Compile the edited airport into its own active scenery folder.
- Remove or disable older layout AFCADs for the same airport.
A layout-only AFCAD supplies functional runway data, but it does not automatically create matching terminals, photographs or detailed custom ground textures. If the fix comes as a complete scenery package, use the correct FS2004 scenery-folder and library procedure so both its visual files and AFCAD load together.
Why does ATC or AI traffic ignore a visible runway?
A runway that is visible but unused by ATC is not necessarily missing. It may be marked closed for take-off or landing, lack a valid start position, have an incomplete taxiway connection, or simply not be selected for the present wind.
Inspect the runway properties and taxi network in AFCAD. If FS2004 lists the runway in Map and GPS but AI aircraft cannot reach it, concentrate on runway links, hold-short nodes and connected taxi paths rather than replacing the visual scenery.