Engine shop visits
Engine shop-visit package review for MRO teams supporting a lease return
When a customer's leased aircraft heads back with engines the shop worked on, the shop-visit package becomes redelivery evidence. This review checks each package the MRO produced or holds, covering workscope, module build records, LLP disk sheets, test-cell results, and the release certificate, against what a lessor's engine reviewer will demand. It is run by or for the MRO's quality and records function before the package enters the return data room. Output is a package-completeness report, a fix list for assembly gaps, and a defensible file the customer can submit without rework.
When this review is needed
- A customer has requested the full visit package for a redelivery data room and the file was assembled for internal retention, never for external review.
- The visit involved subcontracted module work and the subcontractor's records were filed separately from the main package.
- Disk sheets from the build have to line up with an LLP status sheet the customer's CAMO maintains independently.
- The release certificate is on file but the substantiating trail between workscope, findings, and final build is thin.
The problem
A shop-visit package that satisfied the shop's own quality system can still fail a lessor's reviewer, who reads it as a trace document rather than a work record. The reviewer wants to follow a disk from incoming inspection through the module build to the disk sheet and the release, while the package was filed by process step and dispersed across engineering, production, and stores. Reassembling it under a customer's redelivery deadline strains a records team that also has live inductions to serve.
What gets reviewed
- Each shop-visit package inventoried against a redelivery-grade completeness standard
- Module build records checked for continuity from disassembly findings to the final build configuration
- LLP disk sheets reconciled with incoming part status and the customer's LLP status sheet
- Test-cell data verified as present, complete, and matched to the released engine configuration
- Subcontracted work packages folded into the main file with their own release documentation
- The release certificate cross-checked against the workscope actually performed
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
- Every LLP that changed during the visit appears on a disk sheet with life figures consistent with incoming paperwork
- Build records account for each module's configuration without unexplained serial-number changes
- The test-cell report corresponds to the engine's final build, including any rework loop after an initial run
- Subcontractor releases cover their scope of work and their dates nest inside the visit timeline
- Workscope amendments raised mid-visit are documented and reflected in the released configuration
Evidence normally required
- The complete shop-visit file: workscope, findings, build records, disk sheets, test-cell data, release
- Subcontractor packages and their release certificates
- The customer's LLP status sheet and incoming part documentation
- The applicable redelivery documentation standard, if the customer's lease specifies one
Common discrepancies
- Disk sheets whose cycles-since-new disagree with the incoming 8130-3 by a small margin that traces to a data-entry convention
- A subcontracted module returned with its release but without the build detail behind it
- Test-cell records for the penultimate build retained while the final run's file went unfiled after late rework
- Workscope changes agreed by phone during the visit and never written back into the package
What is at stake
Package gaps discovered inside the redelivery window turn into urgent customer escalations and, where the trail cannot be rebuilt, into disputes about the visit itself. A pattern of thin packages also follows the shop commercially: lessors remember which facilities produce files that survive review and route diligence questions, and future work, accordingly.
How the work runs
Inventory the file
List what each package contains against a redelivery completeness standard and mark the gaps.
Reconcile the technical spine
Check disk sheets, build records, and test-cell data against each other and the release.
Recover missing elements
Pull records from engineering, stores, and subcontractors while the sources are still reachable.
Assemble and index
Deliver a data-room-ready package indexed the way an engine reviewer works.
What the buyer receives
- A completeness report scoring each package against redelivery review expectations
- A gap fix list assigning each missing element to the department or subcontractor that holds it
- An assembled, indexed package ready for the customer's data room
Who uses the output
- The MRO's quality leadership answering for the package externally
- Records control staff assembling and indexing the final file
- The customer-facing program manager coordinating with the operator's redelivery team
How the work fits into the transaction or program
The engine package is usually the largest single document set in a redelivery data room and the one lessors staff with their most technical reviewer. Getting it inspection-ready before submission keeps the MRO out of the operator-lessor negotiation, and the completeness report gives the customer's return team a known-quality input for their broader records position.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Packages travel: an engine shopped under FAA Part 145 authority may support a return onto an EASA-registered aircraft or the reverse, and dual-release paperwork plus bilateral agreement coverage decide how much re-examination the receiving side can demand. The review checks release basis and package conventions against the registries actually involved in the customer's return.
Regulatory limits
The review addresses documentation completeness and internal consistency. It does not re-perform inspections, revalidate the shop's findings, alter any release, or determine the engine's airworthiness.
What this review does not cover
- Engineering assessment of workscope adequacy or build decisions
- Borescope, test, or any physical verification of the engine
- Contractual mediation between the MRO's customer and the lessor
Specific to this review
- Redelivery reviewers read packages backward, starting from the release and disk sheets, so a file indexed in production order forces them to hunt and lengthens the review.
- The perishable element in a shop-visit file is subcontractor detail: module shops merge, close, and purge archives, and their records rarely survive as long as the engine does.
- Small cycle discrepancies between disk sheets and incoming releases are usually convention differences, counting a test run or not, and documenting the convention once resolves whole families of findings.
- A package that survives one lessor review becomes reusable evidence for the engine's next several transitions, which repays the assembly effort well beyond the immediate return.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The engine was released years ago. Can the package still be brought up to standard?
Usually, if the shop retained its files. The main losses over time are subcontractor detail and informal workscope changes, so older packages need earlier starts and more chasing. What cannot be recovered gets documented as a known limitation rather than left for the lessor to discover.
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.