FSX jetways do not connect to AI aircraft by design. Learn why Ctrl+J only serves the user aircraft, what will not fix it, and add-on options.
In FSX and FSX: Steam Edition, stock animated jetways are designed for the user aircraft, not AI traffic. Ctrl+J calls a compatible bridge only to the aircraft you are flying. An AI airliner can park correctly at a gate while its jetway stays retracted; this is normal, not a fault.
Is a retracted jetway beside AI traffic normal?
Yes, a stock FSX jetway remaining retracted beside an AI aircraft is normal simulator behaviour. The traffic engine can assign a suitable parking space, taxi the aircraft into position and arrange its departure, but it does not send the command that makes the passenger bridge move.
There is no difference between boxed FSX and FSX: Steam Edition in this respect. The retracted bridge does not disrupt the AI aircraft's schedule, pushback or departure.
Why does Ctrl+J not work for AI aircraft either?
Ctrl+J sends a jetway request for the user aircraft only. Switching the camera to an AI airliner does not make that aircraft the user aircraft, so pressing the command while watching AI traffic will not dock the bridge to it.
The user aircraft must be at a compatible animated gate and positioned close enough to the expected stopping point. Our guide to positioning the aircraft and operating FSX jetways covers those requirements without confusing them with the separate AI limitation.
Can aircraft.cfg exit positions fix an AI jetway?
No edit to aircraft.cfg will make a stock FSX jetway respond to AI traffic. Passenger-door coordinates in the [exits] section help the bridge find the correct door when that model is being flown as the user aircraft; they do not add AI control.
A mistake we see repeatedly is changing an AI model's exit coordinates even though the bridge is behaving exactly as FSX intended. If the same model also fails when loaded as the user aircraft, check the separate causes involving add-on aircraft door positions, parking alignment and scenery compatibility.
How can I confirm that this is only the AI limitation?
A successful user-aircraft test at the same type of stand confirms that the jetway itself is working.
- Identify the bridge. A static scenery object may look like a jetway but cannot animate. Custom airport scenery may use its own controller rather than the stock FSX system.
- Load a default airliner as the user aircraft. Choose an empty stand with a known animated bridge and place the aircraft squarely on the parking line.
- Press Ctrl+J. Allow time for the animation to begin; a bridge may retract or reposition before moving towards the door.
- Interpret the result. If the bridge serves your aircraft but remains retracted for AI at that stand, FSX's AI limitation is confirmed. If it also fails for the user aircraft, investigate positioning, scenery and aircraft-door data instead.
If the actual problem is that no AI airliner reaches the stand, jetway troubleshooting will not solve it. Check the separate causes of AI traffic missing from airport gates, including traffic density, schedules and parking-space size.
Will traffic or ground-vehicle settings make AI jetways move?
No FSX traffic or airport-vehicle setting enables stock jetways for AI aircraft. These controls affect what appears around the airport, not who can command the bridge.
- Airline traffic density changes the amount of scheduled AI traffic.
- Airport vehicle density changes the number of service vehicles operating around supported airports.
- Parking radius and airline codes influence which stands AI aircraft can use.
- Scenery settings may affect whether certain airport objects are displayed, but they do not add AI docking logic.
Replacing an AI model or installing a different traffic package will not make stock jetways AI-aware either.
Can an add-on make jetways connect to AI aircraft?
Some third-party jetway systems can animate for AI traffic, but only when that capability is explicitly supported by the controller and airport scenery. Installing a ground-service add-on does not automatically convert every stock FSX bridge.
| Jetway type | AI docking in FSX | What to do |
|---|---|---|
| Stock animated FSX jetway | No | Use it with the user aircraft and leave it retracted for AI |
| Static scenery jetway | No animation for any aircraft | Use compatible animated scenery if movement is required |
| Custom or add-on-controlled jetway | Varies by system and scenery | Confirm that the specific controller and airport support AI docking |
First establish whether the airport uses stock bridges or a custom system such as GSX- or SODE-controlled scenery. Where GSX controls the stand, follow the checks for GSX, SODE and custom-jetway compatibility rather than editing stock FSX settings.
Do not assign two controllers to the same bridge. Competing stock and custom objects can produce duplicated jetways, overlapping models or a bridge that fails to move. If an add-on does not expressly claim AI docking support, assume its jetways are intended for the user aircraft only.