Fix an airport covered by water by finding scenery conflicts, bad mesh, water masks, elevation errors or missing base data.
In flight simulators such as MSFS, X-Plane, FSX and Prepar3D, an airport is usually covered by water because add-on scenery has overridden its coastline, water mask, terrain mesh or elevation. Disable conflicting packages, restore the default airport and terrain, correct layer priority, then reinstall only compatible scenery. Repair base data if the fault remains.
What causes an airport to appear underwater?
Water over an airport is normally a scenery-layer error rather than an aircraft, weather or graphics problem. The visible water may be only an incorrect aerial image, or it may be an active water surface that replaces the runway.
| Symptom | Likely cause | First check |
|---|---|---|
| The runway looks blue, but the aircraft taxis normally | Incorrect orthophoto, shoreline mask or aerial imagery | Disable photoreal or orthophoto scenery for that tile |
| The aircraft produces spray, sinks or lacks paved-surface behaviour | Water polygon, missing terrain tile or scenery conflict | Test with all third-party scenery disabled |
| The runway is below the water or sits on a raised platform | Airport elevation, flatten or terraforming conflict | Look for duplicate airport and mesh packages |
| Several airports or an entire tile are underwater | Missing base scenery, misplaced mesh or damaged regional data | Repair the simulator’s terrain data and check scenery order |
| Only an add-on airport is affected | Incompatible package, missing dependency or duplicate version | Restore the default airport, then reinstall one version only |
If the runway remains physically solid but merely looks like water, our guide to aerial imagery and shoreline masks explains how an orthophoto can visually replace airport ground without changing the underlying surface.
How can I tell whether the water is visual or physical?
The quickest test is to determine whether the runway merely looks blue or is being treated as water by the simulator.
- Reload in daylight and clear weather. This removes wet-runway reflections, darkness and poor visibility from the diagnosis.
- Taxi slowly across the affected area. Normal braking, tyre sounds and a stable aircraft suggest a texture problem. Spray, wakes, sinking or missing paved-surface behaviour point to an actual water polygon or absent terrain.
- Load the default airport scenery. Temporarily disable every custom airport, mesh, orthophoto, coastline and regional package that covers the location, then restart the simulator completely.
- Check the extent of the fault. One airport indicates a local package conflict. Several airports in the same region suggest a terrain tile, mesh or base-scenery problem.
Do not rely on reloading a saved flight after changing scenery. Many simulators retain terrain data until they are closed and restarted.
How do I fix an airport covered by water?
Restore the default airport first, then add custom scenery back until the fault returns.
- Back up before changing files. Copy configuration files and suspect packages to a safe location. Do not permanently delete scenery while diagnosing it.
- Run with no third-party scenery. On PC versions of Microsoft Flight Simulator, move packages out of the watched
Communitylocation. In X-Plane, disable the relevantCustom Sceneryentries. In FSX and Prepar3D, untick add-ons in the Scenery Library. Console users should disable or uninstall suspect content through the simulator’s content manager. - Use a half-and-half test. If the default airport works, restore half the disabled packages and test again. Repeating this split identifies the offender much faster than enabling packages individually.
- Remove duplicate coverage. Keep only one version of the airport and check for regional scenery, mesh, coastline or orthophoto packages covering the same coordinates. Packages can conflict even when their names do not mention the airport.
- Check simulator compatibility. Airport and terrain packages made for another simulator generation may load without an obvious error but use incompatible elevation, water or material data.
- Correct scenery priority. Airport definitions and exclusions normally belong above broad regional terrain. Mesh and orthophoto layers generally sit below airports and overlays, although the package documentation takes precedence.
- Repair the base scenery if the default is also broken. Use the simulator or platform’s verify, repair or content-management function to restore missing regional terrain and airport data.
- Rebuild scenery caches last. Clear or recreate the simulator’s rolling or scenery cache only after removing the conflicting package. A cache reset cannot correct a bad water polygon that is still installed.
Microsoft Flight Simulator
In MSFS 2020 and MSFS 2024, duplicate Community or installed content is more common than a simple user-controlled scenery-order problem. Test with an empty Community location, disable duplicate airports in the content manager and confirm that required regional content is installed.
If the airport is sunken, raised or surrounded by terrain spikes rather than simply painted blue, follow our MSFS airport elevation repair steps. A stale rolling cache can affect streamed regional scenery, but clear it only after custom packages have been ruled out.
X-Plane
X-Plane users should inspect Custom Scenery/scenery_packs.ini. Custom airports should load above Global Airports, overlays should remain above orthophoto and mesh entries, and mesh-based scenery normally belongs near the bottom.
Only one mesh can effectively control a given tile, so installing two orthophoto or mesh packages for the same coordinates is a common mistake. If a whole tile or region has become water, use our X-Plane terrain-and-water troubleshooting sequence.
FSX, Prepar3D and FS2004
These simulators rely heavily on Scenery Library priority and BGL files. Keep the airport and its exclusions above broader regional scenery, then check for duplicate airport definitions, elevation corrections, flatten polygons and coastline or water files.
Some airport elevation files are stored separately from the main add-on, so disabling the obvious Scenery Library entry may not remove every component. Back up any ICAO-matching files before disabling them. Where the runway is raised or submerged relative to surrounding terrain, our diagnosis for floating or sunken add-on airports covers the related mesh and elevation checks.
What if only one airport is underwater?
If only one airport is affected, the fault is almost certainly local to that airport or its surrounding terrain tile. Search installed package names and documentation for the airport’s ICAO code, then check for a second airport version, an elevation correction or regional scenery covering the same position.
If disabling the airport does not help, disable the nearby mesh, orthophoto or coastline package next. When the default airport is still underwater with every add-on removed, repair the relevant base or regional scenery rather than reinstalling the entire simulator immediately.
Can graphics settings cause water over a runway?
Graphics settings rarely cause an airport to be replaced by water. Texture resolution and anti-aliasing can make the boundary look blurred, while rain may create a reflective runway, but neither should create a water polygon or submerge airport terrain.
If the aircraft still recognises a hard runway, investigate imagery and water masks. If the surface behaves like water, concentrate on terrain files, scenery priority, duplicate packages and airport elevation—not graphics drivers.