Singer v. Newton: Are State and Local Governments Now Prohibited From Regulating Drones?

The short answer is, no.  The Singer decision is narrow, non-binding, leaves other parts of the ordinance in place, and expressly leaves the door open for Newton (and other state and local governments) to enact more narrowly-tailored regulations on drones.

In a way, the four challenged provisions of the Newton ordinance were an easy call, because each conflicted with or effectively usurped existing FAA regulations.  This allowed the court to invoke the doctrine of “conflict preemption,” as opposed to what is called “field preemption.”

“Field preemption” is invoked when the federal government occupies the entire field of an area of regulation that is within its Constitutional authority, even though it might not have enacted a specific regulation pertaining to the challenged state or local law.  Significantly, the court rejected field preemption because the FAA has expressly left the door open to some state regulation of drone use (such as the privacy protections of Florida’s FUSA statute, which I discussed, here).

“Conflict preemption” means exactly what it implies:  That when the federal government regulates an area within its Constitutional authority, those regulations are the supreme law of the land and the states may not enact laws that would contradict or undermine the federal regulation.

Briefly:

Section (b) of the Newton ordinance provided that “[o]wners of all pilotless aircraft shall register their pilotless aircraft with the City Clerk’s Office, either individually or as a member of a club . . . .”  Because the FAA has held itself out as the exclusive authority for registration of aircraft, striking down this provision of the ordinance was that rare bird in litigation: a no-brainer. This is probably the broadest part of the decision, in that the court made it clear that the city may not require any kind of drone registration, period.

The ordinance at subsection (c)(1)(a) prohibited drone flights below an altitude of 400 feet over any private property without the express permission of the property owner.  Also, subsection (c)(1)(e) prohibited flying drones over public property, at any altitude, without prior permission from the city.  The court found that these provisions had the effect of banning all drone flights in the city, because FAA regulations restrict sUAS flights to below 400 feet AGL.  While the FAA left the door open to some local regulation of drones, that should not be interpreted as license to effectively ban drone operations. This leaves the door open to the possibility of a more narrowly-drawn ordinance.

Finally, subsection (c)(1)(b) of the ordinance prohibited drones from being operated “at a distance beyond the visual line of sight of the Operator.”  This was plainly duplicative of Part 107 and, as such, tended to usurp an express regulation of the FAA (which could, at some time in the future, change its mind about BVLoS operation).

The decision ends with a note that Newton is welcome to craft narrower regulations.  Precisely what those regulations will look like is hard to say.

Whatever the case may be, one should not take this as an invalidation of drone regulations in one’s particular state or city.  The court only addressed these specific provisions of the Newton ordinance, and the decision has no binding effect on other courts, let alone other states and municipalities.

But let us not detract from the significance of this win, either.  Major kudos are in order for the petitioner, Dr. Michael Singer, and his attorneys.

The FAA’s Drone Registration Requirement: A Brief Review

CHRISTMAS MORNING – SOMEWHERE IN AMERICA

A 12-year old boy opens a large package under the tree as his mom looks on with a tired smile.  “A drone!” the boy exclaims. “Just what I wanted! Thanks, Mom! Can I fly it, now? Can I, please?”

“I’m sorry, hon,” his mom sighs, “but you’re going to have to wait. Daddy’s still on the FAA website.”

And there you have it.  For the first time in the history of Christmas, an agency of the United States government will require you to register your child’s toy before he can begin to play with it.

Why?  Good question.

Section 336 of the FAA Modernization and Reform Act of 2012 contains an express prohibition, that the FAA “may not promulgate any rule or regulation regarding a model aircraft. . . .”  We naively assumed that, when Congress says that an agency “may not” do a thing, the agency indeed “may not” do it.

