AIRFOIL MXAIRFOIL MXAirFoil MX is an aviation maintenance platform for Part 91, 133, 135 and 145 operators — due status and interval math, airworthiness directives, work orders and the return-to-service gate, parts inventory and purchasing, records and signatures. Built to the regulation, not to a competitor's feature list: every rule it enforces cites the rule, and every record is append-only, hash-chained, and exportable to a file an auditor verifies offline.
Open the live demo See sample recordsWhichever comes first across hours, landings, cycles and calendar. The 100-hour ferry provision shortens the next interval where 14 CFR 91.409(b) says it must, and the EU tolerance runs from accomplishment where it must not — same ten hours, opposite consequence, declared not inferred. It refuses to compute where the record cannot support the answer: an inspection that silently never comes due is the failure this exists to prevent.
Append-only at the database role level; UPDATE and DELETE are revoked, not avoided in code. Hash-chained per tenant by a trigger a caller cannot forge. Signed through a ceremony where the PIN is never compared — it derives a key, and a wrong PIN yields a signature the server refuses. Corrections supersede; nothing is erased.
Five independent preconditions before an approval for return to service: every task signed as performed, every RII item inspected by someone other than the performer, a Form 337 for each major alteration, the § 43.15(c) run-up recorded, and the inspection checklist revision named. The gate refuses at the moment of signing, not at audit.
Applicability comes from an airworthiness directive's own effectivity statement, never a keyword hit — § 39.7 has no "probably fine" state. An overdue applicable directive is a hard dispatch block, composed at read time from the same due engine, and a compliance that reconstructed counters cannot demonstrate is a refusal, not a pass.
A part received without its airworthiness trace document is impounded in quarantine, not shelved — its paperwork is part of the part. Reorder floors compose with due demand. A purchase order's approver can never be the person who raised it: separation of duties as a database constraint, not a policy PDF.
Offline-first from the schema up, for bases without signal; airworthiness writes queue and are server-authoritative on reconnect. Mixed rotorcraft fleets are the normal case, proven across six type profiles. Tenant isolation is row-level security and per-tenant hash chains — structural, not a setting.
§ 91.417(b)(2) requires the maintenance records to transfer with the aircraft when it is sold. A platform that cannot hand them over in a verifiable form is one the records are trapped in. Here are ours, for a full demo fleet — in both forms of the same append-only, hash-chained data.
A human-readable logbook per tail — times in service, the § 91.417(a)(2) entries, work orders with every sign-off and Form 337, directives, open deferrals, and the installed configuration with its cited-or-UNKNOWN weights. Beside it, the verifiable export: every chained row carrying the canonical body that was hashed, and a standalone verifier that recomputes the chains from nothing but the file and sha256. Tamper a row, a body, or remove one, and it fails — naming the exact seam.
Easy to leave is what makes it easy to adopt.
The design target is the operator the established products fit least, so mixed fleets are the normal case here rather than a special one.
Utility, powerline, fire and survey contract work across several type profiles at once — airframe-agnostic from the schema up, validated against six.
The same airframe flies Part 91 one day and 133 the next. Inspection applicability, the 100-hour question and return-to-service authority all shift with it.
Mechanics deployed without connectivity, for whom offline is the normal case — sync is last-write-wins only for non-airworthiness fields; airworthiness writes are queued and server-authoritative.
A self-hosted tier for operators whose records must not leave their environment, with the same structural tenant isolation as the multi-tenant service.
Open the demo, download the sample records, or tell us what you operate.