Fix GSX jetways not moving in Microsoft Flight Simulator with checks for parking position, Couatl, scenery conflicts and jetway exclusions.
To fix GSX jetways not moving in Microsoft Flight Simulator, park at a gate with an animated jetway, stop in the correct position, set the parking brake, shut down the engines, then request the jetway through GSX. If it remains still, check for duplicate scenery, incorrect GSX exclusions or a stalled Couatl process.
Fix GSX jetways in this order
Most failures come from the selected stand, aircraft position or two scenery packages trying to provide the same jetway. Work through these checks before reinstalling anything.
- Confirm that the gate has a functional jetway. A visible passenger bridge can be a static scenery object. Try another gate at the same airport, then test a gate at another airport where the simulator's native jetway request is known to work.
- Reposition the aircraft accurately. Select the actual gate in GSX and use its repositioning function if necessary. The forward left passenger door must be inside the jetway's movement envelope; slewing the aircraft after GSX has initialised the stand can invalidate its position.
- Put the aircraft into a service state. Apply the parking brake or set the chocks if the aircraft profile supports them, switch off the engines and anti-collision beacon, and leave the aircraft stationary.
- Send one jetway request. Use the relevant jetway, boarding or deboarding command in the GSX toolbar menu. Do not immediately send another request through default ATC or a keyboard binding, because a second command can reverse or interrupt the first.
- Reset GSX. Cancel active services, use the GSX restart command for Couatl, reopen the toolbar menu and request the service again. A Couatl problem is likely if the menu is unresponsive or GSX services fail as well.
- Reload the stand. If the bridge has become stuck between states, return to the main menu and load the flight again. Repeated commands rarely recover a jetway whose animation state is already broken.
For the normal order of parking, requesting services and disconnecting before pushback, see our GSX Pro service workflow.
Why does GSX say no jetway is available?
GSX reports no available jetway when the parking position has no functional jetway link, the bridge is only a static model, or the aircraft door is beyond its operating range.
- Wrong stand type: a ramp, cargo or remote stand may resemble a gate but have no jetway assigned in the airport data.
- Static scenery: GSX cannot add animation to a bridge baked into the airport model as an ordinary scenery object.
- Aircraft too far away: an incorrect stop position can leave the main door outside the bridge's reach.
- Unsuitable gate: a narrow-body stand may not accommodate the door position or fuselage geometry of a wide-body aircraft.
- Incorrect aircraft profile: bad door coordinates can make GSX target the wrong point even when the aircraft appears correctly parked.
An airport profile can correct stop positions, while an aircraft profile can correct door locations. Neither can turn a static scenery object into an animated jetway.
What does each GSX jetway symptom mean?
| Symptom | Likely cause | Best next check |
|---|---|---|
| No jetway moves at any airport | Couatl, installation or package-link problem | Restart Couatl and update GSX |
| Only one airport or gate fails | Static bridge, airport data error or scenery conflict | Test another stand and inspect installed airport packages |
| Two jetways occupy the same gate | GSX replacement and airport scenery overlap | Exclude that airport from GSX replacement jetways |
| Jetway moves but misses the door | Parking position or aircraft profile error | Reposition the aircraft and verify door coordinates |
| GSX menu does not respond | Couatl has stopped or cannot communicate with the simulator | Restart Couatl and check the GSX installation |
How do I fix a GSX jetway scenery conflict?
A scenery conflict is likely when two bridges appear at one stand, one model moves through another, or every gate fails only at a particular add-on airport.
- Close Microsoft Flight Simulator. Do not change GSX replacement settings while the airport is loaded.
- Check for duplicate airports. Keep only one scenery package for the affected ICAO code. A Marketplace airport and a separate package in the
Communityfolder can both replace the same location. - Choose which package supplies the jetways. If a third-party airport includes its own animated bridges, mark that airport as excluded from GSX replacement jetways. Use GSX replacements where the underlying default airport supports functional jetways and no custom package is providing them.
- Run the GSX installer or configuration tool. Apply available updates and verify that its packages are linked to the
Communityfolder used by the simulator version you are launching. - Test without custom profiles. Temporarily disable a recently added airport profile if the problem began after installing it. A bad stop position may look like a failed jetway.
Do not delete random GSX folders to resolve an exclusion problem. The installer manages its package links and replacement configuration; our GSX Pro installation and linking steps for MSFS 2020 cover that process.
Is GSX broken if the jetway works through ATC?
If the same jetway moves through the simulator's ATC ground-services request, its model, animation and parking link are working. The fault is then more likely to be the GSX service sequence, Couatl communication or a command sent from two different systems.
Reload the flight so the jetway starts fully disconnected, then test only one control method. GSX supplies service logic and replacement models, but Microsoft Flight Simulator still handles the underlying jetway animation. If neither GSX nor ATC can move the bridge, use our native MSFS 2020 jetway troubleshooting checks to isolate the airport and simulator settings.
Does the fix differ between MSFS 2020 and MSFS 2024?
The parking and scenery checks are the same, but MSFS 2020 and MSFS 2024 can use different package locations and separate Community folders. Updating or linking GSX for one installation does not prove that the other installation is configured correctly.
For Microsoft Flight Simulator 2024, check Couatl, the active package links and airport exclusions using our MSFS 2024 GSX repair checklist. GSX Pro also requires external PC software, so it cannot run on Xbox Series X|S or PlayStation 5/PS5 Pro; jetway failures on those consoles belong to the simulator or airport scenery, not GSX.
What if the jetway moves but misses the aircraft door?
A moving bridge that docks too high, too low or beside the fuselage normally indicates incorrect aircraft positioning or door coordinates rather than a jetway animation fault.
Reposition at the GSX stop point, confirm that the selected aircraft profile matches the exact aircraft variant, and test a larger gate. Correct the profile's passenger-door location only if it is visibly wrong across several airports; if the error occurs at one stand alone, adjust or replace that airport's stop position instead.