How do I fix airport elevation problems in MSFS?

Airport elevation problems in Microsoft Flight Simulator are usually caused by two airport packages loading together, incompatible mesh or terraforming scenery, or stale cached terrain. Test the airport with all add-ons disabled, restore packages one group at a time, remove the duplicate or incompatible package, then clear the rolling cache and restart the simulator.

What causes sunken runways and floating airport buildings?

Most airport terrain defects come from scenery layers that provide different elevation, exclusion or terraforming instructions for the same location. This applies to both Microsoft Flight Simulator 2020 and MSFS 2024.

Older conversions are especially prone to floating buildings and abrupt plateaux because their altitude and flattening methods do not translate cleanly. Our explanation of why legacy FSX and Prepar3D scenery needs rebuilding for MSFS covers that limitation.

Is it really an airport elevation bug?

If the ground looks correct and only the aircraft altimeter disagrees with the published field elevation, this is not an airport scenery problem. Set the local pressure correctly rather than changing scenery or mesh.

A genuine elevation defect is visible in the geometry: wheels sink below the apron, the runway forms a cliff, buildings float, or taxiways separate from the surrounding ground. If one aircraft alone behaves incorrectly on an otherwise level surface, suspect its contact points or suspension configuration.

How do I isolate the scenery package causing the problem?

A clean-package test is the fastest way to identify an airport elevation conflict without reinstalling the simulator.

1. Close Microsoft Flight Simulator completely. On PC, move third-party packages out of the Community folder or use your existing package-management method to disable them. Do not manually delete files from the Official folder.
2. Disable managed add-ons on consoles. Xbox users, and PlayStation users running MSFS 2024, must use the simulator's content or package-management controls because there is no accessible Community folder.
3. Load the airport with no optional add-ons. Use the same runway and parking position. If the stock airport is now level, a third-party package is responsible.
4. Enable only the airport you want to use. If it breaks by itself, that airport package is outdated, damaged or incompatible with the simulator's terrain data.
5. Restore other scenery in groups. Test regional mesh, city enhancements, landmarks, nearby airports and global airport packages first. Adding half the remaining packages at each test is faster than checking them individually.
6. Remove the package that recreates the defect. Check for two editions of the same airport, duplicate folders or a separately installed handcrafted version.
7. Restart after each meaningful change. Returning to the main menu does not always rebuild every terrain layer cleanly.

Changing package priority is useful only when both products are designed to coexist and their documentation specifies an order. Priority cannot reliably merge two packages that both flatten or terraform the same airport. For wider checks beyond elevation faults, follow our complete scenery-conflict diagnosis process.

A common mistake is reinstalling several packages at once and immediately losing track of which one fixed or recreated the fault. Our package-isolation method for MSFS scenery mods explains how to keep that test controlled.

Should I disable the default airport?

Usually, no: a properly made airport add-on should exclude or replace the necessary stock elements without removing the simulator's base scenery. Never delete core airport or terrain files manually.

Disable a separately manageable stock, handcrafted or optional airport only when the add-on developer requires it or a clean test proves that both versions are loading. The same rule applies if two third-party editions cover one ICAO code: keep one active. MSFS 2024 users can use our guidance on deciding when a stock airport package must be disabled.

Will clearing the rolling cache fix airport elevation?

Clearing the rolling cache helps only when stale or incomplete streamed terrain data is involved; it does not cure two incompatible scenery packages.

1. Resolve duplicate packages first.
2. Open the simulator's data settings and delete the rolling cache using the in-sim control.
3. Remove the affected region from any manual cache if one is configured.
4. Restart the simulator and allow the airport terrain to stream again.
5. If necessary, test once with the rolling cache disabled and photogrammetry turned off.

If the airport works with photogrammetry off but fails when it is enabled, leave photogrammetry disabled for that location until the streamed terrain or airport package is corrected. Raising Terrain Level of Detail may make the defect more visible, but it does not repair incorrect elevation data.

What if the airport is still broken with no add-ons?

A stock airport that remains malformed in a clean configuration is usually affected by cached data, an incomplete content package or an error in the simulator's airport and terrain data.

• Install pending simulator, world and airport-package updates through the platform's normal content-management system.
• Test online world data and photogrammetry separately so you can distinguish streamed terrain from locally installed scenery.
• Confirm that the fault appears with a default aircraft and after a full simulator restart.
• Record the ICAO code, runway or parking position, coordinates, active data settings and screenshots before reporting the defect.

A complete simulator reinstall should be the last resort. It rarely fixes an airport-specific terrain error that remains reproducible with clean packages and a cleared cache.