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 20

PDF page 20 of 31

Enlarge original ↗

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

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

        Note: The term “COTS device” used in this document applies to a semiconductor
         product that is fully encapsulated in a package. This term does not apply to circuit
        board assemblies.

6.1     Background
      COTS devices continue to increase in complexity and are highly configurable. COTS
         devices provide “off-the-shelf” already developed functions, some of which are highly
        complex. Their development and production processes undergo a semiconductor
         industry qualification based on their intended market (consumer, automotive, telecom,
           etc.). Their usage by the aerospace industry provides additional integration and higher
        performance capabilities than were possible in the past.
       The design data for these COTS devices are usually not available to the COTS user.
        Since these devices are generally not developed for airborne system purposes,
         assurance has not been demonstrated that the rigor of a COTS manufacturer’s
        development process is commensurate with the aviation safety risks.
       ED-80/DO-254 introduces a basis for the development assurance for the use of COTS
         devices in Section 11.2, “COTS components usage.” This section states that “the use of
      COTS components will be verified through the overall design process, including the
         supporting processes.”
        Since ED-80/DO-254 was released in the year 2000, the number of functions embedded
        and integrated in a single COTS device has significantly increased. Functions which
        were previously split into various components, making the interface between those
        components accessible for verification, are now embedded within a single chip. While
         there are clearly some benefits of integrating more functions within a device, the
         increased level of integration makes it difficult for the user to verify the different
        hardware functions in the device due to lack of access to the interfaces between
         functions. Since these devices are more complex and highly configurable than the older
         separate devices, the risk is greater that the COTS device will not achieve the intended
         function in particular use cases over the required operating conditions.
         Furthermore, some additional assurance is needed because design errors may still be
         discovered after the COTS device is released to the market, or when an applicant
         extends the use of the device beyond the manufacturer’s specifications.

6.2      Applicability to COTS devices
         Section 6 is applicable to digital, hybrid, and mixed-signal COTS devices that
         contribute to hardware DAL A, B, or C functions. For COTS devices contributing to
        hardware DAL C functions, a limited set of the objectives of this section will apply.
         Section 6 is also applicable to FPGA and PLD devices that embed Hard IP (see
          definition) in their produced/manufactured silicon, but only for the COTS part of the
       FPGAs/PLDs.
         Section 6.4 only applies to COTS devices that are complex, as determined by the
         following COTS complexity assessment.


                                         20

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 →