A neighbor we will call Dave unboxes a shiny new quadcopter on a Saturday morning. By noon he has it hovering forty feet over the backyard fence, camera live, getting some "cool footage" of the cul-de-sac. By 12:15 the woman next door is on her porch, arms crossed, demanding he land it. By 12:30 someone has Googled "can I shoot down a drone over my house," and somebody else has Googled "is my neighbor's drone legal," and—this being America—both of them are now half-convinced they are the aggrieved party with the law squarely on their side.

Here is the surprising truth: that small toy buzzing over the fence is, in the eyes of federal law, an aircraft. The same agency that certifies Boeing 787s and runs the air traffic control system also regulates Dave's $400 drone. The moment a drone leaves the ground, it enters the National Airspace System, and the National Airspace System belongs—legally speaking—to the Federal Aviation Administration. That single fact explains most of what follows, and it surprises almost everyone the first time they hear it.

This article is a guided tour of drone law in the United States as it stands in 2026. It is written so three very different readers can follow it: a hobbyist who just wants to fly without getting fined, a business owner thinking about aerial photography or package delivery, and a lawyer or judge who needs the statutes, regulations, and cases. We will cover the federal framework first—who can fly, under what rules, with what paperwork—because federal law is the foundation everything else is built on. Then we will turn to the genuinely unsettled and fascinating parts: privacy, trespass, the Fourth Amendment, the tangled question of what states and cities are allowed to regulate, and the strangely common problem of people shooting at drones.

A word of orientation before we take off. Drone law is a layered system, and the layers do not always agree. There is one robust, comprehensive federal regime governing safety and airspace. There is no comprehensive federal regime governing privacy. Into that gap have rushed dozens of state statutes, hundreds of local ordinances, and a grab-bag of old common-law doctrines—trespass, nuisance, invasion of privacy—being stretched to cover a technology their authors never imagined. Keeping those layers straight is most of the value here. Let us start at the bottom: the FAA and the airspace.

Part One: Who Owns the Sky? The FAA and the National Airspace System

To understand drone regulation, you first have to understand a deceptively simple legal proposition: in the United States, the federal government regulates the navigable airspace, and it does so almost completely.

By statute, the FAA is responsible for the safety of civil aviation and for managing "the navigable airspace" of the United States (49 U.S.C. §§ 40103, 44701), and it holds the exclusive power to prescribe air-traffic rules for the flight of aircraft (49 U.S.C. § 40103(b)). An "aircraft" is defined broadly as any device "used or designed for navigation of or flight in the air" (49 U.S.C. § 40102(a)(6)). Courts and the agency have long read that definition to swallow drones whole. A drone—formally an unmanned aircraft system (UAS), sometimes called an unmanned aerial vehicle (UAV)—is an aircraft without a human pilot onboard (a definition Congress traces back to the FAA Modernization and Reform Act of 2012, Pub. L. 112-95 § 331(8)). That is why your camera quadcopter is regulated by the same federal machinery as a crop duster. (Drone technology may also be protected by patents and trade secrets, but that is a different body of law entirely; this article is about the rules for flying the thing, not for owning the invention—for the latter, see our overview of utility patent basics and, for the protective side, building a trade secret protection program from scratch.)

But if the federal government owns the airspace, what does a landowner own? This question is older than drones, and the foundational case is United States v. Causby, 328 U.S. 256 (1946). The Causbys ran a chicken farm near a military airfield; low-flying bombers terrorized the chickens (many of which, the record says, killed themselves flying into walls in panic) and made the farm unusable. The Causbys sued the United States, arguing that the constant low flights amounted to a "taking" of their property. The Supreme Court agreed in part, but in doing so it buried an ancient legal slogan once and for all.

That slogan was cujus est solum, ejus est usque ad coelum—"whoever owns the soil owns up to the heavens." Under that old doctrine, a landowner owned the column of air all the way up. The Causby Court flatly rejected it, calling it a doctrine that "has no place in the modern world." Air travel would be impossible, the Court reasoned, if every flight were a trespass against every parcel it crossed. The navigable airspace is a "public highway." Causby, 328 U.S. at 261. At the same time, the Court held that a landowner still owns "at least as much of the space above the ground as he can occupy or use in connection with the land," and that flights low enough to interfere directly with that use can be a taking or a trespass. Id. at 264.

That two-sided holding—the public owns the high airspace, the landowner controls the low airspace immediately above the surface—is the conceptual fault line that drone disputes keep falling into. A drone at 380 feet is in the FAA's public highway. A drone hovering at fifteen feet outside your bedroom window is in the zone Causby reserved to you. The hard cases live in between, and we will return to them.

For now, hold onto the basic architecture: the FAA regulates the who, what, and where of flight for safety; landowners and states regulate, in a much more contested way, the intrusion a low-flying drone can cause. Almost everything in drone law is a fight about where the boundary between those two regimes sits.

The statutes that built the modern framework

Congress did not seriously address drones until the last fifteen years, and it has done so mostly through a string of FAA reauthorization bills:

  • The FAA Modernization and Reform Act of 2012 (Pub. L. 112-95) first told the FAA to integrate drones into the airspace and created a narrow statutory shelter for traditional model aircraft.
  • The FAA Extension, Safety, and Security Act of 2016 (Pub. L. 114-190) added penalties for interfering with emergency response, including the wildfire-suppression penalty now at 49 U.S.C. § 46320.
  • The FAA Reauthorization Act of 2018 (Pub. L. 115-254) overhauled the recreational rules, ordered up the Remote ID system, addressed counter-drone authority, and gestured at privacy.
  • The FAA Reauthorization Act of 2024 (Pub. L. 118-63) pushed the agency toward routine beyond-visual-line-of-sight operations, drone delivery, and counter-UAS authority for more agencies, setting deadlines the FAA is still working through in 2026.

The agency turned those statutes into the regulations that operators actually live by, principally the small UAS rule, 14 C.F.R. Part 107, the Remote ID rule, 14 C.F.R. Part 89, and the recreational framework now codified at 49 U.S.C. § 44809. We will take each in turn.

Part Two: The Two Doors—Recreational Flight vs. Part 107

Almost every civil drone flight in the United States goes through one of two legal "doors." (Government drones—military, police, public-agency—travel a third path we cover in Part Six.) Picking the right door is the single most important compliance decision a drone operator makes, because the rules behind each door differ sharply.

