Nexus Aero
Follow us
Stay updated
NEXUS AVIATION JOURNALPractical knowledge · Considered analysis · Clear sources
Practical guideMaintenance & repair4 min read

A life counter needs a history, not just a number

An overhaul entry does not explain every life counter. Build the evidence chain before comparing remaining life or presenting an engine component to a buyer.

Nexus editorialPublished:
Illustrative aviation image; not evidence of a specific item, approval, applicant or customer

Illustrative image—not evidence of a real case or verified capability.

Separate the clocks before comparing offers

Consider a hypothetical engine component offered with an overhaul certificate and a remaining-life figure. A buyer might read both as one reassuring status, although they describe different things. A maintenance event records work performed; an accumulated counter describes use; an applicable limit defines a boundary for a particular part and configuration. The first records task is to establish which counter the figure represents and which evidence supports it. Do not reset time since new merely because time since overhaul changed. Equally, do not assume that every serialized item is life-limited. Start from the identified part, its actual control basis and the responsible technical function, rather than a universal field labelled life.

Make every counter a dated statement

A useful counter record states the value, unit, effective date and source together. Hours, cycles, landings and calendar time cannot be combined by visual proximity. Record whether a figure belongs to the whole engine, a module or a specific serialized part. If a part moves between assemblies, preserve the relevant installation and removal intervals rather than assigning the current engine total to its entire past. A spreadsheet import should flag a missing date or ambiguous unit for review. It should not infer a value from a neighbouring row. The resulting record can support a calculation while still making clear which inputs were supplied, independently checked or left unresolved.

Link the limit to the exact identity

EASA's technical-records FAQ distinguishes the continuing-airworthiness record obligations associated with life-limited components and the information retained with their histories. It also cautions against treating the commercial expression back to birth as the wording of a universal European rule. For a practical review, ask for the identified limitation source, revision and applicability, then keep the source separate from the arithmetic. A component may have more than one relevant restriction. A remaining-cycle display should not conceal a calendar constraint or an unresolved configuration question. For Iranian operations, the applicable authority, approved programme and controlled technical information govern the decision; a European reference article cannot decide national applicability for an operator.

Agree the transfer package before dispatch

Before a commercial commitment, list the records the receiving party needs, their format and the point at which they will be reviewed. Separate a current status summary from the documents supporting that summary. Identify missing intervals, legibility problems and contradictions explicitly. A supplier may be able to locate a better scan or obtain clarification from the issuing organisation, but neither party should rewrite an old document to make the package look complete. Tie each question to the exact serial number and transaction. When an answer arrives, retain the original question and the evidence that resolved it. A handover is stronger when the receiver can explain the history without relying on the seller's memory.

Correct the record without erasing the past

Suppose a receiving reviewer discovers that one cycle figure was transcribed incorrectly. A controlled correction should retain the previous value, corrected value, supporting document, author and time, together with the effect on any downstream calculation. Review whether the same figure already appeared in an offer, lease schedule or maintenance planning record. Merely fixing the inventory row leaves those copies inconsistent. Notify the responsible parties through the agreed process and preserve what they acknowledged. If the evidence cannot establish the correct number, keep the uncertainty visible and route the item for disposition. A green dashboard is not a reason to choose the more convenient of two conflicting totals.

Prove the chain with one component

Use one synthetic component to rehearse the record chain: receipt, installation interval, removal, maintenance event, offer and transfer. Ask a second person to distinguish total life, maintenance-related counters and the applicable limitation without opening unrelated files. Then introduce a missing source date and check that the calculation stops presenting a falsely precise result. This exercise tests record design, not technical acceptability. Its practical outcome is a short unresolved-evidence list with owners and next actions. Extend the pattern only after the team can reconcile the component's identity, history and current statement. Software should help qualified people find and explain the evidence; it should never manufacture life credit or an installation authorization.

Sources & scope

This is editorial educational analysis. Licensed manuals are not reproduced; Iranian applicability and independent technical approval are not established. Actual operations require current controlled sources and authorized decisions.

EASA — Technical records FAQ — opens in a new tabReference for the limited discussion of life-limited-part records. The workflow examples are the Journal's original analysis; national applicability and contractual requirements need separate review.Source link checked: 17 Oct 2026

Continue with the Library tools

Related reading

On this page
ONE MINUTE TO THINK

Test the idea, not just your memory

Short learning scenarios with explained answers—not a qualification test, training certificate or operational decision.

A component was overhauled. What should happen to its total-life counter?
About Nexus editorial

Educational and analytical writing with explicit references—not maintenance instructions, airworthiness decisions or authority approval. Analysis, news, experience and sponsored content must remain distinguishable.

Suggest a topic or report a correction