Component releases at import
Authorized release certificates verified across the import and export package
Every component on an aircraft crossing registries is judged by the release document behind it, and the receiving side applies its own rules about which forms it accepts. This review works through the component release file in the import and export package, confirming that each installed item carries a certificate that is present, correctly completed, and acceptable in the receiving context. It is commissioned by transition or acquisition teams while authority submissions are being assembled. What it returns is a component-level exception list naming each item whose release is missing, defective, or unacceptable to the importing registry.
When this review is needed
- Components were installed during the current lease from stock certified for the current registry, and the destination registry applies different acceptance rules.
- The import inspection will sample recently installed items whose releases were filed by a stores system rather than into the records package.
- A certificate in the file shows a block completed ambiguously and its acceptability needs a judgment before an inspector makes one.
- Parts arrived through distributors and brokers whose paperwork chains have never been read end to end.
The problem
Release certificates fail quietly. The form is present, so the row looks complete, but block entries contradict each other, the release covers overhaul when the work performed was a repair, the certificate names a different part number dash level, or the issuing authority's form is one the receiving registry accepts only under conditions. Nobody reads certificates hard until an import inspector does, and by then the installation is years old and the supplier chain is cold.
What gets reviewed
- Installed components mapped from the package's fitment records to their release certificates
- Form completion reviewed block by block against the issuing system's completion rules
- Dual-release status established for parts that must satisfy both FAA and EASA contexts
- Work-scope consistency checked: the release's stated work matches the maintenance record that installed the part
- Supplier chain documents read where parts passed through distribution before installation
- Receiving-registry acceptability assessed for each certificate's issuing authority and form type
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
- Part number, serial number, and quantity on the certificate match the fitment record and the status data for the position
- The certifying statement and approval blocks are completed for the work actually performed, without contradictory entries
- Dual-release wording is present where the receiving context requires it, or a conforming alternative path is identified
- Certificate dates precede installation dates, and the sequence stays coherent through any distribution steps
- New-part releases trace to a production approval holder and used-part releases to an appropriately rated maintenance organization
Evidence normally required
- The component release file and the installation or fitment records that anchor it
- The package's component status data and recent removal and installation history
- Distribution paperwork for items sourced through the parts market
- The receiving registry's acceptance rules or bilateral guidance for release forms
Common discrepancies
- A certificate whose left-side and right-side blocks disagree about whether the release covers airworthiness or conformity only
- Used parts released by an organization not rated for the component class at the time of the work
- An installation supported by a packing slip and a photocopied certificate for a different serial number
- Single-authority releases on parts fitted shortly before the transition, exactly the population the import inspector samples
What is at stake
A component with an unacceptable release faces removal, re-certification, or replacement before the import completes, and each of those paths costs a hangar visit. Where several items share the same defective sourcing pattern, one finding multiplies across the installed fleet of parts. Certificates that fail also taint the stores process that filed them, inviting wider sampling.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Anchor to fitment
Build the component population from installation records, then pull each certificate.
Read each certificate
Check completion, work scope, identity, and date coherence block by block.
Judge the receiving context
Assess each form's acceptability under the destination registry's rules and bilateral terms.
Deliver cures
Issue the exception list, acceptability matrix, and a cure path per finding.
What the buyer receives
- A component-level exception list naming the defective or missing certificate for each affected position
- An acceptability matrix by issuing authority and form type for the receiving registry
- A cure recommendation per exception: recover, re-certify, or replace, with the realistic path noted
Who uses the output
- Transition leads sequencing cures before the import inspection
- Stores and records teams correcting the filing patterns the findings expose
- The receiving CAMO and its quality function accepting components onto the new registry
How the work fits into the transaction or program
The release-document review reads the same shop and fitment records the LLP and AD reviews use, but asks a different question: whether each installation event is covered by a certificate the destination registry will honor. Its exceptions feed the pre-import workscope, since certificate cures often need the same downtime as the physical import survey.
Jurisdiction-specific considerations
FAA Form 8130-3 and EASA Form 1 are near-parallel instruments, and bilateral arrangements govern when each side accepts the other's, with dual-release completion bridging most cases; on the FAA side, completion is governed by FAA Order 8130.21. Releases from third-country authorities, and older forms issued before current bilateral terms, are where acceptability turns case-specific, so the review treats those populations explicitly.
Regulatory limits
The review does not issue or amend release certificates, does not approve parts for installation, and does not decide acceptability on behalf of any authority or operator. It reports each certificate's condition and the acceptance question it raises, for the responsible organizations to resolve.
What this review does not cover
- Physical inspection of installed components or verification of data plates in situ
- Procurement of replacement parts or certificates
- Suspected-unapproved-parts investigation, beyond flagging the indicators that warrant one
Specific to this review
- The population at highest risk is parts installed in the final months before transition: sourced fast, filed by stores, and never reviewed against the destination registry's rules.
- A dual release is a completion choice made at certification time; it cannot be added retroactively, so a single-authority release on a part crossing systems needs a cure path, never an edit.
- Distribution steps do not generate release certificates of their own, which is why an unbroken certificate-to-installation chain matters more than the thickness of the broker paperwork around it.
- Import inspectors sample recent installations first because acceptance-rule mismatches concentrate there; ordering the review the same way front-loads the findings that matter.
- Certificate defects repeat by supplier: one bad completion habit shows up across every part bought from the same source, so findings cluster and cures can be batched.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
Most of our certificates are single-authority releases. Does the import fail?
Not necessarily. Acceptability depends on the bilateral arrangements between the issuing and receiving systems, the part's class, and when and where the work was done. Many single-authority releases are acceptable as they stand. The review separates the certificates that are fine from the ones that genuinely need re-certification or replacement, so cure effort lands only where it is required.
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.