Serial-number integrity
Duplicate serial-number records on a component
Duplicate serial-number records are two or more histories that carry the same part number and serial number, so a component's identity and its traceability cannot be relied on. It concerns lessors and acquisition teams on an engine or component transaction, airlines reconciling a fleet, and the MRO that received the part. The review separates the conflicting histories, tests each against release and installation evidence, and works out which records belong to the genuine part. You receive a conflict map per serial, the evidence distinguishing the histories, and the route to a single clean chain.
When this review is needed
- A status list shows one serial number against two different time-and-cycle histories.
- An incoming part's release names a serial number that already exists in the records under a different history.
- A fleet reconciliation surfaces the same rotable serial recorded on two aircraft.
- An engine transaction depends on a serial whose trace splits into two conflicting chains.
The problem
A serial number is the key that ties a part to its release, its accumulation, and its life status, and the records assume it is unique. When two histories share one serial, every downstream record built on it is suspect, because there is no way to know which accumulation and which release belong to the part actually installed. The conflict can come from a transcription error, a misread plate, a re-stamped part, or a counterfeit, and each cause closes differently.
What gets reviewed
- The conflicting histories carrying the same part and serial number, set side by side
- Release certificates for each history and the asset each was installed on
- Removal and installation records linking each history to a specific aircraft or engine
- Time-and-cycle accumulation for each history and where the chains diverge
- The likely cause of the duplication, from transcription error to a re-stamp or suspected counterfeit
- Life-limited-part status where the serial drives remaining life
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
- Each history is tied to a distinct release and installation event by evidence, not by assumption
- Removal and installation entries reconcile with the asset each history claims
- Time-and-cycle accumulation is internally consistent within each separated history
- The genuine part is identified against original release and birth documentation where available
- A re-stamped or relabeled part is distinguished from a transcription error
- Life-limited-part life remaining is recomputed against the correct, separated history
Evidence normally required
- The conflicting component histories and status-list entries
- Release certificates for each appearance of the serial number
- Removal and installation records and aircraft or engine logbooks
- Birth or original-equipment documentation for the part where available
- Shop-visit reports that may show a re-stamp or part substitution
Common discrepancies
- A transcription error that created a phantom second history from one real part
- Two genuinely different parts stamped or recorded with the same serial
- A re-stamped or relabeled part whose new identity overlaps an existing serial
- Release certificates pointing the same serial at two different aircraft
- A life-limited part whose remaining life cannot be trusted until the histories are separated
What is at stake
An unresolved serial duplication breaks traceability on the component, and on a life-limited part it can force conservative life assumptions or pull the part early. A buyer will not pay full value for a serial whose history is ambiguous, and on an engine transaction that ambiguity is expensive, so separating the histories before the deal is far cheaper than after.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Set the histories side by side
Assemble every record carrying the duplicated serial and lay the competing histories against each other.
Test against hard evidence
Use release, removal, and installation records to tie each history to a distinct part and asset.
Identify the genuine part
Determine which history belongs to the real component and classify the cause of the duplication.
Rebuild or escalate
Construct the single corrected chain, recompute life where needed, and escalate any suspected unapproved part.
What the buyer receives
- A conflict map per serial showing the competing histories and where they diverge
- The evidence distinguishing the histories and identifying the genuine part
- A recommended route to a single clean chain, including any escalation for a suspected counterfeit
Who uses the output
- Asset and acquisition teams pricing or clearing the component before a deal
- Records teams rebuilding the corrected component history
- Continuing-airworthiness staff recomputing life status once the histories are separated
How the work fits into the transaction or program
This narrows a traceability review to the specific case where a serial number is duplicated rather than merely incomplete. It feeds an LLP traceability review and the transaction discrepancy register, and it escalates any part where the duplication points to a re-stamp or a suspected unapproved part.
Aircraft-specific considerations
On engines and high-value rotables the serial drives life status and value, so a duplication there carries far more weight than on a low-value line-replaceable unit. The review is prioritized toward life-limited and serialized rotables for the specific engine or aircraft type rather than spread evenly across every part.
Jurisdiction-specific considerations
A release accepted under one authority is not automatically accepted under another, so where the separated histories cross the FAA and EASA systems, each history is tested against the release evidence the receiving authority will accept. A suspected unapproved part is escalated under the receiving authority's reporting expectations.
Regulatory limits
The review separates conflicting histories and identifies which records belong to the genuine part from the documentation. It does not physically verify the part, determine its airworthiness, re-life a life-limited part, or adjudicate a suspected unapproved part on the authority's behalf.
What this review does not cover
- Physical inspection, measurement, or material verification of the part
- Re-lifing or re-certifying a life-limited part
- Any airworthiness determination or regulatory adjudication of a suspected unapproved part
Specific to this review
- A serial number is treated as the unique key for a component, so a duplication makes every record built on that serial suspect rather than just one entry.
- The duplication can come from a transcription error, a re-stamp, or a suspected counterfeit, and the cause determines whether closure is a records fix or an escalation.
- On a life-limited part, the histories must be separated before remaining life can be trusted, because the wrong accumulation can be read against the part in service.
- A suspected unapproved part discovered through serial duplication is escalated rather than quietly corrected in the records.
Sources
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Does a duplicate serial number always mean a counterfeit part?
No. The most common cause is a transcription error that splits one real part into two histories. The review distinguishes that from a re-stamp or a genuinely duplicated serial, and only the latter cases are escalated as suspect.
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.