Component releases
Checking authorized release certificates against the data-room files
Installed components are only as acceptable as the release documents behind them, and this review checks that coverage from inside the seller's data room. It works the component release file position by position, locating the FAA Form 8130-3 or EASA Form 1 for each tracked installation and reading it for completeness, correct part and serial identity, and a release status the receiving context can use. Diligence teams commission it while the purchase or lease review period is open. What comes back is a position-level exception list for the diligence exception schedule, with each defect classified by cure difficulty.
When this review is needed
- The component release file arrived as a bulk folder and coverage has never been confirmed position by position.
- The aircraft changed operators recently and installations from the prior operator lack visible releases.
- Dual-release requirements apply because the aircraft may move between FAA and EASA environments.
- Q&A time remains to demand missing certificates from the seller.
The problem
Release paperwork fails quietly. A folder of hundreds of certificates looks like coverage, but the certificate for a given position may name a different serial, carry a repair release where the installation context needed a new-part release, or be missing while a neighboring duplicate pads the count. Matching document to installed position is slow, exacting work, and data rooms are organized to discourage exactly that reading.
What gets reviewed
- The component release file reconciled to the installed configuration and tracked-position list
- Certificate content checked: part number, serial, work performed, release status, and issuing authority
- Release status suitability for the receiving context, including new versus repaired distinctions
- Dual-release presence where cross-registry operation is contemplated
- Chronology: the release predates and supports the recorded installation event
- Duplicates, superseded versions, and certificates orphaned from any installed position
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 tracked position pairs with a release document whose part and serial identity matches exactly
- Release blocks are completed for the work claimed and signed under an authority the context accepts
- Installation dates on the aircraft records fall after the release date on the certificate
- Components requiring dual release carry both signatures or an accepted equivalent
- No exception is cleared on the strength of a certificate belonging to a different removal cycle
Evidence normally required
- The component release file and tracked-component or configuration list
- Data-room access with removal and installation history
- The intended operating and registry context after closing
- The Q&A log and any seller statements about known gaps
Common discrepancies
- Certificates matching the part number but not the serial actually installed
- Repair releases in positions where the record claims new or overhauled condition
- Installations from a prior operator with no release document anywhere in the room
- Single-authority releases on components the post-closing operation needs dual-released
What is at stake
Positions without usable releases surface at the next removal, borescope finding, or lease transition, when the component must be dispositioned and the paperwork cannot support it. Replacing or re-certifying at that point costs multiples of what a diligence-stage demand on the seller would have, and some certificates are simply unobtainable once the issuing shop is out of the chain.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the position list
Fix the set of tracked installations the coverage will be judged against.
Match and read
Pair each position with its certificate and read identity, work, status, and signatures.
Judge in context
Test each release against the post-closing registry and operating context.
Classify and demand
Deliver the coverage matrix and the seller demand list while Q&A remains open.
What the buyer receives
- A position-level coverage matrix: covered, defective, or missing
- Exception entries classified by cure route and difficulty
- A demand list for the seller while Q&A leverage remains
Who uses the output
- The transaction lead deciding which release gaps go on the exception schedule
- Technical due diligence staff pressing the seller's Q&A on curable items
- Asset managers planning post-closing component actions around known defects
How the work fits into the transaction or program
Release-document review runs with the LLP and repair checks in the diligence records workstream, since the three share the same shop and installation evidence. Its coverage matrix informs both the exception schedule and post-closing planning, because a defective release that cannot be cured pre-closing becomes a managed item on the new owner's file.
Jurisdiction-specific considerations
FAA Order 8130-21 governs issuance of the 8130-3, EASA Form 1 serves the parallel role under EU 1321/2014, and 14 CFR Part 43 sets the maintenance-record duties that installation entries must satisfy. Whether a given release works in the receiving context depends on registry, the nature of the work released, and any bilateral provisions in force, so the review states the context it judged against.
Regulatory limits
The review evaluates documents against the stated receiving context. It does not issue or reissue release certificates, approve parts for installation, or determine airworthiness, and it does not substitute for the installing organization's own acceptance responsibilities.
What this review does not cover
- Physical verification of installed components against data plates
- Sourcing replacement certificates or parts
- Legal interpretation of bilateral agreement applicability
Specific to this review
- Orphan certificates inflate confidence: rooms often contain more 8130-3s than tracked positions, while specific positions still lack any match.
- Serial-number mismatches cluster around rotable pools, where the paperwork for a sister unit followed the wrong shipment.
- The new-versus-repaired distinction in the work description decides usability more often than the presence of the form itself.
- Cure difficulty splits sharply: issuing shops still in business reissue certificates routinely, while gaps from dissolved shops usually cannot be cured at any price.
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
Is a scanned 8130-3 acceptable, or do we need originals?
For diligence purposes a legible scan showing all blocks and signatures generally serves, and most transactions proceed on scans. What matters is that the document's content matches the installed part and the release status fits the receiving context. Where a scan is partial or altered-looking, the exception list flags it for an original or a reissue request.
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.