Boeing 787 family structural repair records review

When this review is needed

• A 787 structural check is coming and the repair map has to be proven against approved data first.
• A composite repair shows on the map but its damage-tolerance substantiation is not in the file.
• Structural repairs created repeat inspections that need reconciling with the program status.
• A buyer wants the structural repair history confirmed before pricing the airframe condition.

The problem

Structural repairs on a 787 are dominated by composite work, where the approval basis depends on the damage size, location, and layup rather than a standard metallic scheme. A repair can be embodied and flying while its substantiation sits with the shop that did the input, and the repeat inspections a damage-tolerant repair generates can slip out of the program status. When the repair map, the damage reports, and the manual references were built at different times, the airframe's structural condition is asserted by documents that do not fully support each other.

What gets reviewed

• The structural repair map reconciled against the logbook and check records that created each repair
• Damage reports and structural repair manual references matched to each embodied repair
• Approved or acceptable data supporting the size, location, and layup of composite repairs
• Damage-tolerance repeat inspections traced into the program status
• Repairs to primary structure checked for the correct approval path
• Interaction between adjacent structural repairs and any allowable-damage limits

What gets validated

• Each structural repair on the map has approved data covering its actual damage geometry
• Composite repair substantiation matches the recorded size, location, and layup
• Repairs to primary structure carry approval appropriate to the change and jurisdiction
• Damage-tolerance repeat inspections from repairs appear in the program status
• Structural repair manual references cite a revision effective at the time of repair

Evidence normally required

• The current structural repair map for the tail
• Damage reports and structural repair manual references for each repair
• Approved-data or engineering substantiation packages for composite and metallic repairs
• The program status showing damage-tolerance repeat inspections
• Logbook and check records covering the structural repair events

Common discrepancies

• A composite structural repair embodied without the damage-tolerance substantiation that supports it
• A repair on the structural map with no matching approved-data reference
• A damage-tolerance repeat inspection that never reached the program status
• A repair to primary structure recorded against a superseded structural repair manual revision

What is at stake

A structural repair without traceable approved data can force removal, re-substantiation, or a conservative structural assumption the owner carries into the next deal. A damage-tolerance follow-up inspection lost from the program status means a required check is not being tracked, which is a direct airworthiness exposure, and composite structural work is expensive and slow to reopen once the approval trail has gone cold.

How the work runs

What the buyer receives

• An exception list keyed to each structural repair with its missing or unsupported item
• A source map linking every structural repair to its approval basis and inspection follow-up
• A closure plan for the substantiation to recover and the repeat inspections to reinstate

Who uses the output

• Asset managers pricing the airframe condition the structural records support
• Records teams assembling the structural repair file before a check or a sale
• Engineering deciding how to treat a structural repair whose approval basis is missing

How the work fits into the transaction or program

The structural repair record underpins the airframe condition a buyer or a receiving operator inherits, so this review clears each repair's basis before a structural check or a valuation relies on it. It sits close to the general repair-approval review but concentrates on primary structure, and it feeds the damage-tolerance inspections into the program status where they have to be tracked.

Aircraft-specific considerations

The 787 uses composite primary structure across the fuselage and wing, so structural repairs are substantiated through damage-tolerance analysis tied to the specific damage rather than a standard metallic repair. This makes the substantiation package the pivotal document, and its absence is both harder to reconstruct and more consequential than on a metal airframe. The review is scoped to the actual structural repair history on the serial number rather than a family scheme.

Jurisdiction-specific considerations

A structural repair approved under FAA data may need validation for an EASA operator inducting the aircraft, so the review flags where a repair basis will have to be re-established for the receiving register.

Regulatory limits

The review confirms the structural repairs are supported by traceable approved data and that their follow-up inspections are tracked. It does not approve a repair, develop repair data, or make an airworthiness determination on the structure or the aircraft.

What this review does not cover

• Physical inspection or damage assessment of the structure
• Developing or approving structural repair or substantiation data
• Any airworthiness determination on the structure or the aircraft

Specific to this review

• Composite structural repairs are substantiated to the specific damage, so the substantiation package is the load-bearing document and a generic repair scheme will not close the trace.
• A damage-tolerance repeat inspection dropped from the program status is a live airworthiness exposure, not just a records gap, because a required check goes untracked.
• The approval basis for a structural repair usually lives with the shop that performed the input, so it degrades faster than the repair map that references it.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits