Component-history gap
Incomplete component history on installed parts
Incomplete component history means a rotable's recorded history skips one or more events in its life, such as an overhaul, a repair, or a change of ownership, so its current status and time-since-overhaul cannot be fully supported. It is a problem for lessors, airlines, and MROs at induction, redelivery, or component sale. The check reads component history cards, shop reports, release certificates, and the installation and removal entries that should account for every event. You receive the parts with gaps in their history, what each gap conceals, and the evidence needed to close it.
When this review is needed
- A hard-time or on-condition rotable is approaching a limit and the time-since-overhaul that the limit is measured against cannot be fully accounted for.
- A component is being sold or pooled and the buyer needs its full history before assigning value to the remaining life.
- An aircraft is inducted and the incoming team finds component cards that begin partway through the part's life with no earlier record.
- A part has moved between several operators and the chain of overhauls and repairs across those changes is broken.
The problem
A rotable's value and its next due point both rest on a continuous history of what has been done to it and when. That history lives on a component card that is supposed to follow the part, but cards get re-started at an overhaul, lost at a sale, or replaced with a summary that drops the detail behind the headline figures. The status list then states a time-since-overhaul and a condition that the underlying history can no longer fully support.
What gets reviewed
- Each rotable by part number and serial number across its recorded life
- Overhaul and repair events with the shop report and disposition for each
- Release certificates at every overhaul, repair, and change of custody
- Installation and removal entries linking the part to the aircraft it has been on
- Time and cycle accumulation reconciled across cards, shop reports, and status lists
- Changes of ownership and the history that should carry across each one
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- The component card accounts for every overhaul and repair across the part's recorded life
- Each event carries the shop report and release that supports it
- Time-since-overhaul is continuous from the last overhaul the records can produce
- Installation and removal entries reconcile with the serial number on the release
- A change of ownership shows the history carrying across rather than restarting
Evidence normally required
- Component history cards for the rotables in scope
- Shop and overhaul reports across the part's life
- Release certificates at each event and change of custody
- Installation and removal records or their digital equivalents
- Component status list with current time and cycle figures
Common discrepancies
- A component card that begins at an overhaul with no record of the life before it
- An overhaul referenced in the status list with no shop report or release behind it
- A repair performed at a prior owner that the current card does not carry forward
- Time-since-overhaul that cannot be tied to a producible last overhaul
- A serial number on the card that does not match the part the installation record names
What is at stake
A part whose history is incomplete may have to be treated as if its earlier life never happened, which can mean an early overhaul or a conservative life assumption that costs real money. On a sale or a pool, an unsupported history reduces what the part can be traded against, and reconstructing it after the deal is far harder than confirming it during diligence.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Set the part list
Identify the rotables in scope by part and serial number and pull the component card and status figure for each.
Walk the events
Trace every overhaul, repair, and custody change against its shop report and release, and mark where the trail breaks.
Test the status
Tie time-since-overhaul to the last producible overhaul and flag any figure the history cannot support.
Map recovery
Recommend sourcing the missing event evidence or a conservative treatment per part, and identify who can supply it.
What the buyer receives
- A per-part history record showing each event and where the trail is incomplete
- A statement of what each gap conceals and how it affects status or value
- A recovery path per part, whether sourcing a shop report, a release, or a conservative treatment
Who uses the output
- Records teams assembling the component history for a transaction or induction
- Asset teams pricing remaining life on a part with an incomplete trail
- Engineering deciding how to treat a rotable whose earlier life is unsupported
How the work fits into the transaction or program
The review isolates the history gap on a part-by-part basis within a wider records audit, so rotables that fail on a missing event are separated from those with a clean trail. It feeds the component section of a data room and the discrepancy register that drives recovery before the asset moves.
Jurisdiction-specific considerations
A shop report or release accepted under one authority is not automatically accepted under another, so where a part has moved across systems, the history has to show events documented in a form the receiving authority will accept. A part overhauled under one system may need a bridging release before its history supports installation under another.
Regulatory limits
The review confirms whether a component's history is complete, continuous, and consistent. It does not overhaul or re-certify the part, set its remaining life on the authority's behalf, or make an airworthiness determination.
What this review does not cover
- Physical inspection, test, or overhaul of the component
- Re-certification or re-life of any part
- Any airworthiness determination or regulatory acceptance
Specific to this review
- A component card is frequently re-started at an overhaul, so a card that looks complete may quietly drop the entire life before its first entry.
- Time-since-overhaul is only defensible from the last overhaul whose shop report and release can be produced, not from the figure the status list happens to carry.
- When earlier life cannot be supported, the conservative treatment is to disregard it, which can force an early overhaul on a part that may in fact have more life.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
Is a part with incomplete history unserviceable?
Not necessarily. The part may be sound, but its recorded status rests on history the records cannot fully show. Until the missing events are recovered, the status has to be read conservatively, which is what the review quantifies.
Can a missing shop report be recovered?
Often. The overhaul facility or a prior owner may hold the report or a duplicate release. The review identifies which parts are candidates for recovery and which are likely to need a conservative treatment instead.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Walk through your situation with an engineer who has done this work.