Redelivery source review
Structural repair records reviewed against the redelivery binder source set
This review verifies that every repair on the structural repair map inside a redelivery binder is backed by the source evidence the binder claims to hold. It is run for the lessor or the returning operator during redelivery preparation, before the acceptance file is finalized. Each mapped repair is traced to its damage report, approved data, and inspection sign-off within the binder indexes, discrepancy registers, and return-condition evidence. The output is a repair-by-repair exception list that tells the asset manager which entries stand on evidence and which need documents recovered before handback.
When this review is needed
- The return-condition annex requires a complete structural repair map and the binder is being assembled against it.
- A repair found during the pre-return bridging check does not appear on the map the operator has been maintaining.
- The lessor's inspector has sampled the binder and asked for approval data behind specific dent and blend repairs.
- The aircraft changed operators mid-lease and the earlier repair history arrives as scanned fragments from another records system.
The problem
Repair maps drift from their evidence over a lease. Repairs accumulate at line stations, heavy checks, and third-party visits, each documented in a different place, while the map gets updated from memory and summaries. When the binder is assembled under a return deadline, a mapped repair without its drawing and an unmapped blend found on the airframe both stall acceptance, and the people who embodied the older repairs are long gone.
What gets reviewed
- Every entry on the structural repair map matched to a damage report, repair record, and inspection release in the binder
- Approval basis checked per repair: the SRM chapter and limits, or approved data where the repair exceeds them
- Repeat-inspection requirements from temporary or time-limited repairs traced into the maintenance evidence
- Discrepancy-register and return-condition findings reconciled against the map entries
- Doubler, blend, and skin-patch records checked for location, dimensions, and proximity to adjacent repairs
- Binder index rows for the structural section verified against the documents actually filed
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 mapped repair cites the SRM revision or approved-data reference that was current when the repair was embodied
- Repairs exceeding SRM limits carry a design approval, such as an FAA Form 8110-3 or a Part 21 design approval, rather than a work order alone
- Temporary repairs show a defined life or inspection interval and evidence that the interval has been controlled since embodiment
- Damage locations on the map agree with the dent and buckle chart and with any survey performed for the return
- Repairs recorded by prior operators or third-party checks are supported by records transferred into this binder, with the source noted
Evidence normally required
- The structural repair map or dent and buckle chart at its current revision
- The redelivery binder index and the structural repair section as filed
- Damage reports, repair work packages, and inspection sign-offs for mapped repairs
- Approved data referenced by repairs outside SRM limits
- The lease return-condition language covering structural repairs
Common discrepancies
- A mapped repair whose work package exists but whose approved-data reference was never filed into the binder
- A blend or doubler found during the return survey that no map entry or damage report accounts for
- A temporary repair carried for years without evidence that its repeat inspection was tracked
- Map entries copied forward through revisions with locations that no longer match the referenced damage reports
What is at stake
A repair that cannot show its approval basis becomes a negotiation item at return. Acceptance slips while documents are chased, holdover costs accrue, and where the basis truly cannot be produced, someone pays for engineering re-substantiation or a re-inspection. Unmapped structure discovered by the lessor's survey lands harder than the same finding raised by the operator a month earlier.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Index the structural section
List every map entry and every structural document filed in the binder, then match the two sets.
Trace each repair
Follow each mapped repair to its damage report, work package, approval basis, and inspection release.
Reconcile survey and register findings
Compare return-condition findings and discrepancy registers against the map to surface unmapped structure.
Issue the exception list
Deliver the annotated map and open-item list with a recovery path for each missing document.
What the buyer receives
- An annotated structural repair map marking each entry as supported, partially supported, or unsupported
- An exception list for the redelivery acceptance file with the missing document named for every open entry
- Recovery recommendations identifying which shop, operator, or archive most likely holds each missing record
Who uses the output
- Asset managers deciding what to accept, dispute, or price at redelivery
- The returning operator's records team, which must recover documents before handback
- The incoming operator's CAMO, which inherits the map as its structural baseline
How the work fits into the transaction or program
The structural section is usually the slowest part of a redelivery binder to settle because its evidence spans the entire lease and several performing organizations. This review sits between binder assembly and lessor acceptance: its exception list feeds the return negotiation, and the verified map becomes the structural starting point for the next operator's bridging work.
Jurisdiction-specific considerations
FAA and EASA both require repairs to rest on approved or accepted data, but the acceptable instruments differ. A repair substantiated through an FAA designee approval may need a fresh look before an EASA-registered incoming operator relies on it, and Part 21 design approvals arriving on an FAA-bound asset raise the mirror-image question. Entries whose approval basis will not transfer cleanly to the receiving registry are flagged separately from entries that are simply missing paper.
Regulatory limits
The review reports whether the binder's evidence supports each repair record. It does not approve repair data, classify repairs as major or minor on behalf of any authority, issue airworthiness determinations, or certify the structure as conforming. Those judgments remain with the operator, its CAMO, and the authority.
What this review does not cover
- Physical inspection of the airframe or non-destructive testing of repairs
- Engineering re-substantiation of repairs that lack approved data
- Negotiation of return-condition disputes between lessor and lessee
Specific to this review
- Outstation repairs are the most common source of unmapped structure at redelivery, because the paperwork often stayed in a station file instead of reaching the repair map.
- An SRM reference is only meaningful with its revision date; a repair within limits under an older revision can sit outside limits under the current one, which changes what evidence the acceptance file needs.
- Temporary repairs with repeat inspections generate two record trails, the repair itself and the recurring task, and either can break independently of the other.
- Return surveys routinely find blend-outs barely thicker than a paint coat that still require a map entry and a disposition record.
- The earlier a mapped-but-unsupported repair is identified, the better the odds that the performing shop still holds its retained copy of the work package.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The operator says a repair is within SRM limits, so no separate approval exists. Is that a finding?
Not by itself. A repair inside SRM limits is supported by the SRM chapter, the applicable revision, and the inspection sign-off. It becomes a finding when the map entry fails to cite the chapter and revision, or when the measurements in the work package show the damage was outside the stated limits after all.
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.