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
combination of deterministic tests and analyses that ensures correct functional
performance under all foreseeable operating conditions with no anomalous behavior.
The following criteria should be used for assessing whether a device should be
classified as simple:
• Simplicity of the functions and their number,
• Number and the simplicity of the interfaces,
• Simplicity of the data/signal processing or transfer functions, and
• Independence of functions/blocks/stages.
Additional criteria specific to the digital part of the design include:
• Whether the design is synchronous or asynchronous,
• Number of independent clocks,
• Number of state machines, number of states and state transitions per state machine,
and
• Independence between the state machines.
The applicant may propose other or additional criteria for the technical assessment of
simplicity.
When an item cannot be classified as simple, it should be classified as complex.
However, note that an item constructed entirely from simple items may itself be
complex.
Objective CD-1
For each custom device, the applicant should document in the PHAC or any related
planning document:
1. The development assurance level,
2. The simple or complex classification, and
3. If a device is classified as simple, the justification based on the simple
classification criteria.
5.3 Development Assurance for Complex Custom Devices
ED-80/DO-254 is recognized as the industry standard for the development assurance of
complex custom devices.
The applicant should satisfy ED-80/DO-254 and the additional objectives or
clarifications described in this AC from Sections 5.5 through 5.11.
4
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.