FAA / Advisory circular

AC 20-152A

Development Assurance for Airborne Electronic Hardware

Development assurance for custom airborne hardware, COTS devices, COTS IP and circuit board assemblies.

Start with the scope.

This AC recognises DO-254/ED-80 and adds objectives for distinct hardware categories. Its stated applicability covers hardware contributing to DAL A, B and C functions; the relevant objective restrictions still apply.

The source, within reach.

Search within this AC, jump to a source page, or download the complete saved publication.

Download saved FAA PDF ↓

Read the source

The document, within reach.

FAA source document

Printed page 28

PDF page 28 of 31

Enlarge original ↗

Original FAA page; extracted words support search. Text reflow has not been reviewed.

Original FAA AC 20-152A, PDF page 28
AC 20-152A · 28Open saved PDF here ↗
Extracted text for finding words

This extraction supports search. Read the original page for complete notation and layout.

                     APPENDIX A. GLOSSARY

Abnormal conditions – Conditions that are inconsistent with specified normal operating
conditions.

Airborne electronic hardware – An electronic “hardware item” (see ED-80/DO-254 for
definition of “hardware item”) intended to be installed in airborne equipment/systems.

Batch – A manufacturing lot of a semiconductor device that is reproduced using the same
semiconductor fabrication process.

Commercial off-the-shelf (COTS) device – A device, integrated circuit or multi-chip module
developed by a supplier for a wide range of customers (not restricted to airborne systems), whose
design and configuration is controlled by the supplier or an industry specification. A COTS
device can encompass digital, analog, or mixed-signal technology. COTS electronic components
are generally developed by the semiconductor industry for the commercial market, not particular
to the airborne domain. These devices have widespread commercial use and are developed
according to the semiconductor manufacturer’s proprietary development processes.

COTS device usage – Definition of the used and unused functions that are implemented in the
device. This is further defined as an exhaustive list of conditions/constraints (such as
configuration settings, usage rules, protocol, timing constraints, input output (IO) interface, and
addressing schemes) associated with the performance characteristics of the used COTS
functions. Respecting the defined usage of the COTS will ensure the expected performance of
the device for a given set of constraints.

Commercial-off-the-shelf intellectual property (COTS IP) – Intellectual property (IP) refers
to design functions (design modules or functional blocks, including IP libraries) used to design
and implement a part of or a complete custom device such as a PLD, FPGA, or an ASIC.
Intellectual property is considered to be “COTS IP” when it is a commercially available function,
used by a number of different users in a variety of applications and installations. In this
document, the terminology “a/the COTS IP” refers to a piece of hardware that is COTS IP per
this definition. COTS IP is available in various source formats:

    a.  Soft IP
       Soft IP is COTS IP defined as register transfer level (RTL) code, captured in an HDL
       such as Verilog or VHDL, that may be readable or encrypted. It is instantiated by the IP
       user within the custom device HDL code or by selecting the COTS IP function in a
        library. Soft IP will be synthesized, placed and routed in the AEH custom device.

       In this document, the terminology “a/the Soft IP” refers to a piece of hardware that is Soft
       IP per this definition.

    b. Firm IP
      Firm IP is COTS IP defined as a technology-dependent netlist. It is instantiated within the

Saved from the FAA on November 17, 2026. All original pages are retained. Engineering explanations are presented separately below.

Aerospace Consulting / Engineering perspective

Define the hardware assurance approach by function and device.

Use the PHAC to identify intended functions, assurance levels, custom and COTS boundaries, and the evidence needed for each applicable objective. Keep supplier information, integration verification and system-level assumptions connected.

Discuss the system and hardware assurance approach →
Source edition and reading coverage

31 original pages. 0 pages have reviewed text reflows. Original-first pages retain the source layout, with extracted text available for finding words.

Source SHA-256: 06b17bec98562261063d87e518df3fe581412a5dce64b39ef4769c57433b6bc6

This is a dated source copy. Automatic source acquisition is not yet scheduled.

Original FAA PDF ↗

Working through a certification question?

Bring the aircraft, the basis and the issue your team needs to resolve.

Discuss your programme →