Delivery and redelivery binder
Boeing 737 MAX delivery and redelivery binder records review
A Boeing 737 MAX redelivery-binder review confirms the binder index resolves to the documents behind it and that acceptance evidence and the discrepancy register are complete before handover. It is run by or for a party delivering or accepting a specific tail. Binder indexes, acceptance evidence, discrepancy registers, and the source-record references are reconciled so an index line points to a document that exists and every discrepancy is either closed or carried explicitly. You receive a supported exception list of index lines that do not resolve, a source map across the binder, and a plan to complete the package before the handover date.
When this review is needed
- A lease is ending and the redelivery binder has to satisfy the return conditions before the handover date.
- A binder index line points to a document the binder does not actually contain.
- A discrepancy raised during acceptance is open in the register with no closure or carried basis.
- An incoming party is accepting the binder and needs its index confirmed against the documents.
The problem
The redelivery binder is where the whole records story is assembled for handover, and it is judged against the return conditions and the acceptance checklist under a firm date. An index line can promise a document the binder does not hold, an acceptance item can be signed without the evidence behind it, and a discrepancy raised during the acceptance walk can sit open in the register with no closure or carried basis. Assembling all of this against the handover clock, with the counterparty watching, is where redeliveries slip.
What gets reviewed
- The binder index reconciled so each line resolves to a document the binder contains
- Acceptance evidence confirmed present for each item the checklist requires
- The discrepancy register checked so every item is closed or carried with a basis
- Source-record references confirmed to point to retrievable documents
- The binder measured against the return conditions and acceptance checklist
- Superseded or duplicate documents removed so no two references contradict
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 actually present in the binder
- Each acceptance-checklist item has the evidence the checklist requires
- Every discrepancy in the register is either closed with evidence or carried with a stated basis
- Source references point to retrievable, legible documents rather than image-only fragments
- The binder satisfies the return conditions the lease sets for redelivery
Evidence normally required
- The delivery or redelivery binder and its index
- The lease return conditions and the acceptance checklist
- The discrepancy register from the acceptance walk
- The source records the binder references
- Any prior audit findings on the asset's records
Common discrepancies
- An index line pointing to a document the binder does not contain
- An acceptance item signed without the supporting evidence behind it
- An open discrepancy in the register with no closure or carried basis
- A duplicated or superseded reference that contradicts another in the binder
What is at stake
A binder whose index does not resolve forces the accepting party to hunt for documents, which reads as a disorganized asset and slows the handover past its window. An open discrepancy with no closure or carried basis becomes a dispute at handover, and a missing acceptance item can hold the redelivery until it is produced, all against a date the lease depends on.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Test the index
Confirm every index line resolves to a document the binder actually contains.
Check acceptance evidence
Match each acceptance-checklist item to the evidence it requires.
Reconcile the register
Confirm every discrepancy is closed with evidence or carried with a stated basis.
Measure against return conditions
Check the completed binder against the lease return conditions before handover.
What the buyer receives
- A supported exception list of index lines and acceptance items that do not resolve
- A source map showing how the binder reconciles to its underlying records
- A plan to complete the binder and close or carry each discrepancy before handover
Who uses the output
- Records teams assembling the binder to the return conditions before handover
- Accepting parties confirming the index resolves before they take the aircraft
- Asset managers tracking which discrepancies are closed and which still carry exposure
How the work fits into the transaction or program
The redelivery-binder review is the last records pass before handover, drawing together the status, configuration, and discrepancy work the earlier reviews produced into one package judged against the return conditions. Its exception list drives the final completion work, and a discrepancy that cannot close feeds a carried basis the counterparties agree to before the date.
Aircraft-specific considerations
The 737 MAX carries configuration, software, and avionics evidence that a redelivery binder has to present cleanly, so the acceptance checklist for this family gives particular weight to the delivery-to-operator baseline and the modification embodiment that has to be reflected in the binder. Because the fleet is young, the binder for a given tail is often its first redelivery, which means the package is built from the full history rather than carried from a prior handover.
Jurisdiction-specific considerations
A binder assembled for an FAA-registered tail returning to a lessor who will place it on an EASA register has to anticipate the receiving system's expectations, so the review notes where a document acceptable for FAA recordkeeping will need supplementary evidence or reformatting for the next register.
Regulatory limits
The review reconciles the binder to its records and the return conditions. It does not accept the aircraft on a counterparty's behalf, waive a return condition, or make an airworthiness determination on the asset.
What this review does not cover
- Accepting or rejecting the aircraft on a counterparty's behalf
- Negotiating or waiving the lease return conditions
- Any airworthiness determination on the asset
Specific to this review
- A binder is judged against the return conditions and acceptance checklist, so an index that resolves internally still fails if it does not meet the conditions the lease sets.
- An open discrepancy carried with a stated basis is more defensible at handover than one left silent in the register, because the counterparty agrees to it before the date.
- Because the MAX fleet is young, a given tail's binder is often its first redelivery, so it is built from the whole history rather than inherited from a prior handover.
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
What happens to a discrepancy that cannot be closed before the handover date?
It is carried in the register with a stated basis and the residual exposure named, agreed between the parties before handover. That is more defensible than leaving it open and silent, because it becomes part of the accepted package rather than a surprise the accepting party finds after the date.
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.