GTF modification status
Geared turbofan engine modification-status records review
This review confirms that the modifications and STC embodiments recorded against a geared turbofan engine match what the records can actually support. It is run when a GTF asset is being evaluated, transferred, or held and its configuration status has to be trusted. It checks SB records, STC files, configuration lists, and the approval data behind each embodied change against the effectivity for the serial number. You receive an exception list of unsupported or mis-recorded changes, a source map per modification, and a closure plan for the serial number.
When this review is needed
- A fleet campaign SB was issued and the embodiment status on this engine has to be confirmed.
- An STC is claimed embodied and the approval file behind it has never been checked.
- The configuration list disagrees with the SB records and the two have to be reconciled.
- A GTF engine is transferring and the buyer needs its modification standard confirmed.
The problem
The geared turbofan carries a heavy and fast-moving stream of service bulletins, many of them fleet campaigns tied to durability findings. The status report says a bulletin is embodied, but the record that proves it, the SB accomplishment, the STC approval, or the configuration entry, may reference the wrong effectivity or be missing entirely. Because embodiment on this type happens in bursts during shop visits, the paperwork lags the metal, and the status list is updated from intent rather than evidence.
What gets reviewed
- Service bulletin embodiment status against the effectivity for this serial number
- STC files with the approval that authorizes each installation
- Configuration list reconciled to the SB and STC records it summarizes
- Approval and substantiation data behind each embodied change
- Fleet-campaign bulletins checked for embodiment or a valid alternative
- Unsupported or mis-effectivity changes carried as tracked exceptions
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 SB traces to an accomplishment record at the effectivity for this serial number
- Each claimed STC carries the approval that authorizes it for this engine
- The configuration list reconciles with the SB and STC records behind it
- Fleet-campaign bulletins show embodiment or a documented alternative means
- Approval data exists for every change the records assert is embodied
Evidence normally required
- The modification status report and configuration list for the engine
- Service bulletin accomplishment records with effectivity
- STC files and their approval documentation
- Approval and substantiation data for embodied changes
- The applicable SB and campaign list for the engine type
Common discrepancies
What is at stake
A modification shown embodied without its approval data can force removal or re-substantiation, and a fleet-campaign SB recorded against the wrong effectivity leaves the engine either over-credited or exposed to a requirement it never met. Either finding surfaces at a shop visit or transaction, when reconstructing the embodiment basis is slowest and the configuration has to be settled before anything else proceeds.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the asserted configuration
Assemble the SB, STC, and configuration status the records claim for the serial number.
Test effectivity and basis
Confirm each change applies to this engine and carries its accomplishment and approval.
Reconcile the list
Match the configuration list against the SB and STC records that should support it.
List the exceptions
Flag unsupported, mis-effectivity, or open-campaign items and order the closure evidence.
What the buyer receives
- An exception list of modifications lacking approval data or carrying wrong effectivity
- A source map linking each embodied change to its accomplishment and approval
- A closure plan for the unsupported modification records on the serial number
Who uses the output
- Records teams settling the modification standard the rest of the file rests on
- Engineering deciding how to treat a change with no traceable approval
- Asset managers pricing the configuration the records can actually support
How the work fits into the transaction or program
Modification status defines the configuration standard other records reference. Once the embodied SBs and STCs are confirmed, the equipment list, weight and balance, and structural-repair records can be read against a configuration that is known rather than assumed, and the export package can assert a modification standard it can prove.
Aircraft-specific considerations
The geared turbofan runs an unusually dense service-bulletin stream because durability findings on the gear system and hot section drive recurring campaigns. Embodiment happens in bursts at shop visits, so the review checks each campaign bulletin against the shop-visit record that would have embodied it, rather than trusting a status list that tends to record intent ahead of evidence.
Jurisdiction-specific considerations
An STC approved under the FAA and one validated under EASA rest on different approval documents, so an engine whose modifications were approved in one system needs the validating basis present for a receiving operator in the other. The review flags embodied changes whose approval does not carry across the two systems.
Regulatory limits
The review confirms recorded modifications are supported by approval data and correct effectivity. It does not approve a modification, grant or validate an STC, or determine that the engine's configuration is airworthy.
What this review does not cover
- Developing or approving modification, repair, or STC data
- Embodying or removing any modification on the engine
- Any airworthiness determination on the installed configuration
Specific to this review
- The geared turbofan's SB stream is dominated by fleet campaigns, so effectivity errors matter more here than isolated one-off modifications.
- Embodiment happens in shop-visit bursts, which is why the status list routinely records intent before the accomplishment evidence exists.
- A modification shown embodied without approval data can force removal, which is far costlier than confirming the basis before a transaction.
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 is effectivity the main risk on a modification-status review of this engine?
Most of the geared turbofan's modifications come through fleet campaigns that apply to specific serial-number ranges. Recording a bulletin against an effectivity that does not include this engine either credits it with a change it never received or hides a requirement it still owes. Confirming effectivity per serial number is what makes the configuration standard defensible.
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.