Handover packages
Delivery and redelivery binder review
A delivery and redelivery binder review is for lessors and operators presenting or accepting an aircraft handover binder at delivery or return. The trigger is a binder assembled and offered for sign-off. It walks the index, the section tabs, the status lists, and the component release sheets the binder claims to hold, then tests them against the source records they summarize. You receive a section-by-section completeness map and a list of items the index promises but the binder does not actually contain or support.
When this review is needed
- A handover binder has been built for a delivery and the team wants it checked before it is put in front of the other side.
- A return binder has been offered and the receiving party needs to know whether the tabs match what is filed behind them.
- A binder assembled under time pressure needs a completeness pass before anyone signs against it.
- An earlier handover left open binder items and the next transaction will reuse the same package.
The problem
A binder is an argument that the records are in order, presented as a tidy index and a row of tabs. The argument fails section by section when a tab is empty, a status sheet inside the binder disagrees with the source it summarizes, or a release named in the component list is simply not behind its divider. Under handover pressure the index gets trusted on its face, and the gaps surface only after sign-off, when they have already become someone's acceptance.
What gets reviewed
- The binder index against the documents physically present in each tabbed section
- Each status list inside the binder reconciled to the underlying source records it restates
- Authorized release certificates for every component the binder lists as installed
- Logbook and task-card sections for continuity across the period the binder covers
- The configuration the binder describes against the aircraft records it is drawn from
- Cross-references between sections, so an item cited in one tab is actually filed where it points
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 entry resolves to a document that is actually present in the binder
- Each status list in the binder agrees with the source documents it summarizes
- Release certificates are present for each component the binder lists as installed
- Logbook and task-card sections are continuous across the covered period with no dropped span
- Cross-references between tabs land on the document they name rather than a missing page
- The configuration stated in the binder is supported by the airframe records behind it
Evidence normally required
- The delivery or redelivery binder and its index
- Status lists for AD, Service Bulletin, modification, and components as bound
- Authorized release certificates for installed and replaced parts
- Airframe and component logbooks for the covered period
- The handover conditions or acceptance checklist the binder is built to satisfy
Common discrepancies
- Index entries that point to a section where the document is not actually filed
- A status list bound in the package that disagrees with its own source record
- Release certificates missing for components the binder lists as installed
- Logbook continuity broken across an operator or maintenance-program change
- A tab cited from another section that resolves to an empty divider
What is at stake
A binder accepted on a clean-looking index can hand the receiving party an incomplete package and the cost of rebuilding it. Missing releases and unreconciled status sheets become open items that travel into the next lease, and the leverage to make the presenting side complete them drops sharply once the handover is signed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Confirm every index and tab entry resolves to a document that is physically present in the binder.
Reconcile the bound status
Compare the status lists inside the binder to the source records they summarize and flag disagreements.
Check releases and continuity
Verify component releases are present and logbook and task-card sections run continuous across the covered period.
Map completeness
Produce a section-by-section map and an open-items list with a closure action for each gap before sign-off.
What the buyer receives
- A section-by-section completeness map of the binder against its index
- A list of referenced-but-missing or unsupported items by tab
- A recommended action for each gap so the binder can be completed before sign-off
Who uses the output
- Technical-records teams presenting the binder at handover
- Receiving asset and fleet teams deciding whether to accept the package
- Transaction stakeholders tracking open binder items to closure
How the work fits into the transaction or program
The review runs before the binder is signed, so the presenting side can fill empty tabs and reconcile status sheets while it still owns the obligation. Its output becomes the open-items list that governs whether the handover closes clean or carries conditions.
Aircraft-specific considerations
Binder structure follows the asset. An aircraft with separate engine and APU log sets, landing-gear records, and a long modification history needs more tabs and more cross-references, and each additional section is one more place an index entry can promise a document that is not filed behind it.
Jurisdiction-specific considerations
When the handover moves the asset between authorities, the binder has to carry releases and a configuration the receiving side accepts. A component sheet that reads complete under one authority is checked for whether its forms are acceptable where the aircraft is going.
Regulatory limits
This review confirms the binder is complete, internally consistent, and supported by its source records. It does not constitute technical acceptance, does not stand in for the receiving party's sign-off, and does not make any airworthiness determination.
What this review does not cover
- Technical acceptance or sign-off of the handover itself
- Assembling or rebuilding the binder from scratch
- Physical inspection of the aircraft at handover
Specific to this review
- A binder index can read as complete while the documents behind several tabs are absent, so each entry is checked against the contents rather than trusted on its face.
- Status sheets bound inside a binder are reconciled to their own source records, because a clean restatement does not prove the underlying documents support it.
- Cross-references between sections are followed to their target, since a citation that lands on an empty divider is a gap the index will not reveal.
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How is a binder review different from accepting the handover?
Acceptance is the receiving party's sign-off on the asset. The binder review is the check that the package actually holds and supports what its index claims, run early enough that the presenting side can still close the gaps.
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.