Learn when MSFS 2020 airport add-ons work in MSFS 2024, how to test them, and how to fix duplicate buildings, terrain and jetway faults.
Many MSFS 2020 airport add-ons do work in Microsoft Flight Simulator 2024, especially conventional scenery packages, but compatibility is not guaranteed. Use a developer-approved MSFS 2024 build where one exists; otherwise test the 2020 package alone and check for terrain, jetway, object, runway and performance faults.
Which MSFS 2020 airports are most likely to work?
Airports built mainly from standard scenery objects, textures, aprons, runways and taxiways have the best chance of working unchanged. Compatibility becomes less predictable when an airport relies on custom modules, shared object libraries, specialised jetways, external installers or features tied to the MSFS 2020 SDK.
| Package type | Likely result in MSFS 2024 | Best choice |
|---|---|---|
| Basic airport scenery | Often works, but may show terrain or object conflicts | Test it by itself |
| Airport using shared libraries | Works only when every required library is compatible and installed | Check all dependencies |
| Custom jetways, scripts or modules | More likely to require an update | Use a confirmed 2024 build |
| Marketplace package | Availability depends on its MSFS 2024 listing and platform support | Install it through the in-simulator library |
| Separate 2020 and 2024 editions | Installing both commonly creates conflicts | Keep only the 2024 edition enabled |
The same principle applies beyond airports, although aircraft, utilities and weather tools have different risks. Our broader MSFS 2020-to-2024 compatibility guidance explains those distinctions.
How do I install and test a 2020 airport in MSFS 2024?
On PC, install the airport into the Community package location used by MSFS 2024, not the folder belonging to MSFS 2020. An older external installer may fail simply because it cannot locate the newer simulator; that does not necessarily mean the scenery package itself is incompatible.
- Check for a dedicated 2024 release. If one exists, use it instead of the older package.
- Remove duplicate editions. Do not enable the 2020 package, a converted copy and a native 2024 version together.
- Install the package through the correct route. Put ordinary freeware or manually installed scenery in the MSFS 2024 Community location. Manage Marketplace content through the simulator's library rather than copying protected package files.
- Start with a clean test. Temporarily disable other add-ons for the same airport and nearby city scenery, mesh or object packs.
- Inspect the whole airport. Check runway elevation, taxiway markings, terminal placement, parking stands, night lighting, jetways and approach alignment. Test both departure and arrival because some faults only appear after scenery has streamed or reloaded.
- Add other scenery back gradually. If the fault returns after enabling another package, the problem is a conflict rather than basic 2024 compatibility.
On Xbox and PlayStation, ordinary PC Community-folder packages cannot be sideloaded. The airport must be offered through the simulator's approved in-game distribution for that platform. A package working on PC therefore does not prove that it is available on every console.
Why do compatible airports still have scenery problems?
An airport can load successfully and still be only partially compatible. MSFS 2024's default airport, terrain data or nearby scenery may overlap rules created for the 2020 environment.
- Duplicate terminals or control towers: another edition of the airport is active, or its exclusion areas no longer suppress the default objects. Disable every competing package first.
- Sunken runways, plateaus or terrain spikes: old terraforming conflicts with newer terrain or mesh. Use an updated package; changing package priority may help only when two add-ons overlap.
- Pink textures or missing buildings: a required object library or texture dependency is absent or incompatible. Reinstall the stated dependencies rather than adding unrelated libraries.
- Frozen or misaligned jetways: the airport's jetway definitions or stand positions need revision. This usually requires a developer update rather than a cache change.
- Wrong gates, taxiways or approach alignment: the airport layout may be outdated, while navigation data comes from a separate source. Airport scenery does not automatically update procedures or magnetic data.
- Loading hangs or crashes: remove the package and test again. If MSFS 2024 starts normally without it, check for an updated scenery build, installer or required module.
A scenery package that needs changed exclusions, terraforming or SDK features may require a proper rebuild. We explain the difference between unchanged packages and genuine SDK conversion in our guide to converting MSFS 2020 scenery for MSFS 2024.
Should I use the 2020 package or a native MSFS 2024 version?
Choose the native MSFS 2024 version whenever the developer provides one. It is more likely to account for revised terrain, default objects, package rules and simulator-specific airport features.
Keep the 2020 version only when no newer build exists, its licence permits use in MSFS 2024, and it passes a clean test. Never assume that “loads without crashing” means fully compatible: inspect the airport and fly an approach before relying on it for a longer flight.
When comparing replacements, our MSFS 2024 airport scenery selection advice covers developer support, duplicate editions and conflict testing. The practical rule is simple: one airport package at a time, all dependencies present, and the 2024 build preferred wherever available.