Flight School Management Software — Aircraft Scheduling, Training, Maintenance & Billing

Record Keeping Requirements Made Easy for Part 141 Schools

By Flight Suite HQ Staff | Published 2026-07-14

Why Part 141 schools face a higher recordkeeping bar

Part 61 flight training is largely pilot-driven — the individual keeps their own logbook and tracks their own endorsements. Part 141 schools are different. The certificate holder is directly responsible for maintaining a comprehensive training record system that the FAA can audit at any time. When you layer in electronic signatures and digital records, the FAA points you toward AC 120-78B (Advisory Circular for Electronic Signatures, Electronic Recordkeeping, and Electronic Manuals) as the standard your system must meet.

The circular is thorough, but it was written for air carriers, repair stations, and training centers alike — which makes it dense. Below, we break it into the pieces that actually matter for a Part 141 flight school and show exactly how Flight Suite HQ addresses each one.

Understanding the FAA Letter of Authorization (LOA A025)

Before you can officially rely on electronic signatures and records, the FAA expects your organization to hold a Letter of Authorization (LOA) under OpSpec/MSpec/LOA A025. This is not a software certification — it is the FAA's acknowledgment that your organization has described its electronic recordkeeping system in sufficient detail and that the system meets the criteria in AC 120-78B.

The process works like this:

  1. Letter of Intent (LOI) — You notify your local FSDO that you intend to use electronic signatures for training records.
  2. System Description — You submit a written description of your system architecture, security controls, and signature process.
  3. FAA Review — The Principal Inspector evaluates your submission against the advisory circular.
  4. LOA Issued — Once satisfied, the FSDO issues A025 authorizing electronic recordkeeping.

In Flight Suite HQ, the LOA Tracker walks you through every step. It auto-generates a properly formatted Letter of Intent and a complete System Description document you can submit directly to your FSDO — no consultant required.

Requirement 1: Electronic Signature Identity and Authentication

AC 120-78B Section 3.2 requires that every electronic signature is tied to a unique, verifiable individual. The system must:

  • Identify the signer (full name, certificate number)
  • Authenticate the signer at the moment of signing (not just at login)
  • Record the signer's intent (what they are attesting to)
  • Bind the signature cryptographically to the record content

Flight Suite HQ enforces re-authentication at signing time. When an instructor signs off a lesson or endorsement, the system prompts for their password again, captures their identity and intent statement, then computes a SHA-256 hash that binds the signature to the exact record content. If a single character in the record changes after signing, the hash will no longer match — and the system will flag it.

Requirement 2: Non-Repudiation

Non-repudiation means a signer cannot later deny having signed a record. AC 120-78B requires that the combination of identity verification, authentication, and intent capture makes it impossible to credibly claim "that wasn't me."

Flight Suite HQ satisfies this by recording:

  • The authenticated user ID (tied to their Supabase auth session)
  • The re-authentication timestamp
  • The intent statement ("I certify this training was completed as described")
  • The cryptographic hash of the record at signing time
  • The signer's IP address and session metadata

All of this is stored immutably — no user, including administrators, can modify a signature record after creation.

Requirement 3: Data Integrity Verification

Section 3.2.5 of AC 120-78B requires a mechanism to detect unauthorized alteration of electronically signed records. This is where many spreadsheet-based or paper-hybrid systems fail entirely — there is no way to prove a PDF or Excel file has not been silently edited.

Flight Suite HQ includes a Data Integrity Verifier that re-computes the SHA-256 hash of every signed record and compares it against the stored hash. You can run this check at any time — before an FAA audit, monthly, or on demand. The results show exactly which records are verified intact and which (if any) have been tampered with.

Requirement 4: Immutable Audit Trail

AC 120-78B Chapter 3 requires a comprehensive, tamper-evident audit trail that records every create, update, and access event on regulated records. The audit trail must include:

  • Who performed the action (user identity)
  • What was changed (before and after values)
  • When it happened (timestamp)
  • A checksum of the audit record itself (to detect log tampering)

Flight Suite HQ automatically logs every modification to training records, endorsements, flights, and signatures into an immutable Record Audit Trail. Each log entry includes its own checksum, creating a chain where tampering with any individual entry would be detectable. The audit viewer is accessible directly from the AC 120-78B Compliance dashboard.

Requirement 5: Formal Correction Process

