Major international events force a hard choice for public-safety planners. The 2026 FIFA World Cup will concentrate crowds, transport hubs and civic ceremonies into predictable windows and locations that are attractive targets for malicious unmanned aircraft systems. Federal directives and grant guidance this year have made clear that the executive and legislative branches expect state and local partners to move quickly on detection, identification and mitigation tools.

Local and state public-safety groups have also sent a clear message: detection without mitigation authority leaves responders exposed and helpless during an incident. That lobbying has pushed Congress to act on counter-UAS authorities and to consider broader reauthorization and standards.

All of that creates a plausible planning scenario where a concentrated federal investment in counter-drone capabilities for World Cup host cities is on the table. Whether that pot is $50 million, $115 million or something else, the operational problem set looks the same. Here is a practical, risk-oriented blueprint for how to spend a hypothetical $115 million so the money increases safety, is legally defensible, and leaves usable capability behind after the tournament.

Priority rules before line-item spending

  • Treat C-UAS as a dual problem of detection and lawful mitigation. Grants and federal guidance already accept detection systems as allowable purchases but require legal consultation and SOPs before mitigation tools are used. Build legal review and SOP development into the budget up front.
  • Favor multi-sensor fusion, not single-sensor black boxes. Radar, RF signature monitoring, and electro-optical/infrared cameras feed complementary classification data. Sensor fusion reduces false positives and the likelihood of onerous kinetic responses in urban environments. Use open interfaces and common data models so cities can integrate future sensors without locked vendor systems.
  • Prioritize people and processes over gadgets. A detection network without trained operators, secure comms and an operational playbook will create noisy alerts and liability. Training, exercises and an accredited certification path must be funded alongside hardware.

Recommended allocation (example that totals $115M)

1) Multi-sensor detection network and backhaul integration: $35M

  • Deploy portable and fixed radars, RF direction-finding and EO/IR towers around primary stadiums, transit hubs and critical intermodal nodes. Fund edge compute and secure fiber or hardened wireless backhaul. These purchases are explicitly allowed under current FEMA guidance for preparedness grants when coupled with legal and policy work.

2) Identification/classification and command-and-control software: $18M

  • Purchase or develop sensor-fusion middleware with auditable logs, role-based access, and the ability to ingest third-party feeds. Allocate money for independent performance testing and acceptance criteria so systems meet institutional needs rather than vendor marketing claims.

3) Lawful mitigation capability and rules-of-engagement workstream: $20M

  • Rather than defaulting to kinetic interceptors, fund graduated mitigation tech such as RF jamming under vetted legal authority, capture nets launched from intercept drones in controlled airspace, and remedial options for recovery of downed UAS debris. Budget legal counsel, SOP creation, public notice requirements and an independent oversight mechanism. FEMA guidance and pending legislation both stress the need for legal guardrails and training before active mitigation.

4) Training, exercises and accreditation: $10M

  • Train operators on detection-to-decision timelines, evidence preservation, interagency coordination, and public communications. Fund tabletop and full-scale exercises with stadium operators, transit authorities, and neighboring jurisdictions.

5) Interoperable command centers and secure comms: $12M

  • Stand up regional C2 capability with encrypted links to local EOCs and federal partners, data retention systems for forensic review, and integration pathways to aviation authorities.

6) Grants to local subrecipients and sustainment fund: $10M

  • Ensure at least some funding flows to local public-safety agencies for maintenance, consumables, and local pre-positioning of assets.

7) Transparency, privacy safeguards and community engagement: $5M

  • Contracts for third-party privacy impact assessments, community notices, and an independent audit mechanism to review deployments and civil liberties impact.

8) Rapid prototyping and industry engagement (small awards): $5M

  • Seed small, competitive trials for open-source or locally developed detection and classification tools. Prize-style pilots generate competition and can surface lower-cost alternatives. European agencies have used prize contests to accelerate novel C-UAS ideas and this model can help the public sector avoid vendor lock.

Why this split works

  • It balances detection and mitigation while protecting rights. Many operational failures in previous C-UAS rollouts came because agencies bought mitigation tools without legal SOPs or interoperability. Funding legal and oversight work up front reduces operational risk and future liability.
  • It builds sustainability. A recurring problem with grant-driven procurement is the lack of sustainment dollars. A modest dedicated sustainment line and local pass-throughs keep systems live after the event.
  • It buys capacity, not vendor showpieces. Modular, standards-based systems are cheaper to maintain and easier to adapt to future threats.

Implementation steps and red flags

1) Legal and policy gates before mitigation deployment. Any plan that spends heavily on active mitigation must budget for immediate legal reviews and signed SOPs. FEMA guidance and current legislative proposals emphasize this point. 2) Require third-party performance testing. Do not accept vendor claims without third-party verification of detection range, false positive rate, and classification accuracy in dense urban RF environments. 3) Avoid mass-surveillance creep. If systems can collect personally identifiable information, require minimization and retention controls and public reporting on incidents and mitigations. 4) Train on forensics. Preserve chain of custody for any interdicted UAS and record operator decisions across the detection-to-mitigation timeline. 5) Prioritize interoperability with aviation authorities. Stadium airspace sits within a broader national airspace. Any local mitigation must coordinate with the FAA and equivalent aviation authorities so mitigation actions do not endanger Manned aircraft.

Metrics that show success

  • Time from detection to positive identification under 90 seconds for Class 2 and 3 UAS within stadium footprint.
  • False positive rate below an agreed threshold during full-scale exercises.
  • Number of incidents successfully contained without collateral damage.
  • Percent of sustainment dollars allocated to local partners within 90 days of award.

Conclusion

A one-off headline number does not guarantee safer skies. Dollars must flow into legal, operational and sustainment pieces as much as into hardware. If planners shape a $115 million program around fusion sensing, legal guardrails, trained operators, and sustainable maintenance, host cities will finish the tournament with lasting capability and far less operational risk. If the money buys unproven hard-kill toys and little training, it will be expensive theater with real legal and safety downsides. The choice is not technological; it is programmatic and ethical. The work to get both right is already underway in executive guidance and congressional activity. Public-safety leaders should use the next months to insist on measurable outcomes, independent testing, and community safeguards before systems go live.