Use the F-35 autopilot in MSFS 2020: set heading, altitude and NAV modes correctly, and fix common engagement and route-tracking problems.
The F-35 is a third-party aircraft in Microsoft Flight Simulator 2020, so its autopilot controls vary by add-on. In most versions, stabilise the jet, set a heading and altitude, engage the aircraft's AP master or assigned Autopilot Master control, then select HDG or NAV and ALT, VS or FLC.
Is the F-35 autopilot the same in every add-on?
No: MSFS 2020 has no default F-35, and each developer decides which autopilot functions to model. One package may provide controls on the cockpit display, while another relies partly on standard MSFS control assignments or offers only basic heading and altitude hold.
First identify the exact aircraft package and variant you installed. Our guide to the available F-35 packages and their differences can help if the aircraft name is unclear. The supplied manual remains authoritative for custom cockpit pages and mode limitations.
The F-35's fly-by-wire system is not the autopilot. Fly-by-wire stabilises and interprets control inputs continuously; autopilot modes command a heading, route, altitude or vertical profile without the pilot holding the stick.
How to engage the F-35 autopilot
The reliable method is to configure the route and targets first, establish stable flight, and then engage one lateral mode and one vertical mode.
- Prepare the navigation source. For NAV mode, create a flight plan before loading the flight or enter it through the add-on's avionics if supported. Confirm that GPS or FMS navigation is selected and that the intended leg is active.
- Check your control assignments. In
Options > Controls Options, search for autopilot, heading, altitude and vertical speed. Assign the AP master, heading hold, navigation hold and altitude controls you need. Remove duplicate assignments from unused controllers because a second switch can cancel the cockpit command. - Stabilise the aircraft manually. Use a moderate attitude and speed, level the wings, centre the stick and allow the flight controls to settle. Large control inputs or a noisy joystick axis can prevent engagement or cause an immediate disconnect.
- Set the lateral target. Move the heading bug to the required heading for HDG mode. For NAV mode, verify the route, active leg and navigation source rather than relying on the map line alone.
- Set the vertical target. Select the desired altitude. Use ALT to hold level flight, VS for a chosen climb or descent rate, or FLC if the particular F-35 implements it. With FLC, the autopilot normally controls pitch for speed while you manage thrust.
- Engage the AP master. Press the cockpit's AP control or your assigned Autopilot Master command. Select HDG or NAV, followed by the required vertical mode. Some implementations initially hold the present attitude until another mode is selected.
- Read the active-mode indications. Confirm that the display shows the modes as active or captured, not merely selected or armed. Flight-director guidance alone does not mean the autopilot is controlling the aircraft.
- Monitor speed and disconnect deliberately. Do not assume the add-on has autothrottle. Use the AP disconnect command before taking control, then apply smooth stick pressure rather than fighting the servos.
If the relationship between AP master, heading, altitude and vertical modes is unfamiliar, the same principles are covered in our general MSFS autopilot workflow.
What do the F-35 autopilot modes do?
The exact labels vary, but these are the common MSFS autopilot functions an F-35 add-on may expose.
| Mode | Purpose | Common mistake |
|---|---|---|
| AP or AP master | Enables autopilot control | Assuming it automatically follows every selected target |
| HDG | Turns towards and follows the heading bug | Leaving the bug on an old heading |
| NAV or GPS | Tracks the active flight-plan leg | Using the wrong source or having no active leg |
| ALT | Holds or captures altitude, depending on the add-on | Confusing present-altitude hold with selected-altitude capture |
| VS | Commands a climb or descent rate | Selecting an excessive rate and losing airspeed |
| FLC | Uses pitch to maintain a selected speed | Expecting the autopilot to manage thrust |
| APR | Captures supported approach guidance | Treating approach mode as an automatic landing system |
Why will the F-35 autopilot not engage or follow the route?
An F-35 autopilot usually fails because of control input, conflicting bindings, an invalid navigation source or a mode that the add-on does not implement.
- AP disconnects immediately: centre the stick, inspect axis jitter and add a small dead zone if necessary. Check that no controller button is continuously sending an AP disconnect command.
- The jet ignores the selected heading: verify that HDG is active rather than merely armed, and confirm that the heading bug actually moved.
- NAV turns the wrong way: check the GPS or FMS source, activate the correct flight-plan leg and approach the route on a reasonable intercept. HDG mode may also need to be cancelled before NAV can capture.
- The route appears on the World Map but not in the cockpit: some custom avionics do not import every MSFS flight plan correctly. Load or enter the route using the method supported by that aircraft.
- Altitude hold climbs or descends: determine whether ALT captured the current altitude or armed the selected altitude. Reduce an aggressive VS setting and maintain enough thrust to prevent airspeed loss.
- The AP button works but a mode is missing: that function may not be modelled. Standard MSFS bindings cannot force unsupported custom avionics to provide FLC, approach capture or autothrottle.
- AI assistance fights the aircraft: disable AI piloting and any assistance that manipulates flight controls while troubleshooting.
For persistent engagement failures, work through the power, trim, navigation-source and controller checks for an MSFS autopilot.
Can the F-35 autopilot land or control STOVL flight?
Do not assume that an F-35 add-on can autoland or manage an F-35B hover transition. APR mode may capture an ILS localiser and glideslope when the package supports them, but that does not guarantee automatic flare, throttle control or rollout guidance.
STOVL and hover controls are separate from the normal MSFS autopilot. During an F-35B transition, use only the procedures and dedicated controls documented for that package; disconnect the conventional autopilot unless its manual explicitly says it supports the manoeuvre.