Taking over the airframe
Repair and alteration approval review for operators inheriting an aircraft
An operator inheriting an aircraft from a previous operator inherits every repair on its structure, along with whatever approval data does or does not stand behind each one. This review builds a repair map from the delivered records, ties each repair and alteration to its damage report, disposition, approved data, and return-to-service entry, and identifies the repeat inspections and limitations those approvals impose. It is performed for the incoming director of maintenance and CAMO before the aircraft enters the new program, and it produces the repair map, an approval-status register, and the inspection obligations the new program must absorb.
When this review is needed
- The dent and buckle chart delivered at handover has grown across several operators and nobody has reconciled it to the repair files.
- Repairs were approved under the previous operator's authority framework and their standing under the new one is untested.
- The incoming maintenance program needs every repair-driven repeat inspection loaded before the first check is planned.
- An alteration visible on the aircraft, an antenna, a cabin change, a winglet, has no obvious paperwork in the delivered files.
The problem
Structural repairs accumulate silently over an airframe's life, each one approved in the context of its own moment: a structural repair manual chapter, a designee's data package, a manufacturer telex. At transfer the incoming operator receives the pile without the context. Some repairs are outside SRM limits and were approved individually; some carry inspection intervals nobody transcribed into a tracking system; some exist on the airframe but not in the pile at all. Sorting inherited fact from inherited assumption lands on the new records team in the middle of induction.
What gets reviewed
- A consolidated repair map built from damage charts, logbook entries, and heavy-check dossiers
- Approval basis identified for each repair: SRM within limits, designee-approved data, manufacturer disposition, or STC
- Alterations reconciled between the physical configuration references and the modification records
- Repeat-inspection requirements and thresholds extracted from each approval and disposition
- Return-to-service entries located for the accomplishment of each repair
- Categorization of repairs affecting future modification or freighter-conversion eligibility
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 entry on the dent and buckle chart resolves to either an assessed allowable-damage disposition or a documented repair
- Repairs claimed as SRM-based fall inside the SRM limits for that location, thickness, and damage type
- Designee-approved data packages carry the correct authorization scope for structural approvals on this type
- Each approval that imposes recurring inspection has a corresponding entry in the delivered tracking data
- Alteration records account for the supplemental structure and systems visible in the delivered configuration documents
Evidence normally required
- Dent and buckle charts and any structural repair mapping the previous operator maintained
- Repair files: damage reports, dispositions, approved data, and embodiment work orders
- Heavy-check dossiers for the periods when major repairs were accomplished
- Modification and STC records for alterations embodied since delivery
- The tracking-system extract for repair-driven inspections, if one exists
Common discrepancies
- Repairs on the airframe that appear in no delivered file, usually from line damage handled quickly at an outstation
- A repair approved as temporary years ago, still installed, with its terminating action never planned
- Repeat inspections stated in a designee's data package but absent from the operator's tracking system
- An SRM justification citing a manual revision that did not cover the repair location at the time of accomplishment
What is at stake
A repair without traceable approved data becomes the new operator's finding, discovered at the worst time: during a heavy check with skin panels open or during an authority audit. Repeat inspections that never entered the tracking system get missed, and missed structural inspections are the kind of lapse that escalates from records problem to airworthiness question quickly.
How the work runs
Assemble the map
Merge damage charts, repair files, and check dossiers into a single location-keyed inventory of repairs and alterations.
Attach the approvals
Tie each item to its damage report, disposition, approved data, and return-to-service entry.
Extract the obligations
Pull repeat inspections, thresholds, and limitations out of each approval and compare against delivered tracking data.
Grade and hand over
Issue the approval-status register, the inherited-inspection schedule, and the sequenced data-recovery list.
What the buyer receives
- A consolidated repair and alteration map keyed to airframe location
- An approval-status register grading each item as substantiated, questionable, or undocumented
- A schedule of inherited repeat inspections and limitations ready to load into the new program
- A recovery list for missing data, sequenced by structural significance
Who uses the output
- The director of maintenance and CAMO signing the aircraft onto the new program
- Planning engineers loading repair-driven tasks into the maintenance forecast
- Structures engineers prioritizing which undocumented repairs need engineering attention first
How the work fits into the transaction or program
This work front-loads the structural records problem that otherwise surfaces piecemeal over the first years of operation. It runs during the transfer window, feeds the program-bridging exercise with the inherited inspection burden, and gives the first heavy-check planning cycle a repair map instead of a surprise inventory.
Start with a single asset
Reconcile maintenance tracking against the underlying records.
Regulatory limits
The review classifies repairs by the documentation that supports them under 14 CFR Part 43 and the EASA continuing-airworthiness framework. It does not approve repair data, does not perform engineering evaluation of the structure, and does not clear a questionable repair for continued service; it defines precisely what needs engineering or authority attention.
What this review does not cover
- Physical survey of the airframe or non-destructive inspection of repairs
- Engineering re-substantiation or new approved data for undocumented repairs
- Terminating-action embodiment planning beyond identifying that one is owed
Specific to this review
- Approval frameworks do not translate one to one: data approved through one authority's designee system may need review before the receiving authority's regime treats it as approved data.
- The dent and buckle chart is a map of what was noticed, never a map of what was repaired; the two diverge a little more with every operator the aircraft passes through.
- Temporary repairs have a habit of outliving the team that installed them, because the terminating action lives in a work order nobody carried forward.
- Repairs near planned modification zones matter disproportionately at transfer: a substantiated repair in the wrong place can still complicate a later freighter conversion or cabin change.
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 previous operator passed its authority audits. Why would its repair approvals be a problem for us?
Most will be fine. The transfer risk concentrates in the margins: data approved under mechanisms specific to the old operator's authority, temporary repairs that were never terminated, and inspection obligations that lived in engineering files rather than the tracking system. Those margins are exactly what an incoming operator answers for after acceptance.
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.