Repair substantiation
Closing repair approval gaps on managed aircraft
Managed aircraft accumulate repairs across successive owners, operators, and management companies, and the approval data behind those repairs is what goes missing first. This remediation matches each documented repair or mapped damage to its substantiation: the SRM evaluation, the designee-approved data, or the authority approval that made the repair legitimate. An owner representative or maintenance controller brings the finding; the work brings back the file. Repairs whose approval basis cannot be recovered are documented with a defined path to regularization instead of an unexplained entry on the damage chart.
When this review is needed
- A pre-sale survey mapped damage the records cannot explain: no repair record, no disposition, no evaluation.
- A repair entry cites approved data that is nowhere in the aircraft's file.
- The aircraft moved between management companies and the repair substantiation stayed behind in someone's project folder.
- An insurer, auditor, or prospective operator has asked for the engineering basis of a visible repair.
The problem
Repair substantiation lives in more places than any other record type: the SRM evaluation at the MRO, the designee's approval in an engineering file, the photographs in a project email chain. Management transitions scatter those pieces, because each departing company hands over the logbooks and keeps its working files. Years on, the owner's representative faces a dent-and-buckle chart annotated with repairs whose engineering basis nobody can produce, on an airframe about to be sold.
What gets reviewed
- Reconciliation of the damage chart against the repair and alteration records on file
- Identification of the approval basis each repair claims: SRM chapter, designee approval, or authority approval
- Retrieval of missing substantiation from the MROs, engineering organizations, and designees involved
- Assessment of whether recovered data actually covers the repair as executed, including size and location
- Classification of each unexplained damage entry: repaired, blended, within limits as found, or unknown
- Assembly of a repair file per finding for the permanent records set
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 repair record cites data appropriate to its structural significance, from SRM reference to specific approval
- The cited SRM revision or approval was current at the date the repair was performed
- Recovered approval data matches the repair actually installed in dimensions, location, and configuration
- Damage-chart entries reconcile with a corresponding record: a repair, a permitted-damage evaluation, or a disposition
- Recurring-inspection requirements attached to any repair appear in the maintenance program
Evidence normally required
- The dent-and-buckle chart or damage map, at its latest revision
- Repair and alteration records, including FAA Form 337s or their EASA-regime equivalents
- Logbook entries and work packages covering the repair events
- Contact history for the MROs and engineering organizations that touched the airframe
- Prior survey reports and transaction records that may capture earlier states of the damage map
Common discrepancies
- A structural repair executed to designee-approved data that survives only in the designee's own files
- Damage recorded as within limits with no record of the evaluation that reached that conclusion
- A repair drawn on the chart at a different station than the paperwork describes
- Repairs carrying supplemental inspection requirements that never entered the maintenance program
What is at stake
Every unexplained entry on the damage chart reads as a possible unapproved repair, and reviewers price it accordingly. A structural repair without recoverable approval data can stall a sale outright, force an engineering re-evaluation at the buyer's chosen shop, or push the aircraft into a repair regularization exercise on the buyer's timeline instead of the seller's.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Reconcile chart to records
Match every damage-chart entry to a repair or disposition record and list what fails to match.
Trace the approval basis
Determine what data each repair claims to rest on and who would still hold it.
Recover and verify
Retrieve substantiation from designees, engineering organizations, and MROs, and test it against the repair as installed.
File and roadmap
Build the per-repair files and set out the regularization path for anything unresolved.
What the buyer receives
- A substantiation file per repair, containing the recovered approval data and disposition records
- A reconciled damage chart in which every entry points at its supporting record
- A regularization roadmap for repairs whose approval basis stayed unrecoverable
Who uses the output
- Owner representatives defending the airframe's condition in a sale or refinancing
- Maintenance control ensuring inherited repair inspection requirements are actually being flown
- The next operator or management company receiving a records set that explains its own damage chart
How the work fits into the transaction or program
Repair substantiation recovery usually runs alongside pre-sale preparation or a management transition, downstream of the survey that exposed the gaps and upstream of the buyer's technical review. Its regularization roadmap hands any true engineering work to the appropriate designee or organization with the records problem already solved.
Jurisdiction-specific considerations
Approval paths differ enough between regimes to change what closure looks like: an FAA-registered aircraft may rely on designee-approved data and Form 337 records, while an EASA-managed airframe leans on approved repair designs under the design organization system. A repair performed under one regime on an aircraft now under the other needs its original basis documented before its current acceptability can even be discussed.
Regulatory limits
The remediation locates and files repair substantiation. It produces no engineering approvals, and a repair that genuinely lacks approved data still requires an approval path through the appropriate designee, organization, or authority; this work defines that path but cannot walk it.
What this review does not cover
- Engineering analysis, repair design, or approval of repair data
- Physical inspection or nondestructive testing of the repairs
- Execution of any regularization work identified in the roadmap
Specific to this review
- A repair inside SRM limits still needs the record showing someone evaluated it against the SRM; the limit itself is not the evidence.
- Unexplained damage entries are ambiguous three ways, since the mark could be a repair, a blend, or damage left as found, and each reads differently to a buyer.
- Management-company transitions lose repair files at a higher rate than operator transitions, because working engineering files are treated as the company's property rather than the aircraft's.
- Designees and engineering organizations archive their approvals independently, which makes them the most reliable recovery source years after the MRO has purged its job file.
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 repair looks fine and has held for years. Why does the paperwork matter now?
Because the next reviewer cannot see the engineering, only the record of it. A sound repair without its approval data is treated as a question mark in valuation and in any registry or operator transfer, and resolving it later, under transaction pressure, costs more than recovering the file while the organizations that produced it still hold their archives.
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.