Communication hardware
DO-254 hardware assurance evidence support for communication equipment
This service examines the DO-254 evidence behind a communication radio's airborne electronic hardware and confirms it demonstrates the assurance the certification plan asserts. It fits VHF and HF radios, datalink units, and their custom logic devices. Working from the hardware plans, a specialist confirms that requirements, design, verification, and configuration data hang together and match the DAL the safety assessment assigns. The output is an objective-by-objective standards map, a gap list ordered for efficient closure, and a route to clear each open item before the package reaches an authority.
When this review is needed
- A radio or datalink unit is entering TSO authorization and its hardware assurance evidence needs a read against the plan.
- A finding landed on the communication hardware and the team must locate which DO-254 objective it belongs to.
- A logic device on the radio board changed and the verification evidence has to be shown current for the new build.
- An acquired design is being carried forward and its DO-254 pedigree was never confirmed by the current team.
The problem
Communication hardware tends to accumulate reuse: a logic device carried from an earlier program, a supplier core dropped into the design, a board revision that outran its verification. DO-254 assurance depends on being able to show the current build was verified against captured requirements, and reused elements are where that thread most often frays. The evidence can look complete while the trace for the reused block is missing or points at an older revision.
What gets reviewed
- Requirements capture for the communication hardware and the rationale behind derived requirements
- Design data assessed against the DAL the safety assessment assigns to the radio function
- Verification results tied to each hardware requirement, with reused elements identified
- Assurance treatment of any supplier core or carried-over logic device
- Configuration records that fix the verification to a specific board revision
- The path from derived hardware requirements into the safety assessment
What gets validated
- Reused logic blocks carry verification against the current build, not only the program they came from
- Every hardware requirement links to a verification result and a design element
- The DAL used for the radio hardware agrees with the safety assessment
- Supplier-provided cores carry the assurance data the plan requires to credit them
- Verification records name the same board revision that the configuration baseline fixes
Evidence normally required
- The hardware plans and verification plan for the communication unit
- Requirements, design, and verification data for the airborne electronic hardware
- Assurance data for any supplier core or reused logic device
- The safety assessment that sets the DAL for the radio function
- The certification basis and prior findings on the hardware
Common discrepancies
- A reused logic block credited from an earlier program without verification against the current build
- A supplier core relied on with no assurance data to substantiate the credit taken
- Verification tied to a board revision superseded by the submitted configuration
- Derived requirements from the datalink logic that never reached the safety assessment
What is at stake
A submittal that rests on unverified reuse invites a finding that forces re-verification of the reused hardware, which is slow and expensive to run late in a program. For a radio tied to a fleet installation schedule, a DO-254 stall on the hardware pushes the whole approval, and the reused block that seemed like a shortcut becomes the critical path.
Move from findings to resolution
Identify gaps against the means of compliance.
How the work runs
Fix the assurance level
Confirm the DAL the safety assessment assigns to the communication function and the objectives it triggers.
Isolate the reuse
Identify carried-over logic and supplier cores, then check whether their assurance data supports the credit taken.
Verify the current build
Confirm verification results map to the submitted board revision, not a superseded one.
Order the gaps
Rank open objectives by closure effort so re-verification, if needed, is scheduled honestly.
What the buyer receives
- A standards map covering each DO-254 objective for the communication hardware
- A gap list sequenced by closure effort, with reused elements called out
- A closure route from open finding to the evidence that resolves it
Who uses the output
- Certification leads gauging submittal readiness for the radio package
- Hardware engineers closing the trace on reused and supplier-provided elements
- Compliance managers watching open objectives against the program schedule
How the work fits into the transaction or program
The mapping runs after hardware verification is nominally complete and before the compliance package goes to the authority. It gives the reused and carried-over elements the scrutiny a reviewer will apply, so a supplier learns where the assurance thread breaks while there is still time to reverify, not after a finding forces it.
Start with a single asset
Confirm requirements trace through verification.
Jurisdiction-specific considerations
Both the FAA and EASA credit DO-254 for airborne electronic hardware, and both scrutinize how a supplier substantiates reused or supplier-provided logic. Where the evidence leans on credit taken from a prior program, the mapping notes whether that credit will read the same way to each authority under the applicable certification basis.
Regulatory limits
This work maps evidence to the DO-254 objectives and locates gaps. It does not approve the radio hardware, issue a TSO or STC, make an airworthiness determination, or stand in for the authority's acceptance of the package.
What this review does not cover
- Producing the hardware requirements, design, or verification data
- Executing or witnessing the hardware verification runs
- Granting an approval or compliance finding on the authority's behalf
Specific to this review
- Reused logic is the recurring DO-254 weak point on radio boards, because credit taken from an earlier program rarely comes with verification against the current build.
- A supplier core can be perfectly good hardware and still fail DO-254 credit if the assurance data behind it never travels with the design.
- Board revisions on communication hardware often outrun their verification, so the configuration baseline is checked against the actual test records rather than assumed.
Sources
RTCA. Design assurance objectives and lifecycle data for airborne electronic hardware (FPGA/ASIC/PLD).
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Frequently asked questions
We reused a logic device from a prior certified program. Does that credit carry over?
Only if the assurance data supports it against the current design and build. Credit from a prior program is not automatic under DO-254; the mapping checks whether the reused element was verified in this context or still needs work.
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.