Why are jetways not working in MSFS 2020?
Jetways in Microsoft Flight Simulator 2020 usually fail because the stand has no functional animated jetway, the aircraft is outside the parking trigger, or airport scenery and ground-service add-ons conflict. Park precisely at a gate, set the parking brake, request the jetway through ATC Ground Services, then test with default content.
How do I connect a jetway in MSFS 2020?
Use a recognised gate and send the built-in jetway request only after the aircraft is correctly parked.
- Select a gate: Choose a parking position labelled as a gate rather than a runway, ramp or general-aviation stand. A visible jetway does not guarantee that it is animated, but ordinary ramp parking rarely provides one.
- Park accurately: Stop with the nose wheel near the stand’s stopping point and leave the forward left side of the aircraft accessible. Spawning directly at a gate can occasionally place an aircraft just outside the stand’s service trigger.
- Secure the aircraft: Set the parking brake. Shutting down the engines is sensible and may be required by third-party ground-handling systems, although stock jetway behaviour is not identical at every airport.
- Send the request: Open the toolbar’s ATC window, select Ground Services, then choose Request Jetway Connection.
- Leave the aircraft still: Allow the animation to finish before moving or opening doors. Repositioning the aircraft can interrupt the connection or leave the jetway visibly misaligned.
Jetways generally target the forward left passenger door. Small aircraft, freighters and add-on aeroplanes with unusual door positions may be outside the jetway’s movement limits even when the stand itself works.
Why is the jetway option missing or greyed out?
The command is unavailable when MSFS 2020 does not recognise the aircraft as being at a gate with an operable jetway.
- Wrong parking type: The position may be defined as a ramp, cargo stand or parking spot rather than a serviced gate.
- Static scenery: Some objects merely look like jetways. They have no animation or connection to the parking stand.
- Incorrect stopping position: The aircraft may be too far forward, too far back or offset from the centreline.
- Unsupported aircraft geometry: An add-on aircraft may have missing, inaccurate or unusual passenger-door data.
- Occupied gate: AI or live traffic can interfere with the stand or leave another aircraft assigned to it.
- Ground-service conflict: A third-party handling package may replace the normal request process or impose its own engine, beacon and parking requirements.
How do I isolate the exact jetway problem?
Cross-testing one default aircraft and one default airport quickly separates a scenery fault from an aircraft or add-on conflict.
- Establish a baseline: Load a default airliner at a large default airport and try several marked gates. One unsuccessful stand is not enough to prove that the simulator is broken.
- Test the suspect aircraft: Use the add-on aircraft at the gate that worked with the default aircraft. Failure now points to its door geometry or aircraft package.
- Test the suspect airport: Use the default aircraft at the original airport. If only that airport fails, its stand definitions or jetway models are responsible.
- Remove add-ons temporarily: On PC, test with an empty Community folder. Add-ons installed elsewhere must be removed through Content Manager because emptying Community does not disable them. On Xbox, remove the suspect airport, aircraft or ground-service package through Content Manager and restart the simulator.
- Restore packages individually: Add the airport scenery first, then the aircraft, then any ground-service utility. Testing one category at a time identifies the package that changes the behaviour.
| Test result | Likely cause | Best next step |
|---|---|---|
| Default aircraft works; add-on aircraft fails | Door position or aircraft configuration | Update the aircraft and try another compatible stand |
| One airport fails with every aircraft | Static or incorrectly configured scenery | Try another gate, then update or remove the airport package |
| Jetway moves but stops short | Aircraft parked outside its reach | Repark closer to the stop point or use a different stand |
| Jetway enters the fuselage | Door geometry and scenery model mismatch | Use another stand or aircraft; graphics settings will not correct it |
| Everything works with add-ons removed | Package conflict | Restore packages one by one |
A mistake we see constantly is installing an old airport simply because its folder appears to load. Read our explanation of why legacy FSX scenery is not automatically compatible with MSFS; an airport can display while its jetways and service definitions remain unusable.
When replacing suspect scenery, use airport packages explicitly made for the simulator. Our MSFS scenery and add-on library separates Microsoft Flight Simulator content from older simulator formats.
Can every visible jetway be made to move?
No; a jetway must be authored as an operable object and associated with the airport’s parking position.
If it is an ordinary static scenery model, there is no cockpit command or assistance setting that will animate it. Use another stand or replace the airport scenery with a properly configured MSFS 2020 version.
Do traffic, photogrammetry or graphics settings affect jetways?
Graphics quality and photogrammetry do not turn a static jetway into a functional one.
Traffic can still cause a practical obstruction if another aircraft occupies or clips the stand. In that case, choose a clear gate or temporarily reduce airport traffic. Airport vehicle density changes surrounding activity, not whether the jetway model itself is operable.
What if no default jetway works anywhere?
If default aircraft fail at several default airports, update and verify the simulator’s installed content before considering a full reinstall.
- Restart the flight and simulator: This clears a stuck airport-service state.
- Check Content Manager: Install available updates for the simulator’s base content and the airport being tested.
- Retest without add-ons: Use an empty Community folder on PC and remove other suspect packages through Content Manager.
- Verify the installation: Use the repair or file-verification function provided by the platform on which MSFS 2020 was installed.
A complete reinstall should be the last step. If one default aircraft connects successfully at even one default gate, the core jetway system works and the fault lies with the original stand, aircraft or add-on combination.