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
Figure 1 – Position of COTS IP within a “simplified” design representation flow
The availability of a COTS IP does not guarantee that it is suitable to be used in a
custom device for aircraft systems. Some COTS IP may have been developed using
ED-80/DO-254 and will therefore have the necessary life cycle data to demonstrate
satisfaction of ED-80/DO-254. However, most COTS IP are not developed to meet
aviation development assurance standards and, therefore, there are risks associated with
their use in a custom device for aircraft systems or equipment.
The risks of using COTS IP may include:
• Incomplete or missing documentation/data regarding:
o The behavioral operation of the COTS IP,
o How to integrate it into the design;
• Insufficient verification performed by the COTS IP provider;
• Deficient quality of the COTS IP.
The potential for design errors may be increased by the lack of development assurance,
and/or by insufficient service experience.
Possible design errors within COTS IP or in the use of COTS IP may lead to a failure
mode. Risk factors for these types of errors include:
• Unknown level of rigor of the COTS IP design and verification process;
• Misalignment between the intended usage of the COTS IP by the IP provider and
the usage in the custom device by the IP user;
• Incomplete or missing details regarding the detailed operation of the COTS IP;
• Incorrect integration of the COTS IP with the rest of the custom device design;
• Integrator lacking expertise with the function of the IP.
Additionally, the COTS IP user completes the development of the integrated COTS IP
up to the physical implementation of the device. The COTS IP user may introduce a
design error while completing the physical implementation of the COTS IP because of
the user’s incomplete knowledge of the internal design of the COTS IP.
13
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.