A handoff must survive the next schedule change: The next CFI receives a note that says, "Almost ready to solo. Watch the right landing." That is not enough to plan a safe lesson.

A strong handoff states the objective, what was independent, where help was needed, the open risk, the evidence, and the next decision.

A useful flight instructor handoff note tells the next instructor what the lesson was intended to accomplish, what the learner completed independently, where prompting or intervention occurred, which risk or performance issue mattered most, what evidence supports the assessment, and what should happen next. It should support continuity without becoming a substitute for the pilot logbook, instructor records, endorsements, approved syllabus records, or the receiving instructor's own assessment.

Handoff boundary: This is a FlytWERX editorial template, not an FAA-mandated form. Use the applicable regulation, current endorsement guidance, school record, approved syllabus, and local policy for required documentation.

Why instructor handoffs often fail

A weak handoff usually contains a grade and a vague comment:

"Steep turns need work. Practice landings next time."

That note leaves the receiving instructor to guess:

what standard applied;
which direction or phase caused the problem;
whether the learner recognized it;
how much prompting occurred;
whether the issue was control skill, knowledge, risk management, or setup;
whether conditions changed the result;
what correction was already taught;
what the student may legally and safely practice;
whether required records and endorsements are current.

A detailed data dump can fail in the opposite direction. A link to an entire flight, several scores, every graph, and a long narrative may contain the answer without making it easy to find.

The better handoff is brief, structured, factual, and tied to the next instructional decision.

What the FAA guidance contributes

The FAA Aviation Instructor's Handbook says effective assessment should be factual, objective, constructive, specific, organized, and aligned with the lesson's completion standards. It also explains that a comprehensive assessment does not need to be long or discuss every detail.

The FAA learner-centered assessment model uses four stages:

replay what happened;
reconstruct what could or should have been different;
reflect on what the learner understood;
redirect the next lesson or decision.

A handoff note should preserve the result of that process, not merely a grade.

Keep three records separate

The required aviation record

Depending on the activity, this may include:

the pilot's training or aeronautical-experience logbook entry;
instructor signatures;
required endorsements;
instructor records required by 14 CFR 61.189;
approved school or curriculum records;
stage-check or deficiency documentation;
aircraft discrepancy records through the appropriate system.

Under 14 CFR 61.189, a flight instructor signs the logbook of each person to whom the instructor gives flight or ground training and maintains specified records of certain solo and test endorsements. The required endorsement records must be retained for at least three years. Reopen the current regulation before publication or operational use.

The instructional handoff

This is the concise continuity note for the next instructor. It explains the learner's current performance, level of assistance, main risk or deviation, and next objective.

The supporting evidence

This may include:

a FlytWERX session or maneuver replay;
a relevant screenshot;
a score component;
an instructor annotation;
a weather or wind record;
a simulator session;
an aircraft or school record that the recipient is authorized to access.

The handoff should point to the smallest amount of evidence needed. It should not copy protected or unnecessary personal information into another system.

Step 1: Identify the student, course, and lesson context

Record only the context the receiving instructor needs.

Include:

learner name or approved identifier;
certificate or rating sought;
course, stage, or syllabus lesson;
date;
instructor;
aircraft or simulator type;
dual, supervised review, stage check, or other activity;
planned lesson objective;
revised objective if the lesson changed.

Do not use a generic label such as "Lesson 12" without the objective. Different instructors may interpret the number differently, and the lesson may not have followed the original plan.

Step 2: State the applicable standard and aircraft procedure

Name the standard used to assess the lesson.

Possible sources include:

the current ACS task;
an approved syllabus completion standard;
a school grading rubric;
a developmental lesson target;
the current POH/AFM procedure;
an instructor-prescribed practice objective.

Do not imply that every early lesson should be graded as a checkride. State whether the target was introduction, practice with coaching, independent performance, or checkride-level consistency.

Step 3: Record the conditions that changed the interpretation

Include only material context, such as:

wind and gusts;
turbulence;
runway or surface;
density altitude;
traffic and ATC workload;
aircraft or equipment difference;
simulator versus aircraft;
lesson interruption;
instructor demonstration or control intervention;
data-source problem.

Avoid using the handoff to make medical, maintenance, or causal conclusions beyond the instructor's qualifications and evidence. Use the proper school, maintenance, or safety-reporting process when required.

Step 4: Describe what the learner completed independently

The receiving instructor needs to know what the learner can already do without prompting.

Use observable language:

"Established the short-field approach configuration and target without prompting."
"Recognized the unstable approach at the prebriefed gate and initiated the go-around."
"Held the left steep turn within the lesson altitude and bank targets after one setup reminder."
"Completed the checklist correctly but required a prompt before clearing the area."

Avoid broad labels such as "good," "weak," "almost ready," or "unsafe" without the supporting behavior and context.

Step 5: Mark prompting, assistance, and intervention

Performance completed with assistance should not look identical to independent performance.

Record:

verbal cue;
leading question;
demonstration;
repeated coaching;
instructor control input;
maneuver termination;
go-around direction;
safety intervention;
postflight explanation only.

Use neutral wording. The purpose is continuity, not blame.

Example:

"The learner noticed the bank increase but did not connect it to the altitude trend until prompted. After the prompt, the correction was timely and did not create a secondary deviation."

Step 6: Identify the first meaningful deviation

Do not hand off only the final result.

A long landing may begin with excess eIAS or a high flight path. An overshot heading may begin with a late rollout lead. An unstable steep turn may begin during setup rather than after the altitude moves.

Record:

phase where the deviation began;
first recorded or observed change;
whether the learner noticed it;
time or event marker when useful;
correction attempted;
whether the correction worked;
relevant missing context.

Use "possible contributor" or "working explanation" when the cause is not established.

Step 7: Separate knowledge, risk management, and skill

A single grade can hide important differences.

Knowledge

State whether the learner could explain:

the maneuver's operational purpose;
the aircraft procedure;
the relevant aerodynamics or systems;
the cue that should trigger action;
the limitation or discontinuation condition.

Risk management

State whether the learner:

cleared the area;
selected an appropriate runway, altitude, or practice area;
considered wind and aircraft performance;
maintained traffic awareness;
used a prebriefed decision gate;
recognized when to discontinue, divert, or go around;
managed workload and distraction.

Skill

State the task-specific result and level of assistance:

setup;
aircraft control;
applicable performance targets;
recognition and correction;
recovery;
repeatability.

Step 8: Link one useful piece of evidence

Select evidence that supports the main handoff point.

Examples:

a marked steep-turn entry showing bank and altitude;
a final-approach segment showing eIAS and vertical path;
a ground track showing where wind correction changed;
a go-around timeline from decision marker through stable climb;
a note showing the learner's own explanation;
a comparison of two attempts under similar conditions.

Do not require the next instructor to review an entire session before understanding the note.

Step 9: Describe FlytWERX eIAS accurately when airspeed matters

For supported live-flight reviews, FlytWERX calculates estimated indicated airspeed using GPS-derived speed, current winds aloft, temperature, and the active wind correction. A pilot or instructor can enter more representative winds for the local 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 accuracy specification or universal guarantee.

When an eIAS trace affects the handoff, record:

wind source and update time;
whether representative training-area winds were entered;
temperature source;
maneuver and flight phase;
whether the trace was compared with the aircraft indication;
any local wind, maneuvering, sensor, or timing factor that could affect the estimate.

Use `eIAS`, not `IAS`, in the note. The airplane's approved indication remains controlling in flight.

Step 10: Write one primary correction

Choose the correction with the greatest effect on safety, understanding, or repeatability.

Write it as:

Cue: what the learner should notice;
Action: what the learner should do;
Result: what should change;
Boundary: when to discontinue or ask for help.

Example:

Cue: the selected bank is approaching 30 degrees during steep-turn entry. Action: establish the outside pitch reference, apply the planned power change, and cross-check altitude before the target bank is reached. Result: altitude remains stable through entry. Boundary: discontinue if traffic, orientation, or aircraft control is not satisfactory.

Do not hand off five unrelated corrections as equal priorities. Put secondary points in a short supporting note only when the next instructor needs them.

Step 11: Define the next lesson objective and proof point

Tell the receiving instructor what to verify, not exactly how to teach.

Include:

next objective;
planned environment;
demonstration or review needed;
conditions needed;
level of independence expected;
stop criteria;
proof point for progress;
unresolved question.

Example:

"Next objective: repeat left and right steep turns after one instructor demonstration. Proof point: stable altitude through entry, recognition of any bank increase before prompting, and rollout on the assigned heading on two comparable attempts."

The receiving instructor still adapts the lesson to current conditions and the learner's actual performance.

Step 12: Confirm authorization and required records separately

Before the handoff is considered complete, verify the authoritative source for legal or school status.

For a student pilot, this may include:

current pre-solo training and proficiency requirements;
current make-and-model endorsement;
current solo endorsement and its limitations;
route, airport, cross-country, weather, or other applicable endorsements;
school dispatch or authorization;
instructor-imposed limitations;
current aircraft and operating conditions.

A FlytWERX note, score, shared target, or session does not create or expand solo privileges. Use the current pilot certificate, logbook, endorsement, approved school record, regulation, and instructor authorization.

Also confirm that required training entries, endorsements, instructor records, school records, and discrepancy reports were completed in their proper systems.

Step 13: Share only with authorized people

The FlytWERX privacy policy describes visibility controls and states that lessons and AI-generated debriefs are private by default. The current product and organization settings should be verified before operational use.

Before sharing a session or note:

confirm the intended recipient;
use the minimum necessary information;
avoid unrelated personal information;
remove or de-identify information used for public examples;
follow school, operator, and retention policy;
verify whether AI-generated text is included;
correct unsupported or outdated statements;
preserve the student's access and privacy rights as applicable.

Do not assume that a public link, screenshot, exported file, or copied note inherits the original privacy setting.

