Return to Home is an automated flight function that directs an unmanned aircraft to fly back to a recorded home point, usually the takeoff location, after a pilot command, low-battery condition, or loss of command link. In aerospace documentation, it appears in operational manuals, emergency procedures, ground-station software settings, and training materials where trigger conditions, return altitude, and termination behavior are specified.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Return to Home appears in consumer and commercial UAV user manuals, ground control station apps, mission planning tools, safety bulletins, and training scripts. Translators handle 'RTH altitude,' 'Return to Home triggered by low battery,' and 'cancel Return to Home' in both abbreviated UI text and full manual sentences, so expansion rules must be consistent.
A common mistake is translating the term as 'going home mode' or 'home return,' which sounds informal and loses the automated function meaning. Others render 'home point' as 'homepage point' or 'home dot,' creating confusion when the operator must verify the landing location. Omitting the automatic nature may blur the difference from a manual return, which is hazardous in emergency procedures.
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.
Product manuals.
Read the published project →Aviation documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
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.