Boeing 747 modifications
Boeing 747 family modification-status records review
This review confirms the modification and STC status recorded for a Boeing 747 rests on approval data and matches the effectivity for this serial number. It is run for the party evaluating the asset when embodied changes carry both value and risk. The work reads service bulletin records, STC files, and configuration lists, and ties each embodied change to the approval basis behind it. You receive an exception list of modifications that do not stand up, a source map linking each change to its approval, and a closure plan for the items whose basis or effectivity cannot be shown.
When this review is needed
- A 747 carries an STC-heavy configuration and the buyer will test each modification against its approval.
- A service bulletin is claimed as embodied but the record does not show the correct revision or effectivity.
- An STC was installed under one authority and the asset is moving to a register that must accept it separately.
- A modification list has grown across operators and no one has reconciled it to the airframe.
The problem
Modifications carry a 747's individuality and much of its risk. A service bulletin embodied at the wrong revision, an STC installed without its full data package, or a configuration line recorded against effectivity that does not apply to this serial number all leave the status report claiming a change the file cannot support. On an aircraft modified repeatedly across operators, those mismatches accumulate quietly until a transaction reads the list against the airframe.
What gets reviewed
- Embodied service bulletins checked for the correct revision and effectivity
- STC files confirmed complete with their approval and installation data
- The modification list reconciled to the configuration recorded for this serial number
- Approval data confirmed for each embodied change under the governing authority
- Effectivity checked against the airframe history and prior configuration
- Modifications that alter AD applicability flagged for the status they affect
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 embodied service bulletin cites the revision and effectivity that apply to this serial number
- Every STC on the list carries the approval and installation data appropriate to the register
- The modification list reconciles with the recorded configuration for the airframe
- Effectivity on each change matches the serial number and its history
- Modifications that change AD applicability are reflected in the AD status
Evidence normally required
- The modification and STC status report for the aircraft
- Service bulletin embodiment records with revisions and effectivity
- STC files and their approval and installation data
- The configuration list and effectivity reference for the serial number
- The AD status where modifications change applicability
Common discrepancies
- A service bulletin recorded as embodied against effectivity that does not apply
- An STC on the list with an incomplete approval or installation data package
- A modification that alters AD applicability without the AD status catching up
- A configuration line that reflects a change the airframe history does not support
What is at stake
A modification without traceable approval data may have to be removed or re-substantiated, and an STC that does not transfer to the receiving register can strand a configuration a buyer paid for. A service bulletin recorded against the wrong effectivity throws doubt on the AD position that depends on it, which is exactly the kind of finding that stalls acceptance.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the claimed status
Assemble the service bulletin, STC, and configuration status the records assert.
Check basis and effectivity
Confirm each change carries approval data and applies to this serial number.
Reconcile to configuration
Map the modification list against the recorded configuration and AD applicability.
Flag the mismatches
Flag the modifications whose basis or effectivity is missing and plan recovery.
What the buyer receives
- An exception list of modifications and STCs that do not stand up to their basis
- A source map linking each embodied change to its approval and effectivity
- A closure plan for the changes whose data or effectivity needs recovery
Who uses the output
- Asset managers pricing the configuration the records can actually support
- Engineering deciding how to treat a modification with no traceable approval
- Records teams reconciling a modification list that has drifted from the airframe
How the work fits into the transaction or program
The review sets the modification baseline that AD applicability, equipment status, and later change tracking depend on. It runs before a transaction or a register move so the configuration the records claim is confirmed before anything is priced or accepted against it, and its exception list feeds the recovery of any missing approval.
Aircraft-specific considerations
A long-lived 747 typically carries a dense modification history: cabin reconfigurations, avionics upgrades, and in many cases a passenger-to-freighter conversion that is itself a major STC touching structure, systems, and configuration. Because the conversion reshapes so much of the airframe, the review reads its data package with particular care and scopes effectivity to the specific serial number.
Jurisdiction-specific considerations
An STC approved by the FAA is not automatically valid on an EASA register and usually needs validation or a separate approval, and the same is true in reverse. The review notes which modifications will require a validation path for the register the asset is moving toward.
Regulatory limits
The review reads the modification records against their approval basis and reports what is traceable. It does not approve a modification, grant or validate an STC, or determine that the configuration is airworthy.
What this review does not cover
- Developing, approving, or validating modification or STC data
- Physical survey of the installed configuration
- Any airworthiness determination on the modified aircraft
Specific to this review
- Effectivity is where modification records break most often on a 747: a service bulletin can be genuinely embodied yet recorded against a serial number it does not apply to.
- A passenger-to-freighter conversion is usually the largest single STC on a 747, so its data package is both the highest-value and the most exposed item on the modification list.
- A modification that changes AD applicability has to be reconciled with the AD status, because an out-of-date applicability turns a clean AD position into a false one.
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). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
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.
Frequently asked questions
Will an STC embodied under FAA approval carry to an EASA register?
Not automatically. Most STCs need validation or a separate approval on the receiving register, and some do not transfer at all. The review flags which modifications need a validation path so the configuration risk is visible before the asset moves.
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.