Pre-purchase diligence
Engine shop-visit records review for acquisition teams in pre-purchase diligence
An engine shop-visit records review during acquisition tests whether the shop-visit packages in the data room actually support the maintenance status the price assumes. It is run for the buy-side technical team while the data room is open and terms can still move. Reviewers work through shop reports, module build records, test-cell results, and release certificates for each visit claimed on the status summary. The output is an exception register tied to price exposure, a request list for the seller, and a closure route for every open item before signing.
When this review is needed
- A letter of intent is signed and the data room holds shop-visit packages nobody on the buy side has opened yet.
- The price carries maintenance adjustments that rest on a claimed performance restoration at the last visit.
- An engine changed hands between shops or operators and the visit history arrived in fragments.
- Exclusivity expires soon and the team must decide which engine findings justify a price conversation.
The problem
Engine value usually carries the deal, and the seller's status summary states shop-visit outcomes as settled facts. The packages behind those facts can run to thousands of pages across several shops, formats, and owners, and the diligence window is measured in weeks. Reading them properly means tying each claimed workscope to the report, the build records, and the release that prove it happened, which is exactly the work a compressed timeline squeezes out.
What gets reviewed
- Each claimed shop visit matched to a complete package: report, workscope, findings, and release
- Workscope actually performed compared against the level asserted in the status summary
- Module build records and the LLPs installed or carried through each build
- Test-cell acceptance results and any concessions or deviations recorded at release
- Release certificate coverage for the engine and for parts introduced during the visit
- Consistency between shop-visit dates, cycle counts, and the engine's operating history
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 performance-restoration claim behind the price is supported by the workscope documented in the shop report
- LLP serial numbers in the build records agree with the current status sheet and its cycle totals
- Test-cell data shows an acceptance result, and any waived limits are documented with an approval
- The release certificate for each visit covers the work described and carries the approvals FAA and EASA acceptance requires
- Cycle accumulation between visits is arithmetically consistent with utilization records
Evidence normally required
- The engine shop-visit packages and status summaries in the data room
- Current LLP status sheets for each engine with supporting releases
- Engine logbooks or electronic equivalents covering the ownership period
- Utilization statements showing hours and cycles between visits
- The maintenance-adjustment assumptions used in the pricing model
Common discrepancies
- A visit priced as a full performance restoration whose report documents module-level repair only
- Parts introduced at a build without release certificates in the delivered package
- Test-cell sheets missing from an otherwise complete shop report
- Cycle counts on the status summary that cannot be reproduced from the visit history
What is at stake
A buyer who signs against an unverified shop-visit history absorbs the difference between what was claimed and what the records support. If the last visit was booked as a restoration but the package shows a lighter workscope, the maintenance adjustment was mispriced, and the shortfall surfaces at the next shop visit or the next trade, when the seller is long gone.
How the work runs
Index the packages
List every claimed shop visit per engine and confirm a package exists for each, flagging visits with no documentation at all.
Verify workscope and builds
Read each report against the claimed workscope and trace module builds, LLP movements, and test-cell acceptance.
Check release coverage
Confirm release certificates cover the work performed and the parts introduced, with the approvals the registries require.
Report against the price
Deliver the exception register ranked by pricing impact, with a request list and closure route per item.
What the buyer receives
- An engine-by-engine reconciliation of claimed status against package evidence
- An exception register ranked by pricing impact
- A seller request list with the specific documents needed to close each exception
- A short-form summary the deal team can carry into negotiations
Who uses the output
- Transaction leads deciding whether findings become price adjustments or conditions
- Technical due-diligence engineers completing the wider records review
- Investment teams documenting the basis for the maintenance assumptions in the model
How the work fits into the transaction or program
Shop-visit findings feed directly into the purchase negotiation while terms are still open, and whatever remains unresolved at signing carries into the closing conditions. After the deal, the same reconciliation becomes the starting point for the buyer's engine records baseline, so nothing found during diligence has to be rediscovered later.
Start with a single asset
Organize records and a discrepancy register for diligence.
Jurisdiction-specific considerations
Packages assembled under FAA and EASA regimes document the same work differently. A visit released on an FAA Form 8130-3 with a domestic-only approval can complicate a later transfer to an EASA-registered operator, so the review notes which releases carry dual acceptance and which do not.
Regulatory limits
The review reports what the delivered records substantiate. It does not determine airworthiness, approve or reject any repair, issue or amend release documentation, or replace the borescope inspections and physical surveys the buyer commissions separately.
What this review does not cover
- Physical or borescope inspection of the engines
- Valuation or maintenance-reserve modeling
- Negotiation of the purchase agreement itself
Specific to this review
- Shop-visit packages often live with the shop, the prior operator, and the lessor in different versions, and the data-room copy is not always the most complete one.
- The gap between a claimed restoration and a documented repair workscope is one of the largest single records-driven price exposures in an aircraft trade.
- Module swaps between engines in the same fleet are where LLP trace most often breaks, and the break is only visible by reading the build records, never the summary.
- Requests to a shop for missing documents move faster while the seller still has a commercial relationship with that shop, which is another reason to raise them before closing.
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
Can this run in parallel with the rest of the records diligence?
Yes, and it usually should. Engine packages are the largest and slowest part of a data room, so starting them first keeps the engine findings from arriving after the airframe review has already closed.
What happens if the seller cannot produce a missing shop report?
The item goes on the exception register with the exposure stated plainly. The deal team then decides whether to chase the document through the shop, price the uncertainty, or make delivery of the record a closing condition.
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.