Component trace evidence
Reviewing task-card records inside a component-history source file
This review tests whether the closed task cards inside a component-history source file actually support the trace claimed for a serialized part. A records specialist reads each card against the removal and installation entries, release certificates, and shop paperwork gathered in the same file, working card by card rather than from the work-order summary. It is typically commissioned during a serialized-component trace review, before the file is presented to a lessor, buyer, or auditor. The output is an exception list naming every card whose sign-off, reference, or part movement cannot be matched to source evidence.
When this review is needed
- A serialized part is being sold or exchanged and the buyer wants the work history behind it proven, card by card.
- A lessor has questioned a component trace and the cards cited in it have never been read against their own references.
- A closed work package is the only evidence that a removal and reinstallation happened, and the sign-offs on it look thin.
- An audit sampled the component file and found a card referencing a part movement the file cannot show.
The problem
Task cards are where the physical work on a component was actually recorded, yet most trace files quote the work-order summary and never open the cards. Sign-off blocks get missed on the last shift of a check, part numbers get transcribed from memory, and a card can reference a removal that generated no matching installation record. The records lead discovers this only when a counterparty starts reading the cards themselves.
What gets reviewed
- Every closed card in the package tied to the subject component, read in full rather than sampled
- Sign-off completeness on each card, including inspection stamps where the task required them
- Part removals and installations recorded on cards matched to the file's movement records
- References from cards to approved data, work orders, and non-routines confirmed to resolve
- Card dates and locations checked against the component's serial-number history
- Cards cited by the trace summary confirmed to exist in the delivered set
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 card carrying a part movement has a corresponding removal or installation entry elsewhere in the source file
- Sign-off blocks are complete for every step the card required, with no steps closed by a package-level signature alone
- Part and serial numbers written on cards agree with the installed-part list and the release certificates in the file
- Card references to non-routine cards or engineering dispositions resolve to documents present in the package
- The dates on the cards sequence sensibly against the component's known shop visits and fitment history
Evidence normally required
- The closed task-card set for the work packages touching the component
- The component-history source file, including removal and installation records and release certificates
- The installed-part list or fitment history for the subject serial number
- Work-order summaries and any non-routine cards the task cards reference
- The current draft of the component trace the cards are meant to support
Common discrepancies
- Cards closed with the mechanic's signature but no inspection stamp on steps that called for one
- A removal written on a card with no installation record for the replacement part anywhere in the file
- Serial numbers on cards that disagree with the release certificate for the same event
- Trace summaries citing card numbers that are absent from the delivered card set
What is at stake
A trace that leans on unverified cards collapses at the worst moment, in front of the party paying for the part. Once a single card shows a missing sign-off or an orphaned part movement, every other card in the package becomes suspect, and the negotiation shifts from price to whether the component is tradable at all.
How the work runs
Fix the card population
Establish which work packages touched the component and confirm every card from those packages is in hand.
Read each card
Check sign-offs, steps, part movements, and references on every card rather than sampling.
Match to source
Tie each part movement and reference to the movement records, certificates, and non-routines in the file.
Issue the exception list
Deliver card-level exceptions with the specific missing element named for each.
What the buyer receives
- An exception list keyed to individual card numbers, stating what each card fails to support
- A cross-reference table linking cards to the movement records and certificates that back them
- A short memo on whether the card set, as delivered, sustains the component trace
Who uses the output
- The component records lead deciding which cards need replacement evidence before the trace ships
- Quality managers responding to audit findings sampled from the card set
- Asset managers judging whether a part can go to market on its current paperwork
How the work fits into the transaction or program
Within a serialized-component trace review, the task-card layer sits between the movement records and the shop paperwork. This review clears that layer so the trace builder can cite cards with confidence, and its exception list feeds the remediation work that follows, usually requests back to the performing organization for corrected or supplementary records.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Under 14 CFR 43.9 each maintenance entry must describe the work and identify who approved it for return to service, so a card missing that identification is a defect in the record itself, not a formality. EASA operators working under Regulation 1321/2014 face the parallel expectation through Part-M record retention, and a card set crossing between the two systems is read against whichever regime governed the work when it was done.
Regulatory limits
The review reports on what the cards evidence and where they fall short. It does not approve work for return to service, does not judge the airworthiness of the component, and does not recreate or sign records on behalf of the organization that performed the maintenance.
What this review does not cover
- Physical inspection of the component the cards describe
- Re-performance or engineering evaluation of the maintenance tasks themselves
- Authoring replacement task cards or obtaining signatures for open steps
Specific to this review
- Package-level closure signatures hide the most defects: a work order can be signed complete while individual cards inside it still carry open steps.
- Cards written during a hangar visit's final days show the highest transcription error rate, because part movements are recorded after the fact from staging tags.
- A card that references a non-routine by number is only as strong as that non-routine's presence in the file; the reference alone proves nothing.
- When a component has crossed operators, the same task can appear on two card formats, and traces often cite the format the current owner recognizes rather than the one that was actually executed.
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. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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
The work order is signed off as complete. Why read the individual cards?
A work-order closure attests that the package was finished, but the trace for a serialized part hangs on specific cards: the one recording its removal, the one recording its installation, and any card that touched it in between. Those cards carry the sign-offs, serial numbers, and references a counterparty will check, and package-level closure does not cure a defect inside them.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.