Restricted airspace is a rule that can't see
Drone incursions over crowded public events keep happening because enforcement depends on detection that isn't there. No-fly zones are policy without sensing.
The call, up front. Unauthorized drones over stadiums and public gatherings — including World Cup festivities — are not a regulation problem. The no-fly zones exist. The gap is detection-and-identification: today’s geofencing and spotters can’t reliably tell an authorized low-altitude asset from a malicious one, fast enough to act.
The gap
Geofencing trusts the drone to police itself. Visual spotters don’t scale to a stadium. Radio-frequency monitoring is coarse. The binding constraint is the middle link — real-time identification that distinguishes friend from threat with low enough latency for an interception decision.
Source: GAPTIQ engine — challenge definition; restricted-airspace incident reporting
The opportunity is the detect-and-identify layer that closes inter-agency latency — not another rule or another geofence.
- NowHigh-profile incursions over crowded public events
- NextMandatory remote-ID enforcement gains teeth
- ThenCounter-UAS detection becomes standard event infrastructure
Source: Drone flown over World Cup festivities — TorontoToday, Jun 2026
So what
The buyer is the event operator and the city, not the regulator. Sell the sensing layer that makes an existing rule enforceable — detection, identification, and a single decision feed across agencies — before the next headline incident forces it.
Source: This is what happens if you fly a drone over World Cup festivities, TorontoToday. Surfaced by the GAPTIQ engine.