Mods across registries
Modification and STC status in the import and export package
A modification embodied under one authority does not automatically carry its approval onto another registry, which makes the modification status report the most import-sensitive document in the package. This review verifies that each listed modification and STC was actually embodied on this serial number, that its approval data exists, and that an acceptance route to the importing registry is identifiable. It is carried out during import, export, or registry-change preparation. The transition lead receives an exception list separating supported modifications from those needing validation, substantiation, or removal decisions.
When this review is needed
- The aircraft carries STCs approved by the exporting state and the destination registry applies different acceptance rules.
- A prior operator handed down the modification status report and its embodiment claims are unverified.
- Cabin, avionics, or connectivity modifications were installed mid-lease with paperwork spread across several parties.
- Early certainty is needed on whether any installed modification requires validation or removal, because the export timeline hangs on it.
The problem
Modification records accumulate across owners, installers, and design organizations, and the status report is a summary of summaries. It lists what someone once recorded as embodied, under approvals that made sense on the registry of the day. The receiving authority asks a harder question: show the approval, show the embodiment on this airframe, and show why that approval means anything under our system. Few packages answer all three without work.
What gets reviewed
- Every entry on the modification and STC status report, verified for embodiment evidence on this serial number
- Approval data behind each modification: STC certificates, SB references, or other approved data
- Effectivity of each STC and major modification for this specific MSN and configuration
- Acceptance position of each approval under the importing registry's framework, including bilateral routes
- Consistency of the modification status with the equipment list and weight and balance amendments
- Classification checks where installed changes may have been treated as repairs or minor when they were not
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 embodiment traces to a logbook entry, work order, or task card on this aircraft
- The approval document behind each modification is present and covers the configuration installed
- STC effectivity lists include this serial number, or an amendment extends them to it
- Every approval has an identifiable acceptance route to the destination registry or is flagged as needing validation
- Downstream records affected by each modification, equipment list and weight and balance included, reflect it
Evidence normally required
- The current modification and STC status report
- STC certificates, approved data packages, and SB accomplishment records referenced by the report
- Logbook entries, work orders, and task cards evidencing embodiment
- The equipment list and weight and balance file at current revision
- The draft import or export application and any authority correspondence on modifications
Common discrepancies
- An STC embodied under the exporting state's approval with no acceptance path yet identified for the destination registry
- A modification listed as embodied that has no logbook entry or work record on this airframe
- An effectivity list that does not include this MSN, with no amendment or follow-on approval located
- Minor modifications that changed installed equipment without ever reaching the status report
What is at stake
An unsupported modification discovered late forces one of three expensive outcomes: a validation effort with a design organization on the critical path, a substantiation hunt across parties with no remaining obligation to respond, or physical removal of the installation before the registry change. Each of these costs more than the review that would have exposed the gap months earlier, and each can move the transfer date.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Verify embodiment
Trace each status-report entry to work records proving it was installed on this airframe.
Assemble approvals
Locate the approval data behind each modification and check its coverage of the installed configuration.
Assess acceptance
Determine the route each approval has onto the destination registry, or flag the absence of one.
Report decisions needed
Deliver the register with each open entry framed as a substantiation, validation, or removal decision.
What the buyer receives
- A verified modification register separating supported, unsupported, and validation-required entries
- An acceptance-route assessment per modification for the destination registry
- An exception list with the substantiation, validation, or removal decision each open item requires
Who uses the output
- Transition leads sequencing validation work before the registry date is fixed
- Certification and engineering staff engaging design organizations on acceptance routes
- Asset managers pricing the cost of carrying, validating, or removing contested installations
How the work fits into the transaction or program
Modification status connects the records package to the certification world: its findings determine what the equipment list must show, what the weight and balance file must have amended, and what the importing authority's design-acceptance side will ask. Reviews of those neighboring record sets consume this one's output, so it runs ahead of them in the package sequence.
Jurisdiction-specific considerations
Between the FAA and EASA systems, bilateral agreements define which design approvals transfer with limited or no additional showing and which need validation; 14 CFR Part 21 and EU Regulation 748/2012 frame the two sides. Transfers involving a third-country registry add that state's own acceptance rules. The direction of transfer therefore changes which modifications on the same aircraft become the problem entries.
Regulatory limits
Identifying an acceptance route is analysis, and the limits around it are firm: the review approves nothing, validates nothing, and does not represent any authority's position. Whether a given approval is accepted on the destination registry is decided by that authority, and design-approval work belongs to the appropriately approved organizations.
What this review does not cover
- Performing or managing STC validation projects
- Preparation of design substantiation or approved data
- Physical survey of installed modifications against drawings
Specific to this review
- The direction of transfer matters as much as the modification itself: an installation unremarkable on the exporting registry can be the single blocking item on the destination one.
- Connectivity and cabin systems installed mid-lease produce the highest rate of unsupported entries, because installation, design approval, and record-keeping were split across parties.
- Removal is sometimes the rational answer for a low-value installation with an expensive validation path, but only if the decision is made early enough to schedule the work.
- Modification findings cascade: one unsupported mod typically reopens the equipment list and the weight and balance amendment chain built on top of it.
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
How early in a transfer should modification status be reviewed?
As soon as the destination registry is known. Validation projects and design-organization engagement run on calendars measured in months, and they only start once an unsupported modification is identified. Every week of earlier notice comes off the critical path.
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.