Find why AI traffic is missing at one FSX airport, then fix schedules, scenery conflicts, parking spots, taxi links and runway data.
AI traffic is usually missing at one airport in FSX because no active flight plan serves it at that time, or the airport’s scenery lacks usable parking, taxi links, runway starts or a valid ICAO. Duplicate airport files and undersized parking spots can also prevent aircraft from spawning or operating.
FSX and FSX: Steam Edition use the same basic AI traffic and airport-facility logic. If aircraft appear normally elsewhere, concentrate on the affected airport rather than reinstalling the entire traffic package.
Why does AI traffic appear elsewhere but not at one airport?
An airport-specific failure normally points to its schedule, code or scenery data. The quickest clues come from what the aircraft does—or fails to do.
| Symptom | Likely cause | First check |
|---|---|---|
| No AI at any time | No matching flight plan, wrong ICAO or incomplete airport data | Test a known schedule and inspect the airport record |
| Traffic appears only at high density | The flight plan has a higher density threshold | Temporarily set the relevant AI slider to 100% |
| Aircraft approach but disappear | No suitable vacant parking or no connected route from the runway | Check parking radius and taxi links |
| Aircraft park but never depart | Broken taxi network, invalid hold-short link or unusable departure runway | Inspect the route from parking to the runway |
| The stock airport works but the add-on does not | Faulty or conflicting airport-facility BGL | Disable the add-on scenery layer and retest |
If AI is absent at every airport, this is probably a system-wide traffic problem instead. Work through our checks for FSX traffic sliders, BGL conflicts and missing aircraft models before changing the airport.
How do I diagnose the affected FSX airport?
- Confirm that the problem is local. Load a large default airport at the same simulator date and time. If the same traffic package appears there, its aircraft models and traffic BGL are being read.
- Raise the correct traffic slider temporarily. Airline and general aviation traffic have separate sliders. A compiled flight plan appears only when its assigned density threshold is met.
- Check the schedule and ICAO. Make sure at least one flight plan actually uses the airport’s FSX identifier. Traffic schedules are commonly compiled against UTC, so loading the expected local time can put the flight outside its operating window. Load the flight before its departure time rather than waiting at the exact minute.
- Test available parking. Move the user aircraft away from the airport and try again. The airport needs a vacant spot large enough for the AI aircraft; parking type and airline codes can also affect where it is allocated.
- Disable the add-on airport temporarily. Use the FSX Scenery Library with the simulator closed, restart FSX and test the default airport. If traffic returns, the add-on contains incomplete airport data or is conflicting with another airport BGL.
- Inspect the active airport facility record. With an FSX-compatible airport editor, check for runway start positions, valid runway links, correctly placed hold-short nodes, connected taxi paths and suitable parking spots. The taxi network must form an unbroken route between parking and an operational runway.
A mistake we see constantly is assuming detailed buildings and ground textures mean that an airport supports AI. Those are visual scenery elements; AI requires a separate airport-facility definition. Some small scenery packages, such as the airports described in this collection of Australian FSX airfields, include locations where incomplete runway or taxiway data prevents normal AI operation.
Can duplicate airport files remove AI traffic?
Two airport-facility BGLs for the same ICAO can produce missing parking, displaced taxi routes or conflicting runway data. The higher-priority scenery layer may override or partially combine with another version of the airport.
Disable suspected scenery areas one at a time and restart FSX after each change. Keep one corrected airport-facility file active for that ICAO, and never delete or modify the simulator’s default APX files. Searching only by filename is unreliable because an airport BGL does not have to include its ICAO in the name.
Why do AI aircraft land and then disappear?
An AI aircraft that lands successfully but vanishes usually cannot find a suitable parking position or a valid taxi route to one. Check that the parking radius accommodates the aircraft, that a spot is free, and that every taxi link connects correctly from the runway exit to parking.
If the aircraft stops indefinitely on the runway or near the holding point, inspect runway links and hold-short nodes as well. A hold-short point that is missing, disconnected or badly positioned can stop departures and interfere with runway use.
What should I fix: the traffic plan or the airport?
Fix the traffic plan when the airport works with other AI aircraft but your intended service never appears. Confirm the ICAO, aircraft title, operating day, UTC time and density value; our custom FSX AI schedule troubleshooting steps cover those checks in detail.
Fix or replace the airport-facility BGL when no suitable AI can use the airport, when arrivals disappear, or when disabling the add-on restores traffic. A visual-only airfield needs a complete facility record with parking, taxi paths, runway links and starts—not merely more scenery objects.