Delivery & redelivery
Pilatus PC-12 delivery and redelivery binder records review
This review confirms that a Pilatus PC-12 delivery or redelivery binder is complete against its own index and that every claimed record is actually present and sourced. It suits a lessor, buyer, or manager accepting or handing back the aircraft who needs the binder to hold at delivery. The work checks the binder index, acceptance evidence, and discrepancy register against the source records for the single-engine turboprop. You receive an exception list of index lines that point nowhere and records that are present but unindexed, a source map behind the acceptance evidence, and a closure plan for the tail.
When this review is needed
- A PC-12 is being handed back at lease end and the redelivery binder has to be complete against its index.
- A buyer is accepting the aircraft and wants the delivery binder checked before signing.
- A prior handback left a discrepancy register whose items the binder does not clearly resolve.
- The binder index and the documents behind it were assembled by different parties and need reconciling.
The problem
A delivery or redelivery binder is the record that governs acceptance, so its index has to match the documents behind it exactly. In practice an index line can promise a certificate the binder does not hold, a document can be present without any index line to find it, and a discrepancy register can list items the acceptance evidence quietly leaves open. On an owner-managed PC-12 the binder is often assembled once, under handback pressure, by whoever has the file, and the gaps between index and content are exactly what the accepting party finds first.
What gets reviewed
- Every index line reconciled to the document it names in the binder
- Documents present in the binder confirmed to appear on the index
- Acceptance evidence checked against the delivery conditions it certifies
- The discrepancy register reconciled to what the binder shows as open or closed
- Source-record references behind status summaries confirmed retrievable
- Superseded or duplicate documents removed so the binder reads once and cleanly
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
- Each index line resolves to a document actually present in the binder
- Every document in the binder is findable through an index line
- Acceptance evidence supports each delivery condition it is offered against
- The discrepancy register agrees with the open and closed position the binder shows
- Status summaries in the binder point to retrievable source records, not to themselves
Evidence normally required
- The delivery or redelivery binder and its index
- The acceptance evidence and delivery-condition record
- The discrepancy register for the handover
- The source records the binder summarizes and references
- The lease or purchase delivery conditions the binder answers to
Common discrepancies
- An index line pointing to a document the binder does not contain
- A document present in the binder with no index line to locate it
- A discrepancy shown open in the register but treated as closed in acceptance evidence
- A status summary that references a source record the binder cannot produce
What is at stake
An index that points to documents the binder does not contain reads as an incomplete asset and slows or stalls acceptance. A discrepancy left open in the register but treated as closed in the acceptance evidence carries straight into the new holder's ownership, and a document present but unindexed may as well be missing until someone stumbles on it, usually after the leverage to demand it has gone.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Confirm each index line resolves to a document actually present in the binder.
Walk the contents
Check that every document in the binder is findable through the index.
Reconcile discrepancies
Match the discrepancy register to the open and closed position the binder shows.
Flag before acceptance
List index and content gaps and name the reconciliation needed before the delivery signs.
What the buyer receives
- An exception list of index lines without documents and documents without index lines
- A source map behind the acceptance evidence and status summaries
- A closure plan naming the document or reconciliation needed before acceptance
Who uses the output
- Lessors and buyers deciding whether the binder supports acceptance
- Asset teams holding the counterparty to the delivery conditions
- Records teams reconciling the index and content before handover
How the work fits into the transaction or program
The redelivery binder consolidates the AD, modification, deferred-maintenance, and airworthiness statuses settled elsewhere in the file into the record that governs acceptance. Reviewing it before handover means the accepting party finds a binder whose index and content already agree, rather than surfacing the gaps at the table when leverage has shifted.
Aircraft-specific considerations
PC-12 redeliveries are frequently handled by owner-managers rather than a dedicated records team, so the binder is often built once under handback pressure and the index tends to run ahead of the documents actually gathered. Because the aircraft's role changes drive a busy modification and equipment history, the review scopes the binder to this tail's specific delivery conditions rather than a fleet handback template.
Jurisdiction-specific considerations
Delivery conditions and the records a binder must present differ where an aircraft changes register at handover, so a PC-12 redelivered across an FAA and EASA boundary may need its binder re-mapped to the receiving system's expected content before acceptance.
Regulatory limits
The review confirms the binder is complete and traceable against its index and delivery conditions. It does not accept the aircraft, sign the delivery, or make an airworthiness determination on its behalf.
What this review does not cover
- Physical inspection or acceptance walk of the aircraft
- Signing or refusing the delivery on a party's behalf
- Any airworthiness determination at handover
Specific to this review
- The most common binder defect is an index that runs ahead of the documents actually gathered.
- A discrepancy shown open in the register but closed in the acceptance evidence is the gap that follows the aircraft into new ownership.
- A document present but unindexed is effectively missing until acceptance is over and the leverage to demand it has gone.
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
Is this the same as checking the underlying status records?
No. The binder review checks completeness and traceability against the index and delivery conditions, confirming each summary points to a retrievable source. The detailed AD, modification, and life-limited status is verified in its own review; the binder review makes sure that verified status is actually present and findable at handover.
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.