CFM56 redelivery
CFM56 engine delivery and redelivery binder records review
A CFM56 redelivery-binder review tests whether the binder assembled for handover actually matches the source records it claims to represent. Lessors, records teams, and asset managers use it as an engine is delivered or returned. The work checks the binder index against its contents, reconciles the acceptance evidence and discrepancy register to the underlying documents, and flags any tab that points to a record not present or not supported. You get a marked binder index, a note on each discrepancy, and a plan to close the items that would hold up acceptance.
When this review is needed
- A binder has been assembled for handover and no one has checked it against source.
- An accepting party is reviewing the binder and discrepancies are surfacing tab by tab.
- A discrepancy register lists items whose closure evidence is not in the binder.
- A tight redelivery window leaves no time for the binder to bounce during acceptance.
The problem
A redelivery binder is built to a contractual index, and the index tends to get ahead of the records that back it. A records team handing over a CFM56 finds tabs that promise a certificate or a status report the binder does not actually contain, and the accepting party discovers each shortfall as they work through the index. The binder presents as complete while individual tabs point at records that are missing or do not match.
What gets reviewed
- The binder index checked against the documents actually filed behind each tab
- Acceptance evidence reconciled to the source records it summarizes
- The discrepancy register read against the closure evidence in the binder
- Status reports in the binder tied back to release and shop records
- Cross-references between tabs checked for consistency
- A residual list of tabs pointing at records that are missing or unsupported
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
- Every tab in the index has the document it names filed behind it
- Acceptance evidence in the binder reconciles to the underlying source records
- Each item on the discrepancy register has matching closure evidence in the binder
- Status figures in the binder agree with the release and shop records they derive from
- Cross-referenced tabs point at each other consistently without dead references
Evidence normally required
- The redelivery binder and its contractual index
- The acceptance evidence and discrepancy register for the handover
- Release certificates and shop records the binder summarizes
- Current AD, Service Bulletin, and LLP status reports for the engine
- The delivery conditions or records standard the binder is built to
Common discrepancies
- A tab named in the index with no document filed behind it
- A discrepancy shown closed on the register with no evidence in the binder
- A status figure in the binder that does not match the release records it cites
- A cross-reference pointing to a tab that does not exist
What is at stake
A binder that fails acceptance stalls the redelivery and puts the returning party back into records work under the clock, often with a counterparty applying penalties or holding the aircraft. Discrepancies found late are the most expensive to close, because the evidence has to be chased after the engine has already moved rather than while it was still in hand.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Check every tab against the document actually filed behind it and note the gaps.
Reconcile to source
Tie acceptance evidence and status figures back to the release and shop records.
Work the register
Match each discrepancy to its closure evidence or flag it as unsupported.
Report before handover
Deliver the marked index and a plan for the tabs that would stall acceptance.
What the buyer receives
- A marked binder index showing each tab as complete or open
- A note on each discrepancy tying it to closure evidence or flagging the gap
- A closure plan for the tabs that would hold up acceptance
Who uses the output
- Lessors and records teams handing over the engine against a contractual index
- Accepting parties confirming the binder matches source before signing
- Asset managers who need the redelivery not to slip on a records shortfall
How the work fits into the transaction or program
The binder review is where the individual evidence checks come together, because the binder pulls the equipment list, repairs, deferrals, and status into one contractual package. Verifying it against source is the last gate before handover, and the earlier reviews feed the tabs it depends on so the binder can be tested rather than assembled on faith.
Aircraft-specific considerations
A CFM56 redelivery binder collects module build records, disk sheets, shop-visit releases, and installation history from a very large installed base, and an engine returning after years on wing carries records assembled by more than one operator. The wide fleet means contractual indexes and delivery conditions vary between counterparties, so a binder built to one lessor's standard rarely maps cleanly to the next holder's expectations.
Regulatory limits
The review reports whether the binder matches the source records and the delivery conditions it is built to. It does not certify the engine for acceptance, make an airworthiness determination, or bind either party to a contractual outcome, and acceptance remains the receiving party's decision.
What this review does not cover
- Signing off acceptance on behalf of either party
- Renegotiating the delivery conditions or the records standard
- Producing missing source records that do not exist
Specific to this review
- A CFM56 redelivery binder is built to a contractual index that runs ahead of the records, so tabs commonly promise documents the binder does not hold.
- Discrepancies surface one tab at a time during acceptance, which is why testing the whole index against source up front is what prevents a bounce.
- Because delivery conditions differ between counterparties, a binder acceptable at one return often needs rework to satisfy the next accepting party.
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.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Should we run this before or during acceptance?
Before. The point is to find and close the shortfalls while the engine and its records are still in hand. Running it during acceptance means every gap becomes a discrepancy the counterparty raises, which is slower and costlier to fix.
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.