787 repair records
Boeing 787 family repair and alteration approval records review
This review examines the repair and alteration records on a specific Boeing 787 family aircraft to confirm each disposition rests on approved data and traces to the airframe it sits on. A records specialist runs it for the party evaluating, transferring, or holding the tail, usually ahead of a sale, a lease event, or a heavy input. It walks the repair map, damage reports, engineering dispositions, and return-to-service entries, then checks the substantiation behind composite and metallic repairs against the type design. You receive an exception list keyed to each repair, a source map back to the approval basis, and a closure plan for the items that lack it.
When this review is needed
- A buyer is pricing a 787 and needs every recorded repair tied to an approval basis before closing.
- A composite repair shows on the airframe but its substantiation package is not in the file.
- The repair map and the logbook entries disagree on where a damage disposition was applied.
- A lease return is approaching and the lessor wants the repair record cleared before redelivery.
The problem
On a 787 the repair story spans composite skin, metallic structure, and systems changes, and the approval basis for each lives in a different place. A repair can be embodied and flying while its substantiation sits with a shop that handled one input years ago. When the repair map, the damage reports, and the logbook entries were built at different times, the records claim a configuration that no single document supports on its face.
What gets reviewed
- The repair map reconciled against the logbook and work-package entries that created each repair
- Damage reports and engineering dispositions matched to the repair actually embodied
- Approved or acceptable data cited behind each metallic and composite repair
- Return-to-service entries confirming each repair was released against that data
- Alterations that changed the type design checked for the correct approval path
- Interaction between adjacent repairs and any repeat-inspection or damage-tolerance follow-up
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 on the map has a disposition and an approval basis that names the data used
- Composite repair substantiation covers the actual damage size, location, and layup on the airframe
- Return-to-service entries reference the same repair the disposition describes
- Alterations affecting structure or systems carry approval appropriate to the change and jurisdiction
- Repeat inspections or damage-tolerance tasks flowing from a repair are captured in the program status
Evidence normally required
- The current repair map or structural repair listing for the tail
- Damage reports, engineering dispositions, and the associated approved-data references
- Airframe logbook entries and work packages covering the repair events
- Return-to-service documentation for each recorded repair
- Any STC or major-alteration files that changed the type design
Common discrepancies
- A composite repair embodied without the substantiation package that supports its size and location
- A repair on the map with no matching disposition or approval reference in the file
- A damage-tolerance follow-up inspection that never made it into the program status
- An alteration recorded as a minor change that actually needed a major-change approval path
What is at stake
A repair without traceable approved data can force removal, re-substantiation, or a conservative assumption the owner carries into the next deal. A buyer who finds the gap during diligence discounts the asset or slows the timeline, and composite repairs in particular are expensive to reopen once the approval trail has gone cold.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair map
Pull the current repair listing and the logbook and work-package entries that created each repair.
Match disposition to data
Tie every repair to its damage report, engineering disposition, and cited approved data.
Check the release and follow-up
Confirm each repair was returned to service and that any repeat inspection reached the program status.
List exceptions and closure
Record repairs without a supported basis and sequence the substantiation to recover.
What the buyer receives
- An exception list keyed to each repair with its missing or unsupported approval item
- A source map linking every repair to the disposition and approved data behind it
- A closure plan sequencing the substantiation to recover and the follow-up tasks to schedule
Who uses the output
- Asset managers pricing the structural condition the records actually support
- Records teams assembling the repair file before a redelivery or sale
- Engineering deciding how to treat a repair whose approval basis cannot be found
How the work fits into the transaction or program
The repair record sits underneath the configuration baseline and the structural picture a buyer or receiving operator relies on. This review clears the approval basis for each repair before those larger reviews build on it, and it feeds the follow-up inspections into the maintenance-program status where they belong.
Aircraft-specific considerations
The 787 carries far more composite primary structure than earlier widebodies, so repair substantiation leans on damage-tolerance and layup data rather than a simple metallic repair scheme. Electrical and systems alterations tie back to software part numbers and configuration state, which means a structural repair on this type can pull in changes that a metal-airframe review would never touch. The review is scoped to the actual repair history on the serial number rather than a family checklist.
Jurisdiction-specific considerations
A repair approved under FAA data does not automatically satisfy an EASA operator inducting the tail, so the review notes where a repair basis will need validation or a parallel approval for the receiving register.
Regulatory limits
The review checks whether the recorded repairs are supported by traceable approved data. It does not approve a repair, develop repair data, or make an airworthiness determination on any repair or on the aircraft.
What this review does not cover
- Physical inspection or damage assessment of any repair on the airframe
- Developing or approving new repair or substantiation data
- Any airworthiness determination on the structure or the aircraft
Specific to this review
- Composite repairs on the 787 are substantiated to the specific damage geometry, so a generic repair scheme rarely closes the trace on its own.
- A structural repair can trigger repeat inspections that only live in the program status, so the two records have to be read together or the follow-up quietly disappears.
- The approval basis for a repair often sits with the shop that performed the input, and that link degrades faster than the repair map itself.
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
Why do composite repairs need more scrutiny than metallic ones on a 787?
Composite repairs are substantiated to the actual damage size, location, and layup rather than a standard metallic repair scheme, so the approval package has to match the specific repair on the airframe. A missing substantiation file is harder to reconstruct after the fact and can force the repair to be reworked.
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.