A concise handoff template

Use the following paragraph-and-bullet structure in a CMS, lesson record, or approved note field.

Student and lesson

Student or approved identifier:
Certificate/rating and stage:
Date, instructor, aircraft/simulator:
Lesson objective:
Applicable standard:

Material conditions

Wind/weather/runway/practice area:
Aircraft/equipment/data-source factors:
Instructor demonstrations or lesson changes:

Performance

Completed independently:
Prompting or intervention:
First meaningful deviation:
Recognition and correction:
Knowledge result:
Risk-management result:
Skill result:

Evidence

FlytWERX session or maneuver:
Relevant marker or screenshot:
Data labels and limitations:
eIAS wind/temperature context, when relevant:

Redirect

Primary correction:
Cue, action, result, and boundary:
Next lesson objective:
Proof point:
Open question:

Records and access

Required records completed:
Authoritative endorsement/authorization source checked:
Recipient and privacy setting verified:

Illustrative handoff note

The following example is fictional and is included only to demonstrate the structure. It is not a customer record or a claim about typical performance.

Student and lesson

Private-pilot student, pre-solo pattern lesson, dual in the training airplane. Objective: identify an unstable normal approach and make a timely go-around while maintaining directional control.

Material conditions

Moderate crosswind with gusts. Runway traffic required one spacing adjustment. FlytWERX session recorded position, ground track, heading, altitude, vertical speed, bank, pitch, groundspeed, and eIAS. Local training-area wind correction was entered before the lesson.

Performance

The student established the first two approaches with minimal coaching. On the third approach, the flight path became high and eIAS remained above the lesson target. The student verbally identified excess energy but continued below the prebriefed gate until the instructor asked whether the approach still met the plan. The student then initiated the go-around, maintained directional control, and stabilized the climb. The instructor prompted the decision but did not manipulate the controls.

Evidence

Review the third approach from the point where the vertical path diverges through stable climb. The useful fields are eIAS, altitude/vertical path, vertical speed, heading, and ground track. The trace does not establish flap position, power, radio calls, traffic position, or control feel.

Redirect

Primary correction: use the prebriefed gate as a decision point rather than a discussion point. Cue: the approach is outside the path or speed target at the gate. Action: initiate the aircraft-specific go-around procedure without waiting for instructor confirmation. Result: the descent stops and a stable climb is established earlier. Boundary: follow ATC instructions and maneuver laterally only as necessary for traffic, runway visibility, obstacles, or local procedures after aircraft control and the climb are established.

Next objective: two normal approaches in comparable conditions with an independent continue-or-go-around decision at the gate. The receiving instructor should first confirm the student's explanation of the gate and the POH/AFM go-around sequence.

Records and access

Training entry and lesson record completed. The instructor record and any endorsement status remain in the authoritative systems. Session shared only with the student and assigned instructors.

How FlytWERX can support instructor continuity

FlytWERX can help students and instructors preserve structured maneuver sessions, replay, flight paths, notes, lesson history, performance feedback, shared progress, and current instructor-student connections, subject to the production version and privacy settings.

A good workflow is:

record or select the relevant session;
mark the event or maneuver;
add the learner's replay;
add the instructor's factual assessment;
identify the primary correction;
set the next objective or target;
share with the authorized instructor;
complete required records in their authoritative systems.

FlytWERX can reduce the loss of instructional context. It does not remove the receiving instructor's duty to brief the learner, verify the record, assess current performance, check current authorization, and adapt to present conditions.

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 next CFI can understand the objective, assistance, risk, evidence, and next action. 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

Replace one vague handoff note with a complete, source-labeled summary the next instructor can use. 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: Create a Clearer Instructor Handoff 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

Is a CFI handoff note required by the FAA?

The FAA sources used here do not prescribe this specific handoff template. Required training entries, endorsements, instructor records, and school records still apply. The handoff is a supplemental continuity tool.

Can the next instructor rely on the prior instructor's grade?

The prior assessment is useful context, but the receiving instructor should verify the standard, conditions, level of assistance, current authorization, and present performance.

Should the handoff include every graph and score?

No. Link the smallest amount of evidence that supports the primary point. The full session can remain available for deeper review.

How much detail belongs in the note?

Enough to identify the objective, context, independent performance, assistance, first meaningful deviation, risk result, primary correction, and next proof point. A comprehensive note does not need to be long.

Can a shared FlytWERX target authorize solo practice?

No. Solo privileges depend on current regulations, endorsements, limitations, school procedures, conditions, and instructor authorization documented in the proper source.

Should eIAS be copied into the note as aircraft IAS?

No. Label it as FlytWERX eIAS. Record the wind and temperature context when the estimate affects the assessment, and keep the airplane's approved indication controlling in flight.

Can AI-generated debrief text be used in a handoff?

It can be used only after a qualified person verifies the facts, data labels, aircraft and maneuver context, causal statements, privacy, and consistency with the applicable procedure and standard. Do not hand off unreviewed AI text as instructor judgment.

Sources