How do you use VATSIM with Microsoft Flight Simulator?

To use VATSIM with Microsoft Flight Simulator, fly on PC, create and activate a VATSIM account, install the approved vPilot client, prepare a valid route and callsign, then connect only when your aircraft is parked. File a flight plan, tune the assigned frequency and follow live controller instructions.

VATSIM is not part of the simulator's built-in ATC system. vPilot runs alongside Microsoft Flight Simulator 2020 or 2024 and uses SimConnect to exchange your aircraft's position, radio state and nearby network traffic.

Can you use VATSIM on PC, Xbox and PlayStation?

VATSIM works with the PC editions of Microsoft Flight Simulator 2020 and 2024, but there is no supported VATSIM connection for the console editions.

How do you set up VATSIM in Microsoft Flight Simulator?

The reliable setup order is account, client, audio, simulator traffic, route and then connection.

1. Create your VATSIM account. Complete the required new-member orientation and entry test, then retain your VATSIM ID and password. Your numerical account ID is not your flight callsign.
2. Install vPilot. Obtain it from the network's approved pilot-client area and install it as a separate Windows application. It does not belong in the MSFS Community folder.
3. Configure voice and push-to-talk. Select the exact microphone and headset or speaker device inside vPilot. Assign a dedicated push-to-talk button there; assigning one only in MSFS will not transmit on VATSIM.
4. Remove conflicting simulator traffic. Disable multiplayer aircraft and MSFS AI or live aircraft traffic, but leave Live Weather available. Reduce static ground aircraft if occupied stands are a problem. Turn off AI radio assistance and built-in ATC audio so they do not retune radios or speak over human controllers.
5. Prepare the flight. Choose a callsign, aircraft type, departure, destination, route and cruising altitude. Our guide to building and checking a route in the MSFS flight planner covers departures, arrivals and altitude selection.
6. Load at a parking stand. Start at a gate, ramp or other non-movement area with the parking brake set. Never spawn on a runway and then connect. If another network aircraft occupies your stand, disconnect before moving to a free one.
7. File and connect. File through vPilot's flight-plan function or the network's prefile tool. Use exactly the same callsign in the flight plan and vPilot, then connect while stationary.
8. Check coverage and call ATC. Read the controller information, obtain the ATIS where available, tune the correct frequency on an active COM radio and listen before transmitting.

Use a three-letter ICAO airline designator plus flight number for an airline callsign, or an aircraft registration without spaces or punctuation. A mismatch between the connected callsign and filed plan is a common reason controllers cannot find the expected flight plan.

Do you need model-matching add-ons?

Model matching is optional and affects how other pilots' aircraft look, not your ability to connect or speak to ATC. Set up the network and radios first; add matching rules and aircraft models only after the basic connection works.

What flight plan should you file on VATSIM?

An IFR flight plan should contain a route your aircraft can actually fly, with the correct aircraft type, departure, destination and requested altitude.

Controllers may amend the route or assign a different runway and procedure. Be ready to edit the flight plan, use direct-to navigation and fly a heading. If your avionics do not contain an assigned SID, STAR or approach, say unable rather than pretending to accept it.

VATSIM controllers generally work with the active real-world navigation cycle, while stock simulator data or an add-on aircraft database may differ. If procedure names, fixes or runways do not agree, check our advice on updating and synchronising MSFS navdata.

VFR flying is supported too. Local flight-plan and advisory-frequency practices vary by region, so read the controller information and applicable local instructions rather than assuming every airport uses the same procedure.

Do you need to know ATC phraseology first?

You need enough standard phraseology to identify yourself, state your position and request, understand a clearance, and read back safety-critical instructions.

A first clearance call can be short: controller's station, your callsign, stand or location, aircraft type if useful, destination, ATIS code and request. Listen to other pilots before calling, but do not copy a clearance meant for someone else.

• Read back runway assignments, hold-short instructions, headings, altitudes, squawk codes and clearances.
• Use the cockpit radio to tune the frequency and confirm it is active rather than left in standby.
• On hand-off, acknowledge the instruction, change frequency and check in with the next controller.
• If you miss something, say say again. If you cannot comply, say unable and briefly explain why.
• Where no controller covers you, monitor the locally specified advisory frequency and make concise traffic calls. 122.800 is common, but some regions use a published airfield CTAF instead.

For the underlying radio concepts, our explanation of frequencies, clearances and ATC hand-offs in Microsoft Flight Simulator provides a useful foundation. The main difference is that VATSIM controllers are real people, so instructions may change with traffic and workload.

Should you use Live Weather on VATSIM?

Use Live Weather or manually match the reported conditions so your wind, pressure and runway expectations agree with the controller's information.

Small differences between MSFS weather and the controller's data can occur. Set the altimeter value you are given and use the assigned runway even if the simulator initially proposed another one. Weather selection does not replace listening to the ATIS.

What makes a good first VATSIM flight?

Choose a familiar aircraft, a quiet airport and a simple route rather than joining a major event for your first connection.

• Know how to taxi, hold position and stop without assistance.
• Be able to maintain an assigned heading, altitude and speed manually.
• Have the airport and procedure charts ready before connecting.
• Avoid an airliner whose flight-management system you are still learning.
• Use observer mode first if you want to hear network radio traffic without appearing as an active aircraft.

VATSIM does not require perfect phraseology, but it does require control of the aircraft. If you must leave the computer, lose control or need to reposition with slew, disconnect first.

Why is VATSIM not working in MSFS?

Most first-time failures come from the wrong audio device, an inactive radio, conflicting simulator traffic or a mismatch between the callsign and flight plan.

• No transmission: verify the vPilot push-to-talk assignment, microphone permission and selected input device. Confirm vPilot shows the simulator and network as connected.
• No controller audio: check the output device, powered avionics, active COM radio, tuned frequency and radio volume. A listed controller may also be outside radio range.
• Duplicate aircraft: disable MSFS multiplayer and AI or live aircraft traffic. VATSIM traffic should be injected by vPilot alone.
• Other pilots are invisible: inspect vPilot for model-matching errors. Missing or unsuitable models affect traffic display but not radio communication.
• Wrong route or procedure: compare the filed route with the aircraft's navigation database and tell ATC immediately if a fix or procedure is unavailable.
• Radio fails after a hand-off: confirm the new frequency was transferred from standby to active and that the intended COM radio is selected for transmission.