Fix wrong FS2004 ATC gate or terminal assignments by checking aircraft.cfg parking codes, stand size, occupancy and conflicting AFCAD files.
FS2004 (FS9) ATC assigns parking from the active airport facility (AFCAD) data, not from real-world terminal rules or the aircraft’s painted livery. It matches parking type, stand radius, airline codes, availability and taxiway access. If any of those do not fit, ATC sends the aircraft to another gate or ramp.
What supplies FS2004 ATC with gate information?
The active AFCAD supplies ATC with the airport’s logical parking positions, while aircraft.cfg supplies the parking preferences for the selected aircraft variation. “AFCAD” is commonly used as shorthand for the airport facility data even when another editor created the file.
Each airport parking position can contain:
- A parking type, such as gate, cargo or ramp.
- A radius determining which aircraft can fit.
- One or more airline parking codes.
- A parking name and number used by ATC.
- A parking link connecting the stand to the taxiway network.
FS2004 has no separate field that says “Terminal 1” or “Terminal B”. A terminal assignment is produced indirectly by placing and coding individual stands around that terminal. ATC supplies the assignment and taxi instruction; it does not create or understand the terminal layout itself.
The aircraft preferences normally appear in the selected repaint’s [fltsim.x] section:
atc_parking_types=GATEfor a passenger airliner.atc_parking_types=CARGOfor a freighter.atc_parking_types=RAMPfor an aircraft intended to use ramp parking.atc_parking_codes=BAWto prefer stands carrying the matching airline code.
The code is usually the airline’s three-letter ICAO designator, but it must match whatever the airport designer entered. Do not substitute a two-letter IATA code unless the airport file also uses it. The atc_airline and atc_flight_number entries control radio phraseology, not terminal selection, while atc_heavy=1 does not make a parking stand larger.
Our explanation of how FS2004 evaluates parking types, size, airline codes and taxi links covers the wider selection logic.
Why can the correct airline code still lead to the wrong terminal?
A matching airline code only gives FS2004 a preference; it does not reserve that gate or make the stand airline-exclusive. The position must also be large enough, of a compatible type, connected to the taxi network and unoccupied when ATC makes the assignment.
A correctly coded gate may be unavailable because AI traffic is already using it. This is especially common when an airport has only two or three coded stands for an airline but the traffic schedule generates many arrivals. Once those stands fill, later aircraft are sent to compatible fallback parking.
Uncoded stands can also be used as general parking. If no suitable coded position remains, FS2004 may choose one of these rather than leave the aircraft without a route. For AI traffic, the aircraft variation’s atc_parking_codes entry matters; the paint scheme and apparent airline identity do not.
What usually causes the wrong gate or terminal?
The pattern of the fault usually reveals whether the problem is in the aircraft configuration or the airport data.
| Symptom | Likely cause | What to check |
|---|---|---|
| One repaint parks incorrectly at several airports | Missing or incorrect parking entries in that repaint’s [fltsim.x] block | Check atc_parking_types and atc_parking_codes in the exact variation being flown. |
| Several airlines use the wrong terminal at one airport | Inaccurate, outdated or mismatched airport facility data | Confirm that the active AFCAD was made for the installed visual scenery. |
| The fault appears only with busy AI traffic | Suitable coded gates are occupied | Retest with low AI traffic and provide realistic overflow capacity if necessary. |
| A large aircraft receives a remote stand | No available coded gate has a sufficient radius | Check stand radii and aircraft size rather than relying on the atc_heavy setting. |
| ATC’s gate number disagrees with terminal signs | The logical parking label does not match the scenery model | Correct the stand name and number in the airport facility data. |
| A passenger aircraft is sent to cargo or ramp parking | Wrong aircraft parking type or no compatible gate remains | Use GATE for the repaint and check whether suitable gates are occupied or missing. |
| Aircraft park inside buildings or follow displaced taxi routes | Duplicate airport definitions or an AFCAD for a different scenery layout | Keep one add-on facility definition that matches the visible airport. |
Static aircraft and terminal graphics are only visual objects. They do not supply ATC with parking rules, and a stand shown in the scenery may have no logical parking record underneath it. Our guide to diagnosing missing parking records and conflicting airport files explains this scenery-versus-AFCAD problem.
How do I fix an incorrect FS2004 gate assignment?
Separate aircraft-wide faults from airport-specific faults before changing files; otherwise it is easy to repair the wrong component.
- Test the scope. Fly the same repaint into another airport, then test another aircraft at the affected airport. If only one repaint fails everywhere, start with
aircraft.cfg. If several aircraft fail at one airport, inspect that airport’s facility data. - Back up the configuration. Save copies of
aircraft.cfgand any third-party airport BGL before editing. Do not overwrite or delete FS2004’s stock airport files. - Edit the selected repaint. Find the exact
[fltsim.x]block used by that livery. Add or correct oneatc_parking_typesentry and oneatc_parking_codesentry; do not leave duplicate keys in the same block. Use the most accurate parking type rather than addingRAMPsimply to increase the number of available positions. - Run an availability test. Reduce AI traffic, reload the flight and request taxi to parking again. A correct assignment with light traffic indicates insufficient capacity or occupied coded stands rather than a bad airline code.
- Check for duplicate airport definitions. Temporarily disable suspected add-on scenery areas or facility BGLs one at a time. Keep the airport definition intended for the visible scenery; changing library priority alone cannot make two different terminal layouts compatible.
- Inspect the parking records. With an FS2004-compatible airport facility editor, verify the intended stands’ parking types, airline codes, radii, names, numbers and connections to the taxiway network. Do not inflate every radius indiscriminately, because overlapping or unrealistic stands create further AI parking problems.
- Reload and retest. Restart FS2004 after replacing compiled airport data. Test first with light AI traffic, then restore the normal traffic level to confirm that the terminal has enough suitable capacity.
Can I force FS2004 ATC to use one exact gate?
No. FS2004 has no dependable aircraft.cfg field that forces ATC to assign a particular arrival gate number. Airline codes can narrow the preferred positions, but availability, size, type and taxi connectivity still determine the final choice.
For departure, select the required parking position as the flight’s starting location; these steps for starting at a specific FS2004 gate or stand also explain why a position may be absent from the list. For arrivals, code enough correctly sized stands in the intended terminal and remove inappropriate airline codes elsewhere, while retaining realistic overflow parking for busy periods.