Non Precision Approach: A Pilot's Complete Guide

A non-precision approach provides lateral guidance to a runway but lacks the electronic vertical guidance of a precision approach, so you manage your own descent to a Minimum Descent Altitude. Typical system minima reflect that difference, with 250 ft for localizer procedures and 300 ft for VOR and NDB procedures.

You're likely here because you've looked at an approach plate and thought, “I get what an ILS does. But what exactly am I doing on a VOR, LOC, or LNAV approach, and why do some GPS approaches seem to have a glidepath but still get lumped into the non-precision bucket?” That confusion is normal.

A lot of instrument training starts with a clean definition, then reality muddies it. In an actual cockpit, the problem isn't vocabulary. It's workload. You're in cloud, the runway isn't in sight, and nobody is going to descend the airplane for you. You have to know where to descend, when to level, what altitude is sacred, and when to stop trying to salvage the landing and go missed.

That's why a non precision approach still matters, even in a GPS world. If you understand the old-school logic behind MDA, step-down fixes, and the MAP, modern procedures make a lot more sense.

Your First Non Precision Approach Scenario

You're fifty miles out in solid IMC. The ride is fine, the radios are busy, and you've already briefed the ILS. Then Approach tells you the glideslope is unavailable and the only way in is the VOR approach.

Now the whole arrival changes.

Instead of following lateral and vertical guidance down to a decision altitude, you're about to fly an approach where the airplane will only be guided sideways. The descent is now your job. You'll need to identify the final approach fix, respect every step-down altitude, level at MDA if required, and know exactly where the missed approach point is. If you get loose on any of that, the approach gets unstable fast.

That's the heart of a non precision approach. It gives you course guidance but not electronic vertical guidance. SKYbrary describes it as an approach where the pilot manages descent with the MDA, step-down fixes, timing, DME, or distance-to-fix information rather than following a glidepath, which makes altitude discipline the main safety constraint (SKYbrary on non-precision approach fundamentals).

What changes in the cockpit

On an ILS, the scan often narrows around keeping needles centered and energy under control. On an NPA, the scan widens.

You're watching more things at once:

• Altitude control: You can't let the airplane drift below a published altitude, even briefly.
• Distance awareness: DME, GPS distance, or timing may define when descent is allowed and where the MAP sits.
• Configuration timing: Gear, flaps, power, and speed matter more because you don't have a glideslope helping pace the descent.
• Mental positioning: You need a clear picture of where you are along the approach, not just whether you're on course.

Treat every non precision approach as a navigation exercise first and a landing opportunity second.

If you want to review real airport procedures before a lesson or trip, browsing approach options through PilotGPT airport data tools can help you spot when the only arrival available may be non-precision.

Precision vs Non-Precision A Clear Comparison

A lot of pilot confusion comes from trying to force every approach into a simple yes-or-no box. Precision. Non-precision. Has glidepath. Doesn't have glidepath. That used to work better than it does now.

The simple mental model

A precision approach is like descending on an escalator. You get lateral guidance and vertical guidance together. If you stay on both, the airplane follows a defined path down to a DA.

A classic non precision approach is more like walking down stairs with a flashlight. The light shows where the hallway goes, but you decide how to step down and when to stop. That stopping point is the MDA, and you must stay at or above it unless you have the required visual reference and can make a normal landing.

Here's the side-by-side picture:

Why GPS makes the labels confusing

Many instrument students often encounter difficulty with this concept. You fly an LPV or LNAV/VNAV, the procedure gives vertical guidance, you descend to a DA, and it feels very much like a precision approach. So why do training materials sometimes still talk about it as non-precision?

Because classification and cockpit technique are not always the same thing.

The FAA explains that APV procedures such as LNAV/VNAV and LPV do not meet ICAO precision-approach standards, so they are classified outside the strict precision category even though they provide vertical guidance and are flown to a DA (FAA Instrument Procedures Handbook Chapter 4).

The useful question isn't just “Does it have vertical guidance?” The useful question is “What kind of guidance is it, and what minima logic goes with it?”

That distinction matters in training. If a student memorizes “non-precision means no glidepath,” they'll be confused the first time they brief an APV. A better habit is to separate three ideas:

1. What guidance does the pilot receive
2. What minimum is used, DA or MDA
3. How the procedure is formally classified

Once you do that, the fog clears. A VOR or LNAV flown to MDA is the traditional NPA picture. An LPV may feel precision-like, but that doesn't automatically make it a precision approach in the regulatory sense.

Decoding the Non-Precision Approach Chart

A non precision approach plate gives you everything you need, but it won't organize your thinking for you. You have to know what to pull from it quickly.

What to find before you intercept final

Before you even start down, lock onto the approach structure.

Look for these items first:

