A paper notebook in the truck is honest until the second aircraft, the night job, and the week the battery log and the calendar stop agreeing. Drone flight log software for Part 107 pilots is not a hobby stamp collection. It is the ops record of what flew, on which aircraft, under which authorization, with which crew, and whether the remote pilot was still current to do it.
This is a Pilot Ledger Field Work post about logging practice. It is not a photogrammetry bake-off and not a waitlist pitch. The test is simple: six months later, can you reconstruct a job without reconstructing a story.
What Part 107 actually asks you to be able to show
Part 107 does not hand commercial remote pilots a manned-style § 61.51 logbook mandate with columns the FAA grades on the ramp. That is not permission to remember nothing. The remote pilot in command still has to operate the aircraft safely, complete the preflight required by 14 CFR § 107.49, and keep the small unmanned aircraft in a condition for safe operation under § 107.15. Recurrent aeronautical knowledge under § 107.65 is on a calendar. Accident reporting under § 107.9 is event-driven. Waivers and airspace authorizations, when you use them, come with conditions you either followed or did not.
The practical result: the log is how you prove the week. Insurers, clients, and your future self will ask versions of the same questions. Which tail or serial flew. How many cycles on that pack. Who was PIC. Whether night anti-collision lighting was on. Whether the LAANC authorization covered that grid and altitude. Whether the waiver special provisions were in force. Software that cannot answer those is a diary, not an ops record.
Currency is not the same as a filled hour column
Part 107 currency for commercial remote pilots is knowledge recency under § 107.65, not a three-takeoff manned-airplane currency rule imported from part 61. You still want flight history. Hours and cycles tell you whether the aircraft and the pack are tired. They do not substitute for completing the recurrent training or testing the rule requires. Good drone flight log software keeps both in view: the last recurrent date next to the last flight, so a busy October does not hide an expired knowledge window.
Log the operation type, not just “flew.” Mapping at 250 feet over an empty pad is not the same record as a night inspection with lights, a visual observer, or a flight under a certificate of waiver. If you later need to show that the PIC who flew the waivered profile had practiced that profile, a generic hour total will not help.
The record a commercial week actually produces
Treat every accepted job as a packet, not a row:
- Who — remote PIC name and certificate number; visual observer if used; anyone who handled the aircraft.
- What — aircraft registration and serial; payload; firmware if it matters to the profile; battery pack IDs and cycles.
- Where and when — site name, lat/long or address, local date, launch and recovery times, day or night or civil twilight.
- Why it was legal — airspace class; LAANC or DroneZone authorization number and altitude cap if used; waiver number and the section it covers if used; any local launch permission.
- How it went — weather notes, aborts, incidents, maintenance squawks, and whether the aircraft returned in a condition for safe operation.
That packet is what “ops records” means on a Part 107 shop floor. A spreadsheet with date and minutes is a start. It fails when two aircraft share a week, when a pack is swapped mid-site, or when the client asks which serial flew the Thursday roof.
Maintenance belongs in the same system or in a system that the flight log can point to. § 107.7 gives the Administrator inspection and testing authority; § 107.15 is the condition-for-safe-operation rule. You do not need a dramatic story to keep a discrepancy log. You need a place to write “gimbal play after landing, grounded until inspected” so the next PIC does not launch on hope.
Authorizations and waivers are first-class log fields
Airspace authorization and operational waivers are different documents. LAANC or a DroneZone authorization answers § 107.41 in a volume. A certificate of waiver under § 107.200 answers a deviation from a listed operating rule. Mixing them in a notes field is how shops fly the right aircraft under the wrong paper.
Put the authorization or waiver identifier on the flight. Put the altitude cap, the grid, the lighting condition, the visual-observer requirement, or the other special provision that actually constrained that sortie. If the job was vanilla Part 107 with no extra paper, say so. Silence in the log is not the same as “no waiver required.”
Night is a good example of precision. Night operations with anti-collision lighting under § 107.29 are not the same record as a waiver from the lighting paragraphs in § 107.205(b). If you flew lights-on night, log lights-on night. If you flew under a lighting waiver, log the waiver. Future you will not remember which one it was.
What to ignore in consumer log apps
Consumer drone logs are often telemetry dumps: GPS tracks, battery percent, pretty maps. Useful for flying. Incomplete for a business. They rarely store PIC certificate numbers, client job IDs, authorization numbers, recurrent dates, or the discrepancy that grounded the backup airframe. They also tend to live in a phone that is not the invoice system, so the log and the job never meet.
You do not need every parameter the flight controller recorded. You need the fields a second PIC, an insurer, or a client audit will ask for, plus enough telemetry to reconstruct an incident if one happens. Exportability matters. If the only copy is inside a vendor account you cannot leave, you do not have a record. You have a subscription.
A weekly habit that keeps the log honest
Log the same day, not “Sunday when I catch up.” Same-day notes capture the abort, the pack that sagged, and the client who moved the cones. A Monday reconstruction will invent smoothness.
Close the week with three checks: every flown job has a PIC and an aircraft; every authorization used is cited; every grounded airframe has a squawk or a return-to-service note. If a job slipped for weather, that belongs on the job board—not as a ghost flight in the log.
Keep personal practice flights in the same system with a clear type tag. Mixing them into commercial hours without a label is how currency conversations get sloppy. Practice still counts as cycles on the pack.
Soft next step
Pilot Ledger is built for commercial drone ops that have outgrown a notebook and a camera-app track log—jobs, records, and the week in one place. Start from Pilot Ledger or see pricing when the flight log and the job calendar should stop living in different apps.
Practical notes
Write the minimum fields you will actually fill. An empty twenty-column template is worse than a short packet you complete. Put recurrent dates on a calendar reminder, not only in a bio. Name files and log entries with site, date, and aircraft—not “final_flight.” And when a waiver or authorization is in play, copy the identifier into the flight that used it. The PDF in email is not the record until it is attached to the sortie.