The X-Plane universe is vast, but it truly becomes your own when you start molding it. World Editor (WED) is the official tool from Laminar Research that allows you to transform default airports into living, breathing hubs of detail. Whether you are crafting a realistic rendition of your local general aviation field, building a fictional hub for your virtual airline, or submitting a high-fidelity airport to the Scenery Gateway, the workflow involves much more than just placing a few buildings.

This guide provides a comprehensive, production-oriented workflow. It moves beyond the surface-level tutorials to cover the critical topics that separate hobbyist projects from professional-grade scenery: precise geometry, AI-compatible taxi networks, library utilization, terrain integration, and validation. By working through these steps, you will have a complete understanding of how to build an airport that looks great and functions perfectly in the simulator.

Getting Started with World Editor

Downloading and Installing the Latest WED

First, you need the latest version of the application. The X-Plane developer website is the definitive source. Avoid outdated versions found in package managers, as the scenery format updates frequently. Download WED from the official World Editor page and unzip it. The application is self-contained and runs directly without installation, making it portable across different systems. A stable internet connection is recommended because you will frequently download data directly from the X-Plane scenery gateway and base mesh.

Mastering the Interface

When you first open WED, the interface can seem dense. However, it is logically divided into four primary panels:

  • Map View: The central canvas where you visually build and edit geometry.
  • Hierarchy: The side panel listing every object, polygon, and property in your project. Organization here is critical for complex airports.
  • Toolbar: The top icons for selection, drawing runways, taxiways, polygons, ramps, and exclusion zones.
  • Palette: The resource browser where you search for objects from the default library or add-on libraries like OpenSceneryX.

Take time to learn the keyboard shortcuts. Spacebar toggles between the select and pan tools. Shift+Click adds to a selection. Delete removes items. A fluid workflow in WED depends on spending less time clicking menus and more time editing geometry.

Initial Project Configuration

Launch WED and select "Create New Scenery." Give it a descriptive name, such as "KLAX – Custom Hub." The first practical step is to download the existing default airport data. Go to File > Download Scenery. Enter the target airport ICAO code. This downloads the apt.dat (pavement, ramps, taxi routes) and the DSF base mesh for that tile. This gives you a starting point, allowing you to see how the default airport is laid out and what needs to be replaced or supplemented. Never build from a completely blank canvas if you intend to match real-world location coordinates.

Geometry: Building the Core Infrastructure

Geometry is the skeleton of your airport. It dictates how the simulator interacts with the surface and how AI aircraft move. Do not rush this phase.

Runways and ILS

The Runway Tool is simple but precise. Click and drag to set the length, or manually enter the exact dimensions in the property panel. You must define:

  • Surface: Asphalt, concrete, grass, or dirt. This affects friction and sound.
  • Markings: Precision instrument, non-precision, visual, or none.
  • Lighting: Edge lights, centerline lights, touchdown zone lights, and approach lighting system (ALS).
  • ILS Setup: In the runway properties, set the localizer and glideslope frequencies. Ensure the heading aligns perfectly with the runway end.

Double-check the runway heading. A one-degree error can cause ILS misalignment. Use real-world charts or Google Earth to verify the true heading.

Taxiways and Aprons: The Pavement Network

Do not use the Runway tool for taxiways. Use the Taxiway Tool. This creates a polygon with specific pavement properties. You can control the smoothness, surface type, and lighting. Use the Polygon Tool for irregularly shaped aprons or ramps outside the main taxi lane network.

Key property to understand: Smoothness. A value of 1.0 is perfectly smooth (like fresh asphalt). Lower values simulate rough terrain or gravel. For ramps, keep smoothness high to prevent aircraft from bouncing.

Proper marking lines are essential. Taxiway centerlines and edge lines are drawn using the Line Tool. Set the line type to "Yellow" or "White" and adjust the width. For complex intersections, use the bezier curve tool to make smooth turns.

Ramp Starts: Parking and Airline Codes

Ramp starts dictate where aircraft spawn and how AI parking works. Use the Ramp Start Tool. Place the start, then rotate it to match the parking direction.

Critical properties to configure:

  • Operation Type: Gate (jetway), Tie-Down (general aviation), Hangar, or Cargo.
  • Airline Codes: This is the most common point of failure for AI traffic. Assign the correct ICAO airline code (e.g., AAL for American, UAL for United, SWA for Southwest). If you want a gate to be generic, leave it blank. Use the Ramp Groups feature to assign multiple airlines to a single gate.
  • Gate Name: Use real gate numbers (e.g., A12, B7). This helps with ground services and ATC communication.

The Active Taxi Network: Making AI Work

An airport with no taxi network looks dead. The Taxi Route Tool defines how AI aircraft move between runways and ramps. You must draw one-way paths. Use Start and End nodes.

For a runway, you typically have a Runway type taxi route. For taxiways, use Taxiway. Define Hold Shorts at runway intersections. These are invisible lines where AI stops and waits for clearance.

The most common validation error is a disconnect in the taxi network. Every ramp start must be connected to the taxi network, and the network must have a clear path to the runway. Use the Validate button to check this.

Object Placement and Library Utilization

Once the pavement is down and the taxi network is connected, you can populate the airport with structures and objects.

Essential Object Libraries

The default Laminar library is functional but limited. For higher visual fidelity, most scenery developers use community libraries. These are free to download and use. The most important ones are:

  • OpenSceneryX: The standard library, containing thousands of objects, vehicles, people, and vegetation.
  • MisterX Library: High-quality static aircraft, vehicles, terminals, and jetways.
  • CDB Library: Excellent European-style buildings and details.

