Delivery and redelivery
LEAP engine delivery and redelivery binder records review
This review tests whether a LEAP engine's delivery or redelivery binder actually contains what its index claims. It walks the binder index, the acceptance evidence, and the discrepancy register, confirming that each indexed line resolves to a real, legible source document rather than a placeholder. It is run for the party delivering or accepting the engine at a lease event. You receive a supported exception list of index-to-document mismatches, a source map behind the acceptance evidence, and a closure plan for the entries that will not survive the counterparty's review.
When this review is needed
- A LEAP engine is being redelivered and the binder has to satisfy the receiving party's acceptance checklist.
- A delivery binder was assembled quickly against a deadline and no one has verified the index against the documents.
- Acceptance is being contested because entries in the register point to evidence the binder does not contain.
- A prior redelivery was rejected on binder completeness and it has to be rebuilt before the next attempt.
The problem
A redelivery binder is judged by whether every promise in its index is met by a document behind the tab. On a LEAP engine assembled by more than one contributor, index lines drift ahead of the paper: a tab is listed, a discrepancy is marked resolved, an acceptance signature is referenced, and the underlying document is missing, illegible, or a superseded revision. The delivering party often does not see the gap until the receiving side works the index line by line.
What gets reviewed
- The binder index checked line by line against the documents actually filed behind each tab
- Acceptance evidence confirmed to name the engine and the event it is claimed for
- The discrepancy register reconciled to the resolutions the binder asserts
- Source-record references followed to legible, current-revision documents
- Duplicate or superseded documents identified where two tabs contradict each other
- The binder's coverage measured against the receiving party's acceptance checklist
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 index line resolves to a document that is present, legible, and the current revision
- Acceptance evidence names the same engine and event the binder is assembled for
- Each discrepancy shown resolved in the register has a supporting document behind the resolution
- No two tabs present contradictory versions of the same status or certificate
- The binder covers the items the receiving party's acceptance checklist will test
Evidence normally required
- The delivery or redelivery binder and its index
- The discrepancy register and any acceptance or handover certificates
- The receiving party's acceptance checklist or redelivery conditions
- Source documents referenced by the index: releases, status lists, and shop paper
- Findings from any prior redelivery attempt on this engine
Common discrepancies
- An index line pointing to a tab the binder does not actually contain
- A discrepancy marked resolved with no document behind the resolution
- An acceptance reference that names a different event or a different serial number
- A superseded status report filed alongside its replacement, so two tabs disagree
What is at stake
A binder whose index outruns its contents delays acceptance, invites a retrade at the redelivery table, or pushes the whole event past its window while both sides argue over missing tabs. Each unresolved discrepancy in the register becomes a condition on acceptance, and rebuilding the binder after a rejection costs more than assembling it correctly the first time.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Work the index
Check each index line against the document filed behind its tab or its digital link.
Confirm acceptance evidence
Verify acceptance and handover records name the correct engine and event.
Reconcile the register
Match each resolved discrepancy to the document that closes it and flag those without one.
Clear the exceptions
List the mismatches against the receiving checklist and plan the tab-by-tab closures.
What the buyer receives
- A supported exception list of index-to-document mismatches
- A source map behind the acceptance and discrepancy evidence
- A closure plan for the tabs that will not pass the counterparty's checklist
Who uses the output
- Asset managers approaching a redelivery table with a binder that has to hold
- Records teams assembling the binder to the receiving party's checklist
- Acceptance stakeholders confirming each register entry resolves to evidence
How the work fits into the transaction or program
The binder is the artifact the redelivery event turns on, sitting downstream of the status and release records that fill it. Verifying the index against the documents before the table means acceptance runs against a binder that matches its own promises, and the exception list drives the tab-by-tab fixes that clear the conditions on sign-off.
Aircraft-specific considerations
LEAP engine binders are increasingly compiled from digital indexing systems, so an index line may resolve to a scanned file or a system link rather than a physical tab. The review follows the reference into the digital set and confirms the linked file is the legible, current-revision document the index claims, because a broken or stale link reads as a complete index until someone opens it.
Jurisdiction-specific considerations
Acceptance conventions differ between an FAA and an EASA redelivery, particularly in which release forms and status statements the receiving party expects behind each tab. When the delivering and receiving sides sit on opposite sides of that line, the review notes where a binder built to one authority's habit needs an added or restated tab for the other.
Regulatory limits
The review confirms the binder's index matches its contents and that acceptance evidence is present. It does not accept the engine on any party's behalf, sign a redelivery certificate, or make an airworthiness determination on the asset.
What this review does not cover
- Signing or negotiating the acceptance or redelivery certificate
- Performing corrective maintenance behind a listed discrepancy
- Any airworthiness determination on the engine
Specific to this review
- A binder index is the most optimistic document in a redelivery, because lines get added as work is planned and rarely retracted when a tab fails to materialize.
- In a digital binder, a stale or broken link is the modern equivalent of a missing tab and looks complete until the file is opened.
- Superseded status reports filed next to their replacements cause more acceptance disputes than outright missing documents, because two tabs disagree and neither side can say which governs.
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
The binder index looks complete. Why check every tab against a document?
A complete-looking index is exactly what the receiving party will test line by line at the table. Lines get added as work is planned and are rarely pulled when a tab fails to appear, so the review opens each reference and confirms a legible, current document sits behind it before the counterparty finds the gap.
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.