Engine records
How to validate an engine shop-visit package
Validating an engine shop-visit package means confirming that the report, the workscope, and the release paperwork agree with each other and with the engine's recorded status. You work through the build records, the life-limited part changes, the disposition of removed and installed modules, and the release certificate that closes the visit. The package is validated before an engine transaction, a lease return, or an installation on another asset. The output is a finding list that says where the report and the supporting documents disagree.
When this review is needed
- An engine is changing hands and the shop-visit package is the evidence the value rests on.
- A module has moved between engines and the build records need to confirm what is now installed.
- A status list shows post-visit life that has not been checked against the shop report and release paperwork.
- An engine is being returned at end of lease and the last visit sets the redelivery configuration.
The problem
An engine shop visit produces documents across several owners of the process: the workscope set before induction, the report written after teardown and reassembly, the part-level release paperwork, and the build sheets for each module. A removed part and its replacement are documented in different places, and post-visit life is often typed into the tracking system before the report is filed. The status everyone relies on is therefore a summary several steps removed from the records that justify it, and the steps are where the numbers drift.
What gets reviewed
- The shop-visit report against the agreed or recorded workscope
- Life-limited part removals and installations with their part and serial numbers
- The module build records and the disposition of parts removed during the visit
- The release certificate that closes the visit and the parts it covers
- Post-visit time and cycle status carried into the engine records
- Embodiment of service bulletins and ADs performed during the visit
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 report's stated workscope matches the parts actually worked and replaced
- Each life-limited part change is supported by a release certificate and a recorded serial number
- Build records reconcile with the report and the post-visit configuration
- The release certificate is valid for the visit and covers the installed parts
- Service bulletin and AD work claimed in the visit ties to embodiment evidence
- Life on the post-visit status list traces to the shop report rather than standing alone
Evidence normally required
- The full shop-visit report and the workscope it was run against
- LLP removal and installation records with serial numbers
- Release certificates for parts installed during the visit
- The module build sheets or equivalent configuration records
- Embodiment records for service bulletins and ADs worked in the visit
- Pre- and post-visit engine status from the tracking system
Common discrepancies
- A workscope that does not match the parts the report shows as replaced
- A life-limited part installed without a release certificate in the package
- Build records that disagree with the report on which module was fitted
- A release certificate that does not cover every installed part it should
- Service bulletin work claimed in the report without embodiment evidence attached
- Life on the status list that the shop report does not support
What is at stake
If the package does not reconcile, post-visit life on the status list can be overstated against what the report and release paperwork actually support, which is expensive on a green-time or part-out decision. A configuration that cannot be confirmed forces conservative assumptions or rework before the engine can be installed, returned, or sold.
How the work runs
Anchor to the workscope
Read the workscope the visit was inducted against and use it as the reference for what the report should show.
Trace parts and modules
Follow each LLP and module change through removal, install, release certificate, and build sheet to confirm the post-visit configuration.
Reconcile status
Check that post-visit life on the tracking system traces to the shop report and not to an early transcription.
List and close findings
Record each disagreement, then close it or quantify its effect on usable life and configuration.
What the buyer receives
- A validated configuration view of the engine after the visit
- A finding list of disagreements between the report and the supporting documents
- A path to close each finding or to quantify its effect on usable life
- A reconciled post-visit status the tracking system can be corrected against
Who uses the output
- Asset and acquisition teams pricing green time or a part-out
- Records teams correcting the tracking system to the validated configuration
- Engineering deciding how to treat a module or part with an unconfirmed history
How the work fits into the transaction or program
Validation sits between the shop visit and any reliance on its outcome, so an engine sale, lease return, or installation rests on a configuration that has been checked rather than transcribed. It feeds the engine trace package and the discrepancy register for the wider transaction.
Aircraft-specific considerations
Module architecture drives where the records can diverge. An engine built as separable modules documents each module's life and history independently, so a swap moves life between assets and has to be confirmed module by module. The validation follows the actual build standard of the engine type rather than a single generic teardown.
Jurisdiction-specific considerations
A part released on one authority's form is not automatically acceptable for installation under another. Where parts in the visit were released across authorities, the package has to carry release documentation the receiving side will accept rather than relying on the form alone.
Regulatory limits
Validation confirms that the records and release paperwork are consistent and traceable. It does not re-life parts, re-certify the engine, or replace the approvals required to install and operate it.
What this review does not cover
- Physical inspection, test-cell run, or borescope of the engine
- Re-life or re-certification of any part or module
- Any airworthiness determination on the engine
Specific to this review
- Module swaps during a visit are where build records and the report most often diverge, because the part that left and the part that arrived are documented in separate places.
- A release certificate can close a visit while still omitting an individual installed part, so the certificate is checked against the install list rather than accepted on its face.
- Post-visit life is frequently transcribed into the tracking system before the shop report is filed, which lets the status list and the report drift apart.
- Separable-module engines carry life at module level, so confirming post-visit life means tracing each module's status rather than a single engine figure.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
Does validating the package re-life or re-certify the engine?
No. Validation confirms that the records and release paperwork are consistent and traceable. It does not re-life parts, re-certify the engine, or replace the approvals required to install and operate it.
Why check the release certificate against the install list?
Because a certificate can close the visit while omitting an individual installed part. Reconciling it against the parts the report says were fitted catches the gap before the engine is relied on for a transaction.
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.
Adapt the checklist to your asset, event, and jurisdiction.