How do I add static aircraft to airport scenery?

To add static aircraft to flight simulator airport scenery, place an aircraft scenery model with the simulator’s scenery editor or SDK, then compile or export it as part of an airport package. Use properly licensed, low-detail models, position them at empty stands, and test parking, jetways, AI traffic and frame rate.

A static aircraft is a scenery object, not a flyable aircraft or AI vehicle. It remains where the scenery designer placed it and does not follow flight plans, respond to ground services or vacate a stand.

Which scenery editor and file format should I use?

Use the official scenery editor and asset format for the simulator that will load the airport. The overall process is similar in Microsoft Flight Simulator 2020 and 2024, FSX, Prepar3D and X-Plane, but their packages are not interchangeable.

Scenery creation tools are principally PC workflows. Console editions of Microsoft Flight Simulator do not provide normal access to project folders, compilers or manually installed community packages, so console users need scenery distributed through the simulator’s supported content system.

How do I place static aircraft at an airport?

The reliable workflow is to prepare the model, add it to the airport project, position it away from active parking and build a self-contained scenery package. If the airport itself is still being developed, our complete airport-scenery creation workflow covers the wider project, compilation and testing process.

1. Choose a scenery model. Use a stock library aircraft or a model you have permission to distribute. Do not extract and redistribute an aircraft supplied with the simulator or another add-on.
2. Prepare the asset for the target simulator. A custom model must use that simulator’s scenery format, materials and texture structure. Add sensible levels of detail and remove cockpit interiors, systems and unseen geometry that a parked background object does not need.
3. Add the model to the scenery project. Register it as a library or project asset, then create an object placement at the required latitude and longitude. In FSX and related BGL-based simulators, follow the matching SDK workflow; our FSX-specific static-aircraft placement instructions cover that version in more detail.
4. Set position, heading and altitude. Align the nose wheel with the stand centreline, check wing and tail clearance, and use ground-relative placement where the editor supports it. A bad model origin can leave the aircraft floating, buried or rotating around the wrong point.
5. Keep the stand out of active use. Static scenery does not reserve a parking position. Place it on a closed or decorative stand, or remove or relocate the corresponding spawn and AI parking point if the airport design permits that change.
6. Build and install the package. Compile or export with the tools for the exact simulator generation, install it in the appropriate add-on location and activate its scenery layer where required. Keeping static aircraft in an optional component makes later removal much easier.
7. Test in the simulator. Load the airport with AI traffic both enabled and disabled, try nearby user spawn points, inspect the aircraft at night and check it from several viewing distances. Test the packaged copy rather than relying only on the editor preview.

Can I use a flyable aircraft as a static model?

A flyable aircraft cannot normally become airport scenery simply by copying its aircraft folder. Flyable models contain simulator-specific systems, animations and often detailed interiors, while a scenery editor expects a library object in its own supported format.

Conversion is possible only when the licence permits it and the geometry can be exported legally. The model should then be optimised: remove systems and invisible parts, simplify materials, reduce texture use and create distance-based levels of detail. The mistake we see constantly is placing a full-detail flyable model around an airport several times and then blaming the entire scenery package for poor performance.

Should I use static aircraft or AI traffic?

Use static aircraft for permanent visual dressing and AI traffic for aircraft that should occupy working stands or move around the airport.

• Choose static aircraft for museum exhibits, stored airframes, maintenance areas, cargo-apron background objects and permanently closed stands.
• Choose AI traffic when aircraft should arrive, depart, taxi, change with traffic schedules or interact with operational parking positions.
• Combine both carefully by keeping static models on remote or inactive stands while reserving terminal gates for AI and the user aircraft.

Static models usually require less CPU processing than AI traffic, but they are not free. Excessive geometry, large textures, transparent materials and missing levels of detail can still reduce frame rate or cause visible object pop-in.

How do I stop static aircraft overlapping AI traffic?

Prevent overlaps by ensuring that every occupied static stand is unavailable to AI traffic and user spawning. Merely placing a model over a parking spot does not tell the simulator that the gate is occupied.

Move or remove the parking position and its taxi connection where appropriate, or place the aircraft somewhere that was never defined as active parking. Check the result at several traffic-density settings because a conflict may not appear until the airport becomes busy.

Duplicate static aircraft can also come from two airport packages loading together. Disable one scenery layer or its optional static-object component rather than deleting random shared libraries. Our guidance on isolating removable static-object files safely explains the same modular BGL principle used by many FSX packages.

Why are my static aircraft missing or displayed incorrectly?

A missing or broken static aircraft usually indicates a packaging, dependency, texture or placement problem rather than an aircraft-system fault.

• Nothing appears: confirm that the scenery package is installed and active, the object library is present, and scenery complexity or density is not filtering out the placement.
• Only some users can see it: the project probably references an object library that was not included or declared as a dependency. Referencing a stock object may also require content that another installation does not have.
• The model is white, pink or textureless: check texture paths, material compatibility and filename capitalisation. Case mismatches are especially troublesome on case-sensitive systems.
• The aircraft floats or sinks: inspect the model origin, ground-clamping option and altitude mode. Sloping aprons may require a different placement point or a corrected model origin.
• The heading or scale is wrong: apply and export model transforms before packaging, then verify the units expected by the target simulator.
• Two aircraft occupy one spot: look for stock scenery, another airport package, AI parking or an optional static-aircraft file loading at the same location.
• Performance drops near the terminal: reduce model detail, texture size and the number of unique materials; add suitable distance-based detail levels rather than relying only on fewer aircraft.

Can jetways connect to static aircraft?

Operational jetways generally cannot connect to static aircraft because the simulator does not recognise a scenery object as a serviceable aircraft. A manually positioned jetway can be arranged to meet the model visually, but automated gate logic will not treat it as parked traffic; our jetway operation and compatibility guide explains what an active aircraft must provide.