MRO induction
Authorized release certificate review when an MRO inducts an aircraft
When an MRO inducts an aircraft, the release certificates behind its installed components decide how much of the existing configuration the shop can rely on. This review verifies FAA Form 8130-3 and EASA Form 1 coverage across the component release file, matching each certificate to the part, serial number, and installation entry it is supposed to support. It runs at induction, before workscope decisions lock in. The quality team receives a verified release-document index, a list of unsupported installations, and targeted requests to the operator or prior shops.
When this review is needed
- A new customer aircraft arrives with a component file the shop has never seen and a check start date already fixed.
- The workscope depends on retaining installed components whose release documents are unconfirmed.
- Dual-release requirements apply because the operator or the next destination sits under a different authority.
- Previous maintenance was done at multiple shops and the release file was consolidated by none of them.
The problem
An MRO that inducts an aircraft inherits a component configuration built by other hands. Every installed part the shop leaves in place during the check implicitly relies on the release document behind it, and the file that arrives is typically an accumulation of scanned certificates in no particular order, mixing 8130-3s, Form 1s, and shop paperwork of varying completeness. Sorting proof from noise while the check clock runs is the records team's problem, and the workscope decisions cannot wait for it.
What gets reviewed
- The component release file indexed against the aircraft's current installed configuration
- FAA Form 8130-3 and EASA Form 1 documents checked for completeness and correct execution
- Certificate data matched to part number, serial number, and the installation entry it supports
- Dual-release status established for components where cross-authority acceptance matters
- Block-level content reviewed: work performed, approval basis, and limitations or exceptions
- Installation records cross-checked so each release connects to a documented fitment
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 release certificate is executed correctly, with the right boxes completed for the release type claimed
- Part and serial numbers on the certificate agree with the installation record and the tracking system
- The releasing organization held the appropriate approval at the date of issue
- Limitations, exceptions, or split-release conditions on the certificate are carried into the aircraft's records
- No installed component in the sampled configuration lacks a release document entirely
Evidence normally required
- The component release file as delivered by the operator or owner
- The current installed-configuration listing or component tracking export
- Installation and removal records connecting parts to positions
- The planned workscope, to prioritize positions the check will not disturb
- Operator contacts for requesting missing certificates
Common discrepancies
- Certificates that match the part number on file while the serial number belongs to a different unit
- A single-authority release on a component whose dual-registry situation requires both authorities to accept it
- Installations documented in the logbook with no corresponding release anywhere in the file
- Releases carrying limitations that never made it into the operator's records
What is at stake
If an unsupported installation surfaces mid-check, the shop faces an unplanned removal, a parts chase, and a schedule slip it did not quote. If it surfaces after redelivery of the work, it becomes a quality escape with the shop's release on top of it. Either path costs more than an induction review that found the gap while the operator could still be asked for the document.
How the work runs
Index against configuration
Match every document in the delivered file to a component position, exposing coverage gaps immediately.
Verify the certificates
Check execution, approval status, and block content for each release relied on by the configuration.
Tie releases to installations
Confirm part and serial continuity from certificate through installation record to tracking data.
Report and request
Deliver the verified index, the unsupported-installation list, and the requests that close the gaps.
What the buyer receives
- A verified release-document index mapped to the installed configuration
- A list of unsupported or partially supported installations, prioritized by workscope relevance
- Drafted evidence requests for the operator, owner, or prior maintenance providers
Who uses the output
- Quality leadership deciding what the shop can rely on and what it must challenge
- Program managers protecting the check schedule from mid-event surprises
- Records-control staff assembling the final work package and redelivery documentation
How the work fits into the transaction or program
Release verification sits at the front of the check because its findings alter the workscope: an unsupported component the plan assumed would stay may now need replacement or documentation recovery. The verified index also becomes part of the work package the shop hands back, which shortens the operator's own acceptance review at the other end.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Which certificate satisfies which authority depends on the part's origin, the work performed, and the bilateral arrangements in force at issue. The review applies the acceptance rules relevant to this aircraft's registry and the operator's stated needs, and flags components whose paperwork would fail on a registry the aircraft is known to be heading toward.
Regulatory limits
The review assesses documents against their own requirements and the acceptance rules that apply. It does not issue or correct release certificates, approve parts for installation, or relieve the MRO of its own inspection and release obligations under its approval.
What this review does not cover
- Physical verification of installed part and serial numbers on the aircraft
- Suspected unapproved parts investigation beyond flagging the documentary indicators
- Release of the MRO's own work at check completion
Specific to this review
- Serial-number mismatches between certificate and installation record are the most common defect in delivered release files, and most are clerical, but each one has to be resolved as if it were not.
- A release certificate proves the state of a part when it left the releasing organization; the installation record is what connects that state to this aircraft, and files usually break at that connection.
- Dual-release gaps stay invisible until a registry transfer or cross-authority workscope makes them binding, which is why the review considers the aircraft's destination registry as well as its current one.
- Operators answer document requests fastest in the first weeks after handing an aircraft to a shop, while their own induction file is still open.
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
Does the review cover parts the shop will install during the check?
No. Incoming parts for the check flow through the shop's own receiving inspection. This review covers the components already installed on the aircraft at induction, whose documentation the shop would otherwise take on trust.
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.