Fix FSX jetways that will not connect to add-on aircraft: check Ctrl+J, parking, aircraft.cfg exits, scenery, GSX and SODE.
In FSX and FSX: Steam Edition, jetways usually do not connect to add-on aircraft because the forward-left passenger exit is missing or misplaced in aircraft.cfg. Other common causes are poor parking alignment, disabled Advanced Animations, a static or out-of-range bridge, or scenery controlled by GSX, SODE, or another custom system.
Diagnose the jetway before editing aircraft.cfg
Testing a default FSX airliner at the same gate is the fastest way to separate an aircraft configuration fault from a scenery, control, or parking problem.
- Identify the jetway system. A native FSX animated jetway normally responds to
Ctrl+J. GSX, SODE, and airport-specific bridges may require their own menu, profile, or controller. - Test a default airliner at the same stand. Park it on the centreline with the forward-left passenger door beside the bridge. If it connects, the add-on aircraft's exit position or physical dimensions are the likely cause.
- Enable Advanced Animations. Native moving bridges require this FSX display option. If the bridges are not visible at all, also check Scenery Complexity.
- Check the control assignment. Confirm that the jetway attach or detach command is still assigned to
Ctrl+J. Another utility or a changed control profile may have intercepted it. - Repark the aircraft. Move slightly forwards, aft, or towards the correct side of the centreline. Jetways have fixed limits for extension, rotation, and height.
- Try a different gate. Some scenery objects look like working boarding bridges but are static models. No keyboard command or aircraft configuration edit can animate them.
Our guide to using Ctrl+J and identifying compatible FSX jetways covers the normal operating sequence. If positioning is the uncertain part, follow the gate parking and jetway alignment checks before changing configuration files.
When Ctrl+J does nothing
A completely silent Ctrl+J response usually points to the gate, control assignment, or animation settings rather than slightly inaccurate door coordinates.
Try the same gate with a default aircraft, then try another known animated gate. If no aircraft can activate the bridge, do not edit the add-on aircraft: verify Advanced Animations, the key assignment, scenery settings, and whether the bridge belongs to a custom system.
What each FSX jetway symptom usually means
| Symptom | Likely cause | Best next check |
|---|---|---|
| No movement with any aircraft | Static bridge, disabled animations, missing control assignment, or custom controller | Try a default airliner at another animated gate |
| Works with default aircraft only | Missing or incorrect add-on exit data | Inspect the add-on's [exits] section |
| Moves towards the cockpit or behind the door | Incorrect longitudinal exit position | Adjust the fore-and-aft coordinate |
| Targets the wrong side | Incorrect lateral coordinate or exit selection | Check the forward-left main exit |
| Reaches the fuselage too high or low | Incorrect vertical coordinate | Correct the door height relative to the model datum |
| Moves but stops short | Aircraft is beyond the bridge's physical reach | Repark or select a more suitable stand |
| Only GSX or SODE fails | Custom aircraft, stand, or airport profile problem | Use that system's configuration tools |
What if the jetways are completely gone?
If the jetways are completely gone, the problem is in the scenery layer or display settings rather than the add-on aircraft's door coordinates.
At every airport, check Scenery Complexity and confirm that the expected airport scenery is enabled. At one airport only, look for a scenery package that excludes the stock bridges without loading its replacements, an inactive supporting module, or duplicate airport layout files defining the same stands.
Do not delete scenery files at random. Our checks for missing jetways and conflicting FSX scenery layers explain how to distinguish disabled objects from an airport installation conflict.
Why is this showing only with one add-on aircraft?
If the problem is showing only with one add-on aircraft, that aircraft probably has missing, inaccurate, or incompatible passenger-exit data.
FSX does not inspect the visible model to discover the door. It reads the positions declared in the [exits] section of aircraft.cfg. A door can open correctly in the visual model while its configuration entry points the jetway towards the cockpit, the wrong side, or empty space.
An FSX exit entry uses this structure:
exit.N = opening_rate, longitudinal_position, lateral_position, vertical_position, type
The coordinates are measured in feet from that particular model's reference datum. Positive longitudinal values are forwards, negative lateral values are to the aircraft's left, and positive vertical values are upwards. Type 0 identifies a main exit; the stock jetway target is normally the first suitable main passenger exit, commonly exit.0.
The opening-rate value controls how quickly the associated door opens. It does not tell the jetway where the door is.
Correcting the aircraft.cfg exit position
Correct the existing forward-left main exit in small, controlled steps rather than copying coordinates from another aircraft.
- Close FSX and make a backup. The relative file location 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_exitsmatches the listed entries and that a type0main passenger exit exists. - Choose the correct axis. Adjust the longitudinal value if the bridge aims forwards or aft of the door. Change the lateral value for a sideways or wrong-side error, and the vertical value only for a height error.
- Change one value at a time. Make small adjustments while preserving the commas and the other fields. Large guessed changes make the result harder to diagnose.
- Confirm that the file really saved. Protected installation folders may block the edit or redirect it. Make sure the editor did not create a file named
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 gate and parking position.
Do not copy values from another Boeing, Airbus, or similar-looking model. Two developers can place the reference datum differently even when modelling the same aircraft type. One aircraft.cfg may also serve several liveries, so the change can affect every variation in that aircraft folder and may be overwritten by an add-on update.
What does GSX jetway not close enough mean?
A GSX jetway not close enough message means the bridge cannot physically reach the configured door or the aircraft has stopped outside the stand's expected position.
Repark on the centreline with the forward-left door level with the bridge. If the marked stop position still leaves the aircraft outside its range, use a stand intended for that aircraft size or correct the airport's stopping position and jetway profile.
If the same aircraft fails at many otherwise working GSX gates, inspect its GSX aircraft profile and door position. If only one gate fails, the airport stand or bridge association is the stronger suspect. Do not falsify an accurate global aircraft door position to compensate for one badly placed jetway, because that will cause failures elsewhere.
GSX bad jetway data and other custom-system warnings
A GSX bad jetway data warning normally identifies an airport, parking, profile, or custom-bridge configuration problem rather than a stock FSX aircraft.cfg error.
Confirm that the intended airport scenery is active and that another airport layout is not defining the same stands. Then use the custom system's own profile reload, rescan, or configuration process. GSX and SODE can store aircraft-door positions, stand coordinates, and bridge associations outside the native FSX jetway system.
Use our GSX, SODE, and custom-jetway troubleshooting process when stock Ctrl+J works but the add-on-controlled bridges do not.
What should I do if nothing worked?
If nothing worked, return to a controlled default-aircraft test and use the result to identify which layer is still failing.
- Restore the aircraft.cfg backup. This removes unsuccessful coordinate edits from the diagnosis.
- Use a default FSX airliner. Test it at a default airport gate known to contain an animated bridge, with Advanced Animations enabled.
- Test the add-on at the identical stand. Keep the parking position unchanged. If only the add-on fails, its exit data, dimensions, or custom aircraft profile remains the cause.
- Check for duplicate aircraft installations. Make sure you edited the
aircraft.cfgbelonging to the copy FSX is actually loading. - Separate stock and custom controls. Use
Ctrl+Jonly for native FSX bridges; use the relevant menu or profile for GSX, SODE, or airport-specific systems. - Change the test location. If the aircraft works at another airport, stop editing it and investigate the original stand or scenery package.
Reinstalling FSX is rarely the right first response. It cannot make a static bridge move, extend a jetway beyond its modelled limits, or repair one incorrect airport profile.
Limits of add-on aircraft and FSX jetway compatibility
Not every add-on aircraft can use every FSX jetway, even when both are installed correctly.
- Older conversions may have animated visual doors but no usable FSX exit entries.
- Very small, large, tall, or unusually shaped aircraft may sit outside a bridge's movement limits.
- Decorative jetways are static scenery and cannot be activated.
- Custom airport scenery may replace native FSX controls with GSX, SODE, or another system.
- Gates with multiple bridges depend on scenery-specific support and correctly profiled doors; stock FSX cannot reliably assign each bridge in a complex wide-body arrangement.