767 modification status
Boeing 767 family modification and STC status records review
This review confirms that the modifications and STCs recorded on a Boeing 767 are embodied against the right effectivity and supported by approval data. It is run for a lessor, airline, or asset manager working a specific 767 tail through a transaction or a configuration review. The work reconciles the modification status report against service bulletin records, STC files, and the configuration list, then flags any change lacking a basis or recorded against the wrong effectivity. You receive a modification status reconciled to source, an exception list of unsupported or mis-recorded changes, and a closure plan for the gaps.
When this review is needed
- A 767 with a long modification history is entering diligence and each STC needs its approval file confirmed.
- A service bulletin is marked embodied but the embodiment record or effectivity cannot be confirmed.
- A freighter conversion STC has to reconcile against the configuration and its approval data.
- A buyer wants the modification status tied to source before pricing the configuration.
The problem
A modification status report asserts a configuration, but the assertion is only as good as the approval data behind each change. On a 767 that has picked up service bulletins and STCs across several operators, an SB marked embodied without an embodiment record, or an STC recorded against effectivity that does not apply to the serial, leaves the configuration claiming something the file cannot prove. The report reads consistent until a buyer traces a single line to its basis.
What gets reviewed
- The modification status report reconciled against the configuration list
- Service bulletin embodiment records with the correct revision and effectivity
- STC files with the approval data behind each supplemental type certificate
- Freighter-conversion and cabin modifications matched to their approval basis
- Effectivity confirmed to apply to this serial number for each embodied change
- Modifications lacking a basis or mis-recorded on effectivity 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 embodied service bulletin carries an embodiment record with revision and effectivity
- Every STC on the status report has an approval file appropriate to the installation
- Effectivity on each modification applies to this serial number and the airframe history
- The modification status report reconciles with the configuration list on file
- Conversion and cabin modifications trace to approval data valid for the jurisdiction
Evidence normally required
- The modification and STC status report
- Service bulletin embodiment records
- STC files with approval and installation data
- The configuration and effectivity list for the serial number
- Freighter-conversion approval documentation where applicable
Common discrepancies
- A service bulletin marked embodied with no embodiment record on file
- An STC recorded against effectivity that does not apply to the serial number
- A modification with no traceable approval data behind it
- A conversion STC that does not reconcile with the configuration list
What is at stake
An STC without a traceable approval file can force removal or re-substantiation, and a modification recorded against the wrong effectivity misstates the configuration everything downstream depends on. At a transaction these become priced exposures, and on a register change an STC approved in one system may not carry to the other without additional work.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the claimed configuration
Assemble the modification and STC status the records assert for the serial number.
Trace each change to its basis
Confirm SB embodiment records, STC files, and the approval data behind each modification.
Check effectivity
Verify each embodied change applies to this serial number and reconciles with the configuration list.
Flag the exceptions
List unsupported, mis-recorded, or unvalidated modifications and the source to close each.
What the buyer receives
- A modification status reconciled to the source records
- An exception list of unsupported or mis-recorded changes
- A closure plan naming the source that can supply each missing approval
Who uses the output
- Asset managers pricing the configuration the records actually support
- Engineering deciding how to treat a modification with no traceable basis
- Records teams assembling the modification evidence a buyer will request
How the work fits into the transaction or program
The modification status is the spine of the configuration baseline, so this review feeds the configuration and repair work a transaction depends on. Unsupported or mis-recorded changes route into remediation while the approval source can still be reached, before the configuration is priced or the tail moves registers.
Aircraft-specific considerations
A 767 accumulates service bulletins and STCs over a long service life, and freighter-converted tails carry a major conversion STC covering the main-deck cargo door, floor, and systems that has to reconcile against the whole configuration. Long service means some early modifications sit only in an archive, so the effectivity trail reaches back through paper records.
Jurisdiction-specific considerations
An STC approved by one authority is not automatically recognized by another, so a 767 moving between an FAA and an EASA register may need validation or supporting approval for affected modifications. The review notes where an STC or SB embodiment will require additional evidence for the receiving authority.
Regulatory limits
The review reconciles the modification status against its approval data and the configuration. It does not approve a modification, grant or validate an STC, or make an airworthiness determination on the configuration.
What this review does not cover
- Developing, approving, or validating any modification or STC
- Physical configuration survey of the aircraft
- Any airworthiness determination on the configuration
Specific to this review
- An STC recorded against effectivity that does not apply to the serial misstates the configuration even though the STC itself is real.
- On a freighter-converted 767 the conversion STC touches structure and systems across the airframe, so its approval file has to reconcile against the whole configuration.
- A modification without a traceable approval file may face removal or re-substantiation, which costs far more than confirming the basis before a sale.
- An STC accepted on an FAA register may need validation before it carries onto an EASA register, so a register change reopens the modification file.
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
Does an STC recorded on the report mean the modification is fully supported?
Not on its own. The report line has to trace to an STC file with approval data appropriate to the installation, and the effectivity has to apply to this serial number. A line that cannot be tied to its approval file, or that is recorded against the wrong effectivity, is treated as unsupported until the basis is produced.
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.