Read the framework as conditions, not blanket permission
The interim final rule published July 6, 2026 addresses eligible SLTT law-enforcement and correctional agencies. Its framework includes certification, authorized technologies, spectrum and airspace coordination, operational planning, reporting and privacy. Detection-and-warning and mitigation are distinct categories; meeting requirements for one does not establish authority for the other.
The rule does not eliminate every legal question about a particular operator, system, site or activity. The correct starting point is a documented determination of what the agency and its personnel may do under the applicable provisions.
Treat the mission as an operating discipline
An agency must connect detection, assessment, escalation and lawful response. Sensors can generate alerts, but people need to determine what the alert means, who should be notified and which response is permitted. A display that detects an object without a staffed and authorized decision path is not a complete protective service.
The environment also matters. A stadium, correctional facility and mixed urban area have different operational constraints. Aviation and communications coordination should be built into planning rather than added after a purchase. Section 124.9(i) of the rule distinguishes passive, non-RF-emitting detection systems with no effect on aviation safety: those uses do not require the same per-operation advance FAA/FCC coordination, although applicable law and other requirements still apply. The rule's specific requirements must be checked for the proposed operation; agencies should not infer that a neighboring jurisdiction's approval transfers to them.
Procurement should reflect the approved mission and safety constraints, with qualified personnel reviewing technical suitability.
Prevent procurement from outrunning governance
Buying a system after a high-profile incident can feel like progress. Before committing, define who owns alerts, who can authorize action, how operators maintain qualifications and how records are reviewed. Vendor demonstrations should be evaluated against the agency's approved use and environment, rather than treated as proof of permission to operate.
- People: accountable leadership, qualified operators, backups and continuing training.
- Process: operational approval, coordination, escalation, reporting and incident review.
- Technology: systems suitable for the authorized scope, with maintainable integrations and support.
- Information: controlled access, privacy protections, retention and a usable audit trail.
Those elements need a recurring budget. A purchase price excludes exercises, maintenance, operator time, updates and compliance work. An agency that cannot fund the operating model should consider a narrower mission or a shared arrangement before acquiring a standalone system.
Consider regional capability without blurring responsibility
A state-coordinated or regional program may share expertise, planning support and approved infrastructure. The whole-of-state cybersecurity model offers an analogy for pooling scarce resources, not proof that the same arrangement is automatically lawful or effective for counter-UAS.
Mutual-aid agreements should identify which entity provides personnel and equipment, who approves an operation and which entity handles records and reporting. Participation does not erase each agency's responsibilities or create authority it otherwise lacks. Test the arrangement in a planning exercise before an event creates pressure to improvise.
Regional coordination can also make lessons easier to compare. Record alert handling, coordination delays, operator availability and compliance issues in a consistent form. Use that evidence to improve the program, while respecting the rule's restrictions on collected information and unrelated uses.
Decide who will operate the capability
The service model affects more than price. Under section 124.4 of the interim rule, an accredited SLTT agency can provide support to a non-accredited host agency under the applicable conditions. The qualified provider retains operational authority for the covered activity. A host's request for help does not make its own personnel qualified to operate the system.
The same section distinguishes contractor support from operational decisions. Contractors may assist with functions such as maintenance and training; they cannot operate mitigation capabilities or make credible-threat determinations. A proposal to supply equipment, technical support and event staffing therefore needs to identify who will perform each role and under what authority. The vendor's availability cannot cure a missing qualified government operator.
These boundaries make a regional service worth evaluating for an agency with occasional demand. It can reduce the burden of maintaining a standalone capability, but introduces availability and travel constraints. Establish how competing requests are prioritized and what the host does when the provider cannot support the event. A memorandum that promises cooperation without addressing those constraints is not a dependable service commitment.
Use a missing-operator exercise before committing funds
Take a hypothetical public event for which an agency is considering counter-UAS support. During a planning exercise, remove the proposed lead operator from the roster. Ask the team to demonstrate the authorized replacement, required coordination, approved system and reporting responsibilities. Do not fill the vacancy with a contractor or an unqualified employee simply because that person knows the equipment.
If the exercise cannot establish a lawful, qualified operating team, the decision is to change the support arrangement, narrow the proposed mission or defer that capability. The broader event protection plan still needs accountable staffing and coordination. A counter-UAS acquisition should not consume resources on the assumption that authority and people will arrive later.
Then follow the information the proposed service would collect. Identify who can access it, what approved purpose it serves, how long it may be retained and how a disclosure or improper use would be handled under the applicable rules. Recordkeeping should support oversight without treating every observed flight as evidence of wrongdoing. The exercise can expose a gap between a vendor's default data practices and the agency's permitted use before live collection begins.
For acquisition acceptance, require evidence of the operating arrangement as well as the equipment's suitability: qualified coverage, documented provider and host responsibilities, the required approvals, support availability and a workable records process. These are recommended acceptance questions. The rule and the facts of the proposed operation determine the actual legal conditions; a completed purchasing checklist does not itself grant authority.
A readiness sequence before acquisition
- Establish scope and authority. Have qualified legal and operational staff identify applicable eligibility, personnel and operation requirements from the current rule.
- Define the protective mission. Document the location, service need, operating limits and relationships with other responsible organizations.
- Build the coordination plan. Assign contacts, approval responsibilities, communications and reporting tasks; verify required federal coordination.
- Evaluate suitable systems. Confirm the relevant authorization status and limitations, then assess integration, support and total operating cost.
- Exercise the complete process. Test notification, escalation, records handling and staffing continuity in a controlled planning exercise.
- Authorize only supported capability. Resolve gaps before operational use and review material changes to personnel, systems or mission.
Sources and further reading
- Federal counter-UAS interim final rule — effective date, agency scope, certification and operational conditions. The planning sequence above is our implementation analysis; it does not replace the rule.
Spartan X's engineering, cybersecurity and program-execution capabilities address the integration work around a mission: requirements, system boundaries, accountable operations and sustainment. Those pieces need to fit before equipment becomes a dependable service.
