Binder assembly
Delivery and redelivery binder records built from the shop-visit file
Shops assembling a delivery or redelivery binder work from an index agreed with the operator or lessor, and the binder's value depends on every indexed record actually being present, current, and sourced. This review audits the binder index against the shop-visit source package line by line. It runs during closeout, before the binder ships with the aircraft. Indexed records that are missing, superseded, or unsupported by the package come back as an exception list the shop can cure on site.
When this review is needed
- A lease redelivery follows the shop visit and the binder is a condition of acceptance.
- The binder index was agreed months earlier and the visit has since changed what the records should show.
- Sections of the binder were populated from operator archives and shop output in parallel, with no one reconciling them.
- The receiving party's records team will audit the binder on delivery day.
The problem
Binder assembly is a copying exercise performed under delivery pressure, usually by whoever is available in the final week. The index says what should sit behind each tab; the assembler pulls the nearest matching document. A status list one revision old, a work report missing its attachments, a certificate filed under the wrong tab: each is a small error, and a delivery binder accumulates dozens of them. The receiving team finds them one by one, and each becomes a delivery-day discussion.
What gets reviewed
- Every index line checked for a present, legible, complete document behind its tab
- Document revisions and dates verified current against the visit's closing records
- Binder contents cross-checked to the source package so each record has a supported origin
- Certificates and releases confirmed as executed copies rather than drafts or blanks
- Attachments and continuation sheets verified where the indexed document references them
- Index structure compared with the agreed redelivery or delivery standard
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
- No indexed record is absent, and no substantial record in the package is unindexed
- Each status list in the binder carries the latest revision issued during the visit
- Executed signatures and certificate numbers appear where the index promises certified documents
- Multi-part records include every referenced attachment, never the lead sheet alone
- Binder dates are internally consistent with the visit timeline and the closing work report
Evidence normally required
- The agreed binder index or delivery records standard
- The assembled binder, physical or electronic
- The shop-visit source package as the origin for visit-generated records
- Status lists and reports at their final closeout revisions
Common discrepancies
- Tabs filled with the pre-visit revision of a list the visit updated
- Index lines pointing at records the visit was expected to generate but did not
- Lead pages present with attachments missing, especially for test data and work reports
- Documents in the binder that contradict the source package they were copied from
What is at stake
A binder that fails audit at delivery converts a records problem into a commercial one, with acceptance, rent, and redelivery conditions in play. Documents that were current in the shop become hard to regenerate afterward, since the source package gets archived and the visit team disbands. Worse, a binder accepted with quiet defects seeds the next transaction's disputes, because the binder is what the following operator inherits as truth.
How the work runs
Confirm the standard
Establish the governing index or records standard, including any changes agreed during the visit.
Audit every tab
Verify presence, revision, execution, and completeness of each indexed record.
Trace to source
Check binder contents back to the source package and flag contradictions.
Cure and certify
Issue the exception and pull lists, then record binder condition once corrections land.
What the buyer receives
- A tab-by-tab exception list against the agreed index
- A pull list of source-package documents that cure each exception
- A completion statement describing binder condition at the review date, for the delivery file
Who uses the output
- Records staff completing the binder before the aircraft repositions
- Lessor and operator delivery teams planning the acceptance audit
- Program managers tracking binder completion as a delivery milestone
How the work fits into the transaction or program
The binder outlives the shop visit; it is the artifact the next operator, auditor, and buyer will actually read. Auditing it against the source package during closeout is the one time both exist in the same place, which turns delivery-day findings into shop-floor corrections a week earlier.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Binder content expectations blend regulation and contract: 91.417 and 91.419 shape what records transfer with a US-registered aircraft, while EU 1321/2014 defines the continuing-airworthiness records an EASA-regime operator must receive. The agreed index usually exceeds both, and the review tests against the index while noting where regulatory minima would also fail.
Regulatory limits
The review reports binder completeness and consistency with the source package. It does not certify records, accept the aircraft, interpret lease terms, or determine airworthiness; the delivery parties retain those judgments.
What this review does not cover
- Negotiating the binder index or the redelivery conditions behind it
- Recreating operator records that predate the shop visit
- Physical delivery inspection of the aircraft
Specific to this review
- Binder defects cluster in the final assembly week, when the index is old and the assembler is new.
- Revision errors dominate: the document behind the tab is real and executed, just one issue behind the version the visit produced.
- Electronic binders fail differently from paper ones, mostly through broken internal references and files that open but fail to match their index title.
- A completion statement dated at closeout gives the delivery team a fixed reference point when contents are questioned weeks later.
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 is electronic. Does the review change?
The tests are the same; the failure modes shift. Electronic binders add checks for file integrity, index hyperlinks, and title-to-content matches, and they make revision errors easier to introduce because replacing a file leaves no physical trace.
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.