Install a KSAN GSX Pro profile in Microsoft Flight Simulator, match it to the correct San Diego scenery, and fix profiles that fail to load.
To install a KSAN GSX Pro profile in Microsoft Flight Simulator on PC, extract the downloaded archive and place its airport-profile files in %APPDATA%\Virtuali\GSX\MSFS. Use a profile made for your exact San Diego scenery package, remove conflicting KSAN profiles, then restart Couatl or the simulator and test the assigned gates.
Install the KSAN GSX profile step by step
The profile belongs in GSX's roaming AppData folder, not the Microsoft Flight Simulator Community folder.
- Confirm GSX Pro works first. Start the simulator and check that the GSX menu opens. A KSAN profile cannot repair a broken GSX or Couatl installation; if the menu is missing, first check the core GSX Pro and Couatl setup.
- Identify your KSAN scenery. Determine whether San Diego International Airport is the simulator's default airport or a particular add-on package. The profile must match that exact airport layout and simulator generation.
- Extract the download. Do not leave the profile inside its ZIP or other archive. The usable airport profile is normally an
.inifile; retain any companion files and instructions supplied with it. Our detailed profile extraction and installation notes explain how to handle less obvious archive layouts. - Open the GSX profile folder. Press Windows Run, enter
%APPDATA%\Virtuali\GSX\MSFS, and press Enter.%APPDATA%selects the roaming profile of the Windows account running GSX. - Back up conflicting KSAN profiles. Move any older KSAN profile you installed to a temporary folder rather than deleting it immediately. Alternatively, use Profile Manager to import and enable the profile for the correct scenery package.
- Copy the extracted files. Put the profile directly in the GSX MSFS folder unless its included instructions specify otherwise. Do not add an unnecessary nested folder and do not place the archive itself there.
- Reload GSX. Use GSX's Restart Couatl command where available, or restart Microsoft Flight Simulator. Spawn at a KSAN parking stand and test the gates, stopping position and pushback instructions that the profile claims to customise.
Which KSAN GSX profile should you use?
Choose by scenery package and simulator version, not by the KSAN airport code alone. Different versions of San Diego scenery can use different parking coordinates, stand numbers, jetway positions and pushback routes.
| Your installed KSAN | Profile to choose | Risk from the wrong profile |
|---|---|---|
| Default or stock airport | A profile explicitly labelled for the default airport and your MSFS generation | Add-on scenery coordinates may place equipment inside buildings |
| Third-party KSAN scenery | The profile naming that exact scenery package and simulator generation | Gates, walk-in routes and pushbacks may not align |
| KSAN after a major scenery update | A profile confirmed for the updated airport layout | An older profile may load successfully but still use obsolete positions |
A GSX airport profile does not install San Diego scenery. It only customises GSX behaviour for scenery already installed in the simulator.
How can you tell whether the KSAN profile loaded?
A working profile aligns the customised GSX positions and routes with the visible KSAN scenery.
- Test one or two gates the profile specifically documents rather than assuming every stand was edited.
- Check that the marshaller or VDGS stop position follows the aircraft type and marked stand centreline.
- Confirm that service vehicles, passenger routes and custom pushbacks avoid terminal buildings where the profile covers those features.
- Compare the available gate names and pushback directions with the installed airport layout.
A functioning boarding or catering menu is not proof that the custom profile loaded. GSX can provide basic services at an airport without using a downloaded profile.
Why is the KSAN GSX profile not working?
Most failures are caused by the wrong folder, a scenery mismatch, duplicate profiles or GSX retaining old airport data.
- Nothing changes: make sure the file is extracted, placed directly in
%APPDATA%\Virtuali\GSX\MSFS, and stored under the same Windows account that runs GSX. - GSX works but positions are displaced: the profile probably targets a different KSAN scenery package or an older airport layout.
- Your edits or replacement profile are ignored: disable the older KSAN profile, restart Couatl and rebuild GSX's airport data if that option is offered after a scenery change.
- Some gates use unexpected layouts: check for duplicate KSAN scenery packages. Only one intended airport package should be active.
- The GSX menu itself is missing: repair the GSX Pro or Couatl installation before troubleshooting the airport profile.
Does the same KSAN profile work in MSFS 2020 and 2024?
Not necessarily: the installation method is similar, but compatibility depends on the airport package and layout used by each simulator. Use a profile labelled for your MSFS generation unless its documentation explicitly confirms both. GSX Pro and its AppData profile system require a Windows PC, so this installation cannot be performed on a console.