On June 2, 2026, the U.S. Federal Aviation Administration (FAA) released a revised Appendix D to AC 21.17B, clarifying that all eVTOL aircraft applying for a type certificate must ensure that core fly-by-wire flight-control software meets DO-178C Level A, the highest software safety assurance level, and must submit an independent verification and validation evidence package. This update is especially relevant to the eVTOL certification, avionics, flight-control software, and export-facing aerospace supply chain segments, because it directly affects compliance thresholds and market access timing.
Event Overview
According to the disclosed information, the FAA issued the revised Appendix D to AC 21.17B on June 2, 2026. The revision explicitly requires that, for eVTOL aircraft seeking a type certificate, the core flight-control software within the fly-by-wire system must comply with DO-178C Level A certification requirements. The FAA also requires applicants to provide an independent verification and validation, or V&V, evidence package.
The currently confirmed information focuses on two points: first, the software assurance level for core flight-control functions has been made explicit at the highest safety level; second, compliance documentation must include independently produced V&V evidence. The event summary further indicates that this requirement is expected to materially affect the export access pace of Chinese eVTOL flight-control hardware and software integrators.
Which Industry Segments Will Be Affected
eVTOL aircraft developers seeking type certification
These companies are directly affected because the new wording applies to all eVTOL aircraft applying for a type certificate. The impact is likely to appear in certification planning, software development workflows, and document preparation. From an industry perspective, the requirement for DO-178C Level A and independent V&V means software compliance can no longer be treated as a secondary supporting task within a broader airworthiness process; it becomes a central certification gate for fly-by-wire architectures.
Flight-control software developers and embedded avionics suppliers
This segment is affected because the revised guidance specifically targets core fly-by-wire flight-control software. The main impact is on software architecture, development assurance processes, traceability, testing depth, and evidence generation. Analysis shows that suppliers supporting redundancy architectures in eVTOL flight controls may face higher entry barriers where their deliverables are intended for FAA-facing certification programs.
Hardware-software integration firms in the eVTOL supply chain
Integration firms are likely to be affected because they often sit between aircraft developers and subsystem suppliers, especially where flight-control computers, sensors, and software are validated as one integrated chain. The event summary specifically points to Chinese flight-control hardware and software integrators facing changes in export market access timing. More appropriately understood as a compliance timing issue, the effect may be seen in program scheduling, customer qualification reviews, and cross-border project acceptance milestones.
Independent verification and validation service providers
This segment is affected because the FAA has explicitly asked for an independent V&V evidence package. That creates a direct compliance relevance for organizations involved in software verification, validation, and audit-style evidence preparation. Observably, the change does not simply raise the software standard; it also raises the evidentiary standard for proving compliance in a form usable within certification review.
What Companies and Practitioners Should Watch, and How to Respond Now
Track official FAA wording and any follow-on clarification
Companies should closely review the published revision to Appendix D of AC 21.17B and pay attention to any subsequent FAA clarification on scope, interpretation, or evidence expectations. Current priority should be placed on understanding exactly how the agency defines core flight-control software within fly-by-wire systems and how independent V&V evidence is expected to be presented in a certification context.
Reassess whether current software assurance processes align with DO-178C Level A expectations
For aircraft developers, software teams, and integrators, the practical issue is not only awareness of the rule update but whether current engineering and compliance processes can support Level A certification objectives. From an industry perspective, teams involved in export-oriented eVTOL programs should promptly map existing development, testing, traceability, and configuration practices against the newly explicit requirement, especially where their systems are positioned as core flight-control functions.
Separate policy signaling from immediate business readiness
Current priority should be distinguishing between a regulatory signal and a completed business outcome. The FAA revision is already a confirmed compliance development, but companies still need to determine where in their project pipeline the effect becomes immediate. Analysis shows that firms with ongoing or planned certification-linked deliveries should focus first on contracts, customer commitments, and technical deliverables tied to FAA-recognized approval pathways.
Prepare independent V&V documentation pathways early
Companies should not limit preparation to software coding or test execution alone. The explicit requirement for an independent V&V evidence package means evidence ownership, review independence, document structure, and submission readiness should be planned early. More appropriately understood as a certification packaging issue as well as an engineering issue, this may affect partner selection, documentation sequencing, and internal approval workflows.
Editorial View / Industry Observation
Observably, this FAA update is not just a technical wording change for software teams. It functions as a clearer compliance threshold for eVTOL certification programs that depend on fly-by-wire control architectures. From an industry perspective, the development matters because it narrows the room for flexible interpretation around the safety assurance level of core control software.
Analysis shows that the immediate significance is strongest for supply chain participants whose products are intended for certification-linked export projects, especially flight-control software and integration providers. More appropriately understood as a regulatory signal with near-term operational consequences, the update does not by itself determine every commercial outcome, but it does define a more demanding baseline that market participants will need to address.
Current priority should be continued attention to how this requirement is implemented in project reviews, supplier qualification, and certification preparation. That is why the industry should watch not only the policy text itself, but also how developers and suppliers adjust documentation, engineering evidence, and delivery timelines in response.
Conclusion
The FAA's revised eVTOL airworthiness guidance has clear industry relevance because it explicitly elevates core fly-by-wire flight-control software to DO-178C Level A and requires independent V&V evidence for type certification applications. For aircraft developers, software suppliers, and integration firms, the significance lies less in headline value and more in the practical compliance burden it introduces.
From an industry perspective, the update is best understood as a concrete certification requirement and a strong market-access signal rather than a standalone news event. A neutral reading suggests that affected companies should focus on certification readiness, evidence preparation, and schedule impact assessment, while continuing to monitor official interpretation and implementation details.
Source Note
Primary source: U.S. Federal Aviation Administration (FAA), revised Appendix D to AC 21.17B, released on June 2, 2026.
Ongoing observation item: the specific downstream impact on export access timing for Chinese eVTOL flight-control hardware and software integrators should continue to be monitored through subsequent official interpretation and project-level implementation.