Assign airline-specific gates in GSX with ICAO parking codes, save them in an airport profile, and learn why ATC or AI may still ignore them.
Assign airline-specific gates in GSX by editing the airport’s parking positions in the GSX airport customisation editor and entering each carrier’s three-letter ICAO code in the gate’s airline-code field. Save the profile and repeat for each stand. This marks the stand for that carrier inside GSX; it does not control simulator ATC or AI traffic.
The method applies to GSX Pro in Microsoft Flight Simulator and classic GSX in FSX and Prepar3D, although labels can differ slightly between editions. GSX Pro is a PC add-on and cannot be installed in the console editions of Microsoft Flight Simulator.
How do I set airline codes for a GSX gate?
Use the GSX airport customisation editor to associate one or more ICAO airline codes with each parking position.
- Load the correct airport scenery. Make sure the airport package you actually use is active, because the profile is tied to its parking positions.
- Open the GSX menu. Select the option labelled Customize Airport Positions or its equivalent in your GSX edition.
- Select the parking stand. Check both its identifier and physical location; scenery developers do not always name stands exactly as their real-world gate numbers.
- Enter the airline code. Find the Airline Codes field and enter the carrier’s three-letter ICAO code in uppercase. Use
UAL,BAWorDLH, for example, rather than the two-letter IATA codesUA,BAorLH. - Add shared operators where needed. Separate multiple codes with commas, following the format shown by the editor, such as
UAL,ACA. - Save the user profile. Repeat the process for the other stands, then reopen the airport or GSX parking menu to confirm the associations appear correctly.
GSX stores these edits in an airport profile rather than rewriting the scenery package. Our explanation of installing and checking GSX airport profiles covers profile priority and what to inspect when an imported profile does not load.
Does GSX make ATC or AI use those gates?
No. Airline codes in a GSX profile affect GSX’s own parking information and selection logic, not the simulator’s ATC or AI parking system.
| What you want to control | Where it must be configured |
|---|---|
| Airline preference shown to GSX | GSX airport profile and its Airline Codes field |
| Your aircraft’s arrival stand | Select the stand manually through GSX or the simulator |
| AI airline parking | Airport scenery parking records and the AI traffic system |
| ATC gate instructions | Simulator airport data and ATC logic; GSX cannot override them |
| Ground-handler or vehicle livery | GSX handling-operator settings; a gate code alone does not guarantee a particular operator |
In FSX and Prepar3D, the underlying airport parking records are commonly called AFCAD data. MSFS scenery contains equivalent parking definitions. Our guide to how parking size, type and airline metadata affect gate selection explains why changing GSX alone cannot redirect AI aircraft.
Should every gate be assigned to one airline?
No. Use several codes for a shared terminal and leave genuinely common-use stands unrestricted.
Airlines often favour a terminal, concourse or group of stands rather than owning one fixed gate. Aircraft size, international-arrival facilities, towing requirements and stand availability still affect the real assignment. For a realistic profile, model the usual operating area rather than locking every flight to a single gate; our overview of the factors behind real airport gate allocation provides the operational context.
Why is the airline-specific gate assignment not working?
Most failures come from an incorrect airline code, the wrong active airport profile or expecting GSX to control a separate parking system.
- Two-letter code entered: replace the IATA designator with the three-letter ICAO code.
- Wrong scenery profile: a profile made for another version of the airport may point to different stand identifiers or coordinates.
- Airport updated: scenery updates can rename, move or recreate parking positions. Open the editor and assign the affected stands again.
- Aircraft metadata missing: automatic matching may require the flight or aircraft configuration to expose the same ICAO airline code. A painted livery alone does not always provide that metadata.
- Stand unsuitable: airline preference does not override parking type, radius, wingspan limits or other compatibility checks.
- ATC or AI ignores the code: this is expected when the code exists only in the GSX profile. The corresponding airport or traffic-system parking data must be changed separately.
Treat the airline code as a GSX preference, not an exclusive gate lock. You can still select another compatible stand manually when operations or airport layout require it.