Learn how Boeing 777 autoland uses ILS, LAND 3 or LAND 2, flare and rollout, with simulator setup steps and fixes for failed captures.
In a Boeing 777 flight simulator, autoland uses the ILS and multiple autopilot channels to capture the localiser and glideslope, then command runway alignment, flare, touchdown and rollout. It works only when the aircraft add-on models these functions, the runway supplies valid ILS guidance, and the approach is configured correctly.
Within our Aviation & Real-World Flying guidance, we use autoland narrowly. Following an ILS with one autopilot engaged is an automatic approach, but it is not necessarily an automatic landing. Our explanation of what separates an autopilot approach from a true autoland covers that distinction in more detail.
What does the Boeing 777 autoland system do?
The 777 Automatic Flight Director System combines ILS signals, radio-altimeter data, autothrottle and redundant flight-control computers to guide the aircraft through the final approach and landing. The localiser provides lateral guidance, while the glideslope supplies vertical guidance.
In real 777 logic and detailed simulations, selecting APP arms the approach modes and the additional autopilot channels needed for autoland. Once the required signals and channels are available, the system prepares FLARE and ROLLOUT. Simplified add-ons may reproduce only part of this sequence or merely display similar annunciations.
| Approach phase | Typical indication | What the system is doing |
|---|---|---|
| ILS intercept | LOC and G/S armed or captured | Tracking the runway centreline and descent path |
| Autoland validation | LAND 3 or LAND 2 | Checking autopilot, receiver and sensor redundancy |
| Final seconds | FLARE active | Reducing the descent rate and commanding the landing attitude |
| After touchdown | ROLLOUT active | Holding the runway centreline through rudder and steering commands, as modelled |
The autothrottle controls approach speed and normally retards thrust during the flare. Autobrakes, spoilers and reverse thrust remain separate systems: they must be configured correctly, and reverse thrust is normally selected by the pilot.
How do you set up a 777 autoland in a simulator?
- Confirm the aircraft can autoland. A basic freeware or default-style 777 may track an ILS without modelling triple-channel logic, FLARE or ROLLOUT. Use the aircraft documentation and its flight-mode annunciator rather than assuming every working cockpit switch is functional.
- Select a runway with a usable ILS. Check the frequency, identifier and inbound course for the correct runway end. A localiser-only approach has no glideslope and cannot provide a normal ILS autoland.
- Programme and configure the approach. Load the arrival and approach where supported, set the landing reference speed, and choose Flaps 25 or 30 as appropriate. Our 777 landing-flap comparison explains how that choice affects speed and handling.
- Verify the ILS rather than trusting the FMC. Detailed 777 simulations may autotune the ILS, while simpler models require manual tuning. Confirm that localiser and glideslope indications appear and that the displayed identifier matches the intended runway.
- Intercept from below. Establish the aircraft on a shallow intercept, normally within about 30 degrees of the localiser, and below the glideslope. Selecting APP while high, close to the runway or crossing at a steep angle is a common reason for failed capture.
- Select APP and monitor the FMA. Confirm LOC and G/S capture. In accurately modelled 777 logic, the remaining autopilot channels arm and engage automatically when the required approach conditions are met; do not import a Boeing 737 procedure unless the particular add-on requires it.
- Check the autoland status. Before continuing into the flare, expect LAND 3 or an acceptable LAND 2 indication, together with FLARE and ROLLOUT armed. If the display says NO AUTOLAND or the modes are missing, disconnect or go around rather than waiting to see what happens.
- Leave the controls undisturbed. Keep hands and feet ready, but avoid moving a noisy joystick or rudder axis. After touchdown, verify spoiler deployment and braking, apply reverse thrust if required, then take manual control before leaving the runway.
For the broader sequence, including stabilised-approach checks and go-around decisions, use our general simulator autoland procedure.
What do LAND 3 and LAND 2 mean?
LAND 3 and LAND 2 describe the available autoland redundancy; they are not runway approach categories.
- LAND 3 indicates three-channel, fail-operational capability. A relevant single failure should still leave the system able to complete the automatic landing.
- LAND 2 indicates reduced redundancy and is generally fail-passive. Following a failure, the automatic control should disengage without a major deviation, but the pilot may have to take over or go around.
- NO AUTOLAND means the required redundancy or sensor status is unavailable. Do not rely on automatic flare and rollout.
In real operations, autoland approval also depends on the aircraft, operator, crew, runway equipment, ILS protection and weather. A successful landing in a home simulator does not prove that the same approach would be authorised operationally.
Why does 777 autoland fail in a flight simulator?
Most failed simulator autolands come from incorrect ILS setup, an unstable intercept or incomplete aircraft-system modelling rather than an autopilot defect.
- Localiser captures but glideslope does not: the aircraft was probably above the glideslope, the wrong frequency was tuned, or APP was selected too late. Reposition below the path and make a shallower intercept.
- The aircraft follows the ILS but never shows LAND 3 or LAND 2: the add-on may model only a single-channel approach, or one of the required channels has not become available.
- FLARE does not arm: check that both LOC and G/S are captured, the radio altimeter is functioning, autopilot and autothrottle remain engaged, and failures have not been enabled.
- The autopilot disconnects near touchdown: control-axis noise, manual trim input or accidental yoke movement may be overriding it. Add a small dead zone and avoid touching the controls until intervention is necessary.
- The aircraft lands beside or short of the runway: scenery and navigation data may place the ILS or threshold incorrectly. Confirm that the visual runway, ILS data and selected runway all agree.
- Touchdown is acceptable but rollout is poor: ROLLOUT may not be modelled, the crosswind may exceed the add-on's capability, or rudder and steering axes may be conflicting with the autopilot.
Does 777 autoland stop the aircraft automatically?
Autoland can steer the aircraft through touchdown and rollout, but it does not automatically complete every stopping action. Arm the speedbrake, select an appropriate autobrake setting and be ready to apply reverse thrust manually.
ROLLOUT is centreline guidance, not a taxi mode. Once the aircraft has slowed sufficiently and control is stable, disconnect the autopilot as required by the simulated aircraft's procedure and taxi manually.