ATC and Online Flying

Shared Cockpit in MSFS: Supported Aircraft and Setup

How shared cockpit works in MSFS with Shared Flight and YourControls, which aircraft are supported, and how to set up a two-pilot flight without desyncs.

On this page
  1. What “shared cockpit” means
  2. Your options in MSFS
  3. Which aircraft are supported?
  4. Setup checklist
  5. Dividing the work: pilot flying and pilot monitoring
  6. Flying shared cockpit on VATSIM or with ATC
  7. Troubleshooting desyncs

What “shared cockpit” means

Shared cockpit lets two simmers fly the same aircraft at the same time from different computers. One person usually acts as the pilot flying and the other as the pilot monitoring, just as a real two-pilot crew would. When one of you flips a switch, programs the flight management computer or moves a control, the change appears in the other person’s cockpit too.

This is different from ordinary multiplayer, where each person flies their own aircraft and simply sees the others. Shared cockpit means one aircraft with two sets of hands.

Your options in MSFS

Shared Flight

Shared Flight is a commercial shared cockpit tool. Its selling point is dedicated, tested support for specific complex aircraft, including popular study-level airliners whose systems are hard to synchronise. It has also been released for X-Plane 12. Because each aircraft is integrated individually, its supported list is the key thing to check before buying.

YourControls

YourControls is a free, open-source tool for MSFS. It synchronises aircraft using community-written definition files, one per aircraft. Coverage is broad for default and many third-party aircraft, but the depth of synchronisation varies. Simpler aircraft tend to work well; complex airliners with custom systems may only partly sync.

Native shared cockpit

Microsoft Flight Simulator has not historically offered a built-in shared cockpit mode, which is why these third-party tools exist. Asobo has discussed shared cockpit as a feature for the newer simulator, so check the current release notes for your version (MSFS 2020 or MSFS 2024) to see what, if anything, is available natively and for which aircraft.

Which aircraft are supported?

Why support is aircraft-specific

A basic aircraft exposes most of its state through standard simulator variables, so a sync tool can read and copy them. Complex add-ons often run their own systems logic: their own flight management computer, electrical model, hydraulics and switch logic. A sync tool has to understand each of those systems individually, which is why “does it support my aircraft?” is the first question to ask.

Shared Flight aircraft

Shared Flight publishes an official compatibility list on its website, and that list should be your reference because it changes as aircraft are added or updated.

For X-Plane 12, the aircraft reported as supported around its launch included the default Cessna 172 (G1000), the ToLiss A319, A320neo, A321, A330neo and A340-600, the Rotate MD-11, the iniBuilds A300 and A310, the Zibo 737-800, the Felis 747-200 and the FlightFactor 757 and 767. Users have reported that some aircraft not on the list, such as the FlightFactor 777, do not work.

For MSFS, support has centred on widely flown airliners and selected general aviation aircraft. Check the official list for the specific aircraft and version you own rather than relying on forum posts, which can go out of date quickly after an aircraft update.

YourControls aircraft definitions

YourControls lists the aircraft it has definitions for inside the program and on its project pages. Many default MSFS aircraft and a range of third-party aircraft are covered. If an aircraft is missing, there is sometimes a community-made definition available, but quality varies.

Setup checklist

Whichever tool you use, these steps prevent most problems:

  1. Same aircraft, same version. Both pilots need the same aircraft at the same version number. Update together.
  2. Same navigation data. Mismatched AIRAC cycles can make flight plans and procedures differ between the two cockpits.
  3. Same tool version. Both of you should run the same version of Shared Flight or YourControls.
  4. Same start state. Load the same airport and parking spot, ideally in the same cold-and-dark or ready-to-taxi state.
  5. Decide who hosts. One person hosts the session and the other joins. Depending on the tool, the connection may go through a relay service or need a direct connection; if direct, the host may need to allow the program through their firewall or forward a port.
  6. Separate voice chat. Use Discord or a similar app to talk to each other. The sync tool does not carry your crew conversation.
  7. Check control transfer. Confirm how the tool hands over the flight controls, and test it on the ground before departure.

Dividing the work: pilot flying and pilot monitoring

Shared cockpit is most enjoyable when roles are agreed before engine start. A common split is:

  • Pilot flying: handles the flight controls, autopilot mode selections and thrust.
  • Pilot monitoring: handles the radios and ATC, runs checklists, programs the FMC as agreed, and cross-checks the pilot flying.

Avoid both people pressing buttons at the same moment. In a shared cockpit, two people changing the same setting at once is one of the most common causes of desyncs.

Flying shared cockpit on VATSIM or with ATC

Shared cockpit pairs well with online ATC, because the pilot monitoring can take the radio while the other person flies. On networks such as VATSIM, only one aircraft should appear on the network for your crew; you should not both connect as separate pilots with the same aircraft. Check the documentation for your pilot client and the network’s rules on shared cockpit before your first flight. Our guide to connecting MSFS to VATSIM with vPilot covers the standard connection, and VATSIM radio phraseology for beginners is handy for whoever takes the radio.

If you would rather practise crew coordination without live controllers, the AI options in our overview of ATC in Microsoft Flight Simulator work too.

Troubleshooting desyncs

  • One cockpit shows a different state. Stop, agree which cockpit is correct, and have the other person match it. Some tools offer a resync option.
  • FMC entries do not appear for the other pilot. Confirm your aircraft is fully supported by the tool, not just partly, and that both of you are on the same aircraft version.
  • Lag or rubber-banding. Check both internet connections and close bandwidth-heavy apps. If using a direct connection, a relay option, where offered, may be more stable.
  • Problems after an aircraft update. Aircraft updates can break sync until the tool is updated. If a flight matters, avoid updating either side just beforehand.

The complete guide to atc and online flying

ATC in Microsoft Flight Simulator: Default AI vs Real Controllers
Read the guide

Keep exploring

Guides from other topics

All topics →