LEAP engine repairs
Repair-approval records review for LEAP engine assets
This review examines the repair and alteration records on a specific LEAP engine and confirms that every repair carried on the asset rests on approved data. It is run for a lessor, airline, or manager evaluating, transferring, or keeping the engine in service, usually when the repair history has grown across shops and operators. It works through the repair map, damage dispositions, and return-to-service entries, matching each one to its approval basis. You receive a supported exception list, a source map behind each repair, and a closure plan sized to this engine.
When this review is needed
- A LEAP engine has passed through more than one shop and the repair history needs to be tied back to approved data.
- A buyer or incoming lessee wants each repair on the engine supported before the asset changes hands.
- A repair disposition on file references a manual section but the approval basis was never captured alongside it.
- A borescope or shop finding produced a blend or repair whose paperwork has to be reconciled to the repair map.
The problem
A LEAP engine accumulates blends, weld repairs, and part swaps at the module level, and the paperwork that authorizes each one is scattered across shop reports, disposition sheets, and return-to-service entries from different visits. A repair that was performed correctly can still read as unsupported if the approved data reference behind it was never filed with the record. The repair map then says one thing while the substantiation says less.
What gets reviewed
- Every repair and alteration on the engine mapped against the disposition that authorized it
- The approved-data reference behind each repair confirmed as applicable to the part and the finding
- Blend and weld repairs reconciled to the limits in the referenced manual section
- Return-to-service entries checked against the repair they close
- Alterations that change the engine build recorded with the correct approval basis
- The repair map reconciled to the shop reports and disposition sheets it summarizes
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
- Each repair on the map traces to a disposition and an approved-data reference an auditor would accept
- Blend and weld dispositions fall within the limits of the manual section they cite
- Return-to-service entries name the repair they close and the data used
- Alterations to the engine build show approval appropriate to the change and the jurisdiction
- The repair map agrees with the underlying shop reports rather than restating them from memory
Evidence normally required
- The repair and alteration map for the engine serial number
- Shop reports and disposition sheets from each visit that touched the engine
- Damage reports and the approved-data references cited against them
- Return-to-service entries covering the repaired parts
- Any records standard the transaction or program requires the repairs to meet
Common discrepancies
- A repair on the map whose approved-data reference is named but not filed with the record
- A blend disposition that exceeds the limit in the manual section it cites
- An alteration recorded as a routine repair when it changed the engine build
- A return-to-service entry that does not identify the repair or the data behind it
What is at stake
A repair carried without a traceable approval basis forces a conservative call at the next transaction: it gets re-substantiated, disputed, or in the worst case the affected part gets pulled. Each of those costs more than confirming the basis while the shop that did the work can still be reached, and the exposure travels with the engine until someone closes it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair map
Pull every repair and alteration claimed on the engine and the disposition behind each one.
Match repairs to approved data
Confirm each repair cites data that applies to the part, the finding, and the jurisdiction.
Reconcile to the shop record
Check the map against the shop reports and return-to-service entries it summarizes.
List and sequence exceptions
Flag unsupported or mis-recorded repairs and set out the evidence that closes each.
What the buyer receives
- A supported exception list ranking each unsupported or mis-recorded repair
- A source map tying every repair to the disposition and approved data behind it
- A closure plan naming the evidence needed to settle each open repair
Who uses the output
- Asset managers pricing the exposure that unsupported repairs carry into a deal
- Records teams assembling the approval evidence each repair needs
- Engineering deciding how to treat a repair whose basis cannot be recovered
How the work fits into the transaction or program
The repair-approval review sits alongside the shop-visit and configuration record checks on the same engine. It settles the substantiation behind each repair before that history feeds a lease transfer, a sale data room, or the next shop induction, so the repair map the counterparty reads is one that holds up.
Aircraft-specific considerations
Because the LEAP is a newer engine, much of its repair history lives in digital shop records and disposition systems rather than paper folders, so the review pays attention to whether the approved-data reference actually rode along with the digital disposition. Current configuration, LLP standing, and shop-visit release evidence carry more weight on this family than on older engines, and repairs are read against that build rather than a generic pattern.
Regulatory limits
The review confirms that each repair is internally consistent and supported by approved data on the records. It does not approve a repair, issue or restore any approval, develop repair data, or make an airworthiness determination on the engine or any part of it.
What this review does not cover
- Performing or re-performing any repair on the engine
- Developing or approving new repair or alteration data
- Any airworthiness determination on the repaired parts
Specific to this review
- On a LEAP engine the highest-risk repairs sit at the module level, so a single blend can be sound in the metal but unsupported on paper if its approved-data reference was never filed.
- Digital disposition systems often store the finding and the fix but drop the approval reference, which is exactly the link this review rebuilds.
- A repair recorded as routine when it altered the engine build is harder to unwind later than an unsupported repair, because the record itself mischaracterizes what happened.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
A repair looks fine physically but its approval reference is missing. Is that a real problem?
Yes. A buyer or auditor relies on the record, not the metal, and a repair without a traceable approval basis reads as unsupported regardless of workmanship. Recovering the reference from the shop that performed the work is far cheaper than re-substantiating or removing the part later.
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.