777 family repair data
Boeing 777 family repair approval data records review
This review confirms that each repair and alteration recorded on a Boeing 777 family aircraft rests on approved data and closed with a valid return to service. It is run for a lessor, airline, or asset manager evaluating, transferring, or holding a specific tail. The work builds a repair map from damage reports, dispositions, and approval references, then checks each entry against the basis it claims. You receive a supported exception list, a source map linking each repair to its approved data, and a closure plan for the serial number under review.
When this review is needed
- A 777 has accumulated structural repairs across a long service life and no one has reconciled them to their data recently.
- A repair was accomplished on a foreign register and its approval basis has to hold on the receiving one.
- A buyer wants every major repair mapped and substantiated before pricing the airframe.
- A heavy check disclosed damage and the disposition has to trace to approved data before the aircraft leaves the dock.
The problem
A long-haul airframe collects skin repairs, doubler installations, and structural dispositions over decades, and each one is only as sound as the data it was approved against. A repair recorded without a reference to its approved basis, or one whose damage report and disposition never got filed together, leaves the airframe carrying a modification nobody can substantiate. That gap surfaces during a transaction or a heavy check, when reconstructing the basis is slowest.
What gets reviewed
- A repair map assembled from damage reports, dispositions, and approval references for the airframe
- Structural repairs matched to the approved data or acceptable basis they claim
- Return-to-service entries confirmed for each repair and alteration
- Repairs affecting the pressurized structure checked for a substantiation reference
- Alterations that change the type design reconciled to their approval basis
- Repairs accomplished on a prior register checked for acceptance on the current one
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 recorded repair references the approved or acceptable data it was accomplished under
- Damage reports and their dispositions are filed together and describe the same event
- Return-to-service entries follow from a repair supported by valid data
- Structural repairs on primary structure carry substantiation appropriate to the location
- Repairs approved under a prior authority carry the acceptance the current register requires
Evidence normally required
- The repair and alteration records and any existing repair map
- Damage reports and structural repair dispositions
- Approved data references and substantiation packages
- Return-to-service entries for the repairs on file
- Heavy-check work packages that disclosed or embodied structural repairs
Common discrepancies
- A structural repair recorded with no reference to the approved data it rests on
- A damage report whose disposition was never filed alongside it
- A repair approved under a prior register that lacks acceptance on the current one
- A return-to-service entry closing a repair whose substantiation is missing
What is at stake
A repair without traceable approved data may have to be re-substantiated or removed, which is expensive on a pressurized fuselage and can ground the aircraft while the basis is rebuilt. On a register change, a repair approved under one authority can require fresh acceptance on the other, and unmapped repairs erode the airframe value a buyer is willing to pay.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the repair map
Assemble the airframe's repairs from damage reports, dispositions, and approval references for the serial number.
Match each repair to data
Confirm the approved or acceptable data behind every recorded repair and alteration.
Check closure and acceptance
Verify return-to-service and confirm cross-register acceptance for repairs approved elsewhere.
List the exceptions
Flag repairs with no traceable basis and sequence the substantiations to recover.
What the buyer receives
- A supported exception list of repairs whose approval basis is unproven
- A source map linking each repair to the approved data behind it
- A closure plan sequencing which substantiations to recover before the next milestone
Who uses the output
- Engineering deciding how to treat a repair with no traceable approved data
- Asset managers pricing the airframe against its substantiated repair history
- Records teams closing repair-data gaps before a heavy check or a transfer
How the work fits into the transaction or program
Repair substantiation sits beneath the airframe value and the configuration baseline, so this review runs before a transaction prices the structure or a heavy check reopens it. The exception list drives recovery of the approved data while the shops and engineering records that hold it can still be reached, and the repair map becomes the structural history a buyer verifies.
Aircraft-specific considerations
The 777 carries a pressurized composite and metallic structure across a long fuselage, and structural repairs concentrate at the doors, the belly, and the wing-to-body fairing where service damage recurs. Repairs on primary structure demand a clear substantiation reference, and a tail that has changed register or operator accumulates repairs approved under different authorities, so the map is built for this serial number's actual damage history.
Jurisdiction-specific considerations
A repair approved on approved data under one authority does not automatically carry acceptance under another, so a 777 moving between FAA and EASA registers needs each significant structural repair checked for the acceptance the receiving system requires.
Regulatory limits
The review reconciles each repair to the approval basis the records claim. It does not approve a repair, develop repair data, or determine that a repaired structure or the aircraft is airworthy.
What this review does not cover
- Developing or approving new repair or alteration data
- Physical inspection of any repaired structure
- Any airworthiness determination on the airframe
Specific to this review
- On a long-life 777 fuselage the recurring repair locations are the cargo-door surrounds and the belly skin, where service damage concentrates.
- A repair recorded without its approved-data reference is more expensive to resolve than a missing release form, because re-substantiating primary structure can ground the aircraft.
- Repairs accomplished under a prior register are the most common acceptance blocker when a 777 transfers between FAA and EASA.
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
How are structural repairs treated differently from minor ones?
Repairs to primary structure carry a higher substantiation bar and are mapped and checked first, because a missing basis on a pressurized structural repair can force re-substantiation or removal. Minor repairs are reconciled to their data but rarely carry the same exposure.
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.