• Approach type and title: VOR, LOC, NDB, RNAV (GPS) LNAV, or something similar. This tells you what kind of signal or database guidance you'll rely on.
• Final approach fix: On many classic non precision approaches, this is marked by the Maltese cross. That symbol should catch your eye immediately because it often marks where final descent begins.
• Step-down fixes: Pilots most often get behind at these fixes. Each one answers a simple question: “How low am I allowed to be by this point?”
• Missed approach point: On one chart it may be a fix, on another a DME value, and on another a runway threshold or timing point. Don't assume.
• Minimums box: Your MDA and visibility requirement live in this box.

A good brief sounds plain, not theatrical. “Cross FAF at the published altitude. Descend no lower than each step-down. Level at MDA if not visual. Missed approach starts at the MAP, not when I get tired of looking.”

What matters most in the profile view

The profile view is where the non precision approach becomes three-dimensional. It tells you where you can descend, how low you can go, and what remains protected.

Focus on reading it in order, not as random chart clutter:

1. FAF altitude
2. Any intermediate descent restrictions
3. MDA
4. MAP location
5. Missed approach climb and routing

If there's a VDP, brief it. That little “V” often gets ignored by students, but it's one of the most useful bits of judgment information on the plate. It tells you the last practical place to start a normal descent from MDA to the runway. If the runway environment appears after that point and you'd need to dive for it, the approach is already telling you the answer.

A non precision approach brief should tell you not only where to descend, but where to stop descending and where to stop trying.

One more chart-reading habit helps a lot. Point to each altitude and say what authorizes it. “Published crossing altitude.” “Step-down after fix.” “MDA until visual or MAP.” If you can't explain why an altitude is legal, don't fly through it.

Flying the Approach From FAF to Runway

Flying the final segment well is where a non precision approach stops being a chart exercise and becomes an aircraft control exercise. The airplane doesn't care that you memorized the plate. It only cares whether you stay ahead of it.

Early training often exposes pilots to the traditional method first. Then experience shows why the industry moved toward something more stable.

The old dive and drive habit

The old method is commonly called dive and drive. You cross the FAF, descend promptly to the MDA, then level off and continue toward the MAP waiting for the runway to appear.

It works. But it asks a lot from the pilot at exactly the worst time.

AOPA training guidance described traditional nonprecision approaches as able to “double” cockpit workload, and that same guidance warned against aggressive descent rates. It noted instructors commonly taught 700–800 fpm and recommended avoiding descent rates above 1,000 fpm (AOPA on nonprecision approach workload and descent technique).

The problem isn't just comfort. It's stability. If you rush down to MDA, then level abruptly, trim changes, power changes, and scan interruptions all pile up near the end of the approach.

How to fly a CDFA

A Continuous Descent Final Approach, or CDFA, fixes most of that by replacing the staircase with one planned, stable descent.

Instead of diving to MDA early, you descend on a constant angle from the FAF toward a point near the runway environment, while respecting that MDA remains a hard floor on a classic NPA.

A practical CDFA flow looks like this:

• Before the FAF: Be fully briefed, configured as appropriate, and trimmed. Know the target speed and expected descent profile.
• Cross the FAF stabilized: Don't be chasing needles, altitude, and checklists all at once.
• Set a planned descent rate: Use your groundspeed and the desired descent path. If your avionics provide advisory vertical information or a computed path, verify it matches the chart logic.
• Make small corrections: CDFA is not a roller coaster. If you're correcting constantly, something upstream is off, usually speed or power.
• Approach MDA with intent: Don't “hunt” below it. If you reach MDA before the runway environment is in sight, level and continue only as authorized.
• At the MAP: Land only if you have the required visual reference and are in position for a normal descent and landing. Otherwise go missed immediately.

Here's a useful cockpit video to study after reading the plate and briefing the profile:

Practical rule: If the airplane is fast, high, and busy at the FAF, the approach isn't set up. Fix it early or don't continue.

The decision at minimums

Students often blend DA logic and MDA logic together. Don't.

On a classic MDA-based approach, reaching minimums does not mean you automatically descend further because you glimpse something gray through the windshield. It means you stay at or above MDA until you have the required visual references and can continue to a normal landing from there.

If continuing would require a steep push, a side-step in your mind, or a scramble to salvage alignment, the answer is missed approach. A disciplined miss is good IFR flying. A forced landing attempt from an unstable non precision approach isn't.

Understanding Minima and Obstacle Clearance

Pilots sometimes treat the minimums box like a legal line item. It's more than that. It's the visible edge of an obstacle clearance system working in the background.

Why MDA is a hard floor

In a precision approach, the glideslope or equivalent path brings you to a DA where the decision is made during descent. In a classic non precision approach, the protected concept is different. The approach is built around an MDA, and you remain at or above it until the approach allows descent visually.

