Continuity breaks quickly: A substitute instructor sees "landings need work" in the previous note. The first half of the lesson is spent reconstructing what that means.

Progress across instructors depends on preserving the objective, assistance level, first deviation, evidence, and next action - not just the final grade.

Track student progress across instructors by preserving the same training objective, standard, operating context, level of instructor support, evidence, risk-management observations, and next action from one lesson to the next. A maneuver score or lesson grade alone is not enough. The next instructor needs to know what the student was asked to do, what occurred, what help was required, and what should happen next.

Recordkeeping boundary: A shared progress record can improve continuity, but it does not replace pilot logbooks, instructor records, endorsements, approved syllabus records, stage-check records, or other documentation required by regulation or school procedure.

Why instructor continuity matters operationally

Students often fly with more than one instructor because of schedules, weather, aircraft availability, stage checks, instructor turnover, specialty training, or school structure. Multiple instructors can benefit the learner by providing broader experience and another perspective. Continuity breaks down when each lesson restarts from an incomplete handoff.

A weak handoff can lead to:

• repeating a lesson without understanding why;
• practicing a different objective under the same maneuver name;
• conflicting technique presented as conflicting standards;
• missing an important risk-management concern;
• changing targets without documenting the change;
• giving the student too much or too little instructor support;
• treating one good attempt as stable proficiency;
• losing the correction selected in the prior debrief;
• confusing supplemental app records with required records.

The purpose of shared progress is not to make every instructor teach identically. It is to preserve the facts and standards needed for the next instructor to exercise informed judgment.

Track eight dimensions, not one grade

1. Lesson objective

State what the student was expected to learn or perform.

Examples:

• recognize the stabilized-approach gate and initiate an unprompted go-around;
• establish a private-pilot steep turn with the planned outside reference and power change;
• maintain coordination during power-on stall entry;
• control runway track and alignment in a moderate crosswind;
• complete a normal pre-solo traffic pattern with reduced instructor prompting.

A generic label such as "landings" does not tell the next instructor what the lesson was testing.

2. Applicable standard

Identify the source:

• current ACS task;
• POH/AFM procedure;
• school syllabus or stage standard;
• instructor developmental target;
• approved operating procedure;
• regulatory requirement;
• solo endorsement limitation;
• scenario or risk-management objective.

Separate a required standard from an instructor technique. If an instructor changes a target, record the reason.

3. Conditions and context

Record factors that materially affected performance:

• aircraft and configuration;
• runway or practice area;
• wind, gusts, turbulence, ceiling, visibility, temperature, and density altitude;
• traffic and ATC workload;
• dual, solo, simulator, or device session;
• equipment and data source;
• abnormal interruption or lesson change;
• instructor demonstration or intervention.

A student who performs well in calm conditions may still be developing the ability to adapt to a gusty crosswind or increased workload. Context prevents an isolated grade from being overgeneralized.

4. Level of instructor support

State what the learner did independently and what required help.

Use clear language such as:

• instructor demonstrated;
• instructor talked through each step;
• instructor prompted the setup;
• instructor prompted recognition;
• instructor prompted the correction;
• instructor intervened for safety;
• learner completed without assistance;
• learner recognized and corrected the deviation independently;
• event was not observed.

The FAA Aviation Instructor's Handbook provides a useful performance progression for maneuvers and procedures: Describe, Explain, Practice, Perform, and Not observed. Its risk-management progression uses Explain, Practice, and Manage-Decide. A school may adopt another approved vocabulary, but every instructor should know exactly what each level means.

5. Performance evidence

Use the evidence available:

• instructor observation;
• learner replay;
• flight or simulator data;
• score details rather than only the total;
• event notes;
• stage or lesson records;
• screenshots or replay links;
• checklist or procedure observations;
• oral knowledge and scenario discussion;
• required records.

Identify what the evidence cannot show. A flight path may show drift but not whether the pilot saw traffic. Bank and heading may look acceptable while coordination is poor.

6. Risk-management and decision performance

Record decisions, not only maneuver tolerances.

