The plateau at 28 hours: prompt dependency, not a lack of talent
A second-year PPL student has 28 hours over 14 weeks, six hours of budget left, and a skills test provisionally booked in eight weeks. With the instructor prompting each action the student flies accurate circuits, clean stalls and medium turns. Without prompts, over the last three flights, the student needed 20–30 verbal prompts per flight and twice drifted about 200 ft below the briefed altitude in the turn while apparently unaware of it. The syllabus is hour-based; the last four lesson entries are the same exercise repeated, and the school's operations manual requires each syllabus item to be signed off before the next is started. In the debrief the student says: "I'm just not a natural. I'll never get this." You have noticed that your own last four lessons followed an almost identical script: demonstrate, talk the student through, land, debrief.
1. How would you distinguish a normal learning plateau from prompt dependency and a transfer-of-learning failure? What evidence would you gather in the next flight?
Read the worked answer
A plateau is a flattening of the learning curve while a skill consolidates; the underlying competence is still improving and the student can usually explain what they are trying to do. Prompt dependency looks different: the student performs well only while the instructor supplies the cognitive work, and performance collapses when the voice stops. Transfer failure shows as competence in one context that does not appear in another.
Evidence to gather:
- Prompt count and type. Sort the 20–30 prompts into commands ("pull back"), cues ("check your altitude") and questions. A student needing commands is not learning; a student needing occasional questions is consolidating.
- Self-monitoring. Ask the student to call their own deviations before I say anything. Two unobserved 200 ft altitude losses in a turn suggest the scan is not established, which is a perceptual skill problem, not an attitude problem.
- Generality. Can the student hold altitude in a straight climb but not in a turn? Can they do it in the circuit but not in a different area? If it is context-specific, the practice has been too narrow.
- My own instruction. The identical script for four lessons is the strongest evidence in the file: I have been doing the thinking, the practice has been massed and blocked, and the student has learned to wait for the voice. That is an instructional design fault, and it is mine, not the student's.
- Attribution. "I'm not a natural" is a stable, uncontrollable explanation. Ask what the student thinks went wrong on a specific turn; a strategy-based answer is a good sign, an ability-based answer needs reframing.
The next flight should be planned as a diagnostic, not another repetition: same exercise, no prompts unless safety demands it, with the student calling their own errors.
2. Design the next two lessons using specific instructional principles, and state what you will do differently as the instructor.
Read the worked answer
Lesson A - fading prompts and self-checking. Start with a ground brief that ends with the student briefing me on the circuit, so the sequence is retrieved rather than recognised. In flight, replace commands with questions, and then with silence. Protocol: at each gate I say only "check" and the student calls the parameter and the correction. Target: no more than five prompts, all questions. Include one deliberate demonstration of a 200 ft altitude loss with the student watching the altimeter, then have them recover it, so the cue for the error is learned. Finish with the student self-debriefing before I speak.
Lesson B - interleaving and a scenario. Replace blocked repetition with varied practice in one flight: a normal circuit, a flapless approach, a go-around from a pre-briefed gate, and a diversion to another aerodrome. Give the flight a purpose - "you are ferrying a passenger to X, I am the passenger" - so the student holds the plan, the radio and the aircraft together. Vary the order each flight; interleaving feels harder and produces better retention than repeating one exercise.
What I change. I stop talking through the manoeuvre; I brief the objective and the success criteria and then let the student fly. I record prompt count, error type and self-corrections each lesson, so progress is visible even when the aircraft handling looks the same. I also schedule a proper review point at the halfway mark, four weeks out, so the skills test booking is confirmed on evidence rather than hope.
3. How do you handle the school's item sign-off rule, the student's morale, and the eight-week skills test booking - without either falsifying a record or destroying the student's confidence?
Read the worked answer
The sign-off rule. The operations manual requires the item to be signed before the next item starts; it does not require me to sign an item that has not been met, and it should permit partial completion to be recorded. So I record what was achieved and what remains - "turns: altitude within ±100 ft with prompts; not yet met without prompts" - and I do not sign the item. If the manual is genuinely rigid on this point, I raise it with the head of training as a training-design problem: a syllabus that forces repetition of identical lessons is producing the plateau, and the manual should allow sub-elements and variation. That is a legitimate professional conversation, not a workaround.
The student's morale. Give the diagnosis honestly and specifically, and attach it to the instruction rather than to the person: "You can fly these exercises; you have learned to wait for me to tell you what to do, and that is my planning, not your talent." Show the evidence - prompt counts falling over two flights is visible proof. Set two or three concrete, achievable targets for each lesson so success is frequent and attributable to effort and strategy.
The booking. Keep the skills test as provisional and set a decision date at four weeks. At that point, review prompt count, self-correction rate and consistency across varied conditions. If the standard is met, confirm the booking; if not, move it and tell the student now rather than three days before. Six hours is enough for this if the lessons are designed rather than repeated, and the honest conversation today protects both the student and the school far better than a signature.