How do I make AI aircraft flyable in FSX?

To make an AI aircraft flyable in FSX or FSX: Steam Edition, give its aircraft.cfg a valid user-selection entry, then add or alias a cockpit panel and sounds from a compatible flyable aircraft. Keep the original title= and flight-dynamics files so existing AI traffic plans continue to recognise it.

What can an AI-to-flyable conversion actually add?

A conversion can make a genuine AI SimObject selectable and provide a 2D cockpit and sound, but it cannot create model features that were never built. Most AI models contain an external aircraft only, so editing configuration files will not add a virtual cockpit, detailed systems or a pilot-quality flight model.

The aircraft folder must contain an aircraft.cfg, an AIR file, model files and textures. Static aircraft compiled into airport scenery are scenery objects rather than aircraft containers and cannot be made flyable this way.

How do I convert the AI aircraft?

The safest method is to preserve the AI model and its flight dynamics, expose an existing livery in the aircraft selector, and alias only the panel and sounds. Our worked AI-to-flyable conversion procedure provides a file-by-file example.

1. Close FSX and back up the aircraft folder. It will normally be under SimObjects\Airplanes, although the installation root differs between boxed FSX, Steam Edition and custom installations. See our guidance on locating and editing aircraft.cfg safely before changing a protected installation.
2. Choose a suitable donor aircraft. Use an installed flyable aircraft with a similar cockpit, engine type and engine count. A stock FSX aircraft is usually safer than a complex add-on whose gauges may depend on extra modules.
3. Edit an existing livery section. In a section such as [fltsim.0], retain the original title=, sim=, model= and texture= values. Add or correct the user-facing fields:
   • ui_manufacturer=Manufacturer
   • ui_type=Aircraft type
   • ui_variation=Livery name
   • ui_typerole=Commercial Airliner
   • ui_createdby=Original developer

   Each [fltsim.n] section must have a unique number and a globally unique title=. Do not create a second section with the same title.

4. Check the aircraft references. The value after sim= must match the AIR file’s base name. Under [General], verify that Category=airplane is present. Setting editable=1 permits changes through FSX’s aircraft-details interface, but it does not create a cockpit or make the model flyable by itself.
5. Create a panel alias. Make a standard panel folder inside the AI aircraft folder and place a panel.cfg in it containing:
   • [fltsim]
   • alias=DonorAircraftFolder\panel

   Replace DonorAircraftFolder with the donor’s exact folder name, not its menu display name. Set panel= to blank in the converted livery entry. A value such as panel=ai makes FSX look for a folder named panel.ai instead.

6. Create a sound alias. Make a sound folder containing a sound.cfg with:
   • [fltsim]
   • alias=DonorAircraftFolder\sound

   Leave sound= blank in the livery entry so FSX uses that standard folder.

7. Restart FSX and load the aircraft. Search under the manufacturer, type and variation entered in the configuration. FSX reads aircraft containers during start-up, so an open session will not reliably detect the changes.

Why does the AI aircraft not appear in the FSX menu?

A converted aircraft usually remains missing because FSX cannot parse its livery entry, cannot find a referenced file or is filtering the entry under unexpected UI names.

If the entry is valid but difficult to find, check how FSX organises and filters aircraft in its selection menu. When saved edits seem to disappear, Program Files permissions, Windows VirtualStore or editing the wrong installation are common causes; use these checks for aircraft.cfg changes that appear to be ignored.

Will the converted aircraft still work as AI traffic?

Yes, the same aircraft can remain available to AI traffic if its original title= is unchanged. Traffic schedules normally identify an aircraft by that exact title string, not by its folder name or ui_type=.

A mistake we see constantly is renaming the title to make the aircraft look tidier in the selection menu. Change the ui_ fields instead; changing the title can cause traffic plans to lose the aircraft.

Why is there no virtual cockpit or realistic handling?

An aircraft.cfg edit cannot add a virtual cockpit because the cockpit geometry must be built into the model. An aliased 2D panel is therefore the practical option for most AI aircraft.

Do not blindly copy the donor’s AIR file or entire configuration. Weight, contact points, engines, gear position and animations may no longer match the AI model. Use a model-specific flyable flight-dynamics package when one is available and permitted; otherwise, treat the conversion as suitable for casual flying rather than accurate systems or handling.

Panel and sound aliases are sensible for private use because they avoid duplicating files. Do not redistribute Microsoft, freeware or commercial donor files unless their licence explicitly permits it.