GSX disabled at an airport in MSFS? Find the exclusion, duplicate scenery, bad profile or parking-data fault and restore ground services.
GSX is usually disabled at one Microsoft Flight Simulator airport because that ICAO is excluded in GSX, a custom airport package or profile has disabled it, or duplicate scenery makes GSX read the wrong airport data. Remove the exclusion or conflict, then restart Couatl and reload the airport.
This is a PC-side GSX Pro issue. The same diagnosis applies to Microsoft Flight Simulator 2020 and 2024 on PC, although configuration labels can vary between GSX builds.
What can disable GSX at one airport?
Most one-airport failures come from an exclusion, conflicting airport data or a profile made for a different scenery package.
- A whole-airport exclusion: GSX can store a disabled setting against an airport’s four-letter ICAO code. It may have been selected accidentally or retained from an older installation.
- A custom airport or bundled profile: An airport package or its GSX profile may deliberately disable GSX, disable particular stands or refer to data that no longer exists after the scenery was updated.
- Duplicate scenery: Two editions of the same airport can leave GSX reading the wrong parking layout. Common examples are an old Community package alongside its replacement, or Marketplace and Community copies installed together.
- An unsuitable airport layout: If the scenery contains no usable parking positions, GSX may be unavailable there. This normally produces an airport-data or parking warning rather than an explicit disabled message.
A mistake we see constantly is treating missing replacement jetways as proof that the entire airport is disabled. Jetway exclusions and whole-airport exclusions are separate settings.
How do I re-enable GSX at the airport?
Re-enable the airport by removing its ICAO from GSX’s disabled settings, eliminating duplicate scenery and testing without any custom airport profile.
- Confirm the scope. Record the exact GSX message and test another established airport. If GSX works elsewhere, its main installation and Couatl process are probably sound.
- Check the airport settings. Open GSX’s airport customisation or configuration controls and look for a whole-airport disabled setting or exclusion matching that ICAO. Clear it, save the change and restart Couatl. Do not confuse this with the separate option that excludes only GSX replacement jetways.
- Remove duplicate airport packages. Check the simulator’s package library and active Community add-ons for two third-party versions of the same airport. Keep the intended edition active and remove or disable the obsolete copy. Do not delete files from the simulator’s Official packages folder merely to repair GSX.
- Test without the custom profile. Back up and temporarily move or rename the profile associated with that ICAO. If GSX then reads the airport normally, install a profile made for the exact scenery edition. Our guide to checking where GSX profiles are installed and which one is active explains the profile workflow.
- Reload the airport data. Restart Couatl after a settings or profile change. If you changed scenery packages, fully close Microsoft Flight Simulator before reloading the flight so the simulator and GSX rebuild their view of the airport.
- Start on a defined parking stand. Test from a normal gate or ramp position rather than a runway, helipad or arbitrary map location. This separates an airport exclusion from a stand-recognition problem.
If a disabled setting returns after you remove it, an active profile or airport package is probably supplying that instruction. Isolate the profile first, then the scenery package; repeatedly reinstalling GSX will not resolve airport data that is still being loaded.
Does a GSX jetway exclusion disable the whole airport?
No—excluding GSX replacement jetways normally preserves the airport developer’s jetway models while leaving boarding, baggage, catering and pushback available.
If GSX opens and other services work, troubleshoot the jetway configuration rather than enabling every airport option. We cover the relevant airport exclusions and scenery conflicts that stop GSX jetways separately.
Why are services still unavailable after GSX is enabled?
An enabled airport can still have individual services unavailable because GSX does not recognise the stand, aircraft or required service points.
- The flight was started on a runway, helipad or position that is not defined as parking.
- The active profile disables that stand or was created for a different airport edition.
- The airport update changed parking names, coordinates or stand sizes but the profile was not updated.
- The aircraft lacks suitable door or service-point configuration for the requested operation.
- The stand’s parking data is missing or too limited for GSX to match it reliably.
Read the status message shown for the unavailable service: a parking or airport-data warning points back to scenery, while an aircraft or door warning calls for an aircraft configuration check. Our overview of GSX service prerequisites and the normal operating sequence covers those aircraft-side conditions.
Should I reinstall GSX?
Reinstalling GSX is rarely the right first fix when only one ICAO is affected.
If every airport fails, check that Couatl starts, the GSX package is linked correctly and the installer can verify or update the installation. MSFS 2024 users can work through our sim-wide GSX troubleshooting checks for MSFS 2024. Back up custom profiles before reinstalling, because preserved user configuration can carry the same airport exclusion into the new installation.