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 6

PDF page 6 of 31

Enlarge original ↗

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

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

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

10/7/22                                                 AC 20-152A

        These custom device requirements, which are traceable from/to the upper-level
         requirements and, therefore, not considered to be “derived,” should also be correct and
         complete.

         Objective CD-3
        The applicant should validate all the custom device requirements by following the
       ED-80/DO-254 validation process (ED-80/DO-254, Section 6). This validation activity
         covers both derived and non-derived requirements.
        For DAL A and B development, validation activities should be performed with
        independence.
        Note: ED-80/DO-254 Appendix A defines acceptable means for establishing
        independence.

5.5.2    Verification Process
       ED-80/DO-254 broadly describes the verification process, but additional guidance is
        needed to ensure the verification of the custom device is complete, particularly in the
         area of:
        •  Design reviews,
        •  Reviews of test cases and procedures, and
        •   Verification of the implementation.

          5.5.2.1     Conceptual Design Review
                    Conceptual design is the process of generating a high-level design
                      description from the hardware requirements (see ED-80/DO-254, Section
                         5.2). The conceptual design review is typically used to ensure that the
                  outcome of the conceptual design activities (see ED-80/DO-254, Section
                       5.2.2) is consistent with the requirements, and identifies constraints for the
                       interfacing components (hardware or software) and architectural
                       constraints for the detailed design activities of the custom device.
                    Since this conceptual design review is already addressed in ED-80/DO-
                     254, Section 5.2.2 through the note, no separate objective is needed.

          5.5.2.2      Detailed Design Review
                     Detailed design is the process of generating, from the conceptual design
                   and the requirements, a hardware description language (HDL) or analog
                      representation of the design, constraints for the implementation (e.g.
                     timing constraints, pinout, I/O characteristics), and the hardware-software
                       interface description.
                 ED-80/DO-254 introduces design reviews in Section 6.3.3.2. A design
                    review is considered to be an essential step during the detailed design
                     process (ED-80/DO-254, Section 5.3) supporting the implementation
                      process, and complementing requirements-based verification.

                                          6

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 →