Can FS2004 aircraft work in FSX and vice versa?

Many FS2004 (FS9) aircraft can work in Microsoft Flight Simulator X (FSX) and FSX: Steam Edition as port-overs, although gauges, textures, animations or effects may fail. Native FSX aircraft generally cannot work in FS2004 because the older simulator cannot read models compiled in the newer FSX format.

FSX vs FS2004 compatibility at a glance

Compatibility is asymmetric: FSX retained support for many older FS2004 models, but FS2004 was not designed to interpret native FSX models.

FS2004, also called FS9, is Microsoft Flight Simulator 2004: A Century of Flight. In this context, an old Microsoft Flight Simulator aircraft means that FS2004 generation; Microsoft Flight Simulator 2020 and 2024 use different add-on systems.

An archive labelled for FSX is not necessarily native FSX. Many older aircraft were repackaged or adjusted for FSX while retaining an FS2004-format visual model. Conversely, an FSX-adjusted port-over may contain FSX-only gauges or configuration changes, so copying that modified package back into FS2004 is unreliable.

Why does compatibility mostly work in one direction?

The compiled .mdl visual model determines whether the simulator can read the aircraft.

FSX can load many models compiled with the FS2004 tools. FS2004 cannot load a model compiled in the native FSX format because that format did not exist when the older simulator was produced. This is why changing aircraft.cfg, replacing the .air file or moving textures cannot convert a native FSX aircraft into an FS2004 aircraft.

The same generation gap affects gauges, materials, animations and other add-on components. Our breakdown of the practical differences between FS2004 and FSX provides the wider simulator context.

What can break when an FS2004 aircraft is used in FSX?

An FS2004 aircraft may appear in the FSX aircraft-selection menu while still having serious compatibility faults.

• Blank instruments or panels: required gauge files may be missing, blocked or incompatible. Some panels depend on gauges installed with an FS2004 default aircraft that FSX does not include.
• Black, opaque or invisible windows: FSX handles some legacy material and texture-alpha settings differently.
• Propeller or rotor artefacts: prop discs can become opaque or sort incorrectly against clouds and scenery. DX10 Preview can make some FS2004 transparency problems more obvious.
• Broken animations: doors, landing gear, control surfaces or virtual-cockpit controls may not respond as their developer intended.
• No sound: the sound.cfg file may alias a default FS2004 aircraft that is absent from FSX.
• Missing lights, smoke or afterburners: the aircraft may rely on effect files that were not installed in the FSX Effects folder.
• Different flight behaviour: FS2004 flight-dynamics files can load, but the aircraft may not perform exactly as it did in FS2004.
• A crash when selecting the aircraft: an obsolete gauge or module can fail even though the visual model itself is readable.

Use an FSX-specific update when the package supplies one. Disabling DX10 Preview is also a useful diagnostic for transparency and propeller problems, but it will not repair missing gauges, bad aliases or unsupported animations.

Why doesn't an FS2004 aircraft show up in FSX?

If an aircraft does not show up in FSX, an incomplete package, wrong folder or configuration error is more likely than model incompatibility.

1. Confirm that it is a complete aircraft. A normal package should include aircraft.cfg, an .air file and a model folder containing an .mdl file. A repaint or update cannot appear as an independent aircraft unless its required base model is already installed.
2. Check the destination. The aircraft folder belongs under the FSX SimObjects\Airplanes directory, not the FS2004 Aircraft directory.
3. Remove extra folder nesting. The correct layout is SimObjects\Airplanes\AircraftName\aircraft.cfg. A common mistake is ending up with another AircraftName folder between the aircraft directory and aircraft.cfg.
4. Inspect the aircraft entries. The configuration should contain a [fltsim.0] section, followed by sequentially numbered variations. Each title= value must be unique. Missing or unsuitable ui_manufacturer=, ui_type= and ui_variation= entries can also make the aircraft difficult to find under the menu filters.
5. Verify the referenced files. The sim= value must correspond to the installed .air file, while the model= value must point to the appropriate model-folder suffix. Panel and sound aliases must refer to aircraft that exist in FSX.
6. Restart FSX and show all variations. FSX does not reliably rescan every aircraft change while running. Enable the aircraft-selection option to show all variations so a hidden livery is not mistaken for a failed installation.
7. Test without optional gauges or modules. If the aircraft appears but FSX crashes while loading it, an old panel component may be responsible. Keep backups and do not overwrite default FSX files while diagnosing the package.

A filename such as VFSX-2004UP does not by itself establish the simulator version or prove that it is a complete aircraft. Read the included documentation and inspect the contents. If the archive contains only replacement models, textures, effects or configuration fragments, it expects a separate base package and will not show up on its own.

For the complete folder procedure and the most common installer mistakes, follow our step-by-step method for installing FS2004 aircraft in FSX.

Does FSX: Steam Edition change the answer?

FSX: Steam Edition uses the same basic FSX aircraft formats, so the model-compatibility answer is broadly unchanged.

The main differences are installation and supporting components. An old automatic installer may search for the boxed FSX location or write files somewhere other than the active Steam library. Verify that the aircraft actually reached the Steam installation's SimObjects\Airplanes directory rather than trusting an installer-complete message.

Legacy compiled gauges and modules can also depend on files or registration details that are missing from a Steam installation. If the external model loads but the panel is blank or the simulator crashes when the cockpit opens, diagnose the gauges before blaming the aircraft model.

Which aircraft version should I download?

Choose the version built specifically for your simulator whenever one is available.

• For FSX or FSX: Steam Edition: choose a native FSX release over an FS2004 port-over. It is more likely to have correct FSX materials, animations, virtual-cockpit features and gauges.
• For FS2004: choose the original FS2004 package. A native FSX edition will not work.
• For a dual-format download: install only the folders and supporting files identified for your simulator.
• When only an FS2004 version exists: try it in FSX if the documentation permits port-over use, but expect that some faults may have no practical fix.

Freeware describes the cost of an add-on, not its simulator format or compatibility. A freeware upload may be a complete native aircraft, an FS2004 port-over, a repaint or just an update. Check the stated simulator and required base model when browsing our freeware aircraft and add-on library.

Can a native FSX aircraft be converted to FS2004?

A native FSX aircraft cannot be converted to FS2004 through configuration-file edits or an ordinary file conversion.

A proper rebuild requires suitable source geometry, textures and animation data, an FS2004-compatible export process, replacement of unsupported systems and permission from the original developer. The compiled FSX .mdl alone is not an installable source project.

This is aircraft development rather than add-on installation. Our explanation of the files and tools involved in creating an FS2004 aircraft shows why a dedicated FS2004 model must be produced. If a download claims to support both simulators, use the separate FS2004 files supplied by its developer rather than trying to convert the native FSX model.