The debrief clock is already running: Ten minutes remain before the next student arrives. The lesson included three landing attempts, a go-around, a radio mistake, and one excellent correction. A debrief that covers everything equally will cover nothing well.

A useful CFI checklist reconstructs the flight, protects required records, and ends with one correction the learner can actually use.

A complete CFI debrief should reconstruct the lesson, compare the performance with the correct objective and standard, assess knowledge, risk management and skill, distinguish observations from explanations, and end with a specific next action. It should be comprehensive enough to guide improvement without trying to discuss every minor detail.

Checklist status: This is a FlytWERX editorial workflow built from FAA instructor guidance. It is not an FAA-mandated form. It does not replace required pilot logbook entries, instructor records, endorsements, school lesson records, approved syllabi, or operator procedures.

Before the checklist: secure the operation first

Complete aircraft shutdown, securing, discrepancy reporting, passenger or student responsibilities, and other required postflight duties before beginning an extended review. If a safety, maintenance, medical, or operational issue requires immediate action, address that issue through the appropriate process before opening graphs or discussing grades.

The debrief should occur when both instructor and learner can focus. A short immediate review may preserve the essential facts, with a deeper replay after the aircraft and records are secure.

Step 1: Restate the lesson objective and completion standard

Begin by naming what the lesson was intended to accomplish.

Confirm:

certificate, rating, stage, or training purpose;
lesson objective;
applicable ACS area and task, when relevant;
POH/AFM procedure and aircraft limitations;
school, operator, or approved syllabus standard;
instructor developmental target;
planned risk-management or scenario objective;
whether the session was dual, solo review, simulator, approved training device, stage check, or another activity.

Do not let the final result redefine the objective after the fact. If the lesson changed because of weather, traffic, aircraft condition, workload, or student needs, record the revised objective.

Step 2: Ask the learner to replay the lesson

Use the FAA learner-centered assessment sequence. Start with open-ended questions before showing the instructor's conclusion or the complete data display.

Ask:

What was the plan?
What happened in sequence?
Where did the plan change?
What did you notice first?
Which part felt most stable?
Where did you become uncertain or overloaded?
When did you decide to correct, discontinue, divert, or go around?
Where did I prompt, demonstrate, or intervene?

Listen for differences between the learner's account and the instructor's observation. A discrepancy is not automatically dishonesty or carelessness. It may reveal what the learner did not perceive, misunderstood, or remembered differently.

Step 3: Reconstruct the operational context

Record only the conditions that matter to interpretation.

Include as applicable:

aircraft, configuration, equipment, and data source;
airport, runway, practice area, route, or airspace;
wind, gusts, turbulence, ceiling, visibility, temperature, and density altitude;
runway or surface condition;
traffic, ATC, radio, or airspace workload;
aircraft or equipment discrepancies;
student fatigue, stress, illness, medication, distraction, or workload concerns that were reported or observed;
instructor demonstration, coaching, or control intervention;
deviations from the planned lesson.

Do not use the debrief to make medical, maintenance, or causal conclusions beyond the instructor's qualifications and evidence. Route discrepancies through the proper process.

Step 4: Assess knowledge, risk management, and skill separately

The FAA ACS integrates all three. A maneuver can meet numeric tolerances and still reveal a knowledge or risk-management gap.

Knowledge

Ask whether the learner can explain:

the operational reason for the maneuver or procedure;
the relevant aerodynamics and aircraft systems;
the POH/AFM procedure and limitations;
the cues that should trigger action;
the factors that change performance;
the conditions requiring a discontinuation, go-around, diversion, or other decision.

Risk management

Review:

area clearing and traffic awareness;
altitude and terrain;
runway and practice-area selection;
weather and wind;
aircraft condition and performance;
checklist and procedural discipline;
workload and distraction;
stabilized-approach or other prebriefed gates;
go/no-go, continue, divert, or go-around decisions;
the timing and independence of the learner's decisions.

Skill

Review the task-specific performance:

setup and configuration;
control coordination;
altitude, heading, bank, airspeed, path, touchdown, or other applicable standards;
recognition and correction of deviations;
recovery and transition;
repeatability;
level of prompting or intervention required.

Step 5: Identify the first meaningful deviation

Do not begin with the most dramatic result unless that result truly began the problem.

Ask:

What changed first?
Which change was expected?
Which change moved the performance away from the objective?
When did the learner recognize it?
What correction followed?
Did the correction solve the problem or create another one?

Examples:

a long landing may begin with an unstable, high-energy final;
an overshot heading may begin with delayed rollout planning;
altitude loss in a steep turn may begin as bank is established;
a weak go-around may begin with a late decision rather than the configuration sequence;
an uncoordinated stall entry may begin before the pitch reaches the expected attitude.

Treat the proposed cause as a working explanation until the evidence supports it.

Step 6: Audit the flight data before interpreting it

Identify the source and quality of every field used in the debrief.

Confirm:

aircraft avionics, Stratus, device sensors, simulator, manual entry, or another source;
whether the device was mounted, oriented, and calibrated correctly;
time alignment and event boundaries;
gaps, dropouts, smoothing, or blended sources;
whether altitude is MSL, AGL, pressure altitude, or derived;
whether direction is heading, course, or ground track;
whether speed is aircraft IAS, simulator airspeed, GPS groundspeed, or FlytWERX eIAS;
whether a score or event marker is algorithmic, manual, or instructor-adjusted;
whether the displayed standard matches the aircraft, lesson, school, and certificate level.

Do not infer an unrecorded control input, checklist action, stall warning, traffic event, power setting, or coordination state from a trace that does not contain it.

