Surveillance avionics
Surveillance equipment certification data support
Surveillance equipment certification is the path a supplier follows to authorize a transponder, traffic-awareness, or collision-avoidance article and substantiate that what it reports about the aircraft and its surroundings is correct and timely. It is used by avionics teams whose unit replies to interrogation or builds a traffic picture the crew acts on. The data support covers the certification basis, the report-accuracy and latency case, the environmental qualification, and the software lifecycle data behind the surveillance logic. You receive a gap read against the applicable standards and an evidence set arranged for review.
When this review is needed
- A transponder or traffic-awareness article is heading toward authorization and the report-accuracy case has to be built against the basis.
- A unit changes how it derives or broadcasts its position report and the evidence has to reflect the change.
- Findings against the report content or latency have stalled the program and need reconciling.
- A supplier wants an independent read of the surveillance package before the basis is locked.
The problem
A surveillance article is judged on the truth and freshness of what it reports, which depends on inputs it does not own. The position report inherits the quality of the source feeding it, the latency budget gets spent across the chain without anyone holding the total, and the logic that decides what to broadcast or alert on carries a level set for a benign failure rather than a wrong or stale report. The weaknesses stay invisible until a reviewer follows a report back to the source it trusts.
What gets reviewed
- The certification basis and the article authorization the surveillance unit is pursued under
- The report-accuracy case and the quality the unit inherits from its position source
- The latency budget across the surveillance chain and where the unit spends it
- DO-160 environmental qualification scoped to the installed location
- Software lifecycle data matched to the consequence of a wrong or stale report
- Antenna and interrogation behavior the installation will depend on
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
- Report accuracy accounts for the quality of the source feeding the unit
- The latency budget is owned end to end, not spent piecemeal across the chain
- DO-160 categories match the install location and antenna environment
- Software lifecycle data matches the level a wrong-report hazard assigns
- Source-loss and source-degraded behavior is specified and verified
Evidence normally required
- The draft or current certification basis for the surveillance article
- The report-accuracy and latency characterization to date
- DO-160 qualification test plans and reports so far
- Software lifecycle data for the surveillance logic at its current state
- Open findings or prior authority correspondence if a program is running
Common discrepancies
- Report accuracy claimed without accounting for the source quality the unit inherits
- A latency budget with no single owner, so the chain total exceeds the claim
- Software level set for a loss when the hazard is a wrong or misleading report
- Source-degraded behavior unspecified, so a bad input has no defined response
- Antenna performance characterized against an installation the unit will not see
What is at stake
A surveillance unit whose report-quality case is thin draws findings that reach back into the sources it depends on, widening the scope of the rework. The schedule slips, the dependency on other articles complicates the fix, and the engineering effort lands across more than the box itself.
How the work runs
Confirm the basis
Establish the certification basis and the report the surveillance article is authorized to produce.
Trace the inputs
Account for the source quality the report inherits and the obstructions the antenna faces in the install.
Own the latency
Hold the latency budget end to end across the chain rather than letting each stage spend it.
Reconcile the case
Align the software level with the wrong-report hazard and deliver a prioritized closure list.
What the buyer receives
- A gap read against the applicable surveillance-article authorization and standards
- A reconciled compliance matrix tied to the report-quality and latency evidence
- A traceability view from surveillance requirements through verification
- A prioritized list of the data needed to close the package
Who uses the output
- Certification leads compiling the surveillance submittal
- Surveillance engineers owning the end-to-end latency budget
- Integration teams reconciling the unit with the position source it depends on
How the work fits into the transaction or program
The work supports the supplier's surveillance program and traces the report quality back through the inputs the unit inherits. It complements a navigation read where the position source is in scope, and it feeds the safety assessment with the wrong-report hazard the logic has to address.
Start with a single asset
Confirm requirements map to substantiating evidence.
Aircraft-specific considerations
An antenna's report quality depends on where it mounts and what masks it, so a belly-mounted transponder on a transport aircraft and a blade antenna on a light platform face different obstructions. The read keeps the antenna characterization tied to the installation the unit will actually see.
Regulatory limits
Endeavor Elements supports the applicant's surveillance-article data. It does not grant an authorization, make report-quality findings for the authority, or warrant operational acceptance. The applicant submits and the authority decides.
What this review does not cover
- Granting an article authorization or operational surveillance approval
- Making compliance findings on the authority's behalf
- Conducting the antenna or interrogation testing itself
Specific to this review
- A surveillance report is only as good as the source it inherits from, so the accuracy case has to account for input quality the unit does not control.
- Latency is a budget spent across the whole surveillance chain, and a unit that does not own the end-to-end total is a recurring finding.
- The hazard for surveillance is usually a wrong or stale report rather than a clean loss, which raises the software level above a simple availability case.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
RTCA. Objectives and lifecycle data for airborne software assurance, by design assurance level (DAL A-E).
RTCA. Environmental qualification test categories and procedures referenced by TSO and equipment qualification.
SAE International. Safety assessment methods (FHA, PSSA, SSA, FTA, FMEA) supporting development assurance level assignment.
Frequently asked questions
Why is a wrong report worse than a lost one for surveillance?
A dropped report tells the crew nothing; a wrong report tells them something false they may act on. That raises the software level above an availability case, and the read checks the lifecycle data against the misleading-report hazard.
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.
Walk through your situation with an engineer who has done this work.