767 repair approvals
Boeing 767 family repair and alteration approval records review
This review confirms that the repairs and alterations recorded on a Boeing 767 rest on approved or acceptable data and are traced to their return-to-service entries. It is run for a lessor, airline, or asset manager working a specific 767 through diligence or a records clean-up. The work maps each structural repair to its damage report, disposition, and approval basis, then flags any repair carried without a traceable source. You receive a repair map for the airframe, an exception list of repairs lacking approved data, and a closure plan for the gaps.
When this review is needed
- A 767 with a long structural history is entering diligence and each repair needs its approval basis confirmed.
- A skin repair was recorded with a disposition but the approved data behind it cannot be located.
- A freighter conversion added structural alterations whose approval documents have to reconcile with the airframe.
- An auditor questioned whether a major repair carries data appropriate to the change.
The problem
A repair is only as sound as the data behind it. On a 767 that has taken years of ground handling and structural work, the repair history is a scatter of damage reports, dispositions, and return-to-service entries, and a repair recorded without its approved-data reference leaves a hole that only surfaces under scrutiny. The airframe carries the repair either way, but the records have to prove the basis, and a missing source is hard to reconstruct after the fact.
What gets reviewed
- Structural repairs recorded on the airframe with location and reference
- The approved or acceptable data basis behind each repair
- Damage reports and engineering dispositions tied to each repair event
- Alterations, including any from a freighter conversion, matched to approval data
- Return-to-service entries linking each repair to its completion
- Repairs carried without a traceable data source logged as open items
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 carries approved or acceptable data appropriate to the structure and the change
- The disposition on file matches the repair actually embodied at that location
- Major alterations show approval data consistent with the jurisdiction of accomplishment
- Each repair traces to a return-to-service entry that closes the event
- Repairs claimed against a repair manual reference cite a revision valid at the time of work
Evidence normally required
- The repair and alteration history or dumps from the maintenance system
- Damage reports and engineering dispositions on file
- Approved and acceptable data references cited for each repair
- Return-to-service entries from the airframe logbooks
- Freighter-conversion documentation where the tail has been converted
Common discrepancies
- A skin repair recorded with a disposition but no traceable approved-data reference
- An alteration whose approval basis does not match the jurisdiction of accomplishment
- A repair citing a manual revision that was not current when the work was done
- A conversion-related structural change not reconciled against the airframe repair map
What is at stake
A structural repair without traceable approved data can force re-substantiation or, in the worst case, removal and re-repair, which is far more expensive than confirming the basis up front. At a transaction it becomes a priced exposure, and on an aging 767 with many repairs, several unsupported ones together can move the valuation.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair history
Pull the recorded repairs and alterations with their locations on the airframe.
Match each to its basis
Tie every repair to its damage report, disposition, and approved-data reference.
Confirm the return to service
Link each repair to the entry that closes the event in the logbooks.
Flag the unsupported
List repairs with no traceable basis and the source that could recover each.
What the buyer receives
- A repair map locating each recorded repair on the airframe
- An exception list of repairs lacking traceable approved data
- A closure plan naming the source that can supply each missing basis
Who uses the output
- Asset managers pricing structural repair exposure into the tail
- Engineering deciding how to treat a repair with no traceable basis
- Records teams assembling the repair evidence a buyer or auditor will request
How the work fits into the transaction or program
The repair map sits alongside the configuration baseline and feeds the diligence pack, because a buyer of an aging 767 examines structural history closely. Repairs the review finds unsupported route into remediation, where the approval basis is recovered or a defensible fallback is documented before the file changes hands.
Aircraft-specific considerations
A 767 airframe accumulates structural repairs over a long service life, and freighter-converted tails add a set of alterations tied to the main-deck cargo door and floor. Aging-aircraft structural programs on this widebody increase scrutiny of repair history, so the approval basis for each repair carries weight it might not on a younger asset.
Jurisdiction-specific considerations
A repair approved under one authority's acceptable data may need a matching basis when the 767 moves to another register, and an alteration approved in one system is not automatically recognized in the other. The review notes where a repair's basis will need supporting evidence for the receiving authority.
Regulatory limits
The review confirms that repairs and alterations trace to an approval basis and are internally consistent. It does not develop or approve repair data, disposition damage, or make an airworthiness determination on any repair.
What this review does not cover
- Developing, engineering, or approving new repair or alteration data
- Physical inspection or assessment of any repair
- Any airworthiness determination on the structure
Specific to this review
- A structural repair without traceable approved data may have to be re-substantiated or removed, which costs far more than confirming the basis before a sale.
- On a 767 the highest scrutiny falls on structural repairs, where an aging-aircraft program raises the bar for approval evidence.
- Freighter-converted tails carry conversion alterations whose approval paperwork has to reconcile against the airframe repair map.
- A repair citing a manual revision has to match the revision current when the work was performed, not the latest one on the shelf.
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
What happens to a repair we cannot trace to approved data?
It is logged as an open item, and remediation tries to recover the basis from the shop or engineering source that held it. Where the data is genuinely unrecoverable, a documented fallback stating the residual exposure is more defensible than a silent gap, and it lets the next party price the repair honestly.
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.