IVAO training material gives concrete system minima of 250 ft for localizer and VOR/DME procedures and 300 ft for VOR and NDB procedures, and it notes that operators must add a performance-based margin to the MDA/H (IVAO guidance on NPA minima and margins). The exact number matters less than the message behind it: without vertical guidance, the procedure needs more conservative minima and more disciplined aircraft handling.

That's why “ducking under a little” is such a serious error. You're no longer inside the protected logic of the procedure.

Why the VDP matters more than many pilots think

The VDP, when published, is where a normal visual descent from MDA to the runway can begin. Think of it as the point where the chart asks, “If you see the runway now, can you land normally from here?”

If the answer is no, the right move is usually not to force the issue.

Use the VDP as a judgment tool:

• If you become visual before or near it: A normal landing may still be on the table.
• If you become visual well after it: The runway may be physically visible but operationally unusable without a steep or unstable descent.
• If no VDP is published: You need to think even harder about what “normal descent and landing” really means in your airplane, on that runway, in that weather.

Seeing the runway isn't the only test. Being able to continue safely is the test.

On dark nights, over black terrain, or with sloping runways, the temptation is to trust what your eyes want to believe. The plate is usually the more honest witness.

Common Pilot Errors and How to Avoid Them

Most non precision approach mistakes aren't caused by ignorance. They happen because workload piles up, the pilot gets task-saturated, and one bad assumption slips through.

The traps that catch otherwise good pilots

Older conventional NPAs gave pilots even less margin for casual flying. Flight Safety Foundation noted that conventional navigation aids used in older procedures had limited angular accuracy, with tolerances around ±5 degrees for NDBs and ±3 degrees for VORs (Flight Safety Foundation on the evolution and limitations of older NPA systems). That history helps explain why these procedures demanded such strict technique.

The most common trouble spots tend to be these:

• Descending below MDA early: Usually caused by runway fixation or a vague idea of where the MAP is.
• Blowing through step-down fixes: Often a scan failure. The pilot is tracking laterally but not thinking ahead vertically.
• Misidentifying the MAP: This happens when the pilot assumes GPS distance, DME, and timing are interchangeable when the chart says otherwise.
• Poor energy management: Fast airplanes turn simple altitude management into rushed power and trim work.
• Overtrusting the signal: Especially on older non-GPS procedures, lateral guidance isn't infinitely precise.

Simple habits that prevent big mistakes

Good habits beat heroic stick-and-rudder corrections.

Try these:

• Brief the miss first: If your brain is primed for the missed approach, you won't cling to a bad landing setup. For broader risk-management habits, PilotGPT safety articles are a useful read between lessons.
• Call out every altitude gate: Say the FAF crossing altitude, each step-down, MDA, and MAP trigger out loud.
• Use one primary source for MAP identification: Don't mix methods unless the procedure supports that.
• Stabilize earlier than you think you need to: A rushed approach almost always becomes a sloppy one.
• Treat lateral and vertical guidance as separate jobs: Being centered on course does not mean you're safe vertically.

A good non precision approach is quiet. No surprises. No chasing. No bargaining at minimums.

Training Tips for Students and Instructors

A student pilot doesn't master the non precision approach by memorizing terms. They master it by building a repeatable decision process. Instructors help most when they teach the “why” behind the altitudes, not just the order of button pushes.

For the student pilot

Chair-fly the approach in plain language. Don't just say, “Cross FAF, descend, MDA, MAP.” Say what each segment means and what instrument or cue confirms it. If you can explain the approach without looking at the plate every few seconds, your cockpit workload will drop.

Use a short study routine:

• Brief one classic NPA each session: VOR, LOC, or LNAV. Focus on what defines the FAF and MAP.
• Practice the missed approach as the default outcome: That keeps your judgment cleaner at minimums.
• Compare MDA-based and DA-based procedures: The mental difference matters as much as the flying difference.

If you want a broader refresher on instrument-rated flying standards and expectations, DuBois Aviation's instrument guide is a solid companion resource.

For the instructor

Teach CDFA early. Don't let students build deep habits around unstable dive-and-drive technique unless the lesson specifically requires understanding legacy methods. Most pilots perform better when the approach is flown as one planned descent rather than a series of recoveries.

Use scenario-based lessons. Fail the glideslope. Make the localizer or VOR the only option. Ask the student where the MAP really is and what happens if the runway appears late. Those are the moments when comprehension shows up.

For curriculum support, lesson ideas, and IFR teaching topics, the PilotGPT blog can give CFIs and students more material to review on the ground before they strap in.

---

PilotGPT helps general aviation pilots reduce workload when the cockpit gets busy. Because it runs offline on your phone or tablet and is built around authoritative aircraft and FAA documents, it can support approach review, checklist access, airport data, and in-cockpit situational awareness when you need fast answers. Learn more at PilotGPT.