Flight records

Practical flight logging for field operations.

Nimbent keeps manual flight records, supported log imports, jobs, clients, and maintenance history in one operational workspace. On Android, DJI Fly private app folders are not accessible to third-party apps, so manual records remain part of the supported workflow.

Supported workflow

Accurate records from manual entries and accessible imports.

Manual flight entries

Record date, location, aircraft, battery, pilot notes, job context, and compliance details directly in the app.

Supported imports

Where a user can provide an accessible supported file, Nimbent can use imported flight details to reduce manual entry.

Job and client context

Link records to client work so operational history is easier to review, report, and reconcile later.

Maintenance continuity

Use flight and equipment records to keep battery, aircraft, and maintenance history organized across your operation.

Android DJI limitation

How Android log access works today.

Modern Android versions restrict third-party access to another app's private data folders, including DJI Fly folders under Android/data. Nimbent supports structured manual logging and supported imports where the operator can explicitly provide an accessible file.

If a source log is not available through a normal device workflow, Nimbent cannot silently collect it from the manufacturer app's private storage.

Compliance

Records built for Canadian commercial operations.

Transport Canada context

Keep flight records, site notes, aircraft details, and job history close together for operational review.

Review-ready history

Maintain cleaner source data for exports, support review, and your own operational records.

Clear limitations

Android DJI import availability depends on files the user can actually access and provide.