Your supplier is Nadcap-certified. Your aircraft isn't.

SkyDrive's partnership with Sanyoh — a 70-year supplier delivering Nadcap-certified precision components for the SKYDRIVE eVTOL — landed as a quality assurance story. It isn't one. It's a procurement story with a certificate attached. I've stood in receiving bays at six in the morning with shipments that didn't match the engineering drawing, the supplier's Nadcap paperwork sitting in its folder looking very authoritative. The certificate was genuine. The nonconformance was real. They coexisted because they describe different things.

What Nadcap actually covers

Nadcap audits special processes — welding, heat treatment, chemical processing, non-destructive testing, surface finishing — at a specific supplier facility against specific process specifications. The auditors are qualified specialists. The rigour is real. I've seen what uncontrolled heat treatment produces: a part that passes every dimensional check and fails in service because the metallurgy has degraded beyond spec. Nadcap exists for exactly this reason, and the industry is better for it.

Here is what Nadcap doesn't do. It doesn't verify your engineering specification, confirm the component integrates with the next assembly, or establish traceability through your manufacturing system. It doesn't set up your receiving inspection or define your nonconformance process when the part arrives with a deviation nobody anticipated. The certificate covers the weld. It doesn't cover the engineering judgment that called for it.

The four gates a purchase order can't buy

When I moved from automotive IATF 16949 to aerospace AS9100/EN 9100 at Airbus, the most common systematic gap was identical in both industries: organizations treat supplier certification as a substitute for their own quality system. The logic is seductive — the supplier is certified, the process is controlled, our job is logistics. It fails at four gates no purchase order can buy.

Specification verification. Does the part meet your engineering drawing? Not the supplier's interpretation — yours. Nadcap confirms the welding process was controlled. It says nothing about whether the weld specification you flowed down was correct for your structural load case.

Receiving inspection. When I built the greenfield QA/QC department for 900+ employees at SNOP, the work wasn't finding certified suppliers. IATF-certified suppliers are everywhere. The work was building the verification architecture — inspection plans, measurement systems, calibration chains, nonconformance routing — that makes supplier certification meaningful. Without that architecture, the certificate is a document that arrives with the truck. With it, the certificate is one input among many.

Traceability. When a component fails in service — and in eVTOL, components will fail — can you trace it through every process step, every sub-tier, every material lot, every operator? Nadcap gives you process confidence at the supplier's facility. It gives you nothing for the chain from their loading dock to your aircraft, through your stores, through your assembly line, into the tail number it flies on.

Integration testing. The weld was sound at Sanyoh's facility. Does it still perform after transport vibration, handling, assembly torque, thermal cycling, and operational stress in your airframe? Special process certification is a point-in-time snapshot at one location. Aircraft are assembled over months across continents through hundreds of hands. The conditions at the supplier's bench are not the conditions in your hangar.

Why sourcing strategy isn't quality architecture

The eVTOL sector has brilliant aerodynamicists and procurement teams that can sign impressive suppliers. What's thin on the ground is the quality architecture between those two functions — the specifications, verification, traceability, and corrective action that turn a stack of certified components into a certifiable aircraft.

This isn't a SkyDrive problem. It's a pattern across new aerospace entrants. They hire the right engineers, source from the right suppliers, publish the right announcements. Then they discover, usually during certification testing, that nobody built the quality system connecting the supplier's certificate to the aircraft's airworthiness. That gap is where programs stall.

At Airbus, the 97% reduction in internal lead time we achieved through Routing Verification KPIs came not from better suppliers but from a verification architecture that made their output transparent. The suppliers didn't change. Our ability to see what we were actually receiving did.

The automotive parallel is direct. IATF 16949 requires PPAP — Production Part Approval Process — which compels the supplier to demonstrate their process can repeatedly produce conforming product. PPAP doesn't relieve the OEM of incoming inspection, traceability obligations, or nonconformance management. It establishes a baseline. The OEM's quality system still has to function end to end.

Sourcing allocates risk

Certification is the supplier's promise. Verification is yours.

Sourcing allocates risk. It doesn't eliminate it. Your supplier's Nadcap certificate reduces their exposure — they've been audited, they've passed, they can demonstrate process control to an accredited body. It doesn't reduce yours. If the specification you flowed down was wrong, if the receiving inspection is inadequate, if the traceability chain breaks at a sub-tier, if the integration testing doesn't exist — the failure is yours. And the supplier's certificate will sit in the audit file looking very thorough while your aircraft sits on the ground.

SkyDrive's deal with Sanyoh tells me they've sourced well. It tells me nothing about whether they've built the quality architecture to make that sourcing meaningful — and in eVTOL, where certifying authorities will scrutinize every assumption in your quality system, that architecture is the difference between an aircraft that earns its type certificate and a press release that ages badly. Your supplier is Nadcap-certified. Your aircraft isn't. The gap between those two statements is where the actual work begins.