AD evidence bundle
Airworthiness directive compliance evidence checklist
airlines, operators and Aircraft records teams turn to this checklist when assembling AD compliance evidence exposes uncertainty in airworthiness directive compliance evidence checklist. We compare AD applicability determination, method of compliance mapping, maintenance record entry, and recurring inspection next-due status with the delivered record set and applicable acceptance criteria. The work separates amoc used with no approval letter, recurring ad shown complied once with no next due, and ordinary cleanup. Deliverables include a source-indexed register, document request list, and management readout.
When this review is needed
- Records manager is preparing for a handover, review, submission, or acceptance gate.
- method of compliance mapping is referenced in the package but not clearly tied to the current status.
- The counterparty asks for evidence by serial, task, revision, or approval basis.
- Commercial timing requires a short list of findings with owners and closure evidence.
The problem
The file can look orderly while still leaving the central acceptance question open. Records manager, Airworthiness engineer and Compliance analyst need enough context to decide whether a mismatch is a clerical defect, a missing document, or a technical blocker.
What gets reviewed
- Review the claimed position for AD applicability determination against delivered source records.
- Tie method of compliance mapping to the specific task, part, aircraft, engine, or approval record.
- Compare maintenance record entry with the supporting release, test, inspection, or log entry.
- Check whether recurring inspection next-due status changes the status, due basis, or eligibility position.
- Document the exact record correction or replacement evidence needed.
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
- Confirm the evidence names the same aircraft, engine, assembly, or software item as the status line.
- Mark a discrepancy when method of compliance not mapped to the directive text.
- Verify revision-sensitive documents against the version used for the recorded work.
- Do not close a finding until the file contains the source page or an accepted correction.
Evidence normally required
- AD applicability determination
- method of compliance mapping
- maintenance record entry
- recurring inspection next-due status
Common discrepancies
- AMOC used with no approval letter.
- Recurring AD shown complied once with no next due.
- Method of compliance not mapped to the directive text.
What is at stake
Unsupported status can block handover, slow a program gate, or reduce confidence in the whole data room. A small number of unresolved records often drives the commercial response.
How the work runs
Frame Evidence Bundle
Confirm the exact event, affected file set, buyer role, and decision standard before any ad applicability determination is treated as sufficient.
Trace Directive Checklist
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 Compliance Proves
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Assemble Complete
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
- Source-linked findings log for airworthiness directive compliance evidence checklist
- Evidence matrix by serial, task, approval, or status line
- Open-item tracker with requested replacement records
- Management note explaining residual records risk
Who uses the output
- Records manager uses the findings log to set the technical position.
- Airworthiness engineer uses source references to challenge or close exceptions.
- Compliance analyst uses the summary to align records, quality, and commercial teams.
How the work fits into the transaction or program
This checklist covers the evidence bundle that proves compliance with a single airworthiness directive, and it names the hardest items to assemble: the applicability determination tying the AD to this aircraft or engine by serial and configuration, the method of compliance actually used mapped to the AD's paragraph including any alternative method of compliance approval, the maintenance record entry with date, hours, and cycles at compliance, and the recurring-inspection status if the AD is not terminating. The evidence set centers on the AD text, the AMOC letter if any, the work record, and the current status line. The likely weak points are an AD closed by an AMOC with no approval letter in the file, and a recurring AD shown as complied once with no next-due tracking, both of which fail an audit. Handoff: records manager, assembling AD compliance evidence, Airworthiness directive compliance evidence checklist.
Jurisdiction-specific considerations
FAA and EASA references are used as record expectations for the evidence set. The review does not assume automatic acceptance by another authority, operator, or contract party.
Regulatory limits
The deliverables support decision-making but do not replace required inspections, approvals, conformity activity, or authorized signatures. Final acceptance stays with the regulator, authorized personnel, and the parties applying their approved processes.
What this review does not cover
- Airworthiness release, conformity sign-off, or approval issuance
- Creation of missing source records where work was not documented
- Valuation advice outside the records evidence impact
Specific to this review
- The bundle is built per directive because fleet status lists often blur applicability and compliance evidence.
- Recurring ADs need next-due logic, not solely a historical completion record.
- AMOC evidence is treated as a controlling approval document and filed with the compliance record.
- The scope uses the Evidence Bundle Per Directive question as the control point, so the review stays tied to assembling AD compliance evidence and the buyer decision behind it.
- The evidence starts with AD applicability determination and follows Checklist Airworthiness Compliance Proves 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 One Assemble Complete Single questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Source-linked findings log for airworthiness directive compliance evidence checklist; it gives the next reviewer a precise map instead of another broad request for a better file.
- The source discipline is stricter on this page than on a general audit because the claim being tested is Assemble a complete compliance evidence bundle for a single airworthiness directive..
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.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
What makes this checklists review different from a general file audit?
The scope is tied to evidence bundle per directive and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block assembling ad compliance evidence or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad applicability determination, 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.
Adapt the checklist to your asset, event, and jurisdiction.