Importing logs

After a flight, upload the log file from the DJI controller. The system creates the flight entry itself - it includes:

• a full-resolution GPS track,
• takeoff and landing times,
• altitudes and speeds,
• battery usage,
• flight events,
• the drone’s serial number.

Format and limits

• Accepted files are .txt DJI FlightRecord logs (e.g. DJIFlightRecord_*.txt) - other extensions are rejected.
• The import handles logs from DJI Pilot 2 and from other apps built on the DJI Mobile SDK.
• A single file can be up to 100 MB. The number of selected files is not limited - the application uploads them in batches and shows the progress.
• On the controller, logs live in: Internal storage / DJI / com.dji.industry.pilot / FlightRecord. Fastest way: long-press the first file, choose “Select all” in the menu and upload everything - duplicates filter themselves out.

Deduplication

The same log never creates two entries in the organisation’s flight log - even if two users upload it. Files can be uploaded in bulk without watching for duplicates: the system first checks which files it already knows and only uploads the new ones.

Deduplication works within the organisation. The same file uploaded by another organisation, e.g. after taking over a drone together with its controller, creates a separate entry in that organisation’s log - every organisation keeps its own records.

The import queue

The import page shows today’s queue and the import history. Statuses: Queued, Processing, Completed (with a report: sample and event counts), Error, Duplicate. On an error, the operator has a Retry action.

Note

Original files are archived for 30 days - within that window a failed import can be retried. The flight entry itself stays in the log for the whole licence period.

Caution

The entry is built from the controller log. If no log was recorded, add the flight manually - see “Adding a flight manually”.