Airworthiness, certification standards, and approvals for eVTOL avionics

What “airworthiness certification” means in this context

In the context of flight control and other safety-critical avionics, “airworthiness certification” is primarily about demonstrating that an airborne system or equipment has been developed, verified, qualified, and produced under recognized aviation rules and standards so that it can be used as part of a certified aircraft.

That scope is different from certifying an entire eVTOL aircraft (type certification / design approval of the aircraft as a whole). Aircraft certification involves a much broader set of requirements (flight, structures, performance, operations, etc.), while avionics airworthiness focuses on the equipment (e.g., guidance, navigation, flight control, and their supporting software/hardware and environmental qualification).

A useful way to think about it:

• Equipment-level airworthiness evidence (software/hardware/environmental qualification + controlled production) helps an aircraft program integrate that equipment into a certified aircraft.
• Aircraft-level certification uses that equipment evidence, but also requires aircraft-level safety assessments, flight testing, operational approval, and compliance demonstrations beyond the equipment itself.

This lesson focuses on the equipment/system side because that is what your reference page is about.

Core airborne standards: DO-178C, DO-254, DO-160G

DO-178C (Software)

DO-178C is the cornerstone standard used to show that airborne software is developed with the rigor expected for aviation. In practice, this drives disciplined requirements management, traceability, verification, configuration management, and quality assurance activities commensurate with the software’s safety criticality. The Embention page explicitly positions DO-178C as one of the key airworthiness standards applied to avionics for eVTOLs.

DO-254 (Hardware)

DO-254 is the hardware counterpart for airborne electronic hardware, including complex electronics (e.g., FPGA/ASIC-based designs) and higher-integrity electronics where process assurance is required beyond “test it and hope.” Again, the referenced airworthiness material highlights DO-254 as part of the compliance baseline for safety-critical avionics.

DO-160G (Environmental qualification)

DO-160 (and its revisions such as DO-160G) defines test categories and procedures for environmental conditions (temperature, vibration, EMI/EMC, humidity, etc.) that airborne equipment must withstand. For eVTOL/UAV avionics, DO-160G is the backbone for showing that the equipment survives and performs under the environmental stresses expected in service. The Embention page’s excerpt explicitly references DO-160G.

Key correction vs my earlier text: DO-160 is not “about the whole aircraft environment”; it’s specifically about testing/qualifying airborne equipment against environmental conditions. For eVTOL programs, this typically appears in the avionics/equipment compliance package.

DAL (Design Assurance Levels): what DAL-A and DAL-B really imply

When aviation software/hardware is developed under DO-178C / DO-254, the rigor is scaled by the Design Assurance Level (DAL) based on the severity of potential failure effects at aircraft level.

• DAL A corresponds to the most stringent development assurance expectations for functions whose failure could lead to catastrophic outcomes.
• DAL B is one step below (hazardous/severe-major level), still extremely demanding in planning, independence, verification depth, and evidence.

For eVTOL/UAV avionics, the DAL assignment is not “picked by the vendor”; it is derived from the aircraft/system safety assessment and then allocated down to equipment functions. Practically, if the flight guidance/control function is safety-critical, the autopilot and its software/hardware elements may be developed to DAL A/B expectations to support integration into certified aircraft. (The Embention materials emphasize safety-critical avionics and certification-grade development aligned to these norms.)

Organizational approvals: POA and APDOA

A major part of “airworthiness readiness” is not only engineering processes, but also organizational approvals that demonstrate controlled design and production capability under aviation regulation.

POA (Production Organisation Approval)

A POA indicates an organization can manufacture aviation products/parts under an approved production system with required controls, traceability, and conformity processes.

APDOA (Alternative Procedure to DOA)

An APDOA (Alternative Procedure to Design Organisation Approval) is an EASA framework that authorizes certain design activities without a full DOA, under defined conditions. The referenced public reporting indicates Embention obtained APDOA approval from EASA, enabling it to design certified autopilot systems within that regulatory framework.

Key correction vs my earlier text: APDOA is not simply a “shortcut”; it is a specific EASA-recognized design approval path with obligations and oversight. It matters because it ties design outputs to an accepted aviation compliance framework (typically under EASA Part 21 processes).

ETSO and ETSO-C198: what it is and what it is not

ETSO in one sentence

An ETSO (European Technical Standard Order) authorization is an approval that an item of equipment meets a defined ETSO minimum performance standard and that the manufacturer meets associated design/production requirements for that article.

ETSO-C198

Public coverage around the same airworthiness context reports an ETSO basis under ETSO-C198 “Automatic Flight Guidance and Control Systems (AFGCS)”, including that EASA verified/approved certification programme elements for the guidance/flight control system under that ETSO framework.

Key correction vs my earlier text: An ETSO authorization is not an “aircraft certification” and does not by itself approve an aircraft to fly passengers. It is an equipment approval that can significantly help aircraft programs by providing standardized compliance evidence and a recognized approval basis for the equipment.

How this ties into eVTOL programs

For an eVTOL aircraft developer, certified avionics/equipment evidence typically plugs into:

• Aircraft-level safety assessments and requirements allocation
• System integration verification (including HIL/SIL, flight tests, abnormal cases)
• Aircraft-level compliance demonstrations required by the chosen certification basis

SC-VTOL (EASA Special Condition for VTOL) is primarily an aircraft-level certification reference for VTOL/powered-lift aircraft. It is relevant to the overall eVTOL certification basis, but it is not the same thing as DO-178C/DO-254/DO-160G evidence for a specific avionics article. My earlier lesson blurred those lines too much. (So: SC-VTOL belongs mainly in an “aircraft certification basis” lesson; here we keep the focus on avionics airworthiness and approvals.)

Conclusion

To operate eVTOLs (especially passenger-carrying) at scale, aviation needs airworthiness-grade components—and for flight control avionics that means:

• DO-178C for software assurance
• DO-254 for airborne electronic hardware assurance
• DO-160G for environmental qualification
• DAL-driven rigor (often DAL A/B for flight-critical functions)
• Organizational approvals that support controlled design and production (e.g., APDOA, POA)
• Where applicable, equipment approvals such as ETSO (e.g., ETSO-C198 for AFGCS) to standardize and strengthen the compliance basis