Skip to content

Repairs under new scrutiny

Structural repair records in an import and export records package

A structural repair map summarizes every known repair on the airframe, and at registry change each mapped repair must be backed by data the destination authority can accept. This review checks the map against the repair dossiers behind it, confirms each approval basis and any repeat-inspection obligations, and tests whether approvals granted under the exporting authority travel to the importing one. It is conducted during import, export, or registry-change preparation. The output is an exception list identifying repairs whose documentation, approval, or inspection trail needs attention before the filing.

When this review is needed

  • The repair map or dent and buckle chart has not been reconciled against repair dossiers since the last heavy check.
  • Repairs on the airframe were approved with data from the exporting authority's system and the acceptance route to the destination is unconfirmed.
  • Repeat inspections arising from repairs must be shown on the maintenance program the importing operator will adopt.
  • Damage entries exist in logbooks or non-routine records that may never have reached the map.

The problem

Structural repairs accumulate over decades, documented to the standard of whichever organization did each one. A map updated only at heavy checks quietly ages in between, while the dossiers behind older repairs thin out with every records handover. The exporting team inherits a chart it believes is complete; the importing authority treats it as a claim to be tested repair by repair.

What gets reviewed

  • The structural repair map or dent and buckle chart, reconciled against repair dossiers item by item
  • Approval basis for each repair: SRM within limits, engineering approval, or other approved data
  • Measured dimensions and location records supporting SRM-within-limits classifications
  • Repeat-inspection and damage-tolerance obligations arising from repairs, traced onto the maintenance program
  • Acceptance of each approval basis under the importing authority's framework
  • Cross-check of logbook and non-routine damage entries against the map for unlisted repairs

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 on the map has a dossier containing the data it was accomplished under
  • Repairs claimed as SRM within limits include the measurements that place them inside those limits
  • Repairs beyond SRM limits carry an engineering approval covering this aircraft and location
  • Inspection obligations generated by repairs appear on the current maintenance status with correct intervals
  • Damage events recorded in logbooks and non-routine cards resolve to a map entry or a documented no-repair disposition

Evidence normally required

  • The current structural repair map or dent and buckle chart
  • Repair dossiers: drawings, dispositions, approvals, and accomplishment records
  • Logbook and non-routine records for damage-event cross-checking
  • The maintenance status showing repair-driven inspection tasks
  • Any importing-authority correspondence touching structural items

Common discrepancies

  • A mapped repair whose dossier survives only as a one-line logbook entry
  • An SRM-within-limits claim recorded without the measured dimensions that would prove it
  • A repair-generated repeat inspection missing from the maintenance program due list
  • Damage events in the non-routine history with no corresponding map entry or disposition

What is at stake

A mapped repair without its dossier raises the question of what is actually on the airframe, and questions about primary structure carry the highest escalation potential in any import review. Resolution paths run through engineering organizations with their own lead times: reconstructing a substantiation, obtaining acceptance for a foreign approval, or in the hardest cases opening an inspection program for a repair whose limits cannot be shown. Any of these can move a registry date by months.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Reconcile the map

Match every map entry to a dossier and every recorded damage event to the map.

02

Grade the bases

Classify each repair's approval basis and check the evidence that supports the classification.

03

Trace the obligations

Follow repair-driven inspections into the maintenance program and flag absences.

04

Rank and report

Deliver exceptions ordered by structural significance and destination acceptance difficulty.

What the buyer receives

  • A reconciled repair map annotated with the dossier and approval state of each entry
  • An exception list ranked by structural significance and acceptance risk at the destination
  • A trace of repair-driven inspection obligations into the maintenance program, gaps marked

Who uses the output

  • Transition leads sequencing engineering engagement for repairs needing acceptance work
  • The importing operator's structures and CAMO staff adopting the inspection obligations
  • Asset teams weighing the cost of substantiation against the transfer timeline

How the work fits into the transaction or program

The repair review draws on the non-routine and logbook reviews for its damage-event cross-check and pushes obligations into the maintenance program review, where repair-driven inspections must land on the due list. Repairs whose approvals need destination acceptance hand off to the certification workstream of the import.

Jurisdiction-specific considerations

Repair data approved under 14 CFR Part 43 mechanisms and repair data approved within the EASA system under Regulation 1321/2014 do not automatically substitute for one another; bilateral provisions cover some categories and leave others needing case-by-case acceptance. The same dossier can therefore be sufficient or deficient depending on which way the aircraft is moving, and the review grades every repair against the actual destination.

Regulatory limits

Assessing whether a dossier supports a mapped repair is a records exercise. The review does not evaluate repair designs, does not approve or accept any repair, and does not determine the structural condition or airworthiness of the airframe. Engineering judgments belong to approved design organizations and the authorities.

What this review does not cover

  • Physical inspection or non-destructive testing of repairs
  • Repair design, substantiation, or re-approval work
  • Negotiating acceptance of specific repairs with the importing authority

Specific to this review

  • Repair maps age between heavy checks, so the reconciliation date of the map matters as much as its content; a chart from two checks ago is a different document.
  • Measured dimensions behind an SRM-within-limits claim are the most commonly missing piece of otherwise complete dossiers, and without them the classification is an assertion.
  • Older repairs from defunct organizations are the hardest dossiers to reconstruct, which is why long-history airframes get sampled deepest in their earliest repairs.
  • One unsupported repair on primary structure attracts more authority attention than a dozen documentation defects elsewhere in the package.

Sources

Frequently asked questions

Does a repair approved years ago under the exporting authority need anything at import?

Often nothing, sometimes a great deal. Many categories pass under bilateral provisions without further showing, while others need the data accepted or validated by the destination authority. Sorting repairs into those bins early is the point of the review, because the difficult bin has engineering lead time attached.

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.