A drone incident can create two separate federal reporting questions: whether the remote pilot in command must report the event to the Federal Aviation Administration, and whether the operator must immediately notify the National Transportation Safety Board. The triggers and deadlines are different, so treating them as one rule can lead to a missed report.
Key takeaway: Part 107 pilots should evaluate every serious incident against both 14 CFR 107.9 and 49 CFR Part 830. An event may require an FAA report, an NTSB notification, both, or neither.
FAA and NTSB reporting are separate systems
The FAA regulates civil aviation operations and pilot compliance. The NTSB investigates transportation accidents and certain serious incidents. The FAA’s Aeronautical Information Manual explicitly tells UAS operators that the two reporting systems are “separate and distinct.”
That distinction matters after a crash, flyaway, collision, injury, or equipment failure. A Part 107 pilot cannot assume that filing with one agency satisfies the other. The safest workflow is to document the facts once, evaluate both standards, and use the official reporting channel for each agency whose threshold is met.
When Part 107 requires an FAA report
Under 14 CFR 107.9, the remote pilot in command must report a qualifying operation to the FAA no later than 10 calendar days afterward. The rule is triggered when the small UAS operation involves at least one of these outcomes:
- Serious injury to any person.
- Any loss of consciousness.
- Damage to property other than the small unmanned aircraft when the repair cost exceeds $500.
- Total loss of property other than the small unmanned aircraft when its fair-market value exceeds $500.
Damage to the drone itself does not count toward the FAA’s $500 property threshold. Damage to a parked vehicle, roof, window, power equipment, another aircraft, or other third-party property can count. Use reasonable repair estimates and retain the documentation supporting the amount.
The injury and property triggers are independent. A person losing consciousness can create an FAA reporting obligation even when there is no property damage. Conversely, a drone that damages a vehicle by more than $500 can be reportable even when nobody is injured.
The FAA directs Part 107 operators to submit qualifying reports through FAADroneZone. Do not wait until the tenth day to begin gathering information. Photographs, witness names, aircraft records, repair estimates, flight logs, weather, airspace information, and a factual timeline are easier to preserve immediately.
When the NTSB may require immediate notification
NTSB notification uses a different standard and a much faster clock. 49 CFR 830.5 requires an aircraft operator to notify the NTSB immediately, using the most expeditious means available, after an aircraft accident or one of the serious incidents listed in the rule.
Under 49 CFR 830.2, an unmanned-aircraft accident includes an occurrence associated with operation of a public or civil UAS in which a person suffers death or serious injury. It also includes substantial damage to an unmanned aircraft that holds an airworthiness certificate. For many small consumer and enterprise drones without an airworthiness certificate, destruction of the aircraft alone does not satisfy that second accident definition.
However, operators must also consider the serious incidents listed in Section 830.5. Relevant examples can include a flight-control system malfunction or failure, in-flight fire, a collision between aircraft, or damage to property other than the aircraft estimated to exceed $25,000. The exact facts matter, and the NTSB—not the pilot’s insurer or equipment manufacturer—decides whether it will investigate.
The FAA’s current UAS guidance specifically states that any midair collision involving a UAS must be reported to the NTSB. If a possible NTSB trigger exists, contact the agency rather than delaying while trying to resolve every classification question alone. The NTSB accident-reporting page lists its 24-hour Response Operations Center at 844-373-9922 and explains what information to have ready.
Serious injury does not mean every minor injury
The agencies use defined terms. The NTSB definition of serious injury includes circumstances such as hospitalization for more than 48 hours beginning within seven days, certain fractures, severe hemorrhage or nerve, muscle, or tendon damage, internal-organ injury, and specified burns. The FAA’s Part 107 rule separately identifies any loss of consciousness as a reporting trigger.
Do not diagnose an injury merely to decide whether a report is required. Address immediate medical needs first, record what is known, and update the agencies if later medical information changes the classification.
What to do immediately after a drone incident
- Protect people. Stop the operation, call emergency services when needed, and remove immediate hazards.
- Prevent additional damage. Secure batteries and the surrounding area without disturbing evidence unnecessarily.
- Preserve the scene and records. Photograph the aircraft and impact area before moving items when safe to do so. Save controller logs, flight-app data, maintenance records, authorizations, checklists, crew statements, weather information, and relevant communications.
- Record facts, not conclusions. Note times, locations, aircraft identification, crew roles, observed damage, injuries, and witness contact information. Avoid guessing at a technical cause before the evidence is reviewed.
- Evaluate both reporting systems. Compare the event separately with 14 CFR 107.9 and 49 CFR Part 830.
- Notify other required parties. Follow applicable emergency, client, property-owner, employer, insurer, waiver, authorization, and state or local reporting procedures.
Under 49 CFR 830.10, an operator involved in an NTSB-reportable event has duties concerning preservation of wreckage and records. Wreckage may be moved when necessary to remove injured or trapped people, protect it from further damage, or protect the public. When movement is necessary, document original positions and significant impact marks when possible.
Five common reporting scenarios
| Scenario | Likely reporting question |
|---|---|
| A non-certificated drone is destroyed, with no injury or damage to other property. | Part 107.9 is generally not triggered by damage to the drone alone. Check NTSB serious-incident criteria before concluding no notification is needed. |
| The drone causes $650 in documented damage to a parked vehicle. | The FAA’s property-damage threshold is exceeded, so a report is due within 10 calendar days. Evaluate NTSB criteria separately. |
| A person briefly loses consciousness after being struck. | Part 107.9 specifically treats any loss of consciousness as reportable. Immediate NTSB notification depends on whether the event meets its accident or serious-incident definitions. |
| The drone collides with another aircraft in flight. | Notify the NTSB immediately. An FAA report may also be required depending on injury or property damage. |
| A control-system failure occurs but the drone lands without damage. | The FAA’s injury and property thresholds may not be met, but flight-control-system failure appears among the NTSB’s listed serious incidents. Contact the NTSB for direction. |
These examples are screening tools, not legal determinations. Waivers, certificates of authorization, public-aircraft operations, air-carrier rules, insurance policies, contracts, and state requirements can impose additional reporting duties.
Build reporting into your operating procedures
A reporting checklist belongs in the operating manual before an incident happens. Assign responsibility for emergency response, scene preservation, client notification, record collection, regulatory review, insurer contact, and final submission. Keep current agency links and phone numbers available offline in case the event occurs where connectivity is poor.
This is also a business-readiness issue. Our guide to starting a drone inspection business explains why documented workflows matter, while the Part 107 preparation guide covers the certification foundation. Operators should incorporate incident-response time, recordkeeping, insurance, and risk controls into their service planning rather than treating them as paperwork after the fact.
The practical next step
Download or write a one-page incident checklist today. Include the FAA’s 10-day triggers, the NTSB’s immediate-notification triggers, the NTSB Response Operations Center number, your insurer and client contacts, and a list of records to preserve. Review it with anyone who serves as remote pilot in command, visual observer, or field lead.
This article provides general educational information, not legal advice. Regulations and agency procedures can change; verify the current rule and official reporting instructions for the specific operation and event.