Cross-authority AD status
Multi-jurisdiction fleet AD status transition records review
This review tests whether a fleet's AD compliance status will survive acceptance by more than one receiving authority at once. It is run by or for the party moving tails across FAA, EASA, and TCCA boundaries, before the records package is handed over. Each AD line is checked for applicability reasoning, accomplishment evidence, and the method-of-compliance basis the receiving system will demand, tail by tail. You get an evidence map keyed to the AD status list, a gap list ranked by acceptance risk, and a document request set aimed at the lines where authorities are likely to diverge.
When this review is needed
- A fleet is splitting to registers under different authorities and each one will judge the AD position on its own terms.
- A prior transfer stalled because a receiving authority rejected the method-of-compliance basis behind several directives.
- State-of-design and state-of-registry directives overlap on the same tails and the mapping has never been reconciled.
- The AD status list was built for one authority and now has to answer questions from two more.
The problem
An AD status list that reads clean to the outgoing authority can unravel when a second and third authority apply their own applicability and evidence rules to the same tails. A directive closed by a service bulletin one authority mandates and another treats as optional creates a line that looks compliant on one register and open on the next. Multiplied across a fleet, those divergences turn a single handover into three separate acceptance negotiations.
What gets reviewed
- Applicability of each directive reasoned against state-of-design and state-of-registry rules for every receiving authority
- Accomplishment evidence checked line by line against the AD status list rather than the summary total
- Method-of-compliance basis assessed for acceptance under each receiving system
- Directives closed by optional versus mandatory service bulletins flagged where authorities disagree
- Recurring-inspection AD next-due status reconciled to current utilization per tail
- Divergent acceptance risk mapped across the fleet so the worst tails are worked first
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
- Each closed AD line traces to accomplishment evidence a receiving authority would accept without a supplementary request
- Applicability calls hold under both the state-of-design and the state-of-registry framing for every destination
- Recurring-AD next-due values reconcile to the current time and cycle status on the same tail
- A directive superseded during the fleet's history shows the superseding action closed, with the original alone treated as insufficient
- The status list total agrees with the count of individually evidenced lines, with no orphaned entries
Evidence normally required
- The current AD status list for every tail in the transition
- Accomplishment records, work cards, and method-of-compliance references behind the closed lines
- The list of receiving authorities and the register each tail is destined for
- Service bulletin and modification records tied to AD closures
- Current time and cycle status supporting recurring-AD due calculations
Common discrepancies
- An AD closed against an optional service bulletin that a receiving authority mandates on its register
- A superseded directive shown compliant on the original action but silent on the superseding one
- Recurring-AD next-due dates that no longer match the tail's accumulated cycles
- A method-of-compliance basis accepted by the outgoing authority that a receiver will not recognize
What is at stake
If the divergences are not surfaced before handover, they land as questions from each receiving authority mid-acceptance, when leverage has already shifted to the party asking. Tails clear at different speeds, the delivery schedule slips against a lease or purchase date, and an AD taken on trust without accomplishment evidence can force a re-inspection that the receiver bills back.
How the work runs
Frame the destinations
Confirm which authority each tail is heading to and the applicability and evidence rules that authority applies to directives.
Evidence each line
Match every closed AD entry to its accomplishment record and method-of-compliance basis rather than the status total.
Reconcile divergence
Flag directives that read compliant on one register and open on another, and recalculate recurring due dates against current status.
Build the request set
List the documents needed to close divergent lines and rank the fleet by acceptance risk.
What the buyer receives
- A transition evidence map tying every AD line to its supporting document per authority
- A gap list ranked by which lines are most likely to draw a receiving-authority query
- A document request set targeting the evidence needed to close the divergent lines
Who uses the output
- Continuing-airworthiness leads answering each receiving authority with the same evidence base
- Asset managers tracking which tails will accept cleanly and which carry AD exposure
- Records teams assembling the closure documents each authority will ask for
How the work fits into the transaction or program
The review runs after the fleet-transition decision and before the records package is delivered, so divergent AD lines are found while the outgoing party still holds the evidence and the contacts to close them. Its gap list feeds the remediation and document-chasing that has to finish before each tail is accepted onto its new register.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
The same directive can carry different applicability and closure rules once a tail changes state of registry, and a service bulletin treated as optional under one authority may be mandated under another. The review reasons each AD line against every destination rather than assuming the outgoing authority's position transfers intact.
Regulatory limits
The review assembles and reconciles AD evidence so each receiving authority can make its own acceptance decision. It does not close a directive, determine airworthiness, or bind any authority to accept the status as presented.
What this review does not cover
- Performing or signing off the maintenance behind an open directive
- Issuing any airworthiness determination on a tail or a fleet
- Negotiating which AD basis a receiving authority will ultimately accept
Specific to this review
- The failure mode unique to cross-authority AD work is a line that is genuinely compliant on the outgoing register and genuinely open on the receiving one, because the mandating basis differs.
- Superseded directives are where fleets most often show a false-clean status, since the original action was recorded and the superseding action was never carried forward.
- Recurring-AD due dates drift silently between the status build and the transition, so they are recalculated against current utilization rather than trusted from the list.
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.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
Why can't we reuse the AD status list the outgoing authority already accepted?
Because each receiving authority applies its own applicability and mandating rules. A line the outgoing authority closed on an optional service bulletin can be open the moment the tail lands on a register where that bulletin is mandatory, and that is exactly the kind of divergence a single accepted list hides.
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.