On May 17, 2026, the U.S. Federal Aviation Administration (FAA) issued Advisory Circular (AC) 20-193B Revision B, mandating DO-333A compliance for flight control software tool qualification in electric vertical takeoff and landing (eVTOL) aircraft. This update directly affects Chinese airframe integrators and subsystem suppliers seeking Type Certificate (TC) or Supplemental Type Certificate (STC) approval from the FAA — a development with material implications for avionics hardware selection, model-in-the-loop (MiL) test architecture, and third-party tool vendor engagement.

Event Overview

On May 17, 2026, the FAA published AC 20-193B Revision B, formally adopting DO-333A, Airborne Software Tool Qualification Using Model-Based Development, as the mandatory standard for qualifying software tools used in the development of flight control software for eVTOL aircraft. The requirement applies to all Chinese manufacturers submitting TC or STC applications to the FAA, including both complete aircraft integrators and suppliers of critical subsystems such as flight control units (FCUs) and motor controllers.

Industries Affected

Aircraft Systems Integrators (Chinese)

These companies are directly impacted because DO-333A validation is now a prerequisite for FAA certification submissions. The requirement affects how they select microcontroller units (MCUs), structure their model-based development (MBD) workflows, and document tool qualification evidence — particularly for tools used in MiL simulation, automatic code generation, and static analysis.

Avionics Subsystem Suppliers (Chinese)

Suppliers providing flight control computers, sensor fusion modules, or actuator interface units must ensure that their internal development toolchains — especially those supporting DO-178C-compliant software — meet DO-333A criteria. This includes traceability between models, generated code, and verification artifacts, potentially requiring updates to tool configuration management and qualification documentation packages.

Third-Party Embedded Software Tool Vendors

Vendors offering modeling, simulation, code generation, or static analysis tools (e.g., MATLAB/Simulink, SCADE, or custom tool suites) face heightened scrutiny when serving Chinese eVTOL developers targeting FAA certification. Their tools must be qualified under DO-333A, and vendors may need to provide updated tool qualification kits or support documentation aligned with the new AC.

Key Focus Areas and Recommended Actions

Monitor FAA’s Implementation Timeline and Interpretive Guidance

While AC 20-193B Revision B is effective immediately, the FAA may issue clarifications, FAQs, or compliance guidance documents in the coming months. Companies should track FAA notices, RTCA working group outputs, and upcoming public workshops related to DO-333A application in eVTOL contexts.

Review Current MBD Toolchains Against DO-333A Annex A Requirements

Organizations should conduct an internal gap assessment of their existing modeling, simulation, and code-generation toolchains — focusing specifically on tool classification (TQL-1 through TQL-5), failure mode analysis, and independence of verification activities. Particular attention should be paid to tool usage assumptions and configuration control processes.

Engage Early with Tool Vendors and Certification Authorities

Chinese applicants should initiate formal discussions with tool vendors regarding DO-333A qualification status and available evidence packages. Concurrently, early alignment with FAA Designated Engineering Representatives (DERs) or certification project teams is advisable to confirm acceptable approaches for tool qualification documentation and integration into overall DO-178C/DO-254 certification plans.

Assess Impact on MCU and Hardware-in-the-Loop (HiL) Architecture Decisions

DO-333A compliance may influence selection of target MCUs and real-time operating systems, especially where tool-generated code interacts closely with hardware abstraction layers or safety-critical peripherals. Teams should evaluate whether current HiL test environments support full traceability from model to executable, as required by DO-333A Section 6.3.

Editorial Perspective / Industry Observation

Observably, this revision signals a tightening of the FAA’s expectations for model-based development rigor in next-generation air mobility platforms — moving beyond DO-178C’s software focus to explicitly govern the tools themselves. Analysis shows that DO-333A adoption is not merely procedural but reflects growing regulatory emphasis on end-to-end traceability and independence in automated development pipelines. From an industry perspective, this change functions less as an isolated policy update and more as a structural signal: it confirms that the FAA is treating eVTOL certification as a high-assurance software-intensive endeavor, comparable in rigor to traditional civil aviation programs. It is therefore more appropriately understood as a foundational shift in certification expectations — one that will likely inform future EASA and CAAC harmonization efforts.

This update underscores that regulatory readiness for eVTOL is increasingly defined by toolchain maturity, not just product-level compliance. For Chinese developers, the implication is clear: certification timelines and resource planning must now account for tool qualification as a parallel, non-trivial workstream — beginning no later than Q3 2026.

Information Sources

Main source: U.S. Federal Aviation Administration (FAA), Advisory Circular AC 20-193B Revision B, issued May 17, 2026.
Additional reference: RTCA DO-333A, Airborne Software Tool Qualification Using Model-Based Development, published December 2023.
Note: Ongoing implementation details, FAA DER interpretations, and potential regional alignment developments remain subject to observation.