Fix aircraft, jetways and airport objects floating in MSFS by identifying scenery conflicts, elevation mismatches, cache faults and model errors.
Aircraft, jetways and airport objects float in Microsoft Flight Simulator when the airport’s elevation does not match the active terrain, or duplicate scenery packages place objects at different heights. If only aircraft float, suspect model contact points, static-aircraft placement, multiplayer data or an AI aircraft fault rather than the airport terrain.
What causes floating objects at an MSFS airport?
The pattern of affected objects usually identifies the cause faster than changing settings at random.
| What is floating? | Most likely cause | Best first check |
|---|---|---|
| All buildings, jetways and parked aircraft | Airport elevation or terrain mismatch | Disable the custom airport and any regional mesh |
| Buildings or jetways, but not the apron | Duplicate object layer or incorrectly placed scenery objects | Look for another package covering the same airport |
| Only static aircraft | Incorrect scenery placement or model origin | Disable static-aircraft and airport enhancement packages |
| Only AI or multiplayer aircraft | AI model contact points or network position data | Compare with a default user aircraft at the same stand |
| Your aircraft at every airport | Aircraft contact-point configuration | Test a default aircraft |
| Several airports across one region | Mesh, cached terrain or streamed-world-data problem | Disable regional terrain add-ons and rebuild the rolling cache |
Airport scenery and terrain are separate layers. The terminal can therefore remain at its authored altitude while the ground underneath is raised or lowered by another airport, mesh or terraforming package. Our guide to diagnosing MSFS elevation conflicts covers the related symptoms, including terrain spikes and sunken runways.
How do I fix floating aircraft, jetways or buildings?
Fix the package or model creating the height mismatch; graphics quality, object detail and terrain LOD settings do not change an object’s authored altitude.
- Establish the scope. Check another stand at the same airport, another airport and a default aircraft. Note whether the apron itself is level and whether every object is displaced by roughly the same amount.
- Test without third-party content. On PC, close MSFS and temporarily move packages out of the
Communityfolder. Marketplace or other managed packages may be stored elsewhere, so deactivate those through the simulator’s content library as well. - Remove duplicate airports. Keep only one third-party version of a given ICAO active. Airport enhancements, city packs, landmark scenery and static-aircraft packages can also contain overlapping objects even when their names do not mention the airport. Follow our checks for isolating a floating or sunken add-on airport if the fault disappears with that airport disabled.
- Test mesh and terrain packages. Temporarily disable regional meshes, terrain replacements and broad scenery enhancements. If the airport then sits correctly, keep the conflicting package disabled or change its priority where the simulator provides package-order controls.
- Refresh cached terrain. Delete and recreate the rolling cache from the simulator’s data settings, then reload the airport. This helps with stale terrain but will not repair scenery authored at the wrong elevation.
- Reactivate packages individually. Add content back one package at a time until the floating objects return. Updating or reinstalling the identified airport is safer than editing its files blindly.
On Xbox, and on PlayStation 5 in MSFS 2024, use the simulator’s content library to deactivate or remove optional packages; consoles do not offer the PC Community-folder test. In MSFS 2024, also allow a streamed airport to reload over a stable connection before treating a one-off terrain error as a permanent scenery fault.
Why do only parked aircraft float?
Aircraft-only faults normally come from the aircraft model, traffic system or static scenery rather than the airport elevation.
- Your selected aircraft floats everywhere: its wheel contact points are probably incorrect. Update or reinstall the aircraft and compare it with a default model before editing configuration files.
- One decorative aircraft always floats in the same place: it is probably a static scenery object with an incorrect origin or placement height. Disable the package that added it.
- One AI aircraft type floats at several airports: the AI model likely has faulty contact points. Other models sitting normally at the same gate confirm this.
- Multiplayer aircraft briefly hover or sink: delayed or imprecise network position data can place remote traffic above the apron. This often changes when the remote aircraft moves or its position updates.
Reducing AI traffic will hide traffic-related examples, but it does not correct static aircraft baked into scenery. See our focused diagnosis of aircraft floating at airport gates when the terminal and jetway remain properly grounded.
Why are only the jetways floating?
A jetway that floats while the terminal and apron remain correct is usually duplicated, incorrectly placed or using a faulty animation profile.
Disable any jetway replacement, ground-service enhancement and alternative airport package, then compare the default airport. If the whole jetway is displaced vertically before it moves, suspect scenery placement. If only the moving cabin, wheels or docking section shifts after activation, the jetway animation or aircraft-door profile is the more likely source.
When the jetway, terminal and nearby scenery all float by the same amount, return to the airport-elevation checks. That pattern is not normally fixed by changing a jetway setting.
Will scenery priority or exclusion zones fix floating objects?
Scenery priority can select the correct version of overlapping content, while an exclusion can remove duplicate objects; neither repairs an incorrect terrain elevation by itself.
Where package-order controls are available, let the specific airport take precedence over a broad regional enhancement. Do not install a second airport merely to cover the first one, and do not delete package-order files as a first troubleshooting step. Our explanation of what exclusion zones can and cannot remove helps distinguish duplicate scenery from a genuine mesh problem.
What if the objects still float with all add-ons disabled?
A persistent fault in a stock airport is likely to be cached terrain, damaged simulator content or an error in the base airport data.
Rebuild the rolling cache, make sure the relevant simulator and world content is installed correctly, and retest with a default aircraft. Repairing or reinstalling the affected content package is more proportionate than reinstalling the entire simulator. If one stock object remains at the wrong height after those checks, it requires a scenery-data correction; traffic density, graphics settings and camera changes cannot fix it.