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 5

PDF page 5 of 31

Enlarge original ↗

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

Original FAA AC 20-152A, PDF page 5
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.4     Development Assurance for Simple Custom Devices
        For the development of simple custom devices, it is understood that the life cycle data
        might be significantly reduced compared with the data required for a complex custom
         device.
       ED-80/DO-254 acknowledges that documentation for the design process of a simple
        hardware device is less extensive than the one needed for a complex device. In
          addition, while verification and configuration management are also needed, these
         supporting processes also require less documentation for a simple device. However, it
           is important that a simple custom device performs its intended function, and is under
         configuration management, thus allowing the device to be reproduced, conformed, and
        analyzed to ensure continued operational safety.

         Objective CD-2
        The applicant should propose a process in the PHAC or any other appropriate
        planning document to develop simple custom devices that encompasses:
           1.    Definition of the device functions,
           2.   Complete verification of the device functions, through tests and analyses,
           3.    Configuration management of the device, including problem reporting and the
                instructions to reproduce the device,
           4.    Assessment of the build conformance of the device.

         Sections 5.5.2.4 and 5.5.2.5 of this document also apply to the verification process for
        simple custom devices.
       The life cycle data for simple devices can be combined with other hardware data.
           If tools are used for the simple custom device development process, the objectives or
          clarifications of those objectives described in Section 5.8 of this document are also
         applicable.
      When the applicant intends to reuse a previously developed simple device, ED-80/DO-
         254, Section 11.1 and the clarifications provided in Section 5.9 of this document should
        be used.
           If the applicant intends to use COTS IP, the objectives or clarifications of those
         objectives described in Section 5.11 of this document are also applicable.

5.5      Clarifications to ED-80/DO-254 Validation and Verification Processes

5.5.1    Validation Process
         Establishing a correct and complete set of requirements is the cornerstone of the
        development assurance process. ED-80/DO-254, Section 6.1 addresses the validation
         process to ensure the completeness and correctness of derived requirements.
         Nevertheless, the validation process is essential for all the requirements. Indeed, the
         upper-level requirements allocated to the custom device are often refined, decomposed
         or restated at the custom device level, and in terms that support the hardware design.

                                          5

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 →