Engines before the deal moves
Engine shop-visit package review for acquisition teams before export
Acquisition teams commission this review when a purchase involves an aircraft exporting off its current registry and the engines carry recent shop visits. It compares each shop-visit package against the workscope and build standard the seller has represented, checking shop reports, module build records, test-cell results, and release certificates. It runs inside the buyer's diligence window, staffed by records specialists working in parallel with the physical inspection. The deal team receives a workscope-versus-records comparison for each engine, a findings memo, and a punch list of items to resolve with the seller before the export certificate request.
When this review is needed
- The purchase price assumes a represented build standard from the last shop visit and nobody on the buyer side has read the package.
- Engines were overhauled close to the transaction, which is when workscope claims and records diverge most.
- The export timetable is fixed and open engine paper would block the same certificate the closing depends on.
- Maintenance-reserve and remarketing models are being built from the seller's engine summaries.
The problem
Engine value in a transaction rests on representations about the last shop visit: what was overhauled, what build standard was achieved, which LLPs went in new. The package that substantiates those representations sits with the seller and its shop, and the buyer typically sees a summary until diligence forces the full set. Reading a multi-volume shop package against a term sheet is slow, and the export timetable is usually set before the reading starts.
What gets reviewed
- Shop reports for each engine's most recent visits, compared against the represented workscope
- Module build records and the build standard actually achieved at assembly
- LLP replacements during the visit, with limits and remaining life for each installed part
- Test-cell acceptance results and margin data where the package includes them
- Release certification for the visit under the exporting side's system
- Post-visit installation and accumulation records tying the engine to the aircraft
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 shop report's completed workscope matches the representation made in the transaction
- Build records show the modules and part levels the claimed build standard implies
- LLPs stated as new at the visit carry zero-time documentation and matching releases
- Test-cell acceptance covers the final build configuration, with results in limits
- The engine serial on every document is the engine actually installed on the aircraft
Evidence normally required
- Complete shop-visit packages for each engine under review
- The transaction's engine representations or technical term sheet
- Current engine LLP status from the seller
- Installation records and utilization since the last visit
- Access to the performing shop for document queries, where the seller grants it
Common discrepancies
- A workscope represented as overhaul that the report records as a performance restoration on fewer modules
- LLPs described as new that entered the build part-used with meaningful life consumed
- Margin data withheld from the package, leaving acceptance results without context
- An engine swap since the visit that the deal documents never caught up with
What is at stake
A represented full overhaul that the records show as a lighter workscope moves real money, and the difference is far easier to recover before export than after title and registry both change. Unverified shop-visit claims also flow into the buyer's reserve and remarketing models, where they distort economics for years.
How the work runs
Anchor the representations
Extract the engine claims from the term sheet and deal documents as the test standard.
Read the packages
Work each shop report, build record, and certificate against those claims.
Quantify divergence
Convert each mismatch into a finding with its documentary basis.
Deliver the punch list
Hand the deal team the comparison and sequence open items against the export date.
What the buyer receives
- A workscope-versus-records comparison per engine, keyed to the transaction representations
- A findings memo quantifying where the records diverge from what was represented
- A pre-export punch list of items to settle with the seller while leverage remains
Who uses the output
- The deal lead adjusting price, holdbacks, or conditions before signing
- Technical due-diligence staff integrating engine findings with the airframe review
- The buyer's engine and reserves analysts recalibrating their models
How the work fits into the transaction or program
Engine findings typically carry the largest single dollar amounts in a diligence, so this review reports early into the negotiation rather than at the end of the records effort. Its punch list feeds export preparation directly, since unresolved engine paper blocks the same certificate the deal timetable depends on.
Start with a single asset
Organize records and a discrepancy register for diligence.
Jurisdiction-specific considerations
The shop completed its certification under the exporting side's system, and the buyer must judge it under the destination's: FAA Order 8130.21 shapes 8130-3 usage on one side, EU Regulation 1321/2014 and EASA Form 1 practice the other, with bilateral provisions defining acceptance between them. The comparison marks documents that will need destination-side reading after transfer.
Regulatory limits
This is buyer-side records verification. It does not certify engine condition, approve any release, validate the shop's work, or perform the airworthiness assessment supporting the export certificate.
What this review does not cover
- Borescope or physical engine inspection, which runs as a separate diligence stream
- Commercial negotiation of price or reserve adjustments
- On-wing serial verification, unless arranged with the technical inspection
Specific to this review
- Workscope language is not standardized between shops; the review reads what modules were exposed and restored rather than what label the visit carries.
- Test-cell margin, rather than a bare pass, indicates how the engine will hold on wing, and its absence from a package is itself a finding.
- Build standards are cost decisions made at the visit; records showing a lighter standard than represented shift value even when the engine performs today.
- The performing shop answers document queries fastest while the seller is still its customer, which is why queries route through the seller during diligence.
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
Should this wait until the physical engine inspection is done?
Run them in parallel. The records review and the borescope answer different questions, and each sharpens the other: a records finding tells the inspector where to look, and an inspection observation tells the records team which package claims to test hardest.
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.