Repair substantiation
Structural repair records checked against a component-history source file
This review takes the structural repair map for a component or its host structure and asks, for each mapped repair, whether the source file holds what continued use depends on: the damage description, the repair data it was worked to, the approval basis, and any recurring-inspection obligation the repair created. Repairs found in shop reports but missing from the map are captured going the other way. The check is performed within a serialized-component trace review, and it produces a repair-by-repair substantiation table with unsupported entries flagged for recovery.
When this review is needed
- The repair map lists repairs by location only, and the dossiers behind several of them have never been assembled.
- A shop report describes structural rework that appears on no map anyone maintains.
- A repair worked outside the structural repair manual carries no visible approval basis in the file.
- Pre-sale review is approaching and repairs with repetitive-inspection requirements need their tracking status proven.
The problem
Structural repairs accumulate over decades and their documentation scatters as they do. The map records that something was repaired at a station and frame; the substantiation, the damage report, the deviation from the manual, the approval letter, the inspection interval, lives in whichever shop visit produced it. Years later the map is treated as the record, when it was only ever the index, and the dossiers it indexes were never consolidated.
What gets reviewed
- Every repair on the map within the component's structure or interfaces, indexed to its source shop visit
- Damage reports and dimensions matched to the repair described
- Repair data identified for each entry, whether structural repair manual, approved deviation, or designed repair
- Approval basis confirmed for repairs outside published manual limits
- Repetitive-inspection obligations extracted and checked against the maintenance program
- Shop-report narratives swept for structural work absent from the map
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 has a locatable dossier containing damage, data, and sign-off
- Repairs exceeding manual limits show an engineering approval appropriate to their significance
- Repair dimensions and locations agree between the map, the dossier, and the shop report
- Any inspection threshold or interval created by a repair appears in a controlled tracking system
- No structural rework described in shop findings is missing from the current map revision
Evidence normally required
- The structural repair map or dent-and-buckle chart at its current revision
- Shop-visit reports and structural work packages from the component's history
- Repair dossiers, approval letters, and deviation records where already collected
- The applicable structural repair manual revisions for the repair dates
- Maintenance-program extracts covering repair-driven inspections
Common discrepancies
- Mapped repairs whose only record is the map entry itself
- A repair beyond manual limits with no engineering approval in the file
- Repetitive inspections created by repairs and never loaded into the tracking system
- Structural rework described in a shop report that no map revision ever captured
What is at stake
An unsubstantiated repair reads as an unapproved repair to any reviewer applying acceptance standards, and structural findings are the kind that stop transactions rather than discount them. Where a repair created a repetitive inspection that no program tracks, the exposure is operational as well as commercial, and demonstrating the inspection history after the fact is far harder than keeping the dossier whole.
How the work runs
Index the repairs
List every mapped repair relevant to the component and tie each to its originating shop visit.
Assemble dossiers
Gather damage reports, repair data, approvals, and sign-offs for each entry from the source file.
Sweep for unmapped work
Read shop-report narratives for structural rework the map never recorded.
Publish substantiation status
Deliver the table, the reconciled index, and the recovery plan.
What the buyer receives
- A substantiation table listing every relevant repair with its dossier status
- An updated repair index reconciled against shop reports over the trace period
- A recovery plan naming the likely holder of each missing dossier element
- A summary of repair-driven inspection obligations and their tracking status
Who uses the output
- Records leads assembling the structural section of the component trace file
- CAMO and engineering staff loading recovered inspection obligations into the program
- Sellers and lessors preparing for the structural scrutiny of a pre-purchase inspection
How the work fits into the transaction or program
Structural substantiation is the slowest recovery effort in any records project, so this review sits early in the source review sequence to start the chase soonest. Its findings interact with the non-routine check, since most repairs were born as non-routine cards, and the two exception lists are reconciled before either ships.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Major repairs on FAA-registered history call for records under 14 CFR 43 with data acceptable to the administrator, and how a repair was classified at the time governs what evidence should exist now. EASA-side repairs approach through Part 21 repair-design approvals and Part-145 execution records under Regulation 1321/2014, and a repair approved in one system may need its acceptance under the other demonstrated when the asset changes registry.
Regulatory limits
The review neither approves repairs nor grades their engineering quality. It does not perform damage assessment, does not classify repairs as major or minor on the authority's behalf, and makes no statement about structural airworthiness; it documents which repairs are substantiated and which are not.
What this review does not cover
- Non-destructive testing or physical examination of repairs
- Engineering re-analysis of repair designs or fatigue substantiation
- Preparation of new repair-design approvals for unsupported repairs
Specific to this review
- The map-to-dossier gap widens with every operator change, because maps transfer as single documents while dossiers stay buried in shop-visit archives that may not transfer at all.
- Repairs installed as temporary with a life limit are the highest-value catch: if the limit was never tracked, the repair may have overflown its approval quietly.
- A shop report that mentions blending, doubler installation, or fastener oversizing in its narrative has produced a structural record whether or not anyone mapped it.
- Older repairs frequently predate the current structural repair manual revision, and substantiation must be judged against the data in force at the repair date, not today's manual.
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
Who should hold the missing repair dossiers?
Usually the maintenance organization that performed the visit, sometimes the design organization that approved the repair, and occasionally a prior operator's archive. The review names the probable holder for each gap because the request strategy differs: shops respond to work-order numbers, design organizations to approval references, and prior operators to lease-transfer obligations.
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.