How do I make an AI aircraft flyable in FS2004?

To make an AI aircraft flyable in FS2004, add valid user-interface entries to its aircraft.cfg and ensure sim= references its AIR file. For a usable conversion, also supply a compatible 2D panel, sounds and flight dynamics. Configuration edits cannot give an AI-only model a true virtual cockpit.

What sort of AI-to-flyable conversion is possible?

FS2004 can expose almost any correctly installed AI aircraft in the aircraft selection menu, but the result depends on how much work you put into the conversion.

AI models are built for efficient external rendering. They often have aggressive levels of detail, simplified animations, no interior and flight dynamics designed to follow traffic instructions rather than feel convincing through a joystick.

How do I make the AI aircraft selectable and flyable?

The safest method is to preserve the original traffic entry, create a separate user-selectable variation and add each missing component methodically.

1. Back up the complete aircraft folder. It will normally be inside the FS2004 Aircraft directory. Keep the original aircraft.cfg and AIR file untouched in the backup, and check the add-on's licence before redistributing any conversion. Our breakdown of FS2004 aircraft folders and core files explains how the model, configuration, panel, sound and flight-dynamics files relate to one another.
2. Open aircraft.cfg in a plain-text editor. Find an existing section such as [fltsim.0]. You may add the display fields to that section, but copying it to the next consecutively numbered [fltsim.x] section leaves the original traffic entry intact.
3. Give the copied entry a unique title. Change title= in the copy only. Duplicate titles can cause an entry to be rejected, while changing the original title can break traffic plans that refer to it.
4. Add the three FS2004 menu fields. The copied section needs entries such as ui_manufacturer="Cessna", ui_type="402" and ui_variation="Operator livery". These values determine where the aircraft appears in the selection menu.
5. Check every folder reference. The value after sim= must match the AIR filename without the .air extension. The model=, texture=, panel= and sound= values select folders named model, texture, panel and sound, or their suffixed variants. A blank panel=, for example, selects the ordinary panel folder.
6. Install or alias a compatible 2D panel. If the AI package has no panel, create a panel folder containing a valid FS2004 panel.cfg. It can contain a complete panel or an alias to the panel folder of another installed FS2004 aircraft. Match the aircraft type, engine arrangement and instrument layout where possible; an FS2004 two-dimensional Cessna 402 panel, for example, is suitable only for a compatible 401/402-style conversion. An FSX-only panel or missing gauges may produce a blank panel in FS2004.
7. Add or alias a sound set. Use a sound package matching the number and type of engines. A sound alias is normally defined in sound.cfg and must point to the exact folder name of an aircraft that remains installed.
8. Evaluate the flight dynamics before replacing them. The AI aircraft should already have an AIR file and relevant aircraft.cfg sections, so test those first. If handling is unsuitable, use a legally reusable donor package closely matching the real aircraft's dimensions, weight, engine type, power, fuel arrangement and performance. Treat the donor AIR file and its aerodynamic, engine and weight configuration as a matched set; mixing unrelated parts often causes unstable pitch, incorrect power or engines that will not start.
9. Test from a simple runway flight. Check engine operation, throttle, propeller and mixture controls where applicable, brakes, steering, trim, flaps, gear and stall behaviour. Then verify take-off acceleration, cruise performance and approach speeds against credible figures for the aircraft type.

Why does the converted aircraft not appear in FS2004?

A missing aircraft normally indicates a configuration error rather than a panel or sound problem.

• Missing UI fields: confirm that the chosen [fltsim.x] entry contains all three ui_ values.
• Broken numbering: keep the [fltsim.0], [fltsim.1] and later sections consecutively numbered without duplicate section numbers.
• Invalid AIR reference: make sure sim=MyAircraft has a corresponding MyAircraft.air file in the same aircraft folder.
• Duplicate title: every title= value should be unique across the installed aircraft collection.
• Wrong file format: verify that Windows has not saved the file as aircraft.cfg.txt.
• Wrong installation copy: installations under protected Windows folders can redirect or block edits. Confirm that you changed the configuration file FS2004 is actually reading, then restart the simulator.

Why is the AI aircraft visible but difficult to fly?

An aircraft that loads successfully but behaves badly usually has an unsuitable flight-dynamics package or mismatched geometry settings.

Why is there no virtual cockpit?

A virtual cockpit must be part of the compiled visual model; no aircraft.cfg or panel alias can create one. A working 2D panel is the practical solution unless the original model source is available for an authorised rebuild.

Why does it sink, float or tip over on the runway?

The [contact_points], centre of gravity and static-position values must fit the AI model's geometry. Copying them from an aircraft with different gear spacing or fuselage dimensions causes this fault. Use our contact-point checks for aircraft sitting incorrectly on the runway before changing the visual model.

Will the converted aircraft still work as AI traffic?

Yes. Adding ui_manufacturer, ui_type and ui_variation does not stop FS2004 using that aircraft for traffic. Preserve the original title= entry because compiled traffic plans identify the assigned aircraft through that title; our guide to FS2004 AI aircraft titles and traffic installation covers that relationship in more detail.