US Drone Incident Reporting Under 14 CFR 91.7

US drone incident reporting is governed by a multi-rule framework that is frequently misunderstood by operators. The primary drone-specific reporting rule is 14 CFR § 107.9 (FAA reporting for serious injuries and ≥ $500 property damage). Separately, 49 CFR Part 830 governs NTSB reporting for serious incidents. The general airworthiness principle in 14 CFR § 91.7 — that no person may operate a civil aircraft unless it is in airworthy condition — applies as a general aviation principle that informs operator responsibility but is not itself a Part 107 reporting trigger.

This article delivers the complete 2026 incident reporting framework, the timing requirements, and the operational discipline that supports prompt and accurate compliance.

1. The Rule Hierarchy

Understanding when each rule applies is essential. An operator may need to report to both FAA and NTSB for the same event.

2. § 107.9 — The FAA Reporting Trigger

eCFR § 107.9: https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107/subpart-A/section-107.9

Under § 107.9, the operator must file a written report with the FAA within 10 calendar days if the operation involved:

Trigger 1 — Serious Injury

Serious injury includes:

• Hospitalization for more than 48 hours
• Bone fracture (excluding simple/hairline fractures of fingers, toes, or nose)
• Severe hemorrhage or damage to internal organs
• 2nd or 3rd degree burns covering more than 5% of the body surface
• Any injury to an internal organ

Trigger 2 — Loss of Consciousness

Any person losing consciousness as a result of the operation.

Trigger 3 — Property Damage ≥ $500

Damage to property other than the small unmanned aircraft itself, where the fair market value of repair or replacement is ≥ $500.

The damage threshold is fair market value, not the operator's out-of-pocket repair cost. A drone that strikes a vehicle and causes superficial damage repairable for $300 may still be reportable if the fair market value of repair (parts plus labor at standard rates) exceeds $500.

3. § 107.9 Reporting Workflow

Step 1 — Document the Incident Immediately

Within hours of the incident:

• Take photographs of the scene, damage, and injuries
• Capture witness statements
• Record exact time, location, and weather
• Save all manufacturer auto-logs from the aircraft
• Save all operational logs (LAANC ID, pre-flight check, flight path)

Step 2 — Notify the Insurance Carrier

Most policies require notification within 24–72 hours. Coordinate timing of insurance notification with FAA reporting timing.

Step 3 — File the FAA § 107.9 Report

Submit via FAA DroneZone at https://faadronezone-access.faa.gov/ within 10 calendar days. The report must include:

• Accident summary
• Injury or damage description
• Flight operation details (location, time, altitude, airspace)
• Aircraft information (registration, make, model, serial)
• Pilot information (Part 107 certificate number)
• Remedial actions taken

FAA FAQ on reporting: https://www.faa.gov/faq/when-do-i-need-report-accident How to submit: https://www.faa.gov/faq/how-do-i-submit-accident-report-under-small-uas-rule-part-107-faa

Step 4 — Track FAA Response

FAA may follow up with additional questions, witness interviews, or compliance reviews. Cooperate fully and document the interaction.

4. § 830.5 — The NTSB Reporting Trigger

eCFR Part 830: https://www.ecfr.gov/current/title-49/subtitle-B/chapter-VIII/part-830

Under 49 CFR § 830.5, the operator must immediately notify the nearest NTSB field office when an unmanned aircraft is involved in:

Trigger 1 — Aircraft Accident

• Any occurrence where a person suffers death or serious injury (NTSB serious-injury definition tracks the FAA definition above), OR
• The aircraft weighs 300 lb or more maximum gross takeoff weight and sustains substantial damage

Trigger 2 — Serious Incident

Collision with a manned aircraft in flight.

The NTSB advisory for UAS operators is at https://www.ntsb.gov/investigations/process/Documents/NTSB-Advisory-Drones.pdf.

Key NTSB Reporting Differences from § 107.9

For events that meet both triggers (e.g., a serious injury), the operator must file BOTH reports.

5. § 91.7 — Airworthiness Foundation

14 CFR § 91.7 establishes the general principle that no person may operate a civil aircraft unless it is in an airworthy condition. While § 91.7 is primarily a Part 91 manned aviation rule, the principle of operator responsibility for airworthiness is foundational across all FAA regulations.

For Part 107 operators, the equivalent rule is § 107.15 (condition for safe operation) combined with § 107.49 (pre-flight inspection). The operator is responsible for determining airworthiness before each flight.