When using these, remember that users must have them installed. Always specify library dependencies in your scenery description.

Structures, Facades, and Jetways

Use the Object Tool to place static 3D models like hangars, towers, and cargo sheds. Use the Facade Tool for terminal buildings. Facades are "smart" objects that stretch and form walls, roofs, and windows based on a footprint you draw. This allows you to create a terminal of any shape or size using a single facade asset.

Jetways are animated objects. They require a Ramp Start with a specified gate name to function. Place the jetway base exactly at the gate location.

Lighting and Markings

Beyond runway lights, add apron flood lights, terminal building spotlights, and street lights along access roads. WED has a Lighting Tool specifically for shared-use lighting objects.

For custom markings (e.g., airline logos, terminal number decals), use the Decal Tool. This allows you to apply a texture to a polygon that sits on top of the pavement. This is often used for "NO PARKING" zones, safety lines, or custom ground signage.

Environmental Detailing

An airport does not exist in a void. Proper environmental integration makes the scene believable.

Orthoimagery

To achieve pinpoint accuracy, use an orthophoto. Download a GeoTIFF of your airport location from sources like USGS EarthExplorer or free satellite imagery providers. In WED, go to File > Import Orthophoto. Align the image using specific control points (e.g., runway corners). This gives you a visual guide to draw perfectly accurate taxiways and ramps. Note: Do not distribute the orthophoto unless you have the license. It is for personal project guidance.

Exclusion Zones

X-Plane generates default autogen scenery (trees, buildings, forests) across the entire world. If you do not remove them, trees will grow through your taxiways. The Exclusion Zone Tool is your best friend.

Draw a large polygon covering your entire airport property. In the properties, check Exclude Objects, Exclude Forests, Exclude Buildings, and Exclude Network (roads). This tells the simulator to remove all default autogen within that boundary, leaving only your custom scenery.

Terrain Mesh Editing

The Elevation Tool allows you to sculpt the terrain. Use it to flatten the runway area, create gentle slopes for taxiways going over hills, or dig out areas for water features. Be conservative. Drastic elevation changes can cause visual anomalies like shear cliffs at the edge of your flattened area. For small adjustments (a few feet), it works perfectly. For large terrain changes (e.g., carving a runway out of a mountain), you should consider using a dedicated mesh tool like Ortho4XP.

Validation, Export, and In-Sim Testing

This is the most important but often forgotten phase. A project that validates cleanly is 90% likely to work perfectly in the sim.

Inside the Validator

Click the Validate button. The validator checks for a long list of standards:

  • Taxi Route Connectivity: Every route must link to another route or ramp.
  • Ramp Start Placement: Ramp starts must be on pavement.
  • Runway Alignment: Runways must be relatively flat and straight.
  • Object Errors: Missing objects or invalid library references.

Fix all Errors. Warnings (like "Pavement alignment slight offset") are often acceptable but should be reviewed. A clean validation is a requirement if you plan to submit to the Scenery Gateway.

Exporting and Testing

Go to File > Export Scenery Pack. WED will create a folder structure in your X-Plane Custom Scenery folder. The naming convention is critical: YOUR_SCENERY_NAME_Earth nav data_apt.dat.

Launch X-Plane, fly to your airport. Check the following:

  • Runway Alignment: Does the runway match the real-world orientation?
  • PAPI/VASI: Are the visual approach indicators correct?
  • AI Behavior: Do AI aircraft park at the correct gates? Do they follow the taxi routes?
  • Scenery Holes: Are any objects missing (shown as pink/magenta question marks)? This means a required library is not installed.

Common Pitfalls and Solutions

  • Missing Textures: Your texture path in the object properties is wrong. Use relative paths.
  • AI Spawning on Top of Each Other: Ramp start locations are too close together or the heading pushes the aircraft into the next parking spot.
  • Flickering Scenery: Two polygons (e.g., two different taxiway pieces) are overlapping. Use the Validate tool to find overlaps.

Sharing Your Work with the Community

Submitting to the X-Plane Scenery Gateway

The ultimate test of your scenery is getting it included in the default X-Plane experience. The X-Plane Scenery Gateway is the official repository. To submit, your airport must:

  • Validate without errors.
  • Use only default Laminar Research objects (no OpenSceneryX or custom objects).
  • Conform to real-world charts and satellite imagery.

Submissions are reviewed by Laminar moderators. If accepted, your airport will be pushed to all X-Plane users worldwide. This is a rewarding way to contribute to the sim.

Packaging for the Forums

If you use custom objects or community libraries, share your airport on the X-Plane.org Forum. Package your folder cleanly. Include a README.txt file that lists the exact versions of required libraries (e.g., OpenSceneryX 4.1.0, MisterX 1.2). Provide screenshots of your airport so users can see the quality before downloading.

Conclusion

Building a custom airport in World Editor is a marriage of technical precision and creative design. You are working with real-world data to create a functional, immersive space. It requires patience, especially when debugging taxi routes or aligning orthophotos. However, the payoff is significant. The first time you watch an AI airliner push back from a gate you designed, taxi along routes you drew, and take off from a runway you aligned, you will feel a genuine sense of accomplishment. Continue studying real charts, exploring the works of other designers, and iterating on your projects. Every airport you build makes the next one better.