This is one of the most misunderstood requirements. AC 120-78B explicitly states that records must never be deleted or overwritten. If a record contains an error, the original must be preserved, marked as superseded, and a new corrected record created with a fresh signature.

Flight Suite HQ implements this through the Record Correction workflow:

  1. The user identifies the record needing correction and provides a written reason.
  2. The original record is preserved in its entirety and locked.
  3. A new corrected record is created referencing the original.
  4. The correction requires approval from an admin or chief instructor.
  5. A fresh electronic signature is required on the corrected record.

This satisfies the FAA requirement that corrections are traceable, authorized, and never destructive.

Requirement 6: Record Retention Policies

14 CFR 141.101 requires Part 141 schools to retain training records for at least one year after the student completes or terminates training. AC 120-78B adds that electronic signature records should be retained for a minimum of seven years. Different record types have different regulatory retention periods.

Flight Suite HQ includes a Record Retention Manager that lets you configure per-record-type retention policies mapped to specific CFR references:

  • Endorsements — Permanent (14 CFR 61.189)
  • Training Records — 3 years (14 CFR 141.101)
  • Flight Records — 3 years (14 CFR 61.51)
  • Electronic Signatures — 7 years (AC 120-78B)
  • Audit Trail — 7 years (AC 120-78B Ch 3)

You can load these defaults with a single click or customize them to your program. The system enforces these policies so records are not purged prematurely.

Requirement 7: Record Locking

Once a record has been signed electronically, AC 120-78B requires that the record be locked from further modification. No user — including system administrators — should be able to alter a signed record without going through the formal correction process.

Flight Suite HQ enforces record locking at the database level. When an electronic signature is applied, the underlying record is locked via a database trigger. Any attempt to modify a locked record is rejected automatically, with the rejection logged in the audit trail.

Requirement 8: Security Controls

Section 3.2.12 requires comprehensive security documentation including access controls, encryption, and authorization matrices. The FAA wants to see that:

  • Data is encrypted in transit (TLS 1.3) and at rest (AES-256)
  • Access is controlled through role-based permissions
  • No shared accounts exist
  • Authentication credentials are properly secured (bcrypt hashing)
  • The system provides organizational data isolation

Flight Suite HQ provides a live Security Documentation panel that shows your actual Row Level Security policy coverage per table, a list of authorized signature users, and a complete summary of encryption and access controls. This is not a static document — it reflects the live state of your system, so it is always audit-ready.

Requirement 9: System Revision Control

AC 120-78B requires that organizations maintain a log of all software versions used in their electronic recordkeeping system. If the FAA asks what version was running when a particular record was signed, you need to be able to answer.

The System Revision Log in Flight Suite HQ tracks every deployed version with its release date, change summary, and the person who deployed it. This provides a complete version history that satisfies the revision control requirement.

Requirement 10: Backup Verification

The advisory circular requires documented evidence that backup and recovery procedures are working. It is not enough to say "we have backups" — you need to periodically verify them and record the results.

Flight Suite HQ maintains a Backup Verification Log in the compliance system. The infrastructure (Supabase/AWS) provides geo-redundant automated backups, and verification events are logged to demonstrate ongoing compliance.

Bringing It All Together: The Compliance Dashboard

All of these requirements — LOA tracking, electronic signatures, data integrity, audit trails, corrections, retention, locking, security, revision control, and backups — live under a single AC 120-78B Compliance Dashboard in Flight Suite HQ. The overview tab shows a checklist of all requirements with their current status, so you always know where you stand.

For Part 141 chief instructors and school administrators, this means:

  • No more binder audits — everything is digital, searchable, and verifiable
  • No consultant needed — the LOA Tracker generates your submission documents automatically
  • Audit-ready at all times — every requirement is continuously monitored, not just checked once a year
  • Instructor buy-in is easier — the signing process takes seconds and the system handles all the compliance machinery behind the scenes

Getting started

If your Part 141 school is still using paper sign-offs, spreadsheet tracking, or a patchwork of tools that cannot prove data integrity, AC 120-78B compliance is going to be a constant headache. Flight Suite HQ was built specifically for flight schools that want to move to fully electronic recordkeeping without hiring a compliance consultant or building custom software.

Enable the AC 120-78B module from your organization settings, use the LOA Tracker to prepare your FSDO submission, and start signing records electronically — with full confidence that every FAA requirement is handled.