eCFR § 107.15: https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107/subpart-A/section-107.15 eCFR § 107.49: https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107/subpart-B/section-107.49

A documented pre-flight inspection per § 107.49 is the operator's evidence that they discharged the airworthiness responsibility.

6. Common Incident Reporting Errors — A Gyoseishoshi Compliance Lens

As MmowW Drone is operated by a licensed Gyoseishoshi (行政書士) office, we observe these recurring errors:

Error 1 — Believing the threshold is the operator's repair cost The threshold is fair market value of repair or replacement, not the operator's out-of-pocket cost.

Error 2 — Missing the 10-day deadline Operators distracted by insurance, client communication, or personal stress may miss the 10-day FAA filing window. The deadline is firm.

Error 3 — Filing only with FAA when NTSB is also required A serious injury triggers BOTH § 107.9 (FAA, 10 days) and § 830.5 (NTSB, immediate). Filing only one is incomplete.

Error 4 — Failing to document the incident immediately Witness recall fades, weather changes, scene evidence disappears. Documentation within hours of the incident is critical.

Error 5 — Failing to coordinate with the insurance carrier Insurance policies typically require notification within 24–72 hours. Timing the FAA report and insurance notification together preserves both pathways.

Error 6 — Believing damage to the drone itself triggers reporting § 107.9 specifically excludes damage to the small unmanned aircraft itself. Only damage to OTHER property triggers reporting.

Error 7 — Treating "I think it was less than $500" as conclusive The fair market value standard is objective. Operator's subjective estimate is insufficient defense if FAA or insurance carrier estimates differently.

7. Severity Tiers and Appropriate Response

Criminal review may be triggered under 18 U.S.C. § 32 (destruction of aircraft / interference with civil aviation) for events where the operator's conduct rises to recklessness or willful misconduct.

8. Documentation for Incident Response

For incident response, retain:

1. Pre-incident flight log — complete log of the flight that produced the incident
2. Incident scene documentation — photos, video, witness statements
3. Manufacturer auto-logs — telemetry export
4. Operational logs — LAANC ID, NOTAM check, pre-flight inspection
5. § 107.9 report copy — FAA-submitted document
6. NTSB notification record — call log, NTSB reference number (if applicable)
7. Insurance notification record — claim number, communications log
8. Remedial action documentation — any steps taken to prevent recurrence

Retain for at least 3 years; longer for serious incidents that may have continuing legal implications.

9. Best Practice Workflow

Before any operation:

1. Maintain comprehensive flight logs
2. Verify Part 107 currency and aircraft registration
3. Ensure insurance is in force
4. Be familiar with § 107.9 and § 830.5 reporting triggers

After any incident:

1. Stop operations immediately
2. Document the scene within hours
3. Notify insurance within 24–72 hours
4. File § 107.9 with FAA within 10 calendar days
5. Notify NTSB immediately if applicable
6. Cooperate fully with all investigations

A SaaS like MmowW Drone integrates incident documentation, § 107.9 reporting workflow, and operational log retention — building the rapid-response capability that incident reporting demands.

Comply with FAA Drone Regulations Using MmowW Drone

Track every Part 107 requirement automatically.

Pilot certification, aircraft registration, flight logs, incident reporting — all in one SaaS.

Start Free Trial →

Disclaimer

This article provides legal information, not legal advice. MmowW Drone is operated by a licensed Gyoseishoshi (行政書士) office in Japan. We are not US attorneys or licensed FAA legal counsel. For binding legal opinions on FAA or NTSB compliance, consult a US-licensed aviation attorney.

Sources

1. 14 CFR § 107.9 — Safety event reporting — https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107/subpart-A/section-107.9
2. 49 CFR Part 830 — NTSB Notification — https://www.ecfr.gov/current/title-49/subtitle-B/chapter-VIII/part-830
3. FAA FAQ — When to Report an Accident — https://www.faa.gov/faq/when-do-i-need-report-accident
4. FAA FAQ — How to Submit Accident Report — https://www.faa.gov/faq/how-do-i-submit-accident-report-under-small-uas-rule-part-107-faa
5. 14 CFR § 107.49 — Pre-flight inspection — https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107/subpart-B/section-107.49
6. 14 CFR § 107.15 — Condition for safe operation — https://www.ecfr.gov/current/title-14/chapter-I/subchapter-F/part-107/subpart-A/section-107.15