Import acceptance
Authorized release document review for import acceptance
An import acceptance release document review confirms that the authorized release paperwork behind the aircraft's components will satisfy the importing authority as the aircraft enters its register. It is run for the team preparing the import, before the acceptance review, across the FAA Form 8130-3, EASA Form 1, and dual-release certificates the installed parts depend on. The work matches each release to the part and installation it supports and identifies certificates the importing authority will not accept on their face. You receive a release evidence view keyed to the component release file, a gap list flagging unaccepted or missing certificates, and a request set for the release paperwork still needed.
When this review is needed
- An aircraft is being imported and the importing authority will examine the release paperwork behind installed components.
- Parts were released on a form the importing authority does not accept without a dual release.
- The component release file was assembled under a different authority and has never been tested for import.
- An acceptance review is scheduled and the team needs to know which certificates will not be accepted as-is.
The problem
A release certificate that satisfied one authority is not always accepted by another, and the difference is exactly what an import acceptance review turns on. A part released on a single-authority form may need a dual release to be accepted on the importing register, and a certificate that reads valid can still fail if it does not tie to the installation it supports. The team preparing the import inherits a component release file that looks complete and has to prove each certificate will hold on the new side.
What gets reviewed
- Each installed component matched to the release certificate that supports it
- The FAA Form 8130-3 and EASA Form 1 certificates checked for the fields and dual-release status the importing authority requires
- Dual-release coverage confirmed for parts crossing between authorities
- Release certificates tied to the installation and removal records for each position
- Certificates the importing authority will not accept on their face identified with the reason
- The component release file assembled into a single view for the acceptance review
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 has a release certificate that ties to its part number and installation record
- Each FAA Form 8130-3 and EASA Form 1 carries the fields and signatures the importing authority requires
- Parts crossing authorities carry a dual release where the importing register expects one
- No release certificate supports a position other than the one it is filed against
- Certificates that will not be accepted as-is are flagged with the acceptance issue
Evidence normally required
- The component release file with the FAA Form 8130-3 and EASA Form 1 certificates
- Installation and removal records for the released components
- The importing authority's acceptance requirements for release paperwork
- Dual-release documentation where parts crossed between authorities
- Configuration status showing which components the release file must cover
Common discrepancies
- A part released on a single-authority form where the importing register expects a dual release
- A release certificate that does not tie to the installation record for its position
- An 8130-3 or Form 1 missing a field the importing authority requires for acceptance
- An installed component with no release certificate in the file at all
What is at stake
A release the importing authority rejects can require the component to be re-released, replaced, or held pending an acceptable certificate, any of which stalls import acceptance. A certificate that does not tie to its installation leaves the component's status unproven at exactly the point the importing authority is deciding whether to accept the aircraft.
How the work runs
Match releases to installations
Tie every installed component to the release certificate that supports its position.
Check the forms
Confirm each 8130-3 and Form 1 carries the fields and dual-release status the importing authority requires.
Test acceptance
Identify certificates the importing register will not accept on their face and the reason for each.
Recover the gaps
Request the missing certificates and dual releases the acceptance review will depend on.
What the buyer receives
- A release evidence view mapping each installed component to its accepting certificate
- A gap list flagging certificates that will not be accepted as-is and components with none
- A document request set for the release paperwork and dual releases still to be recovered
Who uses the output
- Continuing-airworthiness leads presenting the component release file to the importing authority
- Asset managers tracking which components could hold import acceptance for release reasons
- Records teams recovering the release certificates and dual releases the file is missing
How the work fits into the transaction or program
The release document review sits early in the import acceptance sequence, because the certificates it checks underpin the AD, LLP, and configuration positions the importing authority reviews next. Its gap list drives the recovery of missing or non-accepting releases before the acceptance review tests the components that depend on them.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
Parts are released on different forms by FAA and EASA, and TCCA sets its own acceptance basis, so a certificate accepted on one register can require a dual release for another. The review works to the specific importing authority and flags where a single-authority release will not be accepted.
Regulatory limits
The review checks the release paperwork and its acceptance against the importing authority's requirements. It does not issue or re-issue a release certificate, grant import acceptance, install or replace a component, or determine that a part is airworthy.
What this review does not cover
- Issuing or re-issuing any release certificate
- Installing, removing, or re-releasing a component
- Any airworthiness determination on the released parts
Specific to this review
- A release valid on the exporting register is not automatically accepted on the importing one, so dual-release coverage is checked part by part.
- A certificate can read valid and still fail acceptance if it does not tie to the installation record for the position it is filed against.
- Release recovery has a long tail, because the shop that issued the original certificate holds the retained copy, and that is the first thing to chase.
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
Will release certificates from the exporting register be accepted on import?
Not always. FAA and EASA release parts on different forms, and a part released on a single-authority certificate can require a dual release to be accepted on the importing register. The review checks each certificate against the importing authority's basis and flags the ones that need a dual release or recovery before acceptance.
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.