Fix MSFS 2020 floating runway lights by finding duplicate airports, mesh conflicts, wrong scenery priority and stale terrain cache.
Floating runway lights in Microsoft Flight Simulator 2020 usually mean the lights and ground are being drawn from different airport elevations. The usual causes are duplicate airport scenery, a terrain-mesh conflict, stale cached terrain, or faulty add-on placement. Test without add-ons, remove duplicates, then rebuild the terrain cache.
Why do runway lights float above the ground?
Runway lights float when their placement altitude no longer matches the runway or surrounding terrain. An airport package may place the lights correctly, while another package changes the ground elevation underneath them.
This often appears after installing an airport, regional scenery, terrain mesh or an airport-enhancement package. It can also be a defect in the stock airport. Our airport elevation conflict checklist covers the wider terrain problems that can accompany floating lights.
| Symptom | Likely cause | Best first test |
|---|---|---|
| Only one add-on airport is affected | Faulty airport package or duplicate airport | Disable that airport and load the stock version |
| The problem began after installing terrain scenery | Mesh or terraforming conflict | Disable the regional terrain package |
| Aircraft, buildings and lights all float | Airport-wide elevation mismatch | Test with every third-party package disabled |
| Lights float only at long range | Lower-detail terrain geometry or terrain loading | Inspect them again from close range |
| Only approach lights seem raised | Possibly intentional light towers | Check their supports and the terrain below |
How do I fix floating runway lights in MSFS 2020?
The reliable fix is to establish a clean scenery baseline and restore packages one group at a time. Reinstalling the entire simulator is rarely the right first move.
- Confirm that the lights are genuinely floating. Park near the runway at night and inspect the lights from a low external camera. If the mismatch disappears at close range, terrain detail or delayed terrain loading is more likely than broken airport placement.
- Load the airport without third-party content. On PC, temporarily move the contents of the Community folder elsewhere. Its location can differ if a custom packages path was selected. Marketplace scenery is managed separately through Content Manager. On Xbox, remove or disable the relevant optional scenery package through Content Manager. If MSFS offers Safe Mode after an abnormal shutdown, it is also useful for a quick clean test.
- Remove duplicate versions of the airport. Check for two packages covering the same ICAO code, including an old airport, a regional airport pack and a handcrafted version supplied through optional world content. Keep one third-party rendition active. If the runway itself is also displaced, use our focused troubleshooting for floating or sunken add-on airports.
- Test broad scenery packages separately. Disable terrain mesh, regional scenery, city enhancements and packages that modify many airports. If the lights return to ground level, restore those packages in small batches. Halving each batch after a failed test finds the conflict much faster than enabling files individually.
- Correct scenery priority where possible. Give the detailed airport higher priority than broad regional scenery or mesh. Priority cannot repair a badly authored package, however; if two packages both alter the airport elevation, removing one is usually safer.
- Rebuild cached terrain. In the Data section of General Options, delete the rolling cache and recreate it only if you use it. Remove any manually cached region covering the airport as well. A stale cache is not the most common cause, but it can preserve terrain that no longer agrees with an updated airport.
- Update or reinstall only the affected package. Replace an outdated airport or mesh package with its latest compatible release. Do not manually delete random files from the simulator's Official package folders; use Content Manager for official and Marketplace content.
If the lights still float with an empty Community folder, no optional airport installed and a rebuilt cache, the stock airport data is probably wrong. Install any available simulator and world-content updates. Otherwise, the practical remedies are a corrected airport package or a later official scenery correction.
How can I tell whether the airport or terrain mesh is at fault?
If the runway, taxiways and buildings share the wrong elevation, the airport or terrain package is at fault; if only the lights hover by a consistent amount, their placement is probably wrong. Problems affecting aircraft and several object types need the broader diagnosis for floating aircraft and airport objects.
A sharp terrain step around the airport boundary points to competing terraforming data. A normal runway surface with lights fixed at one absolute height points instead to an add-on whose light objects do not follow the ground.
Why do only approach lights or one runway end float?
One-ended problems usually come from sloping terrain, an incorrect runway profile or approach lights placed at fixed elevations. The runway threshold may be correct while the terrain beyond it comes from a conflicting mesh.
Approach-light structures can legitimately stand on towers where the ground falls away, crosses water or passes over an obstruction. Runway edge and threshold lights should remain close to the paved surface; approach lights beyond the runway do not always do so.
Can graphics settings fix floating runway lights?
Graphics settings cannot repair a persistent scenery elevation error. Raising Terrain Level of Detail may reduce a temporary distant mismatch, but lights that remain suspended at close range require a scenery, mesh, cache or package-priority fix.
For scenery authors, inspect the airport with the terrain and all dependencies active, then verify that light rows and individual objects use suitable ground-relative placement rather than an unintended fixed altitude. Our guide to the MSFS 2020 Scenery Editor explains the editing workflow. Avoid raising the whole airport merely to meet the lights, as that can create sunken roads, cliffs and displaced taxiways around the boundary.