United States: Task Force Makes Drone Registration Recommendations Expected To Be Adopted By The FAA, But On What Authority?

On November 21, 2015, the Unmanned Aircraft Systems Registration Task Force Aviation Rulemaking Committee, chartered by the FAA, issued its Final Report to the FAA containing the Task Force's recommendations for how the FAA should implement a national drone registry system. With the dueling goals of maintaining safety in the National Airspace System (NAS) while also encouraging the emergence of the nascent UAS industry, the Task Force was given a difficult job: "develop recommendations for the creation of a registration process" for sUAS. The Final Report is particularly timely, as somewhere between 500,000 to 1 million drones (nearly all of which will be sUAS) are expected to be sold in the United States over the upcoming holiday season.


Although the final report contains ample evidence of disagreement amongst the Task Force's 25 members (which ranged from Google to DJI to Walmart), a "general consensus" was ultimately reached on the following recommendations:

  1. Users must fill out "an electronic registration form through the web or through an application, which would immediately provide the user with an electronic certificate of registration and a personal universal registration number for use on all sUAS owned by that person."
  2. The registration number must be marked on the sUAS before operations in the NAS in a way that is "readily accessible." A user could also opt to identify the drone using the unique serial number provided by the manufacturer in lieu of using the FAA-generated registration number.
  3. The registrant must be at least 13 years old and provide his or her name and physical address to the FAA.
  4. Registration should encompass an "education component," similar to Know Before You Fly.1
  5. Drones that weigh 250 grams or less, including the aircraft, payload, and any other associated weight, would be exempted from the registration requirement.

According to the Task Force, these recommendations will serve the goals of: (i) educating users on the safe operating rules for sUAS; (ii) linking a sUAS to the operator in the event of an incident or accident; and (iii) taking a risk-based approach to registration.

Although the recommendations appear straightforward, they leave some unanswered questions. For example, how useful will a registration number be in the event a drone actually collides with, and is completely destroyed by, a manned aircraft? And what good is the 250 gram exemption when nearly every drone, even toys, weighs more than that? The Task Force implicitly acknowledged these questions, but did not answer them, citing the "time-limited tasking" they were given by the FAA.

Despite these questions, it is anticipated that the FAA will adopt, in large part, the Task Force's recommendations and issue a "direct final rule" requiring registration through its "emergency" rulemaking power under the Administrative Procedure Act (APA). In doing so, the FAA will ignore outstanding legal questions about the process by which it will issue the registration rule, as well as whether it even possesses the underlying authority to adopt the rule.


Generally speaking, under the APA, an agency like the FAA cannot make rules without giving the public notice and an opportunity to comment on the proposed rule. See 5 U.S.C. § 553(b). In limited circumstances, however, an agency can forgo the standard notice-and-comment requirements and directly issue a final rule. 5 U.S.C. § 553(b)(3). Pertinent here, when an "agency for good cause finds . . . that notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest," the notice-and-comment period can be bypassed. 5 U.S.C. § 553(b)(3)(B).

"Emergency rulemaking" usually follows situations that require immediate action (such as a national disaster), minor technical amendments that do not affect the substantive law, or instances where Congress has directed the action in legislation. Nonetheless, the FAA is apparently considering the absence of rules regarding public registration of drones to be an "emergency," and it appears ready to issue a final rule without allowing for public comment.

Under the "good cause" exemption, the FAA itself determines whether to invoke emergency rulemaking, and challenges to the final rules can only be filed after the rules are promulgated. Moreover, despite courts' cautioning they will "narrowly construe" agency actions utilizing the emergency rulemaking exception, in reality the agency's action is often left untouched.

It is unlikely the FAA will try to justify emergency rulemaking by stating that the public interest is not involved (in fact, the Task Force's Report proves the opposite). Moreover, because the notice-and-comment requirements are presumptively applicable to all substantive rulemaking, the FAA likely will not attempt to assert that the traditional rulemaking process is "unnecessary." Thus, the FAA will likely try to justify this "emergency" treatment on the ground that the notice-and-comment period is "impracticable."

"Impracticable" has generally been defined to refer to a situation in which the required execution of agency functions would be unavoidably prevented by public rulemaking proceedings. However, "time constraints" and the "imminence of a deadline" are considered "inadequate justifications to invoke the good-cause exemption, especially when it would have been possible to comply with [a] statutory deadline."2 Put another way, an agency cannot create its own "emergency" (intentionally or otherwise) by delaying announcement of proposed rules.

That begs the question: is the FAA's emergency rulemaking for drone registration valid?

On February 14, 2012, in the FAA Modernization and Reform Act of 2012 (the "2012 Act"), Congress instructed the FAA to issue rules for the "safe integration" of UAS by September 30, 2015. Although the FAA has issued its Notice of Proposed Rulemaking, and comment period has closed, the FAA has yet to finalize these rules, despite nearly four years lapsing between Congress's mandate and today.

With that background, the FAA now intends to issue the Registration Rules directly within the next month, presumably before the massive influx of sUAS enters the NAS this holiday season. If the holiday shopping "deadline" is the impetus for the FAA's "emergency" rulemaking, it seems that the FAA is the cause of its own crisis, and its action may be vulnerable if challenged.

In an analogous situation, the FAA claimed that "good cause" was present, and bypassed the notice-and-comment requirements, when promulgating Penalty Rules for violations of FAA regulations.3 There, a private petitioner challenged the FAA's action and a federal appellate court held that the FAA was required to follow the APA's notice-and-comment requirements because the rule substantially affected the petitioner's (and others' similarly situated) substantive rights. The Court further pointed out that the "good cause" exception should be used for "housekeeping" matters, which are traditionally thought of as purely procedural rules. Notably, in that case, the FAA waited only 9 months to begin promulgating the rules. Here, it has waited years.

