6 U.S.C. § 124n: Federal Counter-Uas Authority and Compliance Requirements

Meta description: Learn what 6 U.S.C. § 124n authorizes for federal counter-drone operations, which safeguards apply, and how agencies must address privacy, aviation safety, and oversight.

Unmanned aircraft systems—commonly called drones—can pose security risks near sensitive government facilities and assets. At the same time, detecting or interfering with a drone can affect aviation, communications, privacy, and property rights. 6 U.S.C. § 124n establishes limited federal authority for the Department of Homeland Security and the Department of Justice to address certain credible drone threats. Understanding its scope means distinguishing that authority from ordinary drone regulation and following the statute’s conditions, agency procedures, and other applicable laws.

What 6 U.S.C. § 124n Covers

Section 124n is a federal counter-unmanned-aircraft provision. It authorizes specified officials within DHS and DOJ to take certain actions to mitigate a credible threat posed by a covered unmanned aircraft system to a covered facility or asset. The authority is not a general license for government agencies, private organizations, or the public to disable drones.

The provision was enacted as part of the FAA Reauthorization Act of 2018, in a section addressing the protection of certain facilities and assets from unmanned aircraft. It is codified in Title 6 of the U.S. Code, which contains federal homeland-security laws. The statute works alongside, rather than replacing, aviation, communications, criminal, privacy, and constitutional requirements.

In practical terms, § 124n is important because some counter-drone measures—such as disrupting a command link, taking control of an aircraft, or destroying it—may otherwise implicate laws that restrict interference with aircraft, radio communications, or property. The statute creates a defined federal framework for certain actions, subject to its limits and safeguards.

Who May Use the Authority

The statute assigns authority to the Secretary of Homeland Security and the Attorney General, subject to its terms and applicable delegations. It is not a standalone authority for every federal, state, or local law-enforcement agency. Operational responsibility must be traced to the statute, an authorized agency component, and any current delegation or implementing policy.

That distinction matters for public agencies and facility operators. A private airport, sports venue, utility, business, or individual does not acquire federal counter-UAS authority merely because a drone appears suspicious or flies near its property. Such parties should contact appropriate law enforcement or aviation authorities rather than attempt to jam, seize, or damage a drone themselves.

Covered Threats, Facilities, and Assets

Section 124n ties action to a credible threat involving a covered unmanned aircraft system and a covered facility or asset. The statute’s definitions and designation processes matter: not every drone flight is a threat, and not every location automatically qualifies for protection under this provision. Officials must assess the circumstances and the statutory criteria before relying on the authority.

Covered facilities and assets are identified under the law and applicable agency processes. Those processes may involve designations, security assessments, and coordination with relevant agencies. A facility’s sensitivity or a property owner’s request, on its own, should not be treated as proof that the statutory requirements are satisfied.

“Credible threat” calls for an evidence-based assessment rather than speculation. Relevant considerations may include the aircraft’s location and behavior, its apparent purpose, the nature of the protected facility, and information available to officials. The precise assessment must follow the statute and applicable policies; this article does not establish a separate legal test.

Actions the Statute May Permit

When the statutory conditions are met, § 124n authorizes a range of mitigation actions. Depending on the circumstances and applicable requirements, these may include detecting, identifying, monitoring, or tracking a UAS; warning its operator; disrupting control of the aircraft; taking control of it; seizing or otherwise disabling it; or using reasonable force to do so.

These powers are significant, but they are not unlimited. An action must be connected to mitigating a qualifying threat and must fit within the statute’s authorization. The availability of a particular technique depends on the situation, agency authority, safety considerations, and legal safeguards. “Counter-UAS” is an umbrella term, not permission to use every available technology in every case.

Measures can have effects beyond the aircraft itself. Radio-frequency interference may affect communications or navigation; taking control of a drone may create risks to people and property; physical interception may endanger aircraft or bystanders. A lawful response therefore requires more than identifying a potential drone: officials must consider necessity, proportionality, foreseeable effects, and safer alternatives under governing law and policy.

Key Compliance Requirements and Safeguards

Follow the statute and agency authorization

Before an operation, responsible officials should confirm that the facility or asset, the aircraft, the threat, the personnel, and the proposed mitigation measure fall within the statute and current agency procedures. Agencies should document the decision path and ensure that personnel are trained and authorized for the specific activity.

Protect privacy and civil liberties

Section 124n includes privacy and civil-liberties safeguards, including requirements for agency policies and procedures. Counter-UAS operations can collect information about operators, passengers, nearby residents, or unrelated activity. Agencies should limit collection and use to authorized purposes, handle information under applicable rules, and apply required retention, access, and sharing controls.

