In-depth buying guides from the AST-Drones certified inspection desk.
Flight hours are a used drone's mileage — but the crash history buried in the log is its accident report, and that's what sellers actually hide. 'Only 20 hours' means nothing if three of them ended in impacts. This guide shows how to pull the real numbers and read them the way our inspection desk does.
In DJI Fly: Profile → Device Management → [aircraft] shows total flight time and flight count for the paired aircraft. For deeper history, the full logs live on the mobile device or controller: DJI Fly stores flight records under the app's FlightRecord folder, exportable via the in-app sync or direct file access. Enterprise platforms log to DJI Pilot 2 with per-flight detail including error events.
| Total flights | Reading |
|---|---|
| <50 | Like New territory — verify the rest matches |
| 50–150 | Excellent grade — normal, healthy use |
| 150–400 | Good grade — airframe fine, consumables priced in |
| 400+ | Working aircraft — buy on documentation, not cosmetics |
The log's value is in its anomalies: hard-impact flags, sudden altitude drops ending flights, IMU calibration requests clustering after a specific date, and compass errors repeating at the same GPS coordinates. A single old crash with months of clean flying afterward is usually fine — the repair held. Recent impacts, or impact-then-listed-immediately, are the pattern that walks us away. Full event-by-event screening is part of the 27-point inspection on every unit we sell.
'Never crashed' with impact flags in the log. 'Barely flown' with 300 flights. 'Always stored indoors' with corrosion patterns and flights logged in coastal salt-air regions. The log doesn't argue — it just records. Any seller unwilling to show it has answered your real question already.
Hours tell you how the airframe lived; battery cycles tell you how the packs lived. Both are published on every drone we list — the two numbers together are 80% of a used drone's true condition.
In the DJI Fly app: Profile → Device Management → select the aircraft — total flight time and count are listed there. Full per-flight logs live in the app's FlightRecord folder on the connected device and can be exported for review.
Hours alone rarely kill a deal — 400+ hour airframes with clean logs often bench-test better than 50-hour crash survivors. What matters is the combination: hours, impact events, and battery condition. We publish all three per unit.
The app's local records can be wiped, but total flight time on the aircraft itself persists. A pristine empty log folder on a well-used controller is itself a signal — we cross-check device logs against airframe totals for exactly this reason.