English–Chinese reference · Aerospace & UAV

Extended Operations延程运行

Extended operations refers to rules and approvals that permit a twin-engine aircraft to operate on routes where flight time at single-engine cruise speed to the nearest diversion airport exceeds standard limits. It appears in airline operational approvals, maintenance program requirements, and flight planning documentation as a framework tied to specific reliability, training, fuel planning, and diversion airport criteria, often called ETOPS in operating manuals.

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

TERM REFERENCE · PROJECT CHECK
EnglishExtended Operations
Chinese (Simplified)延程运行
DomainAerospace & UAV

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

Where this term appears

In localization, extended operations appears in operations manuals, dispatch procedures, and maintenance reliability program sections. Translators encounter it when localizing ETOPS approval conditions, diversion airport planning, and twin-engine performance text, where the distinction between approval status, segment limits, and fuel requirements must be clear and supported by current reliability data.

Translation checks

A common error is translating ETOPS only as a flight-time number, ignoring the operational approval and maintenance reliability framework behind it. Another mistake is standardizing “extended operations” too broadly, which can blur the difference between twin-engine ETOPS and other long-range or extended-range operations that are not covered by the same rules.

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.