AVIATION GLOSSARYThe words this work is done in.

An approved organisation responsible for keeping an aircraft airworthy between maintenance visits: managing the maintenance programme, tracking directives and life limits, controlling deferred defects, and keeping the technical records that prove all of it.

A CAMO's work is judged on evidence, not memory. The hard part is not doing the work — it is being able to show, on any given morning, that every applicable requirement was met and where the proof sits.

In AerSynxDirectives, life limits, programmes and deferred defects are tracked against the aircraft rather than a spreadsheet tab, and the evidence that closes each item is attached to the record itself. CAMO workspace →

The approved manual describing how a CAMO is organised and how it works: its structure, postholders, procedures and the scope of its approval.

The CAME is what an auditor compares reality against. Procedures that live only in the CAME, and not in the system people actually use, are the usual source of findings.

In AerSynxControlled documents, approvals and training records sit next to the operational record, so the procedure and the work it governs are not in two different places. Quality and Compliance →

The EASA regulation setting continuing airworthiness requirements: maintenance programmes, airworthiness reviews, records, and the responsibilities of owners, operators and CAMOs.

Part-M defines what must be kept and for how long. Most disputes at an audit or a lease return are not about the aircraft — they are about whether the record satisfies it.

In AerSynxRecords are attached to the aircraft, engine or component they belong to, and retained with their full history rather than in a folder tree that only one person understands. Technical Records →

The approval framework a CAMO holds today, introduced to separate continuing airworthiness management from the older Part-M Subpart G structure, with a management system and safety requirements of its own.

The change moved CAMOs from a checklist approach to a management-system approach: the regulator now asks how you detect and correct your own errors, not only whether the task was signed.

In AerSynxFindings, corrective actions and the audit trail run on the same records as the work, so a self-detected error and its correction are part of one history. Quality and Compliance →

A single approval combining continuing airworthiness management and maintenance for non-complex aircraft used outside commercial air transport — in effect a small CAMO and a small Part-145 in one.

Smaller operators carry the same obligations with far fewer people, so anything that needs a dedicated administrator does not get done.

In AerSynxWorkspaces are entitlements rather than a bundle: an organisation can run airworthiness and records first, and add maintenance production later without a migration. Platform overview →

A mandatory instruction issued by an aviation authority to correct an unsafe condition in a type of aircraft, engine or component. Compliance is not optional and is usually bounded by a date, flight hours or cycles.

Directives are revised, superseded and cancelled. The risk is rarely missing a directive outright — it is complying with a revision that has since been replaced, and not noticing.

In AerSynxThe EASA library is synchronised every morning and revisions and supersedures are detected automatically; a superseded directive is raised for an analyst rather than silently replaced. AD tracking →

A notice from the manufacturer describing a modification, inspection or repair. Unlike a directive it is not mandatory by itself, though an authority can make one mandatory by issuing a directive that references it.

Bulletins accumulate quietly. Whether a given one was embodied, and on which serial number, is a question that surfaces years later during a sale or a lease return.

In AerSynxEmbodiment is recorded against the aircraft or component with the evidence attached, so the answer is in the record rather than in somebody's recollection. Technical Records →

An operator's own instruction authorising a modification, repair or inspection, usually translating a directive, bulletin or repair scheme into work the hangar can carry out.

An engineering order is where an external requirement becomes internal work. If that handover is a PDF and a phone call, the compliance record and the work record drift apart.

In AerSynxRequirements reach production as work rather than as a document to re-enter, and closing the work returns the compliance evidence to the airworthiness record. Production →

A certificate confirming that an aircraft's continuing airworthiness records have been reviewed and found in order, issued or recommended after an airworthiness review.

The review is a documentation exercise: it fails on missing evidence far more often than on the condition of the aircraft.

In AerSynxReview readiness is derived from the same records the CAMO maintains, so gaps appear as blockers during normal operation instead of during the review. Reliability, Forecast and ARC →

The approved schedule of maintenance tasks for a specific aircraft: what must be done, at what interval, and on what basis. Built from the manufacturer's planning document and adapted to the operator.

