English–Chinese reference · Aerospace & UAV

Time Between Overhauls大修间隔

Time between overhauls (TBO) is the manufacturer-specified operating interval, usually expressed in flight hours or cycles, after which an engine or major component must be removed and overhauled to restore serviceability. In technical documentation, it appears in maintenance planning documents, engine manuals, service bulletins, airworthiness limitations, and reliability programs as a mandatory or recommended life limit for continued airworthiness and operational approvals.

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

TERM REFERENCE · PROJECT CHECK
EnglishTime Between Overhauls
简体中文大修间隔
DomainAerospace & UAV

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

Where this term appears

In translation, TBO appears in maintenance planning documents, engine and component maintenance manuals, lease agreements, reliability reports, and airworthiness limitation sections. Translators must distinguish mandatory overhaul limits from recommended or on-condition intervals, and preserve units, calendar limits, and cycle limits because operators and regulators use these values for maintenance scheduling.

Translation checks

A common error is translating TBO as 'total operating time' or 'service life,' which suggests retirement rather than overhaul. Another is presenting the interval as guaranteed or exact for all operators, ignoring that regulatory approvals or operating conditions may change it. This can misstate lease return conditions or airworthiness obligations.

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.

Related document experience

Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.

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.