Fix FSX jetways that will not connect to add-on aircraft by checking door coordinates, parking position, animations and scenery compatibility.
FSX jetways usually fail to connect to an add-on aircraft because the aircraft’s main passenger-door coordinates in aircraft.cfg are missing or wrong. The same symptom occurs when the aircraft is parked outside the jetway’s reach, advanced animations are disabled, or the scenery uses a static or unsupported jetway.
This applies to both boxed FSX and FSX: Steam Edition. The quickest diagnosis is to separate an aircraft configuration problem from a gate, scenery or simulator setting problem.
How do I find out what is preventing the connection?
- Test a default airliner at the same gate. Park it in roughly the same position and press
Ctrl+J. If the jetway works, the add-on aircraft’s exit configuration or dimensions are the likely cause. - Confirm that the jetway is animated. Many airport models look like jetways but are static scenery objects. FSX cannot move them, regardless of the aircraft used.
- Enable Advanced animations. This option must be selected in FSX’s display settings for standard animated jetways to move.
- Reposition the aircraft. Stop on the gate centreline with the forward-left passenger door within the bridge’s reach. Being a few metres too far forward, aft or sideways can prevent movement or leave the bridge short of the fuselage. Our gate-positioning and pushback walkthrough explains the normal parking and control sequence.
- Check the aircraft’s exit data. If the gate works with default aircraft but not the add-on, inspect the add-on’s
aircraft.cfg.
For more detail on the standard command, supported gates and door targeting, see our explanation of how FSX selects and operates animated jetways.
Why do the door coordinates matter?
FSX does not find a passenger door by examining the visible aircraft model. It reads the exit positions declared in the [exits] section of aircraft.cfg and moves the jetway towards a suitable main exit, normally the forward-left passenger door.
An exit entry follows this general structure:
exit.0 = opening_rate, longitudinal_position, lateral_position, vertical_position, type
The three position values locate the door relative to the aircraft’s reference datum. If they describe the wrong side, height or longitudinal position, the bridge may aim at the cockpit, stop short, pass through the fuselage or refuse to move.
A mistake we see frequently with converted or older add-ons is a visually animated door without matching FSX exit data. Opening the door successfully does not prove that the jetway has a valid attachment point.
How can I correct the aircraft.cfg exit position?
- Close FSX and make a backup. The file is normally inside
SimObjects\Airplanes\<aircraft folder>\aircraft.cfg. - Find the
[exits]section. Check thatnumber_of_exitsagrees with the listed entries and that a main passenger exit exists. - Correct the forward-left door entry. Use values supplied with the aircraft where available. Otherwise adjust one position value at a time, reload the aircraft and observe where the jetway is aiming.
- Preserve the configuration syntax. Keep the comma-separated fields and decimal points intact. A malformed line may cause FSX to ignore the exit.
- Retest at a known working gate. Keep the aircraft position consistent so that a parking change is not mistaken for a configuration improvement.
Do not copy exit coordinates blindly from another aircraft. Even two models of the same airliner can use different reference datums, so identical numbers may put the target several metres away from the actual door.
What does each jetway symptom usually mean?
| Symptom | Likely cause | Best next check |
|---|---|---|
| Works with default aircraft only | Missing or incorrect add-on exit coordinates | Inspect the add-on’s [exits] section |
| No movement with any aircraft | Static jetway, disabled animations or changed key assignment | Test another animated gate and check FSX settings |
| Bridge moves but misses the door | Incorrect door position or poor parking position | Repark, then correct the exit coordinates if necessary |
| Bridge stops before reaching the fuselage | Aircraft is outside the jetway’s physical reach | Move closer to the stand centreline or try another gate |
| Only a custom jetway system fails | Aircraft profile or scenery data mismatch | Check that system’s aircraft and airport configuration |
What if the airport uses GSX or custom jetways?
Default FSX jetways and GSX-controlled or scenery-specific bridges are not the same system. A custom system may use its own aircraft door profile, parking coordinates and airport data instead of relying solely on the standard FSX exit entry.
If the failure involves GSX, use our checks for GSX aircraft profiles, parking positions and custom scenery. Repeatedly editing aircraft.cfg will not fix a separate GSX profile error.
Can every add-on aircraft use an FSX jetway?
No. The aircraft needs a suitably positioned main exit, and the gate must have a moving bridge capable of reaching it. Some older conversions, unusually sized aircraft and models using only custom door animations are not configured for standard FSX jetways.
Native FSX also normally operates a single standard bridge rather than coordinating several jetways around a wide-body aircraft. Multiple bridges, unusual door layouts and scenery-specific animations generally require a compatible custom system rather than the default Ctrl+J function.