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 4

PDF page 4 of 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

        combination of deterministic tests and analyses that ensures correct functional
        performance under all foreseeable operating conditions with no anomalous behavior.
       The following criteria should be used for assessing whether a device should be
          classified as simple:
        •  Simplicity of the functions and their number,
        •  Number and the simplicity of the interfaces,
        •  Simplicity of the data/signal processing or transfer functions, and
        •  Independence of functions/blocks/stages.
         Additional criteria specific to the digital part of the design include:
        •  Whether the design is synchronous or asynchronous,
        •  Number of independent clocks,
        •  Number of state machines, number of states and state transitions per state machine,
           and
        •  Independence between the state machines.
       The applicant may propose other or additional criteria for the technical assessment of
          simplicity.
      When an item cannot be classified as simple, it should be classified as complex.
        However, note that an item constructed entirely from simple items may itself be
        complex.

         Objective CD-1
        For each custom device, the applicant should document in the PHAC or any related
        planning document:
           1.   The development assurance level,
           2.   The simple or complex classification, and
           3.     If a device is classified as simple, the justification based on the simple
                classification criteria.

5.3     Development Assurance for Complex Custom Devices
       ED-80/DO-254 is recognized as the industry standard for the development assurance of
        complex custom devices.
       The applicant should satisfy ED-80/DO-254 and the additional objectives or
          clarifications described in this AC from Sections 5.5 through 5.11.





                                          4

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 →