Learn which FS2004 ATC settings you can customise, how flight plans, weather and AI change behaviour, and what requires an add-on.
Yes, but only within limits. In Microsoft Flight Simulator 2004 (FS9), you can change ATC display and voice options, aircraft callsigns, flight-plan details, weather and AI traffic that influence ATC. You cannot directly edit the built-in controller logic, separation rules or vectoring through the simulator’s settings.
What ATC settings can FS2004 change?
FS2004’s ATC settings control presentation and voice playback, while most behavioural changes come from inputs elsewhere. In the ATC section of Settings, the standard options cover:
- Displaying ATC transmissions as text.
- Automatically opening the ATC window when a controller calls.
- Enabling or disabling the simulated pilot voice.
- ATC audibility, with the relevant volume controls found under the simulator’s sound settings.
These options do not change runway selection, phraseology logic, traffic separation or the instructions available in the numbered ATC menu. Default FS9 ATC is menu-driven and does not interpret free-form spoken requests.
How do flight plans, weather and AI traffic affect ATC?
Flight-plan type, filed altitude, weather and traffic are the main inputs that change what FS2004 ATC tells you to do. Configure them before requesting clearance or taxi:
- Set the aircraft identity. Use the aircraft Details screen where available to enter the registration, airline callsign and flight number.
- Create the appropriate flight plan. An IFR plan produces structured clearances, altitude assignments, hand-offs and approach instructions. VFR operations receive a more limited set of services.
- File the intended cruising altitude. Changing the autopilot altitude alone does not amend an IFR clearance; ATC works from the filed plan and subsequent instructions.
- Load the weather first. Wind direction influences the active runway. Changing the wind after traffic has started may leave aircraft using the previous flow until FS9 reorganises them.
- Choose a practical AI traffic level. More AI creates longer departure queues, delayed landing clearances and more go-arounds.
Our guidance on balancing AI traffic and other FS9 realism settings explains how these inputs work together without pretending the default controller is more capable than it is.
Can I change ATC callsigns and phraseology?
You can alter the identity and vocabulary ATC speaks, but not its decision-making code. For an installed aircraft, back up aircraft.cfg and edit the correct [fltsim.x] variation if its Details screen does not provide the values you need:
atc_idsets the registration or tail number.atc_airlinerequests a spoken airline callsign.atc_flight_numbersupplies the number spoken after that callsign.
A mistake we see constantly is entering an airline’s display name rather than a callsign token that exists in the FS9 voice database. When the token is unrecognised, ATC may fall back to the registration, omit part of the identity or fail to pronounce it as expected.
The EditVoicepack package for expanding FS2004’s ATC vocabulary can add airline callsigns, airport names and aircraft types, adjust phraseology entries and accelerate voice playback. It still does not rewrite vectoring, runway assignment, separation or approach logic.
Can I force runways or change ATC vectoring?
FS2004 has no standard setting that forces a runway, rewrites vectors or changes separation rules. The built-in controller makes those decisions from weather, the airport facility data, your flight plan and the traffic situation.
- Wrong runway: check the wind first, then inspect the add-on airport’s facility data. Duplicate AFCAD-style files can give FS9 conflicting runway, parking or frequency information.
- Landing clearance withheld: an occupied runway or queued AI aircraft is usually responsible. Use our diagnosis of refused and delayed landing clearances for the specific fixes.
- Poor or unexpected vectors: simplify the IFR route and remember that FS9 ATC does not understand published procedure constraints like a modern controller. If you cancel IFR to fly a procedure yourself, you also surrender the simulator’s IFR sequencing and clearances.
- Edited callsign ignored: confirm that you changed the active
[fltsim.x]entry, save the file and reselect the aircraft so FS9 reloads its configuration. - ATC menu choice missing: options are context-sensitive. Tune the correct frequency, complete the previous instruction and verify that you are at the appropriate flight stage.
| What you need | Best choice | Main limitation |
|---|---|---|
| Routine solo IFR or VFR control | Built-in FS2004 ATC | Fixed, menu-driven logic |
| More callsigns, names and quicker speech | EditVoicepack | Changes vocabulary, not decisions |
| Human tower or ARTCC-style control | A radar interface intended for multiplayer controlling | Separate multiplayer workflow rather than smarter automated ATC |
Treat FS2004 ATC settings as presentation controls and operational inputs, not as a rules editor. Callsigns, plans, weather and traffic can substantially change the experience, but replacing the controller’s underlying behaviour requires a separate ATC system or human multiplayer control.