Learn how flight simulator gate and parking assignments use stand size, type, airline codes and taxi links, with fixes for wrong or empty gates.
Airport gates and parking assignments in flight simulators are controlled by airport data: each stand has a location, size, type, identifier and taxiway connection, often with airline or aircraft-use codes. The simulator matches an aircraft to a compatible free stand; missing, conflicting or inaccurate data causes incorrect parking.
In MSFS 2020 and 2024, FSX, Prepar3D and X-Plane, the visible terminal model does not assign parking. The functional airport record beneath it does. A beautifully modelled gate can therefore be unusable if its parking point or taxi link is missing.
What determines which gate an aircraft uses?
A stand must satisfy the simulator's compatibility rules before it can be assigned. The precise priority varies between simulators and traffic systems, but these are the main factors:
| Airport data | What it controls | Common symptom when wrong |
|---|---|---|
| Stand size or radius | The aircraft dimensions or equipment class that will fit | Large aircraft avoid an empty gate or overlap nearby objects |
| Parking type | Gate, general aviation ramp, cargo, military or other use | Airliners park remotely or cargo aircraft appear at passenger gates |
| Airline or operator codes | Preferred stands for matching traffic | An airline uses the wrong terminal or ignores a coded gate |
| Taxiway connection | Whether AI can enter and leave the stand | The stand appears in scenery but is never used |
| Position and heading | Where and in which direction the aircraft spawns | The aircraft faces the terminal, clips a building or misses the markings |
| Availability | Whether another recognised aircraft occupies or reserves the stand | Traffic is sent to an overflow position |
The displayed gate number is mainly a label for the user and ATC. It does not by itself reserve that stand for an airline. Parking codes are also often preferences rather than absolute locks, so an engine may use an uncoded or mismatched stand when no better option exists.
Do player, AI and live aircraft use the same rules?
Player, AI, live and multiplayer aircraft can use different assignment paths even at the same airport.
- Player aircraft: selecting a gate from the departure list normally places the aircraft at that stand's coordinates and heading. Some simulators permit a selection even when the aircraft is too large, resulting in clipping.
- AI aircraft: the traffic engine selects a compatible stand when spawning or after arrival. Its flight plan, aircraft data and the airport's parking records all matter; our explanation of how simulator AI traffic is generated and managed covers the wider traffic process.
- Live traffic: a live feed does not guarantee the real aircraft's real gate. Many feeds or injectors supply the callsign, route and aircraft type but either lack stand data or apply their own parking logic.
- Multiplayer and static aircraft: these may not participate in the same reservation system. A static scenery model can visually occupy a gate without marking it unavailable, while a remote player may appear on top of local traffic.
How do MSFS, FSX, Prepar3D and X-Plane differ?
The underlying principle is shared, but each simulator stores and describes airport parking differently.
| Simulator | Functional airport data | Important assignment details |
|---|---|---|
| MSFS 2020 and 2024 | Compiled airport parking spots, taxi links and service definitions | Stand category, size, connectivity and traffic source affect assignment; ground-service support is separate |
| FSX and Prepar3D | Airport facilities BGL, commonly called an AFCAD file | Parking radius, type, airline codes and aircraft configuration entries have a strong influence |
| X-Plane | Ramp starts and taxi routes in the airport data | Ramp type, operation type, equipment classes, airline restrictions and route connectivity are used |
In FSX and Prepar3D, aircraft can declare preferences through atc_parking_types and atc_parking_codes in aircraft.cfg. The airport's parking records need compatible types, codes and sufficient radius. This Haneda airport-data example showing gate sizes, ramp categories and airline codes illustrates how those properties shape terminal assignments.
Why does an aircraft use the wrong gate or no gate?
Wrong or missing parking usually comes from incompatible stand data, a broken taxi graph, insufficient capacity or a different airport version being loaded.
- Confirm which airport scenery is active. Duplicate default, freeware and payware airport definitions can supply conflicting parking spots. Temporarily disable the add-on version and compare the result.
- Check the stand size against the aircraft. A gate can look large enough while its configured radius or equipment class is too small. Incorrect dimensions in the aircraft model's configuration can cause the same rejection.
- Compare the parking type and codes. Passenger, cargo and general aviation categories must make sense on both sides. Over-coding every gate can leave ordinary or incorrectly coded traffic with nowhere suitable to park.
- Inspect taxi connectivity. The parking point must connect to a valid taxi network. A decorative apron line or painted lead-in line is not necessarily a functional AI route.
- Check actual capacity. Reduce traffic temporarily and test again. Static aircraft may block gates visually, while closely spaced parking points can become unavailable when a large aircraft occupies an adjacent stand.
- Test without the traffic injector. Built-in AI, live traffic and third-party traffic can interpret the same airport differently. Testing one source at a time identifies whether the fault belongs to the airport or the traffic system.
Older FSX and Prepar3D traffic may disappear after landing when no valid parking position can be found. In other cases, the aircraft chooses a remote ramp, waits on a taxiway or occupies an apparently unsuitable fallback stand.
Can I reserve a gate for one airline or aircraft?
You can strongly influence a parking assignment with matching codes and types, but most simulators do not treat them as an unbreakable reservation.
- Edit an add-on airport definition rather than the stock file. Keep the original airport intact so the change can be removed or replaced safely.
- Assign a suitable stand type, size and operator code. Use the code format expected by that simulator and traffic package.
- Add the matching value to the aircraft or traffic definition. In FSX and Prepar3D, this normally involves the parking fields in
aircraft.cfg. - Provide fallback capacity. Other suitable stands are still needed when the preferred one is occupied.
- Build or save the airport in the simulator's required format. Ensure the edited version has the correct scenery priority, then test with low traffic before restoring normal density.
A worked FSX method for linking reserved VIP parking to an aircraft demonstrates the matching-code approach. It reduces unwanted assignments, but manual player starts and some traffic injectors can still bypass the preference.
Do gates control jetways and ground services?
Gate assignment and ground services are related but separate systems. A correctly parked aircraft still needs a usable jetway or service configuration, a compatible stand type and properly defined aircraft doors or service points.
Passenger gates are more likely to support jetways, baggage and catering, while ramp positions generally use stairs and vehicles. The practical distinction is covered in our MSFS 2024 guide to gates, ramp stands and ground services. A gate that accepts AI traffic will not automatically provide every service, and a service-capable gate can remain unused if its parking or taxi data is invalid.