Aerospace catalogues are tightly controlled. Public exposure is sparse, but where it exists, the regulatory and ITAR consequences are heavy. PartSentinel measures, per ATA chapter and per IPC reference, what models claim to know — and flags the dual-use, ITAR or EAR-tagged references that have surfaced inside model responses.
Llama-3 misattributes an ATA chapter for your part — based on a Part 145 maintenance manual scraped from a third-party MRO portal.
ChatGPT lists an IPC reference that was superseded in 2022, citing a paywalled archive that should never have been crawled.
Mistral describes an installation procedure that combines two different revisions of your IPC — invented compatibility under safety load.
Even sparse public exposure is enough to feed a model with controlled references. PartSentinel monitors for ITAR / EAR / dual-use tagged references — and flags any case where a model recalls or volunteers them. Findings are routed to your export-control officer through a signed channel.
ATA chapters are the primary navigation for any aviation copilot. When a model misroutes a part to the wrong chapter, the consequence is wrong maintenance procedure, wrong tool, wrong inspection cycle. We test ATA chapter assignments per model and flag the misroute matrix.
P/N chains span tier-1 OEM, tier-2 supplier, MRO reference and operator-specific tags. Where models break the chain, the wrong part can be procured under the wrong identity. We probe each chain per language and per model panel.
When a maintenance copilot answers an IPC procedural question, we test against the published IPC chapter to flag recall errors. This is not a substitute for the IPC itself — it is a measurement layer that lets you see which models you can trust your operators with.
We support classified-data flows under signed agreements. Onboarding an aerospace customer takes 4–6 weeks for full security review.
Native parser, full data module + applicability + IPD
ATA iSpec 2200 chapters + sub-chapters + figure refs
Boeing, Airbus, Embraer IPCs with figure-level references
Simplified Technical English compliance audit
Direct delta loads via signed S3 / GCS bucket, EU-resident
Mapping assistant + parser tuning included in onboarding
Aerospace engagements are bought by named roles, with security review, and almost never with an open RFP.
We work with you to define the scope before any data leaves your perimeter. The default contract excludes ITAR / EAR controlled data; for engagements that include them, we run on dedicated EU-resident infrastructure with named-engineer access, signed NDA + ITAR / EAR clauses, and a 4–6 week security review.
Yes. We support operator-specific tags and the tier-1 → tier-2 → MRO P/N chain. Operator-side data flows require a signed information-sharing agreement.
Yes. Native parser for data modules, applicability, IPD, and ASD-STE100 compliance audit. Custom DTDs are supported with a 24-hour onboarding overhead.
Classified material is out of scope for the standard product. For engagements that include classified data flows, we operate on customer-managed infrastructure under a separate sovereign engagement.
Aerospace engagements start with a security review and a scoped pilot — typically 50 non-controlled references on 8 LLMs, with named-engineer access. Full engagements run on EU-resident infrastructure with signed export-control clauses.