AD evidence depth
Task-level AD evidence rebuild for redelivery or pre-buy
This page is for airlines, operators, lessors dealing with Task-level AD evidence demanded in review. The review starts with the disputed or high-risk status claim, then checks it against AD status summary, lessor or buyer evidence request, work package archive, task-card completion records. Findings identify absent source pages, wrong-asset evidence, timing conflicts, and limits that should be disclosed rather than hidden. The buyer receives AD evidence depth scope note, task-level evidence map, legacy gap exception register so closure work can be assigned and tracked.
When this review is needed
- A counterparty has challenged the records position or asked for deeper evidence.
- The internal team can see a gap but has not defined the cure route.
- Several record families point to the same unresolved source document or status conflict.
- Commercial or program timing requires a defensible position before every document is recovered.
The problem
The difficult part is deciding what the records actually prove before the deadline or transaction pressure takes over. The status list closes ADs with no task-card references. Legacy compliance predates the current operator file and requires prior custodian recovery.
What gets reviewed
- Define the demanded evidence depth and negotiate any sample or risk-based boundary.
- Rebuild the evidence chain for selected AD lines from status to task-level proof.
- Flag lines where compliance predates the current operator records and needs alternate support.
- Separate unsupported status summaries from source evidence that is merely misfiled.
- Prepare exception language for legacy lines that cannot be fully rebuilt.
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 sampled AD line has task-level or equivalent source support.
- Fail when a status summary is resubmitted after task evidence was requested.
- Pass when legacy gaps are bounded with alternate evidence and disclosure.
- Fail when full back-to-birth evidence is accepted as scope without effort and value review.
Evidence normally required
- AD status summary
- lessor or buyer evidence request
- work package archive
- task-card completion records
- For this review, legacy operator source files
Common discrepancies
- The status list closes ADs with no task-card references.
- For this review, legacy compliance predates the current operator file and requires prior custodian recovery.
- A sampled line has source evidence under a check package, not the AD folder.
- The requester demands every line although the lease or deal can support a risk-based sample.
What is at stake
A weak response can turn a curable records defect into a holdback, delivery condition, audit repeat, or grounded planning assumption. The practical risk is carrying forward an unsupported position because nobody separated evidence gaps from administrative cleanup.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Frame Dirty Fingerprint
Confirm the exact event, affected file set, buyer role, and decision standard before any ad status list is treated as sufficient.
Trace Demand Task
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 Rebuild Redelivery
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Buy Depth
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
- AD evidence depth scope note
- task-level evidence map
- For this review, legacy gap exception register
- requester response pack
Who uses the output
- Records manager uses the findings to decide which gaps block the next milestone.
- CAMO postholder uses the evidence map to request, correct, or reserve records items.
- Redelivery manager uses the summary to brief stakeholders without reopening the full file.
How the work fits into the transaction or program
A lessor's rep at redelivery or a buyer's advisor at pre-buy rejects the AD status summary and demands task-card-level accomplishment evidence, the dirty fingerprints, for every AD line or a sampled subset; The negotiate a defensible sampling scope, then rebuild the evidence chain per AD from work packages, task cards, and certificates, flagging lines where compliance predates the operator's records. The evidence set centers on AD status summary, lessor or buyer evidence request, work package archive, and task-card completion records. The likely weak points are agreeing to full back-to-birth evidence on a mature aircraft without bounding effort, and treating an unsatisfiable legacy line as fatal instead of substantiating it by alternate evidence. Handoff: records manager, task-level AD evidence demanded in review, Task-level AD evidence rebuild for redelivery or pre-buy.
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
The output does not replace regulator review, authorized release, engineering approval, conformity finding, or the buyer's own acceptance process. It documents records support and records limits for the responsible parties to use.
What this review does not cover
- commercial dispute negotiation
- AD accomplishment work
- authority compliance determination
Specific to this review
- Dirty-fingerprint requests are often scope disputes as much as evidence disputes.
- A mature aircraft may need bounded legacy treatment instead of an unlimited rebuild.
- Task-level evidence is strongest when it links the AD paragraph to the exact work package step.
- Negotiating sample depth requires credible first-pass evidence, not refusal.
- The scope uses the Dirty Fingerprint Evidence Demand question as the control point, so the review stays tied to Task-level AD evidence demanded in review and the buyer decision behind it.
- The evidence starts with AD status list and follows Task Level Rebuild Redelivery 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 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 Pre Buy Depth They questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from AD evidence depth scope note; 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.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
What makes this problems review different from a general file audit?
The scope is tied to dirty fingerprint evidence demand and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block task-level ad evidence demanded in review or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad status list, 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 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.