Fix FS2004 ATC not responding to an Airbus: check COM1/VHF1, electrical power, radio synchronisation, panel files, audio and FSUIPC.
FS2004 ATC usually ignores an add-on Airbus because the aircraft has not powered its avionics, the required frequency is not active on COM1/VHF1, or a custom radio gauge is not passing its setting to FS9. Power VHF1, activate the simulator-listed frequency, then test the same contact in a default aircraft.
FS2004, also known as FS9, shipped without a default Airbus. Every Airbus package therefore brings its own panel, gauges and system logic, making an aircraft-specific fault more likely than a failure of the simulator’s ATC engine.
How to restore FS2004 ATC communication
The quickest fix is to identify whether the failure lies with ATC, the Airbus radio panel or sound playback, then change one item at a time.
- Check for a written ATC reply. Make a call using the numbered choices in the ATC window and watch the transcript. If a controller reply appears as text, the radio exchange worked and only the speech is missing; use our checks for missing FS2004 ATC voices and radio audio.
- Repeat the contact in a default aircraft. Load a default Cessna in a ready-to-fly state at the same airport and position, then call the same facility through the ATC window. If that also fails, the fault is simulator-wide rather than Airbus-specific; follow our FS2004-wide ATC diagnostic process.
- Start a fresh Airbus flight. An old saved flight can preserve an unpowered bus, inactive radio or faulty gauge state. Load the Airbus using the package’s documented ready state before diagnosing a cold-and-dark start.
- Power the avionics properly. In a systems-modelled Airbus, the battery alone may not energise every simulated avionics bus. Connect external power or start the APU or engines, place the appropriate generator online and confirm that the radio-management panel responds. Simpler panels may depend on FS9’s underlying master-battery and avionics-master controls.
- Tune active COM1/VHF1. Put the facility frequency in the active field, not standby, and do not leave it on COM2/VHF2. Use the frequency shown by FS9’s own ATC facility list: real-world assignments have changed since the simulator’s data was produced, and replacement scenery can contain different frequencies. Our guide to setting and swapping active FS2004 radio frequencies covers the exact distinction.
- Select VHF1 for transmission. If the Airbus models an audio-control or radio-management panel, select VHF1 or COM1 as the transmitting radio. Turning up a receive volume or selecting VHF2 does not place FS9’s stock ATC call on COM1.
- Use an available ATC menu call. Stock FS2004 ATC responds to the numbered menu choices, not ordinary microphone speech. If the expected call is absent from the window, confirm that the facility exists, you are within range and the airport is controlled.
- Repair the complete panel installation. Reinstall the aircraft or required base package according to its documentation. Missing gauges or modules can leave convincing radio digits on screen without changing FS9’s actual COM1 value. Ensure the panel was made for FS2004, that its files went into the active FS9 installation, and that you did not install only a model or texture expansion.
Why does ATC work in default aircraft but not the Airbus?
If a default aircraft can contact the same controller, FS2004 ATC is working and the Airbus is failing to power, tune or synchronise the simulator’s internal COM1 radio.
| Symptom | Likely cause | Next action |
|---|---|---|
| ATC fails only after a cold-and-dark start | The required electrical or avionics bus is offline | Complete the add-on’s electrical start procedure and verify VHF1 power |
| The displayed frequency is correct but no contact is available | The custom gauge is not writing its value to FS9 COM1 | Repair the panel and check its documented dependencies |
| Moving the frequency from VHF2 to VHF1 restores contact | The ATC frequency was on the wrong radio | Keep the FS9 ATC frequency active on COM1/VHF1 |
| A new flight works but a saved flight does not | The saved panel or electrical state is faulty | Rebuild the flight from a fresh Airbus session |
| Every aircraft fails at the same airport | The problem is global, scenery-related or caused by the selected facility | Test another controlled airport and inspect FS9’s general ATC settings |
| Controller text appears without speech | Communication works, but ATC audio does not | Check voice playback, the sound device and radio volume |
What if the Airbus radio shows the correct frequency?
A correct-looking radio display does not prove that FS2004’s internal COM1 frequency has changed. Advanced panels can draw their own digits and simulate radio-management logic separately from the stock radio variables used by ATC.
If the package includes a default-style radio stack or another panel that directly controls FS9 radios, set active COM1 there as a diagnostic test. If ATC then works, the custom Airbus radio gauge or one of its dependencies is not synchronising correctly.
Check the package documentation for required gauge and module files, panel aliases and a separate base aircraft. On modern Windows installations, an old installer can also target the wrong FS2004 folder or fail to place files under a protected Program Files location. Verify the files rather than assuming that a successful installer message means the active FS9 installation was updated.
A fresh default-aircraft test is safer than changing aircraft solely to carry a tuned frequency into the Airbus. Complex panels can initialise incorrectly when an aircraft is swapped during a running flight.
Can FSUIPC fix Airbus ATC communication?
FSUIPC can help only when the Airbus documentation names it as a dependency for its gauges, radio logic or electrical variables. FS2004’s standard ATC does not require FSUIPC, so installing it will not repair a global ATC or sound problem.
Use an FS2004-compatible FSUIPC 3 module rather than a release intended for a newer simulator. Our instructions for installing and checking FSUIPC 3 in FS2004 explain where it belongs and how to confirm that FS9 has loaded it.
Does FS2004 ATC require a flight plan?
Local VFR calls to ground, tower and other available facilities do not require a flight plan, but an IFR clearance requires an IFR plan to be loaded in FS2004.
The available calls also depend on aircraft position, radio range and the services defined for that airport. An uncontrolled airfield has no tower controller to answer, while a modern real-world frequency may not exist in FS9’s older facility data. If the contact option never appears in the ATC window, investigate the airport, range and frequency before blaming the Airbus panel.