Waiver to Operate Drone Detection and Mitigation Systems: 124n

Due to public safety and liability concerns as well as related laws and regulations, waivers to operate some drone detection or mitigation systems are hard to come by, even for the federal government.

To assist the Department of Justice (DOJ), Department of Defense (DOD), Department of Energy (DOE), and Department of Homeland Security (DHS) in combating drone threats, Congress passed the Preventing Emerging Threats Act of 2018 (codified at 6 U.S.C. § 124n) ("the Act").

The Act provides DOJ and DHS with tailored legal waivers for authorized Department components to mitigate credible drone threats to designated facilities and assets which would otherwise be prohibited by various federal laws.

Extended until October 1st, 2024

DOJ guidance clearly provides instructions for an authorized Department to operate protective measures without being prevented by any of the following laws:

• • • Aircraft piracy (49 U.S.C. § 46502)
    • Destruction of aircraft (18 U.S.C. § 32) (destruction of aircraft),
    • Computer fraud (18 U.S.C. § 1030)
    • Interference with the operation of a satellite (18 U.S.C. § 1367)
    • Interception of communications (Title 18 chapter 119)
    • Pen registers and trap and trace devices (Title 18 Chapter 206).

But they must first go through an approval process. 

An Arduous Approval Process for 124n Covered Equipment

If an authorized Department component seeks to have a facility or asset designated as a covered facility or asset and to deploy protective measures at such a facility or asset, the component head will submit a written request for approval to the Deputy Attorney General (the “Approving Official”).

If an authorized Department component wishes to make a significant change to a previously designated covered facility or asset or a previously authorized protective measure, it will submit a request to the Approving Official updating the information previously provided.

All changes to system settings, however, must be coordinated in advance with the FAA and, when relevant, the National Telecommunications and Information Administration (“NTIA”) which may create a burdensome work effort.

The application process prescribes twenty pages of detail regarding the following components of an request including but not limited to:

1. 1. 1. Written request submitted no less than thirty (30) days before the date on which protective measures would be deployed or modification to such measures would go into effect
      2. Description of the facility or protected asset
      3. Relationship to the mission authorized in 124n
      4. Airspace restrictions
         • The request will describe whether the facility or asset is covered by airspace to which access is restricted, such as airspace subject to temporary flight restrictions imposed by the FAA
      5. Protective measures description
      6. Risk-based assessment
      7. Role of other entities under the Act or otherwise, technology to mitigate drone threats
      8. Requests from States or territories
         • The request will state whether the chief executive officer of a State or territory has requested the protective measures under extreme circumstances
      9. Coordination with FAA, NTIA or other entities
      10. Legal review summary from component counsel’s legal assessment of the request
      11. And finally, Approval

Department of Homeland Security – SAFETY Act and 124n

Congress enacted the DHS Support Anti-Terrorism by Fostering Effective Technologies (SAFETY) Act in 2002 in the aftermath of 9/11 to encourage the development, production, and use of Qualified Anti-Terrorism Technologies. The goal is also to provide vendors and end users liability limitations for claims resulting from an act of terrorism where these technologies are deployed. 

AeroDefense’s AirWarden™ is the first, and currently only, drone detection system to receive a SAFETY Act designation. In the past, SAFETY Act did not confirm or deny system legality, so it is significant that when our system received its designation in August 2019, DHS included this sentence in our official listing on their SAFETY Act website:  

“The Technology does not include a capability to defeat or interfere with the flight of UAS, or perform signal analysis functions which would require legal authorization.”

Since then DHS contributed to the August 2020 federal guidance on the legal use of drone detection and mitigation systems which warns that most radio frequency based drone detection vendors violate federal surveillance laws because they decode and demodulate private drone signals to extract information. On October 13, 2021 DHS posted a SAFETY Act Web Site Notice Regarding Counter-Unmanned Aircraft Systems (C-UAS). It states that DHS will now separate drone detection and C-UAS SAFETY Act applications into two categories that we have simplified:

• • 1. 124n governed (systems that decode and demodulate the drone signal)
    2. non-124n governed (systems that do not decode and demodulate the drone signal)

The significant level of effort to apply to deploy a mitigation and detection system subject to 124n may be worth it in certain circumstances. But some authorized Departments may find it more efficient to deploy drone detection systems that are not governed by 124n. Again, these are systems that do not have mitigation capabilities and do not decode and demodulate the signal between the drone and its controller.