
The migration problem appears after the system goes live: A school assumes the electronic lesson record now satisfies every Part 61 and Part 141 requirement. Later, the team discovers that official records, endorsements, instructor retention, and supplemental analytics were never mapped separately.
The first migration task is to identify which record is authoritative for each requirement.
Part 61 training relies on the pilot's logbook and the flight instructor's required signatures, endorsements, and retained endorsement records. A Part 141 school must also maintain a separate current and accurate student record for each person enrolled in an approved course. The student's logbook does not substitute for the Part 141 school record. Part 141 also adds chief-instructor certification and graduation-certificate requirements.
Legal-review boundary: This article summarizes selected federal requirements as of the verification date. It is not legal advice, an FAA approval, or a complete recordkeeping analysis. A school may have additional obligations under its approved course, FAA letters or specifications, veterans' education rules, state law, contracts, privacy requirements, insurance, or other programs. Reopen the current eCFR and school approvals before relying on the workflow.
Start with the correct training framework
"Part 61 school" is common industry language, but Part 61 primarily regulates airmen certification, training, experience, endorsements, privileges, and limitations. A training provider can offer instruction under Part 61 without holding a Part 141 pilot school certificate.
A Part 141 pilot school is certificated by the FAA and uses approved courses. The FAA describes Part 141 schools as using a structured training program and syllabus, with FAA-approved curricula and additional oversight and operating requirements.
A business may conduct both:
- approved Part 141 courses; and
- training that is not conducted under an approved Part 141 course.
The record must identify the actual enrollment and training framework. Do not assume every lesson at a Part 141-certificated school belongs to a Part 141 course.
Part 61: the pilot's logbook record
Under 14 CFR 61.51, each person must document and record training and aeronautical experience used to meet applicable certificate, rating, flight-review, and recent-experience requirements in a manner acceptable to the Administrator.
For a logged flight or lesson, the rule includes required information such as:
- date;
- total flight or lesson time;
- departure and arrival locations, or the training-device lesson location as applicable;
- type and identification of the aircraft or training device;
- applicable type of pilot experience or training;
- applicable conditions of flight.
For training time, 14 CFR 61.51 requires the authorized instructor to endorse the entry legibly and include a description of the training given, the length of the lesson, and the instructor's signature, certificate number, and current expiration or recent-experience information specified by the rule.
The complete current section contains additional requirements for specific types of logged time. A blog summary should not replace direct review of the rule.
Part 61: the instructor's records
Under 14 CFR 61.189, a flight instructor must sign the logbook of each person to whom the instructor gives flight or ground training.
The instructor must also maintain a record, in a logbook or separate document, containing:
- the name of each person whose logbook the instructor endorsed for solo flight privileges and the endorsement date;
- the name of each person endorsed for a knowledge or practical test;
- the type of test, date, and results for the applicable test record.
The instructor must retain the records required by that section for at least three years.
Those instructor records are not the same as the student's pilot logbook. A provider may maintain additional lesson records for continuity, billing, quality, or school policy, but the supplemental record does not erase the federal requirements.
Part 141 adds a separate school student record
Under 14 CFR 141.101, each holder of a pilot school or provisional pilot school certificate must establish and maintain a current and accurate participation record for each student enrolled in an approved course.
The required record includes:
- the date the student enrolled in the approved course;
- a chronological log of course attendance;
- subjects and flight operations covered in training;
- names and grades of tests taken;
- the date the student graduated, terminated training, or transferred to another school.
The rule explicitly states that the records maintained in the student's logbook do not suffice for the Part 141 record.
When the student graduates, terminates, or transfers, the student's record must be certified to that effect by the chief instructor.
The school must retain the required record for at least one year from the applicable graduation, termination, or transfer date and make a copy available at the student's request.
This is a minimum federal summary. The approved course or other applicable program may require additional content or retention.
Part 141 graduation certificates are separate documents
Under 14 CFR 141.95, a certificated or provisional pilot school must issue a graduation certificate to each student who completes an approved course.
The certificate must include specified information such as:
- school name and certificate number;
- graduate's name;
- course of training;
- graduation date;
- statement that the student satisfactorily completed each required stage, including stage tests;
- chief-instructor certification;
- statement of the cross-country training received;
- the required unique code for an applicable internet-media course.
A lesson-completion screen, student logbook, or analytics report should not be called a Part 141 graduation certificate unless it includes the required content and is issued through the school's authorized process.
Part 141 records connect to approved course control
Part 141 documentation is not merely additional paperwork. It connects the student's participation to an approved course.
Related responsibilities include:
- instructors who meet approved course qualifications;
- review and briefing on course objectives and standards;
- initial and recurrent instructor proficiency checks under 14 CFR 141.79;
- required stage checks and end-of-course tests;
- chief-instructor responsibilities under 14 CFR 141.85;
- current and accurate student training records;
- course-completion and graduation certification.
A school's record system should preserve that connection among course, lesson, instructor, aircraft or training device, grades, checks, and completion status.
What stays separate in both environments
A well-designed system distinguishes several record categories.
Pilot logbook
Used for training time, aeronautical experience, endorsements, and other entries required under Part 61.
Instructor record
Used for the retained endorsement records required by 14 CFR 61.189 and any additional school instructor records.
Part 141 student record
Used for participation in an approved course and the content required by 14 CFR 141.101.
Stage-check and end-of-course documentation
Maintained under the approved course and school procedures.
Graduation certificate
Issued under 14 CFR 141.95 when the student completes the approved course.
Scheduling, dispatch, and billing
Operational records that may support the training record but do not automatically satisfy it.
Aircraft maintenance and discrepancy records
Maintained through the authorized maintenance and operational process, not inside an informal student note.
Training analytics and flight replays
Supplemental evidence used for debriefing, progression, quality, or standardization. It becomes part of a required record only through a verified, authorized workflow.
A record map for Part 61 training
For each Part 61 lesson, the provider should identify:
Before the lesson
- student identity and eligibility relevant to the planned training;
- aircraft and instructor assignment;
- current endorsements or limitations when applicable;
- planned objective;
- required weather, maintenance, dispatch, or school checks.
During and after the lesson
- training content and duration;
- pilot logbook entry and instructor endorsement as required;
- lesson result and next objective under the provider's process;
- any required solo, test, or other endorsement;
- instructor's retained endorsement record when 14 CFR 61.189 applies;
- safety or maintenance issue routed into the correct system.
Supplemental review
- flight path and telemetry;
- FlytWERX maneuver review;
- student reflection;
- instructor notes;
- intervention or handoff record.
The supplemental evidence should be linked without being mistaken for the required logbook or instructor record.
A record map for an approved Part 141 course
A Part 141 workflow should also preserve:
Enrollment
- course identity;
- enrollment date;
- student status;
- prerequisites and prior credit under the approved process;
- approved syllabus version.
Chronological participation
- course attendance;
- subjects;
- flight operations;
- lesson results;
- tests, names, and grades;
- instructor identity;
- stage and course status;
- additional details required by the approved course.
Checks and course completion
- stage checks and end-of-course tests;
- deficiencies and additional training;
- chief-instructor or authorized certifications;
- graduation, termination, or transfer date;
- graduation certificate where applicable.
Retention and access
- at least the federal minimum retention period;
- student-copy process;
- permissions and audit trail;
- archive and deletion controls;
- applicable additional obligations.
The school should validate this map against its approved documents and FAA oversight.
Electronic records need more than a database field
A school evaluating an electronic workflow should ask:
- Does it capture every required data element?
- Who is authorized to enter, sign, certify, correct, and view the record?
- Is the signature or certification method acceptable for the use?
- Does the system preserve the date, identity, and audit trail?
- Can the school produce a readable copy for the student or FAA?
- Does retention meet every applicable requirement?
- How are corrections made without destroying the original history?
- What happens during an outage, vendor change, or data export?
- Are official records distinguishable from draft notes and analytics?
- Are privacy, consent, security, and deletion policies defined?
- Does the approved Part 141 course or FAA office require a particular workflow?
FAA AC 120-78B provides guidance on electronic signatures, electronic recordkeeping, and electronic manuals in contexts addressed by that circular. A school should obtain qualified review rather than assume that using a cloud system automatically makes every record acceptable.
How FlytWERX can fit into the workflow
FlytWERX's public school page describes support for structured programs, syllabi, lesson records, stage checks, endorsements, hour requirements, acknowledgments, performance data, and school-level oversight.
Before using FlytWERX as an official record system, the school and product owner should verify:
- which feature is currently live;
- which regulatory record it is intended to support;
- required fields and signatures;
- permissions and role controls;
- audit history;
- retention and export;
- chief-instructor certification;
- student-copy process;
- course and syllabus versioning;
- integration with the pilot logbook and instructor records;
- whether a separate authoritative system remains necessary.
FlytWERX telemetry, scores, eIAS, notes, and replays can support the debrief and supplemental training evidence. They do not automatically become a legal logbook entry, instructor endorsement record, Part 141 student record, stage-check result, or graduation certificate.
When eIAS appears in the supplemental record, label it correctly. FlytWERX calculates eIAS from GPS-derived speed, current winds aloft, temperature, and the active wind correction. More representative local winds can be entered. The 1-to-3-knot instructor field observation is first-party, not a certified accuracy specification. The aircraft's approved indication remains controlling.
Common recordkeeping mistakes
Treating the student's logbook as the complete Part 141 record
14 CFR 141.101 expressly says the logbook record does not suffice.
Storing endorsements only in lesson notes
The authorized instructor must complete and retain the applicable records under Part 61.
Mixing Part 61 and Part 141 status
A lesson conducted at a Part 141-certificated school is not automatically part of an approved course. Record the actual framework.
Calling analytics a grade without authorization
A product score can inform the instructor. The official lesson or stage grade must follow the approved process.
Missing the exit certification
Part 141 records require chief-instructor certification when the student graduates, terminates, or transfers.
Applying one retention period to every record
Different records and programs can have different periods. For example, the federal minimum in 14 CFR 141.101 differs from the three-year instructor-record period in 14 CFR 61.189.
Deleting records when a student leaves the software
Account deletion, contract termination, and regulatory retention are separate questions. The system needs a defined export and archive process.
A transition checklist for schools
When moving records into a new platform:
- Inventory every required and supplemental record.
- Identify the controlling rule, approved course, policy, and retention period.
- Name the authoritative system for each record.
- Map every required field, signature, certification, and access role.
- Test Part 61, Part 141, transfer, termination, graduation, and instructor-handoff scenarios.
- Test exports, student copies, corrections, audit history, and outages.
- Train instructors and administrators on what belongs where.
- Run parallel records until authorized leadership confirms the new workflow.
- Conduct a sample audit.
- Obtain FAA, legal, privacy, security, and product review as applicable before retiring the prior system.
What a school should evaluate before adopting this workflow
What should a pilot prove?
A useful pilot should show that official and supplemental records remain distinct through migration, correction, retention, and export. 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
Map each required and supplemental record to its authoritative system, owner, retention rule, and export path. 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: Map Your Flight Training Record Workflow.
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
Does a Part 141 student still need a pilot logbook?
Yes. The Part 141 school record is separate, and 14 CFR 141.101 says the student's logbook does not substitute for it. Applicable Part 61 logbook requirements still matter.
How long must a Part 141 school retain the student record?
14 CFR 141.101 requires at least one year from graduation, termination, or transfer. Other requirements or school policies may require longer retention.
How long must a flight instructor retain the records required by 14 CFR 61.189?
At least three years.
Can an electronic system satisfy the requirements?
It may support an acceptable workflow when the required content, signatures or certifications, audit trail, access, retention, and production requirements are met. The school must verify the specific use with qualified reviewers and applicable FAA oversight.
Can FlytWERX replace every training record?
Do not assume so. FlytWERX can support connected training workflows and supplemental evidence. Each official record use requires feature, regulatory, approval, signature, access, retention, and audit verification.
- FAA Part 141 Pilot Schools
- FAA Pilot Schools Information
- AC 141-1B: Part 141 Pilot Schools, Application, Certification, and Compliance
- AC 120-78B: Electronic Signatures, Electronic Recordkeeping, and Electronic Manuals
- 14 CFR 61.51: Pilot logbooks
- 14 CFR 61.189: Flight instructor records
- 14 CFR 141.79: Flight training
- 14 CFR 141.85: Chief instructor responsibilities
- 14 CFR 141.95: Graduation certificate
- 14 CFR 141.101: Training records
- FlytWERX for Flight Schools
