Engine records
Engine shop-visit records reconciled within a scanned archive
Engine shop-visit packages are the densest documents in any records archive, and this review reconciles each scanned package into a coherent account of the visit. It confirms that the workscope, the module build records, the LLP removals and installations, the test-cell results, and the release paperwork all describe the same engine leaving the shop in the same configuration. Pages lost, duplicated, or shuffled in scanning are identified per package, and each visit carries a completeness grade in the corrected index.
When this review is needed
- Marketing or appraisal of the engines is underway and shop-visit history drives most of the value discussion.
- A scanned visit package runs to thousands of pages and its completeness has never been confirmed against the shop's transmittal.
- Configuration questions from a lessee or shop reveal the archive's copy of the last visit is missing sections.
- Multiple visits for the same engine were scanned in one batch and their pages may have interleaved.
The problem
A shop-visit package leaves the repair station as a structured document set: workscope, findings, module records, LLP sheets, subcontract paperwork, test data, and the release. Scanning turns that structure into a page stream, and any transmittal list that defined completeness often stays behind as paper. Years later the archive holds a folder named for the visit number, and no one can say whether the 4,100 pages inside are the whole package or most of it.
What gets reviewed
- Each shop-visit package inventoried against its transmittal or table of contents where one exists
- Workscope compared with findings and accomplished work through the package
- Module build and strip records reconciled with the configuration stated at release
- LLP removal and installation sheets within the visit checked against the engine's status sheet
- Test-cell acceptance data located and matched to the released engine and date
- Subcontracted work and its release paperwork confirmed present inside the package
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
- The engine serial number and visit dates are consistent on every section of the package
- Parts shown installed during the visit appear in the build records and the release configuration
- The test-cell report corresponds to the final build, without a later rework left undocumented
- Page sequences are unbroken where the source documents were paginated
- No section of this package contains pages from a different visit or a different engine
Evidence normally required
- The scanned shop-visit packages with the archive's metadata and folder structure
- Engine status sheets and the current configuration records for each serial number
- Shop transmittal letters or package tables of contents, where retained
- LLP status sheets covering the parts moved during each visit
Common discrepancies
- Test-cell sections absent archive-wide because the shop delivered them separately on media that was never scanned
- Interleaved pages where two visits for sister engines went through the scanner in one session
- Build records showing a part the release configuration does not carry, with the resolving rework sheet missing
- Subcontract release certificates referenced by the package but filed in a general receiving folder
What is at stake
Shop-visit records are how an engine's condition and configuration are believed. A package that cannot demonstrate its own completeness weakens LLP trace, undermines the released configuration, and gives any counterparty grounds to discount green time. When the gap is found at the next induction, the shop rebuilds context from its own retained files at the operator's expense, and lead time stretches while everyone waits on document recovery.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory the visits
List every shop visit per engine and gather each package with any transmittal that defines it.
Reconstruct the structure
Rebuild each package's sections from the page stream and note breaks and intrusions.
Reconcile the story
Check workscope, builds, LLP movements, test data, and release against one another.
Grade and index
Publish per-visit assessments in the corrected index and issue the recovery list.
What the buyer receives
- A per-visit completeness and coherence assessment for every package in the archive
- Section-level pointers into every package, added to the corrected digital index
- A recovery list naming the missing sections and the repair station most likely to hold each
Who uses the output
- Powerplant engineers relying on visit records for workscope and removal planning
- Records staff answering shop-visit document requests from lessors and appraisers
- Asset managers presenting engine history in valuations and remarketing
How the work fits into the transaction or program
The shop-visit review supplies the raw material for LLP trace, since most cycle hand-offs happen inside these packages, and it draws on the release-document review for the certificates embedded in each visit. On a full archive program it typically runs after those two, deepening the same corrected index rather than starting a parallel one.
Jurisdiction-specific considerations
Visits performed at FAA-certificated repair stations close with releases under 14 CFR 43 and documents governed by Order 8130.21, while EASA-approved shops issue the Form 1 under their own approvals, and many packages carry dual releases. An engine that alternated between regimes across visits leaves an archive where the completeness standard shifts package by package, and the review applies the standard each visit was actually built to.
Regulatory limits
The review assesses documentary completeness and internal consistency. It does not evaluate workscope adequacy, does not certify the engine's condition or configuration, and does not reopen the shop's release. Technical judgment about the engine remains with the operator's engineering and the responsible organizations.
What this review does not cover
- Borescope, inspection, or any physical assessment of the engines
- Workscope or cost analysis of past or future shop visits
- Direct retrieval of documents from repair stations, beyond identifying the request
Specific to this review
- Test-cell data is the section most often missing from scanned packages because shops historically delivered it on separate media, and scanning projects only captured paper.
- Package page counts are a fast screening tool: a heavy overhaul that scanned to a few hundred pages is almost certainly incomplete before anyone reads a word.
- Repair stations retain their own copies for finite periods, so a recovery list acted on promptly succeeds far more often than one acted on at the next transaction.
- Interleaving between sister-engine packages is self-hiding, since every page is genuine and correctly formatted; only serial-number checks at section level expose it.
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 shop released the engine, so the records must have been complete then. What changed?
The package was complete when transmitted. Scanning, migrations, and years of handling degrade what the archive retains, and the release does not protect the operator's copy. This review measures what survives today, which is what the next shop, lessee, or buyer will actually see.
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.