Programmes are revised, and each revision has to be reconciled against the manufacturer's source. An escalated interval that was never approved is a finding waiting to happen.

In AerSynxProgramme revisions are managed with gap analysis against the planning document, so a task that exists in the source but not in your programme is visible rather than assumed. AMP Management →

The manufacturer's document listing recommended scheduled maintenance tasks and intervals for a type — the basis from which an operator builds its own approved programme.

The planning document is the reference an auditor returns to. Divergence between it and the live programme is normal and permitted; undocumented divergence is not.

In AerSynxThe gap between the planning document and the approved programme is computed rather than reviewed by hand, and each difference carries its justification. LDND and MPD Management →

A scheduled task established during type certification to detect failures that would otherwise stay hidden. Its interval cannot be escalated like an ordinary maintenance task.

These tasks look like any other line in the programme, which is exactly the risk: escalating one during an optimisation exercise is a certification issue, not a planning one.

In AerSynxTasks carry their own basis and interval rules, so a task that cannot be escalated does not quietly follow a programme-wide change. CAMO workspace →

A documented review of an aircraft's continuing airworthiness records, including a physical survey, carried out to support the issue or extension of an ARC.

It is a point-in-time judgement built on months of record keeping. What is missing on the day usually went missing quietly, long before.

In AerSynxMissing evidence surfaces continuously through findings and completeness checks rather than arriving as a list on review day. Quality and Compliance →

A part with a mandatory life limit set at certification, expressed in cycles or hours. When the limit is reached the part is removed from service permanently — it cannot be overhauled back into life.

The limit is absolute: overhaul, a shop visit or moving the part to another aircraft does not reset it. Software that treats a life limit like a maintenance interval will eventually run one past its limit.

In AerSynxRemaining life is computed by one formula used by every screen and export, and the limit is treated as absolute — nothing in the system resets it. LLP Tracking →

Documentary evidence tracing a life-limited part from manufacture through every installation, removal and period of operation, so that its accumulated life can be proven rather than estimated.

A gap anywhere in the chain devalues the part, because the life that cannot be proven has to be assumed used. Lessors will not accept an aircraft whose LLPs have broken traces.

In AerSynxA component is one record that moves with the part: removing it from an aircraft does not archive it and create a new one, so its history stays continuous across installations. Technical Records →

A maintenance policy where a component is removed at a fixed interval regardless of its condition, and overhauled or discarded.

Hard-time items are the easiest to track and the easiest to forget, because nothing about the aircraft signals that one is approaching.

In AerSynxHard-time status is recalculated nightly and reports into the same deadline horizon as directives and programme tasks. Component Status →

A maintenance policy where a component stays in service as long as it passes defined inspections or tests, with no fixed removal interval.

There is no date to watch, so the control is the inspection itself. If the inspection result is not recorded against the component, the policy has no evidence behind it.

In AerSynxComponent status carries the policy and its last result, so an on-condition item is not simply an item with no due date. Component Status →

Components managed by monitoring rather than a fixed life: their removal is driven by performance trends, inspection results or failure history.

Condition monitoring produces data that only matters if somebody reads it. Trend data with no threshold attached is an archive, not a control.

In AerSynxReliability periods are computed monthly and alerts are raised only when something changes, so the signal is not buried under a routine report. Reliability and Forecast →

Total hours and cycles accumulated by an aircraft, engine or component since manufacture. A cycle is normally one take-off and landing.

These numbers appear on dozens of screens and documents. When they are typed in more than one place they drift, and the version an auditor sees may not be the one the planner used.

In AerSynxCounters are derived from the flight timeline and recomputed after every leg, so a correction to a past leg flows through to every figure that depended on it. Flight Log →

Hours and cycles accumulated since a component's last overhaul — the counters that reset when the component is restored to a defined standard.

These reset and life limits do not, and the two are often shown side by side. Treating them as the same kind of number is how a part gets planned against the wrong figure.

In AerSynxSince-new and since-overhaul counters are held separately and derived from the same timeline, so an overhaul resets what it should and nothing else. Asset Registry →

