When do drone accidents need to be reported to the NTSB?

A drone accident must be reported to the NTSB immediately when any person suffers death or serious injury, or when an unmanned aircraft that holds an airworthiness certificate sustains substantial damage. That is the current definition in the board's rules, and it means most small drone mishaps never reach the NTSB at all: a typical Part 107 aircraft holds no airworthiness certificate, so unless a person is seriously hurt, a destroyed quadcopter is an insurance conversation, not a board notification. When the definition is met, though, the obligations are immediate and specific.

This article separates the NTSB's requirements from the FAA's, walks through the accident definition and the 2022 change that reshaped it, and covers the mechanics of notifying the board and filing the follow up report. It ends with the uncomfortable truth about accident reports: they are written almost entirely from records that either exist before the crash or never will.

Two agencies, two different reports

Drone accidents can trigger two entirely separate federal obligations, and conflating them is the most common error in the field. The FAA's own rule requires a report within 10 calendar days when a Part 107 operation causes serious injury, loss of consciousness, or property damage beyond a modest dollar threshold, filed with the FAA. The NTSB's rules in 49 CFR Part 830 are a different regime with a different trigger, a different clock, and a different recipient, and satisfying one does nothing for the other.

The division of labor is straightforward once seen: the FAA regulates and enforces; the NTSB investigates accidents as an independent board. An event can require both reports, either one alone, or neither. A drone that breaks a car windshield may cross the FAA's damage threshold while falling far outside the NTSB's definition. A serious injury crosses both. The safe habit for any operation is to evaluate every mishap against both rule sets on the day it happens, in writing, so the file shows the decision was made rather than missed.

What counts as an unmanned aircraft accident

The controlling text is the definition in 49 CFR 830.2: an occurrence during the operation of a public or civil unmanned aircraft system, between activation for flight and deactivation after the mission, in which any person suffers death or serious injury, or the aircraft holds an airworthiness certificate and sustains substantial damage. Serious injury and substantial damage are themselves defined terms in the same section, with serious injury covering things like hospitalization beyond 48 hours, fractures beyond simple ones, and significant burns.

The definition changed in July 2022, and older guidance still circulating gets it wrong. The board removed the previous trigger, which keyed on aircraft with a maximum gross takeoff weight of 300 pounds or greater, and replaced it with the airworthiness certificate test, reasoning that smaller aircraft were increasingly flying higher risk operations where certification, not weight, marks the safety significant fleet. The practical effect cuts both ways: an uncertificated heavy lifter no longer triggers on damage alone, while a certificated aircraft of any size now does.

Immediate notification and the ten day report

When the definition is met, the operator must notify the nearest NTSB office immediately and by the most expeditious means available. Immediately means what it says: the notification happens before the wreckage is tidied, with the initial facts, aircraft, location, time, injuries, damage, operator contact, given as best they are known. Contact information for the board's offices is published on its website, and the call is short. What follows is preservation: wreckage and records are to be kept intact until the board releases them, because moving evidence is a decision the investigator makes, not the operator.

The formal filing comes next. An accident requires a report to the board on NTSB Form 6120.1 within 10 days, laying out the operation, the aircraft, the crew, and the sequence of events in detail. The form assumes the operator can produce specifics: pilot certificate data, aircraft identification, maintenance status, what the aircraft was doing and under what authority. Operators who have those answers in their records complete it as an unpleasant errand. Operators who do not discover that an accident investigation is a poor time to begin recordkeeping.

The report is written from records you either have or don't

Every field on an accident report corresponds to something that existed before the crash or cannot be conjured after it. Who was the remote pilot in command, and was their currency intact. Which airframe was it, with what maintenance history and what battery aboard. What authorization covered the flight, what the preflight found, what the crew briefing said. None of that can be reconstructed honestly from memory in the week after a serious injury, and investigators are professionally good at noticing when it has been.

The operations that come through investigations intact are the ones whose ordinary records already answered the questions: a pilot roster with certificate and currency dates, per aircraft histories, flight and job assignments, preflight and incident entries made when they happened. The accident plan then reduces to a short card, notify, preserve, pull the file, file the form, instead of an archaeology project. Nobody builds records for the crash. The programs that have them built them for Tuesdays, and the crash is simply the day the habit pays its full value.

Common mistakes in NTSB accident reporting

Applying the old 300 pound rule. The weight based trigger left the definition in July 2022. The current tests are death or serious injury, or substantial damage to an aircraft holding an airworthiness certificate, and stale checklists still citing weight get both directions wrong.

Assuming the FAA report covers it. The FAA's 10 day accident report and the NTSB's regime are independent obligations with separate triggers and recipients. An event can require both, and filing one while the other lapses is a violation of the one that lapsed.

Waiting to notify until facts are complete. The board's rule calls for immediate notification by the fastest available means, with the facts as known. Holding the call for a tidy narrative converts a compliant operator into a late one.

Cleaning up the scene. Wreckage, memory cards, and records are to be preserved until the board releases them. Recovering the aircraft to the truck and reformatting cards for the next job destroys exactly what the investigation exists to examine.

Documenting the decision only when reporting. Most mishaps will not meet the definition, and that conclusion belongs in writing too. A dated note showing the event was evaluated against Part 830 is the difference between a judgment and an oversight.

FAQ

Does a crashed Part 107 drone have to be reported to the NTSB?

Usually not. Most small drones hold no airworthiness certificate, so the NTSB definition is met only when a person suffers death or serious injury. Check the FAA's separate 10 day reporting rule as well, which has different triggers.

What changed in the NTSB drone accident definition in 2022?

The board removed the 300 pound maximum gross takeoff weight trigger and replaced it with an airworthiness certificate test. Substantial damage now matters when the aircraft holds an airworthiness certificate, regardless of its weight, and injury triggers are unchanged.

How fast does the NTSB have to be notified?

Immediately, by the most expeditious means available, to the nearest NTSB office, with the basic facts as known. The detailed accident report on Form 6120.1 follows within 10 days, built from the operation's own records.

What has to be preserved after a reportable drone accident?

The wreckage and the records of the aircraft and operation, held intact until the board releases them. That includes storage cards and logs, so recovery and cleanup decisions belong to the investigation, not to the crew's schedule.

Closing thought

The NTSB threshold is high enough that most drone programs will never make the call, which is precisely why the ones that must are unprepared. The rule asks almost nothing in advance, only that when the worst day comes, the operator notifies fast, preserves everything, and answers detailed questions from records that already exist.

That last requirement is the real assignment. If you are writing the accident response plan for a drone program, FlybyOps was built for the operational record problem at the center of regulated drone work. Incident reporting, a pilot registry with certification and currency, an equipment registry with per-airframe history, and an append-only audit log are all part of how the platform keeps the facts an accident notification needs written down before anyone has to ask for them.