Compare FS2004 ATC add-ons, including EditVoicepack, Radar Contact, PFE and VoxATC, with compatibility limits and the best choice for each pilot.
FS2004 has three practical types of ATC add-on: EditVoicepack to expand the built-in controller vocabulary, external replacements such as Radar Contact or ProFlight Emulator for different procedures, and legacy voice-recognition packages such as VoxATC. Compatibility, licensing and modern Windows support vary, so EditVoicepack is usually the simplest starting point.
FS2004 ATC add-ons compared
The key distinction is whether an add-on improves FS2004’s stock ATC or replaces it with a separate program.
| Add-on | What it changes | Best for | Main limitation |
|---|---|---|---|
| EditVoicepack 3.1 | Adds airline callsigns, aircraft types, airport names and customised phraseology to the stock voicepack. | Pilots who want better names and pronunciations while keeping default ATC. | It does not improve vectoring, runway selection or traffic separation logic. |
| Radar Contact 4 | Runs outside FS2004 and provides an alternative offline ATC system, particularly for IFR operations. | Pilots wanting a different procedural flow and more varied controller audio. | It is legacy software, uses FSUIPC and does not provide microphone-based voice input. |
| ProFlight Emulator | Generates external ATC around a prepared route using its own flight-processing workflow. | Pilots prepared to trade easier setup for more structured route handling. | Installation and flight preparation are more involved, and old dependencies can be troublesome. |
| VoxATC | Uses speech recognition for pilot transmissions and synthetic controller responses. | Pilots who specifically want to speak to offline ATC through a microphone. | Only FS2004-era editions are suitable; licence activation, speech components and Windows compatibility must be checked. |
For most FS9 installations, the FS2004-compatible EditVoicepack 3.1 package is the lowest-risk improvement. It retains the familiar ATC window and recorded voices while correcting many missing or poorly recognised names.
Radar Contact, ProFlight Emulator and VoxATC are complete or partial alternatives rather than simple voicepack updates. They are legacy products, so an old installer advertised for FSX or Prepar3D must not be assumed to support FS2004.
Which FS2004 ATC add-on should I choose?
Choose according to the part of FS2004 ATC that you actually want to change.
- Missing callsigns or incorrect pronunciations: use EditVoicepack.
- Offline IFR procedures: consider Radar Contact if you have a legitimate, complete installation and the required FS2004-compatible FSUIPC module.
- Detailed route preparation: ProFlight Emulator suits pilots comfortable with its more elaborate setup process.
- Microphone interaction: use only a VoxATC release explicitly made for FS2004, after confirming that its licence and speech-recognition components still function.
- Human controllers: an FS2004-compatible online-network client is a separate alternative, not an enhancement to the simulator’s built-in controller logic.
Do not install multiple replacement ATC programs together. They may compete for keyboard commands, suppress the stock ATC window or attempt to read the same flight-plan and FSUIPC data.
Will an ATC add-on improve AI traffic?
An ATC add-on does not automatically add aircraft, schedules or parking assignments to FS2004.
EditVoicepack helps controllers pronounce AI airline and aircraft names, but the underlying traffic remains unchanged. External ATC replacements vary: some account for nearby AI, some provide only background chatter, and others concentrate mainly on the user aircraft. Check this distinction before choosing one for a busy hub.
AI aircraft still depend on valid airport parking, taxi links, runway data and traffic plans. Excessive traffic can also overwhelm FS9’s separation logic, causing long holds, go-arounds and aircraft disappearing after extended delays.
How do I install an FS2004 ATC add-on safely?
The safest method is to preserve the original voicepack and test one ATC component at a time.
- Confirm the simulator edition. The installer or documentation must explicitly list FS2004 or FS9; an FSX edition is not interchangeable.
- Back up the affected files. Before using a voice editor, copy FS2004’s
Sound\ATCfolder to a safe location. Our FS2004 add-on installation guidance covers the broader backup and folder principles. - Check supporting modules. External ATC programs commonly communicate through FSUIPC. Use a build intended for FS2004 and check whether the add-on requires functions covered by a registered licence.
- Avoid protected-folder failures. If FS2004 is installed under a Windows system folder, the editor may lack permission to update the voicepack. Grant access only as required rather than repeatedly reinstalling the add-on.
- Test a simple flight. Start with default scenery, one aircraft and modest AI traffic. Confirm clearance, hand-offs, approach instructions and audio before restoring other utilities.
A mistake we see constantly is installing both EditVoicepack 3.0 and 3.1 as if they were separate content packs. Use one editor version, keep a backup, and apply only updates intended for the matching FS2004 voicepack language.
Can I create my own FS2004 callsigns and ATC phrases?
EditVoicepack can add or modify voicepack entries, but FS2004 still assembles speech from recorded tokens rather than generating unrestricted natural dialogue.
Advanced authors can use the official FS2004 SDK bundle and its ATC Voicepack kit to understand the supported voicepack structure. Keep an untouched copy of the original files: one malformed or mismatched update can remove voices, produce silent transmissions or stop the ATC audio system loading correctly.