A valuation and lease term describing an asset roughly midway between major maintenance events — about half its interval used, half remaining.

Lease agreements are written around this condition, so the difference between actual status and half-life is money. It is computed from the same counters that have to be right everywhere else.

In AerSynxPortfolio analytics read the maintained record rather than a separate commercial spreadsheet, so the technical status and the financial position are the same number. Portfolio →

The hours and cycles an aircraft actually flies over a period, used to forecast when maintenance and life limits will fall due.

Every forecast rests on an assumed rate. A fleet whose utilisation changes seasonally will produce due dates that quietly move.

In AerSynxForecast scenarios are independent analyses on shared aircraft, so an operator and a CAMO can hold different assumptions without overwriting each other. Overview →

A single forward view of everything that falls due across a fleet — directives, life limits, hard-time components, programme tasks, certificates and deferred defects.

Each of those lives in its own module in most systems, so the earliest due item is whichever module somebody happened to open.

In AerSynxAll of them report into one horizon, so the next thing due is not hidden inside a workspace nobody checked this week. Deadline Horizon →

The EASA approval held by a maintenance organisation permitted to carry out work on aircraft and components and to issue a certificate of release to service.

The approval defines scope: what the organisation may work on, with which people and tools. Work outside scope is not a paperwork problem, it is an unapproved release.

In AerSynxSkills, authorisations and tool calibration are held against the work, and a card cannot be signed by someone without the authorisation it requires. Production →

The statement signed after maintenance confirming that the work was carried out to the required standard and the aircraft or component is fit to return to service.

It is the point where responsibility transfers. Everything behind it — the task, the parts, the tools, the person — has to be traceable afterwards, sometimes years afterwards.

In AerSynxThe sign-off carries the work order, the card, the parts fitted and the person who booked the hours, and every change to it is written to the audit trail. Work Orders and Work Cards →

Work carried out between flights or overnight without taking the aircraft out of service: inspections, defect rectification and component changes at the gate or on the ramp.

Line work happens under time pressure and away from the office, which is why its records are the ones most often reconstructed later.

In AerSynxLine, base, shop and internal work are planned and closed in the same place as the record, so nothing waits to be re-entered afterwards. Production →

Scheduled work carried out in a hangar with the aircraft out of service, typically a C-check or heavier, including structural inspections and modification embodiment.

A base visit generates thousands of findings and task closures in a few weeks. Whatever is not captured as it happens is captured badly.

In AerSynxProjects carry the visit, its work orders and cards together, so the package that arrives from engineering and the evidence that closes it share one history. Projects →

Conventional names for scheduled maintenance checks of increasing depth. An A-check is light and frequent; a C-check is heavy, takes the aircraft out of service for weeks and covers most of its systems.

The letters are a planning shorthand, not a regulatory unit — what is actually due is the set of programme tasks that fall inside the visit.

In AerSynxVisits are built from the tasks that are actually due rather than from a label, so a check contains what the programme requires and no more. LDND and MPD Management →

The pair of values that controls a recurring maintenance task: when it was last accomplished and when it next falls due, in hours, cycles or calendar time.

Every recurring task in a programme is governed by this pair. One wrong last-done value moves every future occurrence of that task.

In AerSynxRecurring tasks are scheduled from the maintained record, and a correction to a last-done value flows forward instead of being patched task by task. LDND and MPD Management →

The instruction authorising a defined piece of maintenance, carrying its scope, the cards beneath it, the labour booked against it and its approval status.

It is the point where technical work becomes commercial work. If hours are re-entered into an accounting system by hand, the invoice and the record stop agreeing.

In AerSynxTime booked on a work order becomes the customer labour invoice directly, and the invoice line can be traced back to the card and the person who booked it. Labour to invoice →

The individual instruction a technician works to: the task, the steps, the required authorisation and the sign-off.

Cards are where findings appear. A card that can be closed with a finding still open is the single most common way an open item disappears.

In AerSynxA finding raised on a card blocks that card from closing until it is rectified or formally deferred — enforced where the record lives, not by a reminder. Work Orders and Work Cards →

