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 11

PDF page 11 of 31

Enlarge original ↗

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

Original FAA AC 20-152A, PDF page 11
AC 20-152A · 11Open 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

        gaps in the tool assessment and qualification process, for example, to explain the
        method of independent assessment of the tool output. In this case, a relevant tool
         history is considered to be complementary data, providing more assurance for a tool.
         In addition to what is already referenced in ED-80/DO-254, Figure 11-1, Item 9, for
          tool qualification guidance, ED-12C/DO-178C and ED-215/DO-330 may also be used.

5.9      Clarifications to ED-80/DO-254 regarding Previously Developed Hardware
         Previously developed hardware (PDH) is defined as a custom-developed hardware
         device that has been installed in an airborne system or equipment either approved
        through FAA type certification (TC/STC) or authorized through TSOA. The section
         providing clarification on the use of PDH also covers PDH that was developed and
        approved prior to the use of ED-80/DO-254 in civil certification.
        This section provides guidance on the use of ED-80/DO-254, Section 11.1, for PDH.

         Objective CD-12
       When an applicant proposes to reuse PDH, the applicant should use ED-80/DO-254,
         Section 11.1 and its subordinate paragraphs. The applicant should perform the
         assessments and analyses required in ED-80/DO-254, Section 11.1, in order to ensure
          that using the PDH is valid and that the compliance shown during the previous
        approval was not compromised by any of the following:
           1.  Modification of the PDH for the new application or for obsolescence management;
           2.  Change to the function, change to its use, or change to a higher failure condition
              classification of the PDH in the new application; or
           3.  Change to the design environment of the PDH.
        The results should be documented in the PHAC or any other appropriate planning
        document.
         In the context of custom device development, any one of these three points potentially
         invalidates the original development assurance credit for the PDH. In case of change
        or modification, the applicant should assess these changes using ED-80/DO-254,
         Section 11.1 and its subordinate paragraphs. When the original design assurance of the
     PDH is invalidated by one of the above points, the custom device should be upgraded
        based on the assessment per ED-80/DO-254, Section 11.1. When upgrading the
        hardware, the applicant should consider the objectives of this document that are
         applicable per the assessment.

5.10     Clarifications to ED-80/DO-254, Appendix A
        This section clarifies the life cycle data referenced in ED-80/DO-254, Appendix A as
         follows.
        •  The row corresponding to 10.1.6 “Hardware Process Assurance Plan” in Table A-1
            should also indicate HC2 for Level C to be consistent with row 10.8.



                                         11

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 →