Fix MSFS 2024 approach mode when it will not capture the localiser, glideslope or RNAV path. Check the procedure, nav source, tuning and intercept.
Approach mode in Microsoft Flight Simulator 2024 usually stays armed because the aircraft has no valid approach guidance to capture. Load and activate the correct procedure, select the right navigation source, tune and identify the ILS when required, intercept the final course at a shallow angle, and meet the vertical path from below.
What does the APR button actually do?
APR arms the autopilot or flight director to capture available lateral and vertical approach guidance; it does not create that guidance. For an ILS, this normally means the localiser followed by the glideslope. On a compatible RNAV approach, it may capture GPS lateral guidance and a glidepath.
An illuminated APR button only confirms that the mode was selected. Check the flight mode annunciator on the primary flight display: armed modes and captured modes are shown differently, although the colours and labels vary by aircraft. Labels such as LOC, GS or GP must become active before the aircraft will follow them.
How do I make approach mode capture in MSFS 2024?
- Confirm the approach is in the cockpit flight plan. Loading a route in the world map or EFB does not guarantee that every aircraft has imported and activated it. The approach must be sequencing naturally towards its final legs, or vectors-to-final must be selected if that is how you are joining it.
- Identify the approach type. An ILS supplies a localiser and glideslope, a localiser-only approach has no glideslope, and an RNAV approach may or may not provide supported vertical guidance.
- Verify ILS tuning. Select the published ILS frequency and front course where the aircraft requires them, then check the displayed station identifier and runway. Many airliners tune automatically, but the result still needs checking. Our complete ILS setup and capture sequence covers this process in more detail.
- Select the correct navigation source. Conventional ILS guidance normally requires
VLOC,LOCor the aircraft's radio-navigation source. RNAV approaches useGPSorFMS. The exact controls differ between Garmin-equipped aircraft and airliners; this explanation of NAV, GPS and VLOC guidance shows which source to choose. - Create a sensible intercept. Join the final course from outside the final approach fix, on a converging heading and at the cleared or published altitude. Roughly 30 degrees or less is a reliable localiser intercept target, though individual autopilots have their own limits.
- Approach the vertical path from below. Level at the published intercept altitude and let the glideslope or glidepath descend towards the aircraft. Trying to capture from above is one of the most common reasons APR remains armed.
- Arm APR before crossing the beam. Watch the flight mode annunciator rather than repeatedly pressing the button. Pressing APR again may cancel the armed mode just as capture becomes possible.
Why does APR stay armed instead of capturing?
APR stays armed when the receiver can see no valid signal or the aircraft has not met the autopilot's capture conditions.
| What you see | Likely cause | What to change |
|---|---|---|
| APR armed but no turn towards final | Wrong frequency, navigation source or active flight-plan leg | Verify the approach, station identifier and GPS/VLOC selection |
| Localiser captures but glideslope remains armed | Aircraft is above the glideslope or the approach has no vertical signal | Re-intercept from below and confirm it is a full ILS |
| Aircraft follows the magenta line but will not descend | RNAV vertical guidance is absent, unsupported or not active | Check the approach minima and look for an active GP or VNAV mode |
| Aircraft turns away after capture | Wrong runway, reciprocal course, route discontinuity or bad intercept | Recheck the procedure and rebuild the final approach legs if necessary |
| APR will not arm or the autopilot drops out | Avionics state, control input, conflicting binding or aircraft limitation | Stabilise the aircraft, release manual inputs and inspect duplicate bindings |
Why does the localiser capture but not the glideslope?
The localiser can capture without the glideslope when the aircraft reaches lateral guidance first but is above, beyond or not receiving the vertical beam. Remaining in altitude hold while GS is merely armed is normal; descent begins only after vertical capture.
Do not dive to chase a glideslope from above. Go around or reposition below it. Also confirm that the selected procedure is not LOC-only or back-course guidance, neither of which provides a normal glideslope. If using an add-on airport, a scenery or navigation-data mismatch can also associate the wrong ILS with the runway.
Does approach mode work on RNAV approaches?
Approach mode works on an RNAV procedure only when that aircraft's avionics support the published lateral and vertical guidance.
- LPV or supported LNAV/VNAV: compatible avionics can normally provide lateral guidance and a glidepath, often shown as
GPrather than the ILS labelGS. - LNAV-only: the autopilot may follow the lateral path, but the pilot must manage descent using published altitudes and an appropriate vertical mode.
- Airliners: some use APP only for ILS operations and use LNAV/VNAV or managed modes for RNAV approaches. Follow the aircraft's flight mode annunciations rather than applying Garmin procedures to every cockpit.
Make sure the final approach leg is active and the source remains GPS or FMS. Switching to VLOC for an RNAV approach removes the guidance the autopilot needs.
Will APR mode land the aircraft automatically?
APR mode is not the same as autoland. It can track an approach towards the runway, but automatic landing requires a suitably equipped aircraft, a supported approach, correct autopilot configuration and aircraft-specific procedures. Our guide to autopilot modes and their limits explains where approach tracking ends and autoland begins.
How can I tell whether this is a setup error or an MSFS bug?
A failure limited to one aircraft or one approach usually points to configuration, avionics modelling or navigation data rather than the core simulator.
- Test a default aircraft on a known full ILS, starting well outside final and below the glideslope.
- Disable AI piloting and assistance features that can alter heading, altitude or throttle.
- Check for duplicate pitch, trim, autopilot-disconnect or mode bindings across every connected controller.
- If one airport is affected, retest without custom airport scenery. A misplaced localiser or mismatched runway record can prevent correct capture.
- If every autopilot mode misbehaves, use our broader MSFS 2024 autopilot fault checklist rather than treating it as an approach-only problem.