Fix GSX pushback not working in MSFS: check brakes, chocks, Couatl, aircraft profiles, airport routing and conflicts with other tug tools.
GSX usually fails to push an aircraft in Microsoft Flight Simulator because the parking brake or aircraft-specific chocks remain set, GSX is waiting for a cockpit confirmation, another pushback system has control, or Couatl has stalled. Remove every restraint, follow the GSX prompts in order, and use only one tug system.
How do I fix GSX pushback not starting?
Start by removing aircraft restraints at the correct stage, then request pushback only through GSX and obey each brake prompt.
- Start at a recognised parking stand. Load at a proper gate or ramp position rather than an arbitrary location on the apron. Poor airport parking data can leave GSX without a usable pushback route.
- Set the parking brake initially. GSX normally expects it to remain set while the tug approaches and connects.
- Finish other ground services. Close doors, retract the jetway or stairs, and let boarding, catering and refuelling equipment clear the aircraft.
- Request pushback from the GSX menu. Select the route or direction offered for that stand. Do not also request the simulator's default ATC tug.
- Wait for the connection prompt. Do not release the parking brake merely because the tug has appeared.
- Release every restraint when instructed. Remove chocks through the aircraft's own EFB or tablet, release its cockpit parking-brake lever and keep pressure off the toe brakes.
- Answer subsequent GSX prompts. A hidden confirmation in the toolbar menu can make a working pushback look frozen. Set the brake again only when GSX tells you to do so at the end.
Menu wording varies slightly between GSX builds and aircraft integrations. Our GSX Pro workflow and setup guide explains how Couatl, aircraft systems and the departure sequence fit together.
| Symptom | Likely cause | First check |
|---|---|---|
| Tug connects but nothing moves | Brake, chocks or brake-axis input | Aircraft EFB and cockpit brake pressure |
| No tug appears | Couatl, stand data or profile problem | Test another aircraft at a stock airport |
| Pushback starts and stops | Brake-axis spike or competing tool | Disconnect pedals and disable other tug systems |
| Tug turns the wrong way | Airport routing or profile mismatch | Stand pushback route and active scenery |
Why does the GSX tug connect but not move the aircraft?
If the tug is attached but the aircraft remains stationary, an aircraft restraint or continuous brake input is almost always blocking movement. GSX cannot override chocks implemented by the aircraft developer, and some complex aircraft do not synchronise their custom parking brake with a generic keyboard or controller command.
- Move the parking-brake lever in the virtual cockpit rather than relying solely on a bound button.
- Open the aircraft's EFB or ground-services page and remove its own chocks. GSX chocks and aircraft-native chocks can be separate systems.
- Check the brake-pressure indication, if fitted. A partially applied toe-brake axis can hold the aircraft even when the parking brake appears released.
- Temporarily disconnect rudder pedals or unbind both brake axes. If pushback then works, recalibrate the axes and add only enough dead zone to stop unwanted input.
- Check whether that aircraft requires a native towing mode, steering-disconnect setting or dedicated integration profile.
A mistake we see constantly is releasing the visible parking brake while an aircraft tablet still shows the chocks installed. The cockpit lever alone does not prove that the aeroplane is free to move.
Why does no GSX tug appear?
If no tug arrives, isolate Couatl, the aircraft and the airport rather than reinstalling everything immediately. The following tests identify which part is failing:
- GSX services work elsewhere: Couatl is running, so inspect the affected stand, airport scenery or aircraft profile.
- A stock aircraft works at the same stand: the original aircraft's profile, nose-gear position or custom ground logic is the likely cause.
- The same aircraft works at a stock airport: the add-on airport probably has unsuitable parking or taxi-link data, a duplicate scenery package, or an incorrect GSX airport profile.
- Nothing works anywhere: restart Couatl, run the GSX updater or repair function, and check whether security software has blocked or quarantined the Couatl process.
Custom profiles can alter tug position, stand availability and routing. Check that the profile belongs to the active aircraft variant and airport package; our guide to installing and checking GSX aircraft and airport profiles covers the common folder and matching problems.
If only one stand fails, reposition at another marked gate before changing the installation. A malformed or disconnected airport taxi path can prevent GSX from calculating a valid push even though the scenery looks normal.
Can another pushback add-on block GSX?
Yes. The default ATC tug, a toolbar pushback utility and an aircraft-native towing system can compete with GSX for the same aircraft.
Use one pushback controller per flight. Do not request a default ATC tug and then start GSX, and do not leave an aircraft's native pushback active in the background. After two systems have spawned equipment or applied movement commands, cancelling one may not clear the conflict; reload the flight before testing again.
Choose GSX when you want pushback integrated with its ground-handling sequence. Use the aircraft-native system when the developer requires it for custom steering or towing logic. Our comparison of MSFS pushback add-ons and their conflicts helps identify which tool should remain enabled.
Does GSX pushback work in MSFS 2024 and on consoles?
GSX Pro can run with compatible PC installations of Microsoft Flight Simulator 2020 and 2024, but it cannot run on Xbox or PlayStation because Couatl is an external desktop process. A console installation therefore cannot be fixed by changing aircraft or stand settings.
On PC, run the GSX updater after a simulator or aircraft update and confirm that the installed GSX build supports the edition being launched. If GSX and the simulator's default tug both fail in MSFS 2024, work through our MSFS 2024 tug, brake and stand checklist; that points to a simulator, controller or aircraft problem rather than GSX alone.
When should I reinstall GSX?
Reinstall GSX only when it fails with every aircraft and airport, Couatl will not start, and the updater or repair option cannot restore it. If the GSX menu opens and other services operate normally, the core installation is probably sound.
A failure confined to one aircraft calls for a profile or aircraft-state check. A failure confined to one airport calls for a stand, scenery-priority or airport-profile check. Reinstalling GSX rarely corrects either of those local problems.