<%# The procedures document (AC 120-78B 2.2.11, 3.2.8), generated from the system's setup. Locals: policy, number, adopted_at, adopted_by, revisions, summary. %> <% info = SystemInfo.new %> <% aircraft = Aircraft.ordered.includes(:roles) %> <% users = User.order(:email_address).includes(:certificates, aircraft_roles: :aircraft) %> <% h2 = "mt-6 text-base font-semibold" %> <% p_ = "mt-1 text-sm leading-relaxed" %>

Standalone procedures document · AC 120-78B paragraphs 2.2.11 and 3.2.8

Electronic Signature and Recordkeeping Procedures

<%= policy.operator_name.presence || "[Operator]" %> · Simple Aircraft Manager

Revision <%= number %><%= adopted_at ? " · adopted #{adopted_at.to_date.iso8601} by #{adopted_by&.display_name}" : " · not yet adopted" %>

1. Purpose and scope

These procedures describe how <%= policy.operator_name.presence || "[Operator]" %> keeps the maintenance records required by 14 CFR 91.417 electronically in Simple Aircraft Manager, and how entries are signed electronically under 14 CFR 43.9 and 43.11. They follow FAA AC 120-78B. Under its paragraph 1.9.5, use of electronic signatures and recordkeeping under part 91 (other than subpart K) needs no FAA approval, acceptance or authorization; the FAA recommends following the AC, and these procedures do.

<% aircraft.each do |a| %> <% end %>
AircraftSerial numberElectronic records sinceEarlier records
<%= a.tail_number %> <%= [ a.make, a.model ].compact_blank.join(" ") %><%= a.serial_number.presence || "—" %> <%= a.electronic_records_since || "not set" %>Paper logbooks<%= " (scans held as legacy records)" if a.documents.where(legacy_record: true).exists? %>

Records kept electronically: logbook entries (maintenance, preventive maintenance, inspections, alterations), inspection status and history, airworthiness directive compliance, component times and life limits, major repairs and alterations with their Form 337s, weight and balance, and supporting documents. Paper logbooks from before the date above remain the record for that period and are kept.

2. Regulatory compliance

