Boeing 747 repairs
Boeing 747 family repair-approval records review
This review examines the repair and alteration records on a Boeing 747 airframe and confirms each one rests on approved data rather than an assumption. It is run for a lessor, operator, or asset manager evaluating a specific serial number before a trade, a lease return, or a program move. The work walks the repair map, ties every disposition to its damage report and approval basis, and checks that the return-to-service entry actually closes the job. You receive an exception list keyed to each repair, a source map showing where the evidence lives, and a closure plan for the items that do not yet stand up.
When this review is needed
- A 747 is being priced for sale and the buyer will test every major repair against its approval basis.
- A structural repair was carried during a heavy check and its disposition has never been reconciled to the map.
- An alteration was embodied under one authority and the asset is moving to a register that reads approval differently.
- A prior operator left a repair map that no longer matches the airframe after later work.
The problem
On a 747 that has flown for decades and passed through several operators, repairs accumulate faster than the map that tracks them. A dent blend, a doubler, a skin replacement each leave a record, but the approval data behind them scatters across work packages, engineering orders, and correspondence that changed hands with the aircraft. When a repair is claimed without the approved data that supports it, the map says one thing and the file cannot prove it.
What gets reviewed
- The repair map reconciled to the repairs actually embodied on this serial number
- Each major repair matched to its damage report and disposition
- The approved or acceptable data supporting every repair and alteration
- Return-to-service entries confirming each repair was closed and released
- Alterations checked for the correct approval path under the governing authority
- Repairs that affect life-limited structure flagged for their inspection obligations
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
- Every repair on the map ties to a damage report and a recorded disposition
- Each disposition cites approved or acceptable data appropriate to the location and jurisdiction
- Return-to-service entries account for the repairs the map claims are complete
- Alterations carry the approval form the governing authority requires for the change
- Repairs to principal structural elements reference the inspection program they trigger
Evidence normally required
- The current repair map or structural repair record for the airframe
- Damage reports and dispositions for each major repair
- Approved-data references, engineering orders, and any repair approval forms
- Work packages and return-to-service entries covering the repairs
- The modification and configuration record where alterations overlap repairs
Common discrepancies
- A repair on the map with no damage report or disposition behind it
- An alteration embodied without the approval form the change required
- A skin or structural repair whose approved-data reference cannot be located
- A repair that triggers a recurring inspection not carried into the program
What is at stake
A repair with no traceable approval basis can force removal, re-substantiation, or a conservative assumption the current owner pays for. Left unresolved, these items surface in the next transaction with less leverage and a harder audience, and a broken repair map slows every later review that has to build on it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the map
Reconcile the repair map to the repairs actually embodied on this serial number.
Trace to approval
Match each repair and alteration to its damage report, disposition, and approved-data basis.
Check the closure
Confirm return-to-service entries and any recurring inspection each repair triggers.
List the exceptions
Record every repair whose basis is missing and plan its recovery.
What the buyer receives
- An exception list keyed to each repair and alteration with its evidence status
- A source map showing where the supporting data for each item sits
- A closure plan sequencing the repairs whose approval basis needs recovery
Who uses the output
- Asset managers pricing a 747 against the repairs its records can actually support
- Records teams rebuilding a repair map that has drifted from the airframe
- Engineering deciding how to treat a repair with no traceable approval basis
How the work fits into the transaction or program
The review sits ahead of a sale, a lease return, or a register change, where every major repair will be tested against its basis. Its exception list feeds remediation while the current owner still holds the leverage to recover a missing approval, and the reconciled map becomes the reference the next review builds on.
Aircraft-specific considerations
A 747 carries a dense structural history: freighter conversions, cargo-door and floor reinforcements, and decades of skin and stringer repairs that vary by operator. Because the airframe is large and long-lived, the repair map is often thick and partly inherited, so the review scopes to this serial number's own damage history rather than a generic type template.
Jurisdiction-specific considerations
A repair approved as minor under one authority may read as major under another, and a field approval accepted on the FAA side does not automatically satisfy an EASA reviewer. The review notes where a repair's approval path will need re-examination for the register the asset is moving toward.
Regulatory limits
The review reads the repair records against the data that supports them and reports what is traceable. It does not approve a repair, issue or restore any approval, or determine that the airframe is in an airworthy condition.
What this review does not cover
- Physical inspection or survey of the repairs on the airframe
- Developing or approving new repair or alteration data
- Any airworthiness determination on the repaired structure
Specific to this review
- On a 747 the repair map is often inherited across operators, so its thickest sections are the ones most likely to have detached from source data.
- A structural repair can silently introduce a recurring inspection that never made it into the program, which surfaces only when the map is walked against the tasks.
- Freighter conversions add repair and alteration density around the main-deck door and floor that a passenger-configured template would not anticipate.
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 support with approved data?
It goes on the exception list with the evidence that is missing and the path to recover it. Where the data is genuinely gone, engineering decides whether the repair needs re-substantiation or removal, and the review documents the residual exposure so it is not carried silently.
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.