DJI Pilot 2 flight records: where they are and how to preserve them
If you need flight history for maintenance, incident review or simply to know what your fleet has done, the original files on the controller are the source of truth. This guide covers finding them, telling the two main log types apart, and copying them without damaging anything.
By Flymetry · Updated
Two different kinds of record
Enterprise controllers running DJI Pilot 2 typically hold two families of log files. They serve different purposes and are not interchangeable.
- TXT flight records — one file per flight, written by the pilot app. They carry the flight summary and time series that apps such as Flymetry read: position, altitude, speeds, battery and, depending on aircraft and version, cell-level battery values.
- Controller DAT logs — lower-level flight-controller data intended mainly for diagnostics and support. They are a separate format and are not a replacement for the TXT record.
Where to find them on an RC Plus
DJI's own support article for the RC Plus describes connecting the controller to a computer with a USB-C cable and browsing its storage. Flight records sit in DJI/com.dji.industry.pilot/FlightRecord, and theMCDatFlightRecords folder holds the flight-controller data (DJI Repair support).
Treat that as a starting point, not a universal rule. Paths vary by app, controller and app or firmware version. Other controllers and consumer apps use different folders. If the folder isn't there, search the device storage for recent files with names beginning DJIFlightRecord rather than assuming the data is missing.
Copy, don't move — and keep the original untouched
- Connect the controller and copy (not move) the whole FlightRecord folder to your computer.
- Put it in a dated folder, for example
2026-10-29_RCPlus-01, and keep the original filenames. - Record a checksum so you can later prove the file hasn't changed:
shasum -a 256 *.txton macOS or Linux,Get-FileHash *.txtin Windows PowerShell. - Make the archive read-only and back it up somewhere other than the laptop you copied to.
- Only then upload copies to any analysis tool.
What you can expect inside — and what varies
Available fields differ by aircraft, battery type, app version and whether encrypted sections could be decrypted. One file may include per-cell voltages and battery temperature; another from a different aircraft may only have overall battery percentage. A good tool shows those gaps as gaps rather than filling them with zeros.
Common mistakes
- Deleting records on the controller to free space before a verified backup exists.
- Renaming files in a way that loses the original date and time.
- Assuming a DAT log can stand in for a missing TXT record.
- Uploading the same file from two laptops and counting it twice.
How Flymetry handles these files
In the current private beta, pilots upload TXT flight records manually. Each file gets a SHA-256 fingerprint, so the same file can't be imported twice in one organisation, and the byte-exact original can be downloaded again later. DJI key requests are blocked by default; an organisation admin can opt in. See security and data control. An Android companion, Flymetry Sync, is in development; controller compatibility has not been verified yet.
Sources
- DJI Repair support — exporting RC Plus flight logs (folder names and USB-C connection, paraphrased above).
- Flymetry's own import behaviour, as implemented in the current MVP.
Flymetry is not affiliated with DJI. DJI and DJI Pilot are trademarks of their owner. Läs guiden på svenska.
See it with synthetic data
Click through the demo, or request a place in the private beta.