Repairs and alterations
Repair and alteration records checked against scanned approved data
A repair map lists every known repair and alteration on the airframe; this review checks whether the scanned archive can substantiate each entry. For every mapped item, the work locates the accomplishment record and the approved data behind it, whether SRM chapter, engineering order, DER approval, STC, or FAA Form 337. Entries with an approval missing, mismatched, or applied outside its stated limits are logged, and each substantiated repair is cross-linked in the corrected digital index.
When this review is needed
- A structural survey or heavy check found repairs on the airframe that the map explains but the archive has never proven.
- The repair map was inherited at delivery and its approval references were taken on faith.
- Damage-and-repair chart requests are expected at an upcoming remarketing and answer time matters.
- Scanned engineering files were migrated separately from maintenance records and the linkage broke.
The problem
Repairs generate two documents that live apart: the record of what was done and the data that authorized it. Maintenance files hold the first; engineering files hold the second; scanning projects usually digitize them in different batches under different conventions. The repair map keeps citing approvals by reference number, and the archive holds a thousand engineering PDFs whose file names say nothing about which dent on which frame they belong to.
What gets reviewed
- Every repair map entry paired with its accomplishment record in the scanned archive
- Approved data located for each entry: SRM reference, engineering order, DER 8110-3, STC, or equivalent
- Major versus minor classification on the map tested against the documentation each class requires
- FAA Form 337s and their approval blocks located for the alterations that need them
- Repair limits and inspection follow-ups from the approving data traced into the maintenance program
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
- The approved data cited by each map entry exists in the archive and covers that location and damage
- Repairs classified major carry field-approved or DER-approved data rather than an SRM citation stretched past its limits
- Each 337 is complete, signed, and consistent with the alteration it records
- Repetitive-inspection requirements imposed by repair approvals appear in the current program tasking
- Repair dimensions and locations in the records match the map's zone and station references
Evidence normally required
- The current repair and alteration map or dent-and-buckle chart
- Scanned maintenance records access, including heavy-check packages and work orders
- The scanned engineering file set with orders, approvals, and correspondence
- STC documentation for embodied alterations
- The current maintenance program task list, for follow-up inspection tracing
Common discrepancies
- An SRM-cited repair whose measured dimensions sit outside the chapter's allowable limits
- Engineering approvals scanned under order numbers with no cross-reference to map entries
- A 337 whose approved-data block was left blank at execution and never cured
- Repair-mandated repetitive inspections that fell out of the program at a later revision
What is at stake
A repair without locatable approved data reads as an unapproved repair until proven otherwise. Structures engineers must then re-evaluate it from measurements, sometimes requiring access panels or NDT to characterize what the paperwork should have described. At transaction time, unsupported majors on the map suppress value and invite condition clauses, and a genuinely undocumented alteration can force retrofit engineering years after the work was done.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the map
Enumerate every repair and alteration entry with its claimed reference and classification.
Pair the records
Locate the accomplishment package and the approving data for each entry across both file sets.
Test the approvals
Check scope, limits, signatures, and follow-up requirements against what was actually done.
Link and report
Cross-index maintenance and engineering evidence per repair and grade the open items.
What the buyer receives
- A substantiation table for the full repair map with evidence pointers per entry
- The corrected digital index cross-linking maintenance and engineering files per repair
- An open-item register for unsupported entries, graded by structural and commercial exposure
Who uses the output
- Structures and continued-airworthiness engineers dispositioning unsupported repairs
- Records teams answering repair-substantiation requests during audits and remarketing
- Maintenance planners restoring dropped follow-up inspections to the program
How the work fits into the transaction or program
Repair substantiation closes the loop between the archive's maintenance side and its engineering side, and it is the review most likely to generate engineering follow-up rather than pure records work. Its output joins the corrected index built by the AD, release, and shop-visit reviews, and its open items commonly feed the agenda for the next heavy check.
Jurisdiction-specific considerations
On FAA-registered aircraft, 14 CFR 43 and its appendices drive major repair and alteration documentation, including the Form 337 and field approval paths. EASA-side repairs run through approved data under Part-21 and continuing-airworthiness records under Regulation 1321/2014. Aircraft that crossed registries mid-life often carry repairs approved under one regime that the current regime's reviewers must interpret, which is exactly where documentation gaps get expensive.
Regulatory limits
The review locates and cross-checks documentation. It does not approve repairs, does not classify damage, and does not perform the engineering evaluation an unsupported repair may require. Those decisions belong to appropriately authorized engineers and the responsible authority.
What this review does not cover
- Physical survey of the airframe or verification of repairs against the structure
- Creation of new engineering approvals or repair dispositions
- SRM or structural analysis of any kind
Specific to this review
- Engineering files and maintenance files are usually scanned by different teams months apart, so the cross-reference between them is the first casualty of digitization and the main thing this review rebuilds.
- A repair map entry citing the SRM without chapter and figure is unverifiable as written; a large share of substantiation effort goes into recovering the precise citation.
- Follow-up inspections attached to repair approvals are a quiet failure mode: the repair holds, the paperwork exists, but the recurring task vanished in a program revision.
- Repairs embodied under a previous registry's field approval can lack any equivalent instrument recognized by the current authority, leaving a sound repair with unpresentable paperwork.
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 repairs have flown for years without question. Why substantiate them now?
Time in service does not substitute for approved data. The question arrives with the next buyer, auditor, or structural finding, and answering it then means engineering re-evaluation under deadline. Rebuilding the paper chain from the archive first is the inexpensive version of the same work.
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.