A last-minute instructor change should not erase the plan: Weather changes the schedule and a substitute CFI is assigned ten minutes before the lesson. The student spends the first half of the flight repeating last week's work because the handoff says only, "Continue landings."

Busy schools need a handoff that can survive instructor changes without losing the training plan.

A useful instructor handoff gives the next CFI enough accurate context to continue the training plan without making the student repeat the previous lesson simply to reconstruct what happened. It should identify the objective, what the student completed independently, where assistance was required, the most important risk or performance issue, the evidence supporting that assessment, the next action, and any current authorization or limitation that affects the lesson.

Record boundary: A handoff note is supplemental unless the school has explicitly made it part of an authorized record workflow. It does not automatically replace the student's logbook, instructor endorsement records, a Part 141 training record, a stage-check report, a safety report, a maintenance discrepancy, or another required school record.

Why handoffs fail in busy schools

Instructor changes are normal. A CFI may be unavailable, the student's schedule may shift, weather may create last-minute substitutions, an aircraft may move to another base, or a chief instructor may assign an independent review. The problem is not the change itself. The problem is continuity loss.

A weak handoff often sounds like:

• "Landings need work."
• "Almost ready to solo."
• "Watch the right steep turn."
• "Student did fine except for airspeed."
• "Continue where I left off."

Those statements may reflect a real observation, but they do not tell the next instructor:

• which lesson objective applied;
• which standard was used;
• whether the student was independent or heavily coached;
• when the first meaningful deviation began;
• whether the student recognized and corrected it;
• whether a safety or authorization issue remains open;
• what the next instructor should test, demonstrate, or continue;
• what information is an observation, a student statement, a calculated value, or an instructor hypothesis.

The result is repeated setup, conflicting techniques, frustrated students, and records that do not explain the training decision.

Step 1: Start with the official training context

Before writing a handoff, identify the actual training framework:

• Part 61 or an approved Part 141 course;
• course, syllabus, stage, lesson, and revision when applicable;
• aircraft and configuration;
• dual, solo, simulator, ground, or combined lesson;
• lesson objective and completion standard;
• current endorsements, authorizations, and instructor-entered limitations;
• records that must be completed separately.

Do not write "ready for solo" unless the authorized instructor has made and documented the required determination. A substitute instructor needs the current facts, not an informal promise.

Step 2: State the objective in operational terms

The objective should tell the next instructor what the student was expected to do and why it matters.

Weak objective:

Work on go-arounds.

Better objective:

Recognize an unstable or obstructed landing condition, announce the decision without prompting, apply the aircraft-specific go-around procedure, establish a safe climb, manage configuration and directional control, and remain clear of conflicting runway traffic.

The improved objective gives the next instructor a cue, action, performance result, and real-world reason.

Step 3: Separate independent performance from assisted performance

A handoff should state what the student did without help and what required support.

Use a consistent vocabulary such as:

• independent;
• completed after a question;
• completed after a direct verbal cue;
• completed with continuous coaching;
• completed after demonstration;
• required instructor control input;
• discontinued or converted to another maneuver.

This does not diminish the student. Instruction is expected. The label simply prevents the next CFI from assuming that a completed maneuver was independently managed.

Step 4: Identify the first meaningful deviation

Do not describe only the final result. State where the sequence first stopped matching the plan.

Examples:

• The short-field landing went long because the approach remained above the planned energy state before the threshold.
• The right steep turn lost altitude after bank continued increasing beyond the selected target.
• The student overshot the assigned heading because rollout was not initiated until the target heading appeared.
• The go-around climb was unstable because the landing decision was delayed, increasing workload close to the ground.
• The crosswind landing drifted because the correction was relaxed during the flare, not because the entire approach was poor.

The first deviation gives the next instructor a more useful place to begin.

Step 5: Preserve the most important risk decision

A handoff should include the risk-management result, even when the aircraft-control trace looked acceptable.

State whether the student:

• cleared the area appropriately;
• chose a suitable runway and training area;
• recognized traffic or an occupied runway;
• initiated a timely go-around;
• stayed within weather, aircraft, school, and instructor limits;
• discontinued an unsafe or unsuitable maneuver;
• managed distraction and workload;
• made a sound continue, divert, delay, or stop decision.

A numeric score cannot substitute for this information.

Step 6: Cite the evidence and its source

A handoff is more useful when it distinguishes what was directly observed from what was recorded or inferred.

Possible evidence includes:

• instructor observation;
• student replay or explanation;
• official lesson grade;
• aircraft or simulator data;
• FlytWERX flight path and maneuver history;
• direct aircraft airspeed data;
• GPS-derived data;
• FlytWERX estimated indicated airspeed;
• a manually entered note or event marker;
• a school-approved checklist or stage-check result.

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.

Step 7: State one primary correction

The next instructor should not receive ten equal priorities.

A useful correction includes:

• the phase or cue;
• the action to take;
• the expected result;
• the evidence that will show improvement.

Example:

As bank passes 30 degrees in the right steep turn, establish the outside pitch reference and planned power change before reaching the target bank. Improvement will be shown by a smaller altitude trend during entry and less need for verbal prompting.

This is more actionable than "hold altitude better."

Step 8: Define the next lesson request

End the handoff with a clear request:

• continue the planned lesson;
• verify a specific skill independently;
• demonstrate an alternate explanation or technique;
• conduct an authorized progress or stage review;
• repeat one task under comparable conditions;
• assess whether an intervention is working;
• resolve a record or authorization issue before flight;
• escalate to the chief instructor or another authorized process.

The next CFI should know what decision the handoff is intended to support.

The minimum handoff structure

A CMS-friendly or system-based handoff can use these headings.

Student and training context

Course, stage, lesson, aircraft, date, instructor, operating conditions, and type of session.

Lesson objective

The exact objective and controlling standard.

Completed independently

Tasks or decisions the student performed without prompting.

Assistance required

Questions, cues, demonstrations, continuous coaching, or control inputs used.

First meaningful deviation

The earliest point at which the performance moved away from the plan.

Risk-management result

The most important traffic, weather, runway, altitude, workload, or decision outcome.

Evidence

The official grade, observation, replay, trace, score, note, or other source used, with source quality and limitations.

Primary correction

One specific cue and action for the next attempt.

Next lesson or decision

What the receiving instructor should continue, test, demonstrate, or resolve.

Authorization and open items

Current endorsements or limitations, unresolved safety or maintenance matters, and required records that remain incomplete.

How FlytWERX can support connected handoffs

FlytWERX is designed to connect scheduling, training programs, lesson plans, grading, stage checks, student history, performance data, notes, messaging, and instructor-student review according to the school's enabled configuration. That connected context can reduce the need for the receiving instructor to reconstruct basic events from memory.

A FlytWERX-supported handoff can link or reference:

• the scheduled lesson and assigned resources;
• the applicable program, syllabus, stage, or lesson;
• maneuver attempts and full flight path;
• instructor notes and grading;
• student replay or debrief;
• the primary deviation and next correction;
• a stage-check or intervention workflow where enabled;
• the next assigned lesson or follow-up.

The product should not be described as replacing the instructor's professional handoff, the school's official record, or required signatures and endorsements. Product roles, access, privacy settings, retention, and school workflow must be verified before publication and implementation.

Protect student privacy and limit unnecessary detail

A handoff should contain what the next authorized instructor needs to continue training. It should not become a broad narrative about the student's personality, health, finances, or personal circumstances.

Use neutral, task-related language. For example:

• "Required three verbal cues to recognize increasing bank" is better than "does not pay attention."
• "Missed two lessons and had a 24-day gap" is better than speculating about motivation.
• "Reported fatigue before the lesson and elected not to fly" is better than making a medical conclusion.

Follow the school's privacy policy, role-based access, record-retention rules, and applicable law. Safety, maintenance, and medical matters may require separate authorized processes.

A realistic handoff scenario

A student normally flies with one instructor but is scheduled with a substitute after weather compresses the week. The prior lesson record says "normal landings - satisfactory."

The detailed handoff shows:

• stabilized approach and centerline tracking were independent in calm wind;
• flare timing improved across four attempts;
• the student did not recognize an occupied-runway scenario until prompted;
• the instructor initiated both go-arounds;
• the primary correction is to verbalize the prebriefed runway-clearance gate and act without waiting for a cue;
• the next instructor is asked to create one realistic traffic conflict and assess the decision independently;
• no solo authorization change has been made.

The substitute instructor can now continue the learning objective instead of repeating an entire landing lesson merely to discover the same open item.

This scenario is illustrative, not a customer record or prevalence claim.

Common handoff failures

Copying the entire debrief

A long transcript can hide the primary correction. Link to supporting detail and summarize the decision-relevant facts.

Passing a diagnosis instead of evidence

Avoid labels such as lazy, unsafe, weak, or not teachable. State the observed behavior, context, intervention, and result.

Mixing official and supplemental records

Identify which entry is the authoritative school record and which content is a handoff, note, replay, or analytics view.

Omitting the level of assistance

A completed task is not necessarily independent.

Failing to state the next decision

The receiving instructor should know whether the goal is continuation, verification, remediation, stage-check preparation, or escalation.

Sharing more data than the role requires

Access should follow the student's training need, school policy, privacy settings, and authorized role.

What a school should evaluate before adopting this workflow

What should a pilot prove?

A useful pilot should show that handoffs reduce repeated setup and preserve the next training decision. Define the baseline, responsible reviewers, representative users, support effort, errors, workarounds, privacy risks, and stop criteria before the first session. At the decision meeting, choose to scale, modify, extend, or stop.

How should records and data be handled?

Inventory the official records, supplemental evidence, permissions, retention requirements, correction process, and export needs before data moves. Do not assume every historical record or vendor format can be imported automatically. Test a representative migration, preserve the legacy system for its required retention period, and document the authoritative system for every record class.

FlytWERX school pricing is quote-based. For the complete buying framework, use the pricing and plan comparison, flight-school implementation, data migration and record continuity, ROI measurement, and software comparison. The controlled pilot method is covered in How to Pilot New Technology at a Flight School.

Put this into practice

Test one substitute-instructor handoff and record what the next CFI still had to reconstruct. 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: See Shared Student Context.

Important implementation and governance limits

This framework is educational and does not make a student, instructor, stage-check, record, privacy, security, compliance, procurement, or quality determination for a specific school. Apply current regulations, approved courses, school procedures, authoritative records, contracts, privacy and security requirements, and qualified human review. Verify the production FlytWERX configuration before operational use.

Frequently asked questions

Is a CFI handoff required by one universal FAA form?

The FAA sources used here do not prescribe one universal handoff form for every flight school. Required records and endorsements still apply, and Part 141 schools must follow their approved course and recordkeeping process.

Should the next instructor rely on the previous instructor's conclusion?

Use it as context, then conduct an independent, qualified assessment appropriate to the lesson. Preserve the evidence and level of assistance so the receiving instructor understands the basis for the conclusion.

Can FlytWERX replace the lesson record?

Do not assume so. FlytWERX can support connected lesson, performance, note, and school workflows. The school must verify each official-record use, required field, signature, retention rule, access role, and approval.

How long should a handoff be?

Long enough to preserve the objective, independence, first deviation, risk result, evidence, correction, next action, and authorization status. Supporting detail can remain linked rather than copied into the summary.

Should the student see the handoff?

Schools should define appropriate transparency and access. Students benefit from clear objectives and next actions, but access to staff notes and school records should follow policy, privacy, and legitimate training needs.