Learn which FS2004 aircraft work in FSX, where to install them, and how to fix missing aircraft, blank panels, broken textures and gauges.
Many FS2004 aircraft add-ons can work in FSX because FSX retains partial support for older aircraft models. Install the complete aircraft folder in SimObjects\Airplanes, then copy any supplied gauges and effects to their matching FSX folders. Compatibility is not guaranteed: old gauges, custom modules, aliases and animations are the usual failures.
Which FS2004 aircraft will work in FSX?
Aircraft built for FS2004 with a conventional model, a complete panel and no unusual external modules have the best chance of working in FSX.
| FS2004 package | Likely result in FSX | Recommended action |
|---|---|---|
| Complete aircraft with standard FS2004 model and gauges | Often usable as a legacy port-over | Install manually and test the cockpit, animations, lights and sounds |
| Aircraft using custom DLLs or very old gauge formats | May show missing instruments, errors or crashes | Find an FSX-compatible panel or remove the incompatible component |
| Texture or repaint package only | Will not appear as a standalone aircraft | Install the exact base aircraft first and add the repaint entry |
| Older FS2002 or FS98 aircraft described as FS2004-compatible | Compatibility is much less likely | Use an FSX-native alternative where possible |
An aircraft that loads remains a port-over; FSX does not automatically convert its model. Propeller transparency, materials, virtual-cockpit controls and animations can still behave differently. Our explanation of the compatibility differences between FS2004 and FSX covers why some components survive the move while others fail.
How do I install an FS2004 aircraft in FSX?
The safest method is to inspect the package and install it manually rather than aiming an old FS2004 installer at the FSX directory.
- Extract the download to a temporary folder. A complete aircraft normally contains
aircraft.cfg, an.airfile and folders such asmodel,panel,soundandtexture. If it contains only a texture folder and installation text, it is probably a repaint; use the repaint and aircraft.cfg installation method instead. - Locate the FSX installation folder. Boxed FSX is commonly under
Microsoft Games\Microsoft Flight Simulator X. Steam installations are normally underSteamLibrary\steamapps\common\FSX, although either edition can be installed elsewhere. - Copy the complete aircraft folder. Place it inside
FSX\SimObjects\Airplanes. The correct structure isSimObjects\Airplanes\AircraftName\aircraft.cfg. An extra nested folder is one of the most common reasons an aircraft does not appear. - Install shared files selectively. Copy supplied
.fxfiles intoFSX\Effects. Put gauge files, gauge folders or gauge cabinets inFSX\Gaugesonly when the package instructions require it. Keep the aircraft's ownmodel,panel,soundandtexturefolders with the aircraft. - Do not overwrite files blindly. Back up any existing file before replacing it. An FS2004 DLL or module should not be copied into FSX unless the documentation explicitly confirms FSX compatibility.
- Check the aircraft configuration. At least one valid
[fltsim.0]entry must exist, itstitle=value must be unique, and itssim=value must match the name of the supplied.airfile. - Start FSX and test the aircraft. Look under the manufacturer and aircraft type defined in
aircraft.cfg. Test first in a simple daytime flight, then check the panel, engine start, control surfaces, undercarriage, lights and sounds.
For packages already designed for FSX, our standard aircraft folder and component instructions explain the normal layout in more detail.
What changes for FSX: Steam Edition?
FSX: Steam Edition uses the same SimObjects\Airplanes structure, but its installation root is different from boxed FSX.
Old installers may search for Flight Simulator 9 or boxed FSX in the Windows registry and then report that the simulator is missing. If the installer permits a custom destination, extract to a temporary folder and move the aircraft manually. Do not allow it to create an Aircraft folder directly inside FSX; that was the FS2004 arrangement. See our guidance on handling legacy add-ons and installers in Steam Edition for the path-specific caveats.
Why does the aircraft not appear or work properly?
Most failed FS2004 aircraft installations can be traced to folder nesting, a broken configuration entry, a missing alias or an incompatible gauge.
| Symptom | Likely cause | What to check |
|---|---|---|
| Aircraft is absent from the selection menu | Extra folder level, missing [fltsim] entry, mismatched sim= value or duplicate title | Confirm that aircraft.cfg sits directly inside the aircraft folder and that the referenced .air file exists |
| Panel is black or gauges are missing | Unsupported gauge, missing gauge cabinet or an alias to an FS2004 aircraft that FSX does not include | Inspect panel.cfg and substitute an FSX-compatible panel or gauges |
| No engine or cockpit sound | sound.cfg aliases an absent FS2004 default aircraft | Use a self-contained sound folder or change the alias to an installed compatible sound set |
| White textures, opaque windows or a solid propeller disc | Missing texture files, incorrect texture= value, broken fallback path or legacy rendering issue | Verify the texture folder name and test with FSX's DirectX 10 Preview disabled |
| FSX crashes when the aircraft loads | Incompatible gauge, DLL or panel component | Back up the package, test with a known-compatible panel and restore components individually |
| Doors, undercarriage or cockpit controls do not animate correctly | The FS2004 model is not fully compatible with FSX | Use an FSX-native model; configuration edits cannot repair model-level animation code |
Can I convert an incompatible FS2004 aircraft to FSX?
A true FSX-native conversion normally requires the original model source files, an appropriate FSX export workflow and the author's permission.
Editing aircraft.cfg, moving folders or replacing gauges can repair configuration, panel and sound problems, but it cannot rebuild an incompatible model. Replace individual components when the aircraft itself displays and flies correctly; choose an FSX-native edition when the exterior model, virtual cockpit or essential animations fail.