FAA B-TFAR — the Beyond Visual Line of Sight (BVLOS) Tribal Flight Approval Regulation, more precisely the broader Temporary Flight Restriction and Authorization Rule framework as it applies to armed and defensive UAS operations — is not a single document. It's a shorthand that practitioners use to describe the cluster of FAA regulatory requirements that govern any operation involving remotely-piloted aircraft that can affect national airspace, including counter-UAS kinetic systems.
If you're building or deploying a fixed-site kinetic counter-drone system in the United States, understanding which FAA authorities apply — and which don't — is not optional. Getting this wrong doesn't just create legal exposure; it creates operational exposure, because a deployment that hasn't secured the appropriate waivers and coordination may be shut down by the FAA or local ARTCC exactly when it's needed most.
What B-TFAR Actually Covers
Title 14 CFR Part 99 establishes the national security framework for airspace. Security TFRs (Temporary Flight Restrictions) under 14 CFR 99.7 can be established around critical facilities at the request of federal agencies — DHS, DoD, DOE — but they describe restrictions on incoming traffic, not authorization for defensive weapons fire.
The operational authorization question for a kinetic counter-UAS system is layered differently. A ground-based kinetic interceptor that fires a projectile through navigable airspace is not itself an aircraft — it doesn't require a Part 107 certificate or Part 91 operational approval. But the projectile passes through controlled airspace, and the deployment of armed defensive systems at a fixed site in or near civilian airspace requires coordination with the FAA under several regulatory hooks:
- Obstruction notification (14 CFR Part 77): Fixed structures above 200 feet AGL that could create hazards to air navigation require FAA notification and may require obstruction marking. A fixed weapon mount at ground level doesn't trigger this, but a mast-mounted detection radar above 200 feet does.
- Airspace coordination for engagement zones: Any defined engagement zone over which projectiles will be fired needs coordination with the controlling ARTCC or TRACON if the zone overlaps with navigable airspace. Navigable airspace begins at 500 feet AGL over populated areas, 1,000 feet over congested areas (14 CFR 91.119). Engagement geometries that keep engagement altitude below these thresholds significantly simplify the coordination burden — this is a real design constraint, not a theoretical one.
- Aeronautical hazard reporting: An engagement that produces airborne debris in navigable airspace is a reportable event to the FAA. Operators should have a post-engagement notification protocol established before first use, not improvised afterward.
The Counter-UAS Authority Framework: Who Can Do What
The counter-UAS legal authority framework in the United States is explicitly tiered. Understanding which tier applies to your situation is the first compliance question.
Under 49 U.S.C. § 44809 and the FAA Extension, Safety, and Security Act of 2016, followed by more extensive provisions in the FAA Reauthorization Act of 2018 (Section 1602) and its subsequent extensions, specific federal departments have explicit authority to detect, identify, monitor, track, interdict, and defeat UAS that pose a threat to their facilities or operations. Those departments are: the Department of Defense, the Department of Justice, the Department of Homeland Security, and the Department of Energy.
Critically, this authorization is department-specific — it does not extend to private operators, state or local law enforcement, or military contractors operating under commercial legal arrangements rather than DoD operational authority. A defense contractor maintaining a facility under a DoD contract does not inherit DoD's counter-UAS authority for that facility unless explicitly operating under a DoD operational order that brings the facility within the DoD authority umbrella.
We're not saying that private operators have no counter-UAS options — they do, within limits. We're saying that the authority framework the federal government uses doesn't automatically extend to the private sector, and operators who assume it does are operating on incorrect legal footing.
What Kinetic Systems Specifically Need to Address
Electronic warfare and RF jamming are explicitly regulated under FCC authority (47 U.S.C. § 333) and the counter-UAS authorizations discussed above. Kinetic defeat systems sit in a different regulatory space — they're not radio communications devices — but they face a distinct set of requirements.
ATF Classification
Depending on the projectile type, a kinetic counter-drone interceptor may be classified as a destructive device under 26 U.S.C. § 5845 (the National Firearms Act) or as a firearm under 18 U.S.C. § 921. Systems that use explosive warheads, multi-projectile payloads (effectively shotgun-type charges), or projectiles over 0.50 caliber bore require NFA registration as a destructive device, which entails ATF Form 1 or Form 4 processing, a $200 tax stamp per unit, and CLEO (Chief Law Enforcement Officer) notification in most jurisdictions.
Systems designed to use non-explosive kinetic intercept — essentially a high-speed projectile sized below the destructive device threshold — can avoid NFA classification but still require compliance with state and local laws governing firearms discharge in the deployment area. An outdoor test range in rural Alabama has different discharge laws than a rooftop deployment at an urban power substation.
NDAA Section 1281 and DoD Coordination
Section 1281 of the FY2017 NDAA directed the DoD to develop a counter-UAS strategy. Subsequent NDAAs through FY2024 have progressively built out the DoD's authorities and procurement pathways, including the Joint Counter-small Unmanned Aircraft Systems Office (JCO) standing up approved system lists and operational guidance. Systems that want to be considered for DoD procurements — including direct-sell to installations — need to engage with the JCO approval pathway, which involves a technical evaluation process distinct from commercial product certification.
ARES-1's development roadmap includes engagement with the JCO evaluation process. We're designing the system architecture to be compliant with relevant MIL-STDs from the start, specifically MIL-STD-810 for environmental qualification and MIL-STD-461 for electromagnetic compatibility — not as an afterthought before a procurement bid, but because a system that doesn't meet those standards isn't a viable military product regardless of how good the intercept geometry is.
Site-Specific Coordination Checklist
For a fixed-site deployment of a kinetic counter-UAS system at a critical infrastructure location, the compliance coordination required before operational deployment includes:
- FAA coordination: Notify the local ARTCC of the intended engagement zone and maximum engagement altitude. If the site is within a Class D, C, or B airspace zone, or near an approach corridor, expect a formal Letter of Agreement process that may take 60-90 days. Engagement zones that remain below 400 feet AGL and outside approach corridors are significantly simpler to coordinate.
- ATF classification determination: Submit an ATF Form 1 classification request for the specific interceptor design before procurement. Don't assume your legal counsel's read on the NFA definition is correct — ATF classification letters are the authoritative source, and classification requests are processed as administrative matters outside the procurement timeline.
- State discharge authority: Confirm state law on discharging projectile weapons for defense of property, including any local ordinances in the jurisdiction. This varies significantly — Texas, for example, has explicit statutory protections for property defense that most other states do not.
- TTIC/DHS notification: For critical infrastructure operators in DHS-designated critical infrastructure sectors (energy, water, communications, transportation), notifying the appropriate sector-specific agency and the Terrorist Threat Integration Center of a defensive deployment is both a coordination best practice and may be required under sector-specific security plans.
- Post-engagement reporting protocol: Establish in advance: what gets reported, to whom, within what timeframe, following any kinetic engagement. FAA, local law enforcement, facility insurance carrier, and sector-specific federal agency are likely all on the notification list.
The Path Forward for Private Operators
The current regulatory framework creates a meaningful gap: private critical infrastructure operators face real drone threats but have limited legal authority to respond with the most effective defeat mechanisms. That gap is recognized in Congress and within the FAA, and the regulatory environment is moving — slowly — toward expanding private operator authorities through delegation and coordination mechanisms.
The practical approach for private operators today is to establish the detection and characterization capability — which faces essentially no legal barrier — and to pre-coordinate the response framework with federal partners who hold the relevant authority. A private utility company that has established a threat-sharing relationship with DHS CISA and a coordination protocol with their regional FBI field office is in a substantially better position to get rapid federal response authorization when a threat materializes than one that is trying to establish those relationships during an active incident.
None of this is quick. Regulatory coordination timelines are measured in months. For operators who haven't started the compliance work, the time to start is now, before the threat event that forces improvisation. ARES-1's deployment support package includes coordination with legal counsel experienced in counter-UAS regulatory matters specifically because we've found that the compliance pathway, not the hardware, is typically the longer lead item in a fixed-site deployment.