Skip to content
Microsoft Flight Simulator 6 min read

How do I use the iniBuilds A310 autopilot in MSFS 2020?

Ian Stephens
In short

Learn the iniBuilds A310 autopilot in MSFS 2020: setup, AP1, NAV, PROFILE, altitude changes, ILS approaches and common fixes.

To use the iniBuilds A310 autopilot in MSFS 2020, align the IRS, programme and verify the MCDU route, switch on both flight directors, set the target altitude, then engage AP1 after take-off. Select NAV or heading guidance and PROFILE, level change, or vertical speed, while confirming every active mode on the FMA.

What must be set before engaging the A310 autopilot?

The autopilot needs valid attitude and navigation data, a sensible flight plan and a stable aircraft before it can provide reliable guidance. A runway-ready start may complete some of this work, but the indications still need checking.

  1. Align the inertial reference system. Confirm that the IRS units are aligned and supplying position and attitude data. Follow our A310 IRS alignment procedure if the displays show flags or NAV refuses to work.
  2. Programme and verify the route. Check the departure, arrival, runway, active leg and every discontinuity. Our guide to building and checking an airliner FMC route covers the underlying workflow.
  3. Set the initial targets. Enter the cleared altitude, departure heading if required and an appropriate speed on the Flight Control Unit, or FCU.
  4. Switch on the flight directors. Their command bars and Flight Mode Annunciator, or FMA, indications show what the automation intends to do before AP1 is engaged.
  5. Prepare autothrust separately. Autothrust controls engine thrust; AP1 controls the flight path. One can operate without the other.

The selected altitude is a limit, not automatically a climb or descent command. After changing it, select a vertical mode that tells the aircraft how to reach it.

How do I engage AP1 after take-off?

Engage AP1 only after the A310 is airborne, stabilised and trimmed at a safe height. Hand-fly the initial departure, then use the FCU to establish lateral and vertical guidance.

  1. Set the cleared altitude in the FCU altitude window.
  2. Select lateral guidance. Use NAV to follow the active MCDU route, or use the heading selector for an assigned heading.
  3. Select vertical guidance. Choose PROFILE, level change or vertical speed according to the situation.
  4. Engage AP1. AP1 is the normal single autopilot channel for departure, cruise and most approaches.
  5. Read the FMA. Confirm that the expected lateral, vertical and autothrust modes are active or armed. The FMA is authoritative; an illuminated FCU control alone does not prove that a mode captured.

The A310 predates the A320-style cockpit and its automation should not be treated as an A320 with older instruments. MSFS Legacy and Lock interaction modes also use different mouse gestures for rotary, push and pull actions, so watch the control tooltip and visible knob movement. For the principles behind armed, captured and active modes, see our airliner autopilot and FMA workflow.

Which A310 autopilot mode should I use?

Choose the mode according to whether you want the MCDU to manage the flight path or need direct control for an ATC instruction.

TaskModeMain requirement or limitation
Follow the programmed routeNAVThe IRS must be aligned and the correct MCDU leg must be active without an unresolved discontinuity.
Fly an assigned headingHDGSet the required heading and command selected heading guidance rather than NAV.
Follow the FMS climb or descentPROFILEThe MCDU needs valid performance data, constraints and a computed vertical profile.
Make a straightforward altitude changeLVL CHThe aircraft pitches for the commanded speed while climbing or descending towards the selected altitude.
Use a specific climb or descent rateV/SMonitor airspeed closely; an excessive rate can produce an overspeed or stall.
Maintain the captured altitudeALTVerify altitude capture on the FMA rather than relying only on the selected altitude window.

PROFILE is appropriate when the MCDU route and vertical constraints are complete. Use LVL CH for a simple altitude change, especially after an ATC clearance, and V/S when controlling the rate matters more than following a computed profile.

How do I fly an ILS approach or autoland?

The A310 can capture an ILS and perform a dual-channel automatic landing when the aircraft, approach and runway data support it. Do not engage both autopilots during ordinary cruise merely because two channels are available.

  1. Tune and identify the ILS. Verify the frequency, inbound course and runway against the approach being flown.
  2. Establish a sensible intercept. Approach the localiser at a moderate angle and remain below the glide slope before capture.
  3. Arm LAND mode. Confirm that localiser and glide-slope guidance appears armed on the FMA, then watch each mode capture.
  4. Engage AP2 for dual-channel operation. Do this only when using the properly established landing mode and intending an automatic landing.
  5. Configure the aircraft normally. Set landing speed, flaps, landing gear, spoilers and autobrake; autopilot engagement does not complete these tasks.
  6. Check the landing annunciations. Continue only if the FMA shows the expected LAND, FLARE and rollout capability. Disconnect and fly manually if the indications are missing or unstable.

Not every MSFS ILS or scenery runway behaves well enough for autoland. The pilot must still monitor the flare, centreline tracking and speed, and reverse thrust remains a pilot action after touchdown.

Why will the A310 autopilot not engage or follow NAV?

Most A310 autopilot problems come from incomplete aircraft setup, an uncommanded mode or conflicting simulator inputs rather than a faulty AP1 button.

  • AP1 will not engage: stabilise and trim the aircraft, centre the controls, confirm electrical and hydraulic availability, switch on the flight directors and check that no autopilot-disconnect binding is being held.
  • NAV turns the wrong way: inspect the active MCDU leg. A departure discontinuity, incorrect direct-to selection or route beginning behind the aircraft can command an unexpected turn.
  • NAV remains armed: reduce the intercept angle and move closer to the intended track. NAV may not capture an unsuitable geometry immediately.
  • PROFILE does nothing: verify the cruise altitude, performance entries, route constraints and vertical profile. Use level change when the FMS profile is incomplete.
  • The altitude window changes but the aircraft stays level: select PROFILE, LVL CH or V/S. Turning the altitude knob alone does not command vertical movement.
  • The aircraft oscillates or disconnects: remove duplicate control bindings, add dead zones to noisy axes, disable AI piloting or assisted controls and return simulation rate to normal.
  • Speed is not controlled: check autothrust separately. AP1 can steer and hold altitude while autothrust remains disengaged.

If the basic checks do not solve it, use our autopilot engagement troubleshooting checklist to isolate power, trim, bindings and navigation-source faults.

How do I disconnect the A310 autopilot cleanly?

Use the assigned autopilot-disconnect control or the active AP1 button, take control smoothly and trim the aircraft for the present speed and configuration. Cancel the disconnect warning using the modelled disconnect control, and verify on the FMA that no autopilot channel remains engaged.

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