FSX aircraft add-ons do not work natively in MSFS 2020. See why copying fails, what conversion requires, and how to spot a genuine MSFS package.
No. FSX aircraft add-ons are not natively compatible with Microsoft Flight Simulator 2020. Copying an FSX aircraft folder into the MSFS Community folder will not convert it. The aircraft must be rebuilt or properly ported to MSFS’s package, model, material, gauge, sound and flight-model systems by its developer.
Why don’t FSX aircraft work in MSFS 2020?
FSX and Microsoft Flight Simulator 2020 use fundamentally different aircraft formats and supporting systems. An FSX installer may place files in SimObjects\Airplanes and shared folders such as Gauges or Effects; MSFS instead expects an organised package with files such as manifest.json and layout.json.
Changing the folder location does not resolve the differences inside the add-on:
| Aircraft component | Typical FSX implementation | What MSFS 2020 needs |
|---|---|---|
| Package structure | FSX folders and installer entries | An MSFS package with a valid manifest and layout |
| 3D models | Legacy model files and materials | Models, materials and animations prepared for MSFS |
| Cockpit instruments | FSX XML or compiled gauges | Instruments using systems supported by MSFS |
| Flight dynamics | aircraft.cfg and commonly an .air file | Flight-model configuration authored and tested for MSFS |
| Sounds and effects | FSX sound and effect definitions | Definitions and assets configured for MSFS |
Our broader explanation of FSX and MSFS add-on compatibility covers why aircraft, scenery and utilities do not all have the same conversion prospects.
Does the Legacy flight model setting make FSX aircraft work?
No. The Legacy flight model option in MSFS 2020 changes how the simulator interprets certain aerodynamic parameters; it is not an FSX compatibility layer. It cannot install an FSX package, translate an old cockpit gauge or convert a legacy model.
Can an FSX aircraft be converted to MSFS 2020?
An FSX aircraft can sometimes be converted by a developer who has the source assets, permission to use them and the skills needed to rebuild each incompatible component. This is development work, not a matter of changing a file extension or repackaging the original download.
- Models and materials may need conversion or rebuilding, followed by repairs to animations, transparency, lighting and cockpit interaction.
- Gauges and avionics often need substantial rewriting. Old compiled gauge files cannot simply be copied into an MSFS cockpit.
- Flight dynamics must be adapted and tested rather than relying unchanged on the FSX configuration.
- Sounds, effects and metadata need to be recreated within a valid MSFS package.
A basic freeware aeroplane may be easier to port than a complex airliner with custom systems. Encrypted commercial aircraft or add-ons without source files generally cannot be converted properly by an end user. A developer may release a separate MSFS edition, but owning the FSX edition does not automatically provide a licence for it.
How can I identify a genuine MSFS 2020 aircraft package?
- Check the stated simulator. The download must explicitly support Microsoft Flight Simulator 2020. References only to FSX, FSX: Steam Edition or Prepar3D indicate a legacy package.
- Inspect a manual-install archive. A normal MSFS package has
manifest.jsonandlayout.jsonat its package root. An archive containing only an FSX-style aircraft folder,aircraft.cfg, an.airfile and model, panel, sound and texture folders is not enough. - Use the correct folder level. The folder placed in Community should directly contain the package files rather than another identically named folder. Our MSFS 2020 mod installation instructions show the expected structure.
- Check the platform. Community-folder add-ons are for PC. Xbox users cannot sideload an FSX aircraft or a PC Community package; compatible Xbox aircraft must be distributed through the simulator’s Marketplace.
What if an MSFS-native aircraft still does not appear?
If the package is explicitly made for MSFS 2020 but is missing from the aircraft selector, check for an extra nested folder, missing dependencies, conflicting duplicate versions or an incompatible simulator build. Our aircraft visibility troubleshooting checklist covers those installation faults.
If the package lacks an MSFS manifest and is labelled for FSX, however, the problem is compatibility rather than installation. Reinstalling it or moving the folder around will not make the aircraft usable.