Each logbook entry carries what 14 CFR 43.9 requires (description of the work, date, the name, certificate number and kind of certificate of the person approving return to service, and their signature) and, for inspections, what 43.11 requires (type and extent of inspection, aircraft time in service, and the airworthiness statement or discrepancy list). The app flags entries missing any of these. Records include the key elements of AC 120-78B 3.1.1: the event, when (date, and the signature's time), where (location), who, the signature, and the make, model and serial of the aircraft, engine, propeller and components. The status required by 91.417(a)(2) is produced by the maintenance status report. Records are made available under 91.417(c) and transferred under 91.419 as described in sections 9 and 10.

3. System description

4. Responsible personnel

<%= policy.responsible_name.presence || "[Name]" %><%= ", #{policy.responsible_title}" if policy.responsible_title.present? %>, has authority and overall responsibility for the electronic signature process and the recordkeeping system, for controlling access to it (accounts, roles, disabling accounts), and for the quality-control audits. Administrators: <%= users.select(&:admin?).reject(&:disabled?).map(&:display_name).to_sentence.presence || "none" %>.

5. Defined users and roles

Owners keep an aircraft's records; pilots can view them and record flights, squawks and preventive maintenance. A user may sign entries with a current certificate on their profile: mechanic certificates (A&P, IA, airframe, powerplant, repair station, repairman) for maintenance and inspection entries; a pilot certificate for preventive maintenance only. Disabled accounts can't sign in or sign.

<% users.each do |u| %> <% current = u.certificates.reject(&:expired?) %> <% end %>
UserRolesCertificatesMay sign
<%= u.display_name %>
<%= u.email_address %>
<%= [ ("Administrator" if u.admin?), *u.aircraft_roles.map { "#{_1.role.capitalize}, #{_1.aircraft.tail_number}" } ].compact.join("; ").presence || "—" %><%= " (DISABLED)" if u.disabled? %> <%= u.certificates.map { "#{_1.short_label} #{_1.number}#{" exp. #{_1.expires_on}" if _1.expires_on}" }.join("; ").presence || "—" %> <%= if u.disabled? || current.empty? then "No" elsif current.any?(&:mechanic?) then "Maintenance and inspection entries" else "Preventive maintenance entries" end %>

People outside these users (e.g. a mechanic who did the work) sign through a one-time email invitation from an owner, with their own account and certificate, for that entry only; or they sign on paper (section 11).

6. Electronic signature process

  1. The signer opens the entry and chooses Sign. The entry is shown in full exactly as it will be certified (AC 2.2.4).
  2. They choose one of their own current certificates. The statement they will certify is shown with it, under the heading “Certified by” (2.2.2): for maintenance, “I certify that the work described in this entry was performed in accordance with 14 CFR Part 43, and I approve it for return to service with respect to that work”; for inspections, the 43.11(a)(5) statement; for preventive maintenance by a pilot, the corresponding statement.
  3. They prove who they are again: their password (with a code from their authenticator app, if they use one), or signing in again with single sign-on within the last five minutes (2.2.6), and confirm that they are signing with intent to sign (2.1.2.4–5).
  4. The system records the signer, the certificate (kind and number), the statement, the time (UTC), how they authenticated, their network address and browser, a SHA-256 fingerprint of the entry's content and a readable copy of it, and a server seal (HMAC) over the signature record (2.1.2.6, 2.2.5). The signer is told on screen and by email (2.2.3).
  5. Once signed, the entry and its components can't be edited or deleted (2.1.2.7–8, 2.2.7). A correction is made as a new entry that, once signed, supersedes the original; the original and its signature are kept and marked superseded (2.2.8).
  6. When someone no longer needs access, the responsible person disables their account: they can no longer sign in or sign, and their past signatures stay valid (2.2.6.4).

Signed records are archived in the database, its nightly verified copies and the off-site backup, and can be exported with their signatures (2.2.9).

7. Recordkeeping system controls

8. Quality control and auditing

Every <%= policy.audit_interval_months %> months the responsible person carries out and records an audit in the system (3.2.8.5). The app checks that the integrity check and backups are passing, the procedures are adopted, signatures are intact, and lists expired certificates and software versions since the last audit. The auditor restores the off-site backup somewhere separate and opens it, compares <%= policy.audit_sample_size %> randomly chosen entries with their work orders or source documents, reviews the users and roles (disabling accounts no longer needed), and confirms the paper logbooks are kept. Audit results are kept in the system.<%= " Last audit: #{AuditRun.latest.performed_at.to_date}." if AuditRun.latest %>

9. Making records available to the FAA and NTSB

On request (14 CFR 91.417(c), 49 CFR 830), the responsible person provides the records package for the aircraft: every logbook entry as a PDF with its electronic signature, a signature register, the full change history, the maintenance status report and the data archive, with a README. Printed copies are produced the same way. Direct access to the system can be offered but isn't required (3.2.8.6).

10. Transfer of records

At sale (91.419, 3.2.8.12): the buyer receives the records package and the data archive, which another installation of the system can import, together with the paper logbooks. To another system (3.2.8.9): records are exported as the data archive and the records package; both systems run side by side until the transfer is checked.

11. Continuity

Legacy records (3.2.8.10): records before the dates in section 1 are the paper logbooks, which are kept; scans are held as legacy records for reference. Maintenance providers (3.2.8.11): a provider signs electronically through an invitation, or signs a printed entry in ink; the signed paper is kept with the logbooks and scanned into the system.

12. Changes to the system and these procedures

These procedures are revised when the system or its use changes. Each revision is numbered, dated and adopted in the system by an administrator; earlier revisions are kept. Under AC 120-78B 1.9.5 no submission to the FAA is required for part 91 operations (3.2.8.13).

13. User instructions and training

Every user who keeps or signs records reads these instructions (also in the system under “How electronic records work”) before signing (2.2.12, 3.2.9).

<%= guide_html(HelpGuide.find("records"), links: false, title: false) %>
<% if policy.additional_procedures.present? %>

14. Additional procedures

<%= policy.additional_procedures %>
<% end %>

Revision history

<% revisions.each do |r| %><% end %>
RevisionAdoptedBySummary
<%= r.number %><%= r.adopted_at.to_date %><%= r.adopted_by&.display_name %><%= r.summary %>
<%= number %><%= adopted_at&.to_date || "—" %><%= adopted_by&.display_name %><%= summary.presence || "This revision" %>