Narrowbody turbofan asset
CFM56 narrowbody engine records review
A CFM56 records review verifies the file of a narrowbody turbofan against the life and status its status sheet asserts. Lessors, airlines, and acquisition teams run it before an engine sale, a lease return, or an asset move. Because the engine is modular, the work traces life-limited parts module by module across the fan, core, and turbine, reconciles shop-visit workscope and build records, and confirms release paperwork at each change of custody. You receive a per-module trace, a list of breaks in the chain, and the evidence each one needs to close.
When this review is needed
- A narrowbody engine is being sold, returned, or moved and the module-level life-limited part trace drives the value.
- A status sheet states life remaining that has not been checked against the shop-visit build records.
- Modules were swapped at a prior shop visit and the release and build evidence has to be reconciled.
- The engine has passed through several operators and the cycle history needs confirming across the chain.
The problem
On a modular engine, parts move between cores and turbines at shop visits, and a status sheet summarizes life remaining without showing the build evidence that justifies it. A trace can break inside a single module group when a part was swapped without the release or build record following it, and a status sheet alone does not reveal that the part now installed is not the one the life figure was computed for.
What gets reviewed
- Module-level life-limited part trace by part and serial number across the fan, core, and turbine modules
- Time-since-new and cycles-since-new accumulation across operators and shop visits
- Shop-visit workscope, build records, and the modules installed at each visit
- Release paperwork at each change of custody and each module swap
- The status-sheet life remaining reconciled against the build and shop records
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 life-limited part traces from current status to its required origin without an unexplained gap
- Module build records reconcile with the part and serial numbers on the current status sheet
- Time and cycle history is internally consistent across logs, shop reports, and the status sheet
- Each change of custody carries a release certificate valid for the jurisdiction it moved under
- Parts swapped between module groups carry the build and release evidence to support the swap
Evidence normally required
- Engine and module status sheets with part and serial numbers
- Shop-visit reports and build records for each visit
- Release certificates for each module and life-limited part at each change of custody
- Logs or digital records showing accumulation and installation history
Common discrepancies
- A life-limited part whose trace cannot be carried back to its required origin
- Module build records that disagree with the serial numbers on the current status sheet
- Cycle counts that differ between the status sheet and the last shop report
- A release certificate missing for a module swapped at a prior shop visit
- A part moved between module groups without the build record following it
What is at stake
A life-limited part whose trace cannot reach its required origin may have to be treated as having less usable life than the status sheet claims, or pulled early. On a narrowbody engine that difference is significant, and it is far cheaper to isolate before the deal closes than to argue afterward.
How the work runs
Map the modules
Lay out the fan, core, and turbine modules and the life-limited parts each one holds against the current status sheet.
Reconcile each build
Match every shop visit's workscope and build record to the modules and parts the status sheet now claims.
Trace to origin
Carry each life-limited part from current status back to its required origin and isolate any break to the visit where it arose.
Register and close
Record each break with its source and a closure path, or quantify its effect on usable life.
What the buyer receives
- A per-module traceability record showing the chain and any break
- A list of missing or inconsistent documents by part and module
- A reconciliation of the status-sheet life remaining against the build and shop records
- A recommended path to close each gap or quantify its effect on usable life
Who uses the output
- Acquisition and asset teams pricing the engine
- Records teams assembling the module trace package for the transaction
- Engineering deciding how to treat a part with an incomplete chain
How the work fits into the transaction or program
The review supports an engine sale, a lease return, or an asset move by turning a status sheet into a supported module-level trace. Its output feeds the data room and the discrepancy register for the larger transaction.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
A release accepted under one authority is not automatically accepted under another. Where a module or part has moved across authorities, the trace has to show release documentation the receiving authority will accept.
Regulatory limits
The review confirms traceability and consistency of the records. It does not certify a part, determine remaining life on an authority's behalf, or replace the approvals required to install or operate the engine.
What this review does not cover
- Physical inspection, borescope, or measurement of the engine or its parts
- Re-certification or re-life of a part or module
- Any airworthiness determination or remaining-life finding
Specific to this review
- A modular engine is traced module by module, because parts move between cores and turbines at shop visits and the trace can break inside a single module group.
- A single missing module release at a prior shop visit can force a conservative life assumption that is expensive on a narrowbody engine transaction.
- The part installed now is verified against the part the status-sheet life figure was computed for, since a swap without the build record breaks that link silently.
Sources
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 Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why trace a modular engine module by module?
Parts move between cores and turbines at shop visits, so a trace can break inside a single module group while the engine-level summary looks intact. Tracing module by module isolates the break to the specific build where it occurred.
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.
Walk through your situation with an engineer who has done this work.