Operator certificate transfer
Release-document records for an operator AOC transfer
This review checks that the authorized release certificates behind installed components will carry an aircraft onto a new operator's certificate. It is done ahead of the transfer, on behalf of the party handing the aircraft over, so the release file is settled before the receiving operator opens it. The work reads FAA Form 8130-3 and EASA Form 1 releases, dual-release entries, and the installation records that tie each certificate to a fitted part. You get an evidence map of the component release file, a gap list, and a document request set built around the release questions that most often break a bridging discussion.
When this review is needed
- An aircraft is moving from one operator's certificate to another and the receiving side will re-examine every installed release.
- The two operators sit under different authorities and the release forms in the file mix FAA and EASA origins.
- A component was fitted under a dual release and only one side of the certificate is on file.
- The receiving operator has set a records standard for acceptance that the release file has not yet been tested against.
The problem
Release certificates accumulate over an aircraft's life in whatever form each shop issued them, and no one reconciles them until the aircraft changes hands. At an operator transfer the receiving side reads that file cold, questioning any release it cannot tie to a fitted part or a recognized origin. What passed daily operation without comment becomes a line of objections once a new certificate holder has to stand behind it.
What gets reviewed
- Each installed component matched to a release certificate for the fitted part and serial number
- FAA Form 8130-3 and EASA Form 1 releases checked for validity and correct issuing origin
- Dual-release entries confirmed to carry both sides where the receiving operator relies on them
- Installation records tying each release to the removal and fitment history
- Releases whose form or origin the receiving authority may question flagged for explanation
- The component release file assembled in the order the receiving side will review it
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
- Every installed component with a life or approval basis has a release certificate on file
- Part and serial numbers on each release agree with the installation record for the fitted position
- Dual releases show both authority signatures where the receiving operator needs them
- Each release traces to an approved source rather than a photocopy with no verifiable origin
- The file has no release that points to a part number no longer installed
Evidence normally required
- The component release file or release-certificate index for the aircraft
- Installation records and the removal and fitment history for tracked components
- The receiving operator's records standard for release acceptance, where one exists
- Logbook entries that reference component changes without a filed release
- Contact points at the shops and operators that issued the original certificates
Common discrepancies
- A component fitted with a release whose part number does not match the installed part
- A dual release present on file with only one authority's side completed
- A release accepted in daily operation that has no verifiable issuing origin
- A recent component change entered in the logbook with no release certificate filed
What is at stake
A release the receiving operator will not accept keeps the associated component in question, and a component in question keeps the aircraft off the new certificate. The bridging discussion then runs on the file's weakest releases rather than its strongest, and each disputed certificate either gets reconstructed at cost or the part comes off. Left to the transfer week, that work happens with no schedule margin.
How the work runs
Index the release file
List every installed component that needs a release and pull the certificate on file for each.
Match releases to fitted parts
Confirm part and serial numbers and origin against the installation and fitment records.
Flag the cross-authority cases
Mark releases and dual-release entries the receiving side may question and prepare each explanation.
Deliver map, gaps, and requests
Hand over the evidence map, the ranked gap list, and requests to the issuers who can confirm or reissue.
What the buyer receives
- An evidence map linking each installed component to its release certificate and origin
- A gap list ranking missing or weak releases by their weight in the bridging discussion
- A document request set aimed at the shops and operators that can reissue or confirm releases
Who uses the output
- Asset managers weighing whether the release file is ready to hand over
- Receiving-operator continuing-airworthiness staff reviewing releases for acceptance
- Records leads assembling the release file to the receiving standard before transfer week
How the work fits into the transaction or program
This review runs in the window between agreeing the transfer and the receiving operator's acceptance. It turns a life's worth of loose release paper into a file the receiving side can read in order, and it feeds the bridging discussion by settling the releases before they can become bargaining points.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
When the two operators sit under FAA and EASA rules, a release valid at issue may still be unfamiliar to the receiving side, and a dual release may be relied on for exactly that reason. The review marks which releases cross the authority line cleanly and which need an explanation prepared, so the receiving operator is not left to interpret them alone.
Regulatory limits
The review reports what the release file supports for the transfer. It does not make an airworthiness determination on any component, issue or endorse a release certificate, and does not replace the receiving operator's acceptance of the aircraft onto its certificate.
What this review does not cover
- Issuing or reissuing any authorized release certificate
- Airworthiness assessment of the components themselves
- Negotiating the records standard set in the transfer agreement
Specific to this review
- A release that carried an aircraft through years of operation can still fail acceptance the moment a new certificate holder has to stand behind it.
- Dual-release entries fail most often because only one authority's side was ever completed, which stays invisible until the receiving side needs the other.
- The bridging discussion is decided by the weakest releases in the file, so finding and fixing those first is where the leverage sits.
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
The releases were fine while we operated the aircraft. Why re-check them now?
Acceptance is done by the party taking the aircraft onto its certificate, not by the record of prior operation. The receiving operator reads the release file to its own standard, so releases that were never questioned in service still have to be provable at the transfer.
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.