Cross-authority repair data
Multi-jurisdiction fleet repair and alteration approval transition review
This review examines whether the approval data behind a fleet's repairs and alterations will satisfy more than one receiving authority. It is run for the party transferring tails across FAA, EASA, and TCCA registers, before the package changes hands. Each repair is traced from its damage report through the disposition, the approved-data basis, and the return-to-service entry the receiver will scrutinize. You receive an evidence map keyed to the repair map, a gap list of repairs whose approval basis is weak under a destination, and a request set for the substantiation each receiving authority will demand.
When this review is needed
- Structural repairs were approved under one authority's data and now face acceptance under others.
- Alterations recorded on the fleet reference an approval basis a receiving system may not recognize.
- A repair map assembled for a single sale now has to answer parallel receiving-authority questions.
- Damage dispositions were signed off years ago and the approval trail behind them has never been re-checked.
The problem
A repair is only as transferable as the approval data behind it, and approval bases do not translate one for one across authorities. A structural repair carried out to an approved repair manual method one authority accepts may need a supplemental type certificate or a specific approval another authority will insist on, and an alteration recorded without a traceable data reference reads as a defect on the receiving register. On a fleet, each tail carries its own repair history, so the divergences do not repeat cleanly.
What gets reviewed
- Damage reports matched to the repair disposition and the approved-data basis used
- Structural repairs assessed for whether their approval basis is recognized by each receiving authority
- Alterations checked for a traceable approved or acceptable data reference per destination
- Return-to-service entries confirmed to follow from the approval and the work performed
- Repairs relying on a supplemental type certificate reconciled to the STC status carried on the tail
- Repairs and alterations whose basis is weak under any receiver mapped to the tail and the missing reference
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 repair on the map ties to a damage report, a disposition, and the approval data it was carried out under
- The approval basis for every structural repair is one the receiving authority recognizes
- Alterations carry a traceable data reference rather than a description alone
- The return-to-service entry corresponds to the approved method and the recorded work
- A repair based on an STC reconciles with the STC status shown elsewhere in the records
Evidence normally required
- The repair and alteration records and the repair map for every tail
- Damage reports, dispositions, and the approved data referenced by each repair
- STC files where a repair or alteration relies on one
- The receiving register and approval-basis expectation for each destination
- Return-to-service entries associated with the repairs
Common discrepancies
- A structural repair approved on a basis the outgoing authority accepted but a receiver will not
- An alteration recorded without a traceable approved-data reference
- A repair that relies on an STC whose status the records elsewhere do not confirm
- A return-to-service entry that does not correspond to the approval basis on file
What is at stake
A repair whose approval basis a receiver will not accept can force a re-substantiation, a re-inspection, or in the worst case removal and rework, all charged against the transition. An alteration with no traceable data can stall a tail's acceptance until the basis is reconstructed from records that may no longer exist. Left unfound, these surface during acceptance, when the receiving authority is asking and the deadline is fixed.
How the work runs
Map the destinations
Confirm which authority each tail moves to and what repair and alteration data basis that authority accepts.
Trace each repair
Follow every repair from damage report through disposition and approval to the return-to-service entry.
Test the basis
Assess whether each approval basis is recognized by the receiving authority and reconcile STC-based repairs to the modification status.
Flag and request
List repairs and alterations that are weak under any receiver and request the substantiation that closes them.
What the buyer receives
- A transition evidence map linking each repair to its approval basis per authority
- A gap list of repairs and alterations whose basis is weak under a receiving system
- A document request set for the substantiation each destination will require
Who uses the output
- Engineering deciding how to treat a repair whose approval basis a receiver rejects
- Asset managers pricing the rework exposure on repairs that may not transfer
- Records teams assembling the substantiation each receiving authority asks for
How the work fits into the transaction or program
The review runs before handover so repairs with a fragile approval basis are found while the original data and the people who dispositioned them are still reachable. Its gap list drives the substantiation work and, where needed, the engineering decision on repairs a receiving authority will not accept as recorded.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
Authorities differ on what constitutes acceptable repair and alteration data, so an approved repair manual method or a national approval that closed a repair on one register may need a different basis, or a supplemental type certificate, to be accepted on another. The review evaluates each repair's basis against every destination rather than assuming approval transfers with the tail.
Regulatory limits
The review assembles and grades repair-approval evidence so each receiving authority can decide acceptance. It does not approve a repair, develop repair data, or make an airworthiness determination on any alteration.
What this review does not cover
- Developing or approving new repair or alteration data
- Re-performing or re-inspecting the physical repair
- Any airworthiness determination on a repaired structure
Specific to this review
- The transferability problem is specific to repairs: a physically sound repair can be unacceptable to a receiver purely because the approval basis it was carried out under is not recognized on that register.
- Alterations fail acceptance most often for a missing data reference, not for the change itself, because the description survives in the records while the approved-data pointer does not.
- A repair that leans on an STC inherits the STC's transition risk, so its acceptance depends on the modification status reconciling elsewhere in the package.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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
The repairs were signed off years ago. Why revisit the approval basis now?
Because the acceptance test changes at the border. A repair the current authority accepted may rest on a basis a receiving authority does not recognize, and the time to confirm or re-substantiate it is before handover, while the original data and the engineers who dispositioned it can still be found.
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.