How eVTOL Certification Is Reshaping Supplier Engineering Expectations

The eVTOL industry spent its first decade making promises about timelines. Certification would take three years. Production would start in 2024. The vehicles would be safe, quiet, and economically viable by the time the infrastructure was ready. Almost none of those timelines held, and the reasons are more instructive than the delays themselves.

One of the least-discussed contributors to program slippage is supplier qualification. The companies building electric vertical takeoff and landing aircraft—Joby, Archer, Lilium’s successors, Wisk, Overair, and dozens of others—are designing vehicles at a systems complexity level that rivals regional jets. They need suppliers capable of supporting that complexity with engineering rigor that matches FAA and EASA expectations. Many of their suppliers, particularly those coming from general aviation or commercial off-the-shelf markets, cannot yet meet that bar. Closing that gap is now one of the central engineering management problems in the industry.

The Standard Stack eVTOL Programs Are Demanding

The three standards dominating eVTOL supplier conversations are DO-178C, DO-254, and ARP4754A. Each addresses a different layer of the system.

DO-178C governs airborne software. It defines five development assurance levels (DAL A through E), with DAL A representing the highest rigor—software whose failure could cause a catastrophic aircraft-level event. For eVTOL programs, flight control software, propulsion management systems, and battery management systems are routinely assigned DAL A or DAL B. The standard requires not just that software work correctly, but that the development process produces specific artifacts at each stage: requirements, design descriptions, source code, test cases, and reviews—all traceable to one another and to the aircraft-level safety objectives.

DO-254 is the hardware analog to DO-178C, covering complex electronic hardware—FPGAs, ASICs, and programmable logic devices. It is frequently underestimated by suppliers who assume that hardware certification is simpler than software certification. In practice, DO-254 at DAL A or B imposes comparable documentation and review burdens, particularly around requirements capture, design verification, and validation.

ARP4754A sits above both. It is the system-level process standard, defining how you develop and validate an aircraft system or subsystem. It requires that safety objectives cascade from the aircraft level through system level to item level—meaning that a supplier building a motor controller cannot simply demonstrate that their controller works. They must demonstrate that it works in the context of the safety analysis their OEM customer has performed, using the allocation of safety requirements their OEM has assigned them.

Together, these standards create a documentation and process architecture that many suppliers have never encountered. A company that makes motor controllers for industrial applications, or even for general aviation under less stringent Part 23 interpretations, may have excellent engineering. They may build reliable hardware. But they may have no requirements management system, no formal traceability, no design reviews structured to produce auditable evidence, and no test documentation that maps to a safety requirement. That gap is not a gap in engineering talent. It is a gap in process infrastructure—and process infrastructure takes time to build.

Where the Certification Bottleneck Actually Forms

The naive model of certification is sequential: the OEM designs the aircraft, qualifies the suppliers, integrates the components, then seeks type certification. In this model, supplier qualification happens before OEM-level certification activities intensify.

That model does not survive contact with eVTOL program realities.

eVTOL OEMs are working under investor pressure, regulatory uncertainty, and compressed timelines that make sequential execution impossible. They are simultaneously designing aircraft, negotiating with regulators over means of compliance, and trying to lock in supply chains. They cannot afford to wait until their own systems engineering is stable before beginning supplier qualification—because supplier qualification itself takes 18 to 36 months for a supplier starting from scratch with DO-178C or DO-254.

The bottleneck forms at the interface between OEM system-level requirements and supplier-level development. For a supplier to begin certified development under ARP4754A, they need safety requirements allocated to their component. Those allocations come from the OEM’s system safety assessment. If the OEM’s architecture is still evolving—which it almost certainly is during early development—then the safety requirements passed to suppliers are provisional. Suppliers either wait for stable requirements, risking schedule delays, or begin development against requirements that will change, risking rework.

This is not a new problem in aviation—it is well-documented in commercial aircraft programs. What makes it acute for eVTOL is scale. A Tier 1 supplier to Boeing or Airbus has organizational infrastructure to manage this: dedicated certification teams, DER relationships, mature requirements management tooling, and program management experience with regulatory interfaces. A motor controller startup supplying an eVTOL OEM typically has none of this. They may have five to fifteen engineers, strong domain expertise, and a capable product—and no pathway to the organizational maturity their customer now requires.

How OEMs Are Responding

The more sophisticated eVTOL programs have recognized that supplier qualification is a program risk that must be managed as actively as any other. Several distinct strategies have emerged.

Early supplier engagement with requirements allocation. Rather than treating supplier qualification as a downstream activity, leading OEMs are engaging key suppliers during preliminary design review (PDR) phase, sharing draft safety requirements, and beginning qualification planning before architecture is frozen. This creates rework risk but trades it against the larger risk of late-start qualification.

Supplier development programs. Some OEMs are providing direct technical assistance to suppliers who lack certification experience—assigning DER (Designated Engineering Representative) consultants, funding process development, and in some cases co-developing the quality management infrastructure a supplier needs. This is expensive and requires OEM staff with certification expertise to spare, which is itself scarce.

