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 9

PDF page 9 of 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

      When performed during requirements-based verification (per ED-80/DO-254,
         Section 6.2), HDL code coverage is recognized as a method to perform ED-80/DO-254
         elemental analysis per Appendix B, Section 3.3.1, for digital devices. HDL code
        coverage supports the assessment of whether the HDL code elements are fully covered
        by requirements-based simulations. As such, it does not represent an assessment of the
        completeness of requirements-based testing activities or the effectiveness of
         requirement coverage.

         Objective CD-9
        For hardware DAL A or DAL B, where HDL code coverage is used to perform
         elemental analysis (ED-80/DO-254, Appendix B, Section 3.3.1), the applicant should
         define in the planning documents the detailed coverage criteria of the HDL code
         elements used in the design. The criteria should ensure coverage over the various cases
          of the HDL code elements used in the design (e.g. branches, conditions, etc.). Any non-
        covered case or element should be analyzed and justified.
        Note: Code coverage might need to be complemented by additional analysis for any
        hardware items that are identified as not covered by the code coverage analysis, in
        order to complete the elemental analysis of all elements. This situation may occur in the
        use of some COTS IP instantiations.

5.8      Clarifications to ED-80/DO-254, Tool Assessment and Qualification
       ED-80/DO-254 introduces the notion of tool assessment and qualification. ED-80/DO-
         254, Figure 11-1 includes a flow chart indicating the tool assessment considerations and
           activities, and provides guidance for when tool qualification may be necessary. This
     AC uses the flow chart and its related text as a basis for providing further clarification,
         as follows:
       ED-80/DO-254 - Figure 11-1, Item 1. - Identify the Tool
         Information capturing the environment required for tool operation and the tool revision
        should be included with the tool identification.
       ED-80/DO-254 - Figure 11-1, Item 2. - Identify the Process the Tool Supports
      When identifying the design or verification process that the tool supports, it is
         important to also identify what purpose or activity within the hardware development
         process the tool satisfies. While assessing the tool limitations, evidence of formal
        assessment of the tool problem reports is not required if the tool output has been
        completely and independently assessed.
       ED-80/DO-254 - Figure 11-1, Item 3. - Is the Tool Output Independently Assessed?
       The purpose of assessing the tool output is to completely cover, with an independent
        means, the potential errors that the tool could introduce into the design or fail to detect
         during verification.





                                          9

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 →