The approved list of equipment that may be inoperative for a limited period while the aircraft continues to fly, with the conditions and the rectification interval that apply.

Every deferred item carries a deadline and conditions. The risk is not deferring — it is losing track of the interval, or applying the wrong category.

In AerSynxDeferred defects carry their deadline and are checked daily, and rectification requires evidence that resolves to the same aircraft before the item can close. MEL / CDL →

The approved list of secondary airframe parts that may be missing while the aircraft continues to operate, with the associated performance penalties and limits.

Unlike a deferred system defect, a missing panel has an operational cost attached. That penalty has to reach the people planning the flight, not just the record.

In AerSynxCDL items are tracked alongside MEL items on the same deadline checks rather than in a separate list nobody opens. MEL / CDL →

A defect that has been assessed and permitted to remain unrepaired for a defined period under the MEL or another approved basis.

Deferrals accumulate. A fleet's real condition is often better described by its open deferral list than by its last check.

In AerSynxOpen items report into the same horizon as everything else due, so a growing deferral list is visible rather than discovered. MEL / CDL →

An aircraft unable to fly until a part or repair arrives — the highest-urgency state in maintenance and supply, where cost is subordinate to time.

AOG decisions are made in minutes and documented afterwards, which is exactly when approval chains and supplier checks get skipped.

In AerSynxUrgent routes exist without removing the controls: an unapproved supplier can be used for a single order under an explicit, recorded exception rather than by bypassing the rule. Procurement →

The removal of an engine, APU or major component for workshop maintenance, and the event that records what was done to it and what changed as a result.

A shop visit changes counters, life status and sometimes the part itself. If the event is recorded as a note rather than as data, everything downstream is estimated.

In AerSynxShop visits are workflow events with evidence requirements attached, and the counters they affect are recomputed rather than typed. Workflow Events →

The complete documentary history of an aircraft and its components: release certificates, work packs, modification records, component paperwork and compliance evidence.

Records are an asset in their own right. At a sale or a lease return they are valued, and what cannot be found is treated as if it never happened.

In AerSynxEvery upload is read by OCR and summarised, then attached to the aircraft, engine or component it belongs to — not to a folder. Technical Records →

The authorised release certificate issued by an approved organisation confirming that a component was maintained or produced to an approved standard and is fit for installation.

A component without a valid release document is, for practical purposes, not fit to fit. The paperwork is not an administrative copy of the part — it is part of it.

In AerSynxRelease documents are held against the component and used as the evidence that closes the event they belong to, rather than filed separately. Evidence →

The FAA authorised release tag, serving the same purpose as an EASA Form 1 under United States rules.

Fleets and supply chains cross jurisdictions, so both forms appear in the same records — and a part accepted under one may need the other for a given operator.

In AerSynxBoth are recognised as release documents against the component, and the record search covers them together across the fleet. Record Search →

A release certificate issued under both EASA and FAA approvals at once, allowing the component to be installed under either system.

It is worth paying for and easy to lose track of. Whether a given part in stock carries dual release decides which customers it can be sold or fitted to.

In AerSynxRelease status travels with the stock item, so the question is answered from inventory rather than by opening a scan. Inventory →

The document attached to a component certifying its current airworthiness status — serviceable, unserviceable, or repaired to a stated standard.

Stock is only as good as its paperwork. An unserviceable part on a serviceable shelf is a stock error and a safety one at the same time.

In AerSynxStock carries its traceability with it, and reservations and expiries are checked daily rather than at the next stock take. Inventory →

The ability to show where a part came from, what was done to it and by whom, in an unbroken chain from manufacture to its current installation.

Traceability is not a document, it is a chain — and a chain is worth the weakest link. One undocumented transfer devalues everything after it.

In AerSynxA component is one record that moves with the physical part, so removal and reinstallation extend the chain instead of starting a new one. Asset Registry →

A record that does not merely exist but can answer what it shows, where it came from and which aircraft it belongs to — the standard a document must meet before it can close a critical item.

A scanned file attached to a record is not evidence until somebody can say what it proves. Most systems accept the attachment and ask nothing further.

