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 15

PDF page 15 of 31

Enlarge original ↗

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

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

         Objective IP-1
        The applicant should select a COTS IP that is considered to be an acceptable solution,
        based on at least the following criteria:
           1.  The IP is technically suitable for implementing the intended function;
           2.  The description of the COTS IP architecture or IP design concept provides an
            understanding of the functionality, modes, and configuration of the IP. The
             description should also include an understanding of the source format or
            combination of source formats of the COTS IP;
           3.  The availability and quality of data and documentation allow the understanding of
               all aspects of the COTS IP functions, modes, and behavior, and enable the
             integration and verification of the COTS IP (e.g., datasheets, application notes,
            user guide, knowledge of errata, etc.);
           4.  Information exists for the IP user to be able to create the physical implementation
             of the COTS IP (e.g., synthesis constraints, usage and performance limits, physical
            implementation, and routing instructions);
           5.   It can be demonstrated that the COTS IP fulfills its intended function.

         5.11.3.2    Assessment of the COTS IP Provider & COTS IP Data

         Objective IP-2
        The applicant should assess the COTS IP provider and the associated data of the COTS
        IP based on at least the following criteria:
           1.   The IP provider provides all the information necessary for the integration of the
          COTS IP within the custom device and to support the implementation of the
          COTS IP within the device (e.g., synthesis constraints, usage domain,
             performance limits, physical implementation, and routing instructions);
           2.   The configurations, selectable options, and scalable modules of the COTS IP
              design are documented so that the implementation of the COTS IP can be
              properly managed;
           3.   The COTS IP has been verified by following a trustworthy and reliable process,
            and the verification covers the applicant’s specific use case for the COTS IP
               (including the used scale for scalable IP and the IP functions selected for
               selectable functions);
           4.   The known errors and limitations are available to the IP user, and there is a
              process to provide updated information to the IP user;
           5.   The COTS IP has service experience data that shows reliable operation for the
               applicants specific use case for the COTS IP.
        The assessment should be documented. The results of the assessment should be
         submitted for certification.



                                         15

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 →