How do I use AFCAD to edit FS2004 airport layouts?

To edit an airport in Flight Simulator 2004, open its active facility file in AFCAD 2, modify runways, taxi links, parking or frequencies, then save the result as a new BGL in an active scenery folder. Keep the stock file untouched, remove competing AFCADs, and restart FS2004 to load the change.

What can AFCAD edit in FS2004?

AFCAD edits the airport facility data that FS2004 uses for runways, taxi routes, parking, AI traffic and ATC. It is not a general-purpose scenery-object editor.

You can examine ready-made FS2004 airport layout files to see how these elements are arranged before changing a busy airport.

Can AFCAD move terminals and scenery objects?

AFCAD cannot move a terminal model, hangar, windsock or other separately placed scenery object. It can alter facility-generated pavement, but it will not redraw custom ground textures or photographic scenery.

If a taxiway line no longer matches a terminal or custom apron, changing the AFCAD alone may make AI traffic work while leaving the visible scenery misaligned. Object placement and custom scenery construction require other FS2004 development tools; our FS2004 SDK guidance explains that separate workflow.

How do I edit an FS2004 airport with AFCAD?

1. Install the FS2004 version. Use the FS2004-compatible AFCAD 2.21 editor and make sure it can locate your FS2004 installation and scenery configuration.
2. Close FS2004 and make a backup. Copy any existing add-on airport BGL before editing it. Never overwrite, move or delete the simulator's core stock scenery files.
3. Open the correct airport. Use File > Open Airport, search by ICAO identifier and inspect the available airport sources. If an add-on airport is installed, edit the facility file belonging to that package rather than starting from the lower-priority stock layout.
4. Save a working copy. Put the edited BGL in the scenery subfolder of an active scenery area. A dedicated location such as <FS2004>\Addon Scenery\My AFCAD\scenery makes later removal easier. Add its parent folder through the FS2004 Scenery Library if it is not already active.
5. Edit the layout. Select existing runways, links, nodes or parking spots and open their properties to change exact values. Use AFCAD's placement tools for new elements, zooming in far enough to join links to the intended nodes.
6. Complete the taxi network. Connect each parking spot to a continuous taxi route, connect that route to the runway system, and preserve correctly placed hold-short nodes. A line that appears to touch another line may still be disconnected.
7. Check parking properties. Set a suitable radius and choose the intended gate, ramp or cargo type. Airline assignments only work when the AI aircraft's own parking codes and types correspond to the stand.
8. Validate, save and restart. Run AFCAD's fault-checking function, correct broken links and save the compiled BGL. A descriptive name such as AF2_EGLL.bgl is useful but not mandatory. Restart FS2004 so it rebuilds or reloads the relevant scenery data.

How do I stop AI aircraft getting stuck?

AI aircraft need one continuous, correctly typed route from a parking spot to the active runway. Most failures are caused by a disconnected node, an unsuitable parking stand or a broken runway connection.

• Inspect every junction: links must terminate on the same node. Crossing or overlapping lines do not automatically form a junction.
• Check link types: ordinary taxi links, apron routes and runway links have different jobs. An incorrectly typed segment can prevent ATC from finding a usable route.
• Protect runway entrances: keep hold-short points on the connected taxi route and reasonably close to the runway boundary. Missing or badly positioned holds can disrupt departures.
• Match parking size: a stand that is too small will not be selected for a larger AI aircraft. Avoid packing stands so tightly that parked aircraft overlap even when their nominal radii fit.
• Match parking codes: airline codes influence stand selection; they do not create AI flights. Leave codes unrestricted when several operators must share the stand.
• Check stand orientation: the parking heading and link geometry affect how an aircraft sits and pushes back.

A detailed Schiphol layout example is useful for studying gate numbering, airline assignments, parking categories and complex taxi routing.

Why are my AFCAD changes not showing in FS2004?

Changes usually fail to appear because FS2004 is loading another airport definition, the new BGL is outside an active scenery area, or the simulator has not reloaded its scenery database.

• Inactive scenery folder: confirm that the BGL is inside an active area's scenery subfolder, not beside that folder or inside texture.
• Competing add-on AFCAD: a higher-priority airport BGL may override your version. Aim to have one intentional add-on facility definition for the airport, while leaving the stock scenery files alone.
• Wrong source edited: add-on airports often supply their own AFCAD. Editing a copy of the stock airport will not reliably preserve the add-on's gates and taxi routes.
• File permissions: older simulators installed under a protected Windows directory may prevent AFCAD from writing where expected. Verify that the BGL was actually created and has a new modification time.
• Simulator still running: FS2004 does not reliably reload a replaced airport BGL during the same session. Exit fully and restart it.
• Visual scenery is separate: an unchanged terminal or ground texture does not prove the AFCAD failed. Test parking positions, ATC taxi instructions and AI movement as well as the visible pavement.

Do not search only for files named after the ICAO code; an AFCAD BGL can have almost any filename. Use AFCAD's airport-source information and disable suspected add-on scenery layers one at a time when tracing a conflict.

How should I test an edited airport?

Test the layout with both a flyable aircraft and AI traffic before adding more gates or making further runway changes.

• Start from several edited parking stands and confirm that the aircraft appears in the correct position and heading.
• Request taxi clearance, follow the assigned route and check that progressive taxi does not take an impossible path.
• Observe AI departures and arrivals at normal simulation speed, paying particular attention to runway exits, hold-short points and pushbacks.
• Test aircraft of different sizes so that parking-radius errors become obvious.
• Keep the previous BGL outside every active scenery folder until the revised layout has passed testing.