Too much feedback becomes no feedback: The instructor's notes contain eight corrections. The student remembers two, combines them incorrectly, and flies the next attempt with more workload than before.

The highest-value correction is usually the earliest safety-significant or causal issue the learner can act on next.

Choose the correction that addresses the highest safety risk or the earliest high-leverage problem the learner can recognize and change on the next attempt. Do not automatically choose the largest numeric deviation. A late, dramatic error may be the result of an earlier setup, decision, or attention problem. The best correction connects a clear cue to a specific action and an observable result.

Assessment principle: The FAA Aviation Instructor's Handbook says a comprehensive assessment does not have to be long or treat every detail. The instructor may focus on a few major points or on what the learner can reasonably improve. Focusing the next attempt is not the same as ignoring safety or required corrections.

Why one correction often produces a better next repetition

A flight lesson may reveal many issues:

  • setup was rushed;
  • the airplane was out of trim;
  • the student looked inside too long;
  • bank wandered;
  • altitude changed;
  • rollout was late;
  • the correction was abrupt;
  • the radio call was incomplete;
  • the checklist flow was interrupted;
  • the student did not recognize the need to discontinue.

Trying to correct all of them at once can increase workload and leave the learner uncertain about what matters most. One primary correction gives the next attempt a deliberate purpose. Supporting comments can still be recorded, and any immediate safety, regulatory, or aircraft-procedure issue must be addressed.

The five-level priority test

Evaluate possible corrections in this order.

1. Safety and legal priority

Address first any issue involving:

  • loss of aircraft control;
  • collision or traffic risk;
  • runway incursion or occupied-runway risk;
  • stall/spin or terrain risk;
  • weather or wind beyond capability;
  • aircraft limitations;
  • checklist or emergency-procedure requirements;
  • unauthorized solo activity;
  • disregard of instructor or logbook limitations;
  • late discontinuation or go-around decisions;
  • maintenance or equipment discrepancies requiring action.

A lesson may stop being about performance refinement when a risk-management or procedural issue dominates.

2. Earliest high-leverage point

Find the first event that meaningfully moved the performance away from the objective.

Examples:

  • the long landing began with excess energy before the flare;
  • the overshot heading began with a late rollout decision;
  • the steep-turn altitude loss began during entry rather than at the lowest point;
  • the unstable go-around began with a delayed decision;
  • the poor stall recovery began with failure to reduce angle of attack promptly;
  • the ground-reference pattern became distorted because wind correction was planned too late.

Correcting the earliest high-leverage point can reduce several downstream deviations at once.

Use the word "high-leverage" carefully. Recorded data may support the sequence without proving a complete causal chain. Treat the selected cause as an instructor-supported training hypothesis when relevant information is missing.

3. Recurrence and repeatability

A one-time deviation caused by a gust, traffic avoidance, an unusual interruption, or sensor problem may not deserve the same priority as a repeated pattern.

Ask:

  • Did the issue appear in both directions?
  • Did it repeat across attempts?
  • Did it occur under comparable conditions?
  • Did it return after a successful correction?
  • Did it appear in simulator and aircraft sessions?
  • Did the student require the same prompt more than once?
  • Does the pattern transfer to another maneuver or phase of flight?

A recurring recognition problem may deserve priority even when each individual deviation is small.

4. Teachability and learner control

Choose a correction the learner can actually recognize and perform.

Weak correction:

Be smoother.

Stronger correction:

As the bank reaches 30 degrees, establish the outside pitch reference and make the planned power change before the selected bank is reached.

Weak correction:

Do not float.

Stronger correction:

At the prebriefed approach gate, confirm path, configuration, and the aircraft-specific speed. If the approach is outside the gate and not promptly corrected, go around rather than carrying excess energy to the flare.

The stronger versions name a cue and action within the learner's control.

5. Transfer and next-lesson value

Prefer a correction that supports future situations.

