Learn how to make an FSX port of an FS2004 aircraft, install it in boxed or Steam Edition, and fix missing models, gauges and sounds.
Yes. Many FS2004 aircraft can be installed in Microsoft Flight Simulator X (FSX) and FSX: Steam Edition as legacy port-overs. Put the complete aircraft folder in SimObjects\Airplanes. Compatibility is partial, however: old gauges, DLLs, model animations, materials, and panel or sound aliases are the components most likely to fail.
Will an FS2004 aircraft work in FSX?
A self-contained FS2004 aircraft with a conventional model, standard gauges and no external modules has the best chance of working in FSX.
| FS2004 package | Likely FSX result | Recommended action |
|---|---|---|
| Complete aircraft with its own model, panel, sounds and textures | Often usable as a legacy port-over | Install manually, then test the cockpit, engines, controls, lights and animations |
| Aircraft using custom gauges, DLLs or external modules | May have blank instruments, error messages or crashes | Use confirmed FSX-compatible components or replace the panel |
| Texture or repaint package only | Will not appear as a separate aircraft | Install the exact base aircraft first, then add the repaint and its [fltsim.x] entry |
| FS2002 or FS98 model described as FS2004-compatible | Much less likely to work correctly | Choose an FSX-native model where possible |
Loading successfully does not make the aircraft FSX-native. Propeller transparency, reflective materials, virtual-cockpit controls and animations may still behave differently, particularly with DirectX 10 Preview enabled. Compatibility can also vary with the aircraft's original model format and the FSX service pack or Acceleration installation.
Our explanation of how FS2004 and FSX differ under the bonnet covers why models, gauges and scenery are not reliably interchangeable.
How do I port an FS2004 aircraft to FSX?
The safest FSX port method is to extract and inspect the package, then install its files manually instead of directing an old FS2004 installer into FSX.
- Extract the download to a temporary folder. Read any supplied instructions before moving files. A complete aircraft normally has
aircraft.cfg, an.airfile and folders such asmodel,panel,soundandtexture. A package containing only textures is a repaint and requires the named base aircraft. - Find the real FSX installation folder. Boxed FSX is often under
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X. Steam Edition is commonly underC:\Program Files (x86)\Steam\steamapps\common\FSX. Custom Steam libraries and non-default installations use different locations. - Copy the complete aircraft folder. Place it in
FSX\SimObjects\Airplanes. The required structure isSimObjects\Airplanes\AircraftName\aircraft.cfg. If extraction created an extra wrapper folder, remove that additional level. Do not put the aircraft inFSX\Aircraft;Aircraftwas the FS2004 folder arrangement. - Install shared files selectively. Supplied
.fxfiles normally belong inFSX\Effects, while shared gauge files may belong inFSX\Gauges. Preserve panel-local files and follow the package documentation. Do not copy an FS2004 DLL or module into FSX unless its documentation explicitly confirms FSX compatibility, and back up any same-named file before replacing it. - Check the configuration. At least one valid
[fltsim.0]section must exist. Itstitle=value must be unique, andsim=must match the supplied.airfilename without the extension. Values such asmodel=,panel=,sound=andtexture=must point to the corresponding suffixed folders when they are not blank. - Save the file correctly. Ensure Windows has not renamed it
aircraft.cfg.txt. If FSX is installed under a protected Windows folder, edit a copy elsewhere and copy it back with the required administrator permission rather than assuming the failed save succeeded. - Start FSX and test methodically. Begin with a simple daytime flight at a default airport. Check the exterior model, virtual and 2D cockpits, engine start, flight controls, undercarriage, doors, lights and sounds. If FSX asks whether to run a gauge or module, approve it only when the file is trusted and documented for FSX.
For a package already made for FSX, use our detailed FSX aircraft installation and folder guide rather than treating it as a port-over.
What changes for FSX: Steam Edition?
FSX: Steam Edition accepts aircraft in the same SimObjects\Airplanes structure, but its installation root and registry detection differ from boxed FSX.
An old installer may search only for Flight Simulator 9 or boxed FSX and report that no simulator is installed. Some legacy installers also cannot run on modern 64-bit Windows. If a custom destination is available, install into a temporary empty folder first and move the files manually; our guide to legacy add-ons and installers in Steam Edition explains the edition-specific path problems.
Why is the ported aircraft not showing or working in FSX?
Most failed FS2004-to-FSX ports are caused by incorrect folder depth, a broken aircraft.cfg entry, missing aliases or an incompatible gauge or module.
| Symptom | Likely cause | What to check |
|---|---|---|
| Aircraft is absent from the selection menu | Extra folder level, missing [fltsim] section, incorrect sim= value or repaint installed without its base aircraft | Confirm that aircraft.cfg is directly inside the aircraft folder and that the referenced .air file exists |
| Duplicate aircraft or object-name warning | Two variants use the same title= value | Give every [fltsim.x] section a unique title |
| Black panel or missing instruments | Unsupported gauge, missing gauge cabinet or a panel alias to an FS2004 aircraft absent from FSX | Inspect panel.cfg and use an FSX-compatible panel or gauge set |
| No cockpit or engine sound | sound.cfg aliases an unavailable FS2004 default aircraft | Use a self-contained sound folder or change the alias to a compatible installed sound set |
| White textures, opaque windows or a solid propeller disc | Missing texture files, incorrect texture= value, broken fallback path or legacy material behaviour | Verify the texture folder and fallback paths, then test with DirectX 10 Preview disabled |
| FSX crashes as the aircraft loads | Incompatible gauge, DLL, panel component or module | Back up the package, test with a known-compatible panel, then restore components individually |
| Doors, undercarriage or cockpit controls do not animate | Model-level incompatibility | Use an FSX-native model; configuration edits cannot rebuild compiled animations |
If the aircraft remains absent, follow our broader checks for aircraft missing from the FSX selection menu, including folder nesting and configuration errors.
Can I convert an incompatible FS2004 aircraft into a native FSX aircraft?
Not through folder moves or aircraft.cfg edits: a true native conversion normally requires the original editable model source, an appropriate FSX export workflow and the author's permission.
- Keep the port-over when it loads reliably and any remaining visual limitations are acceptable.
- Replace individual components when the model works but the panel, gauges or sounds do not.
- Choose an FSX-native aircraft when the exterior model is invisible, the virtual cockpit is unusable, essential animations fail or required external code is incompatible.
- Do not redistribute a converted package unless its licence permits modification and republication or the original author has granted permission. Installing an aircraft privately does not grant redistribution rights.