AD method gap
AD closure repair when recorded method differs
MROs, operators, Aircraft records teams use this review after Method discrepancy found during records review turns a records question into an acceptance, pricing, or program decision. The work compares AD-required action paragraph, accomplishment task cards, inspection technique records with the current claim and any supplied acceptance criteria. Discrepancies are logged where support is missing, dates or serials conflict, applicability is uncertain, or a source document does not prove the asserted status. The package gives the team AD method comparison matrix, AMOC search and applicability log, corrective path recommendation for follow-up and decision making.
When this review is needed
- A records decision is needed before acceptance, closing, release planning, or the next review gate.
- The current file contains summaries that have to be tested against source records.
- Outside evidence from a prior custodian, shop, lessee, or authority may be needed.
- The team needs a ranked list of blockers, curable gaps, and residual limits.
The problem
The difficult part is deciding what the records actually prove before the deadline or transaction pressure takes over. The task card shows a different inspection technique from the AD paragraph. Parts installed satisfy a later instruction but the AD status lacks credit basis.
What gets reviewed
- Compare the recorded work step by step against the AD-required method.
- Identify whether the difference is substantive, clerical, or covered by existing approval.
- Search for AMOC correspondence before selecting a corrective path.
- Assess whether re-accomplishment, engineering substantiation, or retrospective request is the practical route.
- Document the exposure period and status correction 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
- Pass when the accomplishment evidence matches the AD method or an approved alternative.
- Fail when a later service bulletin revision is used without credit language.
- Pass when method differences are classified with evidence and technical review.
- Fail when MRO standard practice silently replaces an AD-specific step.
Evidence normally required
- AD-required action paragraph
- accomplishment task cards
- inspection technique records
- parts installation evidence
- AMOC or correspondence search results
Common discrepancies
- The task card shows a different inspection technique from the AD paragraph.
- Parts installed satisfy a later instruction but the AD status lacks credit basis.
- No AMOC letter exists even though the status line says alternative method.
- The discrepancy was repeated across multiple aircraft because the template task card was wrong.
What is at stake
Open items can become delivery delay, disputed value, or rework when the next reviewer asks for source evidence. The review turns the issue into named documents, responsible owners, and a closure path so the team is not negotiating from uncertainty.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Frame Method Mismatch
Confirm the exact event, affected file set, buyer role, and decision standard before any ad text is treated as sufficient.
Trace Closure Repair
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 Differs Gap
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Wrong Assessing
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 method comparison matrix
- AMOC search and applicability log
- corrective path recommendation
- status correction support file
Who uses the output
- Quality manager uses the findings to decide which gaps block the next milestone.
- Technical records manager uses the evidence map to request, correct, or reserve records items.
- Structures engineer uses the summary to brief stakeholders without reopening the full file.
How the work fits into the transaction or program
This work is usually performed before a larger transaction or program milestone. Its output supports the handoff between records specialists, technical managers, and the people deciding whether to cure, reserve, disclose, or proceed. The page-specific framing is A closure entry that describes work different from what the AD paragraph requires is not compliance, it is a deviation without approval. Problem definition: compare the recorded method (task card, NDT technique, parts installed) against the AD's required action; where they differ, determine whether an AMOC existed, whether the difference is substantive, and what corrective path applies: retrospective AMOC, re-accomplishment, or engineering substantiation. The evidence set is accomplishment records at work-step level,. For method mismatch amoc closure, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The ad method mismatch without amoc scope is intentionally narrow: Resolve AD closures whose recorded method does not match the AD requirement.. The Method Mismatch Amoc evidence question is tested against ad text and not against a generic checklist copied from another page. The Closure Repair Recorded trigger is method discrepancy found during records review, so the review ranks gaps by decision impact instead of document volume. The Differs Gap Done searcher pattern is A quality or records lead searches for options after discovering AD work done to a different method than required.. The Wrong Assessing Repairing evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Paragraph Deviation Cure exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Closure Trace Baseline handoff is written for quality manager, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on ad method comparison matrix, which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is A closure entry that describes work different from what the AD paragraph requires is not compliance, it is a deviation without approval. Problem definition: compare the recorded method (task card, NDT technique, parts installed) against the AD's required action; where they differ, determine whether an AMOC existed, whether the difference is substantive, and what corrective path applies: retrospective AMOC, re-accomplishment, or engineering substantiation. The evidence set includes accomplishment records at work-step level, the AD text, any AMOC correspondence. The failure pattern includes eddy current performed where the AD requires ultrasonic, later SB revisions used without credit language, and MRO-standard practices silently substituted for AD-specific steps. The ad method mismatch without amoc method mismatch without lane records how repair recorded differs affects wrong assessing repairing, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc without amoc closure lane records how differs gap done affects repairing paragraph deviation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc closure repair recorded lane records how done wrong assessing affects deviation cure entry, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc recorded differs gap lane records how assessing repairing paragraph affects entry describes work, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc gap done wrong lane records how paragraph deviation cure affects work different requires, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc wrong assessing repairing lane records how cure entry describes affects requires not compliance, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc repairing paragraph deviation lane records how describes work different affects compliance approval problem, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc deviation cure entry lane records how different requires not affects problem definition compare, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc entry describes work lane records how not compliance approval affects compare task card, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc work different requires lane records how approval problem definition affects card ndt, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc requires not compliance lane records how definition compare task affects method mismatch without, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc compliance approval problem lane records how task card ndt affects without amoc closure, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc problem definition compare lane records how ndt affects closure repair recorded, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc compare task card lane records how mismatch without amoc affects recorded differs gap, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc card ndt lane records how amoc closure repair affects gap done wrong, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc method mismatch without lane records how repair recorded differs affects wrong assessing repairing, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc without amoc closure lane records how differs gap done affects repairing paragraph deviation, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ad method mismatch without amoc closure repair recorded lane records how done wrong assessing affects deviation cure entry, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Resolve AD closures whose recorded method does not match the AD requirement.. The operating angle for this page is A closure entry that describes work different from what the AD paragraph requires is not compliance, it is a deviation without approval. Problem definition: compare the recorded method (task card, NDT technique, parts installed) against the AD's required action; where they differ, determine whether an AMOC existed, whether the difference is substantive, and what corrective path applies: retrospective AMOC, re-accomplishment, or engineering substantiation. Evidence set: accomplishment records at work-step level, the AD text, any AMOC correspondence. Failure modes: eddy current performed where the AD requires ultrasonic, later SB revisions used without credit language, and MRO-standard practices silently substituted for AD-specific.
Jurisdiction-specific considerations
FAA 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 review is an evidence and records assessment. It does not approve data, release aircraft or parts, determine airworthiness, or bind any regulator, authorized person, owner, lessor, operator, applicant, or counterparty.
What this review does not cover
- new AMOC approval
- performing inspection rework
- authority enforcement response
Specific to this review
- AD compliance depends on the method required or approved, not on a general statement that work was done.
- Small wording differences can matter when they change inspection technique or acceptance criteria.
- A method mismatch needs technical review before the status list is corrected.
- The cure route depends on whether the difference can be approved, evidenced, or must be reworked.
- The scope uses the Method Mismatch Amoc Closure question as the control point, so the review stays tied to Method discrepancy found during records review and the buyer decision behind it.
- The evidence starts with AD text and follows Repair Recorded Differs Gap 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 Quality 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 Done Wrong Assessing Repairing 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 method comparison matrix; 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). 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.
Frequently asked questions
What makes this problems review different from a general file audit?
The scope is tied to method mismatch amoc closure and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block method discrepancy found during records 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 text, 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 quality 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.