Fix Concorde autopilot problems in Microsoft Flight Simulator by checking compatibility, power, flight modes, trim and controller conflicts.
Concorde’s autopilot usually fails in Microsoft Flight Simulator because the aircraft package is incompatible with that simulator version, its electrical or hydraulic systems are not ready, no valid guidance mode is selected, or a controller input disconnects it. First confirm you have a native, updated MSFS Concorde rather than an FSX/P3D model.
Is the Concorde add-on compatible with your MSFS version?
Concorde is an add-on aircraft, so its systems depend on the particular package rather than Microsoft Flight Simulator alone. Use a build that explicitly supports your simulator—MSFS 2020 or MSFS 2024—and your platform.
An old aircraft can sometimes display its exterior model while its gauges, autopilot and custom systems remain inoperative. For example, the package on our legacy Concorde download page is explicitly for FSX and Prepar3D; placing it in an MSFS Community folder does not convert it into an MSFS aircraft.
An MSFS 2020 package is not automatically fully compatible with MSFS 2024 either. Check that the installed release supports the version being used and that it includes a functional cockpit rather than only a visual model.
| Symptom | Likely cause | First check |
|---|---|---|
| Autopilot controls are dead or blank | Legacy package, incomplete installation or missing aircraft power | Package compatibility and electrical state |
| Autopilot engages and immediately disconnects | Controller input, trim command or unstable flight | Bindings, dead zones and manual trim |
| Autopilot remains engaged but does not turn | No lateral mode or the wrong navigation source | Heading mode, INS/GPS source and active route leg |
| Selected altitude changes but the aircraft stays level | No vertical guidance mode selected | Pitch, vertical-speed or aircraft-specific climb mode |
| Heading and altitude work but speed does not | Autothrottle is separate from the autopilot | Autothrottle state and physical throttle input |
How do you get the Concorde autopilot working?
- Install one supported version. Remove duplicate or obsolete Concorde folders before reinstalling the latest compatible package. On PC, check the Community folder; on consoles, use the simulator’s installed-content screen. Do not merge an update into an older aircraft folder unless its instructions specifically require that.
- Test without extra modifications. Select the package’s standard livery and temporarily remove cockpit, systems or flight-model modifications. A normal texture-only livery should not alter the autopilot, but packages containing panel or aircraft configuration files can.
- Start in a powered state. Use a runway or ready-to-fly start for the first test. Confirm the generators, avionics and any modelled hydraulic systems are operating; Concorde’s cold-and-dark procedure is a poor place to diagnose basic autopilot operation.
- Stabilise and trim manually. Fly level at a normal simulation rate, away from take-off, landing and transonic acceleration. Centre the controls and trim out sustained pitch pressure before engaging the system.
- Test simple modes first. Set the heading selector to the present heading, engage the actual autopilot channel, then select heading mode and altitude hold. Flight directors or illuminated mode selectors alone do not necessarily mean the autopilot servos are engaged.
- Check every controller profile. Search for duplicate assignments to autopilot disconnect, pitch trim, elevator, aileron and rudder. Disconnect secondary controllers temporarily and disable AI piloting or assisted control features while testing.
- Add navigation modes last. Once heading and altitude hold work, test route tracking, climb modes, autothrottle and approach functions one at a time.
Why does the autopilot engage and then disconnect?
An immediate disconnect normally means MSFS is receiving a manual control or disconnect command, or the aircraft is not in a state the add-on accepts. Noisy joystick axes, a second controller, repeated trim commands and an incorrectly assigned switch are common causes.
Open the active control profiles for every connected device, not just the main yoke or stick. Add only enough dead zone to stop unwanted movement. If the same fault affects default aircraft, work through our simulator-wide autopilot engagement checks; if it affects only Concorde, concentrate on that package’s installation, systems and operating procedure.
Why will Concorde hold heading but not follow the route?
If heading mode works, the autopilot servos are probably functional; the fault is usually the navigation source or route data. Concorde add-ons differ here: one may simulate an inertial navigation system, while another may translate the MSFS flight plan into custom cockpit logic.
- Confirm that the lateral mode is set to navigation rather than heading.
- Select the source expected by the package, such as INS or its implemented GPS input.
- Make sure the INS is aligned and populated if the aircraft models that process.
- Activate a valid route leg and intercept it from a sensible angle.
- Do not assume a route created on the World Map has automatically entered a custom INS.
If route tracking works but the aircraft will not capture an approach, check the frequency, course, navigation source and intercept geometry using our MSFS ILS troubleshooting steps.
Does Concorde autopilot control speed and altitude automatically?
The autopilot and autothrottle are separate systems. Engaging the autopilot does not guarantee speed control, and entering a higher altitude does not by itself command a climb.
Select an appropriate pitch, vertical-speed or aircraft-specific climb mode, then arm or capture the target altitude as the add-on requires. Controls labelled MAX CLIMB or MAX CRUISE, where modelled, follow aircraft-specific logic and should be used according to that package’s procedure.
For speed control, arm and engage the autothrottle separately. A moved or noisy hardware throttle can override it in some implementations. If the basic heading-and-altitude test succeeds but advanced modes do not, the remaining issue is package-specific configuration or procedure—not a reason to reinstall the whole simulator.