Skip to content
X-Plane 6 min read

How do I install and configure xPilot for X-Plane 11?

Adam McEnroe
In short

Install and configure xPilot for X-Plane 11: place the plugin correctly, set VATSIM audio and push-to-talk, add CSL models, and fix connection errors.

Install xPilot with X-Plane 11 closed, select the X-Plane 11 root folder when prompted, and confirm the plugin lands in Resources/plugins/xPilot. Then start X-Plane and xPilot, enter your VATSIM credentials, choose audio devices, bind push-to-talk, add CSL models, load at a stand, and connect with a valid callsign.

xPilot has two parts: a standalone client handling the VATSIM connection and audio, plus an X-Plane plugin handling simulator data and network traffic. Both components must be present and able to communicate.

What do I need before installing xPilot?

Use a current official xPilot package that explicitly supports X-Plane 11 and your operating system. Avoid old mirrored installers because outdated client or plugin components are a common cause of connection failures.

  • A working VATSIM account and its current sign-in credentials
  • An updated, supported installation of 64-bit X-Plane 11
  • A microphone and preferably a headset, which prevents controller audio feeding back into the microphone
  • Your X-Plane 11 root folder, containing the simulator executable and Resources folder
  • Optional CSL model packages for displaying other pilots' aircraft correctly

If you have several simulator copies, use our guide to identifying the correct X-Plane 11 installation folder before running the installer.

How to install xPilot in X-Plane 11

  1. Close X-Plane and any older pilot client. Plugin files should not be added or replaced while the simulator is running.
  2. Run the official xPilot installer. The standalone client can remain in its suggested application location; it does not belong inside the X-Plane plugin folder.
  3. Select the X-Plane 11 root folder. Choose the folder containing the X-Plane executable, not the desktop shortcut and not another X-Plane installation. If the installer explicitly asks for a plugin folder instead, select X-Plane 11/Resources/plugins.
  4. Enable the X-Plane plugin component. After installation, the expected path is X-Plane 11/Resources/plugins/xPilot.
  5. Start X-Plane 11 and load an aircraft. Open X-Plane's Plugin Admin screen and confirm that xPilot is listed and enabled.
  6. Launch the standalone xPilot client. Its status should change from waiting for the simulator once the plugin establishes communication.

Where should the xPilot plugin be installed?

The xPilot folder must sit directly inside Resources/plugins. A structure such as Resources/plugins/xPilot/xPilot is double-nested and will usually prevent X-Plane from loading it.

Do not place the entire desktop client in Resources/plugins, and do not install the plugin in the main Aircraft folder. If xPilot is absent from Plugin Admin, check the folder structure before changing network or firewall settings.

Which xPilot settings should I configure?

Configure network identity, audio, push-to-talk and CSL paths before your first connection. Explicitly selecting each audio device is safer than leaving xPilot on an operating system default that may change when a USB headset reconnects.

AreaRecommended setupWhat to verify
VATSIM accountUse your numerical VATSIM CID and the credential or sign-in flow requested by xPilot.Do not substitute an email address for the CID.
CallsignEnter the callsign you will use for the session, without spaces or decorative punctuation.It must match the callsign on your flight plan.
Aircraft typeUse the correct ICAO type designator, such as C172 or B738.An incorrect type code produces poor model matching for other pilots.
Audio inputSelect the intended microphone and speak at a normal level.The input meter should respond without remaining at maximum.
Audio outputSelect your headset or chosen speakers.Use xPilot's audio test where the installed version provides one.
Push-to-talkBind one easy-to-hold keyboard, yoke or joystick control in xPilot.The transmit indicator should activate only while the control is held.
CSL pathsAdd the folder containing your installed CSL packages and rescan or reload them.xPilot should report models loaded rather than a missing-path error.

Avoid assigning push-to-talk to a control already used for brakes, trim or another frequent X-Plane command. Grant microphone access in the operating system if the level meter remains dead even though the correct device is selected.

How do I add CSL traffic models?

CSL models let xPilot draw other VATSIM aircraft with an appropriate type and livery instead of a generic substitute. They are separate from flyable aircraft and should not be installed in X-Plane's main Aircraft directory.

Install a compatible package, add its model directory in xPilot's CSL settings, and reload the models or restart the client. Our Bluebell CSL installation and path guide covers the folder layout and model-scanning checks in detail.

Missing CSLs do not normally prevent a VATSIM login. If you can connect and hear radio traffic but see generic aircraft or no external models, investigate CSL paths and model matching rather than your account credentials.

Modern supported X-Plane 11 builds provide a traffic and TCAS interface that xPilot can use. Do not follow old instructions telling you to create 19 AI aircraft unless the documentation supplied with your specific client version explicitly requires it.

How do I connect xPilot to VATSIM?

  1. Start X-Plane 11 and load at a parking stand. Do not connect while positioned on a runway or obstructing another network user.
  2. Open xPilot and confirm simulator communication. Resolve any waiting-for-X-Plane message before attempting the network connection.
  3. Enter the callsign and ICAO aircraft type. Check both carefully because they affect identification and model matching.
  4. Connect to VATSIM. Never run two pilot clients simultaneously with the same account.
  5. Tune the radio in the aircraft. xPilot follows the simulator's active COM frequency and selected transmit radio; there is normally no need to type the frequency into a separate voice window.
  6. File or check the flight plan before requesting clearance. Keep its callsign, aircraft type and route consistent with the connected session.

The core network procedure is shared across supported X-Plane versions. Our broader VATSIM setup sequence for X-Plane explains controller contact, flight plans, radio use and first-flight etiquette.

Why does xPilot say Waiting for X-Plane connection?

This message means the standalone client cannot communicate with its X-Plane plugin. It is not usually caused by an incorrect VATSIM password.

  • Confirm that X-Plane is running and an aircraft has finished loading.
  • Check that Resources/plugins/xPilot exists in the X-Plane 11 copy you actually launched.
  • Remove double-nested folders and duplicate plugin installations.
  • Open Plugin Admin and look for a disabled or failed xPilot entry.
  • Make sure the client and plugin came from the same supported xPilot installation.
  • Allow xPilot through security software and the firewall, including local communication with X-Plane.
  • Restart both applications after reinstalling or moving plugin files.

For error-specific checks, use our xPilot connection fault checklist, which covers duplicate installations, firewall blocks and incorrect plugin placement.

Why can I connect but hear no ATC?

A successful network connection does not prove that the audio configuration is correct. Recheck the selected input and output devices, operating system microphone permission, push-to-talk indicator, active COM frequency, transmit-radio selection and xPilot audio volume.

Silence on an unstaffed frequency is normal. Verify that an online controller is covering the frequency before treating the lack of audio as a fault.

What should I check before the first flight?

  • xPilot appears as an enabled X-Plane plugin.
  • The standalone client recognises X-Plane 11.
  • The microphone meter responds and push-to-talk activates the transmit indicator.
  • The connected callsign and aircraft type are correct.
  • CSL models load without path errors.
  • The aircraft is parked clear of runways before connecting.
  • The active COM frequency and selected transmit radio match the controller you intend to call.
AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members