How do I use the Daher TBM 930 autopilot in MSFS?

To use the Daher TBM 930 autopilot in Microsoft Flight Simulator, programme the G3000 flight plan, set the heading and target altitude, select a lateral mode such as HDG or NAV and a vertical mode such as FLC or VS, then press AP. You still control power, configuration and the landing.

The TBM 930 uses Garmin G3000 avionics with a dedicated autopilot mode controller. The mode annunciations across the top of the primary flight display are authoritative: active modes are normally green, while armed modes are white. Always confirm those annunciations rather than assuming a button press took effect.

TBM 930 autopilot quick-start procedure

A normal departure uses HDG or NAV for lateral guidance and FLC for the climb.

1. Power and configure the G3000. Complete the aircraft start and make sure the primary flight display, multifunction display and navigation system are operating normally.
2. Programme and activate the route. Check that the intended leg is magenta and that the flight plan contains no unwanted discontinuity. Our guide to entering and activating a Garmin-style flight plan covers the route-entry process separately.
3. Set the heading and altitude. Turn the heading bug towards the initial course and use the altitude selector to set the cleared or intended altitude.
4. Select the flight-director modes. Press FD, choose HDG or NAV, then select FLC or VS. Engage the yaw damper when appropriate.
5. Establish a safe climb. Hand-fly the TBM after take-off until it is stable, correctly trimmed and above the autopilot engagement limits used for the flight.
6. Engage AP. Press the AP button and confirm that AP appears on the primary flight display. Avoid moving the controls against the servos.
7. Monitor the aircraft. Check the active lateral mode, active vertical mode, selected altitude, airspeed and engine power. The TBM 930 does not have an autothrottle.

Pressing AP by itself does not tell the aircraft to follow the flight plan or climb to the altitude selector. If no suitable modes have been chosen, the system may enter basic roll and pitch modes instead. Our explanation of the core MSFS autopilot modes provides the wider mode logic behind this TBM-specific procedure.

Which TBM 930 autopilot mode should I use?

Use HDG for manually assigned headings, NAV for the active G3000 route, FLC for speed-controlled climbs, VS for a chosen vertical rate and APR for an ILS or vertically guided RNAV approach.

Most climbs and descents made with FLC or VS will capture the altitude shown in the selector and change to ALT mode. Confirm the capture on the flight-mode annunciator; do not rely only on the altitude bug.

How do I make the TBM 930 follow the G3000 flight plan?

NAV mode follows the active G3000 leg only when the correct navigation source is selected and the aircraft is in a reasonable position to intercept it.

1. Activate the intended flight-plan leg or use Direct-To for the required waypoint.
2. Verify that the course is magenta and the HSI source shows GPS when following a normal GPS route.
3. Use HDG mode to approach the route at a sensible intercept angle.
4. Press NAV and look for NAV or GPS in the armed area of the flight-mode annunciator.
5. Confirm that the lateral mode turns green when the course is captured.

If the active leg begins behind the aircraft, NAV may command a large turn back towards it. Activate the correct onward leg rather than repeatedly pressing NAV. A wrong GPS/VLOC source, route discontinuity or noisy controller input can also produce the behaviour covered in our guide to fixing unexpected autopilot turns and pitch changes.

How should I climb and descend in the TBM 930?

FLC is usually the better choice when protecting airspeed matters; VS is useful when a specific climb or descent rate is required.

Climbing with FLC

Set an altitude above the aircraft, select FLC and adjust the displayed target speed with the autopilot's pitch controls. Apply suitable climb power and verify that FLC is active. The autopilot pitches for the selected speed, while the resulting climb rate changes with power and aircraft performance.

A mistake we see constantly is selecting a high vertical speed and then ignoring the falling airspeed. FLC avoids that particular problem, but it cannot compensate for badly managed power indefinitely.

Descending with VS, FLC or VNAV

For a straightforward descent, set a lower altitude, reduce power and select a modest VS or FLC target. Choose VS when rate is the priority; choose FLC when speed is the priority. Keep watching torque, airspeed and the altitude capture.

VNAV can follow eligible altitude constraints when the route contains usable vertical data. Arm it before the calculated descent point and set the altitude selector no lower than the altitude to which the aircraft is cleared. VNAV manages pitch guidance, not power, and not every approach or imported route provides a capturable vertical path.

How do I use APR mode for an ILS or RNAV approach?

APR mode must be armed with the correct approach, active course and navigation source before the TBM reaches the final approach path.

1. Load the approach. Activate the appropriate leg or continue in HDG mode if vectors are being used.
2. Verify the navigation source. Use GPS for an RNAV approach. For an ILS, verify the localiser frequency and the relevant LOC navigation source rather than assuming automatic switching occurred.
3. Set up the intercept. Approach the final course at a shallow angle and, for vertical capture, from below the glideslope or glidepath.
4. Press APR. Confirm that the lateral and vertical approach modes are armed, then watch them change to active modes during capture. An ILS normally shows LOC and GS; a vertically guided RNAV approach uses GPS lateral guidance and GP.
5. Manage the aircraft. Reduce power, extend gear and flaps, and maintain the required speed. The standard TBM 930 autopilot neither controls the throttle nor performs an automatic landing.

An RNAV approach without approved vertical guidance may provide lateral tracking but no capturable glidepath. If GS or GP remains armed, first check the approach type, source, intercept position and active leg.

Why will the TBM 930 autopilot not engage or follow a mode?

Most TBM autopilot failures in Microsoft Flight Simulator come from missing electrical power, an incorrect navigation source, an unsuitable intercept or conflicting control inputs.

• AP will not engage: check electrical and avionics power, flight-director operation, aircraft trim and any duplicated autopilot-disconnect binding.
• NAV stays armed: verify the active leg and navigation source, then use HDG to create a practical intercept.
• The aircraft stays level: ALT may be holding the present altitude. Set the target altitude and select FLC, VS or VNAV.
• The aircraft will not climb: confirm that the selected altitude is above the aircraft, increase power appropriately and check that FLC or VS is active rather than merely armed.
• The aircraft pitches or turns unexpectedly: disconnect AP, stabilise manually and inspect the active modes, route geometry, trim and controller axes before re-engaging.
• The autopilot disconnects repeatedly: look for strong manual control input, trim problems, an assigned AP-disconnect button firing continuously or another device sending unwanted pitch and roll commands.

For engagement-specific faults, follow our autopilot power, trim and binding checks. Cockpit presentation can vary between Microsoft Flight Simulator releases and aircraft updates, but the G3000 mode logic remains the same: set the target, select the mode and verify the annunciation.

How do I disconnect the TBM 930 autopilot?

Use the autopilot-disconnect control on the yoke, an assigned controller button or the AP button on the mode controller, then confirm that the AP annunciation disappears. Disconnect before fighting an unwanted command. The flight director may remain on and continue showing command bars, while the yaw damper is controlled separately.