Alternative compliance
AMOC approval source evidence review
The decision turns on where compliance used an Alternative Method of Compliance, the AD closure is only as good as the AMOC paper behind it; for every AMOC-based closure, verify the approval letter exists, was issued by the office with AMOC authority for that AD, covers this serial number and configuration, matches the method actually performed, and remains valid under the current superseding AD; AMOC approval letters, global AMOC applicability statements, the work records referencing the AMOC number; Failure. Read AMOC approval letters, global AMOC applicability statements, the work records referencing the AMOC number first. Resolve global AMOCs applied to serials outside their scope, AMOCs invalidated by a supersedure that was never re-checked, and work performed to a repair drawing while the AMOC letter cites a different method.
When this review is needed
- The file is being prepared for redelivery or authority audit with AMOC-based closures.
- The first evidence to test is AMOC approval letters.
- The open question is where compliance used an Alternative Method of Compliance, the AD closure is only as good as the AMOC paper behind it; for every AMOC-based closure, verify the approval letter exists, was issued by the office with AMOC authority for that AD, covers this serial number and configuration, matches the method actually performed, and remains valid under the current superseding AD; AMOC approval letters, global AMOC applicability statements, the work records referencing the AMOC number; Failure.
The problem
The difficult point is global AMOCs applied to serials outside their scope, AMOCs invalidated by a supersedure that was never re-checked, and work performed to a repair drawing while the AMOC letter cites a different method.
What gets reviewed
- Map the current configuration before accepting the status answer.
- Link superseded entries, prior inspections, replacements, and open corrective actions.
- Check aMOC approval letters, global AMOC applicability statements, work records referencing the AMOC number against the active requirement.
- Identify status lines that need a revised basis rather than another copy of the same record.
- Document why each N/A, closed, or next-due position is defensible.
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 old and current requirements are bridged without losing applicability.
- Fail when a stopped repetitive task lacks the modification or replacement record that allowed it to stop.
- Check replacement parts for serial continuity and release evidence.
- Reject any closure that cites an obsolete requirement without explaining the current one.
Evidence normally required
- aMOC approval letters
- global AMOC applicability statements
- work records referencing the AMOC number
- status list
- maintenance entry
Common discrepancies
- global AMOCs applied to serials outside their scope.
- AMOCs invalidated by a supersedure that was never re-checked.
- work performed to a repair drawing while the AMOC letter cites a different method.
- source support for amoc approval stops at a summary entry.
What is at stake
If unresolved, global AMOCs applied to serials outside their scope, AMOCs invalidated by a supersedure that was never re-checked, and work performed to a repair drawing while the AMOC letter cites a different method changes the redelivery or authority audit with AMOC-based closures position for AMOC approval source.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Frame Amoc Approval
Confirm the exact event, affected file set, buyer role, and decision standard before any amoc approval status entry is treated as sufficient.
Trace Review Source
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 Alternative Compliance
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Every Method
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
- Decision register for AMOC approval source, split into supported, disputed, and missing evidence.
- Source map for AMOC approval letters tied to the controlling status records.
- Owner action list for document retrieval, data correction, technical disposition, or acceptance decision.
- Briefing note tying the open items to redelivery or authority audit with AMOC-based closures.
Who uses the output
- Technical records manager uses the output to decide what can be accepted and what needs escalation.
- CAMO manager uses it to update status, request missing records, or brief the counterparty.
- Asset manager uses it to close administrative items without losing technical reservations.
How the work fits into the transaction or program
Where compliance used an Alternative Method of Compliance, the AD closure is only as good as the AMOC paper behind it; for every AMOC-based closure, verify the approval letter exists, was issued by the office with AMOC authority for that AD, covers this serial number and configuration, matches the method actually performed, and remains valid under the current superseding AD; AMOC approval letters, global AMOC applicability statements, the work records referencing the AMOC number; Failure. The evidence set centers on AMOC approval letters, global AMOC applicability statements, the work records referencing the AMOC number. The likely weak points are global AMOCs applied to serials outside their scope, AMOCs invalidated by a supersedure that was never re-checked, and work performed to a repair drawing while the AMOC letter cites a different method. Handoff: technical records manager, redelivery or authority audit with AMOC-based closures, AMOC approval source.
Aircraft-specific considerations
For AMOC approval source, the records depend on where compliance used an Alternative Method of Compliance, the AD closure is only as good as the AMOC paper behind it; for every AMOC-based closure, verify the approval letter exists, was issued by the office with AMOC authority for that AD, covers this serial number and configuration, matches the method actually performed, and remains valid under the current superseding AD; AMOC approval letters, global AMOC applicability statements, the work records referencing the AMOC number; Failure.
Jurisdiction-specific considerations
For AMOC approval source, FAA/EASA review starts with AMOC approval letters; the trigger is redelivery or authority audit with AMOC-based closures.
Regulatory limits
The review stops at AMOC approval letters; release decisions stay with the authorized parties.
What this review does not cover
- Engineering redesign or new approval data
- Release to service or conformity sign-off
- Maintenance program approval changes
Specific to this review
- Supersedure errors often survive because the old AD line still looks closed.
- Configuration proof must travel with the affected asset, not solely with the operator's fleet file.
- A bridge table is usually clearer than a long narrative when several AD numbers or revisions are involved.
- The scope uses the Amoc Approval Records Review question as the control point, so the review stays tied to Redelivery or authority audit with AMOC-based closures and the buyer decision behind it.
- The evidence starts with AMOC approval status entry and follows Source Evidence Alternative Compliance 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 Proving Every Method Was questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Configuration evidence matrix for amoc approval; 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 Scope a review of AMOC approvals supporting AD closures across an aircraft or fleet..
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.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Frequently asked questions
What makes this records review different from a general file audit?
The scope is tied to amoc approval records review and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block redelivery or authority audit with amoc-based closures or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is amoc approval status entry, 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.