Privacy review is not limited to cameras. Radio-frequency detection, tracking data, device identifiers, and information about a drone’s operator may raise distinct concerns. Agencies should assess what information a system collects, whether it can capture unrelated communications or data, who can access it, and when it must be deleted or retained under law.

Account for aviation and communications laws

The statute operates against a broader legal background, including federal aviation and communications laws. Section 124n addresses specified federal counter-UAS actions; it does not generally repeal aviation-safety rules or authorize private parties to interfere with aircraft or radio transmissions. Agency counsel and technical specialists should assess the applicable legal framework before deployment.

Coordination with the Federal Aviation Administration and other relevant agencies is important where an action may affect the National Airspace System or aviation safety. Likewise, equipment that emits or interferes with radio signals can raise issues under federal communications law. The operational plan should account for these risks and any required coordination or approvals.

Use appropriate force and protect property

Where the statute permits force to mitigate a covered threat, the response remains bounded by the law’s requirements and applicable policies. Officials should consider potential injury, damage, falling debris, and the risk that an intervention could make the situation more dangerous. Actions should be tailored to the threat, and incidents should be documented and reviewed under agency procedures.

Maintain oversight and records

Section 124n contains oversight and reporting provisions, and implementing requirements may call for records of operations, effects, or complaints. Agencies should preserve information needed for review while applying privacy and records-management rules. Documentation can help establish why an action was taken, what authority supported it, what method was used, and whether any unintended effects occurred.

How Section 124n Relates to FAA Drone Rules

The FAA primarily regulates civil aviation and the safe operation of aircraft in U.S. airspace. Its rules address matters such as aircraft registration, pilot requirements, operating limits, and airspace restrictions. Section 124n, by contrast, concerns defined federal responses to credible UAS threats at covered facilities or assets.

These legal frameworks can overlap in a real incident. A drone may violate an FAA restriction without automatically satisfying § 124n’s requirements. Conversely, an authorized federal mitigation action does not erase the need to consider aviation safety or other applicable rules. Facility operators should report suspected violations to the appropriate authorities and avoid treating FAA restrictions as permission to interfere with a drone.

What the Statute Does Not Authorize

• It does not grant general counter-drone powers to the public. Individuals and private businesses should not jam signals, hack a drone, seize it, or shoot it down.
• It does not make every drone near a sensitive location a credible threat. The statutory criteria and agency process must be met.
• It does not automatically authorize every federal agency. The statute identifies DHS and DOJ authorities; other agencies need their own applicable legal authority.
• It does not eliminate other legal duties. Privacy, aviation safety, communications, criminal, and constitutional requirements may still apply.
• It does not guarantee that a particular technology or tactic is lawful. Legality depends on the facts, authority, method, and current law.

Practical Compliance Checklist for Agencies

1. Verify current authority. Review the current U.S. Code, amendments, effective dates, sunset provisions, delegations, and agency policies before an operation.
2. Confirm statutory coverage. Establish that the facility or asset and the threat meet the relevant definitions and requirements.
3. Assess necessity and risk. Evaluate the credibility and immediacy of the threat, alternatives, potential harms, and aviation or communications effects.
4. Use approved personnel and systems. Confirm training, authorization, equipment controls, and coordination with relevant agencies.
5. Apply privacy protections. Minimize unrelated collection and follow rules for access, retention, sharing, and deletion.
6. Document and review. Record the basis for the decision, the action taken, its effects, and any complaints or unintended consequences.

Why Current Verification Matters

Federal authority can change through amendments, appropriations laws, extensions, or expiration of temporary provisions. A web page summarizing § 124n may not reflect the latest legal status or agency implementation. Before relying on the statute, readers should consult the current text in the U.S. Code, the relevant enacted public law, and current DHS or DOJ guidance. The Congress.gov legislative record can help identify amendments and extensions.

For a particular operation, legal counsel should verify whether the authority remains in effect, who may exercise it, what designations and procedures apply, and whether additional approvals are required. These details can determine whether a proposed response is within federal authority.

Reliable Sources for Further Research

• Office of the Law Revision Counsel, U.S. House of Representatives: current codified text of Title 6 and amendment notes.
• Congress.gov: public laws, bills, and legislative histories concerning counter-UAS authority.
• Federal Aviation Administration: drone registration, operating rules, airspace restrictions, and safety information.
• Federal Communications Commission: federal communications resources relevant to radio-frequency equipment and interference.

Bottom line: 6 U.S.C. § 124n is a targeted federal tool for DHS and DOJ to mitigate qualifying drone threats at covered facilities and assets. Its use depends on statutory conditions, authorized personnel, operational safeguards, and coordination with other legal requirements. It is not a broad permission for private drone countermeasures.