Engine shop-visit records review for operators between lease events

When this review is needed

• An engine has returned from a shop visit during the lease and the package has been filed without independent verification.
• The mid-lease asset review is approaching and engine documentation is on the lessor's checklist.
• An engine swap or lease of a spare engine has introduced packages built by other organizations.
• Redelivery is still years away, which is exactly when document recovery from the shop is cheap.

The problem

A shop-visit package arrives as a delivery of documents, and the operator's records office files what arrives. What did not arrive, the test-cell acceptance report, the disk sheets for one module, the release for a subcontracted accessory, is invisible until someone audits the package against the workscope. Operators discover these holes at redelivery, when the shop's document desk has turned over and the visit is one among thousands in its archive.

What gets reviewed

• Each shop-visit package during the lease indexed against its workscope and the shop's standard document set
• Module build documentation checked for completeness and serial continuity
• Disk sheets and LLP records verified against the post-visit status sheet
• Test-cell reports confirmed for the released build, including any repeat runs
• Subcontracted repairs within the visit traced to their release documents
• Packages from third-party engines, swaps or spares, reviewed against the same standard

What gets validated

• The package contents match the workscope: every module opened has build records, every part replaced has a release
• Serial numbers are continuous from induction through release, with substitutions and exchanges documented at the point they occurred
• Disk-sheet cycle figures reconcile with the LLP status sheet issued after the visit
• The test-cell report corresponds to the final released configuration rather than an intermediate build
• The release certificate's date, engine serial, and configuration statement are internally consistent with the rest of the package

Evidence normally required

• Shop-visit packages for every visit during the lease, including third-party engines
• Workscope agreements and visit correspondence
• Post-visit LLP status sheets and current engine status
• Removal, installation, and swap records for engines during the lease

Common discrepancies

• Packages complete except for test-cell data, which the shop retained pending a final report that was never chased
• An accessory overhauled by a subcontractor during the visit with its release filed at the shop, never forwarded
• Disk sheets whose installed-cycles figures were transcribed into the status sheet with a digit error
• A spare engine operated for months whose package standard differs from the operator's own and was never gap-checked

What is at stake

Every missing element of a shop-visit package has a recovery half-life. Mid-lease, a request quoting the shop's own visit number usually produces the document within weeks. At lease end, the same gap can stall the engine's redelivery status, force the operator into paying for records reconstruction, or surface as a claim under the return conditions. LLP status questions ride on the same packages, doubling the stakes.

How the work runs

What the buyer receives

• A per-visit package index showing present, missing, and inconsistent documents
• Recovery requests to shops and subcontractors quoting their own visit and order references
• A corrected LLP reconciliation where package findings change the status
• A closure log the records office maintains as documents arrive

Who uses the output

• Records leadership closing gaps against the mid-lease review timetable
• Powerplant engineers who depend on the packages for LLP and workscope history
• Maintenance directors reporting engine documentation status to the lessor

How the work fits into the transaction or program

This review turns shop-visit filing from passive receipt into verified intake, retroactively for past visits and as a template for future ones. It slots naturally after each engine's return and before mid-lease audits. The verified packages then flow into redelivery preparation years later with their contents already proven, removing the single largest records risk from the return.

Jurisdiction-specific considerations

Engine shops release work under their own approvals, and a lease can accumulate packages with FAA releases, EASA Form 1 documents, and dual releases in one archive. The review notes which regime each release satisfies, because the aircraft's next placement determines which combinations will be questioned and where dual-release evidence saves a future re-certification exercise.

Regulatory limits

The review verifies package documentation against Part 43, the 91.417 retention rules, and EU 1321/2014. It does not evaluate engine condition or workmanship, does not re-release any maintenance, and does not alter the operator's continuing-airworthiness responsibilities.

What this review does not cover

• Engine health monitoring, borescope, or performance assessment
• Commercial disputes with shops over invoiced workscope
• Reconstruction of records for visits predating the lease, unless separately scoped

Specific to this review

• Shops answer document requests fastest when quoted their own visit number and work-order references, which the package index is built to capture.
• The gap between a shop report and the test-cell report is routine, because final test documentation often follows the engine by weeks and no one owns the follow-up.
• Third-party spare engines are the weakest packages in most operator archives, since nobody applied the operator's intake standard when they arrived.
• Transcription from disk sheets into status sheets is a known error point; a two-digit cycle error found mid-lease is a correction, found at redelivery it is a dispute.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits