AD compliance
Cross-authority AD and STC mapping for operators
This page is for operators, lessors, CAMOs when Registry transfer or mixed-registry fleet AD divergence puts cross-authority ad and stc mapping on the critical path. EE checks parallel AD texts, registry obligation map, STC or AMOC recognition note against the approval basis, configuration baseline, effectivity, revision status, and source records named in the brief. The buyer receives a discrepancy register, evidence map, and closure request list for the next review gate. The work tests records and certification-data traceability only; it does not replace authority, delegate, approval-holder, or authorized-person decisions.
When this review is needed
- Use this review when Registry transfer or mixed-registry fleet AD divergence starts driving schedule or commercial exposure.
- A CAMO or transition engineer searches for FAA versus EASA AD differences and mutual recognition of compliance after a registry transfer or fleet merger exposes a mismatch.
- The highest-risk breakpoint is: an FAA AMOC the EASA registry does not honor, complying with the state-of-design AD while missing the registry's own, and a transition stalling on divergent terminating actions.
The problem
The decision is which mod, STC, or AMOC satisfies both the FAA and EASA (or TCCA) ADs addressing the same unsafe condition, for mixed-registry fleets or aircraft in transition. The file set covers the parallel AD texts and their differences in applicability, method, and deadlines; the state-of-design versus state-of-registry AD obligations; and whether each authority recognizes the installed STC or AMOC. Known breakpoints include an FAA AMOC the EASA registry does not honor, complying with the state-of-design AD while missing the registry's own, and a transition stalling on divergent terminating actions.
What gets reviewed
- Review the buyer decision in the brief: Get help mapping divergent FAA/EASA AD requirements onto one STC or mod strategy for a mixed-registry fleet.
- Trace parallel AD texts to source date, revision, owner, and current configuration.
- Match effectivity for registry obligation map to the serial range, article version, aircraft, or fleet in scope.
- The decision is which mod, STC, or AMOC satisfies both the FAA and EASA (or TCCA) ADs addressing the same unsafe condition, for mixed-registry fleets or aircraft in.
What gets validated
- Record custody: parallel AD texts is checked for source, date, revision, and relationship to the current program.
- Coverage boundary: registry obligation map must state where the evidence stops applying.
- Baseline comparison: installation, test, drawing, and compliance references are sampled for mismatched revisions.
- Disposition rule: unsupported assumptions are separated from acceptable limitations.
Evidence normally required
Common discrepancies
- The file set covers the parallel AD texts and their differences in applicability, method, and deadlines; the state-of-design versus state-of-registry AD obligations; and.
- Known breakpoints include an FAA AMOC the EASA registry does not honor, complying with the state-of-design AD while missing the registry's own, and a transition stalling on.
- Revision mismatch leaves STC or AMOC recognition note separated from the certificate, matrix, instruction, or delivered baseline.
- Storage completeness is higher than decision readiness because the file lacks a clear disposition for this buying stage.
What is at stake
Specific exposure for this page: an FAA AMOC the EASA registry does not honor, complying with the state-of-design AD while missing the registry's own, and a transition stalling on divergent terminating actions.
Move from findings to resolution
Identify the missing data behind the finding.
How the work runs
Frame Cross Authority
Confirm the exact event, affected file set, buyer role, and decision standard before any parallel ad texts is treated as sufficient.
Trace Compliance Mapping
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 FAA EASA
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Diverge Mod
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
How the work fits into the transaction or program
The decision is which mod, STC, or AMOC satisfies both the FAA and EASA (or TCCA) ADs addressing the same unsafe condition, for mixed-registry fleets or aircraft in transition. The evidence set centers on the parallel AD texts and their differences in applicability, method, and deadlines; the state-of-design versus state-of-registry AD obligations; and whether each authority recognizes the installed STC or AMOC. The likely weak points are an FAA AMOC the EASA registry does not honor, complying with the state-of-design AD while missing the registry's own, and a transition stalling on divergent terminating actions. The output gives the CAMO manager a cleanup register for Cross-authority AD and STC mapping for operators before registry transfer or mixed-registry fleet AD divergence.
Start with a single asset
Confirm each requirement maps to substantiating evidence.
Regulatory limits
For cross-authority ad and stc mapping, EE reviews parallel AD texts, registry obligation map, STC or AMOC recognition note for completeness, consistency, and traceability. The work does not issue approvals, approve data, grant relief, validate STCs, accept release certificates, or make airworthiness determinations. Final decisions remain with the responsible authority, delegate, approval holder, operator, or authorized person.
Specific to this review
- The decision is which mod, STC, or AMOC satisfies both the FAA and EASA (or TCCA) ADs addressing the same unsafe condition, for mixed-registry fleets or.
- The file set covers the parallel AD texts and their differences in applicability, method, and deadlines; the state-of-design versus state-of-registry AD.
- Known breakpoints include an FAA AMOC the EASA registry does not honor, complying with the state-of-design AD while missing the registry's own, and a transition.
- The scope uses the Cross Authority STC Compliance question as the control point, so the review stays tied to Registry transfer or mixed-registry fleet AD divergence and the buyer decision behind it.
- The evidence starts with parallel AD texts and follows Mapping Operators FAA EASA 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 CAMO 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 Ads Diverge Mod Satisfies questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Cross-authority AD and STC mapping discrepancy register; 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 Get help mapping divergent FAA/EASA AD requirements onto one STC or mod strategy for a mixed-registry fleet..
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
Frequently asked questions
What makes this workflows review different from a general file audit?
The scope is tied to cross authority stc compliance and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block registry transfer or mixed-registry fleet ad divergence or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is parallel ad texts, 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 camo 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.