Door One is recreational flight under the statutory exception in 49 U.S.C. § 44809. It is for hobbyists flying purely for fun.

Door Two is Part 107, the FAA's rule for everyone else flying a small civil drone—which, in practice, means anyone flying for any business, work, or commercial reason.

The dividing line is purpose, not money changing hands, and this trips people up constantly. The test is whether the flight is "strictly for recreational purposes" (§ 44809(a)). If your flight furthers a business in any way, you are not recreational, even if no one pays you a dime. A classic worked example: a real-estate agent we will call "Pat" flies a drone over a listing to get aerial photos of a house she is selling. Pat received no separate fee for flying. Doesn't matter. The flight promotes her real-estate business, so it is not recreational and must comply with Part 107. By contrast, if Pat flies the very same drone over the same field on her day off purely because she enjoys it, that flight goes through Door One. Same pilot, same drone, same location—different legal regime, because the purpose changed. (If Pat is unsure which side of the line she is on, the safe play is always to assume she needs Part 107; the certificate is permanent and lets her fly recreationally too.)

Door One: Recreational flying under 49 U.S.C. § 44809

The recreational exception is generous but not lawless. To fly under it, an operator must satisfy a checklist Congress wrote into the statute (49 U.S.C. § 44809(a)):

  1. The drone is flown strictly for recreational purposes.
  2. The operator follows the safety guidelines of a community-based organization (CBO) recognized by the FAA. (A CBO is essentially a 501(c)(3) model-aviation nonprofit—like the Academy of Model Aeronautics—whose mission is to further model aviation and whose comprehensive safety guidelines the FAA has blessed.)
  3. The drone is kept within visual line of sight of the operator or a visual observer who is in direct communication with the operator.
  4. The drone gives way to and does not interfere with manned aircraft.
  5. In controlled airspace (the airspace around airports), the operator gets prior FAA authorization—in practice, through the LAANC system or pre-approved fixed sites.
  6. In uncontrolled airspace (Class G), the operator stays at or below 400 feet above the ground.
  7. The operator has passed an aeronautical knowledge and safety test—the TRUST test.
  8. The drone is registered with the FAA if it weighs more than 0.55 pounds.

There is also a special accommodation for the dwindling number of giant model aircraft: a recreational drone over 55 pounds may still fly, but only if it complies with a CBO's FAA-approved standards and operates at a fixed site (Pub. L. 115-254 § 349). And in a quirk worth knowing, drones used by colleges, universities, and other educational institutions for instruction or research are treated as recreational, not commercial (Pub. L. 115-254 § 350)—so a university aerospace lab flies through Door One, while a startup doing the same flying flies through Door Two.

Two requirements deserve special attention because they are recent and frequently misunderstood.

The TRUST test. TRUST stands for The Recreational UAS Safety Test. It is the recreational counterpart to the commercial pilot exam, and it is the federal government's idea of low-friction regulation done well. TRUST is free, online, administered by FAA-approved partners, and—crucially—you cannot fail it. The test walks you through the rules and corrects you on the spot if you answer wrong, so everyone who completes it passes. When you finish, you get a completion certificate, which you must carry (digitally or on paper) whenever you fly recreationally and present to law enforcement or the FAA on request. Skipping TRUST is itself a violation; the requirement comes straight from 49 U.S.C. § 44809(g). It takes most people about twenty minutes. There is no good excuse to skip it.

The 400-foot ceiling and visual line of sight. Recreational flyers must stay at or below 400 feet above the ground in uncontrolled airspace and must keep the drone where they can see it with their own eyes (no binoculars, no flying behind a building, no relying solely on the camera feed). These two rules exist for the same reason: to keep small drones out of the path of the helicopters, crop dusters, and light aircraft that legitimately operate at low altitude.

A note on the recreational regime's bumpy history. For years the controlling provision was the old "Section 336" model-aircraft carve-out from the 2012 Act, which was famously hands-off. The 2018 Act repealed it (in Section 349) and replaced it with the more demanding § 44809 framework, adding the airspace-authorization and knowledge-test requirements. The change was litigated and survived; the structure described above is the current law.

Door Two: Commercial small-UAS operations under Part 107

If your flight is not strictly recreational, you live under 14 C.F.R. Part 107, the FAA's "small unmanned aircraft systems" rule (the regulations run from § 107.1 through § 107.205). Part 107 governs civil drones weighing less than 55 pounds flown for non-recreational purposes. It is the workhorse of the commercial drone world: real-estate photography, roof inspections, wedding videography, agricultural mapping, infrastructure surveys, utility and pipeline monitoring, film production, and countless small businesses all fly under it.

Part 107 has two halves: a pilot certification requirement and a set of operational limitations.

The Remote Pilot Certificate. To fly under Part 107, the person at the controls must hold a Remote Pilot Certificate—sometimes called a "Part 107 license"—or be directly supervised by someone who holds one and who can immediately take the controls (14 C.F.R. § 107.12). (Helpers who never touch the sticks, such as visual observers, need no certificate; their duties are spelled out in § 107.33.) To earn the certificate you must (14 C.F.R. §§ 107.61, 107.65):

  • be at least 16 years old;
  • be able to read, speak, write, and understand English;
  • be in a physical and mental condition to operate safely; and
  • pass an aeronautical knowledge test at an FAA-approved testing center (covering airspace, weather, loading, emergency procedures, and the regulations themselves), with a recurrent online training requirement to keep the certificate current.

There is also a TSA security background check, and the application runs through the FAA's online system (Form 8710-13). Unlike TRUST, the Part 107 knowledge exam is a real test that people fail; most applicants study for it. The certificate holder—the remote pilot in command—bears legal responsibility for the flight: preflight inspection, compliance with the rules, and producing the certificate and the drone for FAA inspection on request (14 C.F.R. §§ 107.7, 107.15). A certificate can be suspended or revoked for drug or alcohol violations or for refusing a test (14 C.F.R. §§ 107.57, 107.59), and lying on a waiver or certificate application is itself a violation (§ 107.5).