Examples:

  • earlier energy recognition helps normal, short-field, and crosswind landings;
  • rollout anticipation helps turns to headings, pattern turns, and instrument work;
  • maintaining outside reference and cross-check helps steep turns and traffic-pattern control;
  • timely go-around decisions support runway-traffic, unstable-approach, and bounce scenarios;
  • better coordination supports stalls, climbs, slow flight, and go-arounds;
  • a consistent pre-maneuver clearing flow transfers across training tasks.

A transferable correction gives the learner a principle, not just a fix for one screenshot.

The correction-selection questions

For each candidate correction, ask:

  1. Does it address an immediate safety or procedural concern?
  2. Did it occur before the larger deviation?
  3. Is there enough evidence to support the explanation?
  4. Did the issue repeat?
  5. Can the learner recognize the cue without instructor prompting?
  6. Is the action specific and aircraft-appropriate?
  7. Can success be observed on the next attempt?
  8. Will the correction transfer to another realistic situation?
  9. Is the practice environment appropriate?
  10. What should the learner do if the correction does not work?

The highest-value correction usually performs well across several questions.

Use cue, action, result, and boundary

Write the selected correction in four parts.

Cue

The earliest observable signal that action is needed.

Action

The specific response taught by the instructor and consistent with the aircraft procedure.

Result

The expected change in performance.

Boundary

The condition requiring a pause, discontinuation, go-around, instructor intervention, or another safe course of action.

Example for turns to headings:

  • Cue: the target heading is approaching by the instructor-selected rollout lead;
  • Action: begin a smooth, coordinated rollout while adjusting pitch and power as needed;
  • Result: wings level on the assigned heading without a control reversal;
  • Boundary: if orientation, traffic, or instrument cross-check is lost, prioritize aircraft control and follow instructor direction.

Do not confuse the highest score opportunity with the highest training value

A student may gain more points by fixing a small, easily measured deviation. That does not make it the most important correction.

Examples:

  • improving a heading tolerance is secondary to correcting poor coordination during a stall entry;
  • touchdown accuracy is secondary to an unstable approach and late go-around decision;
  • a cleaner altitude trace is secondary to inadequate traffic scanning;
  • a higher maneuver score is secondary to using the correct aircraft procedure;
  • a consistent simulator result is secondary to recognizing that the home controls do not reproduce aircraft control feel.

Use scores as one summary signal. Keep the underlying skill, risk, and procedure visible.

Three worked examples

Example 1: Short-field landing

Observed issues:

  • final approach was above the planned path;
  • eIAS was above the aircraft-specific target late on final;
  • power was reduced aggressively;
  • the airplane floated;
  • touchdown occurred beyond the intended point;
  • braking was abrupt.

Possible corrections include path, speed, power technique, flare, touchdown, and braking.

The instructor selects the stabilized-approach gate as the primary correction because excess energy existed before the flare and affected several later events.

Correction:

At the prebriefed gate, confirm the aircraft-specific configuration, path, and speed. If the approach is not stable and cannot be corrected within the instructor's criteria, go around.

Braking technique is still discussed if it created a safety concern, but the next repetition focuses on arriving at the flare with the correct energy state.

Example 2: Steep turn

Observed issues:

  • bank reached 50 degrees;
  • altitude decreased;
  • eIAS decreased;
  • the student made a large pitch correction;
  • bank then oscillated;
  • rollout finished beyond the entry heading.

The largest numeric deviation may be altitude. The sequence shows the problem began as bank increased without a stable outside pitch reference and planned power change.

Primary correction:

Establish the outside pitch reference and planned power as the bank passes 30 degrees, then use a brief instrument cross-check after the selected bank is established.

The next attempt tests whether that entry correction reduces altitude, speed, and bank variation together.

Example 3: Go-around

Observed issues:

  • the approach crossed the stability gate outside the plan;
  • the student continued;
  • the instructor called for a go-around;
  • yaw increased as power was applied;
  • configuration changes were delayed;
  • climb speed stabilized late.

The instructor must address the aircraft-control items, but the primary lesson may be decision timing. An earlier self-initiated go-around would reduce low-altitude workload and create more time for the aircraft-specific sequence.

Primary correction:

At the prebriefed gate, initiate the go-around immediately when the approach is outside the criteria and not promptly recoverable. Then execute the POH/AFM sequence while maintaining aircraft control.

