LEAP maintenance program
Maintenance-program records review for LEAP engine assets
This review confirms that the maintenance program applied to a specific LEAP engine matches an approved program and that every deviation traces to substantiation. It is run for a lessor, airline, or manager evaluating, transferring, or maintaining the engine, often when the program has changed or the engine is bridging to a new operator. It works through the approved revisions, task escalations, and bridging analyses against the source documents behind them. You receive a supported exception list, a source map for the applied program, and a closure plan for this engine.
When this review is needed
- A LEAP engine is moving to an operator whose program differs and the applied tasks have to bridge to the new one.
- Task escalations or a program revision have been applied and the substantiation behind them needs checking.
- A CAMO or continuing-airworthiness team is taking on the engine and wants the program status confirmed to source.
- The engine's program status feeds a transaction and the buyer wants each deviation supported.
The problem
The program applied to a LEAP engine is a chain of approved revisions, operator-specific escalations, and bridging analyses, and each link has to point back to a source document. When an escalation was applied on a prior program without the analysis that justified it, or a revision was adopted but the applicability to this engine was never confirmed, the status list says the engine is current while the substantiation for how it got there is thin.
What gets reviewed
- The approved program revisions applied to the engine and their effectivity for this serial number
- Task escalations checked against the analysis that justified each one
- Bridging analyses where the engine moved between programs
- Source-document references behind each interval and task the status asserts
- The applied program status reconciled to the underlying approvals
- Deviations from the baseline program identified and traced to their basis
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 program revision applied to the engine names an approval effective for the serial number
- Every task escalation traces to a documented analysis that supports the interval
- A bridging analysis exists wherever the engine crossed between programs
- Intervals in the status list follow from the source documents behind them
- Deviations from the baseline program carry a stated and traceable basis
Evidence normally required
- The maintenance-program status for the engine serial number
- Approved program revisions and their effectivity data
- Escalation analyses and any bridging studies applied to the engine
- Source documents referenced by the program tasks
- The receiving operator's program where a bridge is in scope
Common discrepancies
- A task escalation applied without the analysis that justified the longer interval
- A program revision adopted but not confirmed applicable to this serial number
- A bridge to a new program that skipped a task the receiving program requires
- An interval in the status list that does not follow from any referenced source
What is at stake
An engine running on a program whose deviations do not trace forces the receiving operator to rebuild the justification or reset intervals, both of which cost time and can pull tasks forward. At a transaction, an escalation without its analysis reads as an interval the counterparty did not agree to, and it becomes a point of retrade rather than a closed item.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the applied program
Assemble the revisions, escalations, and bridges the engine's status asserts.
Trace each deviation
Confirm every escalation and bridge points to a documented analysis and approval.
Check effectivity
Verify each revision applies to this serial number rather than the fleet generally.
List the exceptions
Flag deviations that do not trace and the substantiation that would close them.
What the buyer receives
- A supported exception list of program deviations that do not trace
- A source map linking the applied program to its approvals and analyses
- A closure plan for recovering the substantiation each deviation needs
Who uses the output
- Continuing-airworthiness teams taking the engine onto their program
- Asset managers pricing the program deviations a buyer would question
- Records teams recovering the escalation and bridging analyses on file
How the work fits into the transaction or program
The program review establishes the interval and task baseline that the engine's due-status and task-card records depend on. It runs when the engine changes programs or feeds a transaction, so the status the receiving CAMO inherits is one whose deviations each trace to an approved source.
Aircraft-specific considerations
LEAP program status is typically maintained in a digital tracking system, so the review confirms that escalation and bridging analyses referenced by the tracker actually exist as documents rather than as tracker entries alone. On newer fleets like this one, current program status and its traceability to source carry more weight than a long paper history, because the engine has fewer visits but tighter documentation expectations.
Jurisdiction-specific considerations
An engine moving from an FAA-program operator toward an EASA CAMO has to satisfy continuing-airworthiness expectations that treat program approvals and escalation substantiation differently, so the review notes where an interval accepted under one system needs fresh justification for the other before the receiving CAMO can rely on it.
Regulatory limits
The review confirms the applied program traces to approved revisions and documented analyses. It does not approve a maintenance program, accept an escalation, set intervals on an authority's behalf, or make an airworthiness determination on the engine.
What this review does not cover
- Authoring or approving the maintenance program or its escalations
- Setting or resetting task intervals for the operator
- Any airworthiness determination on the engine
Specific to this review
- A LEAP escalation recorded only in the tracking system, with no analysis document behind it, is the deviation most likely to unwind at a program bridge.
- Program applicability on a newer engine is easy to over-adopt: a fleet revision can be logged against a serial number the effectivity does not actually cover.
- Bridging to a new operator's program is where a quietly skipped task surfaces, because the receiving program tests intervals the prior one never checked.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
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.
Frequently asked questions
The tracking system shows the engine as current. Why review the program records behind it?
A tracker shows the interval that was applied, not the analysis that justified it. If an escalation or bridge has no supporting document, the receiving operator has to rebuild the justification or reset the interval, and that is exactly the exposure this review surfaces before it becomes a bridging problem.
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.