STC data
ADS-B Out retrofits for pairing approvals, install data, and mandate compliance
For operators, avionics suppliers, MROs, this review is used when ADS-B equipage mandate. EE checks TSO-authorized equipment and approved pairings, installation approval data (STC or TC-holder SB), post-install performance verification reports against the approval basis, the configuration baseline, and the available DO-160G reports. The output gives avionics managers and installation engineers an evidence map, discrepancy register, request list, and closure plan for the records that need applicant, supplier, or authority disposition.
What gets reviewed
- Challenge TSO-authorized equipment and approved pairings against the claim it supports.
- Reconcile installation approval data (STC or TC-holder SB) against the claim it supports.
- Confirm post-install performance verification reports against the claim it supports.
- Index AFM supplement against the claim it supports.
- Compare approval basis against the claim it supports.
- Trace configuration definition against the claim it supports.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Source control: TSO-authorized equipment and approved pairings fails review if the cited record cannot be tied to the current baseline.
- Closure owner: installation approval data (STC or TC-holder SB) fails review if the cited record cannot be tied to the current baseline.
- Configuration match: post-install performance verification reports fails review if the cited record cannot be tied to the current baseline.
- The review notes that evidence link: AFM supplement fails review if the cited record cannot be tied to the current baseline.
- Limit carryover: approval basis fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
Common discrepancies
- Program risk: an unapproved GPS-transponder pairing.
- Authority question: an installation flagged as a non-performing emitter after return to service.
- Finding in records: foreign-registered aircraft needing separate acceptance of a US retrofit approval.
- Installer issue: baseline does not match the delivered records.
How the work runs
Frame Ads Out
Confirm the exact event, affected file set, buyer role, and decision standard before any tso-authorized equipment and approved pairings is treated as sufficient.
Trace STC Support
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 Evidence Retrofits
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Approvals Install
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
- Avionics managers use the map to brief the decision.
- Installation engineers use the register to assign closure.
- Owner representatives use the request list to collect source records.
How the work fits into the transaction or program
The decision is what approval path and data set an ADS-B Out retrofit needs under 14 CFR 91.225/91.227 and equivalent foreign mandates, especially the pairing of position source and transponder. The evidence set centers on TSO-authorized equipment and approved pairings, installation approval data (STC or TC-holder SB), post-install performance verification reports, and the AFM supplement. The likely weak points are an unapproved GPS-transponder pairing, an installation flagged as a non-performing emitter after return to service, and foreign-registered aircraft needing separate acceptance of a US retrofit approval. The output gives the avionics manager a cleanup register for ADS-B Out retrofits for pairing approvals, install data, and mandate compliance before ADS-B equipage mandate.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not grant certification credit, approve data, or sign return-to-service records. The package documents what was checked and what remains open for the responsible certification parties.
Specific to this review
- what approval path and data set an ADS-B Out retrofit needs under 14 CFR 91.225/91.227 and equivalent foreign mandates, especially the pairing of position source and transponder.
- TSO-authorized equipment and approved pairings often controls whether later summaries can be trusted.
- An unapproved GPS-transponder pairing is treated as a record gap until an owner closes it.
- FAA and EASA evidence should stay distinguishable from commercial claims and installer notes.
- The scope uses the Ads Out Retrofit STC question as the control point, so the review stays tied to ADS-B equipage mandate and the buyer decision behind it.
- The evidence starts with TSO-authorized equipment and approved pairings and follows Support Certification Evidence Retrofits 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 Avionics 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 Pairing Approvals Install 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 ADS-B Out Retrofit STC; 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.
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
Frequently asked questions
What makes this product-types review different from a general file audit?
The scope is tied to ads out retrofit stc and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block ads-b equipage mandate or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is tso-authorized equipment and approved pairings, 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 avionics 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.