Learn Boeing 747 autoland setup: ILS tuning, APP mode, triple autopilot, LAND 3 checks, flare, rollout and fixes for failed capture.
To autoland a Boeing 747 in a flight simulator, load and identify a valid ILS, intercept the localiser and glideslope from below, select APP, then engage all three autopilot channels when the aircraft permits it. Confirm LAND 3 or LAND 2, and keep the automation engaged through flare and runway rollout.
What does a Boeing 747 need for autoland?
For Aviation & Real-World Flying practice, autoland means an automatic approach, flare and runway rollout—not simply following an ILS with one autopilot connected. The simulated 747 must model multiple autopilot channels, radio-altimeter inputs, automatic flare and rollout guidance.
- The runway must have a usable, correctly aligned ILS.
- The aircraft must support multi-channel autoland rather than only a coupled ILS approach.
- The relevant electrical, hydraulic, navigation and automatic-flight systems must be available.
- Wind and runway conditions must remain within the limits modelled by the aircraft.
- The simulator’s navigation data and airport scenery must agree on the runway and ILS position.
Pressing APP cannot add capabilities that the aircraft or airport lacks. Our explanation of why both suitable ILS equipment and a capable aircraft are required covers that distinction.
The 747-400 and 747-8 use the same broad sequence, but FMC pages, mode annunciations and channel-engagement logic vary between aircraft implementations. Simplified models may land automatically without accurately reproducing LAND 3 redundancy, while detailed add-ons may reject autoland if a prerequisite is missing. For Microsoft Flight Simulator, our comparison of 747 add-ons with different levels of systems depth helps identify what the aircraft is expected to simulate.
How do you perform a Boeing 747 autoland?
- Choose a suitable ILS runway. Load the ILS approach in the FMC and check its frequency, identifier and inbound course against the intended runway. A full-fidelity 747 may autotune the ILS through the FMC or
NAV RADpage; a simpler model may require manual NAV-radio tuning. - Prepare the landing data. Select the intended landing flap, normally flap 25 or 30 where supported, and calculate VREF for the actual landing weight. Apply only the wind correction prescribed by that aircraft, set the appropriate minimums and choose an autobrake setting suitable for the runway.
- Configure the aircraft. Arm the speedbrake, lower the landing gear and extend flap on schedule. Both flight directors should normally be on, with one autopilot controlling the initial intercept.
- Intercept from below. Approach the localiser on a shallow intercept heading while level below the glideslope. Trying to capture the glideslope from above is one of the most common reasons a simulated autoland fails.
- Select APP and monitor the FMA. The localiser should capture first, followed by the glideslope. Watch the flight-mode annunciator on the primary flight display; illuminated buttons alone do not prove that either beam has captured.
- Engage the remaining autopilot channels. After approach mode is armed or captured, select the other CMD channels when the model accepts them. A detailed 747 normally uses the left, centre and right channels for full redundancy. Some add-ons arm the extra channels rather than showing them as immediately active.
- Verify autoland status. Before the aircraft reaches the model’s autoland status gate, confirm LAND 3 or an acceptable LAND 2 indication. FLARE and ROLLOUT should arm at the appropriate stage. If only LOC and G/S appear with one CMD channel, treat it as a coupled ILS that still requires a manual flare.
- Leave the controls alone. Keep the autopilot and autothrottle engaged unless the aircraft’s checklist says otherwise. Avoid moving the yoke, pedals or throttles as the system enters flare; even a small controller input can disconnect the automation.
- Monitor touchdown and rollout. Confirm that thrust retards, the main gear touches down, spoilers deploy and autobrake activates. Apply reverse thrust manually where required. Let ROLLOUT track the centreline, then disconnect the automation and take manual control before leaving the runway.
The same intercept, stability and monitoring principles apply across aircraft; our guide to cross-aircraft autoland fundamentals explains those shared requirements without repeating the 747-specific channel logic.
How do you know the 747 is ready to land itself?
The flight-mode annunciator is the deciding reference, not the APP button or the number of illuminated CMD switches. Check it after every capture and again before committing to the automatic landing.
| Indication | What it means | Action |
|---|---|---|
| LOC and G/S with one CMD | Coupled ILS approach; autoland is not confirmed | Expect to disconnect and land manually unless the remaining channels engage |
| LAND 3 | Normal triple-channel autoland status | Continue if the approach is stable and all other conditions are satisfied |
| LAND 2 | Degraded but potentially autoland-capable status | Continue only if permitted by the modelled procedure and selected minima |
| NO AUTOLAND or autopilot disconnect | Automatic landing capability has been lost | Go around, or transition to a manual landing only if stable and appropriate |
A real 747 operation also depends on aircraft certification, runway category, reported visibility, crew qualification and operator approval. A simulator displaying LAND 3 does not by itself reproduce those legal and operational requirements.
Why does Boeing 747 autoland fail in a simulator?
The localiser or glideslope will not capture
Check the ILS frequency, identifier, inbound course and navigation source. If the glideslope is already below the aircraft, do not force a steep descent to catch it; level off, reposition below it and establish another stable intercept.
The extra autopilot channels will not engage
Wait until APP is armed and the required approach modes have captured, then try the remaining CMD channels in the sequence expected by that model. If they still reject, check the flight directors, system failures and add-on documentation. Some basic 747 implementations simply do not simulate triple-channel autoland.
LAND 3 never appears
This usually means the aircraft has only a coupled approach, one channel or sensor is unavailable, or the add-on has simplified autoland logic. Do not assume that three lit CMD buttons guarantee automatic flare and rollout.
The autopilot disconnects near touchdown
Remove duplicate control bindings and add a small dead zone to noisy yoke, joystick, rudder or tiller axes. Also check that no hardware throttle is sending unwanted inputs as the autothrottle retards. A runway localiser offset, excessive crosswind or scenery alignment error can cause a correctly configured aircraft to drift during rollout.
Autoland cannot rescue an unstable approach. If the 747 is too high, too fast, badly configured or missing the required mode annunciations, the correct response is a go-around and another properly established ILS approach.