Federal Rules or Local Control: Who Actually Regulates the Air Over Your House
Every few sessions a bill appears in Congress under a name like the Drone Federalism Act, proposing to bring drone regulation down to the local level. The details differ; the argument never does. Aviation has been regulated nationally since aviation began, but a drone at rooftop height over a back garden does not feel like aviation to the person standing under it, and that gap between the law and the experience is what keeps these bills coming back.
What the local-control bills propose
The common design is a band of airspace immediately above the ground in which state, local and tribal governments may set their own rules. Inside that band a town could say where a drone may launch and land, restrict flights over particular properties or at particular hours, and require permission for commercial work. Above it, federal rules would continue to apply exactly as they do now. Some versions add a right for a property owner to object to routine low flights over their own land, and most preserve the federal authority over aircraft certification, pilot qualification and anything to do with manned traffic.
Supporters make two points that are hard to dismiss. The first is that nobody in a federal office can know which park hosts a school event on a Saturday morning, and local government does that kind of work every day. The second is that nuisance, trespass and privacy have always been local matters, and a camera at window height is closer to those than to air traffic control.
Why the bills stall
Federal preemption. Airspace is a single navigable system, and the courts have long held that a patchwork of local flight rules is precisely what national regulation exists to prevent. An operator flying a pipeline or a delivery route would cross dozens of jurisdictions in an afternoon, and if each one set its own altitude floor, its own permit and its own hours, the flight would be legally impossible to plan even where it was physically trivial.
There is a safety argument too. Altitude limits only work if everyone reads them the same way, and a drone pilot descending to comply with a municipal ceiling may be descending into the volume a helicopter is using. Regulators are consistently unwilling to delegate that geometry.
So the bills tend to pass out of committee with warm words, attract opposition from operators, manufacturers and the aviation agency, and quietly expire. Then the next session begins.
What is actually settled
Rather more than the debate suggests. Where an aircraft may fly, how high, how fast, under what qualification and with what equipment is federal, and no town ordinance changes it. What a drone may point a camera at, whether it may harass a person or livestock, where a vehicle may park to launch, and what happens in a municipal park are matters states and cities already legislate, and many have. That division is workable, and most of the conflict in practice comes from local ordinances drafted as though they were aviation rules, which are the ones that get struck down.
What an operator should do about it
Assume the federal rules govern the flight and local rules govern everything around it. Before working in an unfamiliar jurisdiction, read the municipal code on parks, launch sites and photography as carefully as the airspace chart, because that is where a fine is likely to come from. Keep a stated purpose for each flight, since the local statutes that hold up in court are the ones aimed at conduct rather than at altitude.
And read the next bill for its scope rather than its title. A measure that gives local government authority over launch sites, parks and privacy is likely to become law somewhere. One that sets a local ceiling in the navigable airspace is a press release with a bill number, and it will be back in the following session with a different name.
