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 21

PDF page 21 of 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

6.3    COTS Complexity Assessment
         In order to define which COTS devices are complex, the following high-level criteria
        should be used, considering all functions of the device, including any functions
         intended to be unused:
     A COTS device is complex when the device:
          1. Has multiple functional elements that can interact with each other; and
          2.  Offers a significant number of functional modes; and
          3.  Offers configurability of the functions, allowing different data/signal flows and
              different resource sharing within the device.
       Or when the device:
          4.  Contains advanced data processing, advanced switching, or multiple processing
            elements (e.g. multicore processors, graphics processing, networking, complex bus
             switching, interconnect fabrics with multiple masters, etc.)
        For complex COTS devices, it is impractical to completely verify all possible
         configurations of the device, and it is difficult to identify all potential failures.

         Objective COTS-1
        The applicant should assess the complexity of the COTS devices used in the design
        according to the high-level criteria of Section 6.3, and document the list of relevant
         devices (see note 1), including the classification rationale, in the PHAC or any related
        hardware planning document.
        Note 1: The applicant is not expected to assess the complete bill of material to satisfy
         the above objective, but only those devices that are relevant for the classification,
         including devices that are at the boundary between simple and complex. The resulting
          classification (simple or complex) for those devices that are at the boundary and those
          that are definitely complex should be documented.
        Note 2: A classification rationale is required for those devices that are at the boundary
         (meeting a part of the high-level criteria) and are classified as simple.
       Some examples of classification are provided in AC 00-72 for illustration.

6.4     Development Assurance for Use of Complex COTS
        ED-80/DO-254, Section 11.2.1, identifies some electronic component management
         process items when using a COTS device. ED-80/DO-254, Section 11.2.2, and Section
         6.1 of this document, identify some concerns with using a COTS device. The following
         objectives acknowledge and supplement ED-80/DO-254, Section 11.2 in clarifying how
          to gain certification credit when using complex COTS devices.

6.4.1    Electronic Component Management Process
       As stated in ED-80/DO-254, Section 11.2, “the use of an electronic component
       management process, in conjunction with the design process, provides the basis for
      COTS components usage.”

                                         21

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 →