Registry change
Registry-change authorized release document transition review
This review confirms that the authorized release certificates behind an aircraft's components will satisfy the receiving authority in a registry change. A records specialist runs it before the acceptance package is submitted, from the party moving the asset. It works through FAA Form 8130-3 and EASA Form 1 releases, dual-release certificates, and the installation records that connect each release to the part it covers, then isolates the release questions the receiving registry will raise regardless of which authority it is. You receive a release-to-installation map, a gap list keyed to the receiving registry's acceptance questions, and a document request set for the certificates that are missing or need reissue.
When this review is needed
- An aircraft is changing registries and its component releases have to satisfy the receiving authority, whichever it is.
- The fleet carries a mix of FAA Form 8130-3 and EASA Form 1 releases that have to be reconciled for the receiving registry.
- Recent shop visits produced releases that need matching to the installed components before the acceptance submission.
- A component carries a single-authority release where the receiving registry may need a dual-release basis.
The problem
Registry changes span more than one direction, and a component release file built over years usually holds certificates from more than one authority. A release that closed a shop visit under one system does not always answer the question the receiving registry asks, which is whether the released condition rests on a basis it recognizes for the specific installed unit. Assembling that file late, once the registry change is moving, means matching each certificate to the part it covers from paperwork organized for operating convenience rather than for a receiving authority's review.
What gets reviewed
- FAA Form 8130-3 and EASA Form 1 releases matched to the installed components they cover
- Dual-release certificates checked against what the receiving registry requires
- Installation records reconciled to the release that authorized each fitment
- Releases from prior shop visits confirmed present and legible in the file
- Single-authority releases flagged where the receiving registry may need a dual basis
- The release file structured so the receiving authority can follow each part to its certificate
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 installed component traces to a release naming its part number and serial number
- Every release in the file was issued under an approval the receiving registry recognizes
- Dual-release certificates carry the privileges the receiving registry relies on
- The installation record and the release certificate agree on the unit actually fitted
- No installed component is left with a missing, illegible, or superseded release
Evidence normally required
- The component release file with FAA Form 8130-3 and EASA Form 1 certificates
- Installation and removal records for released components
- Shop-visit reports supporting the released condition
- The current component status list for the serial number
- Any receiving-registry correspondence naming release requirements
Common discrepancies
- An installed component whose release certificate is missing from the file
- A single-authority release where the receiving registry needs a dual-release basis
- A release naming a serial number that does not match the installation record
- An image-only release scan the receiving authority cannot cite
What is at stake
An installed component whose release cannot be traced to an acceptable basis becomes an open item, and the registry change stalls while the certificate is chased from the releasing organization or the part is dispositioned. If the release is unrecoverable and the receiving registry will not credit the component without it, the owner is left choosing between a costly swap and a conservative assumption the authority may reject, either of which delays the change.
How the work runs
Build the component list
Assemble the installed components that require a traceable release for the registry change.
Match releases to installations
Connect each 8130-3 or EASA Form 1 to the unit and installation record it covers.
Test against the receiving registry
Flag installations where a single-authority release will not satisfy the destination.
Chase the gaps
Request the missing or reissued certificates and structure the file for review.
What the buyer receives
- A release-to-installation map connecting each component to its covering certificate
- A gap list organized around the receiving registry's acceptance questions
- A document request set for the certificates to recover or reissue
Who uses the output
- Owners assembling the component evidence for the receiving registry's acceptance
- Records teams closing release gaps before the aircraft changes registry
- Asset managers weighing a component swap against recovering a lost certificate
How the work fits into the transaction or program
Release-document review runs alongside the AD, life-limited part, and modification work that a registry change touches, since all of them read the same component histories. Its release-to-installation map becomes the component evidence the receiving authority examines, and its gap list drives the certificate chase that has to finish before the registry change can complete.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
A registry change is not tied to a single authority pairing, so the receiving registry sets the recognition test and it can differ by destination. A release valid under the issuing authority still turns on whether the receiving registry recognizes the releasing organization's privileges for the installed unit, and whether a dual release is needed to bridge the two systems, which the review establishes per destination.
Regulatory limits
This review verifies and organizes existing release evidence for the receiving authority's examination. It does not issue or reissue any release certificate, grant release privileges, or determine that a released component is airworthy, which rest with the releasing organization and the receiving authority.
What this review does not cover
- Issuing or endorsing any authorized release certificate
- Re-releasing a component or performing the shop work behind a release
- Deciding which release requirements the receiving registry will impose
Specific to this review
- Because a registry change can run to more than one destination, the recognition test is set by the receiving registry rather than a fixed authority pairing, so the same file can pass for one destination and raise questions for another.
- A release file assembled from more than one authority is common, and the mix itself is where reconciliation effort concentrates.
- Whether a single-authority release suffices or a dual basis is needed turns on the receiving registry's recognition, not on the certificate's validity where it was issued.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
Frequently asked questions
Does the receiving registry decide which releases we need, and does that change by destination?
Yes. The receiving registry sets the recognition test, and it can differ by destination, so a release file that satisfies one authority may raise questions for another. The review establishes per destination whether each installed component's release is recognized or whether a dual-release basis is needed before the acceptance submission.
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.