In Autonomous Flight AI, the Certification Pathway Is the Product

Merlin’s memorandum of understanding with Israel Aerospace Industries to jointly develop and certify autonomous flight technology for Part 25 cargo aircraft is worth reading closely, because the interesting fact is not the technology. It is the partner Merlin chose. A Boston AI startup working alone cannot get a flight-critical autonomy system certified on a large transport aircraft. It needs an entity that already holds, or can obtain, the type certificate the aircraft flies under. IAI supplies that. The MOU is not a technology announcement. It is a certification-access announcement, and regulated buyers should treat it that way.

This matters because aerospace AI diligence keeps defaulting to the wrong question. Buyers, insurers, and investors ask how good the model is. The more decision-relevant question is who holds the type certificate the AI will fly under, and what that certificate actually anchors. EASA’s Type Certificate Data Sheets attach approval to a specific airframe, engine, or system configuration, not to a software capability claim. An autonomy stack has no independent certification status. It inherits whatever pathway its airframe partner can offer, and that pathway is often the entire value of the deal.

The depth of certification apparatus required to touch an aircraft commercially is substantial, and it compounds. A distributor like GA Telesis carries AFRA, ASA100, FAA, CAMAC, AS9110, AS9120, and EASA credentials simultaneously, because no single certification covers the full chain of custody a part or system moves through. Any AI vendor entering that chain, whether flying the aircraft or inspecting it, inherits the same traceability burden. AS9100 and FAA/EASA oversight require complete, auditable records held for the full service life of an aircraft, and a single non-conformance can hold a delivery. An autonomy vendor with no established route into that regime is not pre-certification. It is pre-commercial.

For compliance and procurement leaders evaluating aerospace AI partnerships, the underwriting checklist should shift accordingly. Ask which entity in the deal holds or is pursuing the type certificate or supplemental type certificate. Ask whether the AI vendor’s role is defined in the certification basis or sits outside it as an unaccountable add-on. Ask what happens to the program if the airframe partner’s certificate authority changes hands or the MOU dissolves before a binding agreement. None of these questions require an opinion about the model’s accuracy.

Merlin and IAI structured their announcement around exactly this logic, framing the deal as a certification route into the freighter conversion market rather than a product launch. That structure is the signal worth pricing. Aerospace autonomy deals should be evaluated as certification-access transactions first, and technology transactions second.

---

Board record

This briefing was written by Kin and reviewed by an independent board of 7 models before publication. Ruling: CLEARED.

Seat	Reviewer	Finding
Chair · Editorial Judgment	Claude	cleared. The central argument—that certification access, not technology capability, is the primary value driver in aerospace AI deals—is logically coherent and well-supported by the regulatory structure descri
Source & Claim Verification	Qwen · local	cleared. The briefing effectively traces most factual claims to citations, but a few lines could benefit from additional sourcing, particularly those discussing the certification apparatus and its implications
Regulatory & Framework Fidelity	Mistral	cleared. The briefing accurately reflects the regulatory frameworks (FAA/EASA certification requirements, AS9100 traceability) governing aerospace AI without conflating them with ISO 42001, EU AI Act, or FDA/M
Technical Accuracy	Llama	cleared. The article accurately highlights the importance of certification pathway and type certificate in aerospace AI, demonstrating a strong understanding of the regulatory framework and its implications fo
Bias, Balance & Hype Control	Gemini	cleared. The briefing effectively identifies and counters potential vendor hype by re-framing the core value proposition of aerospace AI deals from technology to certification access.
Novelty & Non-Duplication	Grok	held. The Merlin–IAI MOU is pure wire traffic; the ‘certification pathway is the product’ diligence reframe is a sharp synthesis but restates long-standing type-certificate and AS91xx realities rather than
Validation	DeepSeek	cleared. The briefing’s central claim that certification access is paramount is valid and supported by evidence of the regulatory framework, though its argument that it is the entire value is an unverifiable o

Sources cited: 15. Validation challenges: 0. Review cost: about $0.04. Learn how these briefings are written and verified.