Illustrated cover reading "Aviation Course Translation" on a periwinkle background with an arch pattern

Aviation Course Translation: How to Translate Training for Multinational Crews

Table of Contents

Share:
Easily share intel
Summarise this page with your favorite AI assistant

Aviation course translation means converting an existing aviation training course into another language while keeping its technical meaning, terminology and training records intact. For multinational crews, it also means deciding on purpose what stays in English. This guide is for training providers and aviation training organizations that build or sell eLearning.

English is the common language of international aviation, but English-only training does not suit every learner. In April 2026, LOT Flight Academy announced PPL(A) theory content in students’ native language. AFM reported this as reducing “the cognitive barrier of studying complex technical material in a second language.” Radio phraseology, titles and records follow other rules. Blanket translation is rarely right.

We are a content authoring vendor, not an aviation authority, so treat what follows as questions for your authority, not advice. For the general export, import and LMS testing steps, read our guide to course translation for international clients. This post covers what is specific to aviation.

Key takeaways

  • Translate explanations and scenarios. Keep or check anything learners must match to real documents, equipment or radio calls.
  • Radio language proficiency is assessed separately, so a translated course does not replace it.
  • Build a term base before translation, with a do-not-translate flag and an owner for every term.
  • Record the source revision behind each language version, so no stale translation stays in use.
  • Your authority, not your translator, decides what is acceptable within your approval.

What is aviation course translation, and how does it differ from general eLearning translation?

Aviation course translation is the controlled conversion of an aviation course into another language. It differs from general eLearning translation in three ways. A wrong term can change a procedure. Some content must stay in one language. Each version must stay inside your approval and revision control.

Three differences shape the work:

  • Safety-critical meaning: a fluent but wrong term can change what a learner does.
  • Mixed-language content: radio calls, document titles and equipment labels may stay in one language while explanations change.
  • Controlled records: each language version needs its own revision, reviewer and approval trail.

Where does English fit in ICAO and FAA language rules for translated training?

ICAO language proficiency rules concern radiotelephony communication, not the language of your course. According to SKYbrary’s summary of ICAO Annex 1, covered personnel must show they can speak and understand the language used for radiotelephony. Operational Level 4 is the minimum level. A translated course can teach concepts, but it does not replace that assessment.

SKYbrary adds that applicants show proficiency in both phraseology and plain language. It notes the radio language can be “the language normally used by the station on the ground or English.” In our reading, this is about radio communication. It does not set the language in which you teach aerodynamics or safety management.

In the United States, the FAA’s Advisory Circular 60-28B (June 2, 2017) says applicants for certificates under 14 CFR Parts 61, 63, 65 and 107 must be able to “read, write, speak, and understand the English language.” The standard applies at no less than ICAO Operational Level 4. A translated course cannot stand in for that standard.

So keep learners in contact with the English terms they will meet in manuals, charts and radio work. Our guide to aviation English course design covers that practice. As of October 2026 we read ICAO through a secondary summary at SKYbrary, so confirm the wording in Annex 1 and your own authority’s rules.

Which parts of an aviation course should you translate, keep in English or check?

In an aviation course, translate explanations and scenario narration. Keep titles and equipment labels as learners will see them in real life. Check radio phraseology, assessments and records with your authority. This split protects understanding without changing items that your approval or the aircraft fixes.

These defaults are design choices to confirm with your authority and subject-matter experts (SMEs), not regulatory rules.

Content element Default Reason and what to confirm
Explanations, scenario narration and on-screen instructions Translate This is the main learning load. A bilingual aviation SME reviews the result.
Radiotelephony phraseology and standard calls Check Per SKYbrary, the radio language can be English or the ground station’s. Your authority decides what learners practice.
Regulation, manual and document titles and numbers Keep, add a gloss Learners must find the real document. Add a translated explanation beside the title.
Equipment labels, switch names and display text Keep as shown Learners match the course to the real panel. Confirm with your SMEs.
Assessment questions Check Whether a translated assessment is acceptable, and who reviews it, is for your authority.
Certificates and training records Check Your authority sets record language. Store language and revision with each completion.

Pro tip: Tag Every String Before You Export. Mark each text block in the storyboard as Translate, Keep or Check. Translators then get locked Keep strings and a short Check list, instead of guessing which calls and labels must not change.

Who approves an aviation course translation?

Your aviation authority approves courses within the scope of your approval, and a translation vendor does not. Stepes, a translation vendor, states that final regulatory or airworthiness acceptance rests with the applicable authority and that translation does not certify compliance. Treat each new language as a course change to raise with your authority or quality manager.

Never call a course approved because a certified translator produced it. An ISO 17100 certificate, which several vendors cite, describes how a vendor works.

Ask your authority these questions in writing first:

  1. Does a new language version count as a change to the approved course, or sit within the current approval?
  2. Must you submit the text, a translator’s statement or a bilingual reviewer’s sign-off?
  3. Which language must assessments, certificates and records use?
  4. Do radiotelephony phrases stay in a specified language?
  5. Which version is the reference if two languages ever disagree?

As of October 2026, we found no single public rule that answers question 1 for every authority, so ask. Our guides on what regulators accept for aviation eLearning and aviation course version control cover approvals and change classes.

How do you control aviation terminology across languages?

A term base is a controlled list of approved terms, each with a definition, an approved translation per language and a do-not-translate flag. Aviation courses need one because translators otherwise pick their own wording, and two modules can name the same part differently. Build it first.

Each term base entry should carry the fields in this table.

