From the Public Safety edition of November 9, 2026
Flock Safety says Lompoc drones reach calls in 98.1 seconds on average and beat officers 61 percent of the time, in a vendor blog citing agency cases
Flock Safety (vendor), citing Lompoc, Aurora, Elk Grove, Pittsburg KS and Brookville NY police · Policing / drone as first responder and plate readers · United States (Lompoc, California and other cities)
- Publisher
- Flock Safety
- Original publication
- Flock Safety blog, Nov. 9, 2026
- Source retrieved
- 2026-11-10
What happened
A Flock Safety blog post says Lompoc, California used two roof-launched drones on 225 calls from Aug. 1 to Oct. 6, with a 98.1 second average response, drone arrival before officers 61 percent of the time and 144 subjects located. It says one in five calls in Elk Grove is resolved without dispatching patrol, and describes arrests after a school-area shooting in Aurora (about 18 minutes), a Pittsburg, Kansas incident (under an hour and 20 minutes) and a Brookville, New York crisis call (within 20 minutes), using plate reader and camera data. It cites a Lompoc public flight dashboard, audit controls and a unanimous two-year council trial approval, and says program settings and agency policy govern camera use during flight.
Why it matters
Gives claimed operating metrics for drone first responder programs that buyers will encounter, useful as hypotheses to test, alongside the independently measured trials already in the archive.
Evidence and measured results
Vendor marketing content; metrics are vendor-relayed agency statements without methodology, comparison group or independent verification.
Limitations and uncertainty
Marketing source; short window; selected success examples; metrics not independently verified; vendor interest in sales.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies are shown vendor performance numbers but lack independent evidence and a way to evaluate their own pilot.
- Stakeholders
- Police chief
- City manager
- City council
- Dispatch supervisor
- Privacy advocates
- Discovery questions
- What response metrics would convince the council?
- Is there a baseline period to compare against?
- Who owns flight logs and public reporting?
- Value hypothesis
- A pre-defined evaluation can turn vendor claims into local evidence; faster response or fewer dispatches are not promised.
- Potential engagement
- Pilot evaluation design and reporting package for a drone first responder trial.
- Unsupported claims
- That drones beat officers 61 percent of the time elsewhere
- That drones reduce patrol dispatches by 20 percent
- That the cited arrests were caused by the technology
Pre-sales engineering
Role takeaway
- Fit
- Metric definition and logging for a drone first responder pilot; not a vendor product comparison.
- Architecture and integration
- Link dispatch records, drone flight logs and plate reader alerts so response times are measurable.
- Prerequisites
- CAD export with call and arrival times
- Flight log export
- Baseline data for comparison period
- Constraints
- FAA and agency policy limits
- Vendor metrics lack stated method
- Short observation window
- Security
- Control live feed access, retention and sharing; review public dashboard contents.
- Proof of value
- Median call-to-arrival time versus baseline
- Share of calls resolved without patrol, verified in CAD
Delivery
Role takeaway
- Work
- Design the pilot evaluation, set reporting cadence and document policy for dispatch and data use.
- Dependencies
- Dispatch data access
- Council schedule
- Vendor flight log cooperation
- Ownership
- Police operations lead with an independent reviewer for results.
- Skills and adoption
- Train dispatchers and officers on dispatch triggers and logging.
- Governance checkpoints
- Pre-pilot metric sign-off
- Mid-trial public report
- Expansion decision review
- Acceptance criteria
- Metrics defined before launch
- Baseline and pilot data compared
- Public flight reporting in place
- Risks
- Selective reporting
- Metrics not comparable to vendor figures
- Privacy backlash
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Drone dispatch ties to 911 calls and plate reader alerts and streams video to responders; flight logs and a public dashboard are described as transparency features.
Governance
Who approves, reviews and stays accountable for outcomes?
Council trial approval, flight logs and a public dashboard are cited controls; policy on dispatch triggers and data use remains agency-defined.
Security and privacy
What data, permissions and controls need testing?
Vendor says settings, policy and transparency measures govern camera use in flight; residents raised privacy questions in Lompoc, per the post.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Vendor says drones free officers from some calls; staffing effects are claimed, not measured, and no workforce evidence is given.
Procurement
What should contracts, pricing and exit terms secure?
Buyers should require method, baseline and reporting rights for any performance figures in procurement; this is interpretation, as the post is marketing.
Operating model
Which teams own the service once it runs?
Drone dispatch, flight logging and a public dashboard imply new operating roles for dispatch and records staff; ownership is not described.
Publication history
- 2026-11-09Public Safety · Issue 643 resources
Stable resource ID: flock-safety-dfr-lpr-lompoc-98-seconds-vendor-claims-20261109