STC data
STC ownership under 21.47 for rights, permission letters, and the records that prove them
This review supports OEMs, operators, Certification teams during STC acquisition, licensing, or permission dispute. EE reads STC and its current holder of record, transfer endorsements, right-to-use permission letters behind each installation against configuration records, approval assumptions, and the cited source material. The buyer receives a concise package showing what is proven, what is inconsistent, and what should be resolved before submittal, installation, import, or purchase.
What gets reviewed
- Trace STC and its current holder of record against the claim it supports.
- Challenge transfer endorsements against the claim it supports.
- Reconcile right-to-use permission letters behind each installation against the claim it supports.
- Confirm holder viability for future ICA and support against the claim it supports.
- Index approval basis against the claim it supports.
- Compare configuration definition against the claim it supports.
What gets validated
- Limit carryover: STC and its current holder of record fails review if the cited record cannot be tied to the current baseline.
- Source control: transfer endorsements fails review if the cited record cannot be tied to the current baseline.
- Closure owner: right-to-use permission letters behind each installation fails review if the cited record cannot be tied to the current baseline.
- Configuration match: holder viability for future ICA and support fails review if the cited record cannot be tied to the current baseline.
- Evidence link: approval basis fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
Common discrepancies
- Buyer concern: installations performed without the holder's permission evidence.
- Program risk: STCs bought in asset deals but never re-registered.
- Authority question: defunct holders leaving fleets with unamendable approvals.
- Finding in records: diligence discovering the seller never owned the STC it embodied fleet-wide.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Frame STC Transfer
Confirm the exact event, affected file set, buyer role, and decision standard before any stc and its current holder of record is treated as sufficient.
Trace Records Review
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Under Permission
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Prove Them
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
Who uses the output
- certification managers use the map to brief the decision.
- corporate development leads use the register to assign closure.
- fleet engineers use the request list to collect source records.
How the work fits into the transaction or program
The whether the party claiming rights to use or amend an STC actually holds them under 21.47, and what evidence supports installations - permission statements, licensing, or ownership transfer filed with the FAA; the STC and its current holder of record, transfer endorsements, right-to-use permission letters behind each installation, holder viability for future ICA and support. The evidence set centers on the STC and its current holder of record, transfer endorsements, right-to-use permission letters behind each installation, holder viability for future ICA and support. The likely weak points are installations performed without the holder's permission evidence, STCs bought in asset deals but never re-registered, defunct holders leaving fleets with unamendable approvals, diligence discovering the seller never owned the STC it embodied fleet-wide. The output gives the certification manager a cleanup register for STC ownership under 21.47 for rights, permission letters, and the records that prove them before STC acquisition, licensing, or permission dispute.
Start with a single asset
Confirm requirements trace through verification.
Regulatory limits
EE does not certify equipment, approve installations, or declare an aircraft compliant. The output identifies supportable claims, missing records, and questions that need applicant or authority disposition.
Specific to this review
- whether the party claiming rights to use or amend an STC actually holds them under 21.47, and what evidence supports installations - permission statements, licensing, or ownership transfer filed with the FAA.
- STC and its current holder of record often controls whether later summaries can be trusted.
- Installations performed without the holder's permission evidence is treated as a record gap until an owner closes it.
- FAA evidence should stay distinguishable from commercial claims and installer notes.
- The scope uses the STC Transfer Rights Records question as the control point, so the review stays tied to STC acquisition, licensing, or permission dispute and the buyer decision behind it.
- The evidence starts with STC and its current holder of record and follows Review Ownership Under Permission references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for certification manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Letters Prove Them Data questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Evidence map for STC Transfer 21 47 Rights And; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
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.
Frequently asked questions
What makes this standards review different from a general file audit?
The scope is tied to stc transfer rights records and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block stc acquisition, licensing, or permission dispute or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is stc and its current holder of record, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives certification manager a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.