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
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.
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.