Use multiple airport scenery add-ons in MSFS safely. See which combinations work, why duplicate ICAO packages conflict, and how to test them.
Yes. Microsoft Flight Simulator can use many airport scenery add-ons at once when they cover different airports. Avoid leaving two packages active for the same ICAO code; they do not combine cleanly, and package priority rarely prevents duplicate terminals, flickering surfaces, broken elevations or missing objects.
Which airport add-on combinations work?
The safest combination is one active airport package per ICAO code, plus any required object libraries or compatible regional scenery.
| Combination | Use together? | What to check |
|---|---|---|
| Airports with different ICAO codes | Usually yes | Nearby airports can still have overlapping terrain or aerial imagery. |
| Two complete add-ons for the same airport | No | Keep only the preferred package active. |
| Third-party airport and standard stock airport | Usually yes | The add-on should contain exclusions that replace the stock objects. |
| Airport and regional scenery | Usually | Check for overlapping mesh, terraforming, vegetation or aerial imagery. |
| Airport and required object library | Yes | The library is a dependency, not another airport rendition. |
Packages made specifically for Microsoft Flight Simulator 2020 or Microsoft Flight Simulator 2024 should also be checked for compatibility with the version being used. Do not assume that scenery loading successfully means every feature will work correctly in both simulators.
Can two add-ons for the same airport be active?
Two complete packages for the same airport should not normally be active together. Package priority may decide which version of an individual asset appears, but it cannot reliably reconcile separate aprons, runways, exclusion rectangles, terraforming and building placements.
Typical symptoms include:
- Two terminals occupying the same position
- Flickering or overlapping ground textures
- Floating buildings, sunken runways or sharp terrain steps
- Duplicate jetways, windsocks and taxiway signs
- Missing terminals or objects removed by the other package's exclusions
An exception is a product explicitly sold as an enhancement requiring another airport as its base. In that case, follow the package requirements because disabling the base airport may remove assets the enhancement expects.
Should I disable the default MSFS airport?
Usually no: a complete third-party airport is designed to replace the standard autogenerated airport through its own exclusions. The stock scenery beneath it is not the same as having two independent third-party renditions installed.
A separately installed handcrafted or optional official airport can be different. If it covers the same ICAO code and visible overlap occurs, disable only that optional airport package—not core simulator content. Our explanation of when stock airport content should be disabled covers this distinction in more detail.
Will installing many airports reduce performance?
The number of airports installed does not translate directly into lower frame rates because Microsoft Flight Simulator primarily renders scenery near the aircraft. A detailed airport affects performance while flying near it; fifty unrelated airports elsewhere are not all being rendered at once.
A large collection can still consume storage, lengthen some content checks and make troubleshooting harder. Shared object libraries should remain installed when required, while duplicate copies of the same airport—such as Marketplace and externally installed editions—should be removed.
How should I test multiple airport add-ons?
Add airport scenery in controlled batches and test overlapping coverage before building a large collection.
- Record each ICAO code. Check that no other complete package in your installed content covers the same airport.
- Confirm simulator compatibility. Use the edition intended for MSFS 2020 or MSFS 2024 unless the package documentation explicitly supports both.
- Install required libraries. Missing dependencies can produce empty stands, invisible buildings or placeholder objects.
- Restart the simulator. Package changes may not be reflected correctly until a new session begins.
- Inspect the airport and its surroundings. Check terminals, runway levels, taxiway markings, jetways and nearby terrain.
- Disable suspects one at a time. On PC, temporarily move external packages out of the
Communityfolder. For managed or console content, use the simulator's package-management controls.
What if the conflict is difficult to identify?
Start with the affected airport package and any scenery covering the surrounding city or region. On PC, our empty-Community-folder conflict test provides a reliable isolation method, although managed Marketplace or official packages must be disabled separately.
If the whole airport, terminal or runway has vanished rather than merely overlapped, follow our diagnosis for missing or partially displayed airports. That problem can come from exclusions, an incomplete installation or a disabled dependency rather than two full airport packages competing for priority.