Skip to content

Delivery & redelivery binder

De Havilland Dash 8 delivery and redelivery binder records review

This review checks that a Dash 8's delivery or redelivery binder is complete, indexed, and backed by source records rather than assertions. It is run for a lessor, operator, or manager preparing or accepting a binder at a lease transition, ahead of the acceptance milestone. It tests each index tab against the document behind it, confirms the acceptance evidence and discrepancy register are consistent, and checks that what the binder claims matches the underlying status records. You receive a supported exception list, a source map from each binder tab to its evidence, and a closure plan for tabs that point to missing or inconsistent records.

When this review is needed

  • A Dash 8 is being redelivered at lease end and the binder must survive the receiving party's review.
  • A lessor is accepting a returned aircraft and needs the binder verified against the lease conditions.
  • A prior transition left discrepancies open and the binder has to reconcile them before acceptance.
  • The binder index was built quickly and its tabs may not all point to real documents.

The problem

A redelivery binder is the assembled proof that a lease's technical conditions were met, and it is where every earlier records shortcut comes due. On a Dash 8 transitioned under deadline, the index gets built faster than the documents behind it are verified, so a tab can promise a release certificate or a status list that the binder does not actually contain. The receiving party works the binder tab by tab, and every tab that resolves to a missing or inconsistent document becomes a discrepancy that holds the acceptance.

What gets reviewed

  • Each binder index tab tested against the document it claims to contain
  • Acceptance evidence reconciled to the lease's technical redelivery conditions
  • The discrepancy register checked for completeness and consistency with the records
  • Status lists in the binder reconciled to the underlying AD, life-limited, and maintenance records
  • Release and airworthiness documents confirmed present and legible where the binder cites them
  • Open items carried into the binder and whether each is dispositioned

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 tab resolves to a document that is actually present and legible in the binder
  • Acceptance evidence maps to the specific redelivery conditions it is meant to satisfy
  • The discrepancy register reflects the same open items the underlying records reveal
  • Status lists in the binder reconcile to the source status records they summarize
  • Each open item in the binder carries a disposition rather than being left unresolved

Evidence normally required

  • The delivery or redelivery binder and its index
  • The lease technical conditions or redelivery specification
  • The discrepancy register and open-item list
  • The underlying AD, life-limited, and maintenance status records
  • Release certificates and airworthiness documents cited in the binder

Common discrepancies

  • An index tab that points to a document the binder does not actually contain
  • A status list in the binder that does not reconcile to its source record
  • A discrepancy the underlying records show but the register omits
  • An open item carried into the binder with no disposition against the lease conditions

What is at stake

A binder that does not hold up at acceptance stalls the redelivery, extends the lease exposure, and shifts leverage to whichever party is not under schedule pressure. A discrepancy discovered by the receiving side, rather than disclosed by the delivering side, carries more weight and less explanation, and reconstructing a source document after the aircraft has moved is far harder than closing the tab before handover.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Test the index

Check each binder tab against the document it claims to hold for presence and legibility.

02

Reconcile to conditions

Map acceptance evidence to the specific redelivery conditions it must satisfy.

03

Check the register

Confirm the discrepancy register matches the open items the records reveal.

04

Close before handover

List missing documents and undispositioned items with a path to close each.

What the buyer receives

  • A supported exception list of tabs and items that fail against the binder index
  • A source map linking each binder tab to the record that backs it
  • A closure plan for missing documents and undispositioned open items before acceptance

Who uses the output

  • Records teams assembling a binder that will survive the receiving party's review
  • Asset managers confirming redelivery conditions are met before the acceptance milestone
  • Transaction teams closing discrepancies while the delivering side still holds leverage

How the work fits into the transaction or program

The binder is the endpoint that draws on every record set reconciled earlier: AD, life-limited, modification, structural, and deferral status all land in its tabs. Reviewing it after those records are verified means each tab is tested against evidence already confirmed, so the binder review catches assembly and index errors rather than re-litigating the status itself.

Aircraft-specific considerations

Dash 8 aircraft transition between regional operators frequently, so a given airframe accumulates a stack of prior delivery and redelivery binders, and each transition binder should reconcile to the last. High-cycle histories and multiple operators mean the underlying status the binder summarizes is long and detailed, which is exactly where a hastily built index diverges from the documents it points to on this family.

Jurisdiction-specific considerations

A Dash 8 redelivered across FAA and EASA operators has to present acceptance evidence in the form the receiving system expects, and a binder built to one authority's conventions may need reformatting for the other. The review notes where a binder tab's document will need supplementing to satisfy the receiving party's register.

Regulatory limits

The review verifies that the binder is complete and reconciles to the underlying records. It does not accept the aircraft on the receiving party's behalf, determine that redelivery conditions are legally satisfied, or make an airworthiness determination.

What this review does not cover

  • Accepting or rejecting the aircraft on any party's behalf
  • Negotiating the lease redelivery conditions or their disposition
  • Any airworthiness ruling on the aircraft or physical survey at handover

Specific to this review

  • The binder is where earlier records shortcuts come due, because every tab is tested against a real document at acceptance.
  • A discrepancy the delivering side discloses is worth more than the same one the receiving side finds, since disclosure preserves leverage.
  • Index tabs are built faster than the documents behind them are verified, so tabs pointing to absent records are the signature finding at redelivery.

Sources

Frequently asked questions

Should the delivering side run this before or after building the binder?

During assembly and again before handover. Testing the index against the actual documents as the binder is built catches missing tabs early, and a final pass before the acceptance milestone closes discrepancies while the delivering side still controls the timeline.

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.