Automatic Dependent Surveillance (ADS) is a surveillance technique in which an aircraft or uncrewed system automatically derives its position, altitude, velocity, and identity from onboard navigation equipment and periodically broadcasts that data over a datalink. In translated aerospace documentation, the term appears in avionics manuals, airspace procedure texts, operational specifications, and unmanned traffic management materials, where the abbreviation ADS-B must be expanded consistently and distinguished from ground-based radar surveillance.
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.
Translators encounter this term in avionics component manuals, airspace integration documents for uncrewed aircraft systems, and operational texts describing surveillance requirements. It also appears in software localization for cockpit displays or ground-control station interfaces when abbreviating traffic information such as ADS-B IN/OUT. During editing, consistency matters because the same concept recurs in UI strings, abbreviation lists, and explanatory notes.
A frequent error is expanding ADS to 'Automatic Dependent System' or rendering 'dependent' in a way that suggests the aircraft depends on ground interrogation. This misses the core distinction: the aircraft provides its own derived position rather than being prompted by radar. Another mistake is treating ADS-B and transponder as synonyms; they are related but not identical, and conflating them in maintenance or operational text can misstate actual surveillance equipment requirements.
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.