But nothing will upset the Constitutional order of the Republic faster than a bout of media-driven hysteria. The FAA has taken the position that all drones – including what were traditionally called model aircraft – are “aircraft” within the meaning of the Federal Air Regulations.  Taking its cue from panic over sightings of drones coming too close to manned aircraft, the FAA suddenly decided that 49 U.S.C. § 44102 gives it the authority to require registration of all drones, regardless of whether they are operated recreationally or professionally.

A task force of very capable individuals was quickly set up to provide recommendations to the FAA on drone registration.  Their proposal was subjected to a lightning-fast comment period which, depending on who you ask, may or may not have violated the Administrative Procedure Act.

The Final Interim Rule (a title which leads us to suppose that the rule isn’t FINAL final) on drone registration has been published, here.

The putative purpose of the registration requirement:

The estimate for 2015 sales indicates that 1.6 million small unmanned aircraft intended to be used as model aircraft are expected to be sold this year (including approximately 50 percent of that total during the fourth quarter of 2015). With this rapid proliferation of new sUAS will come an unprecedented number of new sUAS owners and operators who are new to aviation and thus have no understanding of the NAS [National Airspace System – ed.] or the safety requirements for operating in the NAS.

The risk of unsafe operation will increase as more small unmanned aircraft enter the NAS. Registration will provide a means by which to quickly identify these small unmanned aircraft in the event of an incident or accident involving the sUAS. Registration of small unmanned aircraft also provides an immediate and direct opportunity for the agency to educate sUAS owners on safety requirements before they begin operating.

Let’s unpack that last paragraph:

1) The risk of unsafe operation will increase as more small unmanned aircraft enter the NAS.

Well, maybe. The fact is that we don’t really know. Numerous reports of “drone strikes” on manned aircraft have turned out to be false.  In any event, Congress expressly prohibited any “rule or regulation” concerning model aircraft.  We are unaware of the FAA’s authority to circumvent Congress.  Indeed, it is almost laughable that the FAA seized the authority to require registration while claiming, for example, that it lacks statutory authority to waive the airman certification requirement under Section 333 or to waive the registration fee requirement for model aircraft.

2) Registration will provide a means by which to quickly identify these small unmanned aircraft in the event of an incident or accident involving the sUAS.

This makes two very large assumptions, neither of which is likely to be valid.  First, there have been almost no incidents of alleged threats to the NAS in which the offending drone has been recovered.  Without recovery, there will be no identification.

Second, it assumes 100% compliance with the registration requirement.  We frankly doubt that the level of compliance will be anything approaching 100%.  We especially doubt that those who are intent on causing harm or, at least, mischief, are likely to comply.

3) Registration of small unmanned aircraft also provides an immediate and direct opportunity for the agency to educate sUAS owners on safety requirements before they begin operating.

This might be true if the rule had either a point of sale requirement (unworkable) or required a device that prevented the drone from being operated before it was registered (some drone companies build this sort of requirement into their devices).  But the rule does neither.

In addition to being likely ineffective and almost certainly contrary to law, the FAA registry will present a significant likelihood of exposing private data to the public.

The drone registration site is here.

The deadlines for compliance is December 21, 2015 for drones that are intended to be used exclusively as model aircraft but never flown, February 19, 2016 for drones that have been previously operated as model aircraft.

Merry Christmas!

FAA Publishes Drone Registration Rules

Other than a few blurbs on Twitter, I haven’t had much to say about the pending rules on drone registration, primarily because it was unclear to me just how it could work, especially vis a vis hobbyists.  And it seemed especially unlikely to achieve the putative goal of allowing authorities to trace drones that endanger other aircraft back to their owners.

As I have said in the past, where the burden imposed by a regulation significantly outweighs the chance of getting caught, the likely result will be a lot of non-compliance.  And, as with many things, the people who do comply are unlikely to be the people that you need to worry about.

But I also know some of the stakeholders who participated in crafting the rule, and I wanted to wait and give them the benefit of the doubt.  They were given an enormous task, and very little time to come up with a solution.

Following a breakneck rule-making timeline, the interim final rule on drone registration has now been published.  It goes into effect next Monday.