Glossary
A glossary of continuing airworthiness terms
Twenty-seven terms that come up in every conversation about aircraft records, explained so that you do not have to read the regulation first. Each entry has a definition and — separately and explicitly marked — one sentence on how that thing looks inside CamoBook.
Records
The technical logbook
Terms that appear on every flight — which means dozens of times a day in a training organisation.
-
Techlog
Short for: aircraft technical log
-
The document kept with the aircraft in which every flight is recorded after it happens: times, counter readings, landings and the technical state — NIL or a reported defect. It is the source of the flight time used to compute maintenance due points, and the first evidence that the aircraft was operated as the records say.
In CamoBook
One entry per flight, never a daily summary. A saved but unsigned entry is a draft and moves no counter.
More Electronic techlog The techlog entry: what it has to contain
-
Electronic techlog
Short for: e-techlog, computerised technical log
-
A technical logbook kept in a computer system instead of on paper. The regulation does not require paper — it requires a record system that meets the conditions set out in AMC1 ML.A.305: a backup kept separately from working data, legibility for the whole retention period, protection against unauthorised change, access control and a written procedure for when the system is unavailable. Acceptance of the system is issued by the operator’s authority.
In CamoBook
The pilot signature posts counters and recomputes task due points immediately, so there is no second register to retype into.
More Electronic techlog The electronic techlog and Part-ML: what a record system must do
-
NIL
-
The entry stating that no defect was found after a flight. It is the opposite of an empty field: an empty field means “nobody answered”, while NIL means “somebody checked and reports nothing”. That is why an entry with neither NIL nor a described defect is an incomplete entry.
In CamoBook
An entry requires NIL or at least one defect — the form offers no third option, and without that field the signature does not pass.
More Electronic techlog The techlog entry: what it has to contain
-
Reversal
Short for: correcting entry
-
The way to correct an error in a record that must not be edited: instead of changing the original entry, you add a record that undoes its effects and then enter the correct one. All three events stay in the register, so you see not just the final state but also what was corrected and why.
In CamoBook
A reversal requires a justification and posts compensating increments on the counters; the original entry stays, flagged as reversed.
More Electronic techlog
-
Block time
Short for: block off / block on
-
Time counted from the moment the aircraft moves from its parking position under its own power until it stops after the flight. It is longer than airborne time because it includes taxiing, and it is usually the basis for accruing hours in the maintenance programme and in training records.
In CamoBook
Times are stored in whole minutes — no decimal hours, because those are what leave you a quarter of an hour short after a year.
More Electronic techlog The techlog entry: what it has to contain
-
Tach time
Short for: tachometer time, in some aircraft Hobbs time
-
Time accrued in proportion to engine speed, so it grows more slowly than block time at low RPM. Many maintenance programmes tie part of their tasks to this counter rather than to block time — which is why both counters must be kept independently and one must never be converted into the other.
In CamoBook
Block and tach are separate accrual bases; each task states which one it is measured on.
More Electronic techlog The techlog entry: what it has to contain
Rules
Rules and organisations
What is what in the European continuing airworthiness system — and who is responsible for which part of it.
-
Part-ML
Short for: Annex Vb to Regulation (EU) No 1321/2014
-
The set of lighter continuing airworthiness requirements for smaller aircraft not used in commercial air transport, covering among other things the maintenance programme, records, maintenance and the airworthiness review. It exists so that general aviation does not have to run on a regime written for airlines.
In CamoBook
The whole product section of this site is organised around the mechanisms an operator uses to demonstrate Part-ML compliance.
More Electronic techlog The electronic techlog and Part-ML: what a record system must do
-
Part-CAMO
Short for: Annex Vc to Regulation (EU) No 1321/2014
-
Requirements for an organisation managing continuing airworthiness: structure, personnel, procedures, management system and record keeping. It applies to the organisation rather than to the aircraft — Part-ML says what has to happen to the machine, Part-CAMO says how the outfit doing it has to be organised.
In CamoBook
The event register covers CAMO actions: task compliance, counter corrections, bulletin assessments and generated authority packs.
More Maintenance tracking
-
ML.A.305
Short for: the Part-ML point on the record system
-
The point of the regulation that sets out what the continuing airworthiness records of an aircraft must contain: a record of every flight, a record of maintenance referencing the release to service, the status of the maintenance programme, of directives and of life-limited parts, accuracy and currency of records, no editing after certification, and retention periods.
In CamoBook
The electronic techlog page maps each requirement to its mechanism, row by row.
More Electronic techlog The electronic techlog and Part-ML: what a record system must do
-
AMC and GM
Short for: Acceptable Means of Compliance, Guidance Material
-
Material issued by the Agency alongside the rule itself. An AMC describes a way of meeting a requirement that is accepted as adequate — you may comply differently, but then you have to demonstrate it. GM provides explanation and examples. For an electronic logbook the key one is AMC1 ML.A.305, because it spells out the conditions for a computerised system.
In CamoBook
The AMC1 ML.A.305 conditions — backups, legibility, protection against change, access control, an outage procedure — are described on the records security page.
More The electronic techlog and Part-ML: what a record system must do
-
CAMO
Short for: Continuing Airworthiness Management Organisation
-
The organisation that manages continuing airworthiness: it looks after the maintenance programme, due dates, airworthiness directives and bulletins, keeps the records and is responsible for the aircraft remaining airworthy. It is not the same as a workshop — CAMO manages and documents; maintenance is performed and released by a maintenance organisation.
In CamoBook
The fleet due list, task statuses, the document catalogue and the authority export are views written for CAMO’s daily work.
More Maintenance tracking
-
CAO
Short for: Combined Airworthiness Organisation, Annex Vd
-
An organisation that holds continuing airworthiness management and maintenance of lighter aircraft under a single approval. For smaller operators it is often more practical than maintaining two separate approvals, because the same organisation keeps the records and performs the work.
In CamoBook
Version 1.0 serves one organisation; a workshop or an authority receives a complete document pack rather than an account in the system.
More Who it is for
-
ATO and DTO
Short for: approved and declared training organisation
-
Two ways of running flight training: an ATO operates under an approval and can deliver a wide range of training, while a DTO operates on a declaration and covers a narrower scope, typically non-professional licences and basic ratings. For technical records the difference is secondary — both have many pilots on one aircraft and the same need for an attributable signature.
In CamoBook
Accounts are individual and a pilot signs only their own entry — a shared “pilot” login would destroy signature attribution.
More Who it is for
Documents
Certificates and publications
The papers you watch ahead of time, and the technical documents that arrive from outside.
-
ARC
Short for: Airworthiness Review Certificate
-
The document confirming that the aircraft records demonstrate its airworthiness. It is issued after an airworthiness review, which consists of a records review and a physical survey of the aircraft. The certificate is valid for a year and — if the aircraft has stayed in a controlled environment — it can be extended, typically twice by one year; after that a full review is performed.
In CamoBook
The ARC is a document with an expiry date: it appears on the due list, and an e-mail alert goes out 60 and 30 days before.
More Maintenance tracking The ARC and the airworthiness review: an operator's calendar
-
CofA
Short for: Certificate of Airworthiness
-
The basic certificate of an aircraft, issued when it enters service and remaining valid as long as the conditions for keeping it are met. It is the ARC that confirms those conditions are still met — which is why the ARC is the one with a date to watch in the calendar.
In CamoBook
The CofA, insurance, noise certificate and AFM live in aircraft documents and follow the same alerts as maintenance tasks.
More Maintenance tracking The ARC and the airworthiness review: an operator's calendar
-
CRS
Short for: Certificate of Release to Service
-
The document issued after maintenance, stating that the work was carried out in accordance with the requirements and that the aircraft may return to service. It is issued by certifying staff or a maintenance organisation — not by a software system and not by CAMO.
In CamoBook
CamoBook does not issue a CRS. When recording compliance you enter its number, the date of the work and the counter state, and the scan goes into the records.
More Maintenance tracking
-
AD
Short for: Airworthiness Directive
-
A document issued by an aviation authority in response to an identified unsafe condition, mandating specific actions by a stated deadline. It is mandatory by law — there is no “is it worth it” assessment, only the question of whether it applies to a given airframe.
In CamoBook
A task arising from a directive enters the maintenance programme with zero tolerance, so the tracking engine knows no exceedance window for it.
More Bulletins and ADs ADs, SBs and SLs: what is mandatory and what is advisory
-
SB
Short for: Service Bulletin
-
A manufacturer publication describing a recommended modification, inspection or change to maintenance practice. It is not mandatory in itself: it becomes mandatory only when an airworthiness directive, the maintenance programme, the airworthiness limitations section, a condition of the airworthiness review or a deliberate CAMO decision makes it so.
In CamoBook
Bulletins are ingested daily into a review queue; the applicable / not applicable call belongs to CAMO and is stored with the person and the timestamp.
More Bulletins and ADs ADs, SBs and SLs: what is mandatory and what is advisory
-
SL
Short for: Service Letter
-
A manufacturer publication of an informational nature: a clarified procedure, an explanation, a warning about an observed phenomenon. It usually imposes no obligation, but it is often the basis of a later bulletin or directive — which is why it belongs with the rest of the documents rather than in an inbox.
In CamoBook
Service letters land in the same catalogue as bulletins and carry the same decision trail.
More Bulletins and ADs ADs, SBs and SLs: what is mandatory and what is advisory
Limits
Maintenance programme and life limits
This is where due dates come from — and where most conversations about records break down.
-
AMP
Short for: Aircraft Maintenance Programme
-
The document setting out which maintenance actions are performed on a specific aircraft and at what intervals — with hour, calendar and cycle limits, tolerances and references to manufacturer documentation. It belongs to the operator and is subject to revisions.
In CamoBook
Tasks are matched across revisions by their code, so changing the programme does not erase compliance history.
More Maintenance tracking Tolerances without drift: how to compute inspection due points
-
Life limit / interval
Short for: the limit between maintenance actions or to retirement
-
The permitted usage before a maintenance action is due or before a part is withdrawn from service, expressed in hours, cycles, calendar time, or several of these at once. When limits appear together, the rule written in the maintenance programme applies: whichever comes first, or whichever comes later.
In CamoBook
Axes are computed separately and the task status is the worst of them — not an average, not the first in the list.
More Maintenance tracking Tolerances without drift: how to compute inspection due points
-
LLP
Short for: Life-Limited Part
-
A part for which the manufacturer has set a hard life limit — once reached, the part is withdrawn from service regardless of its condition. The limit carries no tolerance, and the installation history of such a part is among the first documents examined during an airworthiness review and when an aircraft is sold.
In CamoBook
Zero tolerance for life-limited parts is enforced in the database rather than by an application rule that could be bypassed.
More Maintenance tracking Tolerances without drift: how to compute inspection due points
-
Tolerance
Short for: the permitted window past a due point
-
The margin defined in the maintenance programme within which an action may be performed after its planned due point without breaching the programme. What matters most is what the next due point is counted from: if it is counted from the actual compliance date, the schedule drifts forward and after a few years the “100 h” inspection really happens every 115 hours.
In CamoBook
The anchor for the next due point is the earlier of two values — the actual compliance or the planned due point — so the cycle does not creep forward.
More Maintenance tracking Tolerances without drift: how to compute inspection due points
-
Due list
Short for: a ranked view of approaching due points
-
A list of tasks and documents ordered by remaining margin — how many hours, cycles or days are left. It is the basic maintenance planning tool: it answers which aircraft will stop first and whether that can be reconciled with the season.
In CamoBook
The margin is not a stored number but a subtraction computed at read time — there is nothing to refresh.
More Maintenance tracking Tolerances without drift: how to compute inspection due points
Rollout
Leaving paper, and evidence
Three terms without which a conversation about dropping the paper logbook ends in a misunderstanding.
-
Opening balance
Short for: the starting state carried over from paper
-
The data entered when an electronic system goes live: current counter readings, the maintenance programme tasks, and the dates and counter states of the last compliances. Flight history is not migrated — you carry over the state from which counting starts, together with a note on which document it came from.
In CamoBook
Three CSV files, a dry run that stores nothing, and a commit under a mechanic signature with a note on the source of the data.
More Pricing From paper to electronic records without losing history
-
Dual-run
Short for: keeping two logbooks in parallel
-
A period during which records are kept both on paper and in the electronic system, with paper prevailing in case of divergence. It serves two purposes: catching differences before they become a problem, and building the evidence base for the conversation with the authority about leaving paper behind.
In CamoBook
Rollouts run as a dual-run until the authority accepts the system — the decision to leave paper belongs to the operator and its authority, not to the software vendor.
More Security From paper to electronic records without losing history
-
Authority pack
Short for: the complete records set for an audit
-
The set of documents presented during an audit or an airworthiness review: the flight register for a period, task statuses and compliances, the status of directives and bulletins, components with installation history, defects and aircraft documents. Its value rests on two things — completeness, and whether it can be read without the system that produced it.
In CamoBook
One ZIP in open formats (CSV and PDF) with a manifest of SHA-256 checksums; generating the pack is recorded in the event register.
More Security The ARC and the airworthiness review: an operator's calendar
Disclaimer
These definitions are short and written in our own words — they exist to make a term understandable, not to interpret it. What binds you is the current consolidated text of Regulation (EU) No 1321/2014 and its annexes (Part-ML — Annex Vb, Part-CAMO — Vc, Part-CAO — Vd), the Agency’s AMC and GM material, and the procedures approved for your organisation. This is neither legal advice nor an authority position.
Next
The nearest topics — on the site and in the knowledge base.
On the site
- Electronic techlog
One entry per flight, an electronic signature, immutability and work with no signal.
- Maintenance tracking
Hour, calendar and cycle limits, tolerances without drift, due-date forecasting.
- Bulletins and ADs
Automatic ingest of SBs, SLs and ADs, review and sign-off, manual route.
In the knowledge base
- The electronic techlog and Part-ML: what a record system must do
What ML.A.305 and AMC1 ML.A.305 expect from a computerised technical logbook, and what you actually have to show an inspector to leave paper behind.
- Tolerances without drift: how to compute inspection due points
Why inspections creep forward, how anchoring to the planned due point fixes it, and what to do with a task that has an hour limit and a calendar limit at once.
- ADs, SBs and SLs: what is mandatory and what is advisory
Airworthiness directives always bind you; manufacturer bulletins only once something makes them binding. Where the line runs, where to source documents across the EU, and how not to confuse an SIB with an AD.
See CamoBook on your own fleet
Thirty minutes, live: a signed techlog entry, the due list for your aircraft type and the audit pack. No sales deck — we talk about your maintenance programme.
or write to pawel@mamcarz.com