Find why a runway is missing in FS2004 and fix AFCAD conflicts, scenery priority, inactive stock scenery or airport elevation errors.
In FS2004 (FS9), a runway usually disappears because an add-on AFCAD or scenery BGL overrides the stock airport, the correct scenery area is inactive, or terrain hides it. Disable conflicting airport files, restore the intended scenery priority, rebuild FS2004’s scenery index, then keep one airport definition that matches the visual scenery.
First check what is actually missing
The Map, GPS and starting-position lists reveal whether FS2004 has functional runway data or only visible scenery. An airport’s facility data and its ground textures or models are related, but they are not the same thing.
| What you see | Likely cause | Where to concentrate |
|---|---|---|
| Runway missing from the ground, Map, GPS and starting positions | Airport facility data is absent, inactive or overridden | Duplicate AFCADs, Scenery Library entries and stock regional scenery |
| Runway listed in Map or GPS but invisible on the ground | Visual scenery is missing, excluded or intentionally transparent | The airport’s scenery files, textures and library activation |
| Runway shape visible but absent from Map and GPS | The shape is only a texture or scenery model | A missing or incompatible airport AFCAD |
| Runway lights or markings buried or floating | Airport elevation, terrain mesh or flatten conflict | Elevation corrections and terrain files |
| Only a newer real-world runway is absent | FS2004’s early-2000s airport database predates it | An updated airport layout or complete scenery package |
Runway numbers may also have changed because of magnetic variation, and an airport may now use a different identifier. Check the airport’s location and older runway designators before assuming that FS9 has lost it.
I still cannot find the runway in FS2004
If you cannot find the runway at all, confirm the airport identifier and historical runway number before changing any files.
If your result is simply “niente, non riesco a trovarlo” — “nothing, I can’t find it” — search by ICAO identifier, nearby city and airport name, then inspect every available starting position. Our guide to checking airports, runways and starting positions inside FS2004 helps establish whether the facility exists in the simulator’s database.
Also verify that you are testing the same airport represented by the add-on. A replacement built under an old identifier may not appear when searching for the airport’s modern code.
How do I fix an AFCAD conflict in FS2004?
Fix an AFCAD conflict by disabling all add-on definitions for that airport, confirming that the stock layout returns, and then enabling only the replacement that matches the visual scenery.
“AFCAD” is commonly used to mean an FS2004 airport-layout BGL, even when the file was produced by another airport editor. These files can define runways, starts, parking, taxi links and exclusions; they are not always merged harmlessly.
- Back up the configuration and add-on files. Close FS2004, then copy
scenery.cfgand any BGLs you intend to alter to a safe location. - Disable the main airport package. Deactivate its Scenery Library area and restart FS2004. If the stock runway returns, the fault is inside that package or another file supplied with it.
- Test regional and AI packages. Some mesh, regional scenery and AI traffic packages install their own airport layouts. Disable relevant areas one at a time, restarting FS2004 after each change.
- Locate duplicate airport files. Names such as
AF2_XXXX.bglare common, withXXXXrepresenting an ICAO code, but filenames are not reliable proof. One BGL may also contain several airports. - Disable only add-on candidates. Rename a suspected add-on file from
.bglto a non-loading extension such as.off. Never rename or delete a stock regional BGL merely because it contains the affected airport. - Keep one principal layout. Retain the AFCAD designed for the visible airport scenery. Documented companion files for approaches, navaids or elevation may still be required, but obsolete layout duplicates should remain disabled.
- Correct the priority. Place the intended airport package at a higher Scenery Library priority than broad regional scenery covering the same location. Removing an unnecessary duplicate is safer than depending on priority to hide it.
- Restart and retest. Let FS2004 rebuild its scenery database after changes, then inspect the outside view, Map, GPS, starting positions and ATC runway list.
A higher-priority airport definition can contain instructions that remove stock runways before adding its own. If that replacement is old or incomplete, it may delete every original runway and add back only some of them.
If edits appear to have no effect on a modern Windows installation, check that you changed the copy FS2004 is actually loading. Legacy installations under a protected system folder can leave duplicate or redirected add-on files in a per-user location.
What if the default FS2004 runway is still missing?
If the runway remains absent with the relevant add-ons disabled, it either never existed in FS2004’s database or the stock regional scenery is inactive or damaged.
Compare the airport against information from FS2004’s release era. A runway constructed, extended or redesignated later will not appear after a repair or reinstall; it requires an updated airport definition.
If the runway belonged to the original FS2004 airport, check that the correct default regional scenery area remains active. Stock BGLs commonly contain many airports, so deleting one to repair a single field can make an entire region disappear. Use our procedure for restoring default FS2004 airports and regional files rather than substituting an unrelated BGL.
What if the runway is buried, floating or covered by terrain?
A buried or floating runway is present but being drawn at the wrong elevation, so replacing the layout AFCAD alone will not fix it.
Temporarily disable terrain mesh, regional scenery and any separate airport-elevation correction supplied with the add-on. Some packages install elevation files outside the main airport folder, which means disabling the airport’s library entry may leave the conflicting correction active.
If removing the conflicting file is not appropriate, the airport may need a correctly positioned flatten. Follow the checks in our FS2004 airport-flatten guide before creating one; an incorrect flatten can produce plateaux, trenches or sharp terrain edges.
Can I add a runway that FS2004 never included?
You can add a missing runway with an FS2004-compatible airport editor, but the compiled BGL should be installed as an add-on rather than overwriting Microsoft’s stock scenery.
- Start with the correct airport identifier, coordinates and elevation.
- Enter the runway’s heading, designators, dimensions, surface and lighting accurately.
- Add runway start positions so it appears in the flight-selection menu.
- Connect it to the taxi network if AI aircraft must use it.
- Disable older layout AFCADs for the same airport.
A layout BGL creates functional airport data; it does not automatically supply matching terminals, ground photographs or custom textures. When using a complete replacement package, follow the correct FS2004 scenery-folder and Scenery Library installation process so its visual files and airport definition load together.
Why does ATC or AI traffic ignore a visible runway?
A visible runway may be unusable because it lacks functional facility data, is closed for take-off or landing, has no valid start, or is disconnected from the taxi network.
If the runway is absent from Map and GPS, the visible surface is probably only a scenery object or texture. If it is listed there, inspect its open or closed settings, runway starts, taxi links and hold-short nodes. Wind direction can also cause FS2004 ATC to select another runway even when the runway itself is correctly defined.