How do I migrate FSX aircraft to Prepar3D v5?

To migrate an FSX aircraft to Prepar3D v5, first confirm that it uses an FSX-native model and no 32-bit DLL gauges. Copy the complete aircraft folder and its permitted support files, preferably as an external add-on package, then correct aliases and test it. Some aircraft cannot be made v5-compatible without rebuilt binaries.

Which FSX aircraft work in Prepar3D v5?

An FSX aircraft is a good migration candidate when it has an FSX-native model, conventional textures and sounds, and XML-based gauges. Prepar3D v5 is 64-bit, so compiled 32-bit gauges, system modules and other DLLs made for FSX will not load.

An aircraft advertised for FSX may still contain an older FS9 model, so the label alone is not proof of compatibility. Our explanation of the technical differences between FSX and Prepar3D covers why models and compiled modules behave differently.

Check the aircraft licence before moving files. Owning both simulators does not automatically permit migration or redistribution of Microsoft default aircraft, commercial products or third-party dependencies.

How do I move the aircraft files?

Move one complete aircraft at a time and test it before adding another, rather than pointing Prepar3D at the entire FSX aircraft library.

1. Find the complete FSX aircraft folder. It will normally be under Microsoft Flight Simulator X\SimObjects\Airplanes. The aircraft folder should contain aircraft.cfg plus its model, panel, sound and texture folders. If the download contains only a texture folder and repaint entries, use our guide to recognising complete FSX aircraft and repaints before proceeding.
2. Make a clean working copy. Do not migrate directly from an active FSX installation. Keep the original untouched so configuration edits can be reversed.
3. Choose the installation method. Use a dedicated Prepar3D v5 installer when one exists. For a manual test, copy the aircraft folder into Prepar3D v5\SimObjects\Airplanes. An external package declared through add-on.xml is cleaner and easier to remove; our Prepar3D aircraft installation instructions explain both approaches. Merely placing an aircraft in the Documents add-ons folder without a valid declaration will not make Prepar3D load it.
4. Collect permitted support files. Read panel.cfg for gauge names and inspect aircraft.cfg for effect references. Copy required XML gauge CABs, effects and effect textures to their corresponding Prepar3D locations without overwriting newer files. Do not copy 32-bit DLL gauges or unknown FSX modules into Prepar3D v5.
5. Repair aliases and configuration references. In sound.cfg and panel.cfg, an alias= entry may point to an FSX default aircraft that does not exist in Prepar3D. Replace it with an installed, compatible dependency or obtain the correct P3D package. In aircraft.cfg, verify that sim= matches the AIR file name and that model=, panel=, sound= and texture= match their folder suffixes.
6. Test the aircraft in stages. Restart Prepar3D, load at a simple default airport in daylight, and check the exterior model, virtual cockpit, gauges, controls, engines, lights and sounds. Enable a security prompt only when you recognise and trust the named module.

A mistake we see constantly is forcing an old FSX installer to treat the Prepar3D root folder as FSX. That can scatter incompatible DLLs across shared folders or overwrite common effects and gauges. If the installer has no P3D option, extract or install its files to a temporary location only when the installer and licence permit it, then move the required files manually.

Why does the migrated aircraft not appear?

A migrated aircraft usually disappears from the selection screen because Prepar3D cannot find a valid configuration or model, not because the texture format is wrong.

• Folder nested twice: Airplanes\AircraftName\AircraftName\aircraft.cfg is too deep. The configuration file must sit at the top of the individual aircraft folder.
• Incomplete repaint: a texture-only download needs the exact base aircraft named in its documentation.
• Broken aircraft.cfg entry: check the [fltsim.x] sections, ensure each title= is unique, and confirm that the referenced model and texture folders exist.
• Invalid model: if the configuration is sound but the aircraft remains invisible or crashes while loading, its MDL may be an unsupported legacy model.
• Add-on package disabled: confirm that Prepar3D accepted and enabled the external package, or test the aircraft temporarily from the standard SimObjects\Airplanes folder.
• Selection filters: clear manufacturer, category and other filters that could hide the aircraft.

Can missing gauges, textures or sounds be fixed?

Missing files and aliases can often be repaired, but an incompatible compiled model or DLL cannot be converted through configuration edits.

• Blank instruments: inspect panel.cfg for missing XML gauge packages. If the panel depends on a 32-bit DLL, it needs a 64-bit P3D replacement from the aircraft developer.
• Black or untextured virtual cockpit: restore the required VC textures and check any fallback paths in texture.cfg.
• White exterior model: verify every texture= suffix and ensure the repaint was made for that exact model variation.
• No sound: open sound.cfg and replace an alias to an absent FSX aircraft, or install the sound package the aircraft requires.
• Missing smoke or lights: copy the referenced .fx files and their permitted textures, preserving the expected names.
• Dead avionics or engines: proprietary systems may rely on an incompatible module even when the aircraft model itself loads.

Should I migrate the aircraft or replace it?

Migration makes sense for a simple freeware aircraft with an FSX-native model and XML gauges; replacement is usually better for complex airliners, FS9 port-overs and aircraft built around proprietary DLL systems.

If the model is invisible, its virtual cockpit depends on 32-bit binaries, or the licence forbids file movement, configuration work will not solve the underlying problem. Use an aircraft already prepared for the simulator from our Prepar3D-compatible freeware library instead.