Redelivery preparation
Delivery and redelivery binder review against engine-module sources
A delivery or redelivery binder is only as good as its index, and the index is only as good as the documents behind it. This review walks the binder index for an engine or module line by line and confirms that each listed record exists in the source file, is the current revision, and is supported by build sheets, disk sheets, shop findings, test-cell data, or installation history as appropriate. It is run before the binder goes to the lessor, buyer, or next operator. The engine records lead gets a per-line exception report separating missing documents from stale ones and from entries with no source support at all.
When this review is needed
- A lease is ending and the redelivery conditions specify a binder the lessor's team will audit on receipt.
- An engine is being delivered onto a new lease and the binder must present years of scattered shop history as one ordered file.
- The binder was assembled from a legacy index and nobody has confirmed the listed documents still exist at the listed locations.
- Redelivery negotiations are near and the operator wants to find the binder's weak lines before the lessor does.
The problem
Binder assembly is a copying exercise under time pressure: an index template gets filled from whatever the records system offers, and lines get carried forward from the last transaction's binder without anyone re-pulling the documents. Engines make this worse than airframes because module swaps and off-wing shop visits fragment the history across packages held in different places. An index line can look complete while pointing at a superseded status page or at a document that was never returned by the shop.
What gets reviewed
- Every index line checked for a corresponding document physically or digitally present in the file
- Listed revisions and dates compared with the latest versions the source file holds
- Binder status summaries reconciled to LLP status pages, disk sheets, and build sheets
- Shop-visit documents in the binder matched to the visits the installation history implies
- Required-at-redelivery items from the lease checked for presence, none assumed
- Duplicates, superseded copies, and orphaned documents in the binder identified for removal or explanation
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 index entry resolves to one specific document, at the stated location, at the stated revision
- Status documents in the binder carry dates consistent with the redelivery or delivery measurement point
- Every shop visit evidenced in the installation history has its package represented in the binder
- Lease-required items appear in the binder itself rather than only in the wider records file
- No binder line depends on a document the source file shows as superseded or withdrawn
Evidence normally required
- The draft binder and its index, plus the lease's redelivery or delivery records requirements
- The engine-module records file with shop-visit packages and build sheets
- LLP status pages and disk sheets current at the measurement date
- Installation and removal history for the engine and modules
Common discrepancies
- Index lines inherited from a prior transaction that point to documents never carried into this file
- A status page in the binder one revision behind the page the records system holds
- A shop visit visible in the installation history with no package represented in the binder at all
- Lease-required certificates present in the archive but never pulled into the binder itself
What is at stake
A lessor's inspector who finds three bad index lines stops trusting the index and starts auditing the whole binder, which converts a scheduled acceptance into an open-ended review. Redelivery disputes over binder completeness routinely outlast the lease itself, and each unresolved line becomes a holdback argument. On delivery into a new lease, a weak binder sets the baseline the operator will be measured against at the next return.
How the work runs
Set the measurement point
Confirm the date and configuration the binder must represent under the lease or sale terms.
Walk the index
Resolve every index line to its document and compare revision, date, and content against the source file.
Cross-check the history
Work backward from installation history and shop visits to catch documents the index never listed.
Issue the punch list
Deliver the exception report and the pull list so the binder can be corrected before handover.
What the buyer receives
- A line-by-line exception report against the binder index, sorted by severity
- A reconciliation of binder status summaries to the underlying source figures
- A punch list of documents to pull, replace, or explain before handover
- A verified index the acceptance team can sign against
Who uses the output
- Records teams finalizing the binder before the lessor or buyer sees it
- Redelivery managers negotiating condition compliance with a defensible index
- Receiving operators or lessors using the verified index as their acceptance baseline
How the work fits into the transaction or program
The binder review is the last documentary gate before an engine changes hands. It draws on the same source file as the deeper single-topic reviews, such as LLP trace or shop-visit reconciliation, and it often triggers them: a binder line that fails here becomes the entry point for a focused source review of that evidence type.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Leases written under different legal traditions specify binders differently, but the regulatory floor comes from 14 CFR 91.417 and 91.419 on the FAA side and Regulation 1321/2014 on the EASA side, which govern what records must transfer with the asset. A binder that satisfies the lease can still fall short of the receiving authority's transfer expectations, so the review reads the index against both the contract list and the applicable regulation.
Regulatory limits
This is a documentary verification of the binder against its sources. It does not certify the engine's condition, does not determine airworthiness, does not adjudicate lease disputes, and does not release the operator from any redelivery condition. Whether a binder satisfies the lease remains a matter between the parties.
What this review does not cover
- Physical inspection or borescope of the engine at redelivery
- Commercial negotiation of redelivery conditions or holdbacks
- Assembly of the binder from scratch, which is a separate build effort
Specific to this review
- Binder indexes inherit errors generationally: a line that entered the index two leases ago can survive every subsequent transaction unchecked.
- The measurement date matters more than the handover date, because status documents in the binder must be consistent with the point the lease defines, and the two dates rarely coincide.
- Off-wing shop visits are the classic binder gap, since their packages return to whoever commissioned the visit, which is not always the party building the binder.
- Acceptance teams audit the index before the documents, so a clean index with honest exceptions reads better than a padded binder with silent holes.
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
We built the binder from our records system. Why would the index be wrong?
Because the system's index and the physical or scanned file drift apart over time. Documents get superseded, shop packages arrive after indexing, and module swaps reassign history between serial numbers. The review checks the binder against the documents as they exist now, which is what the acceptance team will do.
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.