Fly an ILS with a Garmin GNS 430: load the approach, identify the localiser, switch GPS to VLOC, capture and fly the missed approach.
To fly an ILS with a Garmin GNS 430, load the published approach, tune and identify the localiser, fly the transition in GPS mode, then select VLOC before intercepting the final course. Capture the localiser and glideslope from below, follow them to decision altitude, and execute the published missed approach if required.
What does the GNS 430 do during an ILS approach?
The GNS 430 performs two separate jobs: GPS guides you around the initial approach, while its VLOC receiver supplies the localiser and glideslope signals for the final approach. The ILS itself remains a ground-based procedure; GPS guidance does not replace the localiser or glideslope.
Pressing the unit's CDI key changes the navigation source between GPS and VLOC. Confirm the displayed annunciation rather than assuming the change occurred. Our explanation of GPS versus VLOC guidance during an ILS covers this distinction in more detail.
The GNS 430 and WAAS-capable GNS 430W use broadly the same ILS workflow, but automatic frequency loading, automatic GPS-to-VLOC switching and autopilot coupling depend on the aircraft installation. Treat automatic source switching as assistance, not something to trust without checking.
How do you set up and fly the Garmin GNS 430 ILS approach?
Brief the published approach. Record the localiser frequency and identifier, inbound course, initial and final approach fixes, glideslope intercept altitude, decision altitude, missed-approach point and missed procedure. Check whether the approach requires DME or another navigation aid.
Load the ILS procedure. Press
PROC, choose the required approach and select the transition matching your clearance. Choose Load while still en route; activate the approach when cleared to join it. Loading inserts the procedure without immediately redirecting the aircraft.Use vectors-to-final only when ATC is genuinely vectoring you onto final. Activating it too early can remove useful intermediate legs from active sequencing and leave you without the expected route to the final approach fix.
Tune and identify the localiser. Loading or activating the approach may place the ILS frequency in the standby VLOC field, depending on the installation. Verify it against the chart, transfer it to active and identify the station. Set the published front course on the external CDI or HSI. These ILS frequency and identifier checks help prevent capturing the wrong localiser.
Fly the transition using GPS. Confirm
GPSis annunciated and follow the loaded legs towards the final approach. Observe any published altitude, speed and course restrictions; loading the procedure does not make those restrictions automatic.Approach the localiser from below the glideslope. Establish the published intercept altitude and use a sensible intercept angle, normally no more than about 30 degrees unless the procedure or controller requires otherwise. Reduce speed and configure the aircraft early enough that you are not chasing both needles while making major configuration changes.
Switch from GPS to VLOC. Press
CDIbefore localiser capture and confirmVLOCappears. Some installations switch automatically near the final approach course, but we still verify the source. If GPS remains selected, the CDI follows the magenta GPS course rather than the live localiser.Capture the localiser and glideslope. Hand-fly the CDI and glideslope indications, or arm the autopilot's approach mode while established on a suitable intercept. The
APRcontrol belongs to the autopilot, not the GNS 430. Autopilot procedures vary by aircraft, so use the aircraft documentation alongside the complete ILS interception and approach-mode workflow.Descend only after a valid glideslope capture. Maintain the localiser and glideslope, cross-check published altitudes and set the correct altimeter minimums. Intercept the glideslope from below; attempting to capture from above can produce an unstable descent and may expose you to false glideslope lobes.
Decide at the published minimum. Continue only when the required visual references are available and the aircraft is in a position to land normally. Otherwise, begin the missed approach immediately.
When should you switch from GPS to VLOC?
Switch to VLOC before the localiser must be captured, while the aircraft is stable and there is time to confirm the indication.
| Approach phase | Normal source | What to verify |
|---|---|---|
| En route and initial approach | GPS | Loaded legs, waypoint sequencing and altitude restrictions |
| Localiser intercept and final | VLOC | Correct frequency, identifier, front course and live localiser indication |
| Missed approach | As published | GPS or required ground-based navigation source, plus correct sequencing |
Do not switch so early that you lose useful GPS guidance to the intercept, but do not wait until the localiser needle is already sweeping rapidly across the display. A late source change is one of the most common reasons an otherwise well-planned simulator approach passes through the localiser.
Why will the localiser or glideslope not capture?
A failed capture usually comes from the wrong navigation source, frequency, geometry or autopilot mode rather than a fault in the GNS 430.
- GPS is still selected: press
CDIand confirm VLOC is annunciated. - The frequency is only in standby: transfer it to the active VLOC field and identify the station.
- The wrong runway or reciprocal localiser is tuned: compare the frequency, identifier and inbound course with the chart.
- You are above the glideslope: descend only as authorised, re-establish below it if practical, or discontinue the approach. Do not force a steep capture from above.
- The procedure is localiser-only: a LOC approach has no usable glideslope even if it shares equipment with an ILS.
- The autopilot is in NAV rather than APR: many autopilots require approach mode to capture both localiser and glideslope.
- Navigation data and scenery disagree: simulator airport layouts, radio frequencies and the GNS database can represent different revisions. Verify the actual signal and use matching procedure data where possible.
How do you fly the missed approach with a GNS 430?
Fly the aircraft first, follow the published missed-approach instructions, then configure the GNS 430 for the required navigation source and sequencing.
Apply power, establish the specified climb and manage the aircraft configuration. If the missed procedure uses GPS guidance, select GPS and confirm the annunciation. At the missed-approach point the GNS 430 commonly suspends automatic waypoint sequencing and displays SUSP; press the OBS key to resume sequencing when appropriate for the published procedure.
If you go around before reaching the missed-approach point, do not begin an early turn unless the procedure or ATC authorises it. Continue to the point from which the missed instructions apply while respecting obstacle-clearance requirements. The autopilot will not necessarily transition from ILS approach mode into the missed procedure automatically.
For simulator practice, rehearse loading, activating, switching CDI sources and releasing suspended sequencing separately before combining them in poor visibility. Our structured GNS 430 practice guidance covers those button-level exercises and database-related differences.