How do I fly a GPS (RNAV) approach in Microsoft Flight Simulator?

To fly a GPS (RNAV) approach in Microsoft Flight Simulator, load and verify the exact procedure in the aircraft’s GPS or FMS, keep the navigation source on GPS/FMS, use NAV or LNAV for lateral tracking, and arm approach mode only when the selected minima and avionics provide vertical guidance.

What does GPS mean on an RNAV approach in Microsoft Flight Simulator?

A GPS approach in Microsoft Flight Simulator normally means a published RNAV (GPS) procedure flown through the aircraft’s GPS or flight management system. RNAV describes the procedure; GPS or GNSS is the navigation sensor used to follow it.

Unlike an ILS, an RNAV approach does not use a ground-based localiser and glideslope. The navigation source therefore remains GPS or FMS, not VLOC, and the final course may be offset from the runway centreline. Some RNAV procedures provide only lateral guidance, while others include an approved vertical path.

The World Map and flight simulator GPS can load the route, but they are not substitutes for the procedure information. You still need to identify the correct transition, altitude restrictions, missed approach and applicable minima. If the cockpit database and the procedure information disagree, do not combine fixes or altitudes from different versions.

What do LNAV, LNAV/VNAV, LPV and advisory +V mean?

The minima line and the avionics annunciation determine what guidance you have; the words RNAV or GPS alone do not promise an automatic descent.

Garmin-style units usually call RNAV vertical guidance a glide path, often abbreviated GP. An ILS uses a glideslope, abbreviated GS. Those labels are a useful warning that the aircraft is following two different kinds of navigation system.

Why does an LNAV-only RNAV approach stay level?

LNAV supplies lateral guidance only, so the autopilot can follow the magenta course without ever commanding a descent. Pressing APR cannot create a glide path that the procedure and avionics do not provide.

Descend in accordance with the published restrictions and do not go below MDA without the required visual reference. A constant-descent technique may be used, but MDA remains a hard floor and the missed approach point still matters.

Is “LNAV LOG” a recognised approach mode?

No. LNAV LOG is not a standard RNAV minima label or normal autopilot annunciation. Check whether the display actually says LNAV, LNAV+V, L/VNAV, LPV or LOC.

If you meant the MSFS Navlog, that is only the route and waypoint summary. Opening the Navlog does not engage LNAV, activate an approach or confirm that vertical guidance is available.

How do I set up and fly an RNAV approach step by step?

1. Brief the procedure and minima

   Identify the complete approach title, runway, transition or initial approach fix, final approach fix, altitude restrictions, missed approach point and missed approach route. Decide before arrival whether you will use LNAV, LNAV/VNAV, LP or LPV minima.

2. Load the exact approach and transition

   Select the correct runway and procedure in the GPS or FMS. Choose a named transition when joining through an initial approach fix; use vectors-to-final only when you genuinely expect vectors to intercept the final course.

3. Inspect the cockpit flight plan

   Do not assume the World Map imported everything correctly. Check the fix order, active leg and altitude constraints, looking for duplicate waypoints, discontinuities, an unexpected procedure turn or a route back to the wrong transition.

4. Set the navigation source

   In Garmin-equipped aircraft, set the CDI source to GPS, not VLOC. In an airliner, confirm that the active lateral guidance comes from the FMS rather than a radio-navigation source. A mistake we see constantly is switching to VLOC simply because the aircraft is approaching a runway.

5. Activate the correct leg at the correct time

   Loading an approach and activating a leg are not the same action. If you are already sequencing towards the selected transition, the approach may become active normally without another command. Do not press Activate Approach as a ritual: on some units it makes an earlier approach fix active and commands an unwanted turn back.

   When receiving vectors, remain in heading mode until positioned to intercept, then activate or select the appropriate inbound leg. Verify that the desired fix is ahead of the aircraft before accepting the change.

6. Establish lateral guidance

   Use NAV, LNAV or the aircraft’s equivalent FMS mode to capture the programmed track. Monitor the active leg and flight-mode annunciator rather than relying only on the magenta line.

7. Arrive below the vertical path

   Set the correct altimeter pressure, reduce speed and configure the aircraft before the final approach fix. Be at the published intercept altitude and below the glide path; joining high often prevents capture even when APR is armed correctly.

8. Arm the appropriate final approach mode

   For LPV or supported LNAV/VNAV guidance, arm APR, APPR or the aircraft-specific equivalent in time for capture. Confirm that GP or another vertical mode changes from armed to active. On LNAV-only procedures, manage the descent yourself even if the autopilot remains coupled laterally.

