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 3

PDF page 3 of 31

Enlarge original ↗

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

Original FAA AC 20-152A, PDF page 3
Extracted text for finding words

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

10/7/22                                                 AC 20-152A

       The applicant should document in the Plan for Hardware Aspects of Certification
       (PHAC), or any other related planning document, the process and activities that the
         applicant intends to perform to satisfy the objectives of this AC. The PHAC, as well as
         those related planning documents should be submitted for certification.

5    CUSTOM DEVICE DEVELOPMENT
        This section provides guidance for the development assurance of programmable logic
         devices (PLDs), field programmable gate arrays (FPGAs), or application specific
         integrated circuits (ASICs), which are collectively referred to as “custom devices.”
        These custom devices are addressed in ED-80/DO-254, Section 1.2, Item 3 as “custom
        micro-coded components.”
        Developing a custom device demands a well-defined development process. However, it
           is understood that the process to develop complex custom devices requires more
        comprehensive activities and artifacts than for a simple device.
        •  Section 5.1 identifies custom devices that are within the scope of this AC.
        •  Section 5.2 provides guidance on simple/complex classification for custom devices.
        •  Section 5.3 provides guidance on development assurance for complex custom
             devices.
        •  Section 5.4 provides guidance on development assurance for simple custom
             devices. In particular, Section 5.4 defines which Sections from 5.5 to 5.11 are
             applicable to the development assurance of simple electronic devices.
        •  Sections 5.5 through 5.10 provide clarifications on ED-80/DO-254.
        •  Section 5.11 provides background information and guidance specific to COTS IP
           used in custom devices.

5.1      Applicability to Custom Devices
         Section 5 is applicable to a digital or mixed-signal custom device that contributes to
        hardware DAL A, B, or C functions.
        Appendix A to ED-80/DO-254 modulates the ED-80/DO-254 life cycle data based on
         the DAL allocated to the hardware function. This document recognizes Appendix A for
         the modulation of the life cycle data according to the hardware DAL for the
        development of custom devices.

5.2     Simple/Complex Classification
       ED-80/DO-254 introduces the notion of simple and complex hardware items. This
         section clarifies and provides criteria that could be used to classify a device as simple
       by considering the design content of the custom device, and subsequently, the ability to
        comprehensively verify the device.
     A hardware custom device is classified as simple only if a technical assessment of the
         design content supports the ability of the device to be verified by a comprehensive

                                          3

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 →