The flight debrief is the highest-leverage teaching moment in a training sortie. The lesson is still vivid for the student. The specific errors and their consequences are available in working memory. The instructor has observed the student's actual performance rather than their self-reported account of it. Used well, the debrief produces more behaviour change per minute than almost any other teaching activity. Used poorly (which is more common) it produces defensiveness, anxiety about future lessons, or the opposite problem: false confidence from a debrief that glossed over real issues.
This article covers what research in aviation pedagogy and cognitive psychology tells us about debriefs that change behaviour, and how the AngaBrief instructor review workflow fits into that framework.
Why most debriefs do not produce behaviour change
The typical debrief structure goes something like: "That was good overall, your circuits were consistent, but you were a bit high on the third approach, and you need to look further down the runway on the flare. Good work though." This is a very common pattern and it has several problems:
Praise-sandwich framing. Framing criticism between compliments is intended to reduce defensiveness but research consistently shows it backfires. Students remember the positive parts more vividly, the criticism is emotionally buffered to the point of reduced salience, and the overall message (that there is a specific technical error requiring correction) is diluted.
Vague language. "A bit high" and "look further down the runway" describe outcomes without describing causes or corrections. The student who was high on the approach does not know whether the issue was turn-onto-base altitude, speed management, power setting, or descent rate. They also do not know specifically what "further down the runway" means in visual terms: what should they be looking at?
No prioritisation. A student who made four different errors in a circuit session cannot fix four things simultaneously. Presenting four pieces of equal-weight feedback creates diffuse improvement effort rather than targeted correction of the highest-priority issue.
No follow-through check. Without a defined moment in the next lesson at which the instructor specifically reassesses the debriefed skill, there is no accountability for whether the change actually occurred.
The PAVE framework adapted for debriefs
The same structured framework used in pre-flight risk assessment (Pilot, Aircraft, Environment, External pressures) provides a useful structure for debriefs, though applied differently:
Pilot performance: What did the student do or fail to do? Focus on specific actions at specific moments. "On the third circuit, when you turned onto base, you were at 700 ft rather than 1,000 ft. That resulted in a low final approach and compression of your checks." This is specific, factual, and actionable.
Aircraft management: How did the student manage the aircraft's energy state, configuration, and systems? "Your speed on final for the last two circuits was 10 knots above the target. That is why you floated: the aircraft was carrying excess energy into the flare zone."
Environment interaction: How did the student handle the specific conditions of the lesson? "The crosswind today was 8 knots from the right. Your aileron input on the approach was adequate but you were not maintaining consistent rudder pressure to hold the centreline. We can see this from the tendency to drift left before the flare."
Decision-making: This replaces the External pressures category. What decisions did the student make and were they the right ones at the right time? "On the second approach, you could see the approach was high and you attempted to correct rather than going around. We need to talk about the decision criteria for going around."
One thing first: prioritisation
Before the debrief begins, the instructor should identify the single most important area for improvement from that lesson. This becomes the anchor of the debrief: the element that receives the most time, the most specific description, and the clearest correction plan.
Everything else is secondary and may be briefly mentioned but not developed. A student who leaves the debrief with one clear, specific improvement target and a concrete plan to achieve it will progress faster than one who leaves with a list of five issues and no prioritisation.
The question to ask yourself as the instructor before beginning: "If this student only improves one thing before the next lesson, what should it be?" That is your debrief anchor.
Descriptive not evaluative language
The most consistent finding in educational research on feedback is that descriptive feedback produces better outcomes than evaluative feedback. Evaluative: "Your approach was unstable." Descriptive: "On final, your speed was 8 knots above the target and your descent rate was increasing rather than stabilising. By 500 ft, you were above the correct glidepath." The descriptive version gives the student the information they need to understand what happened, why, and what the alternative looks like.
Evaluative language (good, bad, unstable, excellent) activates the student's self-assessment and emotional response. Descriptive language activates their analytical processing of the specific event. The goal is analytical processing, because that is what produces changed technique.
How AngaBrief changes the debrief dynamic
The instructor review workflow in AngaBrief creates a pre-debrief structure that most instructors find valuable. Before the flight, the student has completed a PAVE/IMSAFE assessment. The instructor has reviewed and approved (or requested revision of) that assessment. Both parties are working from a shared, documented risk picture before the lesson begins.
After the flight, the instructor can compare the pre-flight assessment against the actual lesson experience. If the student flagged fatigue as a mild concern in the IMSAFE section and then demonstrated impaired attention management in the circuit, there is now a specific, documented connection between a pilot state factor and a performance outcome. That connection is the content of a high-quality debrief: evidence-based, specific, and directly actionable for the next flight.
The assessment record also provides longitudinal data. An instructor who can see that a student has flagged elevated stress in three consecutive pre-flight assessments is equipped to have a different conversation than one who is only working from the single lesson in front of them.
Ending the debrief: the one-forward agreement
The most effective way to end a debrief is the one-forward agreement: a single, specific, measurable commitment from the student about what they will do differently in the next lesson. "In the next circuit session, when I turn onto base, I will check my altitude is 1,000 ft before continuing the turn. If it is below 1,000 ft, I will extend the crosswind to recover altitude before turning base." This is specific, observable, and self-assessable.
The instructor notes this commitment. At the beginning of the next lesson, they briefly revisit it: "In the last lesson, you committed to checking altitude at 1,000 ft before the base turn. Let's see how that goes today." This closes the feedback loop, creates accountability, and makes the debrief part of a continuous improvement system rather than a standalone event.