Skip to content
DCS World 5 min read

DCS F/A-18C autopilot not working: how do I fix it?

Ian Stephens
In short

DCS F/A-18C autopilot not working? Fix failed engagement and disconnects by checking trim, bindings, paddle input and the correct UFC mode.

In DCS World, the F/A-18C autopilot usually refuses to engage because the jet is not stable and trimmed, the control stick is not truly centred, the paddle switch is active, or the chosen mode has no valid guidance. Stabilise the aircraft, clear conflicting bindings, then select the appropriate mode from the UFC A/P menu.

How do I get the Hornet autopilot to engage?

Start by testing a basic hold mode in steady, uncomplicated flight. This separates an autopilot fault from a navigation, approach or mission-configuration problem.

  1. Establish stable flight. Use an undamaged aircraft in a normal configuration, at a safe altitude and airspeed. Settle the bank angle and vertical speed before attempting to engage the autopilot.
  2. Trim and release the stick. The jet should not require continuous pitch or roll pressure. Do not press the paddle switch while selecting a mode.
  3. Inspect the control inputs. Open DCS's controls indicator and confirm that pitch and roll inputs remain centred when the stick is released. Persistent movement usually means axis noise, an unsuitable response curve or another controller sending commands.
  4. Select a simple mode. Press the UFC A/P pushbutton, then use the option-select button beside ATTH or BALT. ATTH is a useful first test; for BALT, settle the vertical speed before engaging it.
  5. Check that the mode remains selected. If it stays active and controls the aircraft, the basic system works. Test HSEL or coupled navigation only after setting the required heading or guidance source.

The F/A-18C autopilot is an automatic flight-control aid, not a recovery system for an aircraft already departing from controlled flight. High angle of attack, aggressive manoeuvring, a large trim error or an active flight-control fault can prevent engagement or exceed its authority.

Why does the F/A-18C autopilot disconnect immediately?

An immediate disconnect normally indicates a live disengage command, non-centred flight controls or an aircraft state outside the selected mode's limits.

  • Paddle switch input: Check the autopilot or nosewheel-steering disengage command. A maintained HOTAS switch assigned to this momentary function can hold the command permanently active.
  • Duplicate pitch or roll axes: DCS may have assignments in several device columns, including a throttle, gamepad or unused controller. Remove every unintended axis rather than masking it with a large dead zone. Our Hornet HOTAS and axis setup procedure explains where these duplicate assignments commonly hide.
  • Noisy controls: If the physical stick jitters around its centre, apply only the smallest dead zone needed to stop the movement. A large dead zone makes formation flying and refuelling harder without fixing a defective axis.
  • Wrong control profile: Make changes in the active F/A-18C aircraft profile, not another module or a general interface layer. See our explanation of aircraft-specific DCS control profiles if a command appears correctly assigned but does nothing in the Hornet.
  • Invalid flight condition: Stabilise after configuration, power or trim changes. The autopilot may also drop out when manual control input or a manoeuvre exceeds its authority.
  • Damage or mission failures: Resolve FCS cautions and repeat the test in a clean mission with failures disabled. A damaged flight-control system cannot be repaired through the UFC menu.

If the UFC A/P menu itself does not appear, verify that the UFC is powered and that other UFC buttons respond. When cockpit controls animate but do not activate, work through these cockpit mouse and switch input checks before treating it as an autopilot failure.

Which F/A-18C autopilot mode should I use?

Choose the mode that controls the quantity you actually want held; ATTH, HSEL, BALT, RALT and CPL are not interchangeable.

ModeWhat it doesCommon mistake
ATTHStabilises the aircraft at its existing attitude.Expecting it to level the wings or capture an altitude automatically.
HSELTurns towards and holds the heading selected on the HSI.Leaving the heading selector on its old value or expecting it to follow a waypoint.
BALTHolds barometric altitude.Engaging during a climb or descent, or expecting terrain clearance.
RALTHolds radar altitude while a valid radar-altimeter return is available.Using it outside the radar altimeter's useful range or treating it as a terrain-avoidance system.
CPLCouples the aircraft to compatible, valid navigation or approach steering.Trying to engage it without the required steering source and mission support.

A displayed navigation needle does not automatically make CPL available. Waypoint steering, course guidance and carrier approach coupling have different setup requirements. Use a procedure matching the aircraft and mission state; our guide to checking module-specific Hornet procedures helps avoid applying instructions from another aircraft or an outdated cockpit workflow.

Why does the autopilot hold altitude but not speed or course?

Altitude hold controls the aircraft's vertical response; it does not automatically manage throttle, airspeed or lateral navigation. Add HSEL or valid coupled steering when lateral guidance is required, and manage thrust separately unless you deliberately engage the Hornet's automatic throttle control under suitable conditions.

A jet can therefore maintain BALT while slowing down, increasing angle of attack and eventually reaching the autopilot's control limits. Likewise, HSEL holds a heading rather than a wind-corrected ground track, so a crosswind can carry the aircraft away from the desired route.

RALT deserves extra caution: it references height above the surface, but it is not a terrain-following or obstacle-avoidance system. Abrupt terrain, invalid radar-altimeter data or excessive closure can demand more than the autopilot can safely provide.

If ATTH and BALT still fail in a clean, stable test after the controls are corrected, disable module-altering mods, run the platform's repair or file-verification function, and retest before rebuilding the Hornet input profile. Back up the existing profile first so useful bindings are not lost.

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