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 30

PDF page 30 of 31

Enlarge original ↗

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

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

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

Mixed-signal device – A device that combines digital and analog technologies.

Note – A note in this document is supporting information used to provide explanatory material,
emphasize a point, or draw attention to related items which are not entirely within context.

Objective – An objective in this document is a requirement for development assurance that
should be met to demonstrate compliance with the applicable airworthiness requirements.

Previously developed hardware (PDH) – 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 FAA TSOA.

Qualification of a device – SAE EIA-STD-4899 defines component qualification as “The
process used to demonstrate that the component is capable of meeting its application
specification for all the required conditions and environments.” Component qualification results
in a “qualified device.” Note that the use of “qualification” is not intended to refer to
ED-14/DO-160 environmental qualification testing.

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 →