The note does not explain the decision: "Needs more consistency - try another instructor." No one can tell what triggered the action, what will change, or when the school will know whether the intervention worked.

A useful intervention record turns concern into an owned, testable training plan.

A flight-training intervention is a deliberate change to instruction after a recurring performance, knowledge, risk-management, attendance, or continuity problem has been identified. A useful intervention record explains the factual trigger, the applicable standard, the evidence reviewed, the action selected, who owns it, when it will be reassessed, and what outcome will show whether it worked.

Record boundary: "Training intervention" is a FlytWERX editorial term, not one universal FAA form. The record described here is supplemental unless a school's approved syllabus, operating procedures, or governing rule adopts it. It does not replace required pilot logbook entries, instructor records, endorsements, Part 141 student records, stage-check documentation, or safety and discrepancy reports.

Why intervention records matter

Without a structured record, an intervention can become a series of undocumented comments:

• "Needs more consistency."
• "Try another instructor."
• "Do more pattern work."
• "Review aerodynamics."

Those statements do not show what pattern triggered action, what was changed, or whether the change helped.

A factual record supports:

• continuity across instructors;
• a defensible reason for changing the lesson plan;
• a clear student explanation;
• follow-up by the chief instructor or check instructor;
• separation of required records from optional coaching notes;
• evidence that the school tested an instructional response rather than merely repeating lessons;
• a defined point for continuing, modifying, escalating, or closing the intervention.

Step 1: State the trigger without labeling the student

Describe observable events rather than assigning a character trait or unsupported diagnosis.

Weak statement:

Student lacks aptitude and is unsafe.

Stronger statement:

During three dual pattern lessons conducted in comparable wind, the student continued below the prebriefed stabilized-approach gate on five approaches after the criteria were not met. The instructor directed four of the five go-arounds. The student could state the gate during the briefing but did not consistently recognize it in flight.

The stronger version identifies:

• the task and conditions;
• the repeated behavior;
• the instructor-assistance level;
• the knowledge-performance difference;
• the safety relevance.

Do not include medical, psychological, disability, misconduct, or maintenance conclusions unless the person making the entry is qualified and the record belongs in the authorized process.

Step 2: Identify the controlling standard or objective

The record should answer: "Compared with what?"

Possible sources include:

• the current POH/AFM or approved checklist;
• the applicable ACS task;
• a Part 141 approved training course outline;
• a school lesson-completion standard;
• a stage-check criterion;
• an instructor-defined developmental objective;
• a regulation or endorsement limitation.

Quote or summarize only the relevant requirement. Do not present an instructor preference as a regulation.

Example:

The lesson objective was independent recognition of the school's stabilized-approach gate and timely go-around initiation. The aircraft-specific go-around procedure remained the current POH/AFM procedure.

Step 3: Record the context needed to interpret the evidence

Include material context, not every detail of the day.

Relevant context may include:

• aircraft and configuration;
• airport and runway;
• wind, gusts, turbulence, temperature, and density altitude;
• traffic and ATC workload;
• lesson gap or schedule pattern;
• simulator versus aircraft;
• instructor prompting or intervention;
• sensor source and data quality;
• changes in syllabus stage or completion standard;
• equipment or connectivity problems that affected the review.

Context prevents a school from comparing unlike events as though they were identical.

Step 4: Separate evidence from interpretation

Use three labeled categories.

Recorded or observed facts

Examples:

• The student rolled out 24 degrees beyond the assigned heading.
• The instructor prompted the rollout on both attempts.
• The approach remained above the target eIAS range after the prebriefed gate.
• The student initiated a go-around before instructor direction on the final attempt.

Learner explanation

Examples:

• The student reported focusing on the radio call and missing the rollout lead.
• The student believed the wind had shifted and delayed the correction.

Instructor interpretation or working hypothesis

Examples:

• The pattern may reflect task saturation during the transition from downwind to base.
• The repeated altitude loss may begin with increasing bank rather than insufficient pitch alone.

A hypothesis should remain labeled as a hypothesis until evidence supports it.

Step 5: Describe the intervention as an action plan

A useful intervention names:

• the specific objective;
• the teaching action;
• the practice environment;
• the responsible instructor or owner;
• the student's responsibility;
• the expected date or lesson;
• the evidence to collect;
• the completion or reassessment criteria.

Example:

Before the next aircraft lesson, the assigned CFI will conduct a 20-minute ground review of the stabilized-approach gate and go-around decision. The student will chair-fly three pattern scenarios and verbalize the gate and trigger. In the airplane, the lesson will begin with two instructor-demonstrated approaches followed by student attempts. The instructor will record whether the student identifies the trigger without prompting and will reassess after two comparable dual lessons.

Avoid broad plans such as "more practice" without an objective or reassessment point.

Step 6: Define safety limits and stop criteria

The intervention should state what must not be practiced independently and when the exercise will be discontinued.

Examples:

• dual instruction only until the instructor documents independent recognition;
• no simulated emergency below the instructor's planned recovery altitude;
• go around when the prebriefed gate is not met;
• discontinue if traffic, weather, aircraft condition, or workload makes the exercise unsuitable;
• follow the current POH/AFM and school procedure rather than an article or app instruction.

