Policy

FAA Part 107 and Local Ordinances: A Practical Guide for City Managers

Understanding federal preemption, what cities can legitimately regulate, and how to write drone ordinances that hold up legally and work operationally.

FAA Part 107 and Local Ordinances

When a city council passes a drone ordinance, one of three things usually happens. The ordinance works as intended. It gets challenged and narrowed. Or it gets challenged and struck down entirely. Understanding which outcome you get depends almost entirely on how well your legal team understands the boundary between federal aviation authority and local regulatory power.

This guide is for city managers who need to understand that boundary without getting lost in aviation law. It covers what cities can legitimately regulate, where the gray areas are, and what effective local ordinances actually look like.

What Cities Can Regulate

The list of areas where local authority is legitimate is substantial. Cities tend to underestimate it.

Takeoff and landing on public property. Cities have authority over their own land. A park drone ordinance that restricts launch and landing is regulating property use, not airspace. Courts have consistently upheld this. New York City's drone permit requirement — which charges a $150 fee and requires advance notice for commercial launches from city parks — is a property-use regulation, not an airspace restriction.

Public land use permits. Requiring a permit to operate a drone for commercial purposes from a public property is similar to requiring a film permit. It is a condition of access to city land, not a flight restriction.

Noise and nuisance. General nuisance ordinances apply to drones the same way they apply to other activities. A drone that creates unreasonable noise over a residential neighborhood is a nuisance. The fact that the noise source is airborne does not remove it from local jurisdiction.

Privacy. Several states have passed drone-specific privacy laws covering surveillance, photography over private property, and data collection. Most of these have survived legal challenge because they regulate conduct — what you do with the data — not how you fly.

Infrastructure at ground level. Drone pads, landing zones, charging stations, and operator facilities are ground infrastructure. Cities have full authority to regulate their placement, construction, and operation.

Public safety response. Cities can establish protocols for law enforcement response to non-compliant or dangerous drone activity, including reporting requirements, coordination with FAA, and use of detection technology.

The Gray Areas

Two areas cause most of the confusion.

Temporary flight restrictions around public events. Cities can restrict access to public space for events — a stadium, a parade route, a festival. But they cannot restrict airspace above that space without FAA coordination. The right approach is to work with the FAA to issue a Temporary Flight Restriction (TFR) for major events. Several cities have established standing relationships with their local FAA Flight Standards District Office (FSDO) for exactly this purpose.

Privacy regulations affecting commercial operators. Local privacy laws that regulate what commercial operators can do with images or data collected over the city are generally legitimate. Local laws that try to restrict where operators can fly — even framed as privacy protection — run into preemption problems. The distinction between regulating conduct and restricting flight paths matters.

What Good Local Ordinances Look Like

Cities with effective drone ordinances share certain characteristics.

They focus on conduct. Effective ordinances focus on what operators can do with the images and data they collect, not on where they can fly. A prohibition on using drone footage for persistent surveillance of identifiable individuals is far more defensible than a prohibition on flying within 500 feet of a building.

They coordinate with the FAA for the restrictions that need federal backing. Temporary no-fly zones for major events, restrictions near critical infrastructure, and airspace protections around sensitive facilities are legitimate — but they require FAA coordination and proper TFR issuance, not just a local ordinance.

They are enforced through permits. An ordinance that requires a permit to fly commercially from a city park gives the city enforcement leverage without asserting airspace authority. Violations are permit violations, not FAA rule violations — and they are fully within local jurisdiction to prosecute.

They are regularly reviewed. Part 107 has been amended multiple times since 2016. The regulatory environment for drones changes faster than most local ordinances are updated. Cities that build review schedules into their drone policies avoid the problem of enforcing rules that have been overtaken by federal changes.

The Enforcement Reality

The most common failure mode in drone ordinance enforcement is not legal challenge. It is practical: the city has no way to identify who is flying, no real-time awareness of violations, and no clear process for responding when something goes wrong.

Remote ID broadcasts are publicly available for any drone operating in the US under FAA rules in effect since September 2023. A city with the right monitoring tools can identify registered operators in real time. That changes enforcement from after-the-fact complaint response to active compliance awareness.

Cities that want their ordinances to have teeth need two things: clear legal authority in the right areas (property use, conduct, permits), and operational systems that give them visibility into what is actually happening in their airspace.

A Checklist for City Attorneys

Before finalizing any drone ordinance, verify:

  • Does the ordinance regulate conduct and ground-based property use, rather than flight paths or altitude?
  • Have time-sensitive event restrictions been coordinated with the FAA for TFR issuance?
  • Are permit requirements attached to property use (launch/landing on city land), not to flight operations generally?
  • Does the privacy provision regulate data collection and use, not where operators can fly?
  • Is there a working relationship with the local FSDO for enforcement coordination and TFR requests?
  • Has the ordinance been reviewed against the current FAA fact sheet on state and local UAS regulation?
  • Is there a review schedule built in for regulatory updates?

The cities that avoid costly legal challenges and actually enforce their drone regulations are the ones that understood from the start that their authority is real but bounded — and built their ordinances accordingly.

Related reading: FAA Part 108: What It Means for Local Communities — the upcoming BVLOS framework and what it changes for cities.

Disclaimer: This article is for general informational purposes only and does not constitute legal advice.