Skip to content

Product certification

VHF communications radio evidence review for DO-160G, DO-178C

This review is for equipment suppliers, avionics suppliers, OEMs responsible for VHF communications radio. It is triggered by comm-radio TSO authorization planning. EE checks channel-spacing, adjacent-channel rejection test data, transmitter/receiver performance results, plus the governing plan or application, against DO-160G, DO-178C. Discrepancies include missing source records, mismatched configuration, unsupported assumptions, or performance shown for 25 kHz but not 8.33 kHz where mandated. Output includes VHF communications radio gap register, Means of compliance map, Test and analysis request list.

When this review is needed

  • A new article, software load, or installation is moving into certification review.
  • Quality control needs a repeatable list of ready and open records.
  • Internal teams need a supplier request list tied to evidence gaps.
  • The buyer wants a defensible package before committing the claim.

The problem

Certification risk sits in the gap between the claimed basis and the records in the folder. With VHF communications radio, performance shown for 25 kHz but not 8.33 kHz where mandated can stay hidden until the exact source record is requested.

What gets reviewed

  • Review channel-spacing against the configuration, installation, or claim under review.
  • Compare adjacent-channel rejection test data against the configuration, installation, or claim under review.
  • Trace transmitter/receiver performance results against the configuration, installation, or claim under review.
  • Challenge dO-178C software data for control logic against the configuration, installation, or claim under review.
  • Reconcile dO-160G environmental categories. against the configuration, installation, or claim under review.

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

  • Pass check: channel-spacing must match the released configuration and the claimed means of compliance.
  • Configuration check: adjacent-channel rejection test data must match the released configuration and the claimed means of compliance.
  • Trace check: transmitter/receiver performance results must match the released configuration and the claimed means of compliance.
  • Rationale check: dO-178C software data for control logic must match the released configuration and the claimed means of compliance.
  • Closure check: dO-160G environmental categories. must match the released configuration and the claimed means of compliance.

Evidence normally required

  • Controlled channel-spacing
  • Released adjacent-channel rejection test data
  • Signed transmitter/receiver performance results
  • Current dO-178C software data for control logic
  • Archived dO-160G environmental categories.
  • Supplier application data

Common discrepancies

  • Gap: performance shown for 25 kHz but not 8.33 kHz where mandated.
  • Mismatch: adjacent-channel rejection failing at the band edges.
  • Unsupported claim: control-head software data that does not match the fielded configuration.

What is at stake

A weak package can convert a planned review into a long question log. If adjacent-channel rejection failing at the band edges, the program may need new evidence before the claim can proceed.

How the work runs

01

Frame Vhf Radio

Confirm the exact event, affected file set, buyer role, and decision standard before any channel-spacing is treated as sufficient.

02

Trace C169a Evidence

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.

03

Sort Communications 160g

Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.

04

Package Product Certification

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

  • VHF communications radio gap register
  • Means of compliance map
  • Test and analysis request list
  • Interface closure plan

Who uses the output

  • Certification engineer assign closure actions from the exception register.
  • avionics engineer use the map to locate source evidence.
  • Product manager decide what can proceed and what must wait.

How the work fits into the transaction or program

What a VHF communications transceiver must substantiate for TSO-C169a, distinct from the generic communication-equipment page because the decisive evidence is 8.33 kHz channel-spacing performance, spectral and audio quality, and DO-178C data for the tuning/control software. The evidence set centers on channel-spacing and adjacent-channel rejection test data, transmitter/receiver performance results, DO-178C software data for control logic, and DO-160G environmental categories. The likely weak points are performance shown for 25 kHz but not 8.33 kHz where mandated, adjacent-channel rejection failing at the band edges, and control-head software data that does not match the fielded configuration. The output gives the certification engineer a cleanup register for VHF communications radio before comm-radio TSO authorization planning.

Start with a single asset

Reduce finding cycles by checking the package first.

Regulatory limits

The output supports applicant decision making and authority discussions. It does not replace required approvals, designee findings, conformity activity, or airworthiness determinations.

What this review does not cover

Specific to this review

  • Configuration identity matters because evidence from another baseline may prove a different article, load, or installation.
  • A useful trail names the source record, revision, owner, and closure decision for each claim.
  • The exception list separates document-control cleanup from gaps that need engineering substantiation.
  • The finding pattern for this page is specific: performance shown for 25 kHz but not 8.33 kHz where mandated changes the strength of the certification argument.
  • The scope uses the Vhf Radio TSO C169a question as the control point, so the review stays tied to Comm-radio TSO authorization planning and the buyer decision behind it.
  • The evidence starts with Channel-spacing and follows Evidence Review Communications 160g 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 engineer: 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 178c Product Certification Channel questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
  • The handoff value comes from VHF communications radio gap register; it gives the next reviewer a precise map instead of another broad request for a better file.

Sources

Frequently asked questions

What makes this product-types review different from a general file audit?

The scope is tied to vhf radio tso c169a and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block comm-radio tso authorization planning or can be closed later without changing the decision.

What evidence has to be available before this work starts?

The starting point is channel-spacing, 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 engineer 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.