Should I disable or remove the default airport when installing a third-party airport scenery in Microsoft Flight Simulator 2024?
Usually, no. In Microsoft Flight Simulator 2024 you normally do not remove or manually delete the default airport when installing a third-party airport. Most add-on airports are designed to sit on top of the stock scenery. You only need to disable built-in content if you see conflicts such as duplicate terminals, jetways, signs, lights or broken ground textures.
Do you need to disable the default airport in MSFS 2024?
Most of the time, the answer is no. A well-made airport add-on includes its own exclusions so the stock airport objects underneath are suppressed automatically. That is how the simulator is meant to work.
Where people run into trouble is when the airport they are replacing is not just a plain autogenerated stock field. If the base sim includes a more detailed handcrafted version, or if another add-on is already modifying the same airport, you can end up with two scenery layers fighting each other.
When should you disable scenery?
Disable scenery only when there is a clear conflict. Good examples are:
- Duplicate buildings such as two terminals in the same place.
- Extra jetways or static aircraft overlapping the add-on stands.
- Floating or sunken objects after an airport enhancement is installed.
- Broken taxiway markings or two sets of ground textures.
- Conflicts with handcrafted airports included with the simulator or optional content packs.
- Two third-party airports installed for the same ICAO.
If none of that is happening, leave the default content alone.
When should you remove scenery?
Almost never. We would not recommend deleting any core Microsoft Flight Simulator 2024 files by hand just to make an airport add-on work. That creates update problems, can break content verification, and makes troubleshooting harder later.
If something needs to be deactivated, use the simulator's own content management tools where available, or remove the add-on package from your Community folder if that is the item causing the clash. Removing a third-party package is normal. Removing stock files is not.
Default airport vs handcrafted airport: what is the difference?
This is the key distinction. People often say “default airport” when they mean two different things.
| Type of airport content | What it means | Usually needs disabling? |
|---|---|---|
| Generic stock airport | The ordinary simulator version generated from default data and objects | No, the add-on should normally override it |
| Handcrafted built-in airport | A more detailed airport supplied as part of the sim or an official content pack | Sometimes, if the add-on developer says it conflicts |
| Another third-party airport | A separate scenery package for the same ICAO | Yes, keep only one active |
If you are replacing a plain stock airport, your third-party scenery should generally install and work without any extra steps. If you are replacing a handcrafted airport, check the developer notes carefully.
How to install a third-party airport without causing conflicts
- Install only one airport add-on per ICAO. If you already have another scenery package for that airport, remove or disable it first.
- Place the add-on in the correct add-ons location. For Community-based packages, make sure the airport folder is installed properly and not buried inside extra zip folders. If you need scenery files, our library is at Fly Away Simulation downloads.
- Start the sim and load the airport. Do a quick visual check from the apron and from external view before changing anything else.
- Look for obvious overlap. Duplicate terminals, doubled windsocks, stacked jetways and conflicting signs tell you another package is active.
- Disable conflicting content through the sim first. If the airport being replaced is a built-in handcrafted field, deactivate that optional content using the simulator's content management area if it offers that option.
- Remove the conflicting add-on if necessary. If the overlap is caused by another Community package, take that package out and test again.
- Restart and recheck. Scenery changes are best verified after a full restart so the airport reloads cleanly.
What if the third-party airport says to disable an Asobo or built-in airport?
Follow the developer's instructions. Some airport developers explicitly require the stock handcrafted version to be turned off because both packages contain custom terminals, aprons and ground polygons for the same field.
That is not the same as deleting the default airport. You are simply preventing the conflicting built-in package from loading. If the developer does not mention any need to disable stock content, we would assume it is meant to coexist with the base sim normally.
Signs that the airport add-on itself is the problem
Not every visual issue means the default airport must be disabled. Sometimes the add-on is old, incomplete or not fully adapted for the current sim build. Suspect the add-on itself if you see:
- Missing textures but no duplicate buildings
- Terrain tears around the runway edges
- Jetways that do not connect properly
- Objects floating after a simulator update
- An airport loading partly, with no obvious second scenery present
In that case, disabling stock content may not help at all.
Best practice for Community folder airport scenery in MSFS 2024
Keep things simple. One airport package per ICAO, one active version of any landmark pack affecting that field, and no manual tampering with core sim files. That avoids most scenery headaches.
We also suggest keeping a note of what each package changes. Airports, mesh fixes, city packs and ground texture enhancements can all affect the same area, and it is much easier to isolate a conflict when you know what you installed.
Common questions
Will two airport add-ons work together if one only changes the terminal?
Usually not reliably. If both packages target the same airport, there is a fair chance they will clash somewhere, even if the overlap is not obvious at first.
Does renaming the stock airport folder fix conflicts?
We would avoid that. Renaming or moving built-in simulator files is not a clean solution and can create trouble after updates.
Can I leave a handcrafted airport active if the third-party airport seems fine?
If the airport looks correct and the developer does not say otherwise, you can leave it alone. If you later notice duplicate objects or odd terrain, that is the first thing to disable for testing.
What if the airport disappears completely?
That is usually a separate issue from stock-airport conflicts. A bad install, a missing dependency, or a damaged package is more likely than the need to remove the default airport.
The short answer
Install the third-party airport and do not remove the default airport by default. Only disable built-in handcrafted content or other add-ons when you can see a genuine conflict, and never delete core simulator files manually just to make scenery work.