Fix FSX jetways that will not connect to add-on aircraft: test Ctrl+J, gate reach and animations, then correct aircraft.cfg exit data.
In FSX and FSX: Steam Edition, jetways usually fail to connect to add-on aircraft because the forward-left passenger-door coordinates in aircraft.cfg are missing or wrong. They also fail when Advanced Animations is disabled, the aircraft is beyond the bridge’s reach, or the gate is static or controlled by another add-on.
A jetway is the passenger boarding bridge beside an airport stand. The quickest fix is to establish whether FSX cannot move the bridge at all or can move it but cannot find the add-on aircraft’s door.
How do I find out why the FSX jetway is not connecting?
Testing a default FSX airliner at the same gate separates an aircraft configuration fault from a gate, scenery or control problem.
- Identify the jetway system. A standard FSX animated jetway normally responds to
Ctrl+J. GSX, SODE and airport-specific bridges may use their own menu, profile or controller instead. - Test a default airliner at the same stand. Keep it on the painted centreline and stop with its forward-left door beside the bridge. If the default aircraft connects, inspect the add-on’s exit data.
- Enable Advanced Animations. Standard moving bridges require the Advanced Animations option in FSX’s display settings. If the jetway is missing entirely, the airport may also require a higher Scenery Complexity setting.
- Check the jetway control assignment.
Ctrl+Jis the normal FSX command, but it may have been changed, removed or intercepted by another utility. Press it once and allow time for the bridge to start moving. - Reposition the aircraft. A bridge has limited extension, rotation and height. Move closer to the centreline or slightly forwards or aft rather than repeatedly pressing the command.
- Try another animated gate. Some scenery objects look like jetways but are static models. No keyboard command can animate a static bridge.
For the normal control sequence and gate-selection rules, see our guide to operating standard FSX jetways with Ctrl+J.
Why does Ctrl+J do nothing?
A completely silent Ctrl+J response points first to the control, animation or scenery layer—not to slightly inaccurate door coordinates.
The reports “still not happening”, “rien ne se passe”, “cela ne marche pas”, “זה לא עובד” and “нет не работают” all describe the same no-response symptom. Check that Advanced Animations is enabled, the key assignment still exists and the object is a native animated jetway. If no aircraft can activate that gate, editing the aircraft will not repair it.
What does each jetway symptom usually mean?
| Symptom | Likely cause | Best next check |
|---|---|---|
| No movement with any aircraft | Static bridge, disabled Advanced Animations or missing control assignment | Try another gate with a default airliner |
| Works with a default aircraft only | Missing or incorrect add-on exit data | Inspect the add-on’s [exits] section |
| Moves towards the cockpit or wrong door | Incorrect longitudinal or lateral door coordinate | Correct the forward-left passenger exit |
| Reaches the fuselage too high or low | Incorrect vertical coordinate | Adjust door height relative to the aircraft datum |
| Moves but stops short | Aircraft is outside the bridge’s physical reach | Repark or use a more suitable stand |
| Jetway disappeared after installing scenery | Scenery complexity, duplicate airport data or a conflicting scenery layer | Check the active airport scenery before editing the aircraft |
| Only GSX or another custom system fails | Airport profile, aircraft profile or custom jetway data mismatch | Use that system’s configuration rather than stock Ctrl+J settings |
Why do aircraft.cfg door coordinates matter?
FSX does not inspect the visible model to discover where the door is. It reads the exit positions declared in the aircraft’s [exits] section and normally aims the bridge at the first suitable main passenger exit.
An FSX exit entry follows this structure:
exit.0 = opening_rate, longitudinal_position, lateral_position, vertical_position, type
The position values are measured in feet from that model’s reference datum. Positive longitudinal values are forwards, negative lateral values are to the aircraft’s left, and positive vertical values are upwards. A type value of 0 identifies a main exit.
The opening rate affects the door animation, not its location. A mistake we see constantly in converted or older aircraft is a door that opens visibly but has no matching FSX exit position. A working door animation therefore does not prove that the jetway has a valid target.
How do I correct an add-on aircraft’s exit position?
Correct the existing forward-left main exit in small steps rather than copying coordinates from a different aircraft.
- Close FSX and back up the configuration. The relative path is normally
SimObjects\\Airplanes\\<aircraft folder>\\aircraft.cfg. The installation root differs between boxed FSX, Steam Edition and custom library locations. - Find the
[exits]section. Confirm thatnumber_of_exitsagrees with the listedexit.nentries and that a type0passenger exit exists. - Identify the relevant axis. If the bridge aims forwards or aft of the door, adjust the longitudinal value. If it targets the wrong side or misses sideways, correct the lateral value. Change the vertical value only when the target height is wrong.
- Change one value at a time. Use small adjustments and retain the comma-separated syntax. Large guessed changes make it difficult to tell which value corrected the problem.
- Verify that the file was saved. Windows permissions can prevent changes inside protected installation folders. Also make sure the editor has not created
aircraft.cfg.txt. - Reload the aircraft fully. Select another aircraft and return to the add-on, or restart FSX. Retest at the same known working stand and parking position.
Do not copy numbers blindly from another Boeing, Airbus or similar-looking model. Add-on developers can place the reference datum differently even on two representations of the same aircraft type. Our worked 767 and 777 door-position examples show the method, but their values should only be used with the models for which they were written.
Remember that one aircraft.cfg usually serves every livery in that aircraft folder. A change can therefore affect all of those variants, and an add-on update may overwrite it.
What if GSX reports bad jetway data?
“GSX bad jetway data” normally indicates an airport, parking or custom-bridge configuration problem rather than a stock FSX passenger-door error.
Make sure the intended airport scenery is the active one and that a second AFCAD or airport layout is not defining the same stands. If the scenery or profile has changed, use the add-on’s own reload, rescan or profile-refresh process before editing door positions. Disable conflicting airport definitions carefully rather than deleting files at random.
GSX and SODE can use their own aircraft profiles, stand coordinates and jetway associations. They may also impose operational conditions such as a set parking brake or a particular service sequence. Our GSX, SODE and custom-scenery troubleshooting checks cover that separate control layer.
What does “GSX jetway not close enough” mean?
A jetway that is not close enough has run out of physical reach or has been associated with the wrong stopping position.
First repark on the stand centreline with the forward-left door level with the bridge. If the marked stop position still leaves the aircraft outside its range, choose a stand designed for that aircraft or correct the custom airport profile. Do not falsify otherwise accurate aircraft door coordinates to compensate for one badly positioned gate; that will make the aircraft miss jetways elsewhere.
Can GSX Pro operate multiple jetways?
Multiple jetways require the airport scenery to contain separate functional bridges and the custom system to recognise the correct stand and aircraft doors.
GSX Pro refers to the Microsoft Flight Simulator edition, not stock FSX. Its airport and aircraft profiles govern the result; FSX aircraft.cfg edits do not apply to packaged MSFS aircraft. GSX cannot turn a static bridge model into an animated one or create physical reach that the scenery object does not have.
Stock FSX does not provide dependable per-bridge selection for complex wide-body arrangements. A gate with two or three bridges is therefore scenery- and controller-dependent, and each bridge needs a reachable, correctly profiled door.
Can every add-on aircraft use an FSX jetway?
No. The aircraft needs a valid main-exit position, and the airport needs a compatible animated bridge capable of reaching that exit.
- Older conversions may contain custom visual doors but no usable FSX exit data.
- Small aircraft and unusually large or high-door aircraft may not fit the bridge’s movement limits.
- Some airport bridges are decorative static objects.
- Custom scenery may replace the stock control system with GSX, SODE or another scenery-specific method.
- Multiple-bridge gates generally need custom airport and aircraft profiles.
What does MISM-430 mean?
MISM-430 is not a standard FSX jetway command, aircraft.cfg field or stock Ctrl+J error code.
If it appears in scenery object metadata, an airport editor or an add-on log, treat it as a model or object identifier whose precise meaning belongs to that add-on. It does not by itself diagnose the aircraft door. Determine whether the identified bridge is controlled by stock FSX or a custom system, then use the appropriate checks above.
Is “inspect the fuel lever on the ship’s bridge” a jetway instruction?
No. A ship’s bridge is the vessel’s control room, not an airport passenger boarding bridge. If a mission or another title displays inspect the fuel lever on the ships bridge, follow that task’s interaction prompts; Ctrl+J and FSX aircraft exit coordinates cannot advance it.