In AerSynxClosing a critical event requires linked records that finished processing, carry a summary, are attached to an accepted event type and resolve to the same aircraft — checked on the server, so a failing record is refused with the reason. Evidence →

A recorded discrepancy — from an inspection, an audit or a document comparison — that has to be resolved or formally accepted before the work it belongs to can close.

Findings are the mechanism by which a problem stays visible. A finding that lives in an email is a problem that has already been forgotten.

In AerSynxFindings are tied to the record that produced them and block the closure of the work they belong to, including findings raised automatically by document comparison. Findings →

The immutable log of who changed what and when, kept so that a past state of the record can be reconstructed and explained.

The question at an audit is rarely what the value is now. It is who changed it, when, and under what authority — and that has to survive the person leaving.

In AerSynxEvery successful change writes an audit line against the organisation, and authority itself is recorded: who could have done it, and who did. Audit Trail →

The owner of the aircraft, engine or component that is leased to an operator — responsible for the asset's long-term value rather than its daily operation.

A lessor's interest is in condition and records, but the data is produced by somebody else's organisation. Most lessor reporting is therefore a request, not a query.

In AerSynxThe lease workspace reads the same aircraft record the CAMO maintains, so status is a query rather than a request to the operator. Lease Management →

The party operating the aircraft under a lease, responsible for its airworthiness and maintenance during the lease term and for returning it in the agreed condition.

Return conditions are agreed years before they are met, and the work needed to meet them is discovered late — usually too late to be cheap.

In AerSynxRedelivery readiness is derived continuously from the maintained record, so the gap appears while there is still time to close it. Transitions →

The return of an aircraft to its owner at the end of a lease, including the physical condition, the maintenance status and the complete records.

Redelivery disputes are almost always about documents, not aircraft. The cost of a missing trace at handback is far higher than it was at the moment it went missing.

In AerSynxMaster record completeness is derived after every event and reported by position, so a missing document is a visible blocker months before the inspection. Transitions →

The contractual requirements defining the state in which an aircraft must be returned: maintenance status, component life remaining, physical condition and the records that prove them.

These are written in commercial language and met with technical work. Translating one into the other is the whole job, and it is usually done in a spreadsheet.

In AerSynxReadiness is measured against the same record that the maintenance is recorded in, so the commercial condition and the technical status are not two systems. Lease Management →

The managed process of moving an aircraft between operators or owners — delivery, redelivery, or a change of registration — with its records, configuration and compliance status.

A transition compresses years of record keeping into a few weeks of review. Everything deferred during the lease arrives at once.

In AerSynxDelivery and redelivery run as tracked transitions on the operating record, not as a separate project started when the notice period begins. Transitions →

The point at which the receiving party signs that the aircraft and its records meet the agreed conditions, completing the handover.

Acceptance is granted against a list of open items. The shorter that list is at the start, the less leverage each item carries.

In AerSynxOpen items are visible on both sides of the handover because both sides read the same record. Comparison →

Payments made by an operator to a lessor against future major maintenance, held and drawn down as that maintenance is carried out.

Reserves are calculated from utilisation and maintenance status — the same numbers that have to be right everywhere else. A reserve built on a stale counter is a financial error.

In AerSynxPortfolio analytics read the maintained record, so the reserve position and the technical status come from one source. Portfolio →

Dismantling an aircraft or engine to recover serviceable components and life-limited parts for reuse or sale, usually at the end of economic life.

Value recovered at tear-down is almost entirely a function of traceability: a part with a broken trace is worth a fraction of an identical part with a complete one.

In AerSynxBecause component records move with the physical part rather than being archived per installation, the history that makes a recovered part saleable stays intact. Asset Registry →

A serialised component that can be repaired or overhauled back to a serviceable standard and returned to stock, carrying its own accumulating life record through every installation and removal.

A rotable's value is its history. The same part number with a complete trace and with a broken one are different assets at different prices.

In AerSynxStock is held against a single part master with traceability attached, and the component record follows the physical part rather than the shelf it sits on. Inventory →

