English–Chinese reference · Aerospace & UAV

Flight Data Recorder飞行数据记录器

A flight data recorder is a crash-protected electronic unit that continuously records aircraft operating parameters such as altitude, airspeed, magnetic heading, vertical acceleration, and flight-control inputs. In aerospace localization it appears in avionics documentation, accident investigation references, maintenance manuals, and regulatory requirements, often abbreviated as FDR, where recorded data is used for incident analysis and to verify operational compliance and corrective action.

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

TERM REFERENCE · PROJECT CHECK
EnglishFlight Data Recorder
简体中文飞行数据记录器
DomainAerospace & UAV

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

Where this term appears

Translators encounter FDR in aircraft flight manuals, avionics installation manuals, and incident investigation reports. It is often referenced in regulatory material concerning mandatory recording parameters and data readout procedures. In localization, the term must remain distinct from cockpit voice recorder and data link recorder, because each unit has different certification, recording duration, and privacy or security considerations.

Translation checks

A common mistake is abbreviating flight data recorder as “FDR” without first expanding it, or confusing it with cockpit voice recorder in list contexts. Another is translating “crash-protected” as “break-proof,” which overstates the protection and may mislead investigators or maintenance crews about the unit’s survival limits. Such errors blur distinctions between recording sources and data availability.

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.