Component AD status
Component replacement AD status re-baseline
Technical records manager, Powerplant engineer, CAMO manager use this work when Component or engine swap surfaces stale AD status exposes a records gap with schedule or value consequences. EE reviews component removal and installation records, incoming part release documents, component history records, airframe AD status list against the stated requirement, the asset configuration, and the claimed status. The review distinguishes proven items, recoverable evidence gaps, conflicting records, and unresolved exposure. Deliverables include incoming component AD baseline, old versus new serial status comparison, corrected status list entries for the people managing closure.
When this review is needed
- A status claim has to be defended from primary records rather than accepted from a spreadsheet.
- The file contains enough evidence to investigate but not enough organization to rely on.
- A prior maintenance, ownership, or configuration event may have broken traceability.
- Managers need to know which requests should go out first.
The problem
The difficult part is deciding what the records actually prove before the deadline or transaction pressure takes over. The incoming engine or LRU carries different AD history than the removed serial. Tracking software keeps the airframe-level closure after component replacement.
What gets reviewed
- Identify ADs attached to the incoming component, engine, LRU, or LLP serial.
- Compare the old part compliance status with the incoming part evidence.
- Check release certificates for AD status statements and supporting history.
- Reset repetitive AD clocks where the component serial changes.
- Correct the airframe status list so it no longer inherits removed-part closures.
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
- Pass when each component-level AD is answered for the installed serial.
- Fail when the airframe status retains compliance from the removed part.
- Pass when repetitive next-due values follow the incoming component history.
- Fail when blank AD status blocks on pool exchange paperwork are ignored.
Evidence normally required
- For this review, component removal and installation records
- incoming part release documents
- For this review, component history records
- airframe AD status list
- parts trace documents
Common discrepancies
What is at stake
Without a structured review, teams often spend time on easy file cleanup while the material blocker waits. That can leave the asset, program, or transaction exposed to late exceptions that should have been started earlier.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Frame Status Reset
Confirm the exact event, affected file set, buyer role, and decision standard before any removal and installation records is treated as sufficient.
Trace Component Replacement
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Swapped Stale
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Compliance Swap
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- incoming component AD baseline
- old versus new serial status comparison
- corrected status list entries
- open supplier evidence request list
Who uses the output
- Technical records manager uses the findings to decide which gaps block the next milestone.
- Powerplant engineer uses the evidence map to request, correct, or reserve records items.
- CAMO manager uses the summary to brief stakeholders without reopening the full file.
How the work fits into the transaction or program
When an engine, LRU, or life-limited part is replaced, every AD that attaches to the component must be re-answered for the incoming serial, and most tracking systems keep the airframe-level closure instead; Problem definition: identify component-level ADs affected by each replacement, obtain the incoming part's compliance history from its release paperwork and back-to-birth records, and correct the status list where the old part's compliance was silently inherited; removal/installation records,. The evidence set centers on removal/installation records, 8130-3 or EASA Form 1 with AD status statements, component historical records. The likely weak points are pool exchanges with blank AD status blocks on the release certificate, engines swapped between tails carrying open AD actions nobody transferred, and repetitive component ADs continuing on the old part's clock. Handoff: technical records manager, component or engine swap surfaces stale AD status, Component replacement AD status re-baseline.
Jurisdiction-specific considerations
FAA and EASA references are used as evidence criteria for records completeness and traceability. The review does not treat one authority's records as automatic acceptance by another authority or by a transaction counterparty.
Regulatory limits
EE identifies whether the supplied records support the stated position. EE does not make final airworthiness determinations, issue certificates or approvals, or guarantee how an authority or counterparty will treat the evidence.
What this review does not cover
- For this review, component maintenance work
- supplier warranty claims
- new AD applicability interpretation
Specific to this review
- For this review, component AD status travels with the installed serial, not with the aircraft spreadsheet line.
- Pool exchanges are high-risk because the incoming history is often thinner than the removed part file.
- A replacement can reopen an AD question that looked closed at airframe level.
- Status correction should happen at installation, before the next audit inherits the wrong baseline.
- The scope uses the Status Reset After Component question as the control point, so the review stays tied to Component or engine swap surfaces stale AD status and the buyer decision behind it.
- The evidence starts with removal and installation records and follows Replacement Baseline Swapped Stale references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for Technical records manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Establishing Compliance Swap Inheritance questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from incoming component AD baseline; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
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
What makes this problems review different from a general file audit?
The scope is tied to status reset after component and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block component or engine swap surfaces stale ad status or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is removal and installation records, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives technical records manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.