How do I use autopilot in MSFS airliners?

To use autopilot in Microsoft Flight Simulator 2024 or 2020 airliners, programme and verify the FMS route, set the flight directors and cleared targets, hand-fly a stable climb, engage AP1 or CMD, then select lateral and vertical modes. Confirm every change on the flight-mode annunciator; lit buttons alone do not prove a mode is active.

Is there autopilot in Microsoft Flight Simulator 2024?

Yes, equipped aircraft in MSFS 2024 have working autopilot systems, as do airliners in MSFS 2020. Autopilot is modelled as part of each aircraft, however, so there is no single universal MSFS autopilot panel or procedure.

A modern Airbus uses an FCU, managed targets and selected targets. Boeing-style aircraft normally use an MCP with modes such as LNAV, VNAV, HDG SEL and FLCH. Older airliners and business jets may offer only heading, altitude hold, vertical speed and basic navigation tracking.

The simulator's AI piloting and assistance features are not the aircraft autopilot. They can manipulate controls independently and should normally be disabled when learning the cockpit system.

What must be set before engaging the autopilot?

The autopilot needs a valid guidance source, sensible targets and an aircraft within its engagement limits. It does not decide the destination, programme the route or interpret an ATC clearance for you.

• Flight plan: the FMS must contain the intended route, with the correct runway, departure, arrival and approach where required.
• Active leg: the waypoint and leg being flown should be ahead of the aircraft. A route drawn on the MSFS world map does not prove that the cockpit FMS imported it correctly.
• Navigation source: FMS or GPS guidance must be selected for route tracking; an ILS or VOR source serves a different purpose.
• Selected targets: set the cleared altitude, initial heading and appropriate speed before take-off.
• Flight directors: switch them on as required so the guidance commands appear on the primary flight display.
• Autothrottle or autothrust: prepare it separately. The autopilot controls the flight path; it does not automatically control engine thrust unless the aircraft's separate thrust system is active.

If the route is the uncertain part, our guide to programming and checking an MSFS airliner FMC explains route entry, discontinuities, active legs and pre-flight verification.

How to use autopilot in MSFS 2024 and 2020 airliners

1. Programme and inspect the route. Check that the FMS route matches the clearance and that the first active leg makes sense. Do not blindly remove every discontinuity: a VECTOR or MANUAL segment may deliberately require an ATC heading.
2. Set the initial clearance. Enter the assigned altitude on the FCU or MCP. Select the runway heading or arm the route mode only when the programmed route is valid and the aircraft is positioned to capture it.
3. Prepare the guidance systems. Turn on the flight directors and configure autothrottle or autothrust according to the aircraft checklist. Confirm the correct barometric setting and navigation source.
4. Take off manually. Establish a positive, stable climb and keep the aircraft correctly trimmed where applicable. Engagement-height limits differ between aircraft, so do not assume that every airliner permits autopilot at the same height.
5. Select the lateral guidance. Use NAV or LNAV for a valid FMS route. Choose selected heading or HDG SEL for ATC vectors, weather avoidance, a route discontinuity or an awkward intercept.
6. Select the vertical guidance. Use managed climb, managed descent, VNAV or a flight-level-change mode when the vertical profile and performance data support it. Use vertical speed for a specific rate, but monitor airspeed closely.
7. Engage one autopilot channel. Press AP1, CMD A or the equivalent. Avoid pressing both channels in normal climb or cruise unless the aircraft's documented approach procedure requires them.
8. Read the flight-mode annunciator. Verify autopilot engagement and identify the active lateral and vertical modes. A second annunciation may show a mode that is armed and waiting to capture.
9. Monitor speed, route and altitude. Check the FMA after every selection. If the aircraft does something unexpected, disconnect or choose a simpler mode such as heading and vertical speed rather than waiting for the automation to correct itself.
10. Prepare the descent early. Load and verify the arrival and approach, set each cleared altitude, initiate the descent when required and configure the aircraft progressively. An FMS top-of-descent marker does not itself authorise or always initiate descent.

A mistake we see constantly is pressing AP and expecting the aeroplane to follow the magenta line automatically. AP1 or CMD only couples the controls to the modes already active; it does not necessarily activate NAV, LNAV or VNAV.

Which autopilot mode should I use?

Choose the simplest mode that performs the immediate task and that you can verify on the FMA.

Vertical speed mode will defend the selected rate even if the aircraft becomes too slow or too fast. FLCH, LVL CHG and Airbus open climb or descent modes normally use pitch to target speed, but thrust still depends on autothrottle, autothrust or the pilot.

How do I disconnect the autopilot safely?

Use the aircraft's autopilot-disconnect switch while holding the controls and watching the FMA. Map and test that command before flight; searching for a cockpit button during an unstable approach wastes valuable time.

Confirm that the AP indication disappears, cancel the disconnect warning as the aircraft requires and continue flying manually. Forcing the yoke or sidestick against an engaged autopilot is not the normal disconnect method and may cause a sharp control input when it releases.

How do I use the Airbus A330 autopilot in MSFS 2024?

In the MSFS 2024 Airbus A330, programme the FMS, set the cleared altitude on the FCU, use managed or selected guidance as appropriate, engage AP1 after a stable take-off and verify every command on the FMA.

