Learn how to add static or moving airport ground vehicles in FS2004, install the scenery correctly, and fix missing objects or animation.
To add airport ground vehicles in FS2004 (FS9), install a scenery or object package containing the vehicle models, place its scenery and texture files in the correct add-on scenery folders, then activate that area in the Scenery Library. Moving vehicles require animation or AI traffic code; AFCAD alone cannot create them.
Choose the right FS2004 ground-vehicle method
The right method depends on whether you want parked equipment, background movement or vehicles that interact with a particular aircraft.
| Method | What it does | Best used when |
|---|---|---|
| Static scenery objects | Places fixed tugs, buses, fuel bowsers and baggage carts | You want predictable ramp detail with little complexity |
| Animated scenery | Moves objects along a route built into the model or scenery | You want ambient movement without ATC interaction |
| AI-style vehicles | Uses aircraft-format models and traffic schedules to make vehicles follow AI logic | The package was specifically designed for an FS2004 taxi network |
| Aircraft-specific services | Displays equipment around a compatible add-on aircraft | You want vehicles positioned at your own parking stand |
Most users should choose static or pre-animated scenery. Our FS2004 scenery library includes airport packages that may already contain ramp equipment. A moving jetway add-on demonstrates the same principle used by animated ground objects: the movement must be built into the package rather than added by AFCAD.
How do I install a downloaded vehicle package?
A downloaded FS2004 vehicle set should normally be installed as a self-contained scenery area. Package-specific instructions take priority, but the standard arrangement is covered in our complete FS2004 scenery-installation steps.
- Confirm FS2004 compatibility. The package should explicitly support FS2004 or FS9. Do not assume an FSX or Prepar3D model, library or traffic file will work in FS2004.
- Create a dedicated scenery area. Under the simulator's
Addon Sceneryfolder, create a package folder with siblingsceneryandtexturefolders—for example,FS2004\Addon Scenery\Airport Vehicles\sceneryandFS2004\Addon Scenery\Airport Vehicles\texture. - Copy each file to its intended location. Scenery and object-library
.bglfiles normally go inscenery; model textures go intexture. Copy effects, sounds, AI models or traffic files only where the package documentation specifies. - Activate the scenery. Open the FS2004 Scenery Library, add the package's root folder—not its
scenerysubfolder—and leave the area enabled. Restart FS2004 so it can rebuild the scenery database. - Test at the intended airport. Check the airport, stand, time and traffic level named by the package. Raise Scenery Complexity; for some implementations, Dynamic Scenery or AI traffic settings also control whether movement appears.
Keep the package separate instead of scattering its files through stock scenery folders. That makes priority changes, troubleshooting and removal much safer. Do not place vehicle models in the Aircraft folder unless the package deliberately uses them as AI aircraft.
Can I place static ground vehicles myself?
Yes—static vehicles can be placed with an FS2004-compatible scenery design tool and a vehicle object library.
- Install the object library and all of its supplied textures in an active scenery area.
- Create placement records for the required vehicle objects using their library identifiers, airport coordinates, heading and altitude settings.
- Compile the placements into an FS2004 scenery
.bglusing a compatible design tool or the FS2004 BGLComp scenery compiler. - Store the placement file separately in your own airport-vehicle scenery area, then activate and test it in FS2004.
Placing a library object only makes it visible; it does not give the object a route or service logic. Also, an FS2004-compatible airport-layout editor can adjust parking spots and taxi links, but AFCAD does not place visible vehicles. It becomes relevant only when an AI-style vehicle package needs better parking or taxi routing.
Why are the vehicles missing or not moving?
Missing FS2004 ground vehicles usually indicate an inactive scenery area, absent library files, unsuitable display settings or an incompatible package.
- Nothing appears: Check that the selected Scenery Library folder directly contains the
sceneryandtexturesubfolders. An extra nested package folder is a common installation mistake. - Some vehicles appear but others do not: Install every required shared-object library and its textures. A placement BGL can reference models that are supplied separately.
- Objects are black, untextured or invisible: Recheck the texture folder and preserve the supplied filenames. FS2004 scenery often depends on exact texture names.
- Vehicles remain stationary: Static objects are behaving correctly. For an animated or AI package, check Dynamic Scenery, AI traffic percentage, the specified time or schedule, and any activation command described by the author.
- Vehicles are buried or floating: The placement altitude may not match the airport's elevation or terrain flatten. Correct the placement rather than moving the object library itself.
- Objects vanish with another airport installed: Move the vehicle scenery above the conflicting airport area in the Scenery Library and check for exclusion files.
- FS2004 crashes near the airport: Remove the newest vehicle or library BGL first, then look for an incompatible model, damaged file or duplicate package installation.
Will FS2004 ground vehicles service my aircraft?
Usually not: generic FS2004 scenery vehicles follow fixed animation or AI rules and do not recognise your parked aircraft.
For baggage carts, stairs, buses or tugs positioned around your aircraft, use a service package designed for that specific aircraft or add-on system. Avoid combining it with static objects at the same stand, or the models may overlap. AI-style vehicles can use taxi routes, but they may also obstruct aircraft, enter runways or trigger unwanted ATC behaviour if the package was not carefully designed for the airport.