Operational limitations. A Part 107 flight must, by default, satisfy a list of operating rules. Among the most important:

  • The drone weighs less than 55 pounds, including payload (14 C.F.R. § 107.3).
  • Flight stays within visual line of sight of the remote pilot or a visual observer (14 C.F.R. § 107.31).
  • The drone flies no higher than 400 feet above ground level—or, if inspecting a tall structure, within 400 feet of that structure (14 C.F.R. § 107.51).
  • Maximum groundspeed of 100 mph (87 knots) (14 C.F.R. § 107.51).
  • Operations stay in Class G (uncontrolled) airspace unless air traffic control authorizes flight in Class B, C, D, or E controlled airspace (14 C.F.R. § 107.41).
  • The drone yields the right of way to all manned aircraft (14 C.F.R. § 107.37).
  • No carrying of hazardous materials (14 C.F.R. § 107.36).

Two of those default limits—the prohibition on flying over people and the prohibition on flying at night—used to require a special waiver. They no longer always do. In a major 2021 rulemaking (the Operations Over People and at Night final rule, 86 Fed. Reg. 4314 (Jan. 15, 2021)), the FAA amended Part 107 to permit routine night operations (provided the pilot completes updated training and the drone carries anti-collision lighting visible for three statute miles with an adequate flash rate) and routine flight over people, sorted into four risk-based categories keyed to how much harm the drone could do on impact:

  • Category 1: under 0.55 pounds with no exposed rotating parts that could lacerate skin—the lightest touch.
  • Category 2: no impact injury exceeding what 11 foot-pounds of kinetic energy would cause, no skin-lacerating parts, no safety defects.
  • Category 3: a higher 25 foot-pounds threshold, with the same no-laceration and no-defect conditions and operating constraints.
  • Category 4: heavier drones holding an airworthiness certificate under Part 21 and operated within their approved limits.

The same rule even allows flight over moving vehicles under defined conditions. This was a genuine liberalization, and it is why you now see drones legally filming nighttime fireworks and crowded events that would once have required individual waivers.

Waivers: bending Part 107 when you can show it is safe