Field What to record
English term and definition One-sentence definition and the source document with its revision.
Approved translation One preferred term per language, plus any alternatives that are banned.
Do-not-translate flag Yes or no. If yes, say whether a gloss goes beside the English term.
Owner and approval date The named SME who approved the entry, and when.

Have an SME who works in the target language review the term base. Decide acronyms one by one: keep the English form, add a local expansion, or both.

Plain source text helps every language. The ASD-STE100 project page says Issue 9 (January 2025) has 53 writing rules in 9 sections. Its aim is to “help the users of English-language maintenance documentation understand what they read.” In our view, short sentences with one term per meaning translate more consistently. STE was built for maintenance documentation, so check whether it suits flight, cabin or ground courses.

How much room do translated text, audio and subtitles need?

Translated text is usually longer than the English source, and short strings expand the most. The W3C internationalization article cites IBM guidelines for English into European languages. Average expansion is 200 to 300 percent for strings up to 10 characters. It falls to 130 percent for strings over 70 characters.

Buttons, tabs and hotspot captions suffer most. Plan for it like this:

  • Layout: let text reflow and avoid small fixed-width boxes, as W3C advises.
  • Images: keep labels out of flattened graphics. See our guide to interactive aircraft system diagrams.
  • Audio: re-record narration for each language, then retime subtitles to the new audio.
  • Radio calls in scenarios: follow your authority’s answer to question 4 above.

Should you use machine translation for aviation training?

Machine translation can produce a first draft of aviation course text, but safety-critical, regulatory and assessment content needs full review by a human who knows aviation. Vendor practice points the same way: Stepes describes tiers of AI and human review by content type, with the most review for safety-critical and regulatory content.

Some platforms offer one-click translation. CPaT Global announced automatic text and audio translation in CPaT Invent in 2021, claiming more than 100 languages. The announcement does not describe quality checks or regulator acceptance. We did not test any translation engine.

Our recommended split, not a rule:

  • Lower risk (background theory, navigation text): machine draft, then a human editor who knows aviation.
  • Higher risk (procedures, emergency content, assessments, regulatory text): human translation, SME review in the target language, and a back-check of critical sentences.

How should an aviation course translation workflow keep every language in sync?

A sound aviation course translation workflow treats the English course as the master and every language version as a dependent copy with its own revision record. A change is closed only when each language copy is updated or formally held with a reason. That stops a stale translation staying in use.

Follow these steps for each module:

  1. Freeze the source revision and tag every string as Translate, Keep or Check.
  2. Update the term base and have the target-language SME approve new terms.
  3. Translate by the risk split above, never into the master course.
  4. Review with an aviation SME who reads the target language.
  5. Back-check safety-critical sentences: a second linguist translates them back to English and your SME compares.
  6. Test in the LMS: audio, subtitles, quiz paths and completion in each language.
  7. Release with a sync record and send changes to your authority as it requires.

A sync record shows where a language lags. This example is illustrative.

Language Translated from source Term base version Reviewer Status
English (master) Rev 4 v6 Course SME Live
Spanish Rev 4 v6 Spanish-speaking SME Live
Arabic Rev 3 v5 Arabic-speaking SME Stale: update or hold

Pro tip: Show the Source Revision Inside Each Language. Put “translated from English Rev 4” on a visible screen in every language version. Support staff and auditors can then tell at once whether a learner saw current content.

Ask your authority whether a stale version may stay in use while an update is pending.

What should you do next?

Next, pick one module and run it through the process in this post. Tag its strings, draft a ten-term term base and send your authority the five questions above. A one-module pilot shows the real review effort before you quote a full course.

SimpliAuthor and SimpliTrain are made by the same company that publishes this site. Based on the vendor’s published documentation, the SimpliTrain aviation page describes an AI course builder that converts SOPs, safety bulletins and airworthiness directives into SCORM-ready modules. It lists SCORM 1.2, xAPI and cmi5 support. The page mentions “multi-lingual capabilities” in a banner without listing languages, and we did not test them.

If language support matters, ask in a demo which languages are supported and how completions record the language. No tool makes a course approved. That stays with your authority.

Frequently asked questions

Can aviation training be delivered in a language other than English?

Often for theory, but your aviation authority decides. The sources we checked treat English proficiency as a separate requirement from course language. The FAA’s AC 60-28B requires certificate applicants to read, write, speak and understand English. Ask your authority whether a translated course sits within your current approval.

Does ICAO require English for aviation training?

We found no ICAO provision in our sources that sets the language of training courses. ICAO language proficiency rules address radiotelephony. According to SKYbrary’s summary of Annex 1, personnel must show ability in the language used for radiotelephony, which can be English or the ground station’s language. Confirm the wording in Annex 1 itself.

Which parts of an aviation course should stay in English?

Keep what learners must match to real material: regulation and manual titles, equipment labels and, where your authority requires it, radio phraseology. Translate explanations, scenarios and navigation. Mark anything uncertain as Check and ask your authority. The table in this post gives planning defaults, not regulatory rules.

Does aviation translation need ISO 17100?

We found no aviation regulation requiring it. ISO 17100 is a translation service standard that several vendors cite. M21Global, a translation vendor, says it is frequently a contractual prerequisite in aviation projects. Ask your client and authority whether they require it, and ask the vendor for the certificate’s scope.

What is ASD-STE100 and does it help with translation?

ASD-STE100 is a controlled English standard for technical documentation. Issue 9, dated January 2025, has 53 writing rules in 9 sections. It aims to help readers of English maintenance documentation understand what they read. It is a writing standard, not a translation tool, and it was built for maintenance content.

Want to learn more?

Reach out to us to learn more.

One Platform for
All Your Training Needs

Get a personalized demo.