Short answer: most drone incidents are preventable, and they rarely start with a mystery failure
Most drone incidents traced in official investigations do not begin with a drone suddenly behaving in an inexplicable way. They begin with a planning gap, a misunderstood automated feature, a flight in the wrong airspace, or a decision to keep flying when conditions had already changed. That is the useful pattern in this guide. If you fix the planning, the airspace check, the battery and signal margins, and the decision to land early, you remove the conditions behind a large share of reported trouble.
This guide recommends no drone, gives no buy box, and contains no affiliate link. That is deliberate. The keyword "drone incidents" is a safety and regulatory topic, not a shopping question. Forcing it into a product roundup would answer a question nobody asked, and it would imply that buying a particular model is the safety answer. It is not. A careful pilot with an ordinary drone is safer than a careless pilot with an expensive one, and the rules in this guide apply across brands and models.
This guide is research based. It draws on United States Federal Aviation Administration (FAA) guidance, National Transportation Safety Board (NTSB) investigation reports, and published analyses of FAA sighting data, all cited in this guide. It does not claim hands on testing, and it does not invent incident details, dates, casualty figures, or regulatory claims. Where a source is old, contested, or limited, this guide says so. Rules change, so always confirm the current FAA position before you fly. This guide is general information, not legal advice.
What counts as a drone incident, and why the words matter
People use the word incident loosely, and that looseness causes confusion. A crash into a tree, a near miss reported by a pilot, a drone sighted near an airport, and a drone that interferes with firefighting are not the same kind of event, and they are not investigated in the same way.
A sighting is a report that a drone was seen. It is not, by itself, proof that a drone was where it was reported, that it was flown unlawfully, or that a collision nearly happened. Published analyses of FAA sighting data make exactly this point: many reports describe something seen at a distance, and later review sometimes finds a legitimate flight, a different object, or an altitude that was misjudged. Treat every sighting headline with that caution. A high sighting count is a reason to improve airspace discipline, not a precise count of dangerous flights.
A close encounter is stronger than a sighting. In the Bard College Center for the Study of the Drone analysis of FAA reports from August 2015 to January 2016, a close encounter was defined as an event where a drone came within 500 feet of a manned aircraft, where a pilot declared a near midair collision, where a pilot took evasive action, or where the pilot used language indicating the drone was dangerously close. That analysis found 188 close encounters out of 519 unique reports in that period. Those figures are historical, from a specific early data set, and they must not be quoted as current rates. Their value is narrower: they show that even in early data, most reports were sightings rather than close encounters, and that altitude and airport proximity were recurring features.
An accident, in the NTSB sense, is narrower still. For civil unmanned aircraft, NTSB notification rules turn on outcomes such as death or serious injury, or on substantial damage to a larger aircraft, plus a list of serious incidents such as flight control malfunction, in flight fire, and in flight collision. A small recreational drone that crashes into a tree with no injury and no damage to anything else may still matter to its owner, but it is not automatically an NTSB accident. The reporting section later in this guide explains the thresholds that do apply, and why recreational and commercial flights are treated differently.
Keeping these distinctions straight matters for two practical reasons. First, it stops a reader from treating every headline as proof that the sky is full of collisions. Second, it stops a pilot from dismissing a real risk because some reports turn out to be mistaken. Both errors lead to bad decisions. The first leads to fear without action. The second leads to complacency.
The incident patterns that keep repeating
The table below summarises patterns that appear across FAA guidance, NTSB reports, and sighting analyses. It is a pattern summary, not a statistical ranking. No pattern is given a percentage in this guide unless a cited source gives it for a defined data set, because mixing data sets with different definitions would produce a false ranking.
| Pattern | What typically happens | What prevents it most often |
|---|---|---|
| Loss of control or flyaway | The drone stops responding as expected, drifts, or fails to return as planned, often after a control, GPS, or link problem, or after the pilot misunderstands an automated mode. | Preflight checks, a clear home point set in open ground, signal and battery margins, and knowing how to exit an automated mode. |
| Return to home trap | Return to home flies toward a home point that is no longer safe, or the pilot keeps re engaging it instead of taking manual control. | Set the home point away from obstacles and restricted zones, check the return path, and practise exiting return to home before you need to. |
| Airspace intrusion | A flight enters controlled, restricted, or temporarily restricted airspace, often near an airport, a stadium, a prison, a military site, or an emergency scene. | Check airspace and temporary restrictions before every flight, get authorisation where required, and do not rely on an app alone. |
| Flight over people or near manned aircraft | A drone is flown where people below or aircraft nearby leave no margin for a failure. | Keep the required separation, give way to manned aircraft always, and do not fly over people unless the applicable rules and the aircraft category genuinely allow it. |
| Battery and weather margin failure | A flight continues until the battery, wind, or visibility leaves no safe return margin. | Land with reserve power, respect wind limits, and treat a rising wind or falling light as a landing signal, not a challenge. |
| Emergency scene interference | A drone is flown near a wildfire, a rescue operation, or another emergency, forcing manned aircraft to pause or divert. | Never fly near an active emergency scene unless you are an authorised part of the response. If you see smoke or emergency aircraft, land and leave. |
| Swarm and show programming error | In a multi drone show, a wrong centre, heading, or selection puts aircraft on crossing paths. | Independent verification of show centre, heading, and aircraft selection, plus separation margins that survive a single input error. |
Each pattern is examined below with the evidence that supports it, and with the limits of that evidence stated plainly.
Loss of control, flyaways, and the automated mode trap
Loss of control is a broad label. It can mean a genuine equipment failure, a lost link, a GPS problem, or a pilot input that the aircraft correctly followed but the pilot did not intend. Investigations often cannot separate those causes from a short description alone, and this guide does not pretend otherwise. What investigations do show repeatedly is that the pilot's response in the first seconds matters as much as the original fault.
The Young Harris, Georgia case, investigated by the NTSB as CEN21LA224, is a clear example. On 6 May 2021, a DJI Matrice flown under Part 107 for a demonstration flight near a prison was involved in an event that caused one serious injury. The pilot had set the home point within a buffer zone around a restricted zone without realising the restricted zone was there. About seven minutes after takeoff, the pilot started return to home. The drone flew toward the set home point, reached the buffer zone boundary, and would not proceed further. Landing attempts were blocked by vehicles on the ground, and the buffer zone prevented relocation while return to home stayed active. The pilot exited return to home four times, which would have allowed manual control, but each time reactivated it within a few seconds, so manual inputs were again blocked. The pilot then grabbed the landing gear, tried to move the drone, handed the controller to another person, and tried to remove the batteries. A propeller blade struck the pilot's right hand several times, causing serious injury. The NTSB analysis states plainly that the pilot could have landed manually if return to home had been exited, and that preflight planning should have found the restricted zone and placed the home point and landing zone further away.
Read that case as a checklist, not as a story about one pilot. The failures were stacked: an unrecognised restricted zone, a home point inside its buffer, a return path that was never checked, and repeated re engagement of the very mode that was preventing a landing. Remove any one of those, and the outcome changes. That is why the preflight section of this guide puts home point placement and return to home practice before any discussion of camera settings or flight modes. Automated features are useful only when the pilot knows how to turn them off.
A related lesson applies to any lost link or flyaway. A lost link that behaves as expected, for example a drone that climbs or returns exactly as programmed, is not the same as a flight control malfunction, and reporting rules treat them differently. But from the pilot's side, the practical response is similar: do not chase the drone, do not grab it while propellers are turning, and do not keep re engaging an automated mode that is blocking manual control. Land, or let the programmed safe behaviour complete, and inspect before any further flight. Never reach for a spinning propeller. That single rule would have prevented the injury in the Young Harris case.
Drone shows: when one wrong input affects hundreds of aircraft
Multi drone shows deserve separate attention because their failure mode is different from a single pilot error. One wrong centre, heading, or selection does not affect one aircraft. It affects the whole formation, and the separation that normally protects aircraft from each other can disappear at once.
The NTSB final report DCA25LA065, for an accident in Orlando, Florida on 21 December 2024, describes exactly this pattern. During the initial phase of a 500 small unmanned aircraft drone light show, multiple aircraft failed to achieve proper spatial separation, resulting in midair collisions and loss of control. Several aircraft entered the audience area, and one spectator suffered a serious injury. The report attributes the event to cumulative errors: the uploaded show centre was incorrect by about 5 metres, which caused the system to assign incorrect aircraft to flight paths, and the show heading had not been entered correctly and was rotated by about 7 degrees. When the show centre location was updated, only 498 drones were selected rather than 500, so two drones had different show centre positions from the others. The heading misalignment moved the show flight position by about 18 metres, closer to the audience. A policy change 12 days before the accident had also reduced the margin between the soft geofence and the hard geofence from 5 metres to 1 metre.
The lesson is not that drone shows are inherently unsafe. It is that show safety depends on independent verification, not on one person's data entry. A centre, a heading, and a selection count are each a single point of failure when they are entered once and trusted. A safer process checks each one independently, confirms the selection count matches the fleet count, and keeps a separation margin that can absorb a small input error without putting aircraft over people. The reduction of the geofence margin in this case is a useful warning: a margin that looks generous on paper can be quietly reduced by a policy change, and nobody notices until it is needed.
For a recreational pilot, the direct application is smaller but real. If you fly more than one aircraft, if you use a waypoint mission, or if you rely on a mapped flight plan, check the plan the same way: centre, heading, count, and margins, verified before takeoff, not discovered during flight.
Near airports and near manned aircraft: sightings, altitude, and the 400 foot line
Airport proximity is the most reported pattern in FAA sighting data, and also the most misread. The Bard analysis of the 2015 to 2016 data set found that three out of five incidents occurred within five miles of an airport, and that nine out of ten incidents with a reported altitude occurred above 400 feet. Those figures describe that historical data set only. They do not prove that nine out of ten drone flights today are above 400 feet, because sighting reports are not a random sample of all flights. Flights near airports and flights at higher altitudes are simply more likely to be seen and reported by manned aircraft pilots.
Even with that caveat, the pattern points to a real discipline problem. The recreational ceiling in uncontrolled airspace is 400 feet above ground level, and controlled airspace near airports requires prior authorisation at or below the authorised altitude. A drone reported at 2,000 feet, 4,000 feet, or 4,300 feet near an airport, as in examples from more recent FAA sighting summaries, is either in airspace it should not be in, at an altitude it should not be at, or both, unless it is an authorised operation. The fact that some reports later turn out to be mistaken does not erase the cases that are genuine, and it does not change the rule for the next flight.
The practical rule is simple and strict. Give way to manned aircraft in all cases. If you see or hear a manned aircraft, descend and move away, and do not wait to judge whether it will pass clear. Do not fly in controlled airspace without authorisation, do not fly above 400 feet in uncontrolled airspace, and do not assume that because you cannot see an airport, you are clear of its traffic. Aircraft on approach and departure cover ground quickly, and a drone that is legal at one moment can become a conflict seconds later if it is near a flight path.
There is a second, quieter airport lesson. Some reported sightings involve authorised flights, or objects that were not drones at all. That is why this guide does not repeat individual recent sighting claims as confirmed incidents. A reader who wants the current picture should read the FAA sighting data itself, with its own caveats, rather than relying on a headline count. The safety action does not depend on the exact count. It depends on staying out of controlled airspace without authorisation and staying below the ceiling.
Wildfires and emergency scenes: the incident where looking is the harm
Flying near a wildfire to film it is not a victimless curiosity. It is one of the few drone incidents where the act of observing directly creates the danger, because firefighting aircraft operate low, in smoke, on tight orbits, and with limited ability to scan for a small drone.
FAA safety material on wildfire operations states the position plainly: if you see wildfire smoke, fly away or land immediately, unless you are an authorised part of the emergency response. The same material warns that not every firefighting operation has a temporary flight restriction in place when response begins, that restrictions can be enacted rapidly, and that smoke itself is the cue to clear the area, even if an app does not yet show a restriction. Fire agencies have repeatedly reported that unauthorised drones forced helicopter and airplane operations to stop, because crews could not fly safely until the area was confirmed clear. The delay is measured in minutes or hours during which a fire continues to spread.
The same principle applies to other emergency scenes: rescue operations, police incidents, and disaster response. The drone does not need to collide with anything to cause harm. It only needs to force a pause, a diversion, or a change of plan by crews who cannot see it clearly and cannot wait. State and local rules add further limits in many places, including rules against impeding emergency personnel, but the federal safety point stands on its own: stay away from emergency scenes, do not fly to watch, and never assume that the absence of a published restriction means the airspace is clear.
This is also the pattern where enforcement is most visible to the public, because fire agencies report unauthorised flights to the FAA and to law enforcement, and civil penalties for interfering with fire suppression have been publicised as exceeding 20,000 dollars in federal material. Penalty figures change and depend on the specific law and facts, so this guide does not present a single figure as the penalty for every case. The point is narrower and more durable: interference with emergency operations is treated as a serious violation, not as a minor paperwork issue.
The rules in plain form: recreational flyers and Part 107
United States drone rules have two main tracks for small drones, and confusing them is itself a common source of incidents. The tracks are summarised below from FAA guidance. This summary is not a substitute for the FAA pages, and a pilot whose flight benefits a business, an organisation, or a monetised project should assume the commercial track applies until the FAA position is confirmed.
| Question | Recreational flyer (49 U.S.C. 44809) | Part 107 commercial operator (14 CFR Part 107) |
|---|---|---|
| Purpose | Purely for fun or personal enjoyment. | Any other purpose, including paid work, business benefit, and many volunteer or goodwill flights for an organisation. |
| Knowledge test | Pass the free Recreational UAS Safety Test (TRUST) and carry proof. | Hold an FAA Remote Pilot Certificate, earned by passing the FAA knowledge test. |
| Registration | Required at 0.55 pounds (250 grams) or more. A single recreational registration covers the flyer's drones. | Required for every drone, regardless of weight. |
| Remote ID | Required where the drone is registered or must be registered, except in an FAA Recognised Identification Area under the applicable conditions. | Required where the drone is registered or must be registered, except in an FAA Recognised Identification Area under the applicable conditions. |
| Visual line of sight | Keep the drone within visual line of sight, or use a visual observer standing next to the pilot and in direct communication with the pilot. | Keep the drone within visual line of sight, subject to the Part 107 rules and any waiver. |
| Altitude in uncontrolled airspace | At or below 400 feet above ground level. | At or below 400 feet above ground level, subject to Part 107 operating limitations. |
| Controlled airspace | Prior FAA authorisation through LAANC or DroneZone, at or below the authorised altitude. | Prior FAA authorisation through LAANC or DroneZone, at or below the authorised altitude. |
| Give way | Give way to manned aircraft, always. | Give way to manned aircraft, always. |
| Community safety guidelines | Fly in accordance with the safety guidelines of an FAA recognised community based organisation. | Follow Part 107 operating rules, including any applicable waiver conditions. |
Three details in that table are worth pausing on, because each one is a common incident trigger. First, weight is not the only registration test. A recreational drone under 250 grams is generally not required to be registered, but a Part 107 drone must be registered regardless of weight. Second, Remote ID follows registration. A drone that must be registered must generally broadcast Remote ID, and flying without it outside an approved identification area is a violation, not a technicality. Third, authorisation is about the airspace, not about the pilot's skill. A skilled pilot without authorisation in controlled airspace is still unauthorised, and an authorised pilot must still stay at or below the authorised altitude.
Rules outside the United States differ, and this guide does not summarise them as if they were the same. The United Kingdom, for example, has its own Air Accidents Investigation Branch reports for unmanned aircraft, with recurring themes of loss of control, GPS problems, and geofence excursions. The pattern is similar, but the registration, competency, and airspace systems are not interchangeable. A pilot flying abroad should check the host country's rules before travelling, not assume that a United States registration or test carries over.
Reporting after an incident: who must report, and when
Reporting rules are where recreational and commercial flights diverge most sharply, and where well meaning advice often goes wrong by applying one track's rule to the other.
For Part 107 operations, 14 CFR 107.9 requires the remote pilot to report an accident to the FAA within 10 days if the event involves serious injury to any person or loss of consciousness, or damage to property other than the unmanned aircraft itself where the repair cost exceeds 500 dollars, or the fair market value exceeds 500 dollars in the event of a total loss. The report goes through the appropriate FAA Regional Operations Center, online, or by telephone, and includes the pilot's details, certificate number, aircraft registration, location, date, time, and a description of the event and any injury or damage.
NTSB rules are separate, and they apply in addition to the FAA rule, not instead of it. Under 49 CFR Part 830, civil and public unmanned aircraft operators must immediately notify the nearest NTSB office of an unmanned aircraft accident, defined in that context as an event where a person suffers death or serious injury, or where an aircraft of at least 300 pounds sustains substantial damage. Serious incidents listed in 49 CFR 830.5 also require notification, including flight control system malfunction or failure, inability of a required crewmember to perform normal duties because of injury or illness, in flight fire, in flight collision, and damage of more than 25,000 dollars to objects other than the aircraft. A true flyaway qualifies as a flight control malfunction for this purpose, while a lost link that behaves as programmed does not. These thresholds are specific, and a pilot who is unsure whether an event qualifies should seek guidance promptly rather than assuming it does not.
Recreational flights under 55 pounds that meet the model aircraft definition have historically been treated differently. AOPA's summary of the FAA and NTSB rules notes that neither set of reporting requirements described above applies in the same way to hobby or recreational aircraft under 55 pounds, and that the NTSB has historically excluded hobby and recreational unmanned aircraft from its accident rule and has not investigated the rare occasions when a model aircraft caused serious injury or fatality. That historical position is not a promise that a recreational crash will never be investigated, and it is not a reason to hide a serious event. A recreational pilot who causes injury or property damage should still contact local law enforcement where appropriate, preserve evidence, and seek advice, because state and local laws, insurance, and civil liability apply independently of the federal reporting thresholds.
For any pilot, the immediate steps after an incident are the same, regardless of the reporting track. First, make people safe: call emergency services if anyone is injured, and do not move an injured person unless they are in immediate danger. Second, stop flying the damaged aircraft, keep people away from spinning propellers and damaged batteries, and treat a swollen, hot, or punctured battery as a fire risk. Third, preserve what happened: note the time, location, weather, flight mode, and any warnings, and keep flight logs and damaged parts where they can be examined. Fourth, report through the correct channel for your flight type, and do not fly the same aircraft again until it has been inspected and any fault is understood. A crash that is flown again without inspection is often the second incident, not the end of the first.
A preflight checklist built from the incident record
Checklists work when they are short enough to use every time. The list below is built directly from the patterns above, and each item maps to a real failure mode, not to a generic safety slogan.
- Airspace first. Check the location and time against current airspace data and temporary restrictions. Confirm controlled airspace authorisation before takeoff, not after. If you see smoke, emergency aircraft, or a stadium event, treat the area as closed unless you are an authorised part of the response.
- Home point and return path. Set the home point in open ground, away from obstacles, water, roads, and restricted zones. Check the return altitude and return path for obstacles. Know how to exit return to home and take manual control, and practise it in a safe place before you need it.
- Battery and signal margins. Start with a full battery, check the return margin for wind, and set a personal landing reserve that is higher than the aircraft's low battery warning. If the wind is rising, land early. A flight that ends with a forced landing has already failed the margin test.
- Visual line of sight and give way plan. Confirm you can keep the drone in sight for the whole planned flight, or that a visual observer is in place. Decide in advance what you will do when a manned aircraft appears: descend and move away immediately.
- People and property below. Check who and what is below the flight path, not just at the takeoff point. Do not fly over people, crowds, roads with moving traffic, or emergency operations unless the applicable rules genuinely allow it and the risk is acceptable.
- Aircraft condition. Inspect propellers, arms, battery, and sensors before flight. Do not fly a damaged aircraft, a swollen battery, or an aircraft with an unresolved warning. A warning that is dismissed on the ground becomes a failure in the air.
- Registration, test, and Remote ID. Carry proof of TRUST or your Remote Pilot Certificate as applicable, carry registration proof where required, and confirm Remote ID is broadcasting where required. These are not paperwork for its own sake. They are how an authorised flight is distinguished from an unauthorised one after an incident.
- Weather and light. Check wind, visibility, and light for the whole flight, not just takeoff. Low light, fog, and strong gusts each reduce the margin for recovery, and each is a reason to shorten or cancel the flight.
If any item fails, the safe decision is to change the plan or cancel the flight. A cancelled flight costs an afternoon. A flight that proceeds past a failed check can cost far more, and the incident record shows that pilots who push past one failed check often push past the next one as well.
Mistakes to avoid, stated plainly
Do not fly above 400 feet in uncontrolled airspace to get a better view, and do not assume that height is safe because you cannot see an aircraft. Altitude reports in sighting data show that height is precisely where conflicts are reported.
Do not fly in controlled airspace on the assumption that a small drone will not be noticed. Authorisation exists to separate drone traffic from manned traffic, and the absence of a visible aircraft at takeoff is not authorisation.
Do not fly over people, over a crowd, or over an emergency scene to get footage. The footage is not worth the risk to people below, and the flight may force emergency aircraft to stop.
Do not grab a drone with spinning propellers, and do not keep re engaging an automated mode that is preventing a landing. Exit the mode, take manual control, and land in open ground. If manual control is not possible, let the programmed safe behaviour complete and keep people clear.
Do not fly a damaged drone, a damaged battery, or a drone with an unresolved warning to see if it still works. Inspection on the ground is cheaper than a second incident in the air.
Do not treat a sighting report as proof of a collision, and do not treat a mistaken report as proof that all reports are mistaken. Read the data with its caveats, and fly as if the next report could be about your flight.
Do not rely on a single app, a single map, or a single data entry for airspace, show programming, or a waypoint mission. Check the critical inputs independently, confirm counts and centres, and keep margins that survive a small error.
Frequently asked questions
There is no single verified ranking that covers all drone flights, because sighting data, investigation reports, and enforcement data use different definitions and different samples. What the record does show, repeatedly, is a cluster of preventable causes: poor preflight planning, airspace errors, misunderstood automated features such as return to home, insufficient battery and weather margins, and flights near people, airports, or emergency operations. A guide that names one cause as the most common without naming its data set would be inventing a ranking, and this guide does not do that.
Confirmed collisions between civil drones and civil manned aircraft have been rare in published FAA material, and older FAA statements noted that investigations of reported collisions had found birds, other objects, or structural failure rather than a drone impact. That historical position must not be read as a guarantee for the future, and it must not be read as permission to fly near manned aircraft. The risk that matters for a pilot is not only a confirmed collision. It is also a near miss, an evasive manoeuvre, a diverted flight, and a grounded firefighting operation. All of those are real harms even when no metal touches metal.
It depends on the flight type, the outcome, and the jurisdiction. Part 107 reporting to the FAA within 10 days applies where the thresholds in 14 CFR 107.9 are met, and NTSB immediate notification applies where the thresholds in 49 CFR Part 830 are met. Recreational flights under 55 pounds have historically been treated differently under those federal rules, as explained in the reporting section. State and local laws, insurance requirements, and civil liability apply independently, and any injury or significant property damage should be handled through emergency services and local law enforcement where appropriate. If you are unsure, seek guidance promptly rather than assuming no report is needed.
No, not as a spectator. FAA safety material states that if you see wildfire smoke, you should fly away or land immediately unless you are an authorised part of the emergency response, and that the absence of a published temporary flight restriction does not make the flight safe. Firefighting aircraft operate low, in smoke, and on tight orbits, and they may ground operations until an unauthorised drone is confirmed clear. The safe action is to stay away from the fire area entirely.
For ordinary recreational and Part 107 flights in uncontrolled airspace, 400 feet above ground level is the ceiling. Higher flight is possible only under a specific authorisation, waiver, or operating rule that genuinely applies to that flight, and the pilot must be able to point to it. A better camera angle, a taller subject, or a clear sky is not an authorisation. If you cannot name the authorisation that allows the higher altitude, do not climb.
Do not chase it, and do not grab it while propellers are turning. If return to home is active and is working, let it complete or take manual control once you have a safe landing area, but do not keep toggling the mode. If the drone is heading toward people, roads, or restricted airspace, prioritise warning people and moving them clear over recovering the aircraft. After the event, preserve flight logs, inspect the aircraft and battery, and check whether the event meets a reporting threshold before flying again.
Final verdict: fly like the next report could be about you
Drone incidents are not a mystery to be solved by buying better equipment. They are a discipline problem with a known shape: check the airspace, set a safe home point, keep margins for battery and weather, give way to manned aircraft, stay away from people and emergency scenes, and know how to exit an automated mode before you need to. The two NTSB cases in this guide show both sides of that discipline. In Young Harris, a stack of planning and mode errors turned a demonstration flight into a serious injury that manual control and better planning would have prevented. In Orlando, a stack of data entry and margin errors turned a show into collisions over an audience. In both cases, the failure was not a single broken part. It was a chain, and chains can be broken at any link.
That is the honest promise of this guide. It cannot make every flight safe, because weather, equipment, and other airspace users are outside any one pilot's control. It can make the preventable share smaller, and that share is large. Fly within the rules, land early rather than late, and treat every warning, every restriction, and every margin as if it will be needed on this flight. The pilots who do that rarely appear in incident reports, and that absence is the point.
Footer notes
This guide is general information about United States drone safety and reporting, based on FAA guidance, NTSB investigation reports, and published analyses of FAA data cited in this guide. Rules, thresholds, and penalty figures change over time, and state, local, tribal, park, and property rules may add requirements. Always confirm the current FAA position and the rules for your exact location and flight type before flying. No product is recommended in this guide, no product photo is used, and no affiliate link is included, because this is an informational safety guide by design, not a product roundup. The only link in this article text is the byline link to the author page, so no product link in this guide can be stale, misdirected, or mistaken for an endorsement.