If you crashed a drone, there are reporting requirements. Below we will discuss the reporting requirements you make to the FAA and the reporting requirements you make to the National Transportation Safety Board (“NTSB”) following a drone crash. Just to be clear, this whole page does NOT apply to Part 101 model aircraft.
“Contact the NTSB’s 24-hour Response Operations Center (ROC) at 844-373-9922 to file a report. A phone call is sufficient initially, but a written follow-up may be required.”
FAA REGIONALOPERATIONS CENTERS. LOCATION WHERE ACCIDENT OCCURRED:
Note that the NTSB’s definitions of accident and unmanned aircraft accident and the FAA’s definition of accident in 107.9 are ALL different. It would have been a good idea for the FAA to just match up the definitions of 107.9 to 830.2 to keep things simple.
Keep in mind that this article is primarily focusing on Part 107 operations, NOT Section 333 exemption operations, but most 333 exemptions have a provisions that requires notification to the FAA UAS Integration Office and NTSB so this article is still very relevant although some the requirements might differ. The language of the exemption and Blanket COA supersedes these requirements.
Report an “accident” or “serious incident” (Part 830’s definitions) immediately to the NTSB Response Operations Center.
Send NTSB Form 6120.1 in within 10 days for an accident or 7 days for an overdue aircraft that is still missing. For a serious incident and if requested, send in the form. No time is mentioned in 830.15.
Notify the FAA within 10 days of the occurrence of an accident (107.9 “accident”).
“NASA Form” is within 10 days of the violation.
During this 10 day period, you have time to call an attorney to help in figuring out how best to handle the situation and what to say in your report.
Don’t want to read? Watch the video of this article!
Who is the NTSB? How Are They Different than the FAA?
“The NTSB is an independent federal agency, charged by Congress to investigate transportation accidents, determine probable cause, and issue safety recommendations to prevent similar accidents. The agency’s scope extends beyond aviation crashes, as it also investigates selected rail, marine, highway, and pipeline accidents, as well as those involving transportation of hazardous materials.” The NTSB is COMPLETELY separate from the FAA. “The primary role of NTSB is improving safety of our nation’s transportation system. The agency determines the probable cause of accidents and issues safety recommendations to prevent similar occurrences. It does not determine fault or liability. In fact, according to 49 U.S.C. § 1154(b), ‘No part of a report of the Board, related to an accident or an investigation of an accident, may be admitted into evidence or used in a civil action for damages resulting from a matter mentioned in the report.’”
In addition to doing investigations, the NTSB can judge appeals of FAA enforcement actions brought against manned aircraft pilots and drone pilots. There are two levels of appeal with the NTSB: (1) the administrative law judge level (ALJ) and (2) the full board of NTSB members. Some of you might remember the Pirker case. The Pirker case was initially won at the ALJ level, but on appeal to the full NTSB Board, was remanded back to the ALJ to determine if Pirker’s flight was careless and reckless.
NTSB Advisory to Operators of Civil Small Unmanned Aircraft Systems in the United States
The use of small civil unmanned operating systems (sUAS) is growing rapidly, with changes happening on a nearly daily basis. In particular, the Federal Aviation Administration (FAA) and the Department of Transportation’s Office of the Secretary issued a new final rule on the operation and certification of small unmanned aircraft systems and the FAA recently issued a new “blanket Certificate of Waiver or Authorization (COA)” for commercial Section 333 and Public Aircraft operators.
The new Part 107 rule, the FAA Blanket COA, and other FAA authorizations for UAS operation, direct UAS operators to provide expedited notification to the FAA in the event that any of a series of enumerated occurrences take place during the operation of a UAS. Included in these instructions are reminders that the FAA procedures “are not a substitute for separate accident/incident reporting required by the National Transportation Safety Board (NTSB) under 49 CFR §830.5.” By means of this Advisory, the NTSB reminds operators of any civil UAS, other than those operated for hobby or recreational purposes, of the NTSB’s accident and incident reporting requirements in Part 830 of title 49, Code of Federal Regulations.
In August of 2010, the NTSB revised its Part 830 regulations to clarify that its accident and incident notification requirements apply to unmanned aircraft as well as conventional manned aircraft.Section 830.5 instructs operators of civil aircraft and certain public aircraft to immediately, and by the most expeditious means available, notify the NTSB when an accident or listed incident occurs.
An accident will result in the NTSB’s initiating an investigation and report with a determination of probable cause. In order to minimize the burden on operators of a small UAS and the NTSB, we have exempted from the definitions of “aircraft accident” and “unmanned aircraft accident” in section 830.2 of the NTSB regulations those events in which there is only substantial damage to the aircraft (no injuries), and the aircraft has a maximum gross takeoff weight of less than 300 pounds. This is what happened with the Facebook drone. You can read the NTSB crash report.
Although any of the incidents enumerated in section 830.5 would require the operator to notify the NTSB, the agency at its discretion may decide to conduct a full investigation with probable cause.
A civil UAS operator must immediately and by the most expeditious means, notify the NTSB of an accident or incident. An unmanned aircraft accident is defined in 49 C.F.R. § 830.2 as an occurrence associated with the operation of any public or civil unmanned aircraft system that takes place between the time that the system is activated with the purpose of flight and the time that the system is deactivated at the conclusion of its mission, in which:
(1) Any person suffers death or serious injury; or
(2) The aircraft has a maximum gross takeoff weight of 300 pounds or greater and sustains substantial damage.
Section 830.2 also provides definitions of what constitutes “serious injury” and “substantial damage”.
Operators must consider that the rest of the reporting requirements for serious incidents listed in section 830.5 apply regardless of UAS weight. Listed serious incidents that apply to small UAS include the following events:
Flight control system malfunction or failure: For an unmanned aircraft, a true “fly-away” would qualify. A lost link that behaves as expected does not qualify.
Inability of any required flight crewmember to perform normal flight duties as a result of injury or illness. Examples of required flight crewmembers include the pilot, remote pilot; or visual observer if required by regulation. This does not include an optional payload operator.
In-flight fire, which is expected to be generally associated with batteries.
Aircraft collision in flight.
More than $25,000 in damage to objects other than the aircraft.
Release of all or a portion of a propeller blade from an aircraft, excluding release caused solely by ground contact.
Damage to helicopter tail or main rotor blades, including ground damage, that requires major repair or replacement of the blade(s).
An aircraft is overdue and is believed to have been involved in an accident.
Below are examples of potential events.
A small multirotor UAS has a fly-away and crashes into a tree, destroying the aircraft: Not an accident, (though substantial damage, too small, and no injuries), but the operator is required to notify the NTSB of a flight control malfunction. NTSB may initiate an investigation and report with a determination of probable cause.
A small multirotor UAS has a fly-away and strikes a bystander causing serious injury: Accident (resulted in serious injury). The operator is required to immediately notify the NTSB. The NTSB must investigate the accident and determine a probable cause.
A small multirotor UAS hits a tree due to pilot inattention on a windy day: Not an accident (too small, even if substantial damage). However, the operator is required to notify the NTSB if other criteria of 830.5 are met. NTSB may initiate an investigation and report with a determination of probable cause.
A large, experimental UAS (400 lbs) has a structural failure and crashes in a remote area: Accident (substantial damage and gross takeoff weight of 300 lbs. or greater). The operator is required to immediately notify the NTSB. NTSB must investigate and determine a probable cause.
We’d also like to remind unmanned aircraft operators that none of Part 830 is intended to apply to hobbyist or recreational operators as described in section 336 of the FAA Modernization and Reform Act of 2012 and applicable FAA guidance.
We hope this advisory serves as a useful reminder to the UAS community that the NTSB remains committed to performing its long-standing mission to support air safety through accident and incident investigation, while placing a minimum burden on this growing industry.
This guidance applies to any unmanned aircraft operated under Part 107, 333, civil COA, experimental certificate, etc. UAS operators should note that they may have additional reporting requirements to the FAA, military, or other government agencies depending on the applicable regulations under which they are operating.
For further information or questions, you may contact:
After contacting the NTSB’s 24-hour ROC, your notification will be taken and forwarded to the appropriate NTSB division for processing. The reported event will be evaluated and a determination will be made whether or not the NTSB will investigate the event. All aircraft accidents as defined by 49 CFR 830.2 are investigated in some capacity, as are select incidents. If an investigation is opened into an event, an investigator will then contact the operator/reporting party to request additional information.
While I’m waiting, do I have to protect the aircraft wreckage?
(a) The operator of an aircraft involved in an accident or incident for which notification must be given is responsible for preserving to the extent possible any aircraft wreckage, cargo, and mail aboard the aircraft, and all records, including all recording mediums of flight, maintenance, and voice recorders, pertaining to the operation and maintenance of the aircraft and to the airmen until the Board takes custody thereof or a release is granted pursuant to §831.12(b) of this chapter.
(b) Prior to the time the Board or its authorized representative takes custody of aircraft wreckage, mail, or cargo, such wreckage, mail, or cargo may not be disturbed or moved except to the extent necessary:
(1) To remove persons injured or trapped;
(2) To protect the wreckage from further damage; or
(3) To protect the public from injury.
(c) Where it is necessary to move aircraft wreckage, mail or cargo, sketches, descriptive notes, and photographs shall be made, if possible, of the original positions and condition of the wreckage and any significant impact marks.
(d) The operator of an aircraft involved in an accident or incident shall retain all records, reports, internal documents, and memoranda dealing with the accident or incident, until authorized by the Board to the contrary.
I called the NTSB phone number. I am currently waiting for an NTSB investigator to contact me. Is there anything I can do now to assist the investigation?
If the event meets the criteria of 49 CFR 830 and is determined to be an aircraft accident, the NTSB investigator assigned to the case will require the operator to complete NTSB Form 6120.1 – Pilot Operator Aircraft Accident/Incident Report. 49 CFR 830.15 requires you file the form “within 10 days after an accident, or after 7 days if an overdue aircraft is still missing.” Should you be directed to complete Form 6120.1 – “Pilot/Operator Aircraft Accident/Incident Report”, please do as follows:
The form-fillable version can be edited and saved repeatedly, or simply printed and filled out manually using the free Adobe Acrobat Reader (or equivalent software).
DO NOT submit the form until you are contacted by an investigator and are provided with instructions regarding where to send the form. Forms can be submitted by email, FAX, or post mail.
Keep in mind that Form 6120.1 has many boxes and fields that are not very applicable to drone pilots. Just do the best you can in filling it all out. The investigator will contact you if there are any questions.
Filing of this report with the assigned investigator satisfies the requirements of 49 CFR 830.15 – Reports and statements to be filed. DO NOT submit a report form in-lieu of providing an initial notification of an aircraft accident to the NTSB ROC.
The Reporting Requirements to Make to the FAA
There are two types of reporting made to the FAA: (1) when there has been a deviation from the regulations and requested to report, and (2) when there has been an accident.
1. Upon Request Following a Deviation Due to an Emergency
107.21 In-flight emergency.
(a) In an in-flight emergency requiring immediate action, the remote pilot in command may deviate from any rule of this part to the extent necessary to meet that emergency.
(b) Each remote pilot in command who deviates from a rule under paragraph (a) of this section must, upon request of the Administrator, send a written report of that deviation to the Administrator.
2. After an Accident (Within 10 Days)
The FAA gives you 10 days to respond. I would highly suggest you take this time to contact an attorney. Remember that the FAA can prosecute you if you did something stupid.
107.9 Accident reporting.
No later than 10 calendar days after an operation that meets the criteria of either paragraph (a) or (b) of this section, a remote pilot in command must report to the FAA, in a manner acceptable to the Administrator, any operation of the small unmanned aircraft involving at least:
(a) Serious injury to any person or any loss of consciousness; or
(b) Damage to any property, other than the small unmanned aircraft, unless one of the following conditions is satisfied:
(1) The cost of repair (including materials and labor) does not exceed $500; or
(2) The fair market value of the property does not exceed $500 in the event of total loss.
“1. At least serious injury to any person or any loss of consciousness. A serious injury is an injury that qualifies as Level 3 or higher on the Abbreviated Injury Scale (AIS) of the Association for the Advancement of Automotive Medicine (AAAM). The AIS is an anatomical scoring system that provides a means of ranking the severity of an injury and is widely used by emergency medical personnel. Within the AIS system, injuries are ranked on a scale of 1 to 6, with Level 1 being a minor injury, Level 2 is moderate, Level 3 is serious, Level 4 is severe, Level 5 is critical, and Level 6 is a nonsurvivable injury. The FAA currently uses serious injury (AIS Level 3) as an injury threshold in other FAA regulations.”
“Note: It would be considered a “serious injury” if a person requires hospitalization, but the injury is fully reversible (including, but not limited to, head trauma, broken bone(s), or laceration(s) to the skin that requires suturing).” [“In addition to serious injuries, this rule will also require accident reporting for accidents that result in any loss of consciousness because a brief loss of consciousness may not rise to the level of a serious injury.”]
“2. Damage to any property, other than the small UA, if the cost is greater than $500 to repair or replace the property (whichever is lower).”
“Note: For example, a small UA damages a property whose fair market value is $200, and it would cost $600 to repair the damage. Because the fair market value is below $500, this accident is not required to be reported. Similarly, if the aircraft causes $200 worth of damage to property whose fair market value is $600, that accident is also not required to be reported because the repair cost is below $500.”
Why is the $500 number important?
When you do your pre-flight walk around, you should be figuring out what is $500 and cheaper in in the area. The FAA said, “Property damage below $500 is minimal and may even be part of the remote pilot in command’s mitigations to ensure the safety of the operation. For example, a remote pilot in command may mitigate risk of loss of positive control by positioning the small UAS operation such that the small unmanned aircraft will hit uninhabited property in the event of a loss of positive control.”
What Do I Report to the FAA?
Remember that the NTSB try to find causes to promote safety and does NOT do enforcement actions while the FAA DOES do enforcement actions. The FAA gave us a clue as to how they will handle this going forward, “the confined-area-of-operation regulations discussed in section III.E.3 of this preamble, such as the general prohibition on flight over people, are designed with the express purpose of preventing accidents in which a small unmanned aircraft hits a person on the head and causes them to lose consciousness or worse. Thus, if there is a loss of consciousness resulting from a small UAS operation, there may be a higher probability of a regulatory violation.”
You are really between a rock and hard place if there is a crash. Why? Because law enforcement or someone else will likely report the accident to the FAA. If you don’t report, you will get in trouble. If you do report, you COULD get in trouble. You might want to contact an attorney during this 10 day period before you file the report. Remember that everything you report can and will be used against you.
Submitting the Report. The accident report must be made within 10 calendar-days of the operation that created the injury or damage. The report may be submitted to the appropriate FAA Regional Operations Center (ROC) electronically or by telephone. Electronic reporting can be completed at www.faa.gov/uas/. Reports may also be made to the nearest jurisdictional FSDO (http://www.faa.gov/about/office_org/field_offices/fsdo/). The report should include the following information:
sUAS remote PIC’s name and contact information;
sUAS remote PIC’s FAA airman certificate number;
sUAS registration number issued to the aircraft, if required (FAA registration number);
Location of the accident;
Date of the accident;
Time of the accident;
Person(s) injured and extent of injury, if any or known;
Property damaged and extent of damage, if any or known; and
Description of what happened.
FAA REGIONALOPERATIONS CENTERS LOCATION WHERE ACCIDENT OCCURRED:
AK, AS, AZ, CA, CO, GU, HI, ID, MP,MT, NV, OR, UT, WA, and WY 425-227-1999
AR, IA, IL, IN, KS, LA, MI,MN,MO, ND, NE, NM, OH, OK, SD, TX, and WI 817-222-5006
Aviation Safety Reporting System (ASRS) aka “The NASA Report.”
The ASRS system is run by NASA which is why this report is nicknamed the “NASA Form” or the “NASA Report.” “The FAA also notes that the Aviation Safety Reporting System (ASRS) is available for voluntary reporting of any aviation safety incident or situation in which aviation safety may have been compromised. The FAA offers ASRS reporters guarantees and incentives to encourage reporting by holding ASRS reports in strict confidence and not using ASRS information against reporters in enforcement actions. Further, the FAA agrees that data collection is a valuable tool for determining a baseline for performance, reliability, and risk assessment. The FAA plans to develop a tool where remote pilots of small UAS can voluntarily share data which may not meet the threshold for accident reporting. This would provide a means for evaluation of operational integrity for small UAS.”
Unfortunately, the FAA said, “The FAA disagrees that SMS and ASRS systems should be covered on the [Part 107] knowledge test. . . . because ASRS is not currently required knowledge for part 61 pilot certificate holders.” This means you aren’t required to KNOW this but you SHOULD. On top of the FAA NOT requiring you to know this, they mention NOTHING about this report in AC 107-2. Remember, this report benefits you more than the FAA.
Keep in mind that the report goes to NASA, not the FAA. NASA is a completely separate agency from the FAA, just like NTSB. “There has been no breach of confidentiality in more than 34 years of the ASRS under NASA management.”
“The FAA considers the filing of a report with NASA concerning an incident or occurrence involving a violation of 49 U.S.C. subtitle VII or the 14 CFR to be indicative of a constructive attitude. Such an attitude will tend to prevent future violations. Accordingly, although a finding of violation may be made, neither a civil penalty nor certificate suspension will be imposed if:
(1) The violation was inadvertent and not deliberate;
(2) The violation did not involve a criminal offense, accident, or action under 49 U.S.C. § 44709, which discloses a lack of qualification or competency, which is wholly excluded from this policy;
(3) The person has not been found in any prior FAA enforcement action to have committed a violation of 49 U.S.C. subtitle VII, or any regulation promulgated there for a period of 5 years prior to the date of occurrence; and
(4) The person proves that, within 10 days after the violation, or date when the person became aware or should have been aware of the violation, he or she completed and delivered or mailed a written report of the incident or occurrence to NASA.
There are no limitations on how many NASA Reports you can file. Immunity will not be granted if you received an enforcement action and have been found in violation of the FAR’s within the previous 5 years from the date of occurrence.
So I should always file a NASA Report? It looks like a “get out of jail free card.”
No! If you did something criminal or were involved in an accident, then that information will NOT be deidentified before NASA sends the information to the Department of Justice for criminal actions or the FAA and NTSB for accidents. This means the report you filed with your name, phone number, address, and a whole bunch of other goodies is going to be sent over to the guys who can prosecute you! How convenient. So if you did something criminal or were involved in an accident, ESPECIALLY if you are unsure if you fall into one of those categories or not, you should contact me. Flying intentionally into a 99.7 TFR is a criminal penalty.
Keep in mind that this is a waiver from disciplinary action. You will still have a violation show up on your pilot record.
Great. So there aren’t any other issues with reporting?
Potentially. Section 91.25 says, “The Administrator of the FAA will not use reports submitted to the National Aeronautics and Space Administration under the Aviation Safety Reporting Program (or information derived therefrom) in any enforcement action except information concerning accidents or criminal offenses which are wholly excluded from the Program.” The problem is that is Part 91 and NOT part 107. The FAA didn’t include a Part 107 equivalent.
We know that NASA won’t give over the info. The FAA can find out a lot of info on their own and can initiate an enforcement action. The idea of the NASA Form was to prevent the imposition of a civil penalty or suspension when the FAA got the info on their own. The FAA indicated in the Part 107 preamble they would continue to honor the program. However, they could change their mind in the future, it isn’t a regulation, and go after people who have filed a NASA Form, but they would get insane amounts of pressure from the safety community to not do that. I’m just making you aware of this situation.
I hope this helps you guys understand what you need to do and when you need to contact me after a crash. Keep in mind that this was only about the FAA and NTSB, not about other potential liability issues that could come about as a result of the crash.
See 81 Fed. Reg. 42063 (June 28, 2016). This action fulfills Congress’s direction in section 332(b) of the FAA Modernization and Reform Act of 2012, Pub. L. 112-95, for the Secretary of Transportation and the FAA to issue a final rule on small unmanned aircraft systems that will allow for civil operations of UAS in the National Airspace System.
 Section 333 of the FAA Modernization and Reform Act of 2012 provides that “[i]f the Secretary of Transportation determines that … certain unmanned aircraft systems may operate safely in the national airspace system, the Secretary shall establish requirements for the safe operation of such aircraft systems in the national airspace system.”