How to Teach a Maneuver a Student Keeps Getting Wrong
Every instructor has had a student who's solid on everything except one maneuver. Steep turns that keep losing altitude. Landings that flare too high, every single time. Slow flight where the airspeed keeps creeping. You've explained it three different ways, demonstrated it twice, and it still isn't sticking — and the instinct is usually to explain it a fourth way, louder or slower.
That's often not the problem. Most maneuvers that "won't click" aren't a knowledge problem at all — they're one of four other things, and each one needs a completely different fix.
First, figure out which of the four it actually is
1. They understand it but can't execute it under workload. Ask the student to explain the maneuver on the ground, away from the airplane. If they can walk you through steep turns perfectly at a desk but fall apart at altitude, the problem isn't conceptual — it's that the maneuver is competing with too many other things for their attention at once (aircraft control, scan, radio, nerves). The fix here is reducing workload elsewhere, not re-explaining the maneuver: talk them through it less, let silence do more, or break the maneuver into smaller pieces they can chain together instead of demanding the whole thing at once.
2. They've built a habit around a wrong mental model. This is the "flares too high, every time" case. It's rarely inconsistency — it's consistency around the wrong picture. Something about their sight picture, their reference point, or their timing is anchored to the wrong cue, and it's repeating reliably because it's now a habit, not a mistake. Explaining the correct technique again doesn't fix this, because they're not missing the explanation — they're executing a different, wrong explanation perfectly. What usually works is finding the specific wrong cue they're using (ask them what they're looking at, exactly, in the flare) and replacing that one reference point, rather than re-teaching the whole maneuver.
3. It's a physical sensation problem, not a procedural one. Slow flight and stalls are the classic case — a student who intellectually knows to add power and reduce back pressure, but freezes or over-corrects because the sensation of an impending stall is triggering something other than the trained response. No amount of ground explanation fixes a reflex. This one usually needs more controlled exposure at a lower intensity — approaches to the maneuver without completing it, repeated until the sensation itself stops being the obstacle — before going back to the full maneuver.
4. The maneuver actually is being taught inconsistently. Worth ruling out honestly: if a student has flown with more than one instructor, check whether they're getting the same technique from both of you. A student alternating between two slightly different sight pictures for the same maneuver will look like they "can't get it," when actually they're being asked to learn two things and blend them. This is the one case where the fix genuinely is a conversation between instructors, not with the student.
The diagnostic questions that actually help
Instead of "let's try that again," a few questions tend to surface which of the four you're dealing with:
- "Walk me through what you're doing, step by step, without the airplane." (Tests understanding vs. execution)
- "What are you looking at right when it starts to go wrong?" (Surfaces the wrong reference point)
- "What does it feel like right before it happens?" (Distinguishes a physical/reflex issue from a procedural one)
- "Has this been the same with every instructor you've flown with?" (Rules in or out inconsistent teaching)
The answers usually point clearly at one of the four categories above — and once you know which one it is, the fix is specific instead of "try harder."
Why this matters beyond the one maneuver
A student who's stuck on one maneuver for multiple lessons is also a student whose confidence is quietly eroding, even if they don't say so. Diagnosing the actual cause — rather than repeating the same explanation and hoping repetition alone closes the gap — usually resolves things faster, and it also tends to be the difference a student remembers years later as "the lesson where it finally clicked," instead of one more frustrating flight.
It's also worth writing down, briefly, what the actual issue turned out to be — in a lesson note, a training record, wherever your school tracks progress. Six months later, when you or another instructor is trying to figure out why the same student is struggling with something related, that one sentence ("kept anchoring the flare to the far horizon instead of peripheral cues") is worth more than a grade of "needs practice."
We built that kind of note-taking directly into FlightDesk AI's training records, alongside scheduling, maintenance tracking, and the rest of day-to-day school operations — because the detail of what actually went wrong in a lesson is exactly the thing that gets lost in a spreadsheet cell that just says "solo stalls, needs work."