Learn to use the default Boeing 747 autopilot in FSX for climbs, altitude capture, GPS tracking and ILS approaches, plus common fixes.
To use the default Boeing 747-400 autopilot in FSX, stabilise the aircraft, set the desired heading, altitude, vertical speed and airspeed on the mode control panel, switch on the flight director and autothrottle as required, select the appropriate modes, then engage CMD/AP. Monitor every capture; FSX models the system more simply than the real 747.
What do the default 747 autopilot controls do?
The stock 747-400 separates lateral guidance, vertical guidance and throttle control; engaging the autopilot master alone does not select all three.
| Control | What it does in FSX | Common mistake |
|---|---|---|
| FD | Displays flight-director guidance bars. | The flight director does not fly the aircraft by itself. |
| CMD/AP | Engages the autopilot master so the aircraft follows selected pitch and roll modes. | Pressing it without checking the selected targets can produce an abrupt turn or climb. |
| A/T ARM and SPD | Arms the autothrottle and commands the selected IAS or Mach. | The autopilot does not control airspeed merely because CMD is engaged. |
| HDG SEL | Turns towards and maintains the heading set in the heading window. | The heading bug may still contain an old value. |
| NAV | Tracks radio navigation or the FSX GPS route, depending on the NAV/GPS selector. | NAV cannot follow a GPS route while the selector remains on NAV. |
| ALT and V/S | Use the selected altitude as the level-off target and vertical speed for the climb or descent. | A zero vertical speed or unarmed altitude mode leaves the aircraft level or lets it pass the target. |
| APP/APR | Captures an ILS localiser and glideslope through NAV1. | It will not capture an ILS while the NAV/GPS selector is set to GPS. |
The panel uses the same underlying simplified FSX logic as the other default aircraft. Our mode-by-mode explanation of the FSX autopilot covers the broader relationship between heading, navigation, altitude and approach modes.
How do I set up a climb, cruise and descent?
For normal use, programme the targets first, establish stable flight and then let CMD/AP take control.
- Hand-fly the departure initially. Complete the take-off, retract the landing gear and establish a sensible climb attitude and airspeed before engaging the autopilot.
- Set the targets. Turn the heading selector to the required heading, enter the cleared altitude, choose a suitable vertical speed and set the desired IAS or Mach.
- Select the roll mode. Use HDG SEL for a commanded heading. Use NAV only when a radio course or active GPS leg is ready to capture.
- Select the vertical modes. Select the target altitude and V/S. Use a moderate climb rate that the aircraft can maintain without losing airspeed.
- Configure speed control. Arm A/T and select SPD if you want the autothrottle to hold the speed-window value.
- Engage CMD/AP. Check immediately that the 747 turns, pitches and accelerates in the expected direction. Reselect a mode if its indication is not active.
- Watch the altitude capture. As the selected altitude approaches, the aircraft should reduce its vertical rate and change to altitude hold. Do not leave a large vertical speed selected close to the target.
At cruise, the usual combination is ALT hold, HDG SEL or NAV, and autothrottle speed control. To descend, select a lower altitude, enter a negative V/S and confirm that altitude capture remains armed. The default system does not calculate a descent profile, observe restrictions or manage a real 747 speed schedule for you.
Avoid trimming against the autopilot. FSX may move elevator trim while CMD is engaged, so be ready for a pitch change when disconnecting and re-trim the aircraft manually. For the surrounding aircraft procedures, use our phase-by-phase checklist for the default 747-400.
How do I make the FSX 747 follow a GPS flight plan?
The default 747 follows an active FSX GPS route through NAV hold; it does not provide a fully modelled 747 FMC with real LNAV and VNAV.
- Load or create an FSX flight plan. Confirm that the GPS displays an active magenta leg rather than merely showing the route map.
- Set the NAV/GPS selector to GPS. This sends GPS steering to the autopilot's navigation mode.
- Intercept the active leg. Use HDG SEL to approach the magenta course at a shallow angle. NAV mode may fail to capture cleanly if the aircraft is far away or pointing in the opposite direction.
- Select NAV hold. Confirm that the aircraft turns onto the active leg and follows subsequent waypoints.
- Manage the vertical profile yourself. Set every altitude, vertical speed and speed change on the panel; GPS tracking supplies lateral guidance only.
If the aircraft turns towards an unexpected waypoint, inspect the active GPS leg rather than the line nearest the aeroplane. Activating the correct leg or using a direct-to command usually fixes the problem.
How do I use APP mode for an ILS?
APP/APR can capture the localiser and glideslope, but only when NAV1 is tuned correctly and the NAV/GPS selector has been returned to NAV.
Set the ILS frequency in NAV1, enter the published front course and intercept the localiser using HDG SEL. Approach from below the glideslope, then arm APP/APR before crossing the localiser. The autopilot should capture lateral guidance first and vertical guidance as the glideslope reaches the aircraft.
FSX ATC clearance does not guarantee that the radio, course and selector are configured correctly. Our complete FSX ILS tuning and capture procedure covers those steps in detail.
Treat APP as an approach aid rather than a complete default-aircraft autoland. The stock 747 can track the beams, but it does not faithfully reproduce the real aircraft's triple-channel flare, retard and rollout logic. Disconnect at a suitable point and land manually unless you are deliberately experimenting; our guide to what a simulated 747 autoland actually requires explains the distinction.
Why is the 747 autopilot not doing what I selected?
Most problems come from a conflicting mode, an incorrect NAV/GPS position or a target that was set but never armed.
- It will not climb or descend: check that the selected altitude differs from the present altitude, V/S is not zero and ALT mode is selected. Also verify that the aircraft has enough thrust and airspeed for the commanded climb.
- It ignores the selected speed: arm A/T and select SPD. A noisy hardware throttle axis can interfere with autothrottle commands.
- It will not follow GPS: confirm that the route has an active leg, set NAV/GPS to GPS and intercept the leg before selecting NAV.
- It captures the localiser but not the glideslope: the aircraft may be above the glideslope, APP may not be armed, or the wrong ILS frequency may be in NAV1.
- It oscillates or overcorrects: reduce the commanded vertical speed, avoid high simulation rates and check for joystick drift or duplicate control assignments.
- It turns the wrong way after engagement: inspect the heading window and active navigation leg before blaming the autopilot. CMD follows the selected target, even when that target is stale.