How do I edit GSX Pro pushback routes and controls in MSFS?
Edit GSX Pro QuickEdit pushback routes and controls in MSFS 2020/2024: set endpoints, save stand profiles, test routes and fix common faults.
To edit GSX Pro pushback routes in Microsoft Flight Simulator, park at the correct stand, open airport-position customisation from the GSX toolbar, select a route slot and launch QuickEdit Pushback. Place the aircraft at the release point and final nose heading, save the airport profile, then test the route through GSX—not the default tug.
The method applies to supported PC installations of MSFS 2020 and MSFS 2024. GSX Pro and its Quick Edit tools are PC-only; these editing controls are unavailable on Xbox and PlayStation. Menu wording can change between GSX builds, so follow the control legend shown by your installed version.
How do I edit a GSX QuickEdit pushback route?
QuickEdit saves a route for one specific airport parking position, so the active scenery, stand and stop point must all be correct before editing.
- Load the correct airport and stand. Park where GSX recognises the intended gate or ramp position. If default and third-party versions of the airport are installed, confirm that GSX has matched the scenery being displayed; our explanation of how scenery and profiles affect GSX stand positions covers this relationship.
- Check the configured stop position. The aircraft should be centred and aligned at the proper stopping point. QuickEdit constructs the manoeuvre from that position, so an offset stand produces an offset route.
- Open airport-position customisation. Open GSX from the in-sim toolbar and select the airport-position customisation command, often labelled Customize Airport Positions. Verify the displayed stand manually if GSX has selected a neighbouring position.
- Select a route slot. Choose the pushback direction or custom route entry you want to edit, then launch QuickEdit Pushback. Each valid exit, such as nose-left and nose-right, needs its own saved route.
- Set the release point and heading. Use the movement and rotation controls shown on screen to place the whole aircraft where the tug should finish. Align the aircraft’s nose with the intended departure direction rather than judging the heading from the tug.
- Confirm and save. Use QuickEdit’s save or confirmation command before leaving. Cancelling, closing the editor or restarting Couatl before confirmation can discard the route.
- Test from the original stand. Leave editor or slew mode completely, reset at the same parking position and request pushback through GSX. If the previous route remains, restart Couatl from the GSX controls, allow it to initialise and reopen the menu.
Where should the endpoint and final heading be placed?
The endpoint must put the entire aircraft safely on the intended taxi path, with enough space for the tug to disconnect.
- Allow for the wingspan and tail of the largest aircraft expected to use the stand; a narrow-body test does not prove that a wide-body will clear buildings, masts or equipment.
- Leave enough straight distance before the turn. An endpoint too close to the gate can produce abrupt tug steering or poor stand clearance.
- Set the final orientation from the aircraft’s nose and align it with the taxiway centreline.
- Do not finish on a runway, busy intersection or anywhere the tug would obstruct traffic while disconnecting.
Which controls should I use for GSX pushback?
Use GSX controls throughout a GSX pushback because Microsoft Flight Simulator’s standard pushback commands operate a separate tug system.
| Task | Use this control | Avoid this mistake |
|---|---|---|
| Open GSX | The GSX toolbar icon or configured GSX menu shortcut | Expecting the MSFS TOGGLE PUSHBACK binding to open GSX |
| Edit the route | The movement and rotation inputs displayed by QuickEdit | Using normal camera or default tug commands |
| Start pushback | Request pushback in GSX and select the saved route | Starting an aircraft EFB tug or another pushback add-on simultaneously |
| Stop the operation | The stop or abort option available in the GSX menu | Trying to steer with MSFS pushback-left or pushback-right bindings |
If a Quick Edit control does nothing, restore focus to the simulator, close any active search field and check Num Lock when the legend requests keypad input. Custom keyboard or controller assignments can alter editor behaviour, so inspect duplicate camera and slew bindings as well. For the surrounding service sequence, see our guide to the full GSX service workflow.
What does GSX QuickEdit save?
QuickEdit saves the selected route slot, endpoint and final aircraft heading against the occupied stand in the airport profile.
GSX uses those values to construct the tug manoeuvre from the configured parking position. The change is not an airport-wide rule, so adjacent gates and similarly named stand variants remain separate. It belongs to the airport profile, not the aircraft profile, control preset or scenery package.
User airport profiles are normally stored under %APPDATA%\Virtuali\GSX\MSFS. Back up edited profiles before replacing an imported airport profile or changing scenery; a route built for one version of an airport may not align with another.
How do I create both pushback directions?
Run QuickEdit separately for every route choice that should appear at the stand.
- Create the first route. Place the aircraft at its release point, set the final nose heading and save it to the appropriate slot.
- Repeat for the other direction. Reopen QuickEdit, choose the second slot and configure it independently.
- Test both routes. Return to the gate and verify each turn because clearance in one direction does not guarantee clearance in the other.
Labels such as left and right can refer either to the tug’s initial movement or the aircraft’s final direction. Where custom labels are available, use an unambiguous description such as Nose east or Face taxiway A.
Why is my edited GSX pushback missing or going the wrong way?
Most QuickEdit faults come from an incorrect stand or scenery profile, an unsaved route, reversed final heading or insufficient turning distance.
| Symptom | Likely cause and correction |
|---|---|
| The route is missing from the GSX menu | It was saved to another stand, left unconfirmed or loaded from a different scenery profile. Check the occupied stand and active airport profile. |
| The old route still appears | The menu or Couatl data has not refreshed. Restart Couatl, wait for GSX to initialise and reopen the airport at the same stand. |
| The aircraft finishes facing backwards | The final nose heading is reversed by roughly 180 degrees. Rerun QuickEdit and rotate the whole aircraft towards the required departure direction. |
| The tug makes an excessively sharp turn | The release point is too close to the stand. Move it farther along the taxiway centreline to provide more turning distance. |
| The route crosses grass or scenery | The endpoint or configured stand stop position is offset. Correct the stand first, then recreate the route instead of adjusting only the heading. |
| The route broke after changing scenery | The replacement airport uses different stand names or parking references. Select or rebuild a profile matching the installed scenery. |
| The route appears, but pushback will not start | This is usually a parking-brake, wheel-chock, aircraft-state, Couatl or competing-tug problem rather than a QuickEdit fault. Work through our GSX pushback start-up checks. |
Can I steer GSX manually during pushback?
GSX normally follows the selected saved route rather than accepting continuous steering from the standard MSFS pushback bindings.
Choose the correct route before starting. If the aircraft approaches an obstruction, stop or abort through GSX and correct the airport profile. Activating another tug controller during the manoeuvre can leave the aircraft, tug and GSX service state out of sync.