Redelivery binder
Boeing 737NG delivery and redelivery binder records review
This review works through the delivery and redelivery binder assembled for a Boeing 737NG and confirms the binder index actually resolves to the documents it lists. It runs at a lease transition, run by or for the party accepting or handing back the aircraft. It covers the binder index, the acceptance evidence, the discrepancy register carried into or out of the transfer, and the source-record references each index line points to. You receive an exception list against the index, a map from index line to source document, and a closure plan for the entries that will not stand up at acceptance.
When this review is needed
- A 737NG is being handed back and the binder has to satisfy the lease agreement's return conditions.
- The receiving operator is assembling an acceptance package and needs the incoming binder verified first.
- A prior redelivery left open discrepancies that were carried into the current binder without closure.
- The binder index was rebuilt from a scan set and no one has confirmed the links still resolve.
The problem
A redelivery binder is judged at the acceptance table under time pressure, and its index promises far more than a quick check can confirm. On a 737NG that has redelivered before, the binder tends to inherit the last transition's structure, so index lines point at documents that moved, were superseded, or never made it into this copy. The discrepancy register that should reconcile open items against the lease conditions often lags the actual state of the file.
What gets reviewed
- The binder index checked line by line against the documents actually present
- Acceptance and conformity evidence for the events the binder claims
- The discrepancy register reconciled to the lease's return conditions
- Source-record references behind each index entry confirmed retrievable
- Superseded or duplicate documents identified so no two entries conflict
- Open items carried from a prior redelivery flagged for closure
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 legible document that is in the binder, not merely named by it
- Acceptance evidence matches the event and configuration the binder asserts
- The discrepancy register reflects the same open items the record set actually shows
- Source references point to retrievable originals rather than to another summary
- No index entry is satisfied by a superseded or duplicate copy of a document
Evidence normally required
- The complete delivery and redelivery binder with its index
- The lease agreement return conditions the binder must satisfy
- The discrepancy or open-items register for the transfer
- The underlying record sets the binder draws from
- Any prior redelivery binder the current one inherited structure from
Common discrepancies
- An index line naming a document that is absent from this copy of the binder
- An acceptance certificate that references a configuration the file no longer matches
- A discrepancy listed as open in the register that the records show was closed, or the reverse
- A source reference that resolves to a summary rather than the original release document
What is at stake
An index that does not resolve turns acceptance into a document hunt across the table, which stalls the handover and gives the accepting party grounds to reject or condition the transfer. Discrepancies that were supposed to close before return but were only listed become the new owner's problem the moment the aircraft changes hands.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the index against the copy
Walk every index line and confirm the named document is present and legible in this binder.
Test acceptance and discrepancies
Check acceptance evidence and reconcile the discrepancy register to the return conditions.
Resolve the references
Confirm each source reference reaches a retrievable original, not another summary.
Deliver exceptions and closure
Report the index exceptions with a plan to close them before acceptance.
What the buyer receives
- An exception list keyed to the binder index and the return conditions
- A source map linking each index line to its retrievable document
- A closure plan for the discrepancies and missing references before acceptance
Who uses the output
- Asset managers deciding whether the binder will pass the acceptance table
- Records teams rebuilding the index so every line resolves
- Transition leads reconciling the discrepancy register to the lease conditions
How the work fits into the transaction or program
The binder is the artifact the transition is judged by, and it sits on top of the status and release records the aircraft carries. This review confirms the binder faithfully represents those records before acceptance, so the exception list drives closure while there is still leverage and the accepting party is not the one to find the gaps.
Aircraft-specific considerations
A 737NG binder usually reflects more than one prior transition, so it carries structural repair mapping, cabin and avionics STC records, and engine and APU histories assembled to whatever standard the last redelivery used. Where the current lease conditions differ from that standard, the index tends to be complete against the old template and short against the new one.
Jurisdiction-specific considerations
A 737NG redelivering across an FAA and EASA boundary needs the binder to carry release evidence in the form the receiving side accepts, so dual-release status and authority-specific acceptance documents are checked rather than assumed to carry over.
Regulatory limits
This review verifies that the binder represents the underlying records and satisfies the stated return conditions. It does not accept the aircraft on any party's behalf, warrant airworthiness, or issue any approval or release.
What this review does not cover
- Conducting the physical acceptance or handover inspection
- Negotiating the lease return conditions or which items are accepted
- Issuing any release or airworthiness statement
Specific to this review
- A binder index is a promise, not evidence: the failure mode is a line that names a document the copy does not contain.
- Binders inherit the prior transition's structure, so they are often complete against the last lease's standard and short against the current one.
- A discrepancy register that lags the file is worse than no register, because it gives false comfort at the acceptance table.
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 came with an index already. Why re-check it?
An index tells you what should be in the binder, not what is. On a tail that has redelivered before, the index often reflects an earlier assembly, so lines point to documents that moved or were superseded. Checking each line against the actual copy is what keeps acceptance from turning into a search.
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.