Why are GSX jetways not working in Microsoft Flight Simulator X (FSX)?
GSX jetways usually stop working in FSX because the airport, scenery, stand, or jetway system is not actually compatible with GSX control. Often GSX itself is loaded, but the required background components are not running, the parking spot is misconfigured, or the jetway is only a standard FSX Ctrl+J jetway.
What usually causes GSX jetways to fail in FSX?
There are a few common reasons, and they are not all the same problem.
- The airport does not support GSX-controlled jetways. A lot of default FSX airports only use the stock jetway system, which is separate from GSX.
- You are expecting GSX to control every jetway. It cannot. Some jetways are scenery objects with no GSX integration at all.
- The stand data is wrong. If the parking spot is not defined as a proper gate, is facing the wrong way, or has the wrong radius, GSX may not offer or move a jetway correctly.
- The aircraft door positions do not match. GSX needs to know where the main exit is. If the aircraft profile is wrong, the jetway may not move, may stop short, or may not be offered.
- GSX background services are not running properly. If the add-on loads partially, you may still see some GSX menus while jetway control fails.
- Scenery conflicts are interfering. Two airport sceneries for the same airport, or a bad AFCAD, can leave GSX reading the wrong stand data.
Do GSX jetways work at every FSX airport?
No. That is the first thing we would check.
In FSX there are really two different worlds: the default simulator jetway system, and GSX's own advanced ground handling. A stock FSX jetway at a default airport may still work with Ctrl+J, but that does not mean GSX can animate or manage it during boarding.
Likewise, GSX boarding can work perfectly while the visible jetway never moves. That usually means the airport scenery or the jetway object is not compatible with GSX control.
How do I fix GSX jetways not moving in FSX?
Confirm what kind of jetway you are using. Park at a default gate and try the standard FSX jetway command, usually
Ctrl+J. If that works but GSX does not move the jetway, you are likely dealing with a stock FSX jetway that GSX cannot take over in that scenery.Check that your GSX installation includes jetway support. Basic GSX ground services and advanced jetway control are not the same thing. If your GSX setup does not include the jetway feature set for supported airports, GSX will not drive jetways even though fuelling, boarding and pushback may still appear.
Test with a known simple setup. Use a default FSX aircraft at a stock airport gate. If the behaviour changes there, the issue is probably with the add-on aircraft, the airport scenery, or a parking definition rather than with FSX itself.
Make sure GSX has fully loaded. If the GSX menu is missing, delayed, or unreliable after FSX starts, restart the simulator and let all add-on modules finish loading. Jetway control depends on GSX's background components initialising correctly, not just the menu appearing.
Check the parking stand type and alignment. GSX works best when the aircraft is parked on a properly defined gate with the nose wheel near the stop point and the aircraft centred on the line. If you stop too far forward, too far back, or on a stand marked incorrectly in scenery data, GSX may refuse to position the jetway.
Verify the aircraft door location. Many add-on aircraft need the correct GSX door configuration. If the main cabin door is not where GSX expects it to be, the jetway may not move because it cannot find a valid target position.
Look for duplicate airport sceneries. If you have more than one version of the same airport active, GSX may read one set of parking spots while FSX displays another. That mismatch is a classic cause of gates, stop positions and jetways behaving strangely.
Rebuild or refresh the airport data within GSX if that option is available in your setup. After scenery changes, GSX can sometimes hold on to old information until it is refreshed.
Rule out a SimConnect or add-on module problem. In FSX, many external utilities rely on SimConnect. If GSX menus, services and animations are all inconsistent, the wider issue may be add-on communication rather than jetways specifically.
GSX jetway problem checklist
| Symptom | Most likely cause | What we would check first |
|---|---|---|
| GSX menu works, jetway never moves | Airport or jetway not GSX-compatible | Try Ctrl+J and test at another airport |
| Jetway option missing at one gate only | Bad stand data or wrong parking type | Move to another gate at the same airport |
| Jetway moves to the wrong place | Aircraft door profile is wrong | Check the aircraft's door configuration in GSX |
| Nothing in GSX works reliably | GSX background components not loading properly | Restart FSX and test with a simple aircraft and airport |
| Jetway works at stock airports but not add-on airports | Scenery-specific incompatibility or AFCAD conflict | Check for duplicate airport sceneries or outdated gate data |
What if the default FSX jetway works with Ctrl+J but GSX still does not?
That usually means nothing is actually broken in FSX. It means the jetway you see is a stock FSX jetway, and GSX is not controlling it at that airport.
Some users expect GSX boarding to automatically trigger any visible jetway. In FSX that is not how it works. A visible jetway only becomes a GSX-controlled jetway when the airport and the installed GSX features support that behaviour.
What if GSX works at some airports but not others?
Then the issue is almost certainly airport-specific.
We would look at the scenery first: gate type, parking radius, stop position, jetway placement and whether there are multiple airport files active. If one airport has custom jetways made outside the normal FSX system, GSX may not be able to interact with them at all.
Can the aircraft itself stop GSX jetways from working?
Yes. This is very common with add-on airliners.
If the aircraft's main exit is defined differently from what GSX expects, the jetway logic can fail even when the gate is fine. That is why testing with a default aircraft is so useful: it tells you whether the problem follows the aircraft or stays with the airport.
FSX and FSX: Steam Edition differences
The underlying troubleshooting is much the same in both versions. The main difference is that older add-ons can be more temperamental in Steam Edition if they were installed with old assumptions about paths, permissions or external module support.
If GSX used to work and then stopped after moving, reinstalling or changing scenery, we would suspect the GSX installation or scenery layering before blaming FSX itself.
When is the problem not fixable from your side?
If an airport's jetways were not built to work with GSX, there may be nothing to repair locally. GSX cannot magically take over every decorative or stock jetway object in every FSX scenery.
In that case you may still be able to use normal GSX boarding and deboarding, or use the stock FSX jetway command where that airport supports it. If you are troubleshooting broader FSX ground and airport add-ons, our FSX downloads library is a good place to compare scenery and utility setups.