I've found that in some airports in 2024 (even default LFPG and LEMD), jetways do not move at all, either if requested via GSX or using the aircraft EFB. I've seen that a workaround is using the default ATC menu for calling the jetway. However, as soon as I tried that, the jetway simply disappeared.

Does anybody know of another method of forcing the jetway to move? In FSX/P3D you could use Ctrl+J or enter the SODE menu and trigger it from there (depending on the jetway type). In the meantime, I canceled the flight in 2024 and I'm trying in 2020.

Edited August 25, 2025Aug 25 by Luis Hernandez

If it’s near a helipad that “airport” will override the one you are at and you won’t be able to use the jetways. 

I know I have the same problem at Orly LFPO. To get the gateways to work, I deactivate VOLOPORT in my library and it works.

4 hours ago, Axis3600 said:

I deactivate VOLOPORT in my library

Is this something that comes in MSFS2024 by default? I'm away from my rig until tonight (AR time), so I can't check yet.

Yes it is included by default in the MSFS library just disable it.

12 hours ago, Luis Hernandez said:

I've found that in some airports in 2024 (even default LFPG and LEMD), jetways do not move at all, either if requested via GSX or using the aircraft EFB

I don’t know how different it is to P3D but there’s a Stop position in GSX which may be further forward or backward to the Parking position.

In P3D GSX you can move either so they’re identical. I do this frequently to make them match so the jetway will move.

For what it's worth, I found that changing the length of the Jetway sometimes helps, if it is not a BGL one and embedded.

I am not clever enough to change stop positions!

12 minutes ago, IanHarrison said:

I am not clever enough to change stop positions!

Dead easy. Display the GSX menu ensuring you have a good aerial view of the front of the aircraft. A four o’clock position is fine.

Select the top option related to Parking position. Let GSX load its stuff and you’ll see lot of lines. That is the position as stored by the airport data in the sim.

Now press F4. Its position will probably change significantly. That’s the Stop position. The one GSX uses when you use that menu to position the aircraft at a chosen gate.

In F4 mode use the cursor arrows to move the Stop position to the parking position. Use F1 and F4 keys to toggle the view. When they’re identical and assuming the parking position has an aircraft door near the jetway it will work.

Hit Y to exit the GSX setup. The positions are automatically saved.

It IS the bug related to the nearby heliport and there are hundreds of them I guess. I had one guy over at discord (or was it here) that provided a 10min fix (for him, for me it would take two hours) for another affected airport, NZAA. Sadly, even if you globally deactivate heliports, the jetways still do not work. So either you find someone who deactivates the nearby heliport(s) for you or you might have a chance enlightening the dev of the addon airport (if it is an addon airport of course). 

BUT: the workaround with the default ATC works. You simply have to take care that you do not do ANY GSX operation prior calling the jetway this way or it will disappear. Means: if you already clicked anything in the GSX menue, your done, the jetway wont work.

@virtuali I still miss the explanation for this behaviour. WHY does the jetway work if called via the default ATC command menue and not via GSX? Why does the jetway disappear if any action of GSX was executed BEFORE the call via default ATC menue? 

3 hours ago, Ray Proudfoot said:

Dead easy. Display the GSX menu ensuring you have a good aerial view of the front of the aircraft. A four o’clock position is fine.

Select the top option related to Parking position. Let GSX load its stuff and you’ll see lot of lines. That is the position as stored by the airport data in the sim.

Now press F4. Its position will probably change significantly. That’s the Stop position. The one GSX uses when you use that menu to position the aircraft at a chosen gate.

In F4 mode use the cursor arrows to move the Stop position to the parking position. Use F1 and F4 keys to toggle the view. When they’re identical and assuming the parking position has an aircraft door near the jetway it will work.

Hit Y to exit the GSX setup. The positions are automatically saved.

Thanks Ray, I'll give it a go.

14 hours ago, Axis3600 said:

I know I have the same problem at Orly LFPO. To get the gateways to work, I deactivate VOLOPORT in my library and it works.

Didn't work. At least at SACO (my home airport, and thus, the one I care the most about) by Simulación Extrema, it didn't. At least using the ATC menu didn't hide the jetway. In MSFS2020 it works as expected.

6 hours ago, AnkH said:

It IS the bug related to the nearby heliport and there are hundreds of them I guess.

I guess 500 m is not far enough 😢. Any way to raise Asobo a ticket about that? The existing thread with that issue has no voting options and I don't feel like dealing with it while waiting 3-6 months for SU4.

6 hours ago, AnkH said:

BUT: the workaround with the default ATC works. You simply have to take care that you do not do ANY GSX operation prior calling the jetway this way or it will disappear. Means: if you already clicked anything in the GSX menue, your done, the jetway wont work.

Interesting: that's why this time the ATC menu worked. So, if I arrive to an airport, I'd have no other option than either enabling ground services and pray that the jetway works there, or just finding parking on my own? 😒

I guess at arrival things like selecting the gate via GSX is no issue. Just park at the assigned gate and call the jetway via ATC menue BEFORE you do any deboarding stuff via GSX.

On 8/25/2025 at 5:14 PM, AnkH said:

WHY does the jetway work if called via the default ATC command menue and not via GSX?

GSX sends the standard TOGGLE_JETWAY key event, that's all what it does, the rest is completely up to the sim. That's the only way each and every other add-on that could also trigger jetways ( like an airplane EFB, for example ), can use to operate a jetway.

The default ATC, instead, might use a different (internal) method that add-ons don't have access to, which might not be affected by the "nearby helipad" bug.

On 8/24/2025 at 9:37 PM, Luis Hernandez said:

I've found that in some airports in 2024 (even default LFPG and LEMD), jetways do not move at all, either if requested via GSX or using the aircraft EFB. I've seen that a workaround is using the default ATC menu for calling the jetway. However, as soon as I tried that, the jetway simply disappeared.

Does anybody know of another method of forcing the jetway to move? In FSX/P3D you could use Ctrl+J or enter the SODE menu and trigger it from there (depending on the jetway type). In the meantime, I canceled the flight in 2024 and I'm trying in 2020.

I figured out how to disable the helipads in the scenery using Dev Mode. Copying a simple scenery folder into Community solves the problem!

Check Flightsim.to for my upload of LEMD...I'll check out LFPG and fix that too if I can.

 

Edit: I just tried a few gates at Charles De Gaulle and the jetways appeared to be working OK. If you have a specific terminal or gate that you want me to check, let me know.

Edited October 19, 2025Oct 19 by Matt2218
Results of investigation

Thanks, Matt. I have yet to try this (I'm in the middle of a flight), but I know there are two airports I'm interested in that have this problem: default KMIA (at least the mid-high D gates, north side) and Simulación Extrema SACO.

It's this file, correct?

https://flightsim.to/file/99117/madrid-lemd-jetway-control-fix