Engine records
Reconciling engine shop-visit records with a maintenance-control export
This review reconciles engine shop-visit packages with what the maintenance-control export says came out of each visit. Engine records specialists run it for operators and fleet teams before transfers, migrations, or lease events that expose the engine file. Workscopes, module build records, disk sheets, test-cell results, and release documents are read against the exported configuration and status. Maintenance control receives a visit-by-visit exception list showing where the package and the system disagree and which one the evidence favors.
When this review is needed
- An engine is moving with the aircraft in a transfer and the receiving team will rebuild status from the shop-visit packages.
- The export's engine configuration was keyed from a build summary rather than the released build records.
- A visit closed with open paperwork items that were never reconciled into the system.
- Test-cell margins in the package do not obviously support the on-wing performance the system assumes.
The problem
Shop-visit packages arrive as boxes or file trees assembled by the shop, then get summarized into the maintenance-control system by whoever inducts them. Two descriptions of the same visit now exist, and they drift: a disk swapped late in the build, a workscope item descoped, a release configuration that differs from the induction plan. The export presents the system's version as fact.
What gets reviewed
- Workscope planned versus workscope performed, reconciled item by item
- Module build records and disk sheets compared against the export's current engine configuration
- LLP identities and cycle positions at build checked against the status the system carries
- Test-cell acceptance results matched to the release and to any performance assumptions downstream
- Release documentation for the visit checked for scope, configuration, and completeness
- Open items, deferrals, and concessions from the visit traced to their eventual closure
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 serialized part in the released build appears in the export's configuration, and nothing extra does
- Disk sheets and module records tell one consistent story about what went into each module
- The release certificate's scope covers the full workscope the package documents
- Test-cell data is present, complete, and consistent with the released condition
- Visit-driven status changes, LLP zero points included, were carried into the system correctly
Evidence normally required
- The complete shop-visit package for each visit in scope, mini-pack at minimum
- The maintenance-control export's engine configuration and status tables
- Induction paperwork and the agreed workscope
- LLP status sheets and disk sheets for the affected modules
- Correspondence covering concessions, descopes, or open-item closure
Common discrepancies
- A late build change in the shop's records that never reached the system configuration
- Test-cell sheets missing from the package while the release presumes them
- An LLP zero point keyed at the visit date instead of the documented accomplishment point
- Open items closed in correspondence but still open, or absent, in the export
What is at stake
Configuration disagreements between package and system surface as hard findings during transfer, because they suggest either the engine or its records are wrong. Resolving them late means reopening a visit that may be years old, with the shop's own records the only arbiter, on a counterparty's schedule.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory the visits
List the shop visits in scope and confirm each package is complete enough to review.
Reconcile the build
Compare module records and disk sheets with the export's configuration, part by part.
Verify the release
Read the release documents and test-cell data against workscope and final build.
Adjudicate and correct
Resolve each disagreement to the stronger evidence and issue the corrected baseline.
What the buyer receives
- A visit-by-visit reconciliation report with each disagreement adjudicated to the stronger evidence
- A corrected configuration and status baseline for system update
- A shortfall list for the shop where the package itself is incomplete
Who uses the output
- Maintenance control aligning the system with the released engine
- Powerplant engineers relying on build data for workscope planning
- Transfer teams presenting a defensible engine file
How the work fits into the transaction or program
Shop-visit reconciliation supplies the event-level truth that the LLP and release-document reviews depend on: builds and releases are where cycle histories reset and configurations change. Run against the same export, the three reviews converge into one defensible engine story for the transfer package.
Jurisdiction-specific considerations
Releases behind FAA-context visits rest on 14 CFR Part 43 and the documentation practices of FAA Order 8130.21; EASA-context visits produce EASA Form 1 releases under Regulation (EU) 1321/2014. Packages from shops holding both approvals still need reading against the regime the receiving operator answers to, because dual approval of the shop does not guarantee dual-release wording on every certificate.
Regulatory limits
The review compares records and adjudicates documentary disagreements. It does not certify engine condition, does not reopen or amend the shop's release, and does not substitute for the operator's or CAMO's acceptance of the engine's status.
What this review does not cover
- Borescope, performance, or any physical engine assessment
- Renegotiation of shop-visit commercial terms or warranty claims
- Workscope engineering for future visits
Specific to this review
- Late build changes are the classic divergence point: the shop's as-released records update, the operator's induction-based system entry does not.
- A mini-pack that lacks test-cell sheets is the most common package shortfall and one of the fastest for the shop to cure if asked early.
- Adjudicating package-versus-system conflicts favors the release documents, because they are what the shop certified against.
- Every year between visit closure and reconciliation makes the shop's retained records harder to reach, especially after facility changes.
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 is no longer in business. Can the visit still be reconciled?
Usually, though with more residual risk. The operator-side copy of the package, release documents, disk sheets, and induction correspondence often support most of the reconciliation. Where only the shop's retained records could resolve a conflict, the review documents the ambiguity and states the conservative position rather than guessing.
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.