Repair substantiation
Structural repair records supported from the engine-module file
This review takes the structural repair map and asks the file to prove every entry on it. Lessors, operators, and records leads use it when repairs to cases, mounts, and nacelle structure recorded against the engine must stand up at transfer or audit. Each mapped repair is traced to the shop record that performed it, the data or approval basis that authorized it, and any inspection or life limitation it created. Entries the file cannot carry, and repairs the file shows that the map omits, are both returned as exceptions.
When this review is needed
- A repair map compiled by a previous custodian is being adopted without its underlying records having been read.
- A mapped repair is near a limit or threshold and its basis must be produced.
- Shop findings from past visits mention rework the map never picked up.
- Transfer conditions require repairs to be within published data or carry specific approval evidence.
The problem
Repair maps summarize decades of work into a drawing and a table, and the summary outlives its sources. The record that performed a weld repair sits in a visit package three custodians back, the approval basis was a data reference nobody copied forward, and the recurring inspection the repair created may or may not have made it into the program. The map keeps asserting all of it regardless.
What gets reviewed
- Every map entry traced to the originating repair record and visit
- Approval basis identified per repair, from published manual data through specific approvals
- Repairs checked against the limits of the data they cite, including size, location, and proximity rules
- Inspection and life obligations created by repairs followed into the program records
- Shop findings and visit records swept for rework the map does not show
- Repair interactions reviewed where multiple repairs share structure
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 a repair record that exists in the file with matching location and description
- The approval basis cited is appropriate to the repair as performed, within its published or approved limits
- Recurring inspections created by repairs appear on the maintenance program with correct intervals
- No rework described in shop findings is absent from the map
- Repairs performed outside published data carry their specific approval evidence
Evidence normally required
- The structural repair map or equivalent register
- Repair records and shop-visit packages for the mapped entries
- The data references cited, at applicable revisions
- Program records showing repair-driven inspection tasks
- Findings reports from past visits for the omission sweep
Common discrepancies
- Mapped repairs whose performing record cannot be located in the package it should occupy
- A repair executed at the edge of published limits with no record of the required assessment
- Repair-generated inspections that never entered the program, leaving the obligation untracked
- Rework noted in findings narratives, invisible on the map because it closed under a routine card
What is at stake
A repair without a producible basis gets treated as an unapproved repair, whatever its true history, and the cures are expensive: re-substantiation engineering, added inspections, or rework of sound structure. Omitted repairs are worse, because a counterparty who finds an unmapped repair stops trusting the map entirely.
How the work runs
Inventory the map
List every entry with its claimed record, basis, and obligations.
Pull the sources
Locate the performing records and cited data for each entry.
Sweep for omissions
Read findings and visit records for structural work the map lacks.
Table the results
Deliver substantiation status, exceptions, and the obligations schedule.
What the buyer receives
- A substantiation table across the map, entry by entry
- Trace-file exception entries, split between unsupported map entries and omissions
- An obligations schedule for repair-driven inspections needing program capture
Who uses the output
- Records leads defending the map at transfer
- Engineering staff assessing repairs near limits or slated for future work
- Lessor reviewers pricing repair status in a transaction
How the work fits into the transaction or program
The repair map is a derived document, so this review reaches back into the same shop-visit and findings evidence other reviews use, but reads it for a different question: what was done to the structure and on what authority. Its obligations schedule feeds the program review, and its omission sweep often triggers non-routine follow-ups.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
On the FAA side, repair data must qualify as approved or acceptable per 14 CFR Part 43, and the major-versus-minor classification of each repair shapes the evidence required. EASA repairs trace to approved data under the design and continuing-airworthiness regulations, 748/2012 and 1321/2014 respectively. The same physical repair can be documented to different standards depending on which regime governed at the time, so entries are judged against the regime in force when the work was done.
Regulatory limits
The review substantiates documentation; it does not approve repairs, perform damage assessments, or clear structure for continued service. Where an entry lacks a basis, the deliverable states the gap, and the engineering and airworthiness decisions that follow belong to the responsible organizations.
What this review does not cover
- NDT or any physical examination of repaired structure
- New repair design or substantiation engineering
- Major-versus-minor classification decisions on behalf of the operator
Specific to this review
- Omissions concentrate in rework closed under routine task cards, since maps are usually populated from non-routines alone.
- The proximity of two individually acceptable repairs can itself exceed data limits, and only a map-level read catches it.
- Basis citations by page and paragraph go stale as manuals revise; each must be read against the revision current when the repair was done.
- Maps redrawn during custodian changes are prone to transcription loss, and the redraw date is worth checking against the exceptions found.
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 map came from the previous lessor's acceptance. Hasn't it already been checked?
Acceptance reviews confirm a map exists and looks reasonable; they rarely pull every performing record and basis document. Each transfer also adds a copying step, and maps degrade in transcription. Adopting a map without reading its sources adopts its accumulated errors as your own.
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.