Drone accident investigation: how it unfolds and which records get pulled

A drone accident investigation moves faster than most operators expect, and it starts by pulling records that either exist in order or do not. When an operation results in injury or meaningful property damage, reporting obligations to the FAA, and sometimes the NTSB, begin on a clock measured in days, and investigators will ask for the flight log, the maintenance history, the pilot's credentials, and the authorization the flight was conducted under. A program that has those assembled answers quickly; one that does not spends the investigation reconstructing them.

This article covers when an accident has to be reported and to whom, how the FAA and NTSB tracks differ, which records an investigation pulls, and how to have them ready before an incident rather than after. The reporting thresholds are specific, the two agencies impose separate duties, and the difference between a manageable investigation and a painful one is usually the state of the records going in.

When an accident must be reported

Under Part 107, the remote pilot in command has to report an accident to the FAA within ten calendar days when the operation results in either of two things. The first is serious injury to any person or any loss of consciousness. The second is damage to property, other than the drone itself, exceeding $500 to repair or replace, valued at the lower of the repair cost or the fair market value. The rule that sets this out, 14 CFR 107.9 on safety event reporting, is the reference for the thresholds and the deadline. It helps to read the property-damage threshold carefully, because it turns on the cost to repair or replace the damaged property, valued at whichever is lower, rather than on any estimate of what the drone or the mission was worth.

The report itself is specific. It includes the pilot's name and contact information, the pilot's airman certificate number, the aircraft's registration number, the location and time of the event, whether anyone was injured or killed, what property was damaged and to what extent, and a description of what happened. Filing goes through an FAA Regional Operations Center or the online reporting system. Missing the ten-day window, or filing an incomplete report, is itself a compliance problem layered on top of the accident.

The separate NTSB track

The FAA report is not the whole obligation, because the National Transportation Safety Board runs its own reporting regime with its own thresholds. Under the NTSB's rules, an operator must immediately notify the Board when an event meets its definition of an accident: a death or serious injury, or a drone that holds an airworthiness certificate sustaining substantial damage, or an aircraft weighing 300 pounds or more sustaining substantial damage. Midair collisions are reportable as well.

Two things follow from this that operators miss. Filing with the FAA does not satisfy the NTSB, and the reverse is also true; the duties are independent, and a reportable event can trigger both. And when an event is NTSB-reportable, the operator has a duty to preserve the wreckage and the associated records until the Board releases them, which means the flight data and maintenance history cannot be cleared or overwritten while an investigation is possible. Sub-55-pound recreational operations are generally outside both regimes, but commercial work under Part 107 is not.

Which records get pulled

When an investigation opens, the document requests are predictable. Investigators want the flight log for the operation, the maintenance records for the aircraft, the pilot's certificate and currency, the aircraft's registration, the terms of any authorization or waiver the flight relied on, and whatever incident documentation the operator produced. The common thread is attribution: each record has to tie a specific flight to a specific pilot and aircraft, without ambiguity. Investigators are not looking for volume; they are looking for a clear chain from the event back to the people and equipment involved, and gaps in that chain are what turn routine requests into pointed questions.

That attribution depends on how cleanly the operation was run. Software that can make each pilot's assigned jobs the only ones they can open keeps the flight record unambiguous, because the person who logged a job is the one assigned to it, and there is no question later about who was flying. An investigation is far smoother when the records already say who did what than when the program has to work backward from a pile of shared access.

Assembling records before you need them

The records an investigation pulls are ordinary operational documents; the problem is that they are usually scattered until the moment they are urgently needed. The time to organize them is before an incident, when a program can decide that every flight generates a log tied to a pilot and an aircraft, that maintenance and currency are tracked rather than remembered, and that the record cannot be quietly changed after the fact. A time-stamped, append-only history is exactly what an investigator trusts and what a reconstruction cannot fake.

There is also a cultural piece. Incidents and near-misses only become records if people report them, and people report more readily when doing so is easy and, where appropriate, anonymous. A program that captures incident reports, including an anonymous option, builds the history that a later investigation, or an internal review, depends on, and it surfaces the small problems that tend to precede the large ones before they become an accident to investigate. The goal is that when an investigation comes, the records it pulls are already assembled and time-stamped, not gathered in a scramble while a deadline runs.

Common mistakes in drone accident investigation

Misjudging the reporting threshold. Part 107 requires an FAA report for serious injury or for property damage, beyond the drone, exceeding $500. Assuming a small crash is below the line without checking the actual thresholds risks a missed filing.

Treating an FAA report as covering the NTSB. The FAA and NTSB impose separate duties with separate thresholds. A reportable event can require notifying both, and filing with one does not satisfy the other.

Clearing data after a reportable event. When an event is NTSB-reportable, the operator must preserve the wreckage and records until released. Overwriting flight data or maintenance logs during that window compounds the problem.

Missing the ten-day window. The FAA report is due within ten calendar days. A late or incomplete filing becomes its own compliance issue, separate from the accident that prompted it.

Keeping records that cannot attribute a flight. An investigation asks who flew and on what aircraft. Records that cannot tie a specific flight to a specific pilot and airframe leave the program reconstructing under pressure.

FAQ

When do I have to report a drone accident to the FAA?

Within ten calendar days, when a Part 107 operation causes serious injury, any loss of consciousness, or property damage beyond the drone exceeding $500 to repair or replace, valued at the lower of repair cost or fair market value.

Does reporting to the FAA also cover the NTSB?

No. The two agencies have separate reporting rules and thresholds. A single event can require notifying both, and filing with the FAA does not satisfy the NTSB, which must be notified immediately for events meeting its accident definition.

What records will an investigation ask for?

Typically the flight log, aircraft maintenance records, the pilot's certificate and currency, the aircraft registration, any authorization or waiver terms, and the operator's incident documentation. The records need to tie a specific flight to a specific pilot and aircraft.

Do I have to preserve anything after a reportable crash?

Yes, when the event is NTSB-reportable. The operator must preserve the wreckage and associated records until the Board releases them, which means flight data and maintenance logs should not be cleared or overwritten during that period.

Closing thought

A drone accident investigation rewards preparation and punishes improvisation. The FAA and NTSB thresholds are specific, the two duties are independent, and the records an investigation pulls are the same ones a well-run program already keeps. Knowing the clock, preserving what has to be preserved, and holding records that attribute every flight is what turns an investigation into a process rather than a crisis.

If you want the records ready before an investigation asks, FlybyOps was built for the operational record problem at the center of regulated drone work. Incident reporting with an anonymous submission option, a pilot registry with certification and currency tracking, an equipment registry with per-airframe hour rollups, and an append-only audit log are all part of how the platform has the records an investigation pulls already assembled and time-stamped.