Learn to use the MSFS 2024 airport editor: set up a project, edit runways and taxiways, override stock airports, then build and test it.
The MSFS 2024 airport editor is part of Developer Mode’s Scenery Editor, not a separate in-game tool. Enable Developer Mode, install the matching SDK, create a scenery project with a BGL asset group, add or override the airport, then build the package and test its output from the Community folder.
Where is the MSFS 2024 airport editor?
Airport editing is performed through the Scenery Editor on the Developer Mode toolbar, while the Project Editor manages the package containing your work. Start with our Developer Mode setup steps, then follow the process for installing the matching MSFS SDK.
This authoring workflow is for the PC version of Microsoft Flight Simulator 2024. Xbox Series X|S and PlayStation 5 users cannot run the desktop SDK tools or install an unpackaged project through a Community folder.
How do I create or edit an airport?
- Load a flight at the airport. Position the aircraft or developer camera over the site so that the editor opens near the area you need. For a new airport, decide on a unique identifier that will not conflict with an existing facility.
- Create a project. Open the Project Editor and create the source project in a writable development folder. Keep source files outside both the Official and Community folders.
- Add a scenery package. Create a package containing a BGL asset group. Some SDK builds provide a project wizard that creates this structure; otherwise add the package and asset group through the Project Editor.
- Open the BGL in Scenery Editor. Load the asset group for editing and save it before placing objects. The editor’s live view is temporary until those source changes are saved.
- Add the Airport object. For a new field, enter its identifier, name, reference position and elevation. When modifying a stock airport, use the same published identifier and configure the airport delete options only for the categories you intend to replace.
- Build the operational layout. Place the runway first, then taxiway points and paths, aprons, parking stands, start positions, signs, lighting and windsocks. Keep airport-specific elements associated with the correct Airport entry in the editor hierarchy.
- Add scenery and terrain work last. Place buildings, fences and clutter after the operational layout is stable. Use small exclusion and terraforming areas rather than flattening or clearing the entire airport.
- Save and build the package. Save both the scenery asset and project, then run the package build from Project Editor. Resolve compiler errors before testing outside Developer Mode.
Our complete scenery project and packaging workflow covers the broader process for adding custom models and preparing a distributable package.
Which airport objects should I use?
| Object | What it controls | Common mistake |
|---|---|---|
| Airport | Identity, reference point, elevation and stock-airport deletion rules | Creating a second airport with a slightly different identifier |
| Runway | Dimensions, heading, surface, markings, lighting and runway ends | Matching the texture visually but entering the wrong true heading or elevation |
| Taxiway points and paths | The connected network used by ATC and AI traffic | Paths that appear to touch but do not share a connected node |
| Apron | Large paved or unpaved surface areas | Assuming an apron creates a routable taxi network |
| Parking and start positions | Spawn points, stand orientation and aircraft capacity | Using a radius too small for the intended aircraft |
| Exclusion and terraforming areas | Removal of unwanted scenery and local terrain shaping | Using an oversized polygon that damages nearby roads, vegetation or terrain |
Snapping, altitude mode and exclusion behaviour can produce subtle errors, particularly on sloping airports. We recommend checking our practical Scenery Editor settings for airport work before laying out taxiway nodes or terraforming polygons.
How do I modify a default airport without creating duplicates?
Use an Airport object with the stock airport’s exact identifier, then enable only the category-specific delete commands needed for the elements you are rebuilding. If you replace a runway, for example, also inspect its starts, taxiway links, lighting and other dependent records rather than leaving mismatched stock elements behind.
An exclusion rectangle is useful for removing buildings, vegetation and ordinary scenery objects, but it is not a substitute for the Airport object’s facility deletion options. Never edit files inside the Official package directories. Handcrafted or protected airport source files generally cannot be imported as an editable project; create your own overlay or replacement package instead.
Disable other add-ons for the same airport while testing. Two packages attempting to control one identifier can produce doubled buildings, missing runways or mixed taxi layouts according to their package priority and deletion rules.
Airport scenery also does not automatically rewrite the procedures stored in an aircraft’s navigation database. Moving or renumbering a runway may leave SIDs, STARs and approaches referring to the published navdata until that database is updated separately.
How should I build and test the airport?
- Build from Project Editor. Check the Developer Mode console for malformed polygons, missing assets and BGL compiler errors.
- Locate the built package. Its package folder should contain
manifest.jsonandlayout.jsondirectly inside the package root. - Install the built output. Copy that package root to the Community folder. Do not copy the entire source project or create an extra nested folder level.
- Restart for a clean test. Exit Developer Mode and restart MSFS 2024 so that the simulator loads the compiled package rather than an editor-mounted version.
- Inspect the whole airport. Test every runway start, taxi route and parking category by day and night. Look for disconnected taxi paths, incorrect hold-short points, floating signs, doubled objects and sharp terrain edges.
Why are my airport editor changes not showing?
- The package was not rebuilt: saving source files does not update the previously compiled BGL.
- The folder is nested incorrectly: MSFS must find
manifest.jsonandlayout.jsonat the expected package-root level. - The wrong asset group was edited: confirm that Project Editor is building the same BGL opened in Scenery Editor.
- Another airport package is winning: remove other add-ons for that identifier and test again.
- Stock elements were not deleted: use airport facility deletion options for runways, taxiways and parking rather than relying solely on scenery exclusions.
- The build failed silently in the view: inspect the Developer Mode console; the editor can retain a live object that never reached the compiled package.