9. Observe restrictions and minima

   Cross each fix at the required altitude. At DA, make the continue-or-go-around decision without levelling off. On an MDA procedure, do not descend below MDA until the required visual reference exists and the aircraft is in a suitable position to land.

10. Fly the missed approach when required

    Apply go-around power, establish the climb and follow the published missed route. Check that the GPS or FMS has sequenced beyond the missed approach point; Garmin units may suspend automatic sequencing at the MAP until SUSP is cancelled. Our explanation of the wider IFR sequence from approach clearance through the missed approach covers the surrounding workload.

Should I use NAV or APR mode for a GPS approach?

Use NAV or LNAV to follow the programmed lateral route; use APR or the aircraft-specific approach mode when required to capture final approach guidance. APR is not a navigation-source selector and does not authorise a descent by itself.

• LNAV or LP: use the supported lateral mode and manage the vertical profile manually. Some autopilots permit APR for tighter lateral tracking, but no vertical mode should appear.
• LNAV+V or LP+V: the displayed vertical path is advisory. Continue to use the published non-vertical minima and restrictions.
• LNAV/VNAV or LPV: arm the appropriate approach mode and confirm that both lateral and vertical modes capture.
• Airliner FMS: use the aircraft’s managed lateral and vertical modes rather than assuming the Garmin NAV-plus-APR workflow applies.

The flight-mode annunciator is the final authority. If it still shows ALT, VS or another vertical mode instead of an armed or captured glide-path mode, the aircraft will not descend with the RNAV path.

Why will the RNAV glide path not capture in MSFS?

A missing RNAV descent is usually caused by the selected minima, navigation source, active leg or intercept geometry rather than an autopilot failure.

• No vertical guidance exists: the loaded procedure offers LNAV or LP only, or the selected avionics do not support its vertically guided minima.
• The display shows +V: this is advisory guidance rather than an LPV or LNAV/VNAV capture. It does not change the published minima.
• The source is VLOC: change it back to GPS or FMS for an RNAV approach.
• The wrong leg is active: activate the inbound leg rather than directing the unit towards an earlier fix.
• The flight plan contains a discontinuity: resolve the route break and verify the next fix before engaging managed navigation.
• The aircraft is above the path: descend to the published intercept altitude without violating restrictions, or go around and reposition. Do not chase a glide path from above.
• APR was armed too late or did not capture: check the mode annunciator instead of assuming that pressing the button changed the active mode.
• The transition is wrong: vectors-to-final and full-procedure transitions produce different leg sequences.
• The navigation data do not match: the World Map, aircraft FMS and procedure information may contain different revisions, particularly in add-on aircraft using their own database.

If the procedure is correct but knobs, procedure pages or navigation fields will not respond, use our checks for G1000 and FMS control problems in MSFS 2024. An unresponsive cursor or incorrect interaction mode can make a normal RNAV setup appear broken.

Should I load the approach on the World Map or in the cockpit?

The World Map is convenient for broad route planning, but the cockpit GPS or FMS must be treated as the working flight plan. We recommend checking every approach leg after loading into the aircraft, even when the World Map already shows the correct runway.

Some aircraft import the complete plan, while more detailed add-ons may rebuild it through their own FMS. MSFS ATC can also assign another runway without correctly reprogramming the cockpit system. Recheck the approach title, transition, active leg and minima whenever the clearance or runway changes.

Does an RNAV approach work like an ILS?

No. An ILS uses a tuned localiser and glideslope with the navigation source on VLOC or an equivalent radio source; an RNAV approach uses GPS/FMS guidance and may not include a vertical path at all.

LPV can look similar on the instruments, but it does not turn the aircraft into an autoland system. Minima, equipment requirements and mode annunciations remain different. For a direct comparison, our ILS setup and capture guide for MSFS 2024 explains the radio tuning, source change and glideslope workflow.

Do RNAV approaches work the same in Garmin units and airliners?

No. The procedure principles stay the same, but the controls, annunciations and vertical-mode logic depend more on the installed avionics than on the Microsoft Flight Simulator generation.

• Garmin-equipped general aviation aircraft: keep the CDI on GPS, use NAV for the route and arm APR when supported vertical guidance is available.
• Older or simpler GPS units: expect reliable lateral guidance first. Any displayed vertical path may be advisory rather than capturable.
• Airliners and detailed add-ons: load the procedure through the FMS and use that aircraft’s managed modes. Do not copy Garmin button sequences into an airliner cockpit.

An approach labelled RNP adds navigation-performance monitoring and may require different aircraft capabilities or mode logic. Our guide to the extra containment and system requirements of RNP approaches explains where they differ from a basic RNAV workflow.