Workload Management and Decision Altitude in Instrument Approach Training

A student can brief an approach correctly, draw the procedure turn on a whiteboard, and recite the missed approach point from memory — and still descend through decision altitude in the airplane. The cause is almost never a knowledge deficiency. It's workload management.

Workload Is Usually the Root Cause

Students who bust minimums almost never do it because they don't know what the minimums are. They bust minimums because their workload at the decision altitude or MAP is so high that the minimums get displaced by more urgent mental tasks.

The typical sequence: the student is working hard to track the localizer and glideslope (or VOR radial and step-down fixes on a non-precision), managing airspeed, configuring flaps, running the landing checklist, monitoring time, and communicating with approach control. By the time they hit DA, their cognitive capacity is at its limit. The altimeter isn't getting attention because everything else is demanding it.

The fix isn't to teach minimums more emphatically. The fix is to reduce workload everywhere else so that the altimeter gets its share of attention.

Build the Approach Briefing to Eliminate In-Flight Decisions

A good approach briefing should remove as many decisions from the approach itself as possible. If the student is deciding anything significant during the approach — what to do with the gear at the FAF, when to start timing, what happens if the approach light system is partial — they're spending cognitive resources that should be on the instruments.

The briefing I use covers, in this order:

1. Expected approach and transition — what ATC has told us or what we expect
2. Field elevation and minimums — say the DA/MDA aloud, then say what's above the terrain at that altitude
3. Required visual references — what exactly we're looking for (approach lights, runway environment)
4. At minimums — the decision: "If we see [specific references], we continue. If we don't, we're executing the missed approach — immediately."
5. The missed approach procedure — climb to, turn to, contact
6. Aircraft configuration plan — gear, flaps, power at each gate (initial approach fix, FAF, glideslope intercept)

The critical piece is number four. "At minimums" is not a discussion point during the approach — it's a programmed decision. If we see it, we continue. If we don't, we go. That decision has to be made on the ground, before any workload exists.

Students who reach DA with an unclear decision framework will hesitate. Hesitation means descending below DA.

Use a Gate-Based Approach to Configuration

One of the most effective changes I've made in how I teach approaches is moving away from "do this around the FAF" to explicit configuration gates.

A gate is a fixed point in the approach where a specific configuration should be complete. Before the gate, the student manages the transition. At the gate, we do a quick verification:

The gate structure does two things: it distributes the configuration workload across the approach rather than front-loading it at the FAF, and it creates checkpoints that make it obvious when the student is behind.

When a student is still adding flaps at 500 feet above DA, I can see immediately that they're going to be heads-down when they should be heads-up, and I can correct it in the pattern before the approach degrades.

The 1,000-Foot Call

I use a verbal callout at 1,000 feet above DA/MDA on every approach: "One thousand above minimums." The student acknowledges it. This does several things:

• Forces the student to reference the altimeter actively
• Creates a mental checkpoint: how am I doing? Am I configured? Is the approach stable?
• Signals that the approach is entering its critical phase

The 500-foot call ("Five hundred above minimums") is a second checkpoint. At this point, if anything is out of place — speed too high, gear not verified, checklist incomplete — we go missed. Stability is a yes/no question, not a judgment call. If you're asking yourself whether it's stable enough, it isn't.

Descending Through Minimums

If a student is consistently descending through DA (not just to it), the root cause is almost always one of three things:

1. They're not monitoring the altimeter actively near minimums. The fix is the gate structure and verbal calls above, plus explicit training on instrument scan priority during final approach. Near minimums, the altimeter gets priority — the glideslope pointer is keeping itself near center, but the altimeter needs eyes.

2. They're confused about when the minimums call is made. DA is a decision altitude, not a stop altitude. The decision is made at DA, which means the student needs to be looking outside as the altimeter passes through DA — not after. Some students think of DA as a floor they shouldn't go below, so they continue descending toward it and then look. That's backwards. The look happens at DA, and if they don't see what they need, the go-around starts immediately, from that altitude.

3. They're too focused on the runway and continuing a bad approach. This is the most dangerous version. The student sees something vague at minimums — a glow of lights, the PAPI — and convinces themselves it's enough to continue. It isn't. The ACS requires specific visual references. Train this explicitly: show them what "not enough" looks like in the sim before they encounter it in actual IMC.

Partial Panel and Non-Precision Approaches

More minimums busts happen on non-precision approaches than on ILS approaches, for an obvious reason: the step-down structure is more complex to manage, and there's no glideslope to follow. Students who have learned approaches primarily on the ILS often struggle when they have to manage altitude actively rather than following a needle.

The specific failure mode on VOR/DME and RNAV LNAV approaches: the student reaches the MDA and levels off correctly, but then descends as workload increases near the MAP. Leveling off at MDA is a discipline skill, not a knowledge skill — it requires active altitude monitoring when every other task is also demanding attention.

The sim is your friend here. Put the student in the MDA level-off on a non-precision, then add ATC calls, unexpected airspeed changes, and a distracting ATIS update. Watch what happens. The altitude awareness failure that was theoretical becomes visible and correctable.

Documenting Progress

One of the things that's improved my instrument instruction significantly is systematic documentation of what each student is struggling with from lesson to lesson. Busting minimums on lesson 7, getting better on lesson 9, still inconsistent on non-precision on lesson 12 — that's a pattern that tells me something specific, and it's also a conversation I can have with the student's training record in front of me.

At our school, we log this through Aloft360's training module — endorsements, specific weaknesses, and progress against Part 61 instrument rating requirements. When a student comes in for a lesson after a two-week gap, I can look at where we were and start there, not from scratch.

NTSB accident analysis of instrument approach accidents consistently identifies continued descent below minimums without required visual references as a factor. The FAA's Instrument Flying Handbook (FAA-H-8083-15B) and the Instrument Rating ACS both frame DA/MDA as decision points, not floors — a distinction that needs to be trained explicitly, not just explained once. The techniques above build procedural habits around that decision through repetition in controlled conditions.

---

References

• FAA Instrument Flying Handbook (FAA-H-8083-15B)
• Instrument Rating – Airplane ACS — Task area covering instrument approaches, decision altitude, and missed approach criteria
• 14 CFR 91.175 — Takeoff and landing under IFR: required visual references before descent below DA/DH or MDA
• NTSB Aviation Accident Database — searchable accident data

Grayson Bertaina is a Master CFI, Gold Seal CFII/MEI, and ATP based in the Eastern Region. He was named AOPA's 2026 Regional CFI of the Year.