Qualification by similarity and incremental certification. Where a COTS component is already qualified to a relevant standard, or where a supplier has prior DO-178C or DO-254 experience from defense programs, OEMs are structuring qualification arguments around that prior art. The FAA and EASA have explicit provisions for this under AC 20-148 and similar guidance, and it can significantly compress qualification timelines—but only when the prior certification genuinely maps to the new use case.

Tiered supplier requirements. Not all components face the same DAL. Suppliers of non-safety-critical components—cabin systems, non-essential displays, ground support equipment—face far lower certification burdens. Pragmatic OEMs are segmenting their supply base and concentrating certification support resources on the suppliers whose qualification is on the critical path to type certificate.

What This Means for Suppliers Making Market Decisions

For a supplier evaluating whether to pursue eVTOL business, the certification question is not primarily a technical question. It is a strategic investment question: are you willing to build the process infrastructure that aviation certification requires, knowing that infrastructure has value beyond any single program?

The case for building it is stronger than it has ever been. DO-178C and DO-254 compliance, once achieved, is directly applicable to defense avionics programs, commercial aviation components, and advanced air mobility systems broadly. A company that develops genuine certification capability becomes a preferred supplier across multiple high-value markets simultaneously. The investment is large—easily $1–3M for a small supplier building the process, tooling, and documentation infrastructure from scratch—but the addressable market it unlocks is correspondingly large.

The case against is also real. Certification infrastructure requires sustained maintenance. It requires configuration management discipline, training investment, tool qualification, and quality management that changes the character of engineering work. Companies that build excellent products in relatively informal engineering environments sometimes find that the cultural change required for certification compliance is harder than the technical change. Not every supplier should pursue every market.

The honest advice for a general aviation component supplier evaluating eVTOL opportunities: assess whether the certification requirements your potential customer is imposing match the DAL assigned to your component. DAL D and DAL E requirements are manageable for most organized engineering teams. DAL A and DAL B requirements for a supplier without prior experience represent a genuine organizational transformation, not an incremental process improvement.

The Traceability Problem That Shows Up in Every Audit

Across supplier qualification audits, one gap appears more frequently than any other: requirements traceability. OEMs and DERs consistently find that suppliers can demonstrate their product works—test results exist, verification is done—but cannot demonstrate that the verification covers all the safety-relevant requirements, and cannot demonstrate that the requirements they verified actually derive from the allocated safety objectives.

This is the practical consequence of building a product first and attempting to construct certification artifacts afterward. Retroactive traceability is possible but expensive, often requiring reconstruction of design rationale from informal communications, whiteboard sessions, and engineering memory. It routinely causes six-to-twelve-month delays in supplier qualification and is almost always avoidable with earlier process investment.

Modern requirements management tools have made this substantially more tractable than it was a decade ago. Purpose-built platforms like Flow Engineering allow engineering teams to maintain bidirectional traceability from system-level requirements through design, implementation, and verification artifacts—capturing the links as they are created rather than reconstructing them afterward. For a supplier starting a DO-178C or DO-254 program, the tooling choice is consequential: legacy document-based tools impose traceability overhead that scales badly with system complexity, while graph-based approaches that treat requirements and their relationships as first-class data structures align better with how certification reviewers actually interrogate compliance arguments.

Flow Engineering’s focus on connecting requirements to system models and downstream artifacts is directly relevant to the supplier qualification challenge: it is precisely the traceability architecture that both OEM customers and certification authorities want to see when they audit a supplier’s development record.

The Broader Aviation Ecosystem Implication

The eVTOL certification wave is having a secondary effect on the broader aviation ecosystem that has not received enough attention: it is expanding the pool of suppliers with genuine aviation certification capability.

Every supplier that invests in DO-178C or DO-254 compliance for an eVTOL program becomes a more capable supplier for the entire aviation industry. Every engineer who learns to work within a certified development process gains skills that are durable and transferable. Every quality management system built to aviation standards is a permanent asset that improves with use.

This is the long-duration positive externality of the eVTOL certification pressure. In the short term, it creates bottlenecks, delays, and cost overruns. In the medium term, it builds supply chain depth that the aviation industry has been structurally short of for years. Defense programs have long complained about the shrinking pool of suppliers with genuine avionics certification experience. eVTOL programs, by forcing the issue with their supplier bases, are inadvertently addressing that shortage.

The companies that survive the qualification gauntlet—that build the process infrastructure, retain the engineering talent, and deliver certified hardware to their first eVTOL customer—will not struggle to find their second customer. The certification credential, once earned, compounds.

Honest Assessment

The eVTOL certification challenge is real, the timelines are difficult, and the supplier qualification bottleneck is genuinely contributing to program delays across the industry. None of that is catastrophic—it is the normal consequence of an industry moving from prototype to certified product, compressed into an unusually short window.

What would accelerate progress: OEMs treating supplier requirements as design outputs that must be managed with the same rigor as vehicle requirements, not as procurement documents drafted after design is complete. Suppliers treating certification investment as market access investment, not as compliance cost. Regulators maintaining predictable means of compliance guidance so that suppliers can invest with confidence in what they are building toward.

The programs that get this right—that treat supplier engineering rigor as a design parameter, not an afterthought—will have type certificates before the programs that do not. At this stage of the industry, that timing difference is the difference between market existence and market irrelevance.