Fix missing VATSIM aircraft landing gear in MSFS 2024 by checking vPilot model matching, package compatibility, dependencies and broken LODs.
VATSIM does not supply aircraft models or landing-gear geometry. In MSFS 2024, vPilot displays a model installed on your PC; missing gear usually means the matched model has a faulty gear animation or LOD, is incompatible with MSFS 2024, or is missing a dependency. Update, rematch or replace that model package.
This diagnosis applies to PC because vPilot is a Windows client and relies on locally installed traffic models.
Why do VATSIM aircraft appear without landing gear?
The gear is normally missing because vPilot selected a defective or incomplete local visual model, not because VATSIM omitted the wheels. VATSIM carries the remote aircraft's position and configuration data; vPilot then applies the received or inferred gear state to whichever model its rules select.
A mistake we see constantly is blaming the remote pilot when the same aircraft type repeatedly floats above the apron. Their client does not send you a 3D aircraft. Callsign, airline and ICAO type matching can also select a different model on two pilots' computers.
| What you see | Likely cause | Best next check |
|---|---|---|
| One aircraft type or airline is affected | Bad match, model or livery reference | Identify the exact model title selected by vPilot |
| Every aircraft from one model package is affected | Old, incomplete or incompatible package | Update or cleanly reinstall that package |
| Gear appears nearby but vanishes at a distance | Landing-gear mesh or animation missing from a lower LOD | Replace or update the model |
| Gear is briefly wrong during take-off or landing | Delayed configuration data, interpolation or an unsupported animation | Watch whether it corrects itself before changing anything |
| Struts show but the wheels are buried underground | Ground-contact, airport elevation or interpolation mismatch | Test the same model at another airport |
A texture-only livery is less likely to remove the gear by itself. If several liveries using the same base model all fail, suspect the base model or its LODs; if only one livery fails, check that livery's model reference and dependencies.
How do I fix missing VATSIM landing gear?
Identify the exact model vPilot spawned, then fix or replace that model rather than reinstalling Microsoft Flight Simulator blindly.
- Separate VATSIM traffic from built-in traffic. Temporarily disable MSFS multiplayer, AI and real-time traffic while testing. This prevents a built-in aircraft or duplicate model from being mistaken for the vPilot aircraft.
- Find the selected model. Check vPilot's model-matching messages or log for the model title and rule set used for the affected callsign. Compare several affected aircraft to establish whether one model, one airline rule or an entire package is responsible.
- Correct the matching rule. Make sure the aircraft type and airline rule points to a model that is actually installed. Disable stale or overlapping rule sets before editing individual entries; our vPilot model-matching setup walkthrough explains rule priority, fallbacks and missing model references.
- Update the traffic model package. Install a build confirmed to work with MSFS 2024 where one is available. Some MSFS 2020 models work correctly in 2024, but compatibility should not be assumed when a particular model has broken animations or LODs.
- Verify the package and dependencies. Close MSFS and vPilot before changing files, confirm that the package is in the simulator's active add-on location, and remove accidental extra folder nesting. Use our checks for the active Community folder and package structure if the installation location is uncertain.
- Test a known-good fallback. Temporarily map the troublesome aircraft type to another installed traffic model or disable the suspect rule set. If the replacement displays its gear, the original model package has been isolated as the cause.
- Run a clean package test. If all VATSIM models are affected, test with only one known-compatible traffic model package and its required dependencies active. When the fault began after a simulator update, follow our post-update package repair sequence.
If the fuselage, engines or textures are also absent, the problem is broader than the landing gear. Our diagnostic for invisible or incomplete aircraft models covers damaged packages, missing base models and broken dependencies.
What if the landing gear disappears only at a distance?
Gear that vanishes as the aircraft moves away is almost certainly a model LOD fault. Each level of detail needs the appropriate exterior geometry and animation; if a lower LOD omits the gear, MSFS cannot draw it.
Changing the Objects Level of Detail setting may move the distance at which the fault appears, but it does not repair the model and can cost performance. The proper fix is an updated model, a corrected LOD package or a different model-matching fallback.
Judge this while the aircraft is parked, taxiing or on final, when its gear should be extended. An aircraft at cruise altitude with no visible landing gear is behaving normally.
Is the remote VATSIM pilot causing the problem?
A remote configuration delay can briefly show the wrong gear state, but it does not usually cause one model to remain permanently gearless. If the gear corrects itself after a few seconds during extension or retraction, no local repair may be needed.
If the aircraft remains floating on its belly at the gate, or every instance of the same matched model is affected, treat it as a local model-matching or package problem. Rematch it before asking the other pilot to cycle their gear.
Will clearing the cache or changing graphics fix it?
Clearing the rolling cache will not restore landing-gear geometry because that cache concerns streamed world data, not the contents of an installed aircraft model. A graphics driver or anti-aliasing setting cannot add a mesh that is absent from the selected LOD either.
A full simulator reinstall should be a last resort. Model-specific faults are normally resolved much faster by identifying the vPilot match, checking its dependencies and substituting a known-good traffic model.