Learn why FS2004 ATC sends you to the wrong gate or terminal, then fix parking codes, stand sizes, AFCAD data and duplicate airport files.
FS2004 ATC assigns gates from the airport’s active AFCAD parking data, matching stand type, size and airline codes against the aircraft’s configuration. It does not understand real-world terminal use or a repaint’s visual livery. Missing, mismatched, occupied or disconnected stands therefore send you to a fallback gate or ramp.
How does FS2004 choose a gate?
When you request taxi to parking after landing, FS2004 searches the airport facility data for a compatible, available parking position. Each position can have a name and number, parking type, physical radius, airline codes and a connection to the taxi network.
The aircraft supplies its parking information through the selected repaint’s [fltsim.x] section in aircraft.cfg. Typical entries are:
atc_parking_types=GATEfor a passenger airliner.atc_parking_types=CARGOfor a freighter.atc_parking_types=RAMPfor general aviation or aircraft intended to use ramp parking.atc_parking_codes=BAWas an example of an airline code matching coded stands in the airport file.
The code must match what the airport designer entered, normally an ICAO-style airline code. The separate atc_airline entry controls the name spoken over the radio; it does not choose the terminal. See our explanation of how FS2004’s spoken callsign fields work if the radio identity is also incorrect.
What usually causes the wrong terminal?
| Symptom | Likely cause | What to correct |
|---|---|---|
| One repaint parks incorrectly at many airports | Missing or wrong aircraft parking code or type | Edit the relevant [fltsim.x] section rather than another repaint’s block. |
| Every airline uses the wrong terminal at one airport | Old, inaccurate or conflicting AFCAD data | Use an airport facility file that matches the installed visual scenery. |
| A heavy aircraft receives a remote stand | No available coded gate is large enough | Increase the intended stand radius where realistic or provide suitable overflow positions. |
| The problem appears only with busy AI traffic | Matching gates are occupied | Add suitable capacity or test with less AI traffic to confirm the cause. |
| ATC’s gate number disagrees with terminal signs | AFCAD parking labels do not match the scenery model | Correct the parking position names and numbers in the airport data. |
| A passenger aircraft is sent to a ramp | RAMP is listed as an accepted parking type, or no suitable gate remains | Use only appropriate types and check gate availability. |
FS2004 does not read terminal lettering, airline logos painted on scenery or real-world gate allocation schedules. If the terminal model says Gate 24 while the underlying parking position is labelled Gate 12, ATC follows the parking data.
How do I fix an incorrect FS2004 gate assignment?
- Identify the scope. Test the same aircraft at another airport and a different aircraft at the affected airport. This separates an aircraft configuration problem from an airport AFCAD problem.
- Back up the files. Save copies of
aircraft.cfgand any third-party airport facility file before editing. - Correct the selected repaint. Add or revise
atc_parking_typesandatc_parking_codesinside the exact[fltsim.x]block used by that livery. Do not addRAMPmerely to obtain more parking unless remote stands are acceptable. - Inspect the airport. You can inspect and edit FS2004 parking spots with AFCAD 2.21. Check the intended terminal’s airline codes, parking types, radii, gate labels and taxiway connections.
- Remove conflicting add-on definitions. Two third-party AFCAD files for the same airport can produce displaced parking or unexpected assignments. Keep the file designed for your installed scenery at the appropriate scenery-library priority. Do not delete FS2004’s stock airport files; the usual problem is duplicate add-on data.
- Reload and retest. Restart FS2004 after changing compiled airport data, then test first with light AI traffic so matching gates are not already occupied.
If the fault affects several default airports, a corrected AFCAD pack covering many FS2004 airports may be quicker than editing each one. Do not layer a generic AFCAD over detailed add-on scenery unless their layouts match, because the aircraft may then park inside buildings or follow displaced taxi routes.
Why can the correct airline code still send me elsewhere?
An airline code improves matching but does not reserve a stand absolutely. FS2004 must also find a position of the right type and sufficient size that is unoccupied and usable by the taxi network; otherwise it selects another compatible position.
A common mistake is coding only two or three real-world gates for an airline that generates much more AI traffic. Once those gates fill, later arrivals need fallback parking. Code enough realistic stands in the correct terminal and include appropriately sized overflow positions there.
Also check the aircraft’s parking type. A correctly coded freighter with GATE rather than CARGO can still be directed to the passenger terminal. Setting atc_heavy=1 will not repair this: that entry affects ATC phraseology, not the parking stand’s size or terminal assignment.
Can I force ATC to use one exact gate?
FS2004 has no dependable aircraft.cfg setting for a specific arrival gate number. ATC chooses dynamically from the compatible positions available when the aircraft lands.
For a departing flight, select the required parking position as the airport starting location. For arrivals, the practical solution is to code all suitable stands in the intended terminal correctly, remove that airline code from inappropriate areas and provide enough capacity to prevent fallback assignments.