Set up a microphone for VATSIM ATC: select the right audio devices, bind push-to-talk, test levels, and fix one-way audio, echo or distortion.
To set up a microphone for VATSIM ATC, connect a headset, select its microphone and headphones in your VATSIM pilot client, assign a push-to-talk button, then check the input meter before connecting. Use the headset mic close to your mouth, transmit only while holding push-to-talk, and release it to listen.
Across general flight-simulator setups, the microphone is configured in the VATSIM pilot client, not in the simulator’s built-in ATC options. If the network connection and client are not yet installed, start with our VATSIM equipment and pilot-client primer.
What microphone should I use for VATSIM?
A USB or analogue headset is usually the simplest choice because its microphone stays close to your mouth and its headphones prevent ATC audio feeding back into the transmission. An aviation-style headset is not required; speech clarity matters more than appearance.
- USB headset: normally the easiest option because the microphone and headphones appear as one clearly named audio device.
- 3.5 mm headset: works well, but a combined headset plug may need an adaptor when the computer has separate microphone and headphone sockets.
- Bluetooth headset: can work, although activating its microphone may switch it into a lower-quality hands-free audio mode. Battery, latency or device-switching problems make wired equipment more dependable.
- Desktop microphone: use headphones with it. Speakers can create echo, and a distant microphone will pick up keyboard, fan and room noise.
How do I configure my VATSIM microphone and push-to-talk?
- Connect the headset first. Plug it in before opening the pilot client so the device appears in its audio list. Check any physical mute switch or inline volume control.
- Test it in the operating system. Confirm that microphone access is permitted and make a short local recording. If that recording is silent, fix the operating-system or hardware problem before changing VATSIM settings.
- Select both audio devices in the pilot client. Choose the headset microphone as the input and its headphones as the output. Selecting the device by name is safer than using
Default, which can change when a monitor, VR headset or controller is connected. For simulator-specific controls, see our Microsoft Flight Simulator vPilot voice setup or X-Plane 12 audio and push-to-talk walkthrough. - Set the microphone position and level. Place the capsule about 2–3 cm from the corner of your mouth, slightly outside the direct breath stream. Speak at normal cockpit volume and adjust the input level so the meter responds strongly without repeatedly reaching its maximum or clipping.
- Assign push-to-talk. Use a momentary button on the yoke, joystick or throttle that is easy to hold without releasing the controls. Avoid a button already assigned to brakes, trim, views or another simulator command. VATSIM transmissions use hold-to-talk, not voice activation or a toggle.
- Check radio selection. Put the controller’s frequency in the active side of COM1 or COM2, not the standby window. Select the same radio for transmission and reception if the aircraft’s audio panel or pilot client models those controls.
- Test before making a live call. Use the client’s microphone test or input meter if provided; otherwise use a local recording. A busy ATC frequency should not be the first place you discover that the microphone is muted.
How do I speak to ATC on VATSIM?
Tune the correct active frequency, listen for a gap, hold push-to-talk, pause briefly and then speak clearly. Release the button immediately after the transmission so that you can hear the reply.
- Listen first. Make sure another pilot or controller is not already speaking.
- Press and hold push-to-talk. A short pause before the first word prevents the callsign being clipped.
- Give the controller and callsign first. Follow with the request or required report in one concise transmission.
- Release the button. Routine aviation radio calls do not need an added “over”.
If you need a readability check, wait until the frequency is quiet and transmit a concise call such as Ground, G-ABCD, radio check. Most pilot clients show a transmit indicator while push-to-talk is held and a receive indicator when another station is speaking.
Why can I hear VATSIM ATC but they cannot hear me?
One-way VATSIM audio usually means the wrong input device is selected, push-to-talk is not reaching the client, or the active radio and transmit radio do not match.
| Symptom | Likely cause | Fix |
|---|---|---|
| The input meter never moves | Wrong microphone, hardware mute or blocked microphone permission | Select the headset microphone explicitly, unmute it and allow the pilot client to access it. |
| The transmit indicator appears, but ATC hears silence or “carrier only” | Push-to-talk works, but the selected microphone supplies no audio | Repeat the local recording test and check the client’s input device and level. |
| ATC is audible, but push-to-talk does nothing | Missing binding, control conflict or the simulator intercepting the button | Bind a unique button in the pilot client and remove any conflicting simulator assignment. If it only fails while the simulator has focus, check that the applications use matching privilege levels. |
| The radio is tuned, but nobody responds | Frequency is in standby, the wrong COM radio is selected, or transmission is not enabled on the audio panel | Move the frequency to active and verify the client’s transmit indicator and COM selection. |
| ATC reports quiet or distorted speech | Incorrect gain or microphone position | Move the mic closer to the corner of the mouth. Raise a weak level gradually or reduce it if peaks are clipping. |
| ATC hears an echo | Radio audio is playing through speakers and returning through the microphone | Use headphones and disable any operating-system option that plays the microphone back through the output. |
| Voice becomes choppy or robotic | Unstable connection, Bluetooth profile switching or overloaded audio routing | Try a wired or USB headset, close unnecessary audio-routing software and stabilise the network connection. |
| Push-to-talk stays permanently active | Stuck button, toggle mapping or conflicting control software | Disconnect promptly to avoid blocking the frequency, then clear and reassign the binding as a momentary control. |
Can I use VATSIM if my microphone fails?
VATSIM pilot clients support text radio communication, so a failed microphone does not require an open-mic workaround. Tune the same frequency, use the client’s text window and tell the controller that you have a microphone failure or require text communication; select the appropriate communication capability wherever the client provides that option.