A low-value item used up during maintenance and not recovered — seals, fluids, fasteners, lockwire.

Individually negligible and collectively substantial. Consumables are where stock accuracy is lost first, because nobody counts what nobody tracks.

In AerSynxConsumables share the same part master and movement history as rotables, so consumption is recorded where the work is recorded. Inventory →

A part that is discarded rather than repaired once removed, though it may be individually tracked and carry a release document.

Expendables sit between rotables and consumables and are often mis-classified, which distorts both stock value and reorder behaviour.

In AerSynxClassification is held on the part master, so the same item behaves consistently in stock, in procurement and on a work card. Inventory →

Buying a serviceable part at a reduced price by returning an unserviceable one of the same type, which the supplier then overhauls and returns to their own stock.

An exchange is not complete when the part is fitted — it is complete when the core is returned. The obligation outlives the transaction and is easy to lose.

In AerSynxCore obligations are tracked as their own commitments, with aging, penalties and credit notes handled daily rather than discovered at reconciliation. Core Obligations →

The unserviceable unit owed back to a supplier under an exchange, usually within a defined period and in a defined condition, with a financial penalty if it is late or unacceptable.

Cores are a debt denominated in parts. A fleet with untracked cores is carrying a liability it cannot quantify.

In AerSynxEvery core carries its deadline and condition terms, and aging runs on a schedule so the penalty is anticipated rather than invoiced by surprise. Core Obligations →

An FAA approval permitting a manufacturer other than the original to produce a replacement part, often at lower cost.

PMA acceptance is a commercial and contractual question as much as a technical one — some lease agreements restrict it, and that restriction has to reach the buyer.

In AerSynxAgreements and partner terms sit alongside procurement, so a restriction recorded in a contract is visible where the purchase is made. Agreements →

A request sent to suppliers for price, availability, condition and lead time on a part, and the first step of the procurement chain.

Quotes arrive by email in free form and are compared in a spreadsheet, so the reason a supplier was chosen is rarely recoverable afterwards.

In AerSynxRequests and the quotes that answer them are held on the same part master, so the award decision and its alternatives stay on the record. Procurement →

The check carried out when a part arrives: that it matches the order, that its documentation is valid and that its physical condition and shelf life are acceptable.

This is the last point at which a wrong or undocumented part can be stopped cheaply. After it reaches the shelf, the error is discovered on an aircraft.

In AerSynxReceiving is a recorded step against the order rather than a signature on a delivery note, and the part that landed is reconciled with the part that was ordered. Logistics →

Stock with a life of its own on the shelf — a cure date, a shelf life or a calibration due date — which expires whether or not the item is used.

Expiry happens in storage, silently. The first signal is usually a technician holding a part that cannot be fitted.

In AerSynxReservation, quotation and calibration expiries are checked daily, so an item going out of date is raised rather than discovered at the point of use. Tools →

A component designed to be replaced quickly at the aircraft rather than repaired in place, typically avionics or a system module.

LRUs move often and across aircraft, which makes them the components whose traceability is most likely to break.

In AerSynxMoving a component between aircraft carries its record with it instead of archiving one installation and opening another. Component Status →

The part number identifies what an item is; the serial number identifies which individual unit it is. Life and history are tracked against the serial number.

Systems that track only part numbers cannot answer which unit accumulated which life — which is exactly the question a lessor or an auditor asks.

In AerSynxThe part master is shared across the organisation while each serialised unit keeps its own record and history. Inventory →

The manufacturer's serial number of an airframe (MSN) or engine (ESN) — the permanent identity of that individual asset, independent of registration, which can change.

Registrations change with operator and country; serial numbers do not. Records filed by registration become hard to follow after a transition.

In AerSynxAssets are identified by serial number, so a change of registration does not fragment the history. Asset Registry →

Checking business partners against government restriction lists before trading with them, and continuing to check them afterwards.

A partner that was clean at onboarding may not be clean next quarter. Screening once is a record of the past, not a control.

In AerSynxFour lists are synchronised nightly and every partner is screened against them, with a blacklist report each Monday. Business Partners and Sanctions →