Part 107 is not a straitjacket. An operator who needs to deviate from a specific operational rule can apply for a Certificate of Waiver under 14 C.F.R. § 107.205. The standard is straightforward in concept: the FAA grants the waiver if the applicant shows the proposed operation can be conducted safely. Waivable rules include visual-line-of-sight (§ 107.31), daylight operation (§ 107.29), use of a visual observer (§ 107.33), operating multiple drones at once (§ 107.35), yielding the right of way (§ 107.37(a)), and operating in certain airspace (§ 107.41), among others. The single most sought-after—and historically hardest to get—waiver is for beyond visual line of sight (BVLOS) operations, which we will come back to, because BVLOS is the frontier where the future of commercial drones is being decided. (Note one express limit: the FAA will not grant a line-of-sight waiver to carry someone else's property for compensation or hire—delivery is its own regulatory animal, discussed below.)

Part Three: Registration and the Remote ID "Digital License Plate"

Two pieces of federal infrastructure sit underneath both doors: registration and Remote ID.

Registration

Most drones must be registered with the FAA. The threshold is weight: any drone weighing more than 0.55 pounds (250 grams) up to 55 pounds must be registered, whether flown recreationally or commercially. (That 250-gram line is why so many consumer drones are deliberately engineered to weigh exactly 249 grams—it lets casual buyers fly without registering, though they still need TRUST and must follow the recreational rules.) Registration is done online through the FAA's DroneZone portal, costs a few dollars, lasts three years, and yields a registration number that must be marked on the exterior of the aircraft. Recreational flyers can register all their drones under a single number; Part 107 operators register each aircraft individually.

Registration is not a mere formality. Congress made flying an unregistered drone that requires registration a potential criminal offense carrying up to three years' imprisonment and substantial fines (49 U.S.C. § 46306). The FAA's original registration rule for hobbyists was briefly struck down by a federal appeals court in Taylor v. Huerta, 856 F.3d 1089 (D.C. Cir. 2017), on the theory that the old Section 336 barred new rules on model aircraft—but Congress promptly restored the registration requirement by statute in the National Defense Authorization Act for Fiscal Year 2018, and it stands today. It is a small but instructive episode: when a court closed one door on the FAA, Congress opened another.

Remote ID: the digital license plate

The newest and arguably most consequential layer is Remote ID, established by the FAA's 2021 final rule and codified at 14 C.F.R. Part 89 (86 Fed. Reg. 4390 (Jan. 15, 2021)). Remote ID is exactly what it sounds like: a system that lets a drone broadcast its identity and location while it flies, so that anyone with the right receiver—especially law enforcement and security agencies—can answer the question "what is that, and who is flying it?" The FAA calls it a "digital license plate" for drones, and the analogy is apt.

A drone subject to Remote ID must broadcast, in real time, a set of data including its serial number or a randomly generated session ID, its latitude/longitude/altitude, the location of its control station (i.e., roughly where the pilot is standing), its velocity, a time stamp, and an emergency status. Crucially, the broadcast includes the pilot's approximate location, not just the drone's—a feature designed to let police walk up to an operator flying somewhere they should not be.

There are three ways to comply (14 C.F.R. Part 89):

  1. Fly a Standard Remote ID drone with the broadcast capability built in by the manufacturer.
  2. Attach a Remote ID broadcast module to an older drone (and keep it within visual line of sight; a module broadcasts its own serial number, the drone's position and velocity, the take-off location, and a timestamp).
  3. Fly at an FAA-Recognized Identification Area (FRIA)—a pre-approved geographic zone (typically a club field or an educational institution's site) where drones without Remote ID may operate.

After a phased rollout—and a brief enforcement-discretion grace period in 2024 while the FRIA application backlog cleared—Remote ID is now in effect for operators. Most drones that require registration must broadcast Remote ID or fly only at a FRIA. The rule survived a constitutional challenge in RaceDayQuads, LLC v. FAA, 78 F.4th 519 (D.C. Cir. 2023), where a hobbyist-led group argued that requiring drones to broadcast their location amounted to constant warrantless surveillance in violation of the Fourth Amendment. The D.C. Circuit disagreed, reasoning (in essence) that a drone voluntarily flown in public navigable airspace, broadcasting only while aloft, does not carry the kind of reasonable expectation of privacy the Fourth Amendment protects. Remote ID, the court held, is a permissible safety-and-security measure. For operators, the practical upshot is simple: if your drone needs to be registered, it almost certainly needs Remote ID too.

Part Four: Airspace, LAANC, and the Long Road to BVLOS and Delivery

Reading the airspace

Both recreational and commercial flyers must understand airspace classes, because the rules change depending on where in the sky you are. In rough terms:

  • Class G is uncontrolled airspace near the ground, away from busy airports. Most drone flying happens here, and it generally needs no air-traffic permission (subject to the 400-foot ceiling).
  • Class B, C, D, and E are controlled airspace—mostly the inverted-wedding-cake funnels of airspace around airports of varying size. Roughly speaking, Class B wraps the busiest airports up to 10,000 feet, Class C up to 4,000 feet, Class D up to 2,500 feet, and Class E fills in much of the rest from 1,200 feet up to 18,000 feet. Flying a drone in any of these requires prior FAA authorization.

The good news is that getting authorization in controlled airspace no longer means a phone call and a long wait. The FAA built LAANC—the Low Altitude Authorization and Notification Capability—a system that grants near-instant, automated authorization to fly in controlled airspace up to pre-set altitude ceilings depicted on UAS Facility Maps. Through an approved app, a pilot requests permission to fly in, say, the Class D airspace under an approach corridor, and if the request is within the published ceiling for that grid square, approval comes back in seconds. LAANC is one of the quieter success stories of drone regulation—a piece of software that turned a bureaucratic bottleneck into a tap on a phone. (Recreational flyers cannot call the tower for case-by-case clearance the way manned pilots can; they use LAANC or pre-approved fixed sites instead.)

BVLOS: the frontier

The single biggest constraint on what drones can do commercially is the visual line of sight requirement. As long as a human has to keep eyes on the aircraft, a drone cannot inspect a 50-mile pipeline, survey a sprawling rail network, or deliver a package across town in one continuous flight. The future of the industry—package delivery, infrastructure inspection at scale, agricultural coverage, medical-supply runs—runs through beyond visual line of sight (BVLOS) operations, and it depends in turn on building a low-altitude unmanned traffic management (UTM) system so that swarms of unseen drones do not run into each other or into manned aircraft (a system Congress directed the FAA to develop, Pub. L. 115-254 § 376).

For years, BVLOS was available only through hard-won, operation-specific waivers and exemptions—the FAA's January 2021 approval of American Robotics to run fully automated, no-observer flights in low-traffic areas below 400 feet was a notable early milestone. That regime is now changing. The FAA convened a BVLOS Aviation Rulemaking Committee, Congress in the 2024 Reauthorization Act ordered the agency to issue a BVLOS rule on a deadline, and in 2025 the FAA published a long-awaited proposed rule to create a new Part 108 governing routine BVLOS flight. As of 2026 the rule is still in the rulemaking pipeline—proposed, comment-laden, and not yet final—so any operator who needs BVLOS today still relies on waivers and exemptions, and any reader should treat the precise contours of Part 108 as a moving target until the final rule lands. The direction of travel, however, is unmistakable: routine BVLOS is coming, and it will unlock the operations that the rest of drone law has been bracing for.

Drone delivery

Package delivery sits at the intersection of every hard problem in drone law: BVLOS, flight over people, air-carrier certification, and community acceptance. Carrying property "for compensation or hire" is air-carrier activity, so a delivery operator needs more than a Part 107 certificate—it needs an air carrier certificate under 14 C.F.R. Part 119/135, plus airworthiness approval for the aircraft itself (the FAA has proposed certifying delivery drones as a "special class" under 14 C.F.R. § 21.17(b), see 85 Fed. Reg. 5905 (Jan. 31, 2020)) and BVLOS authority. A handful of operators have cleared those hurdles and run live delivery services in select communities. But the legal scaffolding for nationwide, routine delivery is still being poured, and it depends heavily on the BVLOS rulemaking. For now, drone delivery is real but local, lawful but heavily conditioned.

Part Five: The Places You Simply Cannot Fly—Security-Sensitive Airspace

Before we leave the safety-and-airspace half of the story, one more rule deserves its own spotlight, because it catches honest hobbyists more often than any other: there are large swaths of sky where no one—recreational or commercial—may fly a drone without special, hard-to-get permission, no matter how careful they are.

Congress and the FAA have walled off security-sensitive airspace through a combination of statute and Notices to Air Missions (NOTAMs):

  • Stadiums and major sporting events. Standing NOTAM restrictions bar drone flight within three nautical miles of large stadiums from an hour before to an hour after a game (the long-running stadium NOTAM, 4/3621). Fly your drone over a packed NFL stadium and you have committed a federal violation before the kickoff.
  • Critical infrastructure. The 2018 Act directed the FAA to restrict drones near sensitive facilities, and the agency has used 49 U.S.C. § 40103(b)(3) to impose flight restrictions over many military bases, Department of Energy nuclear sites, certain prisons, Coast Guard installations, and national landmarks such as the Statue of Liberty and Mount Rushmore. Railroad and energy facilities have drawn particular attention (Pub. L. 115-254 § 369).
  • Washington, D.C. The capital sits inside the most restrictive airspace in the country—the Flight Restricted Zone within the larger Special Flight Rules Area—where recreational drone flight is essentially prohibited within a 15-mile radius of Reagan National Airport.
  • Temporary flight restrictions and wildfires. TFRs pop up around presidential movements, disasters, and—critically—wildfires, where an intruding drone can ground the firefighting aircraft that are trying to save lives and homes.

There is also a softer constraint that effectively functions as a ban. By advisory circular (FAA AC 91-36), the FAA requests that pilots stay at least 2,000 feet above national parks, wildlife refuges, and other noise-sensitive areas. Because that altitude is far above the 400-foot ceiling a drone may legally use, the practical result is that a great deal of America's most photogenic wilderness is off-limits to drones—and many of those parks have layered their own ground-level launch-and-land bans on top. The lesson for the would-be aerial nature photographer is humbling: the most beautiful places are frequently the ones you may not fly.

Part Six: The Privacy Problem—or, Where Federal Law Goes Quiet

Here is where the story gets interesting, and where most of the public's anxiety actually lives. Almost everything we have discussed so far is about safety: keeping drones from hitting airplanes, buildings, and people. But when Dave hovers his camera over the fence, the neighbor's worry is not aviation safety. It is privacy. And on privacy, the comprehensive federal regime simply... isn't there.

There is no comprehensive federal drone-privacy statute. The FAA has said repeatedly that its mandate is aviation safety, not privacy, and it has largely declined to write privacy rules into Part 107. Congress, in the 2018 Act, did gesture at the issue. It directed that drones be operated in a way that "respects and protects" personal privacy consistent with federal and state law (Pub. L. 115-254 § 357); it provided that violating a drone operator's own stated privacy policy could be treated as an unfair or deceptive practice under Section 5(a) of the FTC Act, 15 U.S.C. § 45(a) (Pub. L. 115-254 § 375); it required businesses operating drones to maintain a written privacy policy on the collection, use, retention, and deletion of the data they gather (Pub. L. 115-254 § 378); and it told the Department of Transportation to publish data about government and commercial drones that collect personally identifiable information, including facial recognition (Pub. L. 115-254 § 379). That FTC hook is the same consumer-protection statute that polices misleading marketing generally, a subject we cover in our advertising FAQs for small business. But those are thin reeds. There is no federal statute that says, in so many words, "you may not use a drone to spy on your neighbor."

The privacy advocacy group EPIC tried to force the FAA's hand, petitioning the agency to write privacy rules and then suing when it declined; the D.C. Circuit dismissed the challenge in EPIC v. FAA, 821 F.3d 39 (D.C. Cir. 2016), confirming that the FAA was within its rights not to regulate drone privacy in that rulemaking. The result is a deliberate federal vacuum—and into a vacuum, other law rushes.

The state and local patchwork

In the absence of a federal privacy rule, the states have legislated, and the result is a true patchwork. By 2026 a large majority of states have enacted some form of drone-specific law, and they are all over the map:

  • Many states have created or sharpened criminal offenses for using a drone to conduct surveillance of a person or private property, or to capture images where the subject has a reasonable expectation of privacy. Several explicitly criminalize aerial "voyeurism" or peeping.
  • Some states create a private right of action allowing a person surveilled by a drone to sue for damages and injunctions.
  • Many states restrict law enforcement's use of drones—often requiring a warrant before police may use a drone for surveillance, subject to emergency exceptions.
  • Others address narrow but vivid concerns: flying over prisons or critical infrastructure (power plants, refineries), interfering with hunting, or harassing wildlife.

Florida is a useful concrete example, because it has legislated on both ends of the problem. Its Unmanned Aircraft Systems Act (Fla. Stat. § 330.41) regulates operations and, notably, limits what local governments may do—reserving most drone regulation to the state to avoid a maze of conflicting city ordinances. Its Freedom from Unwanted Surveillance Act (Fla. Stat. § 934.50) goes the other way, prohibiting the use of a drone to record images of people or private property where there is a reasonable expectation of privacy, restricting police use of drones for evidence-gathering absent a warrant or recognized exception, and—critically—creating a private civil cause of action for those who are surveilled. A Floridian whose backyard is photographed by a neighbor's drone has a statute to point to; a resident of a state without one is left to the common law.

Local governments elsewhere have layered hundreds of ordinances on top—no-fly zones over city parks, takeoff-and-landing bans, restrictions near stadiums and schools. The practical reality for an operator is that the federal rules tell you whether you may fly, but state and local law may tell you whether you may photograph, land, take off, or linger in a particular place. Both layers can apply at once.

The preemption puzzle

This raises the question that lawyers and judges fight about most: how much of this state and local law is preempted by federal aviation law?

The FAA's own position, stated in the preamble to the Part 107 rule, is nuanced. Air safety and airspace regulation are core federal functions and are broadly preempted—a city cannot, for example, set its own altitude limits or licensing requirements for drones in the navigable airspace (81 Fed. Reg. 42064, 42119 (June 28, 2016)). But the agency has acknowledged that traditional areas of state concern—privacy, trespass, nuisance, voyeurism, and law enforcement—are generally not preempted and are properly left to state and local law under the states' police powers, subject to a case-by-case analysis rather than a single rule of general applicability. Congress, in the 2018 Act, ordered the Comptroller General to study exactly where these lines fall (Pub. L. 115-254 § 373), a tacit admission that the boundary is genuinely uncertain.

The leading case showing how messy this gets is Singer v. City of Newton, 284 F. Supp. 3d 125 (D. Mass. 2017). Newton, Massachusetts passed a local drone ordinance that, among other things, banned flying a drone below 400 feet over private property without the owner's consent and required all drones to be registered with the city. A resident challenged it. The federal court struck down several provisions as conflict-preempted: by banning flight below 400 feet without consent, Newton had effectively regulated the entire navigable airspace a drone could occupy, intruding on the FAA's domain; and the city's separate registration requirement collided with the federal registration scheme. Singer is a cautionary tale for cities: a local ordinance aimed at privacy can be drafted so broadly that it crosses into airspace regulation and gets struck down. The lesson for legislators is to regulate the harm (surveillance, trespass, harassment) rather than the flight (altitude, airspace)—which is precisely why Florida's surveillance statute, framed around the recording of private images rather than the act of flying, stands on firmer ground.

So the working synthesis a careful operator or counsel should carry is this: The FAA controls the airspace and safety; states and cities may regulate privacy, trespass, and similar harms—but if they try to regulate the airspace itself, they risk preemption. Where exactly the line sits in any given case remains, candidly, unsettled.

Part Seven: The Fourth Amendment and Government Drones

Private drones raise tort and statutory privacy questions. Government drones raise a constitutional one: when police fly a drone over your property, is that a "search" requiring a warrant under the Fourth Amendment?

Government drones occupy a distinct lane in the regulatory scheme. A public agency can certify its pilots like any commercial operator, or it can obtain a certificate of authorization and operate as a "public aircraft operator" that self-certifies its own pilots and aircraft (49 U.S.C. §§ 40102(a), 40125). Either way, the agency still flies within the safety rules—but the constitutional overlay is what makes police drones different from a hobbyist's quadcopter.

The honest answer on the constitutional question is that the Supreme Court has never decided a drone case, so we reason from the closest analogies—the aerial surveillance trilogy of the 1980s, decided in the era of helicopters and fixed-wing planes.

In California v. Ciraolo, 476 U.S. 207 (1986), police flew a fixed-wing plane at 1,000 feet over a suspect's backyard and spotted marijuana growing behind a tall fence. The Court held this was not a Fourth Amendment search. The reasoning: the plane was in public navigable airspace where any member of the public could lawfully fly, and what an officer can see "with the naked eye" from a public vantage point is not constitutionally protected, even if the homeowner subjectively expected privacy behind his fence. Ciraolo, 476 U.S. at 213–14.

The Court doubled down in Florida v. Riley, 488 U.S. 445 (1989), upholding surveillance from a helicopter hovering at 400 feet over a backyard greenhouse, and in Dow Chemical Co. v. United States, 476 U.S. 227 (1986), upholding aerial photography of an industrial complex. The throughline: observation from public airspace, with ordinary or commercially available equipment, is generally not a search.

But drones strain those precedents in two ways the helicopter cases never had to confront. First, drones can fly lower, longer, and far more cheaply than any manned aircraft, enabling persistent surveillance that Ciraolo and Riley never imagined—and a separate line of cases, exemplified by United States v. Jones, 565 U.S. 400 (2012) (GPS tracking), and Carpenter v. United States, 585 U.S. 296 (2018) (cell-site location data), holds that prolonged, comprehensive surveillance can be a search even when each individual observation would not be. Whether a drone hovering over a backyard for hours crosses that line is a question the Supreme Court has not answered. Second, Riley itself emphasized that the helicopter was operating at an altitude where such aircraft routinely and lawfully fly; a drone hovering at fifteen feet outside a window is not operating where aircraft routinely fly, which weakens the analogy considerably.

The result is a live and shifting area of constitutional law. Some state courts and legislatures have gotten ahead of the Supreme Court, holding (or simply enacting, as Florida did) that police generally need a warrant to use a drone to surveil a person or a home, subject to exigent-circumstance exceptions. For a government drone program, the safest assumption in 2026 is that targeted aerial surveillance of a home or its curtilage may well require a warrant, and that the older aerial-surveillance cases are an uncertain shield. (For the closely related questions raised when anyone points a camera at anyone from the ground, see our companion article on cell-phone camera privacy; and for the facial-recognition concerns that drone cameras increasingly raise, see biometric data privacy laws.)

Part Eight: Trespass, Nuisance, and the Recurring Temptation to Shoot

Set the Constitution aside and return to Dave and his neighbor. What are their rights against each other under ordinary tort law?

Trespass to land. Recall Causby: a landowner owns the airspace immediately above the surface that he can use in connection with his land. A drone hovering at fifteen feet outside a bedroom window is plausibly trespassing into that protected low airspace; a drone transiting at 380 feet almost certainly is not, because that is the FAA's public highway. The hard cases are in the middle, and there is no national consensus on exactly where a trespass begins. A few states have legislated a specific altitude (some have used numbers in the low hundreds of feet over private property), but most leave it to Causby's fuzzy "immediate reaches" standard. The key practical point: trespass turns on intrusion into the usable low airspace, not on whether the drone touched the ground.

Private nuisance. Even a drone that never enters your airspace can be a nuisance if it substantially and unreasonably interferes with your use and enjoyment of your land—think a neighbor's drone that buzzes the patio every evening, scaring the dog and ruining dinner. Nuisance is flexible and fact-specific, and it does not depend on a precise altitude line.

Invasion of privacy. The common-law tort of intrusion upon seclusion lets a person sue someone who intentionally intrudes on their private affairs in a manner highly offensive to a reasonable person. A drone peering through a bedroom window or over a tall privacy fence into a backyard is a textbook fit. Many of the state drone-surveillance statutes described above essentially codify and sharpen this tort for the aerial age. And once the footage is captured and published—on social media, say—a fresh set of problems arises: defamation, the public-disclosure-of-private-facts tort, and the platform rules we walk through in social media law basics. If the footage features an identifiable person and is used commercially, the right of publicity can be implicated too.

And then there is the shotgun. No discussion of drone law is complete without the recurring American impulse to solve the problem with a firearm. The instructive cautionary tale is Boggs v. Merideth, 2017 WL 1287549 (W.D. Ky. Mar. 21, 2017)—the so-called "Drone Slayer" case. William Merideth shot a neighbor's drone out of the sky over his Kentucky property, claiming it was spying on his sunbathing daughter. State criminal charges were dismissed locally, and Merideth became a folk hero in some quarters. But the drone's owner sued in federal court, and the case surfaced the uncomfortable federal-law reality: a drone is an aircraft, and shooting at an aircraft is a federal crime. Under 18 U.S.C. § 32, it is a felony—punishable by up to twenty years—to willfully damage, destroy, or disable an aircraft, and the FAA's longstanding position is that this includes drones. The federal court in Boggs ultimately dismissed the case on jurisdictional grounds (finding no federal question or sufficient amount in controversy to keep it in federal court), so it did not produce a definitive ruling that shooting a drone is always a federal felony. But no one should read Boggs as a green light. The legally safe response to a drone over your yard is to document it, call the police, note the operator's location (Remote ID can help), and pursue trespass, nuisance, or privacy remedies—not to open fire. If you want to assert your rights against an operator before suing, a firmly worded letter is often the right first step; our guide to writing a demand letter walks through how to do it without crossing legal lines of your own. Shooting at a drone can expose you to federal felony liability, state criminal charges for discharging a firearm, and civil liability for the destroyed aircraft and any damage the falling debris causes. The cure is far worse than the buzz.

Part Nine: Counter-UAS—Who Is Allowed to Take a Drone Down?

If private citizens generally cannot shoot down drones, who can? This is the counter-UAS (C-UAS) problem, and it is genuinely thorny because the very tools used to defeat a hostile drone—jamming its control link, spoofing its GPS, hacking its communications, or physically disabling it—run headlong into a thicket of other federal laws. Jamming radio signals violates the Communications Act; intercepting the drone's control communications can violate the Wiretap Act and the Computer Fraud and Abuse Act, 18 U.S.C. § 1030 (the same statute that governs unauthorized access to computer systems generally, which we examine in our piece on data scraping after hiQ v. LinkedIn); and damaging the drone implicates the aircraft-sabotage statute we just discussed.

For that reason, counter-drone authority is tightly held by the federal government. The 2018 Act granted the Departments of Homeland Security and Justice limited, conditioned authority to detect, identify, monitor, track, intercept the control communications of, disrupt, seize, and—if necessary, using reasonable force—damage or destroy drones that pose a credible threat to certain covered facilities and assets, notwithstanding the communications, wiretap, and computer-crime laws that would otherwise forbid it (Pub. L. 115-254 § 1602). That same provision conditions the authority on respecting the First and Fourth Amendments. The Departments of Defense and Energy have parallel authorities for their installations. State and local police, airports, stadiums, and private security firms have repeatedly asked Congress to extend C-UAS authority to them, citing threats to crowds and critical infrastructure; the 2024 Reauthorization Act and subsequent proposals have inched in that direction, but as of 2026 broad state/local C-UAS authority remains contested and limited, and the underlying federal authorities have required periodic reauthorization. The bottom line for now: defeating a drone with electronic or kinetic countermeasures is lawful only for a narrow set of federal actors under specific conditions—it is not a self-help remedy for a stadium operator, a prison, or an annoyed homeowner.

Part Ten: The Product-Safety Gap

Here is a fact that surprises almost everyone, including lawyers: the Consumer Product Safety Commission has essentially no authority over drones. The CPSC, which can recall a dangerous toaster or a tip-prone dresser, is barred from regulating "aircraft" by a statutory carve-out in its own organic act (15 U.S.C. § 2052(a)(5)(F)). Because a drone is an aircraft, it falls into that exclusion. The CPSC can and does regulate individual components—the lithium-ion batteries and chargers, for instance—but it cannot set safety standards for the drone as a whole and cannot order a recall when a popular model turns out to have a defect that sends it plummeting.

That leaves an unusual regulatory hole. The FAA polices how drones are flown but has historically focused on operational safety rather than product design (the airworthiness-certification track for delivery and Category 4 drones is the partial exception). The CPSC, which exists precisely to police product design, is shut out by statute. The result is that consumer drones occupy a niche where neither of the two agencies you would expect to guarantee they are safe to own has full authority to do so. For now, that gap is filled mostly by manufacturers' own standards, voluntary industry consensus standards, and ordinary state product-liability law—which means that when a drone's defect injures someone, the injured party's most direct remedy may be a tort suit against the maker, not a federal recall.

Part Eleven: Enforcement and Penalties

The FAA's enforcement philosophy is, by design, more carrot than stick for honest mistakes. Under its Compliance Program, the agency prefers to correct unintentional, low-risk violations through education, counseling, and on-the-spot fixes rather than fines—if the operator is qualified, cooperative, and the conduct was not reckless. Compliance Actions are reserved for deviations that flow from simple mistakes, flawed procedures, a lack of understanding, or diminished skill. The compliance approach evaporates the moment the FAA sees an intentional deviation, reckless or criminal conduct, or a significant safety risk. At that point the penalties get real.

Civil penalties. The baseline civil penalty for violating FAA regulations can reach tens of thousands of dollars per violation, with each day of a continuing violation counted separately (49 U.S.C. § 46301; the maximum amounts are adjusted for inflation, see 14 C.F.R. § 383.2). Specialized provisions hit specific harms: knowingly or recklessly interfering with wildfire suppression, law enforcement, or emergency response draws its own penalty of up to $20,000 (49 U.S.C. § 46320), and operating a drone equipped with a dangerous weapon (as defined in 18 U.S.C. § 930(g)(2)) without authorization carries penalties up to $25,000 per violation (Pub. L. 115-254 § 363). Catch-all "careless or reckless" operation—operating a drone "in a careless or reckless manner so as to endanger the life or property of another" (14 C.F.R. § 107.23)—is the provision the FAA most often reaches for against bad commercial actors, and fraudulent statements in applications (§ 107.5) and drug or alcohol violations (§§ 107.57, 107.59) can cost an operator the certificate altogether.

Criminal penalties. The serious offenses are criminal. To name several:

  • Up to 3 years for operating an unregistered drone that requires registration (49 U.S.C. § 46306).
  • Up to 1 year for violating national defense airspace (49 U.S.C. § 46307).
  • Up to 5 years for interfering with air navigation (49 U.S.C. § 46308).
  • Up to 5 years for unlawfully transporting hazardous materials by aircraft (49 U.S.C. § 46312).
  • Up to 3 years for operating in air transportation without an airman's certificate where one is required (49 U.S.C. § 46317).
  • Up to 1 year for knowingly or recklessly interfering with a manned aircraft's operation (18 U.S.C. § 39B).
  • Up to 2 years for knowingly or recklessly interfering with wildfire, law-enforcement, or emergency-response efforts (18 U.S.C. § 40A).
  • Up to 10 years for knowingly and willfully flying a drone in or above restricted buildings or grounds while using a dangerous weapon, or where serious bodily injury results (18 U.S.C. § 1752(a)(5), (b)).
  • And, as noted, up to 20 years for damaging or destroying an aircraft—including a drone—under 18 U.S.C. § 32.

The practical takeaway: ordinary mistakes by cooperative flyers usually end in a conversation, not a courtroom. Reckless flying near airports, wildfires, stadiums, or restricted facilities can end careers and liberty.

Part Twelve: A Quick Look Beyond U.S. Borders

Because drones cross borders as freely as ideas do, it helps to know that the United States is not alone, and not even first, in regulating them. Most developed nations regulate drones through their civil aviation authorities, with broadly similar building blocks—registration, pilot competency, weight categories, visual-line-of-sight defaults, no-fly zones around airports, and heightened rules for camera-equipped drones.

The European Union has, in many respects, moved further than the United States toward a harmonized regime. Where the EU once left small civilian drones to a confusing thicket of national rules, the European Union Aviation Safety Agency (EASA) now administers a unified, risk-based framework that sorts operations into "Open," "Specific," and "Certified" categories by risk rather than by recreational-versus-commercial purpose—a structurally different and, some argue, more rational cut than the American two-door system. The United Kingdom (through the CAA), Canada (through Transport Canada), Australia (through CASA), Japan, and many others maintain comparable but distinct regimes; meanwhile some governments impose far stricter controls, including outright bans in sensitive zones or for certain users. The comparative lesson is that the problems are universal—safety, security, privacy, and integration into crowded airspace—but the solutions diverge, which matters enormously for any operator or manufacturer working across borders. (Readers interested in how cross-border regulation of an emerging technology fragments into competing national regimes may enjoy our companion survey on the regulation of cryptocurrency around the world, which tells a strikingly parallel story.)

Key Takeaways

If you remember nothing else, remember these:

  1. A drone is an aircraft. The FAA regulates it from the moment it leaves the ground, no matter how small or cheap.
  2. Pick the right door. Recreational flying goes through 49 U.S.C. § 44809 (with the free TRUST test); any work, business, or commercial flight goes through Part 107 (with a real Remote Pilot Certificate). Purpose, not payment, decides.
  3. Register and broadcast. Drones over 250 grams must be registered, and most drones that require registration must now broadcast Remote ID.
  4. Mind the airspace and the 400-foot ceiling. Use LAANC for instant authorization near airports; stay within visual line of sight unless you have a waiver; and steer clear of stadiums, restricted facilities, wildfires, and Washington, D.C.
  5. Federal law governs safety; state and local law govern privacy and trespass. There is no comprehensive federal drone-privacy statute—just a patchwork (Florida's surveillance statute is a leading model). Cities that try to regulate the airspace (not just the harm) risk preemption, as Singer v. Newton shows.
  6. The Fourth Amendment is unsettled for government drones; the old aerial-surveillance cases (Ciraolo, Riley) are an uncertain shield against persistent drone surveillance, and a growing number of states now require a warrant by statute.
  7. Do not shoot the drone. It is an aircraft; shooting it can be a federal felony under 18 U.S.C. § 32. Document, report, and pursue trespass/nuisance/privacy remedies instead.
  8. Mind the product-safety gap. The CPSC cannot recall a defective drone; injured parties typically look to state product-liability law.
  9. BVLOS and delivery are the frontier. The proposed Part 108 BVLOS rule is still being finalized in 2026—treat the cutting edge as a moving target.

Frequently Asked Questions

Do I need a license to fly a drone? It depends on why you are flying. For purely recreational flying, you do not need a pilot certificate, but you must pass TRUST (the free, can't-fail online recreational safety test) and follow the 49 U.S.C. § 44809 rules. For any business, work, or commercial flight, you need a Remote Pilot Certificate under Part 107, which requires passing a real aeronautical knowledge exam and clearing a TSA background check.

My drone weighs 249 grams—am I exempt from everything? No. The 250-gram (0.55 lb) line exempts you only from registration (and, for purely recreational flyers, from some Remote ID obligations). You still must follow the operating rules—visual line of sight, the 400-foot ceiling, airspace restrictions—and recreational flyers still need TRUST. If you fly that same 249-gram drone for any commercial purpose, you are under Part 107 regardless of weight, and a registered Part 107 drone needs Remote ID no matter how light it is.

Can I fly over my neighbor's house? Can they stop me? Federally, transiting at a normal altitude in the navigable airspace is generally permitted. But hovering low over a neighbor's yard, or pointing a camera into their windows, can expose you to state-law claims for trespass (intruding into the usable low airspace under Causby), nuisance, or invasion of privacy, plus possible violations of state drone-surveillance statutes like Florida's Freedom from Unwanted Surveillance Act. "The FAA lets me fly here" is not a complete answer to "you were spying on me."

Someone is flying a drone over my backyard. Can I shoot it down or jam it? No. A drone is an aircraft, and willfully damaging or destroying an aircraft is a federal felony under 18 U.S.C. § 32, with state firearm and property-damage liability on top. Jamming its signal violates separate federal communications and computer-crime laws, and lawful counter-UAS authority is reserved to a narrow set of federal agencies. Document the drone, note the operator's location (Remote ID can help), call the police, and pursue civil remedies.

Is there a federal law protecting me from drone surveillance? Not a comprehensive one. The FAA regulates aviation safety, not privacy, and has declined to write general drone-privacy rules (a decision upheld in EPIC v. FAA). Your protection comes from a patchwork of state surveillance statutes, common-law privacy and trespass torts, the FTC Act's deceptive-practices hook if an operator violates its own posted privacy policy, and—against the government—the Fourth Amendment, whose application to drones remains unsettled.

Do police need a warrant to use a drone to watch my property? Possibly. The Supreme Court's older aerial-surveillance cases (California v. Ciraolo; Florida v. Riley) suggest observation from public airspace is often not a "search." But drones enable cheaper, lower, more persistent surveillance, and the Jones/Carpenter line of cases treats prolonged, comprehensive monitoring as a search. Many states now require a warrant by statute for police drone surveillance. The safest assumption is that targeted surveillance of a home may require a warrant.

Can I get paid to fly a drone for weddings, real estate, or inspections? Yes—but only under Part 107, with a Remote Pilot Certificate, a registered aircraft, Remote ID, and compliance with the operating rules (or appropriate waivers). Flying for any business purpose without a Part 107 certificate is a violation, even if no one hands you cash for the flight itself.

What about flying at night or over crowds? Both are now possible under Part 107 without a special waiver in many cases. Night operations require updated training and anti-collision lighting visible for three statute miles. Flying over people is allowed under four risk-based categories keyed to the drone's potential to cause injury on impact (lighter drones, fewer restrictions). Heavier drones and certain operations may still need a waiver, and stadiums and large gatherings remain off-limits under standing NOTAMs regardless.

Where can I never fly, no matter what? Security-sensitive airspace is effectively off-limits to civil drones: within three nautical miles of large stadiums during events, over many military bases, nuclear and DOE facilities, certain prisons, national landmarks, active wildfire TFRs, and the heavily restricted airspace around Washington, D.C. The FAA also asks pilots to stay 2,000 feet above national parks and wildlife refuges—above the legal drone ceiling—which functions as a practical ban.

When will routine drone delivery and long-distance flights be legal everywhere? Drone delivery and beyond-visual-line-of-sight (BVLOS) flight are legal today only through specific certifications, waivers, and exemptions. A proposed Part 108 rule to make BVLOS routine has been published and is working through the rulemaking process, but it was not final as of mid-2026. Expect meaningful expansion as that rule is finalized—just don't assume any particular operation is permitted until the rules catch up.

Related Articles

This article is general legal information, not legal advice, and reading it does not create an attorney-client relationship. Drone law is changing quickly—especially on Remote ID, beyond-visual-line-of-sight operations, counter-UAS authority, and state privacy rules—so verify the current rules and consult qualified counsel about your specific situation before you fly.