Modification & STC status
Bombardier Global 7500 modification and STC status records review
A Global 7500 modification-status records review confirms that the service bulletins and STCs the records claim as embodied are supported by approval data and correct effectivity. It is run for a lessor, operator, or management provider verifying the modification picture on a specific tail. It reads the service bulletin records, the STC files, the configuration list, and the approval data behind each change, then checks that each applies to this serial number. You receive a supported exception list, a source map from modification to approval, and a closure plan for the aircraft under review.
When this review is needed
- A Global 7500 is being traded and its modification status has to be confirmed before a buyer prices the configuration.
- A cabin or connectivity STC was installed and its approval file has never been reconciled to the record.
- A service bulletin was recorded as embodied but the accomplishment evidence has not been checked.
- A management transition left the configuration list and the STC files held by separate parties.
The problem
Modification status is where configuration drift hides, because each service bulletin and STC is recorded as a line item and rarely checked against its approval data or its effectivity. On a highly configured business jet, cabin, connectivity, and interior STCs accumulate, and an STC installed under one approval basis may need a different one on another register. A service bulletin marked embodied without accomplishment evidence, or recorded against effectivity that does not fit this serial number, leaves the configuration record saying more than the file can prove.
What gets reviewed
- Service bulletin records checked for accomplishment evidence and correct effectivity
- STC files reviewed for approval data and applicability to this serial number
- The configuration list reconciled against the embodied modifications it claims
- Approval data confirmed for each change appropriate to the installation and jurisdiction
- Interior, cabin, and connectivity modifications screened for their approval basis
- Modifications mapped to the type design so none sits outside a known configuration
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 service bulletin marked embodied carries accomplishment evidence for this serial number
- STCs claimed as installed carry approval data applicable to the aircraft and register
- Effectivity on each modification matches the serial number and its configuration
- The configuration list reconciles with the modifications the records show embodied
- No modification on the list lacks an approval reference a reviewer would accept
Evidence normally required
- The modification and STC status report for the tail
- Service bulletin records with accomplishment evidence
- STC files and their approval data
- The configuration list and effectivity references
- The type design reference to map modifications against
Common discrepancies
- A service bulletin recorded as embodied with no accomplishment evidence on file
- An STC installed under an approval that does not carry to the aircraft's register
- A modification recorded against effectivity that does not apply to this serial number
- A configuration list entry with no supporting approval data behind it
What is at stake
A modification without traceable approval data can force removal or re-substantiation, both of which cost far more than confirming the basis up front. An STC whose approval does not carry to the register the aircraft is moving to can stall acceptance until the basis is reconstructed. A configuration record that overstates what is embodied distorts AD applicability and every downstream status built on the modification picture.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the claimed status
Collect the service bulletin, STC, and configuration records the file asserts for the tail.
Test approval and effectivity
Confirm each change carries approval data and effectivity that fit this serial number.
Reconcile to type design
Map the embodied modifications against the type design and the configuration list.
List the exceptions
Flag modifications without a basis or with wrong effectivity and set out what each needs.
What the buyer receives
- A supported exception list of modifications lacking approval data or correct effectivity
- A source map from each embodied change to its approval and accomplishment evidence
- A closure plan naming the approval or evidence each open modification needs
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 basis
- Records teams assembling a defensible modification file before a trade or induction
How the work fits into the transaction or program
The modification-status review sets the configuration baseline that AD applicability, equipment status, and weight and balance all draw on, so a clean picture keeps those downstream records consistent. Its exception list drives remediation while the STC and approval files are still assembled, and the confirmed configuration becomes part of the data room the next transaction verifies.
Aircraft-specific considerations
The Global 7500 carries an advanced cabin management system and high-bandwidth connectivity, so cabin and avionics STCs are common and their approval bases vary by installer and register. A modification approved under one authority may need a validation or an acceptable basis recognized by another, which the review flags. Because the fleet is largely managed, STC files and configuration lists are often held by different parties across a handover, and reconciling them is where the review starts.
Jurisdiction-specific considerations
A Global 7500 moving between an FAA and an EASA register may carry STCs approved under one system that require a recognized basis on the other. The review notes where a modification's approval will need supplementing for the receiving register, without asserting that either authority accepts it as held.
Regulatory limits
The review confirms embodied modifications are supported by approval data and correct effectivity. It does not approve a modification, grant or validate an STC, or make an airworthiness determination on the installed configuration.
What this review does not cover
- A physical configuration survey of the aircraft
- Developing, approving, or validating modification or STC data
- Any airworthiness determination on the installed configuration
Specific to this review
- Effectivity is where modification records break most: a service bulletin can be real but recorded against a serial number it does not apply to.
- Cabin and connectivity STCs on this type carry approval bases that vary by installer, so an STC valid on one register may need a recognized basis on another.
- A service bulletin marked embodied without accomplishment evidence is a line item that reads as done but cannot be proven.
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 valid for the aircraft on one register carry to another?
Not automatically. An STC approved under one authority may need a validation or an acceptable basis recognized by the receiving authority. The review flags where the approval will need supplementing, but it does not decide that either authority accepts the modification.
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.