Fix GSX jetways not working in FSX or Steam Edition. Identify stock, SODE and Level 2 bridges, bad jetway data, scenery and door faults.
In FSX and FSX: Steam Edition, a visible jetway is not automatically a GSX-controlled jetway. Stock bridges normally use Ctrl+J, while GSX Level 2 and SODE-based bridges depend on valid airport data, a compatible stand and correct aircraft doors. Test Ctrl+J first, then isolate the gate, scenery and aircraft.
Which jetway system is FSX actually using?
FSX can display several kinds of jetway, and they are not all controlled in the same way.
| Jetway type | How it normally works | GSX involvement |
|---|---|---|
| Stock FSX animated jetway | Operated with Ctrl+J when the aircraft is correctly parked | GSX may detect or coordinate it, but the underlying animation belongs to FSX |
| GSX Level 2 replacement | SODE-based replacement tied to GSX airport and stand data | Requires the Level 2 expansion and a valid, eligible parking position |
| Third-party animated jetway | Uses the scenery developer's chosen control or SODE integration | Works with GSX only where the scenery supports that integration |
| Static scenery object | Does not move | Cannot be made operational by base GSX |
Park at the gate and try Ctrl+J. If the bridge moves, FSX can find and animate it; that does not prove it is a GSX Level 2 replacement or editable through GSX. If it does not move, check positioning, scenery complexity and advanced animations using our FSX jetway controls and positioning checks.
A failed Ctrl+J test is not conclusive for a custom or SODE-based bridge, because that scenery may use another control method. It is conclusive for a stock FSX jetway that should respond to the standard command.
Do GSX jetways work at every airport?
No GSX installation can make every visible jetway at every airport operational.
Base GSX mainly supplies boarding, baggage, catering, refuelling and pushback services; it does not convert every static or custom bridge into a moving one. The GSX Level 2 Expansion can replace many eligible stock FSX jetways with SODE-based models, but an add-on airport may use its own objects, exclude replacements or contain stands that are not defined correctly.
One failed gate usually points to that stand. Every gate failing at one airport points towards the airport scenery, its active AFCAD or a stale GSX profile. Failures at every airport suggest that GSX, SODE, Couatl or the airport cache is not loading correctly.
How to fix GSX jetways not moving in FSX
Confirm what you installed. Base GSX and the GSX Level 2 Expansion are not the same product. If you expected GSX replacement jetways, verify that Level 2 and its required components are installed and loaded, rather than assuming base GSX provides them.
Test the stock command. Park squarely at the stand, set the parking brake and try
Ctrl+J. A working stock bridge means the FSX animation itself is sound, even if GSX does not offer control of that object.Change one variable at a time. Try another gate at the same airport, the same aircraft at a stock airport, and then a default aircraft at the original gate. This shows whether the fault follows the stand, airport or aircraft.
Check the parking position. Stop on the centreline near the intended stop mark. An incorrect heading, parking radius or stop position can put the cabin door outside the bridge's operating range or cause GSX to reject the stand for that aircraft.
Check the aircraft door profile. GSX must know the position of the main passenger door. A poor add-on aircraft profile can make the bridge stop short, meet the wrong part of the fuselage or disappear from the available services.
Look for duplicate airport layouts. Two active add-on AFCAD or airport BGL files can leave FSX displaying one layout while GSX has cached another. Disable suspected duplicate add-on files one at a time and restart FSX; do not delete the simulator's stock airport BGL files.
Rebuild GSX airport data. After installing, removing or updating scenery, use the airport-cache rebuild or refresh function supplied with GSX. Reset an old user airport profile if the problem began after the airport layout changed.
Check whether GSX itself loaded. If boarding, pushback and other services also fail, this is not merely a jetway problem. Confirm that the GSX/Couatl menu and any required SODE component are present, restart FSX, allow the external modules to initialise, and retest with a default aircraft at a stock airport.
Our explanation of the ground services GSX adds to FSX helps separate a jetway animation fault from a wider GSX service failure.
What does “GSX bad jetway data” mean?
“Bad jetway data” normally means GSX cannot associate a jetway record with a valid parking stand in the active airport layout; it is not simply an animation running slowly or a door being closed.
Common causes include an obsolete or duplicate AFCAD, a jetway linked to a parking position that no longer exists, a stale GSX airport cache, an old user profile, or a malformed airport definition supplied with the scenery. A wrong aircraft door position can cause poor docking, but it does not usually explain a bad-data warning generated while GSX scans the airport.
- One gate is affected: the jetway-to-stand link or parking definition at that gate is probably wrong.
- Every gate at one airport is affected: suspect the active AFCAD, scenery priority, an airport update or an incompatible GSX profile.
- Every airport is affected: suspect the GSX airport cache, Couatl, SODE or the installation rather than individual stands.
- One aircraft docks badly everywhere: correct or reset that aircraft's GSX door profile.
If rebuilding the cache and removing duplicate add-on airport definitions does not clear the warning at one specific gate, the airport's scenery data may need correction. Adjusting the GSX stop position can fix alignment, but it cannot always repair a broken jetway link embedded in the scenery's airport BGL.
What does each GSX jetway symptom point to?
| Symptom | Likely cause | First check |
|---|---|---|
Ctrl+J works, but GSX offers no jetway control | Stock or unsupported custom jetway | Confirm whether Level 2 replacement is expected at that airport |
| Jetway option is missing at one stand | Bad stand data, aircraft restriction or unsupported bridge | Move to the neighbouring gate with the same aircraft |
| “Bad jetway data” appears across one airport | Duplicate, obsolete or malformed airport definition | Check add-on AFCAD files and rebuild the GSX cache |
| Bridge moves to the wrong fuselage position | Wrong door profile or stop position | Test a default aircraft at the same stand |
| Jetways and all other GSX services fail | GSX, Couatl, SODE or module-loading problem | Check the add-on menus and test a stock setup |
If Ctrl+J works but GSX does not, is GSX broken?
Usually not: it often means the visible bridge is still using FSX's stock jetway system rather than GSX Level 2 or compatible SODE control.
You can operate that bridge with Ctrl+J and still use GSX for the rest of the turnaround. If Level 2 was meant to replace it, check that the expansion loaded, that the airport has not been excluded from replacement and that the custom scenery is not supplying its own unsupported jetway object.
Can the aircraft stop a GSX jetway from working?
Yes, but aircraft faults usually cause missing service eligibility or bad docking rather than an airport-level bad-data warning.
GSX uses the aircraft profile to locate the main passenger door. It also compares the aircraft with the parking position, so a large airliner at a small-radius stand may be rejected even when the bridge itself works. Testing a default aircraft at the same gate is the quickest way to separate a door-profile problem from faulty airport data.
Does FSX: Steam Edition change the diagnosis?
The stand, scenery and aircraft checks are the same in FSX: Steam Edition, but older installers can register add-on paths or external modules incorrectly after a migration or reinstall.
If GSX stopped working after moving from boxed FSX, verify that it was installed specifically into the active Steam Edition installation. Missing GSX/Couatl menu entries, failure at every airport and scenery being read from the wrong library point towards installation or module registration rather than bad individual jetways.
Is this the same fix for GSX Pro in MSFS?
No. GSX Pro for Microsoft Flight Simulator is a separate product using different airport, jetway and add-on-loading systems.
The diagnostic pattern still helps: one bad gate suggests stand data, one bad airport suggests scenery or profile data, and failures everywhere suggest an installation problem. Do not apply FSX-specific remedies such as Ctrl+J, FSX AFCAD priority, SODE replacement or Couatl cache procedures blindly to GSX Pro in MSFS.
When can the jetway not be fixed locally?
A static scenery model or an incompatible custom jetway cannot be converted merely by changing a GSX setting.
If the airport works apart from a few unsupported bridges, use the scenery's own jetway control where available, operate stock bridges with Ctrl+J, or let GSX perform boarding and pushback without moving the bridge. If the same gate retains bad jetway data after duplicate layouts, profiles and caches have been ruled out, the fault lies in the airport definition rather than your aircraft controls.