Skip to content

Repair substantiation

Repair-approval data review inside the redelivery binder

Every repair on an aircraft's structure and systems has to be defensible at redelivery, and this review confirms that the binder's repair map is. A specialist reconciles the map against dent and buckle charts, non-routine paperwork, and the approved data behind each repair, whether that is a structural repair manual reference, an FAA Form 8110-3, or a design-organization approval. The work happens during binder preparation or when a counterparty challenges the repair file. What comes back is a repair-by-repair account of what is substantiated, what is not, and what the cure would take.

When this review is needed

  • A pre-return survey found doublers or blended areas that do not appear on the repair map the operator supplied.
  • Heavy checks during the lease generated structural findings and the approved-data trail was filed by the MRO rather than the operator.
  • The lease requires all temporary or time-limited repairs to be made permanent before return, and no one has confirmed which repairs still carry limits.
  • The incoming operator's engineers have asked for substantiation on specific repairs and the answers are taking days per item.

The problem

Repair records age badly across a lease. The chart that plots a doubler and the paperwork that justifies it live in different archives, drawn up by different organizations, sometimes under different registration marks. By return, the operator holds a repair map assembled from memory and system exports, while the substantiating documents sit in heavy-check work packs that were never mined for them. Asking whether repair 47 has approved data becomes an archaeology project under a contractual clock.

What gets reviewed

  • Reconciliation of the repair map against dent and buckle charts, survey reports, and non-routine records
  • Verification that each mapped repair cites its approved data, whether SRM chapter and figure, 8110-3, or Part 21 design approval
  • Confirmation that repairs performed outside SRM limits carry a specific engineering disposition rather than a generic reference
  • Review of repair classifications and any recurring-inspection thresholds attached to them
  • Identification of temporary or interim repairs and the status of their terminating action
  • Cross-check of alteration entries against the modification records where a repair changed configuration

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-map entry resolves to a physical location, a date, and the work pack in which the repair was accomplished
  • The approved data cited for a repair is enclosed in the source set and matches the repair as described, including size and material
  • Repairs referencing the SRM cite a chapter and figure valid at the revision in effect when the work was done
  • Time-limited repairs show either a terminating action or a live inspection requirement carried into the current program
  • No structure noted in survey or discrepancy records is absent from the repair map

Evidence normally required

  • The operator's repair map or repair summary for airframe and major components
  • Dent and buckle charts and any recent survey or bridging-inspection reports
  • Heavy-check work packs, non-routine cards, and engineering dispositions covering the lease term
  • Approved-data documents: SRM extracts, 8110-3 forms, design-organization repair approvals
  • The redelivery conditions addressing repairs, including any permanence requirements

Common discrepancies

  • Visible external repairs with no corresponding entry anywhere in the repair documentation
  • Map entries citing approved data that is referenced by number but never enclosed in the source set
  • Interim repairs recorded as permanent even though the original disposition imposed a life or inspection limit
  • Repairs dispositioned against an SRM revision that did not contain the cited figure at the time of embodiment

What is at stake

Unsubstantiated repairs are among the most expensive record gaps to close late. Recreating approved data means engaging a design organization or DER, sometimes with access to the aircraft, and a repair that cannot be substantiated at all may force rework of sound structure. Left unresolved, these items stall acceptance outright because no incoming operator will adopt a repair it cannot classify for its own inspection program.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Assemble the repair population

Merge the map, charts, survey findings, and non-routine records into one candidate list of repairs to substantiate.

02

Trace each repair to its work pack

Locate the accomplishment record and the engineering disposition for every entry on the merged list.

03

Test the approved data

Confirm the cited data exists, is enclosed, matches the repair, and was valid at embodiment.

04

Report by cure path

Deliver the matrix and gap list split into document retrieval, new engineering, and physical rework candidates.

What the buyer receives

  • A substantiation matrix scoring every mapped repair against its location, work pack, and approved data
  • A gap list separating missing documents from missing engineering, since only the second needs new approval work
  • A corrected repair map draft the operator can adopt for the acceptance file
  • A briefing note on repairs with open inspection thresholds the next program must absorb

Who uses the output

  • Lessor technical teams deciding which repairs to contest at acceptance
  • Operator engineering groups sequencing DER or design-office work before the return date
  • The incoming operator's maintenance-program staff who inherit repair inspection thresholds

How the work fits into the transaction or program

Repair substantiation sits between the physical survey and the records acceptance. Survey findings feed this review as a completeness check on the map; its output feeds the acceptance negotiation and the incoming operator's damage-tolerance and inspection planning. Where a repair changed weight or configuration, the findings also route into the weight and balance and equipment-list reviews on the same binder.

Jurisdiction-specific considerations

Approved data takes different forms on each side of the Atlantic: FAA practice leans on DER-signed 8110-3 forms and 14 CFR Part 43 major-repair records, while EASA operators substantiate through Part 21 design organizations under Regulation (EU) 1321/2014 continuing-airworthiness rules. A repair approved under one system usually needs review, and occasionally validation, before the receiving authority's operator will accept it.

Regulatory limits

This is a records review, and it stops at the paperwork. It does not approve repairs, generate engineering dispositions, classify damage, or make airworthiness determinations, and it does not replace the design-approval processes of either the FAA or EASA.

What this review does not cover

  • Creation of new repair approvals or engineering orders
  • Non-destructive testing or physical mapping of the airframe
  • Negotiating repair-related compensation between lessor and lessee

Specific to this review

  • The SRM revision in force on the day a repair was embodied is the one that governs it, so a repair can be unsubstantiated today even though the current SRM contains an identical scheme.
  • Repairs carrying recurring-inspection thresholds do not close at redelivery; the obligation transfers, and an incoming operator will refuse a map that hides those thresholds.
  • A repair map with more entries than the dent and buckle chart is as suspicious as the reverse, since it often means entries were duplicated from overlapping work packs.
  • Most substantiation gaps turn out to be retrieval problems at the MRO that did the work, which is why the review distinguishes missing paper from missing engineering.

Sources

Frequently asked questions

The MRO that did our heavy checks holds the repair paperwork. Is that a problem?

It is normal, and it is manageable if started early. The review identifies exactly which work packs and dispositions to request, which turns a broad archive request into a targeted retrieval. Difficulty arises when the return date is close, because MRO archive turnaround is measured in weeks and cannot be compressed by contract pressure on the lessee.

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.