Repair substantiation
Repair and alteration approval data behind an owner-managed aircraft file
This review builds a repair map from the logbooks, work orders, and shop reports accumulated over an ownership period, then tests every repair for the data that approved it: an SRM reference within allowable limits, DER-approved data on an FAA Form 8110-3, an STC, or another documented basis. It is commissioned by the owner representative when a managed aircraft heads toward sale or a provider transition. The output is a repair-by-repair exception list with the likely holder of each missing document.
When this review is needed
- A pre-buy inspection surfaced repairs on the airframe that the file does not explain.
- Ownership spans several maintenance providers and each holds a partial slice of the repair history.
- FAA Form 337s that should exist for major repairs cannot be located in the owner's folders.
- The buyer's technical team has asked for a repair map and nothing of the kind has ever been compiled.
The problem
Repairs on a managed aircraft are commissioned by the management company, performed at whichever shop had capacity that week, and reported to the owner as an invoice line. The logbook may carry a single sentence citing the SRM, while the dimensioned damage report and the actual data reference sit in a job file at a shop the owner has no contract with anymore. Assembling what approved each repair means going back through years of scattered custody.
What gets reviewed
- Repair map assembled from logbooks, FAA Form 337s, work orders, and shop repair reports
- Approval basis identified for each repair: SRM within limits, 8110-3, STC, or other approved data
- Major versus minor classification checked against the documentation level actually present
- Skin and structural repairs cross-referenced to any damage survey or dent charts on hand
- Recurring inspections imposed by repair data traced into the current maintenance program
- Missing documents mapped to the shop, registry file, or provider most likely to hold them
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 repair mentioned in a logbook entry appears on the map, and every mapped repair has a logbook anchor
- SRM citations resolve to a real chapter and figure whose limits cover the documented damage
- Repairs classified as major carry a Form 337 with the data-approval block completed
- 8110-3 approvals match this serial number and the damage description they are attached to
- Repeat inspections required by repair data show up on the aircraft's current due list
Evidence normally required
- Airframe logbooks and work orders spanning the ownership period
- Form 337 copies held by the owner plus the FAA registry file where needed
- Shop repair reports and job files that remain retrievable
- Any structural survey or damage chart prepared for the aircraft
- The current maintenance program due list
Common discrepancies
- A one-line entry citing the SRM with no chapter, no dimensions, and no limits assessment behind it
- A major repair absent from the owner's folders that a registry records request recovers
- Repair data imposing a recurring inspection that was never loaded into tracking
- An alteration written up as a repair, which hides the STC or field approval it actually rested on
What is at stake
A repair without its data reads as unapproved to any careful reviewer. Structural items in that state can force a fresh DER evaluation at the owner's cost and on the buyer's schedule, and an EASA-bound transfer can stall entirely while substantiation is rebuilt. Price erosion follows doubt, and doubt compounds each time another undocumented repair turns up.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair population
Sweep logbooks, 337s, work orders, and shop reports to list every repair the record mentions anywhere.
Attach approval data
Match each repair to its SRM basis, DER approval, or other approved data, and note the classification the paper supports.
Chase the gaps
Query the registry file and surviving shop archives for documents the owner's folders lack.
Publish map and exceptions
Deliver the repair map, the exception list with holders, and the carry-forward register for the handover baseline.
What the buyer receives
- A repair map listing each repair with its approval basis or the gap where one should be
- An exception list naming the missing document and its most probable holder
- A carry-forward register of recurring inspections and unresolved classifications
Who uses the output
- The owner representative fielding buyer questions about airframe history
- Structures engineers or DERs whose scope can now be limited to the genuine gaps
- Incoming maintenance control loading repair-driven inspections into its program
How the work fits into the transaction or program
The repair review sits between the logbook continuity check and the modification status review in the owner-managed file workflow. Repairs found here regularly raise release-document and weight-and-balance questions, which the sibling reviews pick up, and the finished map becomes a permanent part of the handover baseline.
Jurisdiction-specific considerations
FAA practice turns on the major-versus-minor call and the Form 337 trail, and the registry file is a genuine recovery source for filings the owner lost. EASA treats repair approval under Part 21 design rules, so a repair that was acceptable domestically may need data an EASA reviewer recognizes before the aircraft can transfer. The review notes, per repair, which regime the existing paper satisfies.
Regulatory limits
Nothing in this review classifies a repair on the authority's behalf, approves data, or judges the airworthiness of the repaired structure. Classification and approval remain with the certifying mechanic, the DER, or the authority. The review establishes what documentation exists and where the record falls short of supporting the entry.
What this review does not cover
- NDT or any physical re-examination of repaired areas
- Obtaining new DER approvals, which the exception list scopes but does not perform
- Negotiating price adjustments arising from repair findings
Specific to this review
- The FAA aircraft records file frequently holds 337s the owner never kept; one inexpensive records request can close several exceptions at once.
- Shops purge job files on their own retention cycles, so the oldest repairs are consistently the hardest to substantiate and should be chased first.
- Undocumented structural repair is the records gap buyers price most aggressively on this class of aircraft.
- Repair data often carries repeat-inspection obligations that die in the gap between the shop's paperwork and the tracking provider's database.
- An SRM citation is only as strong as its applicability: allowable limits vary by damage location, and a citation that fails the chapter check is an exception, however tidy the entry looks.
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
We only hold invoices for some of the older repairs. Does that count for anything?
An invoice establishes that the event happened, when, and who performed it, which is exactly the information needed to request the job file. It does not substitute for approval data. The review separates repairs whose data is recoverable from a shop archive from those that will need fresh substantiation, so effort and budget go where they change the outcome.
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.