The student hears two kinds of truth: One CFI says a technique is required. Another says it is only a preference. The student no longer knows whether the disagreement involves regulation, the ACS, the POH, school policy, or teaching style.

A clear debrief separates those layers before it evaluates performance.

A clear flight debrief identifies the source of every important statement. Separate what is required by regulation, what the POH/AFM or approved procedure requires, what the ACS or lesson-completion standard evaluates, what the instructor teaches as a technique, and what safety boundary caused an intervention or discontinuation. This prevents instructor preferences from being presented as FAA rules and prevents numeric tolerances from being treated as complete definitions of safe operation.

Core rule: Before saying "you have to," name the source. If the statement is a technique, call it a technique. If it is a safety decision, explain the condition and why intervention was necessary.

Five layers belong in the debrief

Although instructors often use the shorthand technique, standard, and safety, accurate instruction usually requires five layers.

1. Regulation or authorization

This layer answers what the current rules allow, require, or prohibit.

Examples include:

• pilot eligibility and privileges;
• student-solo endorsements and limitations;
• required pilot logbook entries;
• instructor records;
• Part 141 school records and approved-course requirements;
• operating rules that apply to the flight.

The instructor should cite the current rule or official source when the distinction matters. Do not rely on a remembered version of a regulation that may have changed.

2. Aircraft or approved procedure

This layer answers how the particular aircraft or approved operation is to be conducted.

Sources include:

• POH/AFM;
• aircraft limitations;
• approved checklist;
• operating manual;
• manufacturer supplement;
• approved school or operator procedure;
• ATC instruction or published procedure when applicable.

Examples include:

• target speeds;
• flap or gear sequence;
• power settings;
• emergency procedure;
• configuration limitations;
• demonstrated or published crosswind information;
• weight and performance limits.

A generic article cannot replace the current aircraft procedure.

3. Performance standard

This layer answers how the task is evaluated.

Possible standards include:

• the current Airman Certification Standards;
• an approved Part 141 syllabus completion standard;
• a school lesson-completion standard;
• a stage-check standard;
• a developmental objective set by the instructor.

A performance standard may include numeric tolerances, procedures, risk management, knowledge, and judgment. The numeric portion is not the whole task.

4. Instructor technique

A technique is one acceptable method for achieving the objective within the regulatory, aircraft, and program boundaries.

Examples include:

• a particular outside visual reference;
• a verbal flow or callout;
• the timing of a cross-check;
• a method for estimating rollout lead;
• a demonstration sequence;
• the order in which a complex skill is introduced;
• a way to organize the traffic-pattern scan.

Two instructors can use different effective techniques while teaching the same standard. A technique becomes mandatory only when an applicable approved source or school policy makes it so.

5. Safety boundary and instructor intervention

This layer answers when the instructor or pilot should discontinue, go around, take the controls, change the plan, or stop the lesson.

Examples include:

• unstable approach beyond a prebriefed gate;
• runway conflict or uncertainty;
• altitude too low for the planned maneuver;
• uncoordinated stall entry or developing spin risk;
• wind, weather, or runway condition beyond the plan;
• operation outside an endorsement or aircraft limitation;
• traffic conflict;
• loss of situational awareness;
• equipment or aircraft condition that changes the risk.

A safety boundary may be stricter than a practical-test tolerance. That does not make it an ACS requirement. It is the condition under which continuing is inappropriate.

Why the distinction matters

When the layers are mixed together, several instructional problems appear.

Preference becomes a false regulation

An instructor may say that a student "must" begin steep-turn rollout at exactly half the bank angle. The FAA handbook offers that as a general lead reference, while the current private-pilot ACS evaluates rollout on the entry heading within the applicable tolerance. The exact lead varies with airplane response and rate of roll.

Teach the technique, then identify the standard.

A tolerance becomes a target

A student may treat the edge of an ACS tolerance as the desired result. The standard is an evaluation boundary, not a reason to accept imprecise control or continue an unsafe condition.

A school procedure becomes an FAA rule

A school may use a 500-foot stabilized-approach gate for VFR training. FAA safety guidance supports stabilized approaches, but the school should describe its policy accurately rather than claim that one universal regulatory gate applies to every operation.

A safety intervention becomes a personal criticism

An instructor takeover should be described in terms of the developing condition and safety boundary. The student needs to know what cue was missed and what action should occur earlier, not merely that the instructor "did not like" the maneuver.

Four realistic examples

Example 1: Steep-turn rollout

Standard

The current private-pilot ACS specifies the required bank and rollout-heading performance for the task.

Technique

An instructor may teach a rollout lead based on a fraction of bank angle and then refine it for the airplane and rate of roll.

Safety

The instructor may discontinue the maneuver for traffic, loss of orientation, excessive bank, uncoordinated flight, or insufficient altitude margin even if the student is still trying to recover the numeric result.

Debrief language

The rollout missed the heading standard. The lead point I taught is a technique for this airplane, not the ACS wording itself. We also discontinued because your scan narrowed and traffic awareness became unacceptable.

Example 2: Crosswind landing

Standard

The applicable landing task requires directional control, appropriate wind correction, no side drift at touchdown, and runway alignment.

Aircraft procedure

Approach speed and any gust adjustment come from the aircraft guidance and instructor direction.

Technique

Crab, wing-low, or a transition between methods may be used as appropriate to the airplane and instruction.

Safety

The landing should be discontinued when alignment, drift, runway clearance, or stability cannot be maintained within the prebriefed plan.

Debrief language

