This document contains some quick visual tips for avoiding common pitfalls that cause airports to get declined by the Gateway moderator. Situations vary, and these suggestions may not apply in all instances.

In World Editor (WED)

Ramp Starts

Place WED in “Taxi+Flow” Mode when working with ramp starts. Ramp start footprints are displayed which are useful for managing incursions.

image16

Examples of incursions:

image1

WRONG

image4

RIGHT

image9

WRONG

image5

RIGHT

Appropriateness of ramp sizes is also considered:

image2

WRONG

(Too large for the runway at this airport.)

image3

RIGHT

(Suited to the runway at this airport.)

Taxiway / Runways

Joins for runways with shoulders should overlap up to the runway edge. (See “Correctly Forming Taxiways and Junctions“ for more information.)

image6

WRONG

image7

RIGHT

Airport Boundary

There is a fine line to walk between making the boundary too loose versus too complex. Also ensure that all runways, taxiways and ramps are completely inside the airport boundary.

image10

WRONG

(Too loose)

image13

WRONG

(Too complex)

image8

WRONG

image12

RIGHT

Taxi Routes

For guidelines on how to properly draw taxi routes, see “ATC Taxi Route Authoring.”

image17

WRONG

(Hot zone extends too far)

image14

WRONG

(Hot zone overlays runway)

image11

WRONG

(Micro-management of taxi routes)

image15

RIGHT

Ground Routes

Details on creating proper service vehicle routes can be found here in the WED manual.

image23

WRONG

(Route exists without parking spot(s) or destination(s) – must have both)

image26

WRONG

(Mismatched parking and destination types)

image19

WRONG

(Parking spot(s) too far from ground route network)

image18

RIGHT

(Parking spots and corresponding destinations – close to network)

Avoid route incursions as well:

image21

WRONG

(Route is touching, or too close to, an object/facade)

image25

RIGHT

(Ground traffic has room to maneuver and avoid objects and facades)

Avoid trying to micromanage the route:

image22

WRONG

(Micro-management of ground routes will compete with desired behavior when servicing aircraft, or parking)

image27

RIGHT

(Place a ground-route node near each aircraft. This is where the trucks will leave, and join the network, when providing service)

In X-Plane

Temporarily remove the Custom Scenery/Global Airports folder when testing your airport in X-Plane.

image24

Use maximum World Objects setting when testing your airport.

image20

Incursions

Check for trees on ramps, taxiways or runways:

image32

Check for road network segments on ramps, taxiways or runways:

image31

Check for objects partially buried inside other objects:

image33

Runway Layout and Appearance

Check runway hierarchy to ensure numbers are not obscured by an overlaying runway:

image28

WRONG

image29

RIGHT

Check runway numbers are present at both ends of the runway (except where runway numbers are not present in reality):

image30

Check grass/gravel/dirt is not above pavement:

image34

8 comments on “Tips for getting your airport approved on the Gateway

  1. I have a question about uploading real airports not included in XP-11. I have been working on scenery for the Bahamas, there are a lot of airports not included in the basic airport. When I try to upload the airport to the gateway using the latest non-Beta WED, I get a server 404 error, no airport with that name.

Leave a Reply

Your email address will not be published. Required fields are marked *

Please do not report bugs in the blog comments.
Only bugs reported via the X-Plane Bug Reporter are tracked.