These are the terms Aersynx is built around — directives, life limits, release certificates, the controls that keep a part honest. For each, a plain-language definition and how the platform handles it.
The instruments that decide whether an aircraft is airworthy today — and the ones an auditor checks first.
A mandatory instruction from a regulator (EASA, FAA) to correct an unsafe condition on a type or specific serials. Missing one is a finding — or a grounding.
In Aersynx: EASA/FAA fetch, Part-21 applicability per serial, supersede chains. A repetitive AD returns to repeat after compliance, not open — so it never silently drops off the list.
Playbook: How AD compliance worksA manufacturer recommendation for a modification, inspection, or repair. Often optional, but frequently the basis a later AD makes mandatory.
In Aersynx: tracked alongside the ADs they relate to, so the link from recommendation to mandate stays visible.
The approved schedule of maintenance tasks an aircraft must follow, derived from the manufacturer's planning document and tailored to the operator.
In Aersynx: revisions move through a draft to approved workflow with gap analysis against the source MPD before they take effect.
The manufacturer's master list of scheduled maintenance tasks and intervals — the source an AMP is built from.
In Aersynx: the reference an AMP revision is compared against, so additions, deletions, and interval changes are explicit, not assumed.
The core of task tracking: when a maintenance task was last accomplished and when it falls due next, by date, hours, or cycles.
In Aersynx: interval deviations surface as findings rather than quietly recalculating, so a stretched interval is a decision, not a default.
What may be inoperative — and for how long — while an aircraft still dispatches. Each item carries a rectification deadline category.
In Aersynx: the A/B/C/D deadline ladder with dispatch control, so a deferral has a clock, not an open end.
The certificate confirming an aircraft's continuing airworthiness has been reviewed and found in order under Part-CAMO.
In Aersynx: an M.A.901 readiness gate — the readiness basis is checked before an ARC is treated as ready, not after.
The organization responsible for keeping an aircraft airworthy over its life — managing ADs, the maintenance program, and the review that backs the ARC.
In Aersynx: the analyst role that reviews and commits records — the human whose sign-off makes the output defensible.
The limits that govern a part's life — and the chain of evidence that says how much of it is left.
A part with a hard cycle (or time) limit it may never exceed — typically engine and landing-gear rotables. At the limit, it comes off, full stop.
In Aersynx: the cycles limit is absolute under Part-21 and Part-C — never reset by overhaul, swap, or shop visit. One canonical formula computes remaining life everywhere it is quoted.
Playbook: Proving LLP remaining lifeThe unbroken cycle history of a life-limited part, from manufacture to today. Without it, remaining life is a claim, not a fact.
In Aersynx: the chain is checked against the release paperwork at commit, so the remaining life you quote is the remaining life you can prove.
Playbook: Proving LLP remaining lifeA component with a fixed calendar or cycle limit at which it must be removed, overhauled, or replaced — managed on a schedule.
In Aersynx: tracked as a component-status type with its own due basis, distinct from on-condition items.
A component kept in service by inspection and monitoring rather than a fixed life — replaced when its condition warrants.
In Aersynx: tracked as a component-status type so condition-based items aren't forced into a hard-time mold.
A record is only as good as the proof attached to it. These are the documents and the rule that ties them together.
The authorized release certificate (EASA Form 1, FAA 8130-3) confirming a part was maintained and released to service by an approved organization.
In Aersynx: linked to the record it certifies, so a remaining-life basis or a shop visit carries its release evidence with it.
Playbook: Proving LLP remaining lifeThe rule that a compliance action must be backed by a real, verified record before it can be trusted — not just asserted.
In Aersynx: a compliance record won't commit unless its linked record is OCR-complete, AI-summarized, on an allowed event type, and resolves to the right aircraft. Otherwise the action is rejected.
See it: Follow one delivery reportWhere inventory and procurement meet the technical record. Supply is in early access and active hardening — the integration thesis is real and demoable today; the hardening is ongoing.
The control that an invoice is only paid when it agrees with the purchase order and the goods actually received — the standard guard against paying for what didn't arrive.
In Aersynx (early access): purchase order, goods receipt, and invoice are reconciled on the shared part master rather than a separate ledger you check by hand.
Supply (early access)Binding a specific physical stock unit to a job or order so it cannot be promised twice. A part reserved against itself is an AOG you didn't see coming.
In Aersynx (early access): a reservation binds a real stock unit, designed so the same part can't be committed to two places at once.
Supply (early access)Bring the terms your fleet runs on. We'll show you where each one already lives in Aersynx.