Microsoft Flight Simulator Updated Sat, 18 Jul 2026 23:32:02 GMT 6 min read

How do I use the Garmin GNS 530 in MSFS 2020?

Learn to use the Garmin GNS 530 in MSFS 2020: enter routes, fly direct-to, couple the autopilot, load approaches and fix common errors.

By Ian StephensEditor-in-Chief

To use the Garmin GNS 530 in Microsoft Flight Simulator 2020, enter or activate a flight plan, keep the CDI source on GPS for en-route navigation, and select NAV on the autopilot if desired. For an ILS, load the approach, tune the localiser, then switch the CDI to VLOC before capture.

The GNS 530 is controlled mainly through its two concentric right-hand knobs rather than a touchscreen. Aircraft may use the standard MSFS implementation or custom avionics, so details such as automatic frequency tuning, VNAV and autopilot coupling can vary.

What do the GNS 530 buttons and knobs do?

The right-hand knobs select pages, move the cursor and enter waypoint identifiers; most difficulty comes from confusing the inner and outer knobs.

Control	Purpose
Large right knob	Changes page groups when the cursor is off; moves between fields or character positions when the cursor is on.
Small right knob	Changes pages within a group; changes the selected letter, number or field value. Push it to turn the cursor on or off.
Left knobs and transfer buttons	Tune COM or VLOC standby frequencies and swap them into the active frequency window.
`FPL`	Opens the active flight plan and stored flight-plan pages.
`PROC`	Loads or activates departures, arrivals and approaches supported by the installation.
Direct-to key	Creates a direct course to one selected waypoint.
`CDI`	Changes the navigation source between `GPS` and `VLOC`.
`OBS`	Enables OBS course selection or releases suspended GPS waypoint sequencing when appropriate.
`ENT` and `CLR`	Confirm an entry or cancel/go back. Holding `CLR` generally returns to the default navigation page.
`RNG`	Changes the map range.

Our illustrated GNS 530 and GNS 430 control tutorial provides another view of the faceplate, maps, knobs and waypoint workflow.

How do I enter a route in the GNS 530?

You can follow a route imported from the MSFS World Map, build one manually on the flight-plan page, or use direct-to for a single waypoint.

Fly direct to one waypoint

Press the direct-to key. The waypoint identifier field should become active.
Enter the identifier. Turn the small right knob to change a character and the large right knob to move to the next position.
Check the result. Confirm that the displayed airport or waypoint has the correct name and location, especially where identifiers are similar.
Press ENT twice. The first press confirms the waypoint; the second activates the direct-to course.
Verify the active leg. A magenta course should appear on the navigation map, with the CDI source showing GPS.

Direct-to bypasses intermediate flight-plan waypoints. A mistake we see constantly is pressing direct-to for the final destination and then wondering why the aircraft ignores the programmed route.

Build or check a flight plan

Press FPL. A route created on the World Map should already appear as the active flight plan.
Push the small right knob to activate the cursor, then use the large knob to highlight an empty line or the required insertion point.
Enter each waypoint. Use the small knob for characters, the large knob to move between positions, and ENT to confirm.
Check the active leg. The leg the navigator is steering towards should be magenta. If necessary, highlight the intended leg and use the page menu’s activate-leg command.

Verify every imported route before departure. The World Map can produce an unexpected transition or duplicate waypoint when a procedure is changed. Edits made only inside the GNS may also leave the built-in ATC system following its original plan.

How do I make the autopilot follow the GNS 530?

The GNS 530 supplies navigation guidance, but the aircraft’s autopilot must be configured to follow it.

Activate the required flight-plan leg and confirm that it is shown in magenta.
Set the CDI source to GPS. If it says VLOC, press CDI.
Intercept the course sensibly. Use heading mode to turn towards the magenta line rather than expecting NAV mode to recover from any position or angle.
Arm or select NAV mode on the aircraft’s autopilot. It should capture and track the GPS course once interception criteria are met.
Manage altitude separately. The GNS route does not automatically control altitude, throttle or descent. Use the aircraft’s altitude, vertical-speed or flight-level-change controls as appropriate.

In a cockpit with two navigators, confirm which unit is connected to the autopilot or selected navigation source. Many installations follow the upper or number-one unit, but third-party aircraft can be wired differently.

How do I load an RNAV or ILS approach?

Press PROC, select the approach and transition, choose Load or Activate, then use the correct CDI source for the final approach type.

Make the airport your flight-plan destination before opening the procedures page.
Press PROC and choose Select Approach. Select the required runway procedure and verify that it matches the clearance.
Choose the transition carefully. Select a named initial approach fix when flying the full procedure. Select vectors-to-final only when ATC is actually providing vectors.
Choose Load or Activate. Load inserts the procedure without immediately abandoning the present route. Activate makes the approach guidance active, so use it only when ready to join.
Confirm the first active leg rather than assuming the unit selected the point you intended.
Select the correct CDI source and use NAV or APR mode as supported by the aircraft.

Approach	CDI source	Typical autopilot mode	Final guidance
RNAV/GPS	`GPS`	NAV en route; APR when supported	GPS lateral guidance, with vertical guidance only when the procedure and installation provide it
ILS	`VLOC`	APR	Tuned localiser and glideslope radio signals
VOR	`VLOC`	NAV	Tuned VOR radial

For an RNAV approach, keep the CDI on GPS and check the displayed approach annunciation rather than assuming vertical guidance is available. Our step-by-step RNAV approach explanation covers loading, source selection and approach capture in more detail.

For an ILS, the GNS can provide procedure sequencing, but the final course and glideslope come from the radio receiver. Verify the localiser frequency, identify it where modelled, and switch to VLOC before interception; some installations switch automatically, but we would not rely on that. See our practical MSFS ILS guide for the complete interception and landing sequence.

Common GNS 530 problems and fixes

The autopilot will not follow the magenta line: confirm an active magenta leg, select GPS rather than VLOC, establish an intercept heading and then arm NAV.
The route will not advance: look for OBS or SUSP. Press OBS only when it is appropriate to resume automatic sequencing. At the missed-approach point, suspension is intentional; begin the go-around before sequencing the missed approach.
The approach turns towards the wrong waypoint: the wrong transition was probably selected, or vectors-to-final was activated without vectors. Reload the approach using the correct initial fix.
The knob changes pages instead of entering text: push the small right knob to activate the cursor, position it with the large knob, then use the small knob to change the value.
A frequency is tuned but the CDI still follows GPS: tuning a VOR or localiser does not select it as the navigation source. Press CDI and verify VLOC.
The screen is blank: check the battery, avionics master, electrical bus and the unit’s power or brightness control.
The controls behave differently from these steps: the aircraft may use custom avionics rather than the standard MSFS GNS implementation. Check its cockpit tooltips and documentation, particularly for source selection and autopilot coupling.