Plan a UAV documentation language set by product category and EU market, then control terminology, source revisions and release checks.
View references (1) ↓Requirements move, so verify late
First determine which product and operating rules apply to the aircraft and its class or category. Product conformity under Regulation (EU) 2019/945 and operational requirements are related but distinct; not every UAV launch follows the same assessment route.
Ask the responsible product-compliance adviser to confirm the current consolidated rules and the Member States’ language determinations. Involve a notified body where the applicable conformity route requires it, rather than assuming one is required for every product.
The language set is a per-market question
For products within its scope, Regulation (EU) 2019/945 requires specified manuals and information in language understandable to consumers and other end-users as determined by the Member State. Confirm applicability and the accepted language set for each destination.
For a consumer or prosumer UAV sold across a wide European footprint, this produces a large simultaneous language set. The programme management problem is usually harder than the translation problem.
Shipping many languages at once
Establish terminology once and apply it across the full set in parallel, rather than sequencing languages and letting each re-decide the same questions.
Freeze the source before the set goes out. Late source edits multiply across every language and are the most common cause of launch slippage in multi-language releases.
Questions
How many languages should we plan for?
Can safety documentation and marketing be handled together?
What if the source changes mid-project?
Sources
- Delegated Regulation (EU) 2019/945 — unmanned aircraft systemsArticle 6(7) addresses manufacturer documentation and Member State language determinations; consult the current consolidated text.