Quick-reference answers on counter-UAS systems, technologies, legal authorities, the C-UAS marketplace, and layered defense architecture. For the full technical walkthrough, see What is Counter-UAS?.
Counter-UAS
Counter-UAS (C-UAS) is the doctrine, technology, and tradecraft of detecting and defeating unauthorized or hostile unmanned aerial systems. It is not a single product or a single sensor - it is a kill chain that spans detection, classification, decision, and engagement, operating across the electromagnetic spectrum and the physical domain simultaneously.
A competent C-UAS capability layers radar, cooperative RF (Remote ID, ADS-B), non-cooperative SIGINT, electro-optical/infrared, acoustic, and increasingly LiDAR - fused into a single operational picture so an operator sees one threat, not five uncorrelated reports. On the effector side it combines passive measures, electronic attack, directed energy, and kinetic interceptors, matched to the engagement geometry and legal authority of the environment.
See the full technical reference: What is Counter-UAS?.
Counter-UAS Systems
Counter-UAS systems are the integrated hardware and software stacks that detect, track, classify, and defeat unauthorized drones. The category spans vendor-specific single-sensor point solutions (a radar, a jammer, an RF direction-finder) through fused multi-sensor platforms that operate as a unified kill chain.
The systems worth evaluating are the ones that can ingest sensors from multiple vendors, fuse them mathematically (not just display them on a shared screen), enforce engagement policy locally, and deploy at the edge without a cloud dependency. Most systems marketed as "integrated" put four feeds on one dashboard and call it fusion. That collapses the moment a real incursion generates more than two simultaneous tracks.
Empyrean's CUAS capability runs multi-hypothesis tracking with optimal global assignment across heterogeneous sensor classes - so the 25th detection in a dense scene gets the same association quality as the first.
Counter-UAS Marketplace
The Counter-UAS marketplace is fragmented across sensor vendors, effector vendors, and a small number of fusion/C2 platforms attempting to tie them together. Specialization is the norm - radar vendors focus on radar, RF vendors focus on RF, and the operator is left to integrate.
The market splits roughly into: long-range radar (EchoDyne, DeTect, Hensoldt, SRC, SpotterRF), RF detection and direction finding (DroneShield, CRFS, Dedrone, Bluehalo), EO/IR (FLIR/Teledyne, HGH, Aselsan), acoustic (Squarehead, WAAY, Scylla), kinetic interceptors (Anduril Anvil, Fortem DroneHunter, Raytheon Coyote), directed energy (Epirus HPM, Lockheed HELWS, Boeing Compact Laser), and fusion/C2 layers (the layer Empyrean operates in).
Program offices increasingly buy best-of-breed sensors and demand an open fusion layer that can tie them together. Closed vertically-integrated stacks are losing budget share to open-architecture platforms that preserve sensor choice.
Counter-UAS (C-UAS) Grant Program
Federal and state-level C-UAS grant programs fund deployment of counter-drone capabilities at critical infrastructure, airports, and public safety agencies. At the federal level, funding flows through DHS CISA, FAA (under limited statutory authorities), DOE for energy infrastructure, and DoD for military installations.
State-level programs are emerging but constrained by 10 USC 130i and related statutes - which restrict active mitigation authority (jamming, kinetic engagement) to federal agencies. Most grant-funded programs at the state and local level therefore fund detection and tracking capability, with mitigation handled through coordination with federal partners or through operator interdiction via law enforcement.
Detection-only grants still create real value: early warning, pattern-of-life analysis, operator localization through RF direction-finding and Remote ID, and evidence preservation for prosecution. A detection-heavy posture is what most non-federal operators actually have legal room to deploy.
Counter-UAS Authority Extension Act
The Counter-UAS Authority Extension Act refers to ongoing legislative efforts to expand 10 USC 130i interdiction authority beyond the current federal agencies (DoD, DHS, DOJ, DOE) to state and local law enforcement and certain critical infrastructure operators. The statutory framework has been extended multiple times and remains under active debate.
The core gap it addresses: airports, power plants, refineries, stadiums, and state/local law enforcement have no legal authority to jam, spoof, or kinetically engage a hostile drone, regardless of how clearly threatening the incursion is. Authority sits with a small number of federal agencies that cannot scale to every incident. The gap between threat evolution and authority evolution is the single most significant policy failure in CONUS C-UAS posture.
Empyrean takes no position on which entities should hold interdiction authority. We build so that when authority is granted, the operator's technical stack is already in place to exercise it lawfully with a full audit trail - see the Policy & Decision Layer.
Counter-UAS Technologies
Counter-UAS technologies split into two functional classes: sense technologies that detect and classify drones, and act technologies that defeat them. Each class has fundamentally different physics, cost curves, and legal constraints.
Sense includes radar (FMCW for small RCS, AESA/MESA for electronic beam steering), cooperative RF (Remote ID, ADS-B), non-cooperative SIGINT (SDR sweeps with TDOA or beamforming DF), electro-optical/infrared (visible, SWIR, MWIR, LWIR bands), acoustic (phased microphone arrays with ML classification), LiDAR (emerging for terminal-zone classification), and UAS-as-a-sensor (tethered and free-flying airborne payloads).
Act includes passive measures (camouflage, dispersion, EMCON), electronic attack (RF jamming, GNSS denial, protocol exploitation), cyber effects (firmware exploits, GCS compromise), directed energy (high-energy lasers, high-power microwave), kinetic interceptors (drone-on-drone, guided munitions, airburst), and operator interdiction through law enforcement.
No single technology defeats every drone. Layered architectures with graduated response and sensor fusion across all modalities are the only approach that holds up in contact.
Counter-UAS Measures
Counter-UAS measures are the operational and technical actions taken to detect, deter, and defeat hostile UAS. Measures are typically grouped by response class: passive (reduce the target signature), soft-kill (non-kinetic defeat via RF, cyber, or directed energy), and hard-kill (kinetic interceptors or explosive munitions).
In CONUS force protection contexts, most operators lack statutory authority for active mitigation and are limited to passive measures plus operator interdiction via law enforcement. In OCONUS and combat contexts the full effector spectrum is available but subject to ROE, collateral damage concerns, and deconfliction with friendly air traffic.
The right measure for a given threat depends on threat class (commercial COTS, modified FPV, OWA drone, swarm), engagement geometry (standoff vs terminal), the operating environment (urban, maritime, remote), and what authorities the defender actually holds. Systems that enforce measure selection via auditable policy - rather than pure operator judgment under time pressure - reduce fratricide risk and make post-engagement defensibility much stronger.
Counter-UAS Solutions
Counter-UAS solutions are the end-to-end capabilities - combining sensors, effectors, command and control, and operator training - that a defender deploys to address a specific drone threat. A solution is not a product; it is a posture matched to a threat, an environment, and an authority.
A C-UAS solution for a CONUS airport looks nothing like a solution for a forward operating base. The airport needs detection, airspace coordination with the tower, and Remote ID integration under FAA Part 89 - with mitigation handled by the responding federal agency. The FOB needs layered soft-kill and hard-kill effectors, edge-deployed fusion that survives loss of comms, and integration with broader theater air defense.
A solution worth buying is one the vendor can honestly deploy at your site against your actual threat profile. Demos in sterile environments with cooperative targets prove nothing. Ask for live-fire or exercise data from environments that look like yours. See our approach.
Can I legally jam or shoot down a drone over my facility?
Almost certainly not, unless you are a federal agency or a trained and certified state/local law enforcement officer operating under the SAFER SKIES Act.
Prior to December 2025, only a small number of federal agencies - principally DHS, DOJ, DOD, and DOE - had the legal authority to detect, track, and mitigate (jam, spoof, seize, disable, or destroy) unauthorized drones. Federal criminal statutes including 18 U.S.C. § 32 (destruction of aircraft), the Wiretap Act, and FAA regulations collectively prohibited non-federal actors from interfering with aircraft in flight - and drones are legally aircraft.
The SAFER SKIES Act, signed into law on December 18, 2025 as part of the FY2026 National Defense Authorization Act, extends limited counter-UAS mitigation authority to state, local, tribal, and territorial (SLTT) law enforcement and correctional agencies - but only under tightly controlled conditions. Certification is individual, role-specific, and federally overseen. Only officers who complete DOJ-approved training at the FBI's National Counter-UAS Training Center may exercise mitigation authority. Agencies may only use systems that appear on a federally maintained list of authorized technologies.
For private-sector facility operators - energy utilities, data centers, venues, ports - the answer remains the same: you cannot jam, spoof, or kinetically interdict a drone. Your authority is limited to detection, tracking, classification, documentation, and reporting to law enforcement or federal agencies who have the authority to act.
This is precisely why Empyrean's C-UAS workflow is designed around the detection-to-handoff chain rather than detection-to-interdiction. Detect the drone. Classify it. Document the track history and RF signature. Produce an evidence-grade package. Alert the law enforcement partner with enough information for them to act. The faster and more complete that handoff is, the more likely the responding agency can take action while the drone is still in the air.
What is the SAFER SKIES Act?
The SAFER SKIES Act (Safeguarding the Homeland from the Threats Posed by Unmanned Aircraft Systems Act) was signed into law on December 18, 2025 as Title LXXXVI of the FY2026 National Defense Authorization Act. It is the first federal legislation to grant counter-UAS mitigation authority to non-federal law enforcement agencies.
The Act authorizes SLTT law enforcement and correctional agencies, after individual officer certification and training, to detect, track, seize, disable, or destroy drones that pose a credible threat to people, critical infrastructure, major public events, or correctional facilities. The authority is bounded by federal oversight, approved technology lists, and post-action reporting requirements. DHS and DOJ were directed to publish implementing regulations within 180 days of enactment.
Shortly after passage, FEMA awarded an initial $250 million to the 11 U.S. states hosting FIFA World Cup 2026 matches and the National Capital Region under a new counter-UAS grant program. Funds may be used for detection, identification, tracking, monitoring, and mitigation of threatening UAS activity. The FBI conducts counter-drone operations at roughly 14 major events per year, and expects to have dozens of SLTT officers trained and operating under FBI authority by the 2026 FIFA World Cup.
For facility operators, the SAFER SKIES Act changes the coordination dynamic. Your law enforcement partners may now have - or will soon have - the legal authority and the trained personnel to act on the drone detection data you provide. The value of your detection and classification capability increases directly with the completeness and speed of the data you can hand off to those partners.
What is FAA Remote ID?
Remote ID is the FAA's requirement that drones in flight broadcast identification and location information that can be received by other parties through a wireless signal. The FAA describes it as a "digital license plate" for drones. The Remote ID rule has been in effect since March 16, 2024, and applies to all drones that are required to be registered - both commercial (Part 107) and recreational.
A compliant drone broadcasts its serial number, its location and altitude, its control station location, a time mark, and an emergency status indicator. This data is broadcast locally (typically Bluetooth 5 or Wi-Fi) and can be received by anyone with a Remote ID receiver - including law enforcement, airport security, and C-UAS detection systems.
Remote ID is significant for facility and venue security because it provides a cooperative identification layer for drone detection. When a drone is detected over a facility, the first question is: is this authorized or unauthorized? Remote ID, correlated with LAANC authorization data, can answer that question immediately. A drone broadcasting a valid Remote ID that matches a current LAANC authorization for that airspace is likely legitimate. A drone with no Remote ID broadcast - or a spoofed one - warrants escalation.
Empyrean integrates Remote ID reception into its C-UAS workflow, correlating Remote ID broadcasts with RF detection, radar tracks, and camera analytics to classify detected drones as cooperative (with valid ID and authorization) or non-cooperative (no ID, no authorization, or anomalous behavior). The classification drives the response workflow: cooperative drones are logged and monitored; non-cooperative drones trigger alert chains to security operations and law enforcement.
What is LAANC?
LAANC - the Low Altitude Authorization and Notification Capability - is a collaboration between the FAA and private-sector UAS Service Suppliers (USSs) that automates the process of requesting and receiving authorization to fly drones in controlled airspace below 400 feet. LAANC provides near-real-time approval for operations within pre-approved altitudes defined in UAS Facility Maps, and routes higher-altitude requests to air traffic managers for manual review.
For security operations, LAANC data provides the authorization context needed to classify a detected drone. When a drone is detected near an airport, a port, or any facility within controlled airspace, the critical question is whether that drone has an active LAANC authorization for its location and altitude. A drone with a valid authorization is operating within the system. A drone without one is either non-compliant or unauthorized - and the distinction between the two matters for the response decision.
Empyrean correlates drone detections against LAANC authorization data as part of the classification workflow. This is particularly important for airports and transportation hubs where legitimate commercial drone operations (pipeline surveys, construction monitoring, agricultural applications) may occur in proximity to the facility. The security team needs to distinguish the authorized operator from the unauthorized intruder without disrupting legitimate operations - and that distinction depends on LAANC data.
What happens when a drone enters airport airspace?
At a Part 139 certificated airport, an unauthorized UAS incursion can trigger a ground stop - halting departures and forcing arriving aircraft into holding patterns. The financial impact is immediate: airlines incur delay costs measured in tens of thousands of dollars per minute. The regulatory impact follows: the FAA opens an investigation, TSA may initiate a security inquiry, and the airport's incident report enters the federal record.
Currently, most airports detect drone incursions through pilot reports or visual observation by tower controllers. There is typically no organic UAS detection system, no automated Remote ID reception, and no correlation with LAANC authorization data. The security coordinator receives a verbal report - "we saw something near the approach corridor" - and must decide whether to recommend a ground stop based on incomplete information.
Empyrean's airspace awareness layer integrates radar, RF detection, Remote ID receivers, and camera analytics alongside the airport's existing ADS-B infrastructure. Cooperative drones are identified via Remote ID and checked against LAANC authorizations. Non-cooperative targets generate alerts with track data, RF characterization, and estimated position. The airport security coordinator and the FAA/TSA liaisons (via TAK federation) see the same picture - and the ground stop decision is based on data rather than a verbal report from someone who saw something out the window.
How do drone detection systems work?
Drone detection systems use one or more sensor technologies to identify, locate, and track UAS in a defined area. The four primary detection methods are:
RF (Radio Frequency) detection monitors the electromagnetic spectrum for the communication signals between a drone and its controller. RF detection can identify the drone model (based on its signal characteristics), locate both the drone and the operator, and provide classification data. It is the most widely deployed detection method for C-UAS because it can identify the pilot - which radar and cameras cannot. Range depends on environment and hardware but typically extends several kilometers.
Radar uses reflected radio waves to detect flying objects regardless of whether they are broadcasting any signal. Radar provides position, speed, and heading data and works against non-cooperative targets (drones with no Remote ID, no RF link, or operating autonomously). Radar can generate false positives from birds, weather, and debris, and is typically paired with other sensors for classification.
Electro-Optical/Infrared (EO/IR) uses cameras - visible light and thermal - to visually confirm and track drone targets. EO/IR provides evidentiary imagery and can be cued by other sensors (radar or RF) to point at a detected target for visual confirmation. Performance depends on lighting, weather, and range.
Acoustic detection uses microphone arrays and AI-based sound recognition to identify the distinctive motor and propeller noise of drones. Effective in quiet environments at short range (typically under 1 km) but degrades rapidly in noisy or windy conditions.
No single sensor is sufficient alone. Effective C-UAS architectures use sensor fusion - combining RF, radar, EO/IR, and acoustic data into a correlated detection picture that reduces false positives and increases classification confidence. This is the approach Empyrean takes: multiple sensor types fused into a single operational picture where a detection is confirmed, classified, and tracked across sensor handoffs.
What is the difference between drone detection and drone mitigation?
Detection is the process of identifying that a drone is present, locating it, tracking its movement, classifying it (type, cooperative status, threat level), and documenting the event. Detection is broadly permissible for any organization - there are no federal laws prohibiting the use of cameras, radar, or passive RF monitoring to detect drones.
Mitigation is the process of neutralizing the drone threat - which may include jamming its control signal, spoofing its GPS to redirect it, taking control of it electronically, capturing it with a net or another drone, or using kinetic force (projectiles, directed energy) to disable or destroy it. Mitigation involves interfering with an aircraft in flight, which implicates federal criminal statutes and is restricted to authorized entities.
For private-sector facility operators, the line is clear: you can detect. You generally cannot mitigate. The SAFER SKIES Act extends mitigation authority to certified state and local law enforcement officers - not to facility security staff. Facility operators build value by making their detection data as complete and as fast to hand off as possible, so that the partners with mitigation authority can act effectively.
Is it legal to jam a drone?
For private citizens and most organizations, no. Jamming a drone involves transmitting a radio signal that interferes with the drone's control link or GPS receiver. This violates the Communications Act of 1934 (47 U.S.C. § 333), which prohibits the operation, marketing, or sale of jamming equipment. The FCC enforces this prohibition and has taken action against individuals and companies that use jammers.
Additionally, jamming a drone constitutes interfering with an aircraft in flight under 18 U.S.C. § 32, which carries criminal penalties. Jamming can also create collateral effects - disrupting legitimate communications, GPS signals, and other RF systems in the vicinity - which creates safety and liability risks.
The only entities currently authorized to jam drones are federal agencies (DHS, DOJ, DOD, DOE) operating under specific statutory authorities, and SLTT law enforcement officers who have been individually certified under the SAFER SKIES Act and are using federally approved technologies during authorized missions.
What is a Temporary Flight Restriction (TFR)?
A Temporary Flight Restriction (TFR) is an FAA-issued restriction that temporarily limits or prohibits flight operations within a defined area of airspace. TFRs are issued for presidential movements, major sporting events, disaster response areas, space launch operations, wildfire suppression, and other situations where unrestricted flight poses a safety or security risk.
For drone operators, TFRs are legally binding - flying a drone inside a TFR without authorization is a federal violation that can result in fines, certificate revocation, and criminal charges. For facility and event security teams, TFRs provide a legal framework but not a detection capability. The TFR establishes that unauthorized drones should not be present. Whether they actually are present - and what to do about it - depends on having detection systems that can identify non-compliant operations and response partners who can enforce the restriction.
What is the FEMA C-UAS Grant Program?
The FEMA Counter-Unmanned Aircraft Systems Grant Program was created by the One Big Beautiful Bill Act of 2025 and provides federal funding to state, local, tribal, and territorial governments to improve their ability to detect, identify, track, monitor, and mitigate threatening UAS activity. FEMA awarded an initial $250 million to the 11 states hosting 2026 FIFA World Cup matches and the National Capital Region - the fastest non-disaster award FEMA had ever made.
Eligible subrecipients include city and county agencies, law enforcement, fire services, EMS, emergency management, and other qualifying public safety organizations. Funds may be used for detection equipment, training, integration, and mitigation technologies operated by personnel trained at the FBI's National Counter-UAS Training Center. The grant program requires that all agencies using mitigation technologies ensure personnel are trained or scheduled for training, with FEMA verifying compliance.
For facility operators partnering with law enforcement on C-UAS, the FEMA grant program is directly relevant - your law enforcement partners may be eligible for funding to acquire detection and mitigation capabilities that complement your facility's sensor architecture.
Could private infrastructure operators get C-UAS authority in the future?
Possibly. On April 23, 2026, Sen. Tom Cotton introduced legislation that would extend limited counter-UAS authority to owners and operators of designated "covered critical infrastructure facilities" - including nuclear plants, key substations, and bulk-power system control centers. Under the proposed bill, trained security personnel at these facilities could take action against drones that pose a credible threat, including disruption, seizure, or destruction, using federally approved technology under DHS oversight.
The bill would authorize $250 million over five years for infrastructure operators to purchase and deploy approved counter-drone systems and would establish a DHS certification program for personnel. This legislation builds on the SAFER SKIES Act's framework but extends it beyond law enforcement to the private sector for the first time.
As of this writing, the bill has been introduced but not passed. Facility operators should monitor its progress - but regardless of legislative outcome, the detection, classification, and evidence documentation capabilities that Empyrean provides are the foundation that any future mitigation authority would require. You cannot mitigate what you cannot detect, and the quality of your detection data determines the effectiveness of any response - whether that response comes from law enforcement today or from your own certified personnel in the future.
How should facility security teams prepare for the SAFER SKIES Act?
The SAFER SKIES Act grants authority to law enforcement, not to facility operators. But facility operators can take steps now that will determine how effective that authority is when it is exercised at or near their facility.
First, deploy detection capability. You cannot hand off what you cannot see. RF detection, radar, camera analytics, and Remote ID reception provide the sensor layer that produces the tracks, classifications, and evidence packages that law enforcement needs to act. Without detection, the law enforcement partner arrives to a verbal report and a guess about which direction the drone went.
Second, establish the coordination relationship now. Identify your law enforcement liaison - local PD, sheriff's office, FBI field office - and discuss the operational model for drone incidents at your facility. Determine the communication channel, the data sharing mechanism, and the roles and responsibilities before the first incident. If your law enforcement partner is pursuing SAFER SKIES certification, ask how you can support their preparation by providing practice data, facility access for exercises, or shared training opportunities.
Third, build the federation architecture. Empyrean's TAK integration enables your detection data to reach your law enforcement partner's operational picture in real time. When the SAFER SKIES implementing regulations are finalized and your partner has certified officers with authorized technology, the value of that shared picture becomes immediate: the certified officer sees the drone track, the classification, and the engagement geometry on their TAK device - and can make the mitigation decision with full situational awareness.
The facilities that will benefit most from the SAFER SKIES Act are not the ones that wait for the regulations to be finalized. They are the ones that have detection capability, established law enforcement relationships, and a shared operational picture before the first incident that requires mitigation authority.
Related
- What is Counter-UAS? - full technical reference on sensors, effectors, and architecture
- The Ultimate Guide to Counter-UAS Operations - 18,000-word operational reference
- CUAS & Force Protection - Empyrean's counter-UAS capability
- Policy & Decision Automation - auditable engagement policy enforcement
- Federation & Multi-Agency Coordination FAQ - TAK federation and shared operational pictures
- Public Venues & Event Security - C-UAS for stadiums and live events
- Energy & Utilities - drone detection for substations and generation facilities
- Transportation & Logistics - C-UAS for airports and ports
