General Updated Thu, 02 Jul 2026 23:03:54 GMT 7 min read

Why do add-on aircraft appear invisible, missing landing gear, or as a skeleton model in FSX or Prepar3D?

Fix invisible, skeleton or gearless add-on aircraft in FSX and Prepar3D by checking textures, model folders, aircraft.cfg and compatibility.

By Ian StephensEditor-in-Chief

In FSX and Prepar3D, an add-on aircraft usually turns invisible, loses its landing gear, or shows only a bare framework because the model, texture or compatibility chain is broken. The usual causes are a bad aircraft.cfg entry, a missing texture or model folder, an old FS2004-era aircraft, or a rendering mismatch in the sim.

Why does the aircraft load but parts are missing?

When the aircraft appears in the selection menu and loads into the sim, the installation is only partly working. FSX and Prepar3D have found the aircraft entry itself, but something the entry points to is missing, incompatible or being drawn incorrectly.

That is why you can get odd symptoms rather than a total failure: a visible cockpit with no exterior, a fuselage with no landing gear, a transparent body with only lights and shadows, or what looks like a wireframe or skeleton model.

Symptom	Most likely cause	What we would check first
Aircraft loads but exterior is invisible	Missing model alias, bad texture reference, or incompatible old model	`model=` entry, `model.cfg`, and the texture folder
Only a bare or skeletal airframe shows	Missing textures or broken transparency materials	Texture files, `texture.cfg`, and sim graphics mode
Landing gear is missing	Model animation issue, incompatible aircraft version, or incomplete repaint	Try another variant and confirm the add-on is native to your sim
Only one repaint is broken	That repaint folder is incomplete or incorrectly named	Compare its `texture=` line and files with a working repaint
Works in FSX but not in Prepar3D	Legacy model or materials not fully supported by P3D	Whether the aircraft was built specifically for Prepar3D

How do we fix an invisible or skeleton add-on aircraft?

Test another variant of the same aircraft
If one repaint works and another does not, the base model is probably fine. That points straight at the broken variant's texture= entry, repaint folder, or a missing fallback texture reference.
Open the aircraft's folder structure
A normal aircraft package should have an aircraft.cfg file and folders such as model, texture, panel and sound, sometimes with numbered or named variants. If the download extracted into an extra nested folder, FSX or P3D may find the aircraft entry but not the correct subfolders.
Check the aircraft.cfg entries
Each [fltsim.x] section points to a specific model and texture set. The lines model= and texture= must exactly match the relevant folder names after the dot. A typo, missing character or wrong capitalisation can be enough to break a variation.
For example, if the entry says texture=BA, there must be a folder named texture.BA. If the line is blank, the sim expects the base texture folder instead.
Inspect the model folder
If the aircraft is invisible, the model folder is one of the first places we look. Some aircraft use a model.cfg file to alias or redirect to another model folder; if that alias points to the wrong place, the exterior can disappear completely.
If the aircraft was installed manually, a missing or corrupted model file can produce a half-drawn aircraft or no visible body at all.
Inspect the texture folder and any fallback file
Skeleton-looking aircraft usually mean textures are missing or not being read properly. Many repaints rely on a texture.cfg file that tells the sim to borrow shared textures from another folder. If that fallback path is wrong, you may see transparent surfaces, bare geometry, missing gear doors or incomplete markings.
Compare the broken texture folder against a working one from the same package. If the working repaint has extra shared texture files or a valid texture.cfg and the broken one does not, you have found the problem.
Confirm the aircraft is native to your simulator
This is a big one. Older FS2004 aircraft can sometimes be made to appear in FSX or Prepar3D, but they often show graphical faults: transparent fuselages, missing undercarriage, dead animations or strange shadows. Prepar3D, especially the newer 64-bit generations, is less forgiving with very old models and materials.
If the aircraft was built for a different simulator generation, there may be no clean fix beyond using a proper native version.
Check whether the issue appears only in one graphics mode
FSX users should be wary of DX10 Preview with older add-ons. Some legacy aircraft models were never prepared for it and can display missing textures, odd transparency or invisible parts. If the aircraft looks normal in the standard renderer but breaks in DX10 Preview, the model is the limitation.
Prepar3D can show similar problems with older material definitions. If the aircraft breaks only after changing graphics options, a shader rebuild can sometimes help, but it will not make an incompatible old model fully correct.
Rule out a bad repaint package
Many "missing gear" reports come from repaint-only downloads installed without the required base package, or from repaints that overwrite files they should not. If the add-on came as texture files only, it still needs the correct original aircraft model underneath it.
If you replaced files rather than adding a new variation, restore the original aircraft first and then reinstall the repaint carefully.
Check whether it is really an AI model
Some aircraft packages were designed for AI traffic, not for flying from the cockpit. AI models are often simplified and may not include the same animations, gear detail, virtual cockpit or texture layout you would expect from a full flyable aircraft.
If an AI model is used as a user aircraft, it can look incomplete even when it is technically working as designed.

What usually causes missing landing gear specifically?

Landing gear problems are often more specific than a fully invisible aircraft. In most cases, we trace them to one of four things:

An old model whose gear animation or material setup does not behave properly in your version of FSX or Prepar3D.
A repaint or texture set missing gear textures, alpha textures or fallback references.
A broken model folder or alias where the sim is loading the wrong exterior model.
An AI-only or reduced-detail model being used as if it were a full flyable aircraft.

If the gear is missing on every repaint, suspect the model. If it is missing on only one repaint, suspect the texture folder.

FSX and Prepar3D compatibility gotchas

FSX

FSX will load a lot of older content, but that does not mean it will render it correctly. Aircraft designed for much older simulators can appear with missing parts, especially if DX10 Preview is enabled.

Prepar3D

Prepar3D accepts many FSX-native aircraft, but there are limits. Very old aircraft, especially those carried forward from FS2004, are common sources of invisible models, gear problems and broken materials. The newer the Prepar3D version, the more often those legacy quirks show up.

How do we tell whether the problem is the install or the aircraft itself?

A quick test helps.

If every variant of the aircraft is broken, the package is either incomplete or not compatible with your sim.
If only one variant is broken, the repaint or that [fltsim.x] entry is wrong.
If the aircraft works in FSX but not Prepar3D, it is usually a compatibility issue rather than a bad install.
If reinstalling the exact same package changes nothing, the aircraft model itself may simply not suit your simulator version.

When a reinstall helps and when it does not

Reinstalling helps when files were misplaced, omitted or overwritten. It does not help much when the underlying aircraft was built for the wrong simulator generation or uses old materials that your sim cannot draw properly.

If you need a replacement, the safest route is to use aircraft packages clearly intended for your simulator version from a trusted library such as Fly Away Simulation Downloads. Native packages are far less likely to produce invisible exteriors, missing gear or skeleton models.

The short version

If an add-on aircraft in FSX or Prepar3D is invisible, gearless or looks like a skeleton, we would first check aircraft.cfg, the model folder, the texture folder and any texture.cfg fallback file. If those are correct, the next suspect is compatibility: many old FS2004-era or non-native models simply do not render properly in newer FSX or Prepar3D setups.