Surveillance TSO
TSO compliance evidence support for surveillance equipment
This support maps the evidence behind a surveillance article against its TSO authorization so a supplier can see where the package is thin before an authority does. It reads the transponder, ADS-B OUT, and antenna substantiation the way a reviewer will, tracing each referenced minimum performance standard and each DO-160G qualification test to a document that actually exists. An engineer who has assembled TSO packages runs it during evidence mapping, before submittal or in response to a finding. You get a standards map keyed to the article, a gap list ranked by closure difficulty, and a sequence for clearing each item.
When this review is needed
- A transponder or ADS-B article is heading for a TSO authorization application and the package needs a read before it goes in.
- An authority raised a finding on the surveillance substantiation and the response has to point to evidence, not assertions.
- A design change to the antenna or its installation reopened qualification and the affected TSO evidence has to be re-mapped.
- A prior authorization is being extended to a new part number and the reused evidence has to be checked for currency.
The problem
Surveillance articles carry evidence from several disciplines at once: radiated performance against the transponder and ADS-B minimum performance standards, DO-160G environmental qualification, software life-cycle data, and installation assumptions about antenna placement and cabling. The supplier who assembled it often cannot see which referenced test report is missing a revision or which performance claim rests on an analysis nobody finished, because the pieces were produced by different teams on different schedules.
What gets reviewed
- Transponder and ADS-B OUT performance claims traced to the minimum performance standards the TSO invokes
- DO-160G qualification categories declared for the article checked against test reports on file
- Antenna and installation assumptions stated in the substantiation and cross-checked to the qualification basis
- Software life-cycle evidence at the declared DAL mapped to the DO-178C data items
- Article authorization representation confirmed so the package presents as a coherent whole
What gets validated
- Each ADS-B and transponder performance figure resolves to a test report or analysis, not a specification restatement
- The declared DO-160G categories match the environmental conditions the article is being authorized for
- Antenna gain and placement assumptions in the substantiation agree with the qualification test setup
- Software DAL and its DO-178C data items are consistent with the surveillance function's failure classification
- Every referenced standard revision cited in the package is the one the evidence was actually produced against
Evidence normally required
- The TSO authorization application draft or the finding to be answered
- Transponder and ADS-B performance test reports and analyses
- DO-160G qualification test reports for the article
- Software life-cycle data and the declared DAL for the surveillance function
- Antenna and installation substantiation and drawings
Common discrepancies
- An ADS-B performance claim referenced to a standard with no test report closing it out
- DO-160G categories declared broader than the qualification testing actually covered
- Antenna placement assumptions in the substantiation that the qualification setup did not test
- A software data item at the declared DAL that the life-cycle evidence never produced
What is at stake
A package that references a standard without the report behind it draws a finding that stalls the authorization until the evidence is produced or the claim is withdrawn. On surveillance articles that late stall lands during the window when installers are already planning around an authorization date, so a missing antenna qualification test cascades into schedule cost well past the certification desk.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Anchor to the authorization
Fix the TSO the article is being authorized against and the performance standards it invokes.
Trace each claim
Follow every performance and qualification statement to the report or analysis that supports it.
Test the assumptions
Check that antenna, installation, and software assumptions agree across the package.
Rank and sequence
Order the gaps by closure difficulty against the submittal date.
What the buyer receives
- A standards map linking each surveillance performance claim to its supporting evidence
- A gap list ranked by how hard each item is to close before submittal
- A closure sequence that orders the evidence work against the authorization timeline
Who uses the output
- Certification engineers assembling the TSO application for the surveillance article
- Compliance managers deciding which gaps block submittal and which can follow
- Engineering leads directing which team produces the missing performance or qualification evidence
How the work fits into the transaction or program
The mapping runs between evidence generation and the authorization application, taking the reports the various teams produced and testing whether they present as one defensible package. Its gap list feeds the evidence work that has to close before the article goes to the authority, and its standards map becomes the reference the finding responses point back to.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
Surveillance mandates and their referenced performance standards diverge between the FAA airspace and the European system, so an article authorized under a TSO may face a different referenced revision when the same evidence is presented for European acceptance. The mapping notes where a performance claim rests on a standard revision that the other authority does not yet recognize.
Regulatory limits
The mapping reads the evidence and shows where it is complete or thin. It does not grant a TSO authorization, approve the article, or make an airworthiness determination on the surveillance function or its installation.
What this review does not cover
- Generating the missing performance, qualification, or software evidence
- Filing the TSO authorization application on the supplier's behalf
- Any installation approval or airworthiness determination on the fitted article
Specific to this review
- Surveillance performance claims are the ones authorities probe hardest because ADS-B integrity feeds airspace separation, so a thin transponder report is not a place to gamble.
- DO-160G categories are often declared aspirationally early in a program and never trimmed to what testing covered, which is where the map most often finds daylight.
- Antenna assumptions live in the installation substantiation but drive the article's qualification, so a mismatch between them reads as two documents describing two different products.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
Frequently asked questions
Can you re-map evidence we are reusing from an earlier transponder authorization?
Yes. Reused evidence is checked for currency against the standard revisions the new authorization invokes and for applicability to the new part number and configuration. Evidence that was valid for the earlier article does not always carry over cleanly, and the map shows where it does not.
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.