How to keep a drone maintenance log
By the BeaconUAV team. Updated
Set a service interval in flight hours for each aircraft, log every flight against it, and record each repair and part swap with the date and the part. The log then tells you what is due and what keeps breaking.
Service by hours, not by calendar
Motors, bearings, and props wear with use. A quad that sat in a bag for two months needs less attention than one flown every day, so set service intervals in flight hours and let each logged flight count down the clock.
Some gear is better serviced as needed. Leave the interval blank for those rather than inventing one; an empty interval is honest, a made-up one causes false alarms.
What to record
| Record | Why |
|---|---|
| Service interval (hours) | Drives the due-soon and due-now warnings. |
| Each service, with date and notes | Resets the clock and shows what was done. |
| Crashes | A crash counter per aircraft shows which one takes the most punishment. |
| Parts installed and removed | Which motor is on which arm, and its history. |
| Firmware and configuration changes | On commercial fleets, a baseline to compare against. |
Forecasting the next service honestly
BeaconUAV projects a service date from your recent pace: flight hours over the last 30 days. It only turns that pace into a date once you have flown on at least 3 different days in the window. With less than that, it shows the rate and says the sample is thin, because a date from two sessions is a guess.
If you have not flown the aircraft recently, there is no date at all. Averaging your whole history would describe how you used to fly, not how you fly now.
Failure rates need enough hours
Hours per crash is a useful number once there is enough data behind it. BeaconUAV waits for at least 50 hours and one crash before it publishes a reliability rate, so one bad day does not brand a quad unreliable.
Parts swaps without losing history
When you move a motor from a crashed frame to a new build, record it as a swap. The part keeps its history, the old part goes back to stock, and you can still answer where a failing motor has been.
Key takeaways
- Set service intervals in flight hours, or leave them blank for as-needed gear.
- Record every service, crash, and part swap.
- Trust a forecast only when there is enough recent flying behind it.