DJI flight log analysis, with the original in reach
Review the flight, the available telemetry and the equipment behind it. Flymetry brings original DJI TXT records into a workspace where each imported flight has a source you can return to.
Illustrative example · synthetic data
Start with the file your flight app recorded
The current workflow is manual: copy the original flight records from your device and upload them to Flymetry. Import results are shown per file. Keep TXT flight records separate from flight-controller DAT logs; they are different inputs, and this workflow is about supported TXT records.
Move from the overview to the detail
Start with recorded flight time and available aircraft information. Where decoded telemetry is present, review the route, use playback and inspect curves or recorded values. A missing field should stay missing: an overview is useful only if you understand what contributed to it.
Keep the source connected
Flymetry retains the byte-exact original and assigns a SHA-256 fingerprint. Identical files are detected within the organisation. CSV export supports further review, while downloading the original lets you return to the source rather than relying only on a derived summary.
Understand coverage before comparing flights
Aircraft, flight app, log format and decryption affect which values are available. A successfully imported summary does not automatically mean that a complete route or cell-level battery data is available. Encrypted telemetry may require keys; DJI key retrieval is blocked by default and is controlled separately.
What this gives your team
A shared starting point for flight-history review, linked equipment and source files. Pilot identity needs care: the person who uploaded a file is not automatically the verified person who flew the aircraft. Keep operational context with the record and use your own review procedures.