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 7

PDF page 7 of 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

                     Objective CD-4
                  For hardware DAL A or DAL B, the applicant should review the detailed
                     design with respect to the design standards and review the traceability
                   between the detailed design and the custom device requirements, in order
                       to demonstrate that the detailed design covers the custom device
                     requirements, is consistent with the conceptual design, and is compliant
                     with the hardware design standards.
                  For hardware DAL C, the applicant should demonstrate that the detailed
                     design satisfies the hardware design standards.

          5.5.2.3     Implementation Review
                   Within a custom device development process, tools are used to convert the
                       detailed design data into the physical implementation. While ED-80/DO-
                  254 does not explicitly address it, a review of the design tool reports (e.g.
                      synthesis and place and route reports) is necessary to ensure that the
                     execution of the tool to generate its output was performed correctly.

                     Objective CD-5
                When tools are used to convert the detailed design data into the physical
                     implementation, the applicant should review the design tool reports (e.g.
                      synthesis and place and route reports) to ensure that the tool executed
                     properly when generating the output.

          5.5.2.4     Review of Verification Cases and Procedures
                 ED-80/DO-254 introduces verification coverage analysis in Section 6.2.2,
                    Item 4, to satisfy the ED-80/DO-254 verification process objectives and
                    determine whether the verification process is correct and complete. A part
                      of the coverage analysis is clarified by the following objective.

                     Objective CD-6
                  Each verification case and procedure should be reviewed to confirm that
                                it is appropriate for the requirements to which it traces and that the
                    requirements are correctly and completely covered by the verification
                     cases and procedures.

          5.5.2.5      Verification of the Timing Performance of the Implementation
                  ED-80/DO-254, Section 6.2 addresses the verification of the
                     implementation. The implementation results from the process to generate
                      the physical custom device from the detailed design data. The post-layout
                          netlist is the closest virtual representation of the physical custom device,
                       resulting from synthesis (for digital part of the device) and place and
                       route.
                  While it is recommended to test the implementation in its intended
                      operational environment (i.e. by a physical test), verification using the

                                          7

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 →