Heavy-check closeout
Release-document review before the aircraft leaves heavy check
This review checks the authorized release certificates in a heavy-check work package before the aircraft leaves the MRO's hangar. Endeavor Elements runs it for the MRO's quality and records-control staff in the final days of the visit, working through the component release file, FAA Form 8130-3 and EASA Form 1 entries, dual-release wording, and the installation records each certificate must pair with. Certificates that support the release stand as verified; certificates with block errors, mismatched serial numbers, or missing installation entries go onto an exception list with the evidence needed to fix each one. The MRO closes the visit with a release file its customer can accept without a paperwork dispute.
When this review is needed
- The check is in its final week and the component release file still has certificates waiting on vendor paperwork.
- The customer's acceptance team arrives in days and the work package has not had an independent certificate pass.
- A prior visit ended in a paperwork dispute over release documents and the invoice sat unpaid while it ran.
- Dual-release work was performed for an EASA-registered customer and the certificate wording has not been checked against that requirement.
The problem
The closing weeks of a heavy check pile released tasks up faster than records control can screen the paperwork. Certificates arrive from subcontractors and parts distributors in whatever state they were issued, and the mechanics who installed the parts have moved on to the next task. By exit day the component release file is large, uneven, and about to be judged line by line by the customer's records team.
What gets reviewed
- Every FAA Form 8130-3 and EASA Form 1 in the component release file, screened block by block
- Dual-release certificates checked for the wording both authorities expect
- Pairing of each release certificate with the installation record for the position it was fitted to
- Subcontracted work releases against the tasks sent out during the visit
- Serial-number and part-number agreement between certificates, task cards, and the fitted configuration
- Certificates for parts removed and refitted during the check, where trace can silently break
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
- Block 11 status and block 12 remarks on each 8130-3 support the use the part was actually put to
- Certificate issue dates precede the installation dates recorded on the corresponding task cards
- Dual-release documents carry both the FAA and EASA statements required for the customer's registry
- Serial numbers on release certificates match the numbers recorded at installation, digit for digit
- No installed position in the work package lacks a release document, and no certificate in the file lacks a fitted part
Evidence normally required
- The component release file as it stands, including certificates still in supplier follow-up
- The work package task cards covering installations and component changes
- The subcontract register for work sent to outside shops during the visit
- The customer's records-acceptance standard or lease requirements, where the operator has shared them
- Removal and installation records for parts swapped between positions during the check
Common discrepancies
- A certificate whose block 11 says inspected or tested while the task card claims an overhaul
- Installation entries citing a certificate number that appears nowhere in the release file
- Dual-release wording missing on parts fitted to an EASA-registered aircraft
- Vendor certificates naming a different serial number than the part the mechanic recorded fitting
What is at stake
A certificate problem found by the customer instead of the MRO changes who controls the clock. Acceptance stalls, the aircraft occupies a line the hangar needs, and the commercial conversation shifts from workmanship to paperwork. Some errors, such as a wrong block entry on an 8130-3 issued months earlier by a vendor, take weeks to correct through the issuing organization.
How the work runs
Inventory the release file
List every certificate in the component release file and match the file against the installations recorded in the work package.
Screen each certificate
Check blocks, dates, serial numbers, and release statements against the task cards and the registry the aircraft flies under.
Register the exceptions
Record each defective or missing certificate with the correction needed and the party who must supply it.
Support closure to exit day
Track supplier corrections and confirm each exception clears before the customer's acceptance review begins.
What the buyer receives
- A screened component release file with each certificate marked verified or exception
- An exception register stating what is wrong with each flagged certificate and who must correct it
- A supplier follow-up list with the specific reissue or correction to request
- A short closure summary the quality manager can hand to the customer's acceptance team
Who uses the output
- The MRO quality manager signing off the visit paperwork
- Records-control staff chasing supplier corrections before exit day
- The customer-facing program manager defending the release file at acceptance
How the work fits into the transaction or program
The review sits between the last task-card signoff and the customer's records acceptance. It runs while the aircraft is still in the hangar, when the mechanics, the supplier contacts, and the leverage to demand corrected paperwork are all still available. Findings feed the exception register the program manager works from through exit day.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA and EASA release documents carry different fields and different signature authority. A part destined for an EASA-registered aircraft needs an EASA Form 1 or a dual-release 8130-3 with the correct acceptance statement, and a domestic 8130-3 alone may not satisfy the customer's CAMO. The review applies the standard of the registry the aircraft will fly under, and of the customer's lease where its terms have been shared.
Regulatory limits
The review examines documents. It does not certify the maintenance performed, issue or amend any release certificate, approve the aircraft for return to service, or make an airworthiness determination. Certification authority stays with the approved organization and the individuals who hold it.
What this review does not cover
- Physical inspection of installed parts or verification of the work itself
- Issuing corrected release certificates on behalf of suppliers
- Negotiating acceptance terms between the MRO and its customer
Specific to this review
- Supplier-issued certificates are the slowest exceptions to fix; a reissue can take longer than the remaining check schedule, which is why the screen runs before the last week.
- Parts robbed from one position and refitted to another during a check often keep their original certificate but lose the paper trail connecting them to the new position.
- Block 12 remarks are where usable certificates go bad: a limitation noted by the shop can quietly conflict with how the part was installed.
- A missing certificate found at acceptance is priced by the customer; the same gap found a week earlier is a supplier phone call.
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
Why review certificates the receiving customer will check anyway?
Because the order matters. An error the MRO finds first is corrected quietly through the supplier while the aircraft is still on the check line. The same error found by the customer becomes an acceptance objection, and the correction happens under a dispute clock with the invoice held.
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.