If an agency can create its own emergency to bypass the APA's notice-and-comment requirements, public comment will effectively be optional for agencies. This not only creates perverse incentives for agencies directed to make rules for hotly debated topics like drones to do so through emergency rulemaking in the hopes of avoiding extensive and controversial public comment, but it also, ironically, threatens to slow down the entire rulemaking process, as lawsuits will inevitably follow such actions.4


In addition to the FAA's procedural shortcuts, the issues of both who and what the registry would encompass present legal challenges. Under the Task Force's model, registration would apply to commercial and hobbyist users alike. In addition, users wouldn't be registering their drones with the FAA; they would be registering themselves.

Traditionally, model aircraft flown for hobby or recreational purposes have not been subject to any registration requirements. This understanding was codified under Section 336 of the 2012 Act, which provides that "notwithstanding any other provision of law relating to the incorporation of unmanned aircraft systems into Federal Aviation Administration plans and policies . . . the Administrator of the Federal Aviation Administration may not promulgate any rule or regulation regarding a model aircraft," so long the aircraft meet certain criteria. Congress defined "model aircraft" under Section 336 as "an unmanned aircraft that is capable of sustained flight in the atmosphere, flown within visual line of sight of the person operating the aircraft, and flown for hobby or recreational purposes."

According to the FAA, the 2012 Act does not affect its ability to require registration of drones flown for hobby or recreational purposes. The agency's stance is that registration has been exempted for model aircraft only through the use of its own discretion, and that prior law unrelated to the incorporation of UAS into FAA plans and policies, specifically 49 U.S.C. 44101(a), gives it the authority to require registration of model aircraft. Notably, the Task Force recognized that, despite the FAA's assertions, the agency may actually lack authority to require registration of drones used for hobby or recreational purposes. Nonetheless, the Task Force did not address that issue because it was "outside the scope of the Task Force's objectives[.]"

The FAA's position is the latest move away from its hands-off attitude towards model aircraft, dating back at least to mid-2014. In June of last year, the FAA issued its "Interpretation of the Special Rule for Model Aircraft." There, the FAA claimed that model aircraft are "subject to all existing FAA regulations." More recently, the rules proposed in the Notice of Proposed Rulemaking for sUAS exempt various types of aircraft or flying vehicles from their ambit, such as moored balloons, kits, amateur rockets, among others, but not model aircraft.

Taken together, the FAA's actions suggest that model aircraft are likely to be subject to increasing regulation. However, it is unclear how to reconcile the plain text of Section 336 of the 2012 Act with the FAA's registration scheme or with the FAA's own interpretation of Section 336, for that matter. In the Interpretation of the Special Rule for Model Aircraft, the FAA noted that "a model aircraft operated pursuant to the terms of section 336 would potentially be excepted from a UAS aircraft certification rule[.]" It is difficult to see how a registration requirement is different.

A second and distinct question concerns whether the FAA has the authority to register people, as opposed to planes, as the Task Force recommends through its one-unique-number-per-person plan. The FAA has stated that it has the authority to require the registration of any "aircraft" that flies in the NAS, but if a user has many unique aircraft all with the same number, it is the person, not the aircraft, that is being tracked.

Other conflicts abound. Under current law, in order to register an aircraft, the aircraft must be owned by a citizen of the United States, a lawful permanent resident, or a corporation doing business under the laws of the United States or a state. 49 U.S.C. § 44102. Yet, the Task Force recommends a rule that would not require citizenship or lawful permanent resident status. If "aircraft" is the registration hook for the FAA, these other statutory requirements might apply to sUAS users.


The Task Force's recommendations appear simple enough. But lurking beneath the surface are complicated issues of agency process and the FAA's authority that may be primed for takeoff.


1. http://knowbeforeyoufly.org/.

2. 2 AM. JUR. 2D Administrative Law § 185 (2012) (emphasis added).

3. Air Transport Assoc. of Am. v. Dep't of Trans., 900 F.2d 369 (D.C. Cir. 1990) ("[T]he FAA is foreclosed from relying on the good cause exception [from the APA,] by its own delay in promulgating the Penalty Rules. The agency waited almost nine months before taking action to implement its authority under section 1475. At oral argument, counsel for the FAA conceded that the delay was largely a product of the agency's decision to attend to other obligations. We are hardly in a position to second guess the FAA's choices in determining institutional priorities. But insofar as the FAA's own failure to act materially contributed to its perceived deadline pressure, the agency cannot now invoke the need for expeditious action as "good cause" to avoid the obligations of section 553(b).").

4. Another potential problem for the FAA is Executive Order 12866, which requires agencies to complete a cost- benefit analysis for rules that, among other things, raise novel legal or policy issues. Given that drone registration will likely raise both novel legal and policy issues, such an analysis may be required.

Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Morrison & Foerster LLP. All rights reserved

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Christopher J. Carr
Joanna Simon
Andrew Barr
In association with
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.