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
post-layout netlist may be necessary to complement the verification of the
implementation for certain requirements (e.g. features not accessible from
the I/O pins of the device, timing, abnormal conditions, or robustness
cases). In such cases, the coverage of the requirements by means other
than a physical test should be justified.
The requirement to capture activities in ED-80/DO-254, Section 5.1.2,
Item 4.g, introduces the need for requirements to address signal timing
characteristics under normal and worst-case conditions. Nevertheless, ED-
80/DO-254 does not explicitly address verification of the performance of
the device under all possible (best-case and worst-case) timing conditions
that could possibly occur during the operation of the device.
The following objective clarifies the need to take into account the
variation of the environmental conditions (temperature, voltage, etc.)
during the evaluation of the timing performance of the design, as well as
the semiconductor device process variations.
Objective CD-7
The applicant should verify the timing performance of the design
accounting for the temperature and power supply variations applied to the
device and the semiconductor device fabrication process variations as
characterized by the manufacturer of the semiconductor device.
Note: Static timing analysis (STA) with the necessary timing constraints
and conditions is one of the possible means of compliance with this
objective for the digital parts of custom devices.
5.6 Clarifications to ED-80/DO-254, Robustness Aspects
ED-80/DO-254 mentions robustness defects but does not explicitly address robustness.
The robustness of the design is defined as the expected behavior of the design under
abnormal and boundary/worst-case operating conditions of the inputs and internal
design states. These conditions are often captured as derived requirements when they
are not allocated from the upper level process. When subjected to these conditions, it is
understood that the design may not continue to perform as it would under normal
conditions.
Objective CD-8
For DAL A or DAL B hardware, the abnormal and boundary conditions and the
associated expected behaviour of the design should be defined as requirements.
5.7 Recognition of HDL Code Coverage Method
HDL code coverage analysis is an assessment of whether the HDL code of the design
has been exercised through HDL simulations.
The HDL code coverage method provides an assessment of the coverage of the design
logic structure, giving an indication of which aspects of the logic structure are exercised
and which are not.
8
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.