Module release papers
Authorized release certificate review for the engine-module records file
This check matches every authorized release certificate in an engine-module records file to the part it covers and the position that part occupies in the current build. It reads each FAA Form 8130-3 and EASA Form 1 for work-scope status, release basis, and receiving context, and confirms the certificate population covers what the build sheets say was installed. Engine records leads use it before a transfer, or when accepting a shop-visit package into the file. It delivers a certificate-to-part reconciliation with an exception list for missing, mismatched, or insufficient releases.
When this review is needed
- The engine is transferring and the counterparty will sample certificates against the build.
- A shop-visit package just arrived and its certificates have not been checked against what was actually fitted.
- A part changed dash number at repair and the certificate no longer matches the build sheet entry.
- The engine is moving between FAA and EASA operating environments and release basis matters.
The problem
Shop-visit packages arrive as stacks of certificates sorted by the shop's convenience, while the build sheets record what went into each module by serial. Nobody is naturally responsible for proving the two sets describe the same parts. Certificates cover parts that were released and then not used, parts get fitted whose certificates ride in a subcontractor's package, and the file ends up with confident coverage in bulk and holes at specific serials.
What gets reviewed
- Every serialized part on the build sheets matched to a release certificate in the file
- Certificate work-scope status read against the status the build and marketing documents claim
- Release basis and authority checked against the environments the engine will operate under
- Certificate part and serial numbers reconciled with build-sheet entries, including dash-number changes at repair
- New-part releases distinguished from maintenance releases and verified for origin
- Orphan certificates, releases without an installed part, segregated from the active population
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
- No installed serialized part lacks a release certificate appropriate to its last shop event
- Work-scope status on each certificate supports the condition the build sheet records
- Dash-number differences between certificate and build sheet are bridged by a repair record
- Dual-release needs are met where the engine's operating environment requires both authorities
- Certificate dates sequence correctly against removal, work, and installation dates
Evidence normally required
- The component release file as held, including shop and subcontractor certificates
- Module build sheets for the current configuration
- Shop-visit reports connecting work scopes to the parts they covered
- Installation history for parts introduced outside shop visits
- The intended operating and transfer context, which sets release-basis requirements
Common discrepancies
- An installed serial whose certificate sits in an unrequested subcontractor package
- An inspected-tested release supporting a build-sheet entry recorded as overhauled
- A certificate and build sheet disagreeing on dash number with no repair record bridging them
- Single-authority releases on an engine marketed into a dual-authority operating context
What is at stake
At transfer, reviewers sample from the build sheet toward the certificates, and each serial without a matching release becomes a finding the seller must cure under deadline. A release whose work-scope status is weaker than the build claims, an inspection release standing where an overhaul is asserted, undermines the module's claimed status and can force the shop-visit narrative to be reproven from findings reports.
How the work runs
Index both populations
List installed serials from the build sheets and certificates from the file as two reconcilable sets.
Match and read
Pair each serial with its certificate and read status, basis, and dates against the build record.
Chase the gaps
Trace unmatched serials into shop and subcontractor packages, and segregate orphan releases.
Report supportable status
Deliver the reconciliation, ranked exceptions, and the release-basis summary for the transfer.
What the buyer receives
- A certificate-to-part reconciliation covering the full serialized configuration
- An exception list ranked by cure difficulty, from re-request to re-documentation
- A release-basis summary stating what operating environments the file currently supports
Who uses the output
- Engine records leads closing exceptions before the counterparty samples
- Receiving inspectors and stores teams accepting the engine onto a program
- Remarketing teams stating supportable release basis to prospective takers
How the work fits into the transaction or program
Release-document reconciliation runs beside the LLP and AD checks in the engine-module source review and shares their document base. A certificate that closes a release exception frequently also carries the cycle figure the LLP trace needed, so exceptions are worked jointly and the results file into the engine trace support file as one evidence set.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA Order 8130-21 governs completion of the 8130-3, and 14 CFR 43 sets the maintenance-release framework behind it; EASA Form 1 serves the parallel role under Regulation 1321/2014. Bilateral arrangements let one document serve both systems when completed as a dual release, but the entitlement depends on how the blocks were completed at issuance, and a reviewer reads the form, never the assumption.
Regulatory limits
The review reconciles documents to configuration. It does not issue or amend release certificates, does not determine that any part is eligible for installation, and does not convert a defective certificate into an acceptable one; where a release fails, the finding names the issuing organization as the cure path.
What this review does not cover
- Obtaining reissued or corrected certificates from shops
- Physical verification of data plates against paperwork
- Judgment on the technical adequacy of the work the certificates release
Specific to this review
- Reviewers sample from the build sheet toward the certificate file, so coverage measured from the certificate stack, however high it looks, is measured in the wrong direction.
- The work-scope status block quietly caps what the build can claim: an inspection release under an overhauled entry is a status defect no volume of other paperwork offsets.
- Dash-number changes at repair are legitimate and routine, and they still fail a serial-match check unless the repair record travels in the file to bridge old and new numbers.
- Dual-release capability is fixed at the moment of issuance by how the form was completed; discovering a single-authority release after committing the engine to the other environment means going back to the issuing shop.
- Subcontractor certificates are the most commonly absent class, because prime shops summarize subcontracted events in their reports and forward the underlying releases only on request.
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
We hold more certificates than installed parts. Doesn't that indicate over-coverage?
Volume in the certificate file says nothing about coverage of the build. Shops release parts that are never fitted, and fitted parts arrive under packages nobody opened. The only meaningful measure starts from the installed serials and asks whether each one is answered.
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.