English–Chinese reference · Aerospace & UAV

Line Replaceable Unit航线可更换单元

A line replaceable unit (LRU) is a self-contained component that can be removed and replaced on-wing or at the maintenance ramp by line personnel to restore aircraft or system function without extensive shop repair. In technical documentation, it appears in maintenance manuals, illustrated parts catalogs, minimum equipment lists, and fault isolation manuals as the primary level for component replacement, troubleshooting, and dispatch decisions.

Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.

TERM REFERENCE · PROJECT CHECK
EnglishLine Replaceable Unit
Chinese (Simplified)航线可更换单元
DomainAerospace & UAV

Check source meaning → confirm the preferred term → record approved variants and references.

Where this term appears

This term appears in fault isolation manuals, maintenance task cards, logistics support records, MEL deferrals, and component interchangeability notes. Translators must keep LRU, shop replaceable unit, and line replaceable module distinct, and avoid changing part-number references or replacement steps because downstream supply and dispatch records depend on precise unit identification.

Translation checks

A frequent mistake is translating LRU as 'easily replaceable unit' or 'quick-change unit,' which introduces a non-standard maintenance concept. Another error is treating it as interchangeable with 'component' in all contexts; some components require shop-level replacement. This can distort fault isolation logic and lead to incorrect parts provisioning or dispatch decisions.

Keep the term aligned across your files

Check procedure sequence, part names, limits and cautions against the supplied references. Applicable aviation or market requirements depend on the product and project pathway.

Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.

Working on aerospace & uav documentation?

Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.

Prepare an inquiry email →Aerospace & UAV solutions →File handling →

A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.