Cross-border engine transfer
Modification-status review for a cross-border engine transfer
This review reconciles an engine's modification and STC status against the approval data behind each change before the engine transfers to another authority. It is run by or for the transferring party ahead of shipment. It covers Service Bulletin embodiment records, STC files, the configuration list, and the approval data each modification rests on, read against what the receiving side recognizes. You receive a modification status report with the basis for each change, a list of modifications whose approval will not carry across, and a request set for the missing files.
When this review is needed
- An engine carries STC-approved modifications that must be recognized on the receiving register.
- Service Bulletin embodiment is claimed but the embodiment record is not in the file.
- The configuration list and the modification records disagree on what is actually fitted.
- A modification changes an AD applicability or a life limit the receiving side will check.
The problem
Modification status accumulates as Service Bulletins are embodied and STCs are applied, each recorded in the context of the register it was approved on. An engine crossing a border carries that history to an authority that recognizes its own approvals. An STC valid at origin may need validation before the receiving side accepts the modified configuration, and a Service Bulletin recorded as embodied without the embodiment record cannot prove the work was done. The configuration list is only as good as the records under each line.
What gets reviewed
- Service Bulletin embodiment records against the claimed configuration
- STC files and the approval each modification rests on
- The configuration list reconciled to the modification and embodiment records
- Approval data read against what the receiving authority recognizes
- Modifications whose approval will not carry across flagged for validation
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 claimed Service Bulletin embodiment carries the record that proves the work was done
- STC-approved modifications carry approval data the receiving authority recognizes
- The configuration list reconciles with the modification and embodiment records
- Modifications affecting AD applicability or life limits are cross-checked against those records
- Superseded modification records are separated from the current configuration
Evidence normally required
- The engine modification and STC status report
- Service Bulletin embodiment records
- STC files and approval data for embodied modifications
- The configuration list for the current engine build
Common discrepancies
- A Service Bulletin recorded as embodied with no embodiment record on file
- An STC valid at origin that the receiving register has not validated
- A configuration list that disagrees with the modification records on a fitted change
- A modification affecting AD applicability that the AD status does not reflect
What is at stake
A modification the receiving authority does not recognize can force the change to be validated, reversed, or re-substantiated before the engine enters service, and any of those stalls induction. A Service Bulletin claimed but not evidenced can hide a change that affects AD applicability or a life limit, which surfaces later as an open item the receiving operator inherits.
How the work runs
Reconcile the configuration
Match the configuration list to the modification and Service Bulletin embodiment records.
Check the approval basis
Read each STC and modification against what the receiving authority recognizes.
Cross-check the effects
Confirm modifications touching AD applicability or life limits agree with those records.
Flag validation and recovery
List modifications needing validation or missing records and request them.
What the buyer receives
- A modification status report with the approval basis behind each change
- A list of modifications whose approval will not carry to the receiving authority
- A document request set for the missing embodiment records and STC files
Who uses the output
- Engineering deciding whether a modification needs receiving-side validation
- Records teams recovering embodiment records and STC files before shipment
- Continuing-airworthiness leads reconciling modification status with AD and life-limit records
How the work fits into the transaction or program
This review runs before transfer, so a modification with a weak or unrecognized basis is found while the origin holder can still recover the file. Its findings drive the STC validation and record recovery that must clear before induction, and it feeds the AD and life-limit reviews any modification touches.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
An STC approved by one authority is not automatically valid on another register, and the receiving side may require its own validation of a modified engine configuration. The review flags STCs and modifications whose approval is register-specific so the validation need is known before the engine moves.
Regulatory limits
This review reconciles modification status against its approval basis. It does not approve a modification, validate an STC on the receiving register, or make an airworthiness determination on the modified configuration. Validation rests with the receiving authority.
What this review does not cover
- Developing, approving, or validating any modification or STC
- Physical inspection of the modified configuration
- Any airworthiness determination on the engine build
Specific to this review
- An STC valid at origin can require receiving-side validation, so a recognized modification at home is not automatically recognized abroad.
- A Service Bulletin recorded as embodied without its record cannot prove the work, which is a distinct gap from a change never claimed.
- A modification can shift AD applicability or a life limit, so modification status is cross-checked against those records, not read alone.
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). Export airworthiness approval requirements and special requirements of an importing authority.
Frequently asked questions
Our STC modifications are approved. Why would the receiving authority not accept them?
An STC is approved on the register that issued it. Another authority recognizes its own approvals and may require validation of the modified configuration. The review flags which modifications need receiving-side validation so that work starts before the engine ships rather than at induction.
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.