What we work on
- Maintenance manuals and technical publications
- Task cards and job instruction data
- Airworthiness and continuing airworthiness documentation
- Structured content in S1000D and related standards
- Component maintenance and repair documentation
- Training and qualification material
- Ground support and operational documentation
- Supplier and programme documentation
Why this sector is a hard case
Structured content breaks differently. S1000D data modules are reused across publications and configurations. A term translated one way in one module and another way in a module that appears beside it in the same manual produces a document that contradicts itself, and neither module was wrong on its own. Machine translation operates on the module; the failure appears at assembly.
Revision cycles are permanent. Documentation is amended continuously across the life of a platform. Terminology decided in the initial translation constrains every revision for twenty years, and correcting it later means re-issuing content that is already in the field.
Controlled language is the point. Much of this content is authored in a restricted English specifically so that it can be understood unambiguously and translated consistently. An engine that produces fluent, varied, natural target text has undone the reason the source was constrained in the first place.
The reader is working, not reading. A technician following a task card in their second language needs the instruction to be unambiguous, in the same words as the last time they performed it. Synonym variety is a defect here, not a virtue.
Consequence is not proportional to volume. A wrong torque value, a reversed sequence, a mistranslated caution — small text, large outcome.
What we deliver
- Reviewers with aerospace or defence technical background, matched to system and document type.
- Consistency enforced at publication level, not module level — findings reported across the assembled document set, which is where the failure actually appears.
- Controlled-language discipline preserved, with variation flagged as an error rather than accepted as style.
- A dedicated pass for warnings, cautions, sequence, units and quantities, scored at critical severity.
- A maintained termbase you own, versioned alongside the documentation it serves.
- Full traceability — source revision, target revision, reviewer, qualifications, date.
On security and export control
This sector has constraints that most of our work does not. Content may be export-controlled, security-classified, or restricted to specified nationalities and locations. Some of it cannot pass through public cloud infrastructure at all, and some of it we will not be the right supplier for.
Tell us the constraint in the first conversation. We would rather say early that a piece of work is outside what we can handle than discover it during onboarding — and where the constraint is data handling rather than clearance, there are usually workable answers.
Languages where this matters most
German and French for the European programme and supplier base. Korean and Japanese for Asian operators and manufacturing partners, where the evidence on machine translation quality is weakest among major languages. Arabic for Gulf operators and defence programmes. And the wider European set wherever a platform is operated across multiple countries.