How FlytWERX can help identify the high-leverage point

FlytWERX can organize the maneuver timeline and show where selected recorded variables began to change. Depending on the source and current version, the review may include altitude, heading, course, ground track, groundspeed, vertical speed, pitch, bank, flight path, maneuver scores, history, notes, instructor-student sharing, and eIAS.

When airspeed matters, FlytWERX can add estimated indicated airspeed, or eIAS, to the debrief. eIAS is a calculated training estimate based on GPS-derived speed, winds aloft, temperature, and the active wind correction; more representative local winds can be entered when available. The airplane's approved airspeed indication remains controlling in flight. See How FlytWERX calculates eIAS.

The replay can show sequence and recurrence. It may not establish traffic scan, control feel, coordination, power or configuration position, checklist use, decision reason, or cause. The instructor chooses the correction by combining evidence with professional judgment.

A one-correction debrief note

Record:

  • Objective: what the maneuver or lesson was meant to demonstrate;
  • Evidence: one or two observations that support the correction;
  • First meaningful deviation: where the pattern began;
  • Primary correction: cue, action, result, and boundary;
  • Supporting concerns: items that must be monitored or addressed separately;
  • Next environment: ground, chair flying, simulator, dual, or authorized solo practice;
  • Success standard: what the instructor expects to see;
  • Review plan: which data or observation will confirm improvement.

When more than one correction is required

One correction is a focus rule, not an absolute limit.

Address multiple items when:

  • an immediate safety issue requires it;
  • the aircraft procedure contains an inseparable sequence;
  • the student cannot safely repeat the task without correcting more than one element;
  • the lesson is a stage check or summative assessment requiring broader coverage;
  • required records or endorsements contain multiple deficiencies;
  • the student is ready to integrate several already-understood elements.

Even then, identify the principal message so the learner knows what to prioritize.

Is FlytWERX a fit for this instructor workflow?

Which plan should a CFI evaluate?

Use Sim-Only for simulator-only preparation and review. Use In-Air + Sim when the CFI needs real-flight telemetry, real maneuver tracking, or a live and post-flight debrief. A multi-user school deployment should be scoped separately. Verify current plan inclusions on the FlytWERX pricing page.

What should a focused test prove?

A useful test should show that the debrief ends with one correction the learner can remember and test. Use several real lessons, include an ordinary session rather than only the cleanest example, and document what still requires instructor observation or judgment.

For the full buying details, use the pricing and plan comparison, flight-school implementation, data migration and record continuity, ROI measurement, and software comparison.

Put this into practice

Choose the earliest high-value issue the learner can act on and deliberately defer the rest. Review the result with the person who owns the training decision, then use the next comparable attempt to test whether the change worked.

Next step: Focus the Next Rep With FlytWERX.

Important operating and training limits

This article is educational. It does not replace a qualified flight instructor, the current POH/AFM, required endorsements or records, approved school procedures, ATC instructions, or pilot-in-command judgment. FlytWERX supports performance review and debriefing; it is not a primary flight instrument and does not determine proficiency, readiness, authorization, or regulatory compliance by itself.

Frequently asked questions

Should the instructor always choose the correction?

The instructor remains responsible for the assessment and lesson plan, but learner-centered assessment should involve the student. Ask which issue the learner believes had the greatest effect, then compare that view with the evidence and instructor judgment.

Is the first deviation always the root cause?

No. The first recorded deviation may follow an unrecorded planning, perception, control, or procedural issue. Use it as a starting point, not automatic proof of cause.

What if the same correction does not work on the next attempt?

Reassess the explanation, cue, aircraft procedure, teaching method, conditions, and data quality. The original hypothesis may have been incomplete or wrong.

Should the selected correction be the item furthest outside ACS tolerance?

Not necessarily. Safety, procedure, recognition, and earlier high-leverage events may matter more than the largest measured deviation.

Can an algorithm select the correction automatically?

An algorithm can identify recorded patterns and departures. Selecting the best training correction requires aircraft context, learner understanding, risk management, unrecorded cues, and instructor judgment.

Sources