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 14

PDF page 14 of 31

Enlarge original ↗

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

Original FAA AC 20-152A, PDF page 14
AC 20-152A · 14Open 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

5.11.2   Applicability to COTS IP
         Section 5.11 is applicable to COTS IP used in a custom device that meets the definition
         of “commercial-off-the-shelf intellectual property” in the Appendix A Glossary. This
        scope encompasses digital, analog, and mixed-signal COTS IP.
        Note: Analog COTS IP is within the above-mentioned scope, as it could be instantiated
         within a custom mixed-signal device.
         Section 5.11 is applicable to COTS IP contributing to hardware DAL A, B, or C
         functions.
         Section 5.11 is applicable to Soft IP, Firm IP, and Hard IP that are inserted within a
        custom device by the applicant. However, Section 5.11 does not apply to Hard IP that is
       embedded in the silicon of an FPGA or a PLD by the FPGA/PLD device manufacturer.
        This type of IP is considered to be part of the COTS device, and is covered in Section
          6, Use of Commercial Off-the-Shelf Devices.

5.11.3   Development Assurance for COTS IP
     A COTS IP development assurance approach should be based on the category of the
      COTS IP (soft, firm, hard) and on the identified risks of failure due to a design error in
         the COTS IP itself or an error in the way it is used in the custom device.
        This section provides objectives addressing development assurance when using COTS
          IP. These objectives are intended to cover the particular aspects of development when
         using COTS IP, and are expressed in connection with the custom device development
         process that follows ED-80/DO-254 and the custom device objectives of this document.
       The development aspects related to COTS IP start from the custom device process that
         captures the allocated requirements for the function that will be performed by the
      COTS IP. From this entry point, the following aspects provide a basis to define the
        development assurance objectives for the use of COTS IP:
        •   Selection of the COTS IP,
        •  Assessment of the IP provider and the IP data,
        •  Planning activities, including the verification strategy,
        •   Definition of the requirements/derived requirements,
        •  Design integration, implementation, and verification of the COTS IP in the custom
             device.

         5.11.3.1     Selection of the COTS IP to implement the function
      COTS IP can be available in different forms/source formats and various levels of
          quality. Some COTS IP may not be acceptable for use in airborne systems. The
         selection criteria below are intended to address the essential characteristics that are
         considered a minimum for the use of IP in custom AEH devices.




                                         14

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 →