Step 7: Use eIAS with the correct context

For supported live-flight review, FlytWERX calculates estimated indicated airspeed using GPS speed, current winds aloft, temperature, and the active wind correction. A pilot or instructor can enter more representative winds for the training area.

FlytWERX instructors have generally observed eIAS averaging approximately 1 to 3 knots from the airplane's indicated airspeed when the wind correction is current. This is a first-party field observation, not a certified specification or a guarantee.

When eIAS is used, record:

wind source and timestamp;
temperature source;
whether local winds replaced the broader forecast;
the maneuver and flight phase;
whether the estimate was compared with the aircraft indication;
any reason the wind may have varied across the training area.

The airplane's approved indication remains controlling in flight. Use eIAS to support postflight analysis, not to rewrite what the cockpit instrument required the pilot to fly.

Step 8: Conduct the collaborative assessment

Use the FAA four-part sequence.

Replay

Confirm the sequence and resolve the few material differences between the accounts.

Reconstruct

Ask what the learner could, would, or should have done differently. Explore the earliest useful cue, not merely the final error.

Reflect

Ask what the learner now understands about the maneuver, risk, aircraft, or decision.

Redirect

Decide how the lesson changes the next flight, simulator session, ground study, chair flying, personal minimum, or instructor demonstration.

Compare the learner's assessment with the instructor's assessment. The goal is not agreement for its own sake. The goal is a shared understanding of the current performance level and next objective.

Step 9: Choose the primary correction

The FAA instructor guidance says a comprehensive assessment does not need to be long or address every detail. The instructor may focus on the few major points or on what the learner can reasonably improve.

Prioritize in this order:

immediate safety or regulatory concern;
aircraft limitation or procedural error;
risk-management or decision issue;
earliest high-leverage performance deviation;
recurring pattern;
correction that the learner can recognize and act on;
item most connected to the next lesson objective.

Write the correction as:

Cue: what the learner should recognize;
Action: what the learner should do;
Result: what should improve;
Boundary: when to stop, ask, discontinue, or go around.

Example:

Cue: bank passes 30 degrees in the steep-turn entry. Action: establish the outside pitch reference and apply the planned power adjustment. Result: altitude remains stable as the selected bank is reached. Boundary: discontinue the maneuver if traffic, orientation, or aircraft control is not satisfactory.

Step 10: Recognize strengths and effective corrections

A constructive assessment includes what the learner did well, particularly behavior that should be repeated.

Identify:

a good preflight or risk decision;
an early go-around;
an accurate recognition of a deviation;
an effective correction;
improved workload management;
a consistent setup;
appropriate checklist use;
a strong question or self-assessment;
performance that transferred from simulator or ground preparation to the airplane.

Avoid empty praise. State what was effective and why it matters.

Step 11: Define the next lesson or practice plan

Record:

one primary objective;
supporting knowledge review;
aircraft or simulator environment;
instructor demonstration or coaching needed;
conditions needed for the task;
what the learner may practice independently, if authorized;
stop criteria;
evidence to capture;
the standard for successful completion;
one question to revisit.

If the learner is a student pilot, do not let a debrief note expand solo privileges. Solo activity remains subject to current endorsements, limitations, regulations, school procedures, conditions, and instructor authorization.

Step 12: Complete required records separately

After the instructional discussion, complete the records required for the operation and training program.

As applicable:

sign the pilot logbook for training given;
complete required endorsements using current guidance;
maintain the instructor records required by 14 CFR 61.189;
complete the school lesson record or approved syllabus documentation;
record stage-check or deficiency information through the approved process;
enter aircraft or equipment discrepancies through the proper system;
store screenshots, notes, telemetry, and debriefs according to privacy and retention policy.

A FlytWERX session, score, AI debrief, or shared note is supplemental unless the applicable regulation or approved school process expressly makes it part of the required record.

Short-form debrief summary

When time is limited, preserve these nine items:

lesson objective;
conditions that materially affected the result;
strongest behavior to repeat;
first meaningful deviation;
whether the learner recognized it;
instructor intervention required;
one primary correction;
next objective and stop criteria;
required records completed.

How FlytWERX can support the checklist

FlytWERX can organize flight sessions, structured maneuvers, flight paths, replay, performance feedback, notes, lesson history, AI-generated debriefs, instructor-student connection, and shared progress, subject to the current product version and privacy settings.

The product can help reduce the time spent reconstructing basic recorded events. It cannot replace the instructor's assessment of traffic awareness, control feel, coordination, checklist use, aircraft-specific technique, judgment, legal authorization, or required records.

Use FlytWERX to establish a common data picture, then conduct the professional debrief.

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 becomes more consistent, focused, and actionable within the available time. 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

Use the checklist on the next debrief and finish with one correction and one proof point for the next attempt. 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: Use the Debrief Workflow 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

How long should a CFI debrief take?

The FAA sources used here do not prescribe one universal duration. The debrief should be long enough to establish what happened, what mattered, and what changes next, but focused enough that the learner can act on it.

Should every deviation be discussed?

No. A comprehensive assessment need not treat every detail. Address safety and procedural concerns, then focus on the few points with the greatest learning value.

Should the student speak first?

Learner-centered assessment normally begins with the learner's replay. The instructor may change the sequence when immediate safety, recordkeeping, or learner needs require it.

Can FlytWERX automatically grade the whole lesson?

The product can organize recorded performance and support grading workflows. It cannot independently evaluate every knowledge, risk-management, procedural, coordination, communication, or judgment element.

Is this checklist a required instructor record?

No. It is an optional workflow. Complete all records required by the regulations, school, operator, and approved curriculum separately.

Sources