Learn when to use autopilot on approach, when to disconnect, how APP mode captures guidance, and why it does not automatically land the aircraft.
Use autopilot on approach when it reduces workload and the aircraft can couple to the selected procedure, but do not treat it as mandatory or as an automatic landing system. Monitor every mode change, remain ready to disconnect, and hand-fly if the guidance, configuration or approach becomes unstable.
In our Aviation & Real-World Flying guidance, we treat autopilot as a workload-management tool, not a replacement for understanding the approach. If the basic controls are unfamiliar, begin with our explanation of heading, altitude, navigation and vertical autopilot modes.
When should you use autopilot on approach?
Use it for a coupled instrument approach, high workload or poor visibility; hand-fly when practising manual skills or when the automation is not behaving as expected.
| Situation | Sensible choice | Reason |
|---|---|---|
| ILS or supported RNAV approach in poor visibility | Keep the autopilot engaged | Accurate tracking reduces workload, provided every mode is verified. |
| Visual approach in good conditions | Either method | The autopilot can position the aircraft, then you can disconnect once established. Our visual approach technique guide covers the manual phase. |
| Manual-flying practice | Disconnect early | This gives time to settle into the aircraft rather than taking control close to the runway. |
| Wrong mode, bad capture or unstable approach | Disconnect or go around | Automation should not be allowed to continue an unsafe flight path. |
| Supported autoland | Remain coupled | Only when the aircraft, approach, simulator model and required system configuration all support it. |
There is no universal altitude at which every pilot should disconnect. Airliner procedures may keep the autopilot engaged until late in the approach, while light-aircraft pilots often disconnect earlier. Follow the modelled aircraft's checklist and any stated autopilot minimum-use height.
How do you use autopilot correctly during an approach?
Set up and monitor the approach exactly as you would when hand-flying; the autopilot merely moves the controls in response to the selected modes.
- Brief the approach. Confirm the procedure, minimum altitude, missed approach, expected runway and the aircraft's autopilot limitations.
- Load and verify the procedure. Check the active approach, transition, waypoints and navigation source instead of assuming the flight plan imported correctly.
- Prepare the guidance. For an ILS, tune and identify the frequency and set the front course where the aircraft requires it. For an RNAV approach, verify the correct active leg and GPS or FMS source. Our complete ILS setup and flying procedure explains the radio and interception sequence.
- Intercept from a sensible position. Join at an appropriate angle and altitude. An ILS glideslope should normally be intercepted from below rather than chased from above.
- Arm the correct approach mode. APP, APR or an equivalent label arms capture; it does not guarantee immediate tracking. The correct timing is covered in our APP-mode capture and arming guidance.
- Read the flight mode annunciator. Confirm that lateral and vertical guidance have actually captured. A lit button shows what was selected, while the annunciator shows what the aircraft is doing.
- Manage speed and configuration. Extend flaps and landing gear on schedule, set the missed-approach altitude when appropriate, and watch thrust. Autopilot does not necessarily control airspeed or configure the aircraft.
- Choose the landing method. Disconnect in time for a stable manual landing, continue with a properly supported autoland, or go around if the required visual reference or stable flight path is missing.
Why won't the autopilot capture the approach?
Approach capture usually fails because the navigation source, interception geometry or active mode is wrong rather than because the autopilot itself is broken.
- Wrong navigation source: the receiver is displaying GPS guidance when the autopilot needs VLOC or ILS guidance, or the reverse.
- Incorrect frequency or course: the localiser has not been tuned and identified, or the selected course is wrong in an aircraft that requires it.
- Too high or too close: the aircraft reaches the glideslope from above or tries to intercept the localiser at an excessive angle.
- APP armed but not captured: the mode remains waiting for valid guidance. Check the flight mode annunciator rather than the button light.
- Wrong RNAV leg: a route discontinuity, vectors transition or inactive final approach leg prevents the system from following the expected path.
- Unsupported capability: some basic autopilots provide lateral tracking but cannot capture vertical approach guidance. Add-on aircraft also vary in how completely these systems are modelled.
If the instruments track a stable localiser that is visibly offset from the runway, the likely cause is a mismatch between navigation data and the airport scenery. Disconnect and land visually if conditions permit; do not force the aircraft to follow two conflicting references.
Does approach mode land the aircraft?
No: approach mode normally captures lateral and vertical guidance, but it does not automatically provide the flare, touchdown, rollout or thrust control needed for an autoland.
A true autoland requires a suitably equipped aircraft, a compatible approach, the correct autopilot channels and a correctly configured system. Exact requirements differ between aircraft. Autothrottle is also a separate system, so engaging APP mode does not prove that landing speed or thrust will be managed.
When should you disconnect the autopilot?
Disconnect before the aircraft exceeds its published autopilot limitation, or immediately when its commands are unexpected and cannot be corrected safely through normal mode selection.
- The aircraft turns, climbs or descends away from the cleared or intended path.
- The localiser or vertical path is not captured by the expected point.
- Pitch, bank, speed or configuration no longer meets stable-approach criteria.
- You have adequate visual reference and want to complete a manual landing.
- A warning, trim problem or control conflict makes the automation unreliable.
Do not wrestle the controls while leaving the autopilot engaged; it may continue applying trim against your input. Disconnect, acknowledge the warning, stabilise the aircraft and decide whether there is enough height to continue. If there is not, execute the missed approach rather than trying to rescue a poor landing.