GTF redelivery binder
Geared turbofan engine redelivery-binder records review
This review works through the redelivery binder assembled for a geared turbofan engine and tests whether its index, acceptance evidence, and discrepancy register actually resolve to the source records they cite. It is run at handback for the party redelivering the engine or the counterparty receiving it. The work confirms the binder index points to real documents, that acceptance evidence supports each claim, and that the discrepancy register captures what the file itself shows. You receive a supported exception list, a source map behind the index, and a closure plan for the specific engine being handed over.
When this review is needed
- A GTF engine is being redelivered and the binder has to satisfy the return conditions before handover completes.
- A receiving party wants the binder index reconciled to the actual documents before it accepts the engine.
- A discrepancy register was carried into redelivery and someone must confirm it reflects the whole file.
- The binder was compiled in stages by different hands and its internal consistency has never been checked.
The problem
A redelivery binder is compiled under deadline from whatever the engine's history left behind, and the index gets built faster than the documents behind it get verified. An index line that points to a certificate the binder does not contain reads as complete right until the receiving party opens the tab. On a GTF the binder also has to carry module and shop evidence that shifts with every visit, so a binder that matched the engine last quarter can already be stale.
What gets reviewed
- The binder index checked line by line against the documents actually filed
- Acceptance and return-condition evidence for the engine at handback
- The discrepancy register measured against what the binder itself reveals
- Source-record references followed to the certificates and reports they name
- Module and shop evidence current as of the redelivery date
- Duplicate or superseded documents that contradict the index
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 entry resolves to a document the binder actually contains
- Acceptance evidence supports each return-condition claim without a gap
- The discrepancy register lists every open item the file itself exposes
- Named source references match the part number and serial number they are filed against
- No two documents in the binder assert contradicting status for the same item
Evidence normally required
- The assembled redelivery binder and its index
- The lease or purchase return conditions the binder must meet
- The discrepancy or open-item register carried into redelivery
- Acceptance records and the most recent shop evidence
- Source certificates the index references
Common discrepancies
- An index line pointing to a release certificate the binder does not actually hold
- Return-condition claims accepted without the supporting acceptance evidence attached
- A discrepancy register that omits an open item the binder itself shows
- A superseded status report left in the binder alongside the current one
What is at stake
A binder whose index outruns its contents stalls handover while the missing documents are chased, often after the redelivery date the lease depends on. If the discrepancy register understates what the file actually shows, the receiving party inherits open items it never priced, and the leverage to have the redelivering party close them is already spent.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Check each index entry against the document the binder actually contains.
Test acceptance evidence
Confirm return-condition claims are backed by the acceptance records filed.
Reconcile the register
Measure the discrepancy register against every open item the binder reveals.
Close or carry
Sequence the failed lines into a plan to close before handover or track after.
What the buyer receives
- A supported exception list for every index line that fails to resolve
- A source map connecting the binder index to the records behind it
- A closure plan for the open items before or after handover completes
Who uses the output
- Redelivering parties closing the binder before the return date lands
- Receiving teams accepting the engine against a verified index
- Records teams reconciling the discrepancy register to the file
How the work fits into the transaction or program
The review runs at the redelivery gate, after the binder is compiled and before the counterparty signs. Its exception list drives the last round of document chasing while the redelivering party still holds the obligation, and the source map becomes the receiving party's starting index.
Aircraft-specific considerations
A geared turbofan cycles through modules and shop visits quickly, so its redelivery binder has to reflect a configuration that may have changed since the last status was pulled. The review checks that the binder's module build, LLP, and shop evidence match the engine as of the redelivery date rather than an earlier snapshot the index was first built against.
Jurisdiction-specific considerations
Return conditions written to an FAA basis and a binder assembled for an EASA receiving operator can call for different release paperwork on the same components. The review flags where the binder satisfies one system but leaves the other short, so the gap surfaces before handover rather than after.
Regulatory limits
The review confirms the binder is internally consistent and supported by its own source records. It does not certify the engine, accept the redelivery on any party's behalf, or make an airworthiness determination.
What this review does not cover
- Physical inspection or borescope of the engine at redelivery
- Negotiating which return conditions the counterparty will accept
- Any airworthiness determination on the engine
Specific to this review
- A binder index almost always finishes ahead of the documents it points to, so the failure mode is a tab that resolves to nothing.
- On a GTF the binder can go stale between compilation and handover because a module change moves the configuration underneath it.
- An understated discrepancy register transfers open items to the receiving party with the closing leverage already gone.
- A superseded status report left in the binder alongside the current one is a common contradiction that a hurried compilation misses.
- Return conditions written to one authority's basis can leave the binder short of the release paperwork the receiving operator's system expects.
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
We already have a discrepancy register. Why re-check it?
The register only helps if it reflects the whole binder. This review confirms it captures every open item the file itself exposes, so the receiving party is not accepting exposure that was never listed.
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.