A drone logbook is the record of who flew what, when, where, for how long, and in what condition the aircraft was before and after. Under 14 CFR Part 107, the FAA does not require you to keep one. Every other party you will ever deal with, insurers, clients, auditors, opposing counsel, and the FAA itself during an investigation, behaves as though you must.
That gap is the whole story. The regulation is silent, the practice is mandatory, and most operators only discover the difference when a claim gets denied or a waiver application comes back asking for evidence they never collected.
This guide covers what belongs in a drone logbook, what the rules on both sides of the Atlantic actually say about retention, and the operational problems that show up once more than one pilot is logging into the same book. Those last parts are where most logbook advice stops and where the real cost sits.
Table of contents
- The three logbooks people call one logbook
- What the FAA actually requires
- When your drone logbook stops being yours
- Remote ID means your logbook is no longer the only record
- Retention periods nobody tells you about
- What to record in a drone logbook
- Paper, spreadsheet, app, or operations platform
- When the logbook and reality disagree
- Making a logbook that holds up as evidence
- Migrating off a logbook you have outgrown
- Frequently asked questions
The three logbooks people call one logbook
"Drone logbook" describes three different records that serve three different audiences, and conflating them is the most common reason an operator's paperwork falls apart under scrutiny.
The pilot logbook follows the person. It records one individual's flight experience across every aircraft they touch: hours, sorties, night operations, conditions, aircraft types. It answers "is this pilot qualified?" It travels with the pilot when they leave your company.
The aircraft logbook follows the airframe. It records that specific tail number's life: total cycles, firmware versions, battery pairings, damage, repairs, component swaps. It answers "is this aircraft airworthy?" It travels with the drone when you sell it, and a well-kept one measurably raises resale value.
The operator record follows the company. It records the operation as a whole: which flight was flown for which client under which authorization, what the risk assessment said, who approved it, what the weather was, what went wrong. It answers "was this operation legal and safe?" Nobody takes it with them. It is the record that gets subpoenaed.
Most consumer drone logbook apps only build the first one. Most paper books build the first two. If you run a commercial operation, the third is the one that protects the business, and it is the one that has to reconcile with the other two. Our guide to flight log automation covers how these three layers get populated from a single telemetry import rather than three separate data entry tasks.
What the FAA actually requires
Part 107 contains no flight logging requirement. There is no drone equivalent of 14 CFR 61.51, the section that dictates logbook content for crewed pilots. A remote pilot can fly commercially for a decade and never write down a single entry without violating the rule.
Four sections still create record obligations indirectly, and they are the ones worth knowing precisely.
§107.7 requires you to present your remote pilot certificate on request to the FAA, NTSB, TSA, or any federal, state or local law enforcement officer, and to "make available, upon request, to the Administrator any document, record, or report required to be kept under the regulations of this chapter." Read that last clause carefully. A voluntary logbook is not required to be kept, so §107.7 does not, on its own, compel you to produce it. That is a real distinction, and it is also nearly worthless in practice, for reasons covered below.
§107.9, retitled "Safety event reporting" in the 2022 amendment, gives you 10 calendar days to report an operation involving serious injury, any loss of consciousness, or property damage where repair cost or fair market value exceeds $500. Ten days is not long to reconstruct a flight from memory. Operators with a logbook file a clean report; operators without one file a vague one, and vague reports invite follow-up questions. See our incident reporting walkthrough for what a defensible report contains.
§107.49 requires a preflight assessment of weather, airspace, restrictions, persons and property on the surface, and other ground hazards before every flight. The rule requires you to do it. It does not require you to record that you did it. If you are ever asked to prove you assessed local weather before a flight two years ago, an unrecorded assessment and no assessment look identical. This is why a pre-flight checklist that writes to your log is worth more than one on a clipboard.
§107.65 sets aeronautical knowledge recency at 24 calendar months. That is a currency date, not a flight hour requirement, and it belongs in your records even though it never appears in a flight entry. Part 107 renewal tracking across a team is a certification management problem, not a logbook problem, though the two live in the same file drawer.
So the honest answer to "does the FAA require a drone logbook" is no. The honest follow-up is that the FAA's own commercial operator guidance treats flight records as normal professional practice, and every discretionary decision the agency makes about you, waiver approvals, enforcement posture, BVLOS authorization, leans on the record you can produce.
When your drone logbook stops being yours
The moment a second pilot flies for your company, the logbook stops being a personal document and becomes a business asset with contested ownership. Almost no logbook guidance addresses this, and it causes more real damage than any regulatory question.
Here is the scenario. You hire a contract pilot for a six-month utility inspection campaign. They log flights in their own app, on their own account, under their own subscription, because that is what they have always used. Eighteen months after the project ends, your client's insurer disputes a damage claim tied to one of those flights. The telemetry, the location trace, the altitude profile, the preflight notes all live in an account controlled by a contractor you no longer work with, who may or may not still pay for that subscription.
You have no record. You had 340 flights.
Three practical rules prevent this.
Log into the company record first, the personal record second. Pilots absolutely should maintain personal logbooks for their own career, and those hours matter for hiring and for demonstrating experience on waiver applications. But the authoritative operational record has to sit in an account the company controls. Automatic upload from the controller solves this cleanly, because the pilot does not have to remember to forward anything. DroneBundle's log sync app runs directly on DJI Smart Controllers and RC Pro and pushes logs to the workspace as soon as the controller reconnects.
Write log ownership into the contractor agreement. One sentence: flight telemetry, mission records and imagery generated during engagement are the property of the operator and must be delivered in original format within X days. Most contractors will not object. The ones who do have told you something useful.
Watch the seat math. Per-pilot pricing is the default in this category, and it quietly punishes the operator model where a core team of three manages twenty occasional contract pilots. DroneLogbook, for example, prices Professional at $6.95 per user per month and Pro+ at $12.95 with one seat per pilot, so seasonal pilots either cost you seats year-round or get dropped and take their history with them. DroneBundle uses workspace tiers instead, Starter at €149/mo through Business at €999/mo, so adding a contract pilot for one campaign does not change the bill or fragment the record. Our DroneBundle vs DroneLogbook comparison breaks down where the two platforms diverge on telemetry depth and reporting.
MobiLysis ran exactly this shape of project in Helsinki: six pilots across seven locations, 200 flight logs and 74 hours of flight time landing in one workspace rather than six phones. When the traffic management client asked for evidence of coverage, the record was already assembled.
Remote ID means your logbook is no longer the only record
Since Remote ID enforcement began in March 2024, every registered drone broadcasts its serial or session ID, position, altitude, velocity and takeoff location in the clear. Anyone within radio range with a receiver app can record it. That changes what a logbook is for.
Before Remote ID, your logbook was the only account of your flight, which meant sloppiness was mostly invisible. Now it is one account among several, and it can be contradicted. A neighbour with a receiver app, a competing operator on the same site, a facility security team, or an investigator working backwards from a complaint may hold a broadcast trace of a flight you logged loosely or did not log at all.
The FAA does not operate a national Remote ID recording network. The 2021 rule dropped the network broadcast requirement, so there is no central database of your flights sitting on a government server. What exists is a distributed, uncoordinated, permanent-enough set of third-party recordings.
The operational takeaway is not paranoia. It is precision.
Log the actual takeoff point, not "the site." Log the actual duration, not a rounded estimate. If a flight was aborted after 90 seconds, log the aborted flight. Discrepancies between your record and an independent trace do more damage in an investigation than the underlying issue usually would, because they shift the conversation from "was this flight safe" to "is this operator's paperwork reliable." The compliance side of Remote ID is well covered elsewhere. The record-keeping implication is the part people miss.
Automatic telemetry import mostly removes this risk. A log written by the aircraft agrees with the aircraft's broadcast because they come from the same GPS.
Retention periods nobody tells you about
US logbook guidance almost never states how long to keep records, because Part 107 sets no retention period. Operators flying outside the US, or planning for what comes next, face specific numbers.
EASA specific category: three years. Under UAS.SPEC.050(g) of Regulation (EU) 2019/947, the UAS operator must keep records of personnel qualifications and training for at least three years after those people leave, maintenance activities conducted on the UAS for a minimum of three years, and information on UAS operations including unusual technical or operational occurrences for a minimum of three years. This is a hard obligation, not a recommendation, and it applies to every operator holding an operational authorisation. If you fly in Europe, see our EASA compliance guide and the SORA process that generates much of what has to be retained.
Part 108, proposed: twelve months after employment. The FAA's BVLOS proposal, published 7 August 2025 and still a proposed rule as of August 2026 after two comment period reopenings, includes §108.40, which would require operators to keep records on each operations personnel member throughout employment and for 12 months after. Public comments, including from the New York City Bar Association, argued that 12 months is too short and that the FAA should additionally require operators to link individual personnel to the specific flights they operated. Whether or not that survives to a final rule, it tells you where the regulator's thinking is heading. Our Part 108 compliance checklist and Part 108 vs Part 107 comparison cover the broader shift.
Insurance and liability: longer than either. Hull and liability claims can surface long after the flight, and civil statutes of limitation for property damage or personal injury commonly run two to six years depending on the state. A record you deleted at 24 months because "the reg only said 12" is a record you cannot use to defend yourself at month 30. Our breakdown of insurance and liability for commercial drone services covers what carriers actually ask for at claim time.
The practical policy: keep everything, permanently, at whatever the cheapest storage tier is. Flight logs are kilobytes. There is no operational reason to ever delete one, and several expensive reasons not to.
What to record in a drone logbook
A commercial drone logbook entry should capture the flight, the aircraft state, and the decision context. Not every field carries the same weight, and treating them as equal is why manual logging feels like busywork.
| Field | Why it matters | Who asks for it |
|---|---|---|
| Date, start and end time (local + UTC) | Anchors the flight to weather, NOTAMs and airspace status | FAA, insurer, opposing counsel |
| Takeoff and landing coordinates | Proves where you actually were; reconciles with Remote ID | Investigator, client |
| Remote PIC name and certificate number | Establishes who was legally responsible | FAA, insurer |
| Aircraft serial and registration number | Ties the flight to the airframe record and its cycles | FAA, insurer, buyer at resale |
| Battery serials used | Enables cycle counting and failure pattern analysis | Maintenance, warranty claims |
| Flight duration and max altitude AGL | Demonstrates 400 ft compliance and utilisation | FAA, client |
| Operation type and authorisation | Part 107, waiver, LAANC authorisation number, recreational | FAA |
| Weather at time of flight | Shows §107.49 assessment happened | Insurer, investigator |
| Preflight inspection result | Shows airworthiness was checked | Insurer, investigator |
| Client, project or job reference | Turns the log into billable evidence and deliverable provenance | Client, accounting |
| Anomalies, warnings, aborted flights | The single most valuable field, and the least completed | Everyone, eventually |
The last row deserves emphasis. Logbooks full of clean flights prove nothing, because they look identical to logbooks that were filled in optimistically. A record that includes a compass error at Site 4, a battery pulled at 22% instead of 30%, and an aborted takeoff due to a gust reads as credible precisely because it is unflattering. Auditors and adjusters know this.
Weather deserves a note too. Recording "clear, 8 mph" from memory is weaker than an automatic capture of the METAR and forecast that applied at that coordinate at that minute. DroneBundle's weather integration attaches conditions to the flight record automatically, which also means your flight safety score reflects what the pilot was actually working with rather than what they remembered.
Maintenance actions belong in the aircraft log rather than the flight log, and they follow their own cadence. Our guides to drone maintenance and fleet maintenance scheduling cover that side.
Paper, spreadsheet, app, or operations platform
Most logbook comparisons offer two options, paper and digital. There are four, and the difference between the last two is where operators lose the most time.
Paper. The Standard by ASA, Parhelion's professional books and similar products remain genuinely good for one pilot with one or two aircraft. The tamper-resistance argument (ink is hard to backdate) is real. So is the failure mode: one coffee spill, one lost book, zero backups, no search, no export, and no way for a client to verify anything without physically seeing it. Fine below roughly 100 flights a year. Untenable above that.
Spreadsheet. Free, flexible, and the most common system in commercial drone operations by a wide margin. It also has no audit trail, which is the fatal flaw: any cell can be changed at any time by anyone with the link, with no record that it happened, which is exactly what an opposing expert will point out. We wrote a full breakdown of where spreadsheets break for drone operations. The short version is that spreadsheets fail not at data entry but at reconciliation, currency alerts and evidence quality.
Logbook app. Purpose-built flight logging with telemetry import. Solves the entry burden and gives you searchable, exportable, GPS-accurate records. This is the right answer for a solo operator or a two-person shop. The ceiling is that a logbook app logs flights and mostly stops there, so scheduling, client deliverables, maintenance triggers, certification currency and invoicing stay in other systems that have to be manually kept in sync. Airdata and DroneLogbook both sit here, with different strengths.
Operations platform. The logbook becomes a byproduct of running the business rather than a separate chore. The flight is planned against airspace and weather, approved through a workflow, flown, and the telemetry lands back against the same job automatically. DroneBundle matches imported DJI logs to projects by polygon overlap, extracts per-cell battery voltages and firmware versions from every flight, and supports 3D replay of the track. See the flight logs and telemetry feature page for the detail, or our guide to choosing fleet management software if you are comparing options.
The honest advice: do not buy an operations platform to solve a logbook problem. Buy one when the logbook is the fourth system you are keeping in sync by hand.
When the logbook and reality disagree
Automated logbooks introduce a class of error that paper never had: entries that are technically accurate and operationally misleading. This shows up the moment you try to use logged numbers to make a decision.
Battery swaps inflate flight counts. Most telemetry systems create a new flight record per power cycle. A three-hour corridor inspection with eight battery swaps becomes eight flights. Your logbook now says 1,400 flights when you have flown roughly 300 missions. Report "1,400 flights" to a client or an insurer and you will eventually have to explain the discrepancy against your invoices. Group by mission, count sorties separately, and label which number you are quoting.
Duplicate imports. Sync from the controller, then sync the same SD card, then have the pilot forward the same file, and one flight appears three times with slightly different timestamps. Deduplication by serial plus takeoff timestamp handles it. Manual cleanup does not scale past a few hundred flights.
Simulator and bench sessions. DJI flight simulator sessions and motor tests on a bench generate log files. They are not flights. If they land in the same log as real operations, your hours are wrong in the direction that looks worst: inflated experience you cannot substantiate. Filter or tag them at import.
Tethered and indoor operations. GPS-denied flights log poorly or not at all, and indoor inspection work can vanish from an otherwise automatic record. If a meaningful share of your work is indoors, you need a manual entry path that produces entries indistinguishable in structure from automatic ones.
PIC handoff mid-mission. Two pilots swapping controls during a long operation is common and almost never logged correctly, because the telemetry has no concept of who is holding the controller. Whoever is named as remote PIC in the record is the person the FAA will treat as responsible. That has to be set by a human, deliberately.
One operator, multiple aircraft. Where local rules permit multi-aircraft operation, the flights are concurrent, not sequential. Summing durations will overstate pilot hours. Track pilot flight hours as wall-clock time under command, separately from aircraft hours.
None of these are exotic. Every one of them shows up in an operation somewhere past its first year, and each one produces a number someone eventually relies on.
Making a logbook that holds up as evidence
A drone logbook is only worth what a skeptical third party will accept. Five properties separate a record that ends an argument from one that starts one.
Provenance. The entry should trace to machine-generated telemetry, not typed recollection. A DJI .txt or .DAT file retained alongside the parsed entry is the difference between an assertion and a source document.
Immutability with an audit trail. Entries should not be silently editable. Corrections are legitimate and necessary, but a correction must be visible as a correction, with who, when and what changed. This is the single property spreadsheets cannot provide and the one that decides credibility.
Contemporaneity. Records created at the time of the flight carry weight that records assembled afterward do not. Automatic upload from the controller timestamps itself; a batch of entries all created the week the lawyer's letter arrived does the opposite of helping.
Completeness including the bad days. Covered above, and worth repeating. Gaps read as concealment.
Exportability. If you cannot hand an investigator, an auditor or a client a clean CSV, PDF or KML of a defined date range within an hour, you do not really have a record, you have a database. DroneBundle supports full project and flight data export, and our position on who owns operational data is that it is yours, in original format, on request.
Add a sixth for teams: linkage. A flight record that connects to the pilot's certification status, the aircraft's maintenance state and the job's risk assessment answers questions a standalone logbook cannot. That linkage is the entire argument for treating logging as part of drone compliance rather than as clerical work, and it is what audit readiness and certification currency tracking are built on. See managing pilot certifications for the currency side.
Migrating off a logbook you have outgrown
Moving flight history between platforms is straightforward if you demand the original files and painful if you accept a summary export. Ask three questions before you commit to any drone logbook system.
Can you export the raw telemetry, not just the parsed summary? A CSV of dates and durations is a report. The original DJI, Autel or Parrot log file is the record. Only the second one can be re-parsed by whatever you use next.
Can you export on demand, without contacting support? Export behind a support ticket is a retention mechanism, and you will discover this at the worst possible moment.
Does the export include attachments? Checklists, risk assessments, incident notes, weather snapshots and approval signatures are usually where the compliance value sits, and they are usually what gets left behind.
Practical sequence: export everything from the old system first and verify the files open, then import into the new one, then run both in parallel for one billing cycle so you can compare flight counts and hours. Discrepancies always surface, and they are much easier to resolve while both systems are live. Keep the original export archived permanently regardless of how clean the migration looks. Our guide to drone flight data monitoring covers what to check once the history is in place, and the aircraft records need rebuilding against the imported flights before the cycle counts mean anything.
Frequently asked questions
Is a drone logbook required by the FAA?
No. Part 107 contains no flight logging requirement, and there is no drone equivalent of §61.51 for crewed pilots. §107.7 only compels you to produce records "required to be kept" under the regulations, and a voluntary logbook is not one. However, §107.9 requires safety event reports within 10 calendar days, waiver and authorisation applications ask for demonstrated experience, and insurers require flight records at claim time. In practice, operating commercially without a logbook is a business risk rather than a regulatory one.
How long should I keep drone flight logs?
Permanently, if you can. EU specific category operators are required by UAS.SPEC.050(g) to retain operational, maintenance and training records for a minimum of three years. The proposed Part 108 rule would require personnel records for 12 months after employment ends. Civil liability exposure typically runs longer than either, commonly two to six years in the US depending on state and claim type. Flight logs are tiny files, so there is no practical reason to delete them.
What is the difference between a pilot logbook and a drone logbook?
A pilot logbook records one person's cumulative flight experience across all aircraft they operate and follows the pilot through their career. A drone or aircraft logbook records a single airframe's usage, maintenance and component history and follows the aircraft, including at resale. Commercial operations need a third record, the operator log, which ties each flight to a client, an authorisation and a risk assessment. Most logbook products only build one or two of the three.
Can I use a spreadsheet as a drone logbook?
Legally, yes, since no format is mandated. Evidentially, it is the weakest option, because a spreadsheet has no audit trail, so any entry can be altered at any time with no record that it happened. That is the first thing an opposing expert or a claims adjuster will raise. If you stay on a spreadsheet, at minimum store the original telemetry files alongside it and keep dated, read-only backups so the entries have provenance.
Get the record without doing the paperwork
The problem with drone logbooks is not that operators do not understand their value. It is that manual logging competes directly with billable work, so it gets done last, badly, or from memory a week later. That is exactly when a logbook stops being useful as evidence.
DroneBundle removes the entry step. The log sync app runs on DJI Smart Controllers and RC Pro and uploads flights automatically as soon as the controller reconnects. Telemetry auto-matches to the right job by polygon overlap, battery health and firmware versions get extracted per flight, weather and airspace conditions attach themselves, and pilot certification currency is tracked against the same record. When an auditor, insurer or client asks, you export a date range instead of reconstructing a year.
Start your free trial and see your first flight log land in the right project without anyone typing a thing.
Or book a live demo and we will walk through what a defensible flight record looks like for the size of operation you actually run.
