Add working jetways to X-Plane 12 airports with WED. Learn which assets animate, how to export them, and why a bridge may not connect.
To add working jetways to an X-Plane 12 airport, edit the airport in WorldEditor (WED), replace static bridge objects with native animated jetway assets, align each bridge with its parking stand, validate the project, and export the scenery pack. Keep that pack above Global Airports, then test the jetway with a compatible aircraft.
Which type of jetway should you add?
For new X-Plane 12 airport work, use the simulator’s native animated jetway assets unless the airport already depends on another jetway system.
| Jetway type | Best use | Main limitation |
|---|---|---|
| Native X-Plane 12 jetway | New or updated XP12 scenery | Placement and aircraft-door geometry must be compatible |
| SAM jetway | Maintaining scenery already authored for SAM | Requires the matching plugin and authoring method |
| Static jetway object | Visual detail where movement is unnecessary | Cannot dock or retract |
Do not assume that an object resembling a boarding bridge is animated. Many older airport packages use ordinary .obj models, which remain fixed regardless of the jetway command.
How do I add native animated jetways in WED?
- Back up the airport package. Never edit X-Plane’s installed default airport scenery in place because an update can replace it. Create or edit a separate package under
Custom Scenery. - Open the complete airport in WED. Use its
earth.wed.xmlproject when one is supplied. Otherwise, create a project and import both the airport data and scenery DSF; importing onlyapt.datdoes not recover buildings, objects or existing bridges. Our WED airport-editing walkthrough covers the wider project and validation process. - Remove the static bridge. Delete or hide any existing jetway object at the stand. Leaving it behind produces overlapping bridges when the animated one moves.
- Select an XP12 native animated jetway. Search WED’s library and check the resource description and preview. Place or draw the asset using the tool required by that resource type. A generic bridge object will not acquire animation merely because it is positioned beside a gate.
- Align the bridge with the stand. Put the fixed end against the terminal and aim the moving cabin towards the aircraft’s forward boarding-door area. The ramp start should place a suitable aircraft inside the bridge’s reach without requiring excessive extension or rotation.
- Check surrounding clearance. Allow room for the jetway to retract and swing without entering the terminal, another bridge, service vehicles or the neighbouring stand.
- Validate and export for X-Plane 12. Resolve WED errors, set an appropriate XP12 export target and export the full scenery pack. Exporting airport data alone will not write the jetway placement.
- Test from the intended ramp start. Reload the airport, spawn a suitable airliner at the gate and operate the bridge through X-Plane or the aircraft’s supported ground controls. The separate explanation of native, SAM and legacy jetway controls covers the cockpit-side procedure.
When installing the finished package, check that its folder is not nested an extra level and that its entry sits above Global Airports in scenery_packs.ini. See our X-Plane scenery installation and load-order guidance if the edited airport does not appear.
Can I make an existing static jetway move?
A static jetway cannot be converted into a working one by changing a WED property; it must be replaced with an animated asset or rebuilt for a supported jetway system.
This is a mistake we see often with older scenery. The airport may look correct, but the bridge is simply a fixed model. Mixing a native animated bridge with the old static model also causes doubled geometry, so remove the original rather than placing the new bridge over it.
Why will the jetway not connect?
Most connection failures come from scenery priority, incorrect bridge geometry, an unsupported aircraft-door position or a mismatch between native and plugin-controlled jetways.
- The wrong airport is loading: another package or Global Airports is overriding the edited scenery. Confirm the active package and its order in
scenery_packs.ini. - The asset is static: inspect it in WED and verify that it is an XP12 animated jetway resource rather than an ordinary object.
- The aircraft is outside the operating envelope: adjust the ramp start or bridge placement. Moving only the painted stand markings does not change where the aircraft spawns.
- The aircraft door is incompatible: test a default airliner at the same stand. If that works, the add-on aircraft’s door definition or custom ground logic is the likely cause.
- The systems do not match: a SAM-authored bridge needs its compatible runtime; X-Plane’s native jetway command does not turn every third-party bridge into a native one.
- The export was incomplete: save the WED project, export the scenery pack again and reload the airport fully.
Does every aircraft work with native jetways?
No; successful docking depends on the aircraft’s size, parking position and defined boarding-door location.
Test each stand with the aircraft category it was designed to handle. A bridge positioned for a narrow-body may not reach a regional aircraft correctly, while a wide-body can place its door beyond the same bridge’s travel. Aircraft-specific doors and service panels may also control when boarding is available, as explained in our guide to X-Plane 12 ground-service compatibility.