Airbus FCU logic differs from a Boeing MCP. Pushing a selector generally requests a managed FMS target, while pulling it requests a pilot-selected target. For example, managed NAV follows the programmed lateral route, while selected heading flies the heading shown on the FCU.

The altitude window acts as a clearance limit. At top of descent, setting a lower altitude is only part of the process: the descent must also be initiated in the appropriate managed or selected mode. If the A330 remains level at cruise altitude, check the FCU target and vertical FMA before blaming VNAV or the flight plan.

Use AP1 for normal single-channel operation. AP2 is not a stronger cruise mode; additional channels are used only when the modelled approach or autoland procedure calls for them. Autothrust remains a separate system, so confirm its status rather than assuming AP1 controls speed and thrust.

The A330 and A320 are not identical, but they share the core Airbus ideas of AP1, the FCU, managed versus selected targets and FMA monitoring. Our detailed explanation of Airbus FCU and managed-mode operation provides a useful foundation, with the A330's own displays and procedures taking precedence.

What should I check in a Falcon 900 add-on for MSFS 2020 or VATSIM?

A Falcon 900 is a business jet rather than an airliner, but the same guidance principles apply; the exact FMS and autopilot capability depends on the specific add-on implementation.

For a package such as an Aegis Simulations Falcon 900, verify the stated simulator compatibility and included systems rather than assuming it reproduces every function of the real aircraft. A working AP button alone does not show that route sequencing, altitude capture or approach modes are sufficiently modelled for online flying.

Before taking an unfamiliar add-on onto VATSIM, test these functions offline:

• FMS route entry or import, waypoint sequencing and direct-to operation;
• HDG, NAV, altitude capture, vertical speed and any FLC or VNAV mode provided;
• recovery from a discontinuity or an ATC vector back towards the route;
• ILS localiser and glideslope capture, followed by a stable autopilot disconnect;
• controller bindings, radios and transponder operation.

VATSIM does not require VNAV or autoland. Reliable heading, altitude and speed control is enough to follow vectors and clearances, provided the pilot can revert to basic modes when the FMS behaves unexpectedly. Do not activate a direct-to waypoint or remove a vector discontinuity online unless it matches the controller's clearance.

Why is the MSFS autopilot not following the flight plan?

An engaged MSFS autopilot usually stops following the flight plan because the wrong lateral mode or navigation source is active, the FMS has no usable active leg, or the aircraft has not met the capture conditions.

1. Read the FMA first. If HDG is active, the aeroplane will fly the selected heading even when LNAV or NAV is armed. Flight-director bars without an AP or CMD annunciation do not mean the autopilot is engaged.
2. Inspect the active leg. The next leg should lead from the aircraft towards a waypoint ahead. If it points behind the aircraft, select the correct intercept or use the FMS direct-to procedure when operationally appropriate.
3. Look for a discontinuity. Correct an unintended route gap. If it represents vectors, remain in heading mode until cleared or positioned to resume the route.
4. Check the navigation source. FMS or GPS guidance, VOR tracking and an ILS localiser are different sources. NAV or LNAV cannot follow a route the avionics are not supplying.
5. Create a sensible intercept. An armed route mode may not capture from a large angle or when the active leg is behind the aircraft. Use heading mode to establish a shallow intercept, then confirm capture on the FMA.
6. Verify route changes. A new arrival, approach or direct-to may need confirmation or execution in the FMS. Ensure the displayed route and active waypoint changed as intended.
7. Check the selected altitude. VNAV and managed descent normally respect the FCU or MCP altitude as a clearance boundary. Lowering the FMS profile alone will not make the aircraft descend through the selected limit.
8. Remove competing inputs. Disable AI piloting and conflicting assistance, then check for duplicate bindings, noisy controller axes or a mapped autopilot-disconnect command.

Why will AP1 or CMD not engage or stay engaged?

AP1 or CMD may refuse to engage when the aircraft is unstable, outside the modelled engagement limits, receiving significant control input or missing a required system state. An immediate disconnect often points to controller noise, conflicting bindings, trim problems or an active disconnect control.

Stabilise the aircraft, release unnecessary control pressure and verify the flight directors, electrical state and any aircraft-specific autopilot-disengage bar or switch. Our full checklist for an MSFS autopilot that refuses to engage covers these faults without assuming one aircraft's solution applies to another.

Can an MSFS airliner autopilot land the aircraft?

Some MSFS airliners model autoland, but APP or APPR mode by itself provides an approach coupling, not a guaranteed automatic landing.

For an ILS approach, verify the correct localiser frequency, course and navigation source, whether entered manually or tuned by the aircraft. Intercept the localiser from a sensible angle and the glideslope from below, then arm approach mode and confirm both captures on the FMA.

A true autoland also requires an aircraft that models it, a suitable ILS, the required autopilot channels, correct landing configuration and explicit landing, flare and rollout annunciations appropriate to that type. If those indications do not appear, treat it as a coupled approach and disconnect in time to land manually.

An RNAV approach is not automatically an ILS autoland, even if the autopilot can follow lateral and vertical guidance. Our step-by-step MSFS 2024 ILS interception and capture procedure covers tuning, localiser and glideslope capture, APP mode and the distinction between a coupled approach and autoland.