The required outcome is runway alignment and no side drift. The wing-low reference is the technique we are using. The go-around was required by the developing drift and late corrections, not because the technique had to look exactly one way.

Example 3: Go-around configuration

Standard

The ACS evaluates timely decision-making, power and pitch transition, aircraft-specific configuration, climb speed, directional control, traffic avoidance, and other applicable elements.

Aircraft procedure

The POH/AFM controls flap, gear, pitch, power, and trim sequence.

Technique

An instructor may teach a specific verbal callout or hand movement to reduce omission risk.

Safety

The instructor intervenes if the pilot delays, loses control, creates a stall risk, conflicts with traffic, or uses an incorrect aircraft procedure.

Debrief language

The callout is our technique. The flap sequence comes from the aircraft procedure. The decision was late relative to the safety gate, and the climb did not stabilize until after instructor intervention.

Example 4: Short-field landing speed

Standard

The ACS first refers to the manufacturer's published approach airspeed. The alternative ACS language applies when the manufacturer has not published one.

Aircraft procedure

Use the current POH/AFM speed, configuration, and braking procedure.

Technique

The instructor may teach a particular aiming-point picture, pitch-power method, or visual cue.

Safety

Go around if the approach is unstable, runway conditions are unsuitable, traffic conflicts, or the landing cannot be completed safely within the plan.

Debrief language

The speed source is the POH, the touchdown tolerance is part of the ACS, the aiming picture is a technique, and the go-around gate is the safety boundary we briefed.

A debrief framework that keeps the layers separate

1. State the fact

Describe what happened without interpretation.

The airplane crossed the runway threshold above the target eIAS trend, floated, and touched down beyond the planned point.

2. Name the controlling source

The aircraft approach speed comes from the current POH/AFM. The applicable ACS task evaluates the touchdown area and the rest of the landing sequence.

3. Identify the technique

We are using a stabilized pitch-power picture and a defined aiming reference to reach that result.

4. Explain the safety boundary

The approach should have been discontinued when the energy state and remaining runway no longer supported the plan.

5. Choose the next action

On the next attempt, call out the stabilization gate, compare the aircraft indication with the planned target, and go around without prompting when the gate is missed.

Questions instructors should ask themselves

Before finalizing the debrief, ask:

• Did I identify the actual source?
• Am I presenting a preferred technique as a requirement?
• Am I using an ACS tolerance as the entire lesson objective?
• Did the school or operator create a stricter internal standard?
• Did the student understand the difference?
• Was the intervention driven by a documented safety condition?
• Does the aircraft procedure differ from the generic example?
• Did a new regulation, ACS revision, handbook addendum, or POH change affect the statement?

How FlytWERX can support source-aware debriefing

FlytWERX can help reconstruct the recorded event and compare it with the selected target or standard, depending on current product configuration. A review may include maneuver scoring, flight path, altitude, heading, course, ground track, groundspeed, vertical speed, pitch, bank, eIAS, instructor notes, and repeated attempts.

The product should not be expected to determine whether a statement comes from regulation, POH/AFM, ACS, approved syllabus, school policy, or instructor technique. The instructor or school should attach or reference the controlling source and keep the target version current.

eIAS source distinction

FlytWERX eIAS is a calculated estimate, not direct pitot-static aircraft IAS. It uses GPS-derived speed, current winds aloft, temperature, and the active wind correction. The 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 correction is current. This is first-party field evidence, not a certified specification or universal guarantee.

In the debrief:

• call the value eIAS;
• preserve wind and temperature inputs;
• compare with the aircraft indication when available;
• use it as training evidence;
• keep the airplane's approved indication controlling in flight.

Prevent standard drift across instructors

A school should maintain a controlled source hierarchy:

1. Current regulation and authorization;
2. Current POH/AFM, approved procedure, and limitation;
3. Current ACS or approved-course completion standard;
4. School SOP or training policy;
5. Instructor technique and coaching language;
6. Safety intervention criteria and escalation process.

When a source changes, the school should update lesson material, rubrics, FlytWERX targets, examples, and instructor briefing. An old screenshot or saved target should not silently become the current standard.

What a school should evaluate before adopting this workflow

What should a pilot prove?

A useful pilot should show that the source hierarchy removes confusion among regulation, standard, procedure, technique, and safety. 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 implementation start?

Begin with one defined workflow, one representative cohort, a small instructor group, and a written baseline. Keep required records and approvals in their current systems until the school verifies accuracy, usability, support, privacy, export, and compliance behavior. Expand only after difficult cases and failure modes have been tested.

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

Label each disputed debrief point as regulation, standard, procedure, technique, safety boundary, or evidence. 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: Structure the Debrief With Clear Sources.

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 an instructor technique optional?

A technique is one method of achieving the required result. The instructor may require the student to use it during a lesson for consistency and learning, but it should not be described as a universal FAA rule unless an applicable source makes it mandatory.

Are ACS tolerances safety limits?

No. They are practical-test evaluation standards integrated with knowledge, risk management, procedures, and judgment. Aircraft limitations and safe-operating decisions come from other applicable sources and conditions.

Can a school set a tighter standard than the ACS?

A school or instructor may set developmental, operational, or completion standards appropriate to the program, subject to approved-course and other requirements. Describe the source accurately.

What should happen when two instructors teach different techniques?

Confirm the regulation, aircraft procedure, program standard, and safety boundary. Then decide whether both techniques are acceptable or whether the school should standardize one for continuity.

Can a FlytWERX score determine which technique is correct?

No. A score can summarize recorded performance relative to configured targets. The instructor must determine whether the technique is appropriate, aircraft-specific, safe, and consistent with the controlling source.