Modifications and STCs
Gulfstream G650 modification status records review
This review confirms that the modifications and STCs recorded on a Gulfstream G650 are embodied against the right effectivity and backed by their approval data. It is run by or for the party evaluating or transferring a specific G650, often before a sale or when cabin and avionics upgrades have accumulated across owners. A records specialist reconciles the modification status report against the SB embodiment records, the STC files, and the configuration list, then checks each change for effectivity and approval. You receive an exception list of modifications lacking a clean basis or effectivity, a source map to the approval data, and a closure plan for the unsupported changes.
When this review is needed
- A G650 is under offer and the buyer wants each modification and STC backed by effectivity and approval data.
- Cabin, connectivity, or avionics upgrades have accumulated across owners and were never reconciled.
- An SB is recorded as embodied but the embodiment evidence or revision has never been checked.
- An STC is claimed on the aircraft but its approval file and applicability have not been verified.
The problem
A G650 accumulates modifications the way a flagship business jet does: cabin refits, connectivity upgrades, and avionics changes driven by successive owners, each riding on an STC or approved engineering package. The modification status report may list these confidently, but a modification recorded against effectivity that does not apply to the serial number, or an STC whose approval file never reached the aircraft, leaves the configuration saying one thing the records cannot substantiate.
What gets reviewed
- The modification status report reconciled against the SB embodiment records and STC files
- Each modification checked for effectivity that applies to this serial number
- STC files confirmed complete with approval data and applicability to the aircraft
- Service bulletin embodiment recorded at the correct revision and effectivity
- The configuration list reconciled with the embodied modifications and STCs
- Modifications lacking a clean basis or effectivity logged for closure
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 modification carries approval data appropriate to the change and the register
- Effectivity on each embodied modification matches the serial number and airframe history
- STC files are complete and applicable to this aircraft rather than a sister serial number
- Service bulletins recorded as embodied cite the correct revision and effectivity
- The configuration list reconciles with the embodied modification and STC record
Evidence normally required
- The modification and STC status report for the aircraft
- Service bulletin embodiment records
- STC files with their approval data and applicability
- The configuration list for the serial number
- Approval and substantiation data for the recorded modifications
Common discrepancies
- A modification recorded against effectivity that does not apply to this serial number
- An STC claimed on the aircraft whose approval file is not in the record set
- A service bulletin recorded as embodied at a revision superseded before the work
- A configuration list that does not reflect a modification the records show as embodied
What is at stake
A modification without a traceable approval basis may have to be removed or re-substantiated before a sale closes, which is far costlier than confirming the basis up front. An SB recorded as embodied but unsupported can put AD compliance that relies on it in doubt, and an STC whose applicability does not fit the serial number can stall acceptance until the configuration is reconciled.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the claimed configuration
Pull the modification status report, SB embodiment records, and STC files for the serial number.
Test effectivity and basis
Confirm each modification applies to this aircraft and carries appropriate approval data.
Reconcile the configuration list
Map the recorded configuration against the embodied modifications and STCs.
Log the exceptions
Flag modifications lacking effectivity or approval data with the source that should hold it.
What the buyer receives
- An exception list of modifications and STCs lacking effectivity or approval data
- A source map tying each modification to its approval file and effectivity
- A closure plan for the unsupported or mis-recorded changes
Who uses the output
- Records teams reconciling the recorded configuration to its supporting approvals
- Engineering deciding how to treat a modification with no traceable basis
- Asset and buyer teams pricing the configuration the records can actually support
How the work fits into the transaction or program
The modification review reconciles the recorded configuration the rest of the file rests on, and it runs before a transaction or after a modification campaign so the records catch up to the airframe. Its exception list feeds remediation while the STC holders and shops can still supply the approval data, and the reconciled status supports the AD applicability and weight and balance that depend on the configuration.
Aircraft-specific considerations
A G650 is a flagship long-range business jet whose owners frequently invest in cabin, connectivity, and avionics upgrades, so its modification history is heavier and more owner-specific than a typical fleet aircraft's. Many of those upgrades are installed under third-party STCs whose approval files have to be present and applicable to the exact serial number, and a modification embodied for one owner can be recorded loosely at the handover to the next, so the review pays close attention to owner-driven changes and the handover boundaries around them.
Jurisdiction-specific considerations
A G650 moving between an FAA register and an EASA register needs modification and STC approvals the receiving authority accepts, and an STC approved under one system may require validation before it is acceptable on the other. The review flags each modification whose approval will not satisfy the destination register.
Regulatory limits
The review reconciles the recorded modification status and grades the approval basis behind each change. 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 most often break, because a real change can be recorded against a serial number it does not apply to.
- A flagship business jet carries a heavier, more owner-specific modification history than a fleet aircraft, which raises the diligence burden.
- A third-party STC is only usable if its approval file is present and applicable to the exact serial number, not a sister aircraft.
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
Why check STC approval files if the modification is clearly installed on the aircraft?
A physical installation does not prove the change is approved for this serial number. Without the STC approval file and its applicability, the modification is unsupported for transfer purposes and may have to be removed or re-substantiated before a sale closes.
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.