LEAP engine deferred-maintenance records review

When this review is needed

• A LEAP engine is heading into a lease return and open deferrals have to be cleared or accounted for before acceptance.
• Diligence on the engine surfaced a deferral log that no one has reconciled against the work packages behind it.
• An operator inherited the asset mid-life and needs to know what carried-over items are still riding on it.
• A status handover is due and the deferred position has to be stated with evidence rather than asserted.

The problem

A deferred item is only as closed as its clearing entry proves. On a LEAP engine that has moved between operators, the deferred-maintenance log tends to accumulate entries whose corrective actions live in separate work orders, task cards, or shop paper that never got tied back to the line that opened them. The reader ends up unable to say whether a deferral was worked, re-deferred under a new MEL reference, or simply dropped.

What gets reviewed

• Every entry in the deferred-maintenance log traced to the corrective action that should retire it
• MEL and CDL references checked for a valid category and interval against the operator's approved list
• Re-deferred items followed across the ownership or program changes they crossed
• Clearing entries matched to the task card or work order that documents the fix
• Items with no supporting closure evidence flagged as genuinely open
• The current open position stated as of a fixed review date

What gets validated

• Each cleared deferral carries a corrective-action record that names the same discrepancy the deferral opened
• MEL references cite a category and repair interval consistent with the operator's approved MEL
• A re-deferred item shows an unbroken chain from the original entry to the current reference
• Clearing entries fall inside the interval the deferral category allowed
• The count of open items in the review reconciles with the log the operator is currently working

Evidence normally required

• The deferred-maintenance log and any separate deferral or deferment registers
• The operator's approved MEL and CDL for the interval categories cited
• Work orders and task cards holding the corrective actions
• Engine and airframe records showing when each deferral opened and cleared
• Any prior audit or diligence findings on the deferral position

Common discrepancies

• A deferral marked cleared with no work order that documents the corrective action
• An MEL reference whose repair interval expired before the clearing entry was made
• A carried-over item re-deferred at an ownership change without a link to the original entry
• Two logs, one line and one system, that disagree on which deferrals are still open

What is at stake

An open deferral that reads as closed can transfer to a new operator as an accepted liability nobody priced. If the clearing evidence cannot be found later, the item reopens at the next audit or return with less leverage and a shorter clock, and the cost of proving the work was done falls on whoever holds the engine at that point.

How the work runs

What the buyer receives

• A supported open-and-cleared deferral list stated as of the review date
• A source map tying each cleared item to the record that closes it
• A closure plan for the deferrals that remain genuinely open

Who uses the output

• Asset managers pricing the open liability an engine carries into a transfer
• Records teams clearing the deferred position before a return or handover
• Continuing-airworthiness staff confirming re-deferred items were tracked correctly

How the work fits into the transaction or program

The deferred position sits underneath the airworthiness and redelivery work that follows it. Clearing it early means the return binder and the status handover start from a settled account of what was open, so a deferral does not resurface as a surprise once the engine is already changing hands.

Aircraft-specific considerations

Newer LEAP fleets keep much of the deferral trail in digital maintenance systems, so a clearing entry may exist in a work-order module rather than a paper log. The review follows the item into whichever system holds it and confirms the digital record carries the same corrective detail a paper task card would, because a system field marked complete is not on its own the corrective evidence.

Jurisdiction-specific considerations

Deferral categories and repair intervals sit under the operator's approved MEL, which differs between an FAA and an EASA operating environment. When an engine has passed between the two, the review notes where a deferral opened under one authority's MEL structure and was cleared or re-deferred under another, so the interval logic reads consistently across the boundary.

Regulatory limits

The review reports what the deferral records support as of the review date. It does not clear any open item, make an airworthiness determination on the engine, or grant, restore, or substitute for any operator or authority acceptance of the deferred position.

What this review does not cover

• Performing the corrective maintenance behind any open deferral
• Revising or approving the operator's MEL or CDL
• Any airworthiness determination on the engine or its installed condition

Specific to this review

• A deferral cleared inside a digital system can look retired at the header level while the corrective detail that would prove the fix was never filled in.
• Re-deferrals are where trace breaks most often, because the item picks up a new reference at each program or ownership change and the link to the original discrepancy is rarely carried forward.
• The expiry of an MEL repair interval, not the age of the entry, is what turns a valid deferral into an overdue one, so the interval math matters more than the calendar date.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits