Why are trees on or near runways in Microsoft Flight Simulator?
Learn why trees appear on runways in Microsoft Flight Simulator and fix scenery conflicts, duplicate airports and stale cache data.
Trees appear on or near runways in Microsoft Flight Simulator when autogenerated vegetation is not suppressed by the airport scenery, aerial imagery is misread, cached scenery is stale, or two airport, terrain or vegetation packages conflict. At small airfields, some nearby trees may also be accurate rather than a fault.
Why does Microsoft Flight Simulator put trees on runways?
The usual cause is a missing, inaccurate or overridden vegetation exclusion around the airport. Microsoft Flight Simulator generates much of its vegetation from aerial data and procedural rules, while airport scenery defines where those trees must be removed.
- Incomplete airport boundaries: a default or add-on airport may not clear vegetation across the entire runway strip, displaced threshold or approach area.
- Misread aerial imagery: dark markings, shadows and old imagery can be interpreted as vegetation.
- Duplicate airport scenery: two packages covering the same ICAO can combine an airport layout from one source with terrain or vegetation from another.
- Regional scenery or mesh conflicts: global vegetation replacements, terrain mesh and vector-data packages can override or distort an airport's exclusions.
- Stale streamed or cached scenery: old rolling-cache data can be loaded alongside a newer airport package.
- Real vegetation: trees beyond the runway threshold or beside a narrow rural strip may match the real airfield. Trees crossing the runway centreline are almost always a scenery fault.
If the runway is also floating, buried or surrounded by sharp terrain steps, the problem is probably elevation rather than vegetation alone. Our guide to diagnosing airport elevation and mesh mismatches covers that related failure.
What does the location of the trees reveal?
The number of affected airports and the position of the trees usually identify the responsible scenery layer.
| What you see | Likely cause | Best first check |
|---|---|---|
| One default airport, with identical trees after every reload | Incorrect source data or a missing exclusion | Update the airport and regional content, then test without add-ons |
| Trees appear only with an airport add-on enabled | Faulty add-on or conflict with another airport package | Run that airport package by itself |
| Many unrelated airports are affected | Global vegetation package, stale cache or scenery-streaming problem | Disable global scenery modifications and refresh cached data |
| Trees accompany a floating or sunken runway | Terrain mesh or airport elevation conflict | Disable regional mesh and duplicate airport packages |
| Trees remain when vegetation quality is reduced but disappear with photogrammetry disabled | Tree-shaped objects baked into the photogrammetry mesh | Test without photogrammetry and check for replacement scenery |
How do I remove trees from an MSFS runway?
The quickest reliable fix is to isolate add-ons first, then refresh the simulator's installed and cached scenery.
- Identify the scope. Note the airport ICAO, runway and exact location. Check another airport in the same region and one elsewhere; this separates a local airport defect from a global vegetation problem.
- Update the simulator and scenery packages. Install outstanding simulator, airport and regional-content updates through the edition's content or library interface, then restart Microsoft Flight Simulator.
- Test without third-party scenery. On PC, close the simulator and temporarily move packages out of the
Communityfolder without touching the official or streamed-content folders. Our empty-Community-folder test explains how to isolate packages safely. On Xbox and, for MSFS 2024, PlayStation, disable or uninstall suspect optional packages through the simulator's content library. - Check managed add-ons as well. An empty
Communityfolder does not disable airport or regional packages installed through the simulator's own library. Look for two products covering the same airport, plus mesh, vegetation and regional scenery covering its location. - Restore packages in small groups. When the trees return, split that group and test again. This is faster than removing files randomly and identifies whether one package is faulty or two packages conflict.
- Refresh scenery data. If your edition provides Rolling Cache controls, delete the cache through the simulator, recreate it if required and verify that online world-data services are enabled. For broader symptoms such as blank terrain or low-detail tiles, follow our checks for repairing missing or corrupted scenery data.
- Retest the airport cleanly. If the trees disappear without an add-on, leave the conflicting package disabled or obtain a corrected version. If they remain at a default airport with all optional scenery removed, the airport's base data probably needs a scenery correction.
A mistake we see often is deleting official package folders or reinstalling the entire simulator before testing add-ons. That creates a much larger repair job and rarely fixes a vegetation exclusion supplied by a third-party airport.
Will changing graphics settings remove runway trees?
Graphics settings can reduce or conceal trees, but they do not repair the underlying airport exclusion. Lowering the vegetation or Trees quality setting may reduce density and draw distance, while changing terrain detail mainly alters when objects appear.
Photogrammetry is a useful diagnostic exception. If an object looks like a solid tree-shaped lump rather than normal vegetation, briefly disabling photogrammetry can show whether it is part of the streamed 3D mesh. Leaving photogrammetry disabled affects the entire surrounding area, so it is not a targeted airport fix.
Can a faulty airport be fixed permanently?
A permanent fix requires corrected airport scenery with a vegetation-exclusion polygon, or removal of the package overriding that exclusion. PC users and scenery developers can learn the relevant principles in our guide to building scenery with proper vegetation exclusions.
On consoles, locally built Community packages are not available, so the practical choices are an updated official airport, a corrected managed add-on or leaving the conflicting package disabled. Reducing tree quality is only a temporary visual workaround and may not clear every obstruction.