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 19

PDF page 19 of 31

Enlarge original ↗

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

Original FAA AC 20-152A, PDF page 19
AC 20-152A · 19Open saved PDF here ↗
Extracted text for finding words

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

10/7/22                                                 AC 20-152A

                   For the requirements-based verification part, the applicant should satisfy
                  ED-80/DO-254, Section 6.2 for the verification of the requirements related
                       to the COTS IP (see Section 5.11.3.4 above). This can be performed as a
                       part of the overall custom device process, therefore there is no separate
                       objective.

         5.11.3.6    DO-254 Appendix B Considerations
               When developing a hardware DAL A or B custom device, ED-80/DO-254,
                  Appendix B is applicable.
                 Code coverage analysis that is recognized as part of elemental analysis
                        (refer to Section 5.7 of this document) might not be possible for the COTS
                    IP part of the design. However, ED-80/DO-254, Appendix B offers other
                     acceptable methods, including safety-specific analysis. The following
                      objective further clarifies the expectations when using safety-specific
                       analysis.

                     Objective IP-7
                  For COTS IP used in DAL A or DAL B hardware, the applicant should
                         satisfy ED-80/DO-254, Appendix B.
                  The applicant may choose safety-specific analysis methods to satisfy
                   Appendix B on the COTS IP function and its integration within the custom
                     device functions. This safety-specific analysis should identify the safety-
                       sensitive portions of the COTS IP and the potential for design errors in the
               COTS IP that could affect the hardware DAL A and DAL B functions in
                      the custom device or system.
                  For unmitigated aspects of the safety-sensitive portions of the IP, the
                        safety-specific analysis should determine which additional requirements,
                     design features, and verification activities are required for the safe
                     operation of the COTS IP in the custom device.
                 Any additional requirements, design features, and/or verification activities
                       that result from the analysis should be fed back to the appropriate
                      process.

6     USE OF COMMERCIAL OFF-THE-SHELF DEVICES
         Applicants are increasingly using COTS electronic devices in aircraft/engines/
         propellers/airborne systems, which may have safety implications for the aircraft,
         engines/propellers, or systems.
         Section 6 addresses the use of COTS devices through objectives that support the
         demonstration of compliance with the applicable airworthiness regulations for hardware
         aspects of airborne systems and equipment certification when using complex COTS
         devices. Section 6.2, “Applicability to COTS devices,” enables applicants to identify
         the COTS devices that are within the scope of Section 6.


                                         19

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 →