Software does not create a solo privilege, endorsement, or operational authorization.

Step 7: Identify the official records that remain required

Pilot logbook and training entries

Under 14 CFR 61.51, training and aeronautical experience used for a certificate, rating, flight review, or recent-experience requirement must be documented as required. Training time must include the description and length of the lesson and the authorized instructor's endorsement information.

Flight instructor records

Under 14 CFR 61.189, a flight instructor signs the logbook of each person receiving flight or ground training and maintains specified records of solo and test endorsements for at least three years.

Part 141 student records

Under 14 CFR 141.101, a certificated pilot school maintains a current and accurate record for each student in an approved course, including enrollment date; chronological attendance, subjects, flight operations, and test grades; and graduation, termination, or transfer date. The regulation states that the student's logbook does not suffice for the school record. The school retains the record for at least one year after graduation, termination, or transfer and provides a copy on request.

The intervention record may support those workflows, but it should not be assumed to satisfy them without school and regulatory review.

Step 8: Use FlytWERX as supporting evidence, not the official conclusion

FlytWERX can support reconstruction of available flight variables, maneuver attempts, session history, notes, and student-instructor discussion. A useful intervention record may link to:

• one marked maneuver segment;
• a comparison of comparable attempts;
• the first repeated deviation;
• the student's written reflection;
• an instructor annotation;
• the result after the intervention.

When eIAS is relevant, record the wind source, update time, temperature source, and whether more representative training-area winds were entered. FlytWERX eIAS uses GPS-derived speed, winds aloft, temperature, and the active wind correction. The 1-to-3-knot average difference observed by FlytWERX instructors when the wind correction is current is first-party field evidence, not a certified specification. The airplane's approved indication remains controlling in flight.

Verify current FlytWERX permissions, sharing, retention, and reporting behavior before incorporating the product into an official school process.

Step 9: Reassess against the original trigger

At the follow-up point, record:

• what training occurred;
• whether conditions were comparable;
• whether the trigger behavior changed;
• whether assistance decreased;
• whether recognition improved;
• whether the correction transferred to a new condition;
• whether a safety concern remains;
• whether the intervention should close, continue, change, or escalate.

Do not declare success solely because one attempt was good. The relevant standard and school process determine whether repeatability is sufficient.

Step 10: Close the intervention clearly

A closed record should state:

• closure date;
• person authorizing closure under the school's process;
• evidence supporting closure;
• remaining limitations or monitoring;
• next syllabus objective;
• where required records were completed.

If the intervention is not successful, document the next decision rather than leaving the record open indefinitely.

A CMS-friendly intervention note template

Student and training context

• Student identifier:
• Certificate, rating, course, stage, or lesson:
• Date opened:
• Instructor or owner:

Factual trigger

• Repeated event or concern:
• Number and type of comparable events reviewed:
• Level of instructor assistance:
• Safety or risk significance:

Standard and source

• POH/AFM, ACS, approved syllabus, school standard, or regulation:
• Developmental objective:

Evidence reviewed

• Instructor observation:
• Student account:
• FlytWERX session or maneuver reference:
• Other authorized record:
• Important missing information:

Intervention plan

• Objective:
• Teaching action:
• Practice environment:
• Student preparation:
• Safety limits and stop criteria:
• Owner:
• Target date or lesson:
• Reassessment criteria:

Follow-up

• Training completed:
• Result:
• Assistance level:
• Decision: close, continue, modify, or escalate:
• Required records completed in:

What a school should evaluate before adopting this workflow

What should a pilot prove?

A useful pilot should show that interventions are documented, owned, reassessed, and changed when the evidence requires it. 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 the school measure value?

Establish a baseline before the pilot. Measure the time, rework, repeated lessons, continuity gaps, or decision delays that the workflow is intended to change, then subtract subscription, onboarding, migration, integration, training, support, and change-management costs. Do not count reduced flight hours, improved pass rates, or safety outcomes as savings unless the evidence supports those claims.

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

Document one intervention with a trigger, action, owner, review date, and observable success criterion. 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 Focused Progress Plan.

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 training intervention required by the FAA?

The FAA sources used here do not establish one universal form called a training intervention. A Part 141 approved syllabus or a school's procedures may create specific requirements. Required records must still comply with the applicable rules.

Should the record include a diagnosis?

No unsupported diagnosis should be included. Record observable behavior, context, evidence, and instructional action. Use qualified referral or authorized reporting processes for matters outside flight instruction.

Can a FlytWERX note replace the pilot logbook or Part 141 record?

Do not assume so. FlytWERX can provide supplemental training evidence. The school and instructor remain responsible for required records and must verify whether any electronic workflow meets the applicable rule and approved procedures.

How long should the intervention remain open?

The sources used here do not prescribe one universal period. Define a reasonable reassessment point tied to lessons, conditions, and the significance of the issue.

Who should see the record?

Only authorized people with a legitimate training or operational need, under the school's privacy, retention, and access policies.