Skip to content

GTF structural repairs

Geared turbofan engine structural-repair records review

This review confirms that the structural repairs recorded on a geared turbofan engine installation each rest on approved data and are captured on the repair map. It is run when a GTF asset is being evaluated, transferred, or held and its repair history has to be trusted. It checks repair maps, damage reports, repair manual references, and the approval data behind each repair. You receive an exception list of repairs lacking a defensible basis, a source map per repair, and a closure plan for the serial number.

When this review is needed

  • A repair is recorded but its manual reference or approval data has never been confirmed.
  • The repair map is out of date and recent repairs have to be captured on it.
  • A damage report describes a finding whose repair record cannot be located.
  • A GTF asset is transferring and the buyer wants the repair history substantiated.

The problem

A structural repair is only as defensible as the data behind it. Each repair should trace to a damage report, a repair manual reference or approved repair data, and a place on the repair map, but repairs done under schedule pressure often reference the wrong manual revision or invoke a repair scheme that was never formally approved. A repair map that lags the actual repairs leaves the airframe carrying work no drawing shows, which surfaces the moment an auditor or buyer tries to assess cumulative damage.

What gets reviewed

  • Each recorded repair matched to a damage report and its location on the repair map
  • Repair manual references checked at the revision the repair was worked to
  • Approved or acceptable repair data present for repairs beyond the manual
  • The repair map reconciled to the full set of recorded repairs
  • Cumulative and adjacent-repair interactions visible on the map
  • Repairs lacking a defensible basis carried as tracked exceptions

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 traces to a damage report and a defined location on the repair map
  • Repair manual references match the revision the repair was actually worked to
  • Repairs beyond the manual carry approved or acceptable data appropriate to the damage
  • The repair map reflects every repair the records assert, with none omitted
  • Adjacent and cumulative repairs are visible so their interaction can be assessed

Evidence normally required

  • The structural repair map for the installation
  • Damage reports for the recorded repairs
  • Repair manual references at the relevant revisions
  • Approved or acceptable repair data for repairs beyond the manual
  • Logbook and shop-visit entries covering the repairs for reconciliation

Common discrepancies

  • A repair invoking a repair scheme with no approved data behind it
  • A repair manual reference at a revision that does not match the work performed
  • A completed repair missing from the repair map
  • A damage report whose corresponding repair record cannot be located

What is at stake

A repair without traceable approval data can force re-substantiation or removal, and one missing from the repair map hides its interaction with adjacent repairs and damage. At a transaction or heavy check, an unsupported repair is among the most expensive findings to clear, because the substantiation has to be reconstructed and the cumulative-damage picture reassessed before anything downstream can proceed.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Assemble the repair set

Collect the repair map, damage reports, and repair records for the installation.

02

Trace each repair

Confirm every repair references the right manual revision or carries approved repair data.

03

Reconcile the map

Check that the map reflects all recorded repairs and shows adjacent-repair interactions.

04

List the exceptions

Record repairs without a defensible basis and order the substantiation needed to close them.

What the buyer receives

  • An exception list of repairs lacking a traceable, defensible basis
  • A source map linking each repair to its damage report and approval data
  • A closure plan for the unsupported repairs on the serial number

Who uses the output

  • Records teams confirming the repair history rests on data that can be shown
  • Engineering assessing a repair whose approval basis is missing or unclear
  • Asset managers weighing the exposure the unsupported repairs represent

How the work fits into the transaction or program

Structural-repair review connects to the non-routine records that raised the damage and the modification records that establish the configuration a repair was applied to. Where a repair invoked approved data, that basis is confirmed here, and where a repair affects a life-limited or fatigue-critical area, the finding feeds the continuing-airworthiness assessment the engine also depends on.

Aircraft-specific considerations

Repairs on a geared turbofan installation cluster around high-stress structure and are often driven by findings the type's service experience has surfaced. The review confirms each repair against its approved basis and its place on the repair map, because on a young type the repair schemes are still evolving and a repair worked to a superseded scheme is a realistic finding rather than an edge case.

Jurisdiction-specific considerations

A repair approved under FAA acceptable data and one substantiated under EASA rest on different approval routes, so a repair valid in one system may leave a receiving operator in the other without a recognized basis. The review flags repairs whose approval data does not carry across the two systems.

Regulatory limits

The review confirms that recorded repairs are traceable to approved data and captured on the map. It does not approve a repair, develop repair data, or determine that the repaired structure is airworthy.

What this review does not cover

  • Developing or approving repair data or a repair scheme
  • Performing, inspecting, or re-working any repair
  • Any airworthiness determination on the repaired structure

Specific to this review

  • A repair missing from the map hides its interaction with adjacent repairs, so the cumulative-damage picture is unreliable until the map is reconciled.
  • On a young type the repair schemes are still evolving, which makes a repair worked to a superseded scheme a common rather than rare finding.
  • An unsupported structural repair is among the most expensive findings to clear because both the substantiation and the cumulative-damage assessment have to be rebuilt.

Sources

Frequently asked questions

Why does a repair need to appear on the repair map even if its paperwork is complete?

The repair map is how adjacent and cumulative repair interactions are assessed. A repair with complete paperwork but no place on the map is invisible to that assessment, so an auditor or engineer cannot judge how it interacts with nearby damage and repairs. Reconciling the map is what makes the cumulative structural picture defensible.

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.