Fix FlyByWire ATC not working in Microsoft Flight Simulator by checking A32NX power, COM radios, flight-plan filing, audio and installation.
FlyByWire does not replace Microsoft Flight Simulator’s built-in ATC. If ATC stops working in the A32NX, the usual causes are an unpowered or incorrectly selected VHF radio, a route loaded only into the MCDU, muted ATC audio, AI radio assistance, or an outdated, duplicate or conflicting A32NX installation.
The A32NX uses Microsoft Flight Simulator’s ATC service through its simulated radios. Its MCDU and ATSU pages do not create a separate voice controller, and the cockpit push-to-talk switch does not make the simulator recognise spoken replies.
What should I check first in the FlyByWire A32NX?
- Test a default aircraft. Load the same airport in a stock aircraft and open the ATC interface. If that aircraft also has blank options, missing voices or a frozen session, the problem is with Microsoft Flight Simulator rather than FlyByWire.
- Power the aircraft properly. Connect external power or start the APU and confirm that the avionics and radio systems are powered. An illuminated EFB tablet is not proof that the aircraft’s radio buses are live.
- Select and tune VHF1. On the radio management panel, select VHF1, enter the required frequency and transfer it to the active side. On the audio control panel, make sure VHF1 reception is selected and its volume is audible.
- Use a valid facility. An uncontrolled airfield will not provide tower or ground services. Tune an available airport, centre or information frequency within range; our guide to using MSFS ATC frequencies, clearances and hand-offs explains the normal sequence.
- Disable AI radio assistance temporarily. The assistance option that handles radio communications can change frequencies or answer before you do. Turn it off while diagnosing the aircraft.
- Select replies from the ATC interface. Built-in ATC does not interpret your spoken words through the A32NX push-to-talk control. Choose the numbered or displayed response unless you have separately configured another compatible system.
What does each ATC symptom mean?
The symptom usually identifies whether the failure is in the aircraft, the flight plan, the audio system or the simulator itself.
| Symptom | Most likely cause | What to do |
|---|---|---|
| No ATC options in the A32NX only | Radio power, active COM selection or an add-on conflict | Power the aircraft, tune VHF1 and test with other Community add-ons removed. |
| ATC works, but no IFR clearance appears | The route exists only in the MCDU | File or load the route through the simulator’s own pre-flight planner. |
| Text appears but voices are silent | ATC voice, audio output or cockpit receive volume | Check the simulator’s ATC voice setting, selected sound device and A32NX audio panel. |
| Frequency changes unexpectedly | AI radio assistance is controlling COM1 | Disable the radio-assistance feature and retune the required frequency. |
| ATC fails in every aircraft | A stalled MSFS ATC session, voice service or simulator setting | Return to the main menu, start a fresh flight and troubleshoot ATC globally. |
Why does ATC ignore the A32NX flight plan?
Microsoft Flight Simulator ATC can only issue a useful IFR clearance for a route known to the simulator’s own flight-planning system. Importing or entering a route solely in the A32NX MCDU may give the aircraft valid navigation data while leaving built-in ATC with no filed IFR plan.
Create or load the route through the simulator’s pre-flight planner—the World Map or EFB workflow, depending on the MSFS version—before starting the flight. Then verify the route in the MCDU. Flight-plan synchronisation options can differ between aircraft builds, so do not assume that completing the MCDU INIT pages automatically files the route with ATC.
A mismatch can also produce nonsensical vectors or missing approach clearance. When diagnosing that problem, start a new flight rather than reloading an old save, because saved flights may restore the aircraft route and simulator ATC state differently.
Does the A32NX ATC COMM page control MSFS ATC?
No. The A32NX ATSU and ATC COMM pages model Airbus data-link functions; they are not a front end for Microsoft Flight Simulator’s toolbar ATC service.
Seeing an unavailable or inactive data-link function therefore does not prove that COM1 or built-in voice ATC is broken. Conversely, tuning a controller in the MSFS ATC interface does not activate every function shown on the MCDU’s ATC pages.
How do I repair a broken FlyByWire installation?
If ATC works in default aircraft but fails after the A32NX loads, remove duplicate aircraft packages and test a clean installation. The Community-folder procedure applies to PC; consoles do not expose that folder for manual package installation.
- Close Microsoft Flight Simulator. Do not replace aircraft files while the simulator is running.
- Remove old A32NX copies. Check every active Community folder, especially if MSFS has been moved or both simulator generations are installed. Do not merge a new package into an old folder.
- Check the package depth. The folder containing
manifest.jsonandlayout.jsonmust sit directly inside the active Community folder, not inside an extra nested directory. - Install the package for the correct simulator. Follow our A32NX installation checks for MSFS 2020 or the separate MSFS 2024 A32NX installation procedure. Do not reuse one simulator’s installation in the other.
- Isolate conflicts. Temporarily move other aircraft-system, avionics, toolbar and radio add-ons out of Community. Start a new flight with only the A32NX installed, then restore the other packages in small groups.
When is the fault with Microsoft Flight Simulator ATC?
The fault is simulator-wide if a default aircraft shows the same blank menu, silent voices or unresponsive controller at the same location. Restart the flight, verify online functionality and voice settings, and confirm that the correct audio device is selected.
If the session remains broken across aircraft, use our broader MSFS ATC troubleshooting sequence. Reinstalling the A32NX will not fix an ATC service or audio problem that also affects stock aircraft.