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 18

PDF page 18 of 31

Enlarge original ↗

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

Original FAA AC 20-152A, PDF page 18
AC 20-152A · 18Open 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.  Tool assessment and qualification aspects when the applicant uses a
                           tool to perform design and/or verification steps for the COTS IP.

         5.11.3.4    Requirements for COTS IP Function and Validation
                 Custom device requirements typically contain requirements that relate to
                      the function supported by the COTS IP. The granularity of these
                     requirements may be very different depending on the COTS IP function
                   and the visibility of the functions supported by the IP at the custom device
                         level.
                  Depending on the extent of requirements-based testing as a part of the
                   chosen verification strategy of the COTS IP, the level of detail and the
                       granularity of the AEH custom device requirements may need to be
                      refined to specifically address the COTS IP functions and the
                    implementation of the COTS IP.
                      In addition, requirements should be captured to encompass all the
                     necessary design details used to connect, configure, and constrain the
              COTS IP and properly integrate it into the AEH custom device.

                     Objective IP-6
                  The requirements related to the allocated COTS IP functions should be
                    captured to an extent commensurate with the verification strategy.
                      In addition, derived requirements should be captured to cover the
                     following aspects associated with the integration of the COTS IP into the
                   custom device design:
                          1. COTS IP used functions (including parameters, configuration,
                          selectable aspects),
                          2.  Deactivation or disabling of unused functions,
                          3.  Correct control and use of the COTS IP, in accordance with the data
                      from the COTS IP provider.
               When the applicant chooses a verification strategy (see Section 5.11.3.3.2)
                        that solely relies on requirements-based testing, the “extent commensurate
                    with the verification strategy” corresponds to a complete requirement
                     capture of the COTS IP following ED-80/DO-254.
                   Regarding the validation aspects, the COTS IP requirements should be
                      validated as a part of the validation process of the AEH custom device.

         5.11.3.5     Verification
                 The applicant should ensure that the COTS IP is verified as a part of the
                       overall custom device verification process per ED-80/DO-254 and based
                  on the verification strategy for the COTS IP that has been described in the
              PHAC or a related planning document.


                                         18

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 →