Flight records and supported imports
Nimbent is designed to keep flight history organized even when a manufacturer app or mobile operating system limits direct access to source logs.
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.
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.
Important Android note
Nimbent should not be treated as having autonomous access to private Android folders used by DJI Fly or other manufacturer apps. If those files are not available to the user through a normal device workflow, Nimbent cannot silently collect them.