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 8

PDF page 8 of 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

                      post-layout netlist may be necessary to complement the verification of the
                    implementation for certain requirements (e.g. features not accessible from
                      the I/O pins of the device, timing, abnormal conditions, or robustness
                       cases). In such cases, the coverage of the requirements by means other
                     than a physical test should be justified.
                 The requirement to capture activities in ED-80/DO-254, Section 5.1.2,
                    Item 4.g, introduces the need for requirements to address signal timing
                        characteristics under normal and worst-case conditions. Nevertheless, ED-
                  80/DO-254 does not explicitly address verification of the performance of
                      the device under all possible (best-case and worst-case) timing conditions
                        that could possibly occur during the operation of the device.
                 The following objective clarifies the need to take into account the
                       variation of the environmental conditions (temperature, voltage, etc.)
                     during the evaluation of the timing performance of the design, as well as
                      the semiconductor device process variations.

                     Objective CD-7
                  The applicant should verify the timing performance of the design
                    accounting for the temperature and power supply variations applied to the
                     device and the semiconductor device fabrication process variations as
                     characterized by the manufacturer of the semiconductor device.
                    Note: Static timing analysis (STA) with the necessary timing constraints
                  and conditions is one of the possible means of compliance with this
                      objective for the digital parts of custom devices.

5.6      Clarifications to ED-80/DO-254, Robustness Aspects
       ED-80/DO-254 mentions robustness defects but does not explicitly address robustness.
       The robustness of the design is defined as the expected behavior of the design under
        abnormal and boundary/worst-case operating conditions of the inputs and internal
         design states. These conditions are often captured as derived requirements when they
         are not allocated from the upper level process. When subjected to these conditions, it is
        understood that the design may not continue to perform as it would under normal
         conditions.

         Objective CD-8
        For DAL A or DAL B hardware, the abnormal and boundary conditions and the
         associated expected behaviour of the design should be defined as requirements.

5.7     Recognition of HDL Code Coverage Method
     HDL code coverage analysis is an assessment of whether the HDL code of the design
        has been exercised through HDL simulations.
       The HDL code coverage method provides an assessment of the coverage of the design
         logic structure, giving an indication of which aspects of the logic structure are exercised
        and which are not.

                                          8

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 →