Flying the RNAV GPS RWY Eighteen Approach at KGPT: An LPV Walkthrough

LPV (Localizer Performance with Vertical guidance) approaches give WAAS-equipped general aviation aircraft decision altitudes as low as 200 feet above the touchdown zone and visibility requirements as low as a quarter mile - minimums that rival a Category One ILS. The RNAV GPS Runway 18 approach at Gulfport-Biloxi International (KGPT) is a practical example of what this technology delivers and what it demands from the pilot flying it.

What Are the Different RNAV Approach Types and What Do the Minimums Mean?

Pull up any RNAV GPS approach plate and you will typically see several rows of minimums. They sound similar, but each represents a fundamentally different approach with different avionics requirements.

LNAV (Lateral Navigation) is the baseline GPS approach. It provides lateral guidance only, flown to a minimum descent altitude - not a decision altitude. You level off at the MDA, look for the runway, and go around if you have not identified it by the missed approach point. Expect minimums in the 400 to 600 foot range or higher.

LNAV/VNAV adds a vertical component to the lateral track, requiring either WAAS or a barometric vertical navigation system. The glidepath is advisory. Minimums are lower than pure LNAV, but not as low as a precision-equivalent approach.

LP (Localizer Performance) approaches are relatively rare. They use WAAS for tighter lateral accuracy without vertical guidance and tend to appear in terrain environments where a safe glidepath cannot be established.

LPV is the highest tier. With a WAAS-certified GPS receiver, an LPV approach delivers both lateral and vertical guidance precise enough to support decision altitudes as low as 200 feet above the touchdown zone. An ILS requires expensive ground equipment and dedicated airport infrastructure. An LPV approach requires a certified receiver in the aircraft and a precise satellite signal - the infrastructure lives in space. For general aviation, that distinction is transformative.

What Equipment Does Your Aircraft Need to Fly LPV Approaches?

The single most important requirement is a WAAS GPS receiver certified for LPV approaches. WAAS is the FAA’s ground-based augmentation network that corrects satellite positioning errors in real time. Without WAAS certification, you are flying LNAV at best, regardless of what the plate offers.

This distinction trips up pilots more often than it should. Many GPS navigators in older aircraft are not WAAS capable. The Garmin GNS 430, for example, exists in both WAAS and non-WAAS versions that look nearly identical in the cockpit. A non-WAAS 430 cannot fly LPV minimums - the navigator will not display an LPV glidepath.

Check your avionics documentation and pilot operating handbook supplements. If the aircraft logbooks reflect a supplemental type certificate for a WAAS navigator, you are likely cleared. If there is any doubt, confirm with your avionics shop before flying into IMC.

The second requirement is a current navigation database. WAAS approaches require current nav data. An expired database means the approach is not legal to fly to published LPV minimums, and some navigators will not display the correct minimums at all.

How Do You Brief the RNAV GPS Runway 18 Approach at KGPT?

Gulfport-Biloxi International (KGPT) sits on the Mississippi Gulf Coast. Runway 18 runs south toward the Gulf of Mexico. Coastal fog, low ceilings, and rapid IMC transitions are a real factor in that environment - the difference between LNAV and LPV minimums can be the difference between getting in and diverting two hours away.

Brief from the top of the plate. Approach name, airport, runway. Then communication frequencies - Gulfport Approach, tower, ground - and know when handoffs happen.

Move to the plan view. Trace your route from where you will enter the system. Runway 18 is a heading of 180 degrees, southbound. Identify initial approach fixes, the final approach course, and your transition route. If you are arriving with approach control in radar contact, expect vectors to final. If self-navigating, know your intercept point and sequencing before you need them.

What Are the Key Technique Points on the Glidepath?

Cross the final approach fix on glidepath. Arriving above it means you have altitude to make up and you are already behind. Know the fix name, its distance from the runway threshold, and the crossing altitude before you get there.

On a standard three-degree glidepath - which most LPV approaches use - you descend approximately 300 feet per nautical mile. At 90 knots groundspeed, that translates to roughly 500 feet per minute. Know your numbers before the final approach fix. Math in the clouds costs attention you do not have.

Your WAAS navigator will present lateral and vertical deviation exactly like an ILS needle display on a modern glass panel. Center the needles and keep them centered. The WAAS glidepath sensitivity increases as you approach the runway - a deviation that seems small five miles out becomes a significant one near the threshold. Catch movements early with small corrections. Do not chase the needles.

Be fully configured before the final approach fix - gear down, flaps set, approach speed stabilized, checklist complete. At a decision altitude of 250 feet, being behind the aircraft is not a recoverable position.

Cross-check your altimeter against the profile view crossing altitudes at published fixes. If your glidepath indicates 1,000 feet at a given fix and your altimeter reads 800, something is wrong - most commonly an altimeter setting error. Always set the current altimeter when you receive ATIS or when approach control issues an update. An incorrect setting can place you below the published glidepath with no obvious indication.

What Happens at Decision Altitude?

At the published decision altitude, one question must be answered: do you have the required visual references?

The regulation is specific. Required references include the approach light system, threshold or threshold markings or lights, runway end identifier lights, the runway itself, runway markings or lights, or a touchdown zone and its markings or lights. A vague glow in the murk does not qualify. If you have the required references and can make a normal landing from your current position and attitude, continue. If you do not, execute the missed approach - immediately.

Decision altitude is not a suggestion. Below minimums without required references is where accident reports begin.

What Mistakes Specifically Trip Pilots Up on LPV Approaches?

Database expiration. If the navigator’s database is expired, the approach cannot legally be flown to LPV minimums. Some navigators will still display the approach with elevated minimums or reduced authorization. Check database currency before the flight, not at the final approach fix.

Missing the LPV annunciation. Before crossing the final approach fix, confirm the navigator shows LPV active - not LNAV, not ARM, not GPS. If you do not see LPV, do not descend to LPV minimums. Continuing below LNAV minimums on the assumption that LPV is active is how pilots encounter terrain they believed was below them.

Altimeter setting errors. An incorrect altimeter can place you below the published glidepath while the deviation needle shows centered. Set the current altimeter at every opportunity and cross-check against published crossing altitudes at named fixes.

Late configuration. Get stable early. If you are still configuring past the final approach fix, the approach is not going well. Execute the missed approach, get established, and fly a second approach from a configured, briefed position.

Skipping the missed approach brief. Brief the missed approach as part of the full approach brief - every time, on every approach. Know the climb heading, target altitude, fix, and hold instructions before you need them. Expecting to land is not the same as planning for every outcome.

Key Takeaways

• LPV approaches deliver Category One ILS-equivalent minimums - decision altitudes as low as 200 feet above the touchdown zone and quarter-mile visibility - to any airport served by a WAAS signal, without requiring ground-based ILS infrastructure.
• A WAAS-certified GPS receiver is required. Many navigators in older aircraft, including some Garmin GNS 430 units, are non-WAAS and cannot fly LPV minimums regardless of what the plate shows.
• Before the final approach fix, the navigator must annunciate LPV - not LNAV, not ARM. If it does not, do not fly to LPV minimums.
• A current navigation database is legally required. Verify before every flight.
• At decision altitude: if required visual references are present and a normal landing is possible, continue. If not, execute the missed approach immediately. There is no third option.