How to keep useful drone flight-time records
A total flight-time figure is useful only when its definition and coverage are clear. Keep the source for each record, name the time measure you are using and show which flights contributed to a total.
By Flymetry · Reviewed
Define the measure before adding it up
| Measure | What you need to know |
|---|---|
| Log-reported duration | Which field the app recorded and what that field represents |
| Motor-running time | Whether motor start/stop intervals were actually recorded and validated |
| Airborne time | Whether a supported take-off/landing definition can be applied to the available data |
| Mission duration | How your organisation defines the wider job, including non-flight work |
Do not substitute one measure for another without saying so. Flymetry's reviewed MVP uses the log's totalTime as its product flight-time measure. That is not an independently verified airborne-time measurement or a universal legal definition of flight time.
Keep a record a colleague can review
Include the source filename and fingerprint, flight date/time and time-zone interpretation, aircraft identity, reported duration, available location context, uploader and any separately confirmed pilot information. Add mission context or a note as separate information rather than changing the original record.
A worked total with a duplicate and a gap
Illustrative example · synthetic data. Synthetic example; duration below means log-reported duration.
| Record | Duration | Decision |
|---|---|---|
| DEMO-FLIGHT-A | 12:00 | Include once |
| Identical copy of A | 12:00 | Exclude from the total as a duplicate |
| DEMO-FLIGHT-B | 18:30 | Include once |
| DEMO-FLIGHT-C | Missing | Keep visible; do not treat as zero |
The known total is 30:30 across two records with usable duration. One additional record lacks duration. Calling the result “three flights, 30:30 known duration; one missing time value” is clearer than implying complete coverage. If your report needs a different definition, calculate it separately from suitable evidence.
Preserve identity and time context
An uploaded file tells you who submitted it, not automatically who piloted the aircraft. Likewise, a date string without a confirmed time-zone interpretation can create incorrect day or month totals. Preserve uncertainty instead of silently assigning a pilot or converting time with an assumed zone.
Build a documentation bundle
Keep the originals, the derived summary and the notes explaining any manual additions. State the export date, filters, time definition and missing-data coverage. An original-file fingerprint helps trace a summary to a copy; it does not certify regulatory compliance or prove every event in the log.
Review history by aircraft and battery
Serial-linked history can help find the equipment associated with a record. It should complement your operational documentation, not be presented as a complete maintenance or mission-management system when those functions are not implemented.
See flight log analysis, fleet records.
Questions
Can I add motor time and logged duration together? They may overlap. Keep separate definitions and totals.
Does a missing record mean no flight happened? No. A log-based report describes the records available to it.
Is a CSV enough? It can be a useful summary, but keep original files and the method behind the export.
Sources and method
Method note: This is a record-management guide based on Flymetry's reviewed time-field and import behaviour. It is not legal advice or a statement that a particular report satisfies an aviation authority's requirements.