Flight records and supported imports

Manual records are always supported

Manual flight records are the most reliable cross-platform workflow. They can be used for every aircraft, client, and job regardless of manufacturer.

• Aircraft, battery, date, duration, location, and crew notes.
• Job and client association.
• Incident, maintenance, weather, checklist, and attachment context where relevant.

Supported imports depend on file access

Where the operating system and source application allow access to a supported file, Nimbent can use that import path. On Android, some manufacturer apps store logs in private application folders that third-party apps cannot browse directly.

If a log file is not available through a normal share, export, or file-picker flow, treat manual entry as the supported record path for that flight.

Importing DJI flight records on iPhone

On iPhone, DJI Fly stores flight records where the Files app can reach them, so Nimbent can import them directly. The records have to be on the phone first:

• Flying with the phone as the screen: records are saved into DJI Fly on the iPhone automatically — you can import right away.
• Flying with a DJI remote controller that has a built-in screen (DJI RC, RC 2, RC Pro): records are saved on the controller, not the phone. In DJI Fly on the controller, sign in to your DJI account and sync your flight records (in your profile area — menu names vary by DJI Fly version). Then open DJI Fly on your iPhone, sign in to the same account, and sync the records down to the phone.
• Importing in Nimbent: open the Logbook, tap import, and browse via the Files app to On My iPhone → DJI Fly → FlightRecords. Select a flight record file to import it.

If the FlightRecords folder looks empty on the phone, the usual cause is records still sitting on the controller or in the DJI cloud — run the sync on both devices and check again.

Why an imported value may need review

Imported files can contain source-app calculations, units, altitude references, sensor values, or derived fields that need review before they are used for regulatory, insurance, or client reporting.

• Check units and altitude reference before relying on a maximum altitude value.
• Compare imported summaries against what the pilot and aircraft actually did.
• Correct or annotate records when source data appears inconsistent.