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.
This extraction supports search. Read the original page for complete notation and layout.
10/7/22 AC 20-152A
Note: The term “COTS device” used in this document applies to a semiconductor
product that is fully encapsulated in a package. This term does not apply to circuit
board assemblies.
6.1 Background
COTS devices continue to increase in complexity and are highly configurable. COTS
devices provide “off-the-shelf” already developed functions, some of which are highly
complex. Their development and production processes undergo a semiconductor
industry qualification based on their intended market (consumer, automotive, telecom,
etc.). Their usage by the aerospace industry provides additional integration and higher
performance capabilities than were possible in the past.
The design data for these COTS devices are usually not available to the COTS user.
Since these devices are generally not developed for airborne system purposes,
assurance has not been demonstrated that the rigor of a COTS manufacturer’s
development process is commensurate with the aviation safety risks.
ED-80/DO-254 introduces a basis for the development assurance for the use of COTS
devices in Section 11.2, “COTS components usage.” This section states that “the use of
COTS components will be verified through the overall design process, including the
supporting processes.”
Since ED-80/DO-254 was released in the year 2000, the number of functions embedded
and integrated in a single COTS device has significantly increased. Functions which
were previously split into various components, making the interface between those
components accessible for verification, are now embedded within a single chip. While
there are clearly some benefits of integrating more functions within a device, the
increased level of integration makes it difficult for the user to verify the different
hardware functions in the device due to lack of access to the interfaces between
functions. Since these devices are more complex and highly configurable than the older
separate devices, the risk is greater that the COTS device will not achieve the intended
function in particular use cases over the required operating conditions.
Furthermore, some additional assurance is needed because design errors may still be
discovered after the COTS device is released to the market, or when an applicant
extends the use of the device beyond the manufacturer’s specifications.
6.2 Applicability to COTS devices
Section 6 is applicable to digital, hybrid, and mixed-signal COTS devices that
contribute to hardware DAL A, B, or C functions. For COTS devices contributing to
hardware DAL C functions, a limited set of the objectives of this section will apply.
Section 6 is also applicable to FPGA and PLD devices that embed Hard IP (see
definition) in their produced/manufactured silicon, but only for the COTS part of the
FPGAs/PLDs.
Section 6.4 only applies to COTS devices that are complex, as determined by the
following COTS complexity assessment.
20
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.
A focused review, an agreed assessment package or ongoing support alongside your team. We can agree the relevant inputs and scope in the initial conversation.
This opens your email application.
Start a conversation
Tell us about your programme, the system you are developing and the support you need.
We can agree a focused use-case review, a defined evidence package or ongoing programme support.
This opens your email application.
Specialist aerospace expertise
Aerospace Consulting is led by Hussein Khimji, an FAA Designated Engineering Representative in systems and equipment, with a focus on system safety, flight controls and avionics.
We work with aircraft developers and systems suppliers to connect technical decisions, safety assessments and certification evidence.
This is the proposed introduction. The full About page will add your approved biography and associate expertise.
Systems engineering & development assurance
Tell us about the aircraft or system, its intended function, stage of development and the support you need.