Examples:

• selected an appropriate runway;
• identified a wind or performance limit;
• cleared the practice area;
• recognized a deteriorating approach;
• initiated a go-around without prompting;
• continued after the instructor's prebriefed gate;
• became task-saturated during radio work;
• selected a safer alternative;
• needed prompting to identify traffic or a hazard.

The next instructor should know whether the student can manage the scenario, not only whether the trace remained inside a band.

7. Recognition and correction

Record:

• first meaningful deviation;
• whether the learner noticed it;
• how long recognition took;
• whether a prompt was required;
• correction applied;
• whether the correction worked;
• whether it created another deviation;
• whether the pattern repeated.

This information distinguishes a student who maintains the standard independently from one who reaches the same result after instructor coaching.

8. Next training action

End every lesson record with one clear next objective.

Include:

• cue;
• action;
• expected result;
• practice environment;
• required instructor support;
• conditions or limitations;
• stop criteria;
• evidence to review.

The next instructor should be able to read the action and understand how to continue the lesson without guessing.

Use a common rating vocabulary

A shared vocabulary reduces ambiguity.

Describe

The learner can state the main characteristics but needs assistance to execute successfully.

Explain

The learner understands the concepts and procedure but still needs assistance to execute successfully.

Practice

The learner can plan and execute, with coaching or assistance correcting deviations.

Perform

The learner completes the activity without instructor assistance, identifies and corrects deviations promptly, and leaves no doubt about successful completion in the applicable conditions.

Not observed

The item was not accomplished or required.

For risk management, use the FAA progression:

• Explain;
• Practice;
• Manage-Decide.

Do not force these terms into an A-through-F grading mindset. They describe a level of learning and support, not personal worth.

Separate four records

A flight school may have several records serving different purposes.

Pilot logbook

Records aeronautical experience and training entries as applicable.

Instructor record

Contains the records required of the flight instructor, including certain endorsements and test recommendations under 14 CFR 61.189.

School or approved curriculum record

Documents lessons, stage checks, syllabus progress, deficiencies, acknowledgments, and other items required by the school's operating rules or approved course.

Supplemental performance record

May include FlytWERX sessions, telemetry, maneuver breakdowns, scores, notes, shared targets, replays, AI debriefs, or instructor comments.

Do not assume the supplemental record satisfies the legal or approved-school requirement. Define where the official record lives and who is responsible for completing it.

A continuity workflow for each lesson

Before the lesson

The incoming instructor reviews:

• current objective;
• previous instructor's primary correction;
• recent conditions and aircraft;
• student support level;
• unresolved safety or procedural concerns;
• applicable endorsements and limitations through the official source;
• required syllabus or stage items;
• selected FlytWERX replay or evidence.

During the briefing

Instructor and student confirm:

• objective;
• standard;
• aircraft procedure;
• expected cues;
• stop criteria;
• data source;
• what will show improvement.

During the flight

The instructor records significant prompts, interventions, decisions, and changes to the plan. Avoid trying to write every minor correction while safety and instruction require attention.

During the debrief

Use replay, reconstruct, reflect, and redirect. Compare the current result with recent comparable attempts without ignoring changes in wind, aircraft, workload, or instruction.

At handoff

Record the principal strength, first meaningful deviation, required support, risk-management issue, one next action, and official records completed.

How to compare performance across instructors fairly

Use comparable objectives

Two sessions labeled "steep turns" may have different objectives. One may emphasize basic entry. Another may assess ACS-level performance under distraction. Compare only what was actually trained or evaluated.

Preserve conditions

Wind, turbulence, aircraft loading, runway, traffic, temperature, density altitude, and instructor workload can change the result.

Record instructor support

A high score after several prompts is different from the same score without assistance.

Review the underlying elements

Do not compare only total scores. Review altitude, heading, bank, speed, recognition, correction, procedure, risk management, and other relevant dimensions.

Use trends, not isolated extremes

A best attempt shows capability. A sequence of comparable attempts shows repeatability. An outlier may require explanation rather than a new label.

eIAS continuity across instructors

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 accuracy specification or guarantee.

When instructors compare airspeed performance across sessions, preserve:

• wind source and time;
• local wind adjustment;
• temperature source;
• aircraft indication comparison;
• aircraft and configuration;
• maneuver phase;
• whether the speed field was aircraft IAS, simulator airspeed, groundspeed, or eIAS.

The approved aircraft indication remains controlling in flight. A new instructor should not assume that two eIAS traces have the same quality without checking their inputs.

A realistic handoff example

Lesson objective:

Establish and hold a 45-degree steep turn in both directions while maintaining outside orientation, coordination, and the private-pilot performance standard.

Conditions:

C172, moderate turbulence, dual lesson, right turn completed first. FlytWERX live-flight session with current forecast winds updated using the instructor's more representative training-area estimate.

Student performance:

Left turn met the selected numeric targets with one altitude prompt. Right turn lost altitude during establishment. Student recognized the loss after the vertical-speed trend developed and made an abrupt pitch correction that increased bank variation.

Instructor support:

Prompted outside reference on the left. Demonstrated right-turn entry after the first attempt. Student then repeated the entry and first 90 degrees with improved altitude control.

Risk management:

Area clearing completed. Student's scan narrowed inside during the first right turn. No traffic conflict. Instructor redirected attention outside.

Primary correction:

As bank passes 30 degrees in the right entry, establish the outside pitch reference and planned power before reaching 45 degrees; cross-check altitude after the bank is stable.

Next objective:

Begin with one right entry and first 90 degrees before completing full turns. Assess outside scan and whether the student recognizes the vertical trend without prompting.

This note gives the next instructor continuity without claiming that the student is checkride-ready or assigning an unsupported cause.

How FlytWERX can support shared progress

Current public FlytWERX materials describe instructor-student connection, shared flight results, maneuver history, lesson-plan and target syncing, flight review, grading workflows, notes, training history, and school features. Product capabilities can change, and schools may configure them differently.

Use the product to:

• preserve a common session and replay;
• link the objective and target to the lesson;
• show the underlying maneuver elements;
• record instructor support and notes;
• carry one correction into the next lesson;
• compare repeated attempts;
• support a consistent handoff.

Before publication or implementation, the FlytWERX product owner and school should verify the exact workflow, role permissions, instructor overrides, official-record integrations, privacy settings, and retention behavior.

Privacy and access

FlytWERX's public privacy policy describes lessons and AI-generated debriefs as private by default and provides Private, Friends, and Public visibility choices for user-generated content. It also describes stored maneuvers, lessons, sessions, notes, feedback, telemetry, and debriefs.

A school should define:

• who can view student performance;
• which records are official;
• who may change grades or standards;
• how corrections and overrides are documented;
• how long records are retained;
• what may be shared with another instructor;
• how student consent and applicable law are handled;
• how exports, screenshots, and AI-generated content are used.

Do not place sensitive training data into an informal handoff channel that is not approved for the purpose.

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 a new instructor can continue the plan without spending half the lesson reconstructing it. 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

Rewrite the last handoff with the objective, assistance, risk, evidence, and next lesson request. 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 Progress 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 every instructor use the same technique?

No. Standardize the objective, procedure boundaries, evidence, rating meaning, and documentation. Instructors may use different effective teaching techniques within aircraft, regulatory, and school requirements.

Can a shared score replace the instructor handoff?

No. The next instructor also needs context, support level, risk decisions, recognition, correction, and the next objective.

What should be reviewed before a substitute instructor flies with the student?

Review official authorization and limitations, the lesson or syllabus objective, recent performance, safety concerns, previous instructor support, the selected correction, and any relevant aircraft or data context.

Should a school average scores across all conditions?

A broad average can hide meaningful differences. Compare task-level trends under reasonably comparable conditions and preserve the context.

Does FlytWERX determine whether a student may solo or advance?

No. An authorized instructor and the school's applicable process determine training progression and endorsements. FlytWERX can support the evidence and continuity used in that professional decision.