Fix an add-on aircraft not appearing in FSX Steam Edition by checking its Steam path, folder nesting, aircraft.cfg, filters and compatibility.
An installed add-on aircraft usually fails to appear in FSX: Steam Edition because its folder is in the wrong FSX installation, nested one level too deep, or lacks a valid aircraft.cfg entry. Put the actual aircraft folder under the active Steam SimObjects folder, then close and restart FSX.
Where should FSX Steam Edition aircraft be installed?
FSX: Steam Edition normally reads fixed-wing aircraft from FSX\SimObjects\Airplanes and helicopters from FSX\SimObjects\Rotorcraft. The live FSX root is the Steam library folder containing fsx.exe, which may not be on the C drive.
Use Steam’s option to browse the simulator’s local files rather than assuming the default path. Our guide to finding the active Steam add-on folders explains the possible locations when boxed FSX and Steam Edition have both been installed.
A correctly placed aircraft normally has this structure:
FSX\SimObjects\Airplanes\AircraftName\aircraft.cfg
A mistake we see constantly is an extra package directory:
FSX\SimObjects\Airplanes\DownloadedPackage\AircraftName\aircraft.cfg
FSX does not recursively search every subfolder. The directory containing aircraft.cfg must normally sit directly inside Airplanes or Rotorcraft.
How do I make a missing aircraft appear?
Work through the aircraft’s path, package type and configuration in that order.
- Find the active installation. Open FSX’s local files through Steam and confirm that the folder contains
fsx.exe. Do not use a remembered path or an old boxed-FSX directory. - Locate the real aircraft folder. Open the downloaded archive and find the directory that directly contains
aircraft.cfg. Copy that directory toSimObjects\Airplanes, or toSimObjects\Rotorcraftfor a helicopter. - Remove extra nesting. If the archive begins with a complete
SimObjectsdirectory, merge that directory with the one under the FSX root. Do not place an entireSimObjectsfolder insideAirplanes. - Confirm that it is a complete aircraft. A normal package has
aircraft.cfg, model and texture data, and usually an.airfile. Panel and sound folders may instead refer to files from a default aircraft. - Check the selection filters. In the FSX aircraft selection screen, reset the manufacturer, publisher and aircraft-type filters. Enable Show all variations, because a newly installed repaint can otherwise be grouped under its base aircraft.
- Restart FSX completely. FSX builds its aircraft list when it starts. Copying files while the simulator is open will not reliably refresh the list.
- Inspect the configuration. If it remains absent, open
aircraft.cfgin a text editor and verify that it contains at least one valid[fltsim.0]section. Make sure Windows has not saved it asaircraft.cfg.txt.
For packages with several folders or separate gauges and effects, follow our manual FSX aircraft installation procedure. Missing gauges, effects or sounds usually do not stop an aircraft appearing, but they cause the next set of problems after it loads.
What does the aircraft.cfg file need?
FSX creates each selectable variation from a [fltsim.x] block in aircraft.cfg. A malformed or absent block can leave an otherwise complete aircraft out of the menu.
- Each variation needs a unique
title=value. Duplicate titles can cause conflicts or missing entries. - The blocks should be numbered consecutively, beginning with
[fltsim.0]. - The
sim=value normally matches the name of the aircraft’s.airfile without its extension. - The
model=value must point to the appropriate model folder. A blank value normally means the plainmodelfolder. - The
ui_manufacturer=,ui_type=andui_variation=values control where the aircraft is grouped in the selection screen.
If only one livery is missing, compare its new [fltsim.x] block with a working one from the same aircraft. Do not replace the entire configuration with one supplied for a different release of the base model.
| Symptom | Likely cause | What to check |
|---|---|---|
| No new aircraft or variation | Wrong FSX root or extra folder level | Find aircraft.cfg and move its containing folder directly under the correct SimObjects category |
| Only texture files were supplied | The download is a repaint | Install the required base aircraft and add the supplied variation entry |
| Aircraft appears under an unexpected name | Menu grouping comes from its configuration | Reset selection filters and inspect the ui_ entries |
| Aircraft appears but fails when selected | Missing model, flight model or dependency | Check sim=, model=, the .air file and any required base package |
Why did the installer report success but install nothing?
An older installer can report success while writing the files to boxed FSX, a previous installation or a default directory that Steam Edition does not use. Search for the aircraft’s folder name, then compare its location with the directory containing the active fsx.exe.
If the installer offers a destination, point it to the FSX root rather than directly to Airplanes; installers often need to place supporting files in several FSX directories. If it cannot detect Steam Edition at all, consult our explanation of how older FSX add-ons behave with Steam Edition.
Can a repaint or incompatible aircraft stay hidden?
A repaint, an AI-only model or a package made for another simulator is not necessarily a complete, user-selectable FSX aircraft. A repaint requires its named base aircraft, while some traffic models are intentionally distributed for AI use rather than cockpit flying.
Many FSX add-ons work in Steam Edition, and some older FS2004 port-over aircraft can appear with limitations. Aircraft compiled solely for newer Prepar3D releases or Microsoft Flight Simulator use different model or package formats and cannot simply be copied into FSX.
Will verifying FSX through Steam restore the aircraft?
Steam file verification repairs the simulator’s official files, not third-party aircraft, so it will not reinstall a missing add-on. Use it only when FSX’s own files are damaged; for an absent add-on, the installation path, nesting and aircraft.cfg checks are the relevant fixes.
Editing fsx.cfg is also unnecessary for a normal installation. It matters only when the aircraft is deliberately stored in a custom directory that has been registered as a SimObjectPath. If the files are correctly placed but other installation faults remain, use our broader FSX add-on fault checklist to check permissions, dependencies and incorrect installer destinations.