From the Public Safety edition of November 5, 2026
WRAL cites Mourtgos randomized DFR trial: about two minutes faster first arrival; Montgomery County resolved ~127 drone-only calls (~20%), Philadelphia 72% without patrol
University of South Carolina research team (Mourtgos) / WRAL Investigates · Policing / drone-as-first-responder evaluation · Montgomery County, Maryland and Philadelphia, Pennsylvania (study sites); North Carolina agencies adopting DFR
- Publisher
- WRAL Investigates
- Original publication
- WRAL.com, updated Nov. 4, 2026
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-03
What happened
WRAL Investigates reported on Nov. 3–4, 2026 on North Carolina agencies adopting drone-as-first-responder programs and interviewed Scott Mourtgos about a five-month randomized control trial at Montgomery County Police (Maryland) and Philadelphia Police, described as the first RCT of DFR effectiveness. Mourtgos said first arrival was about two minutes faster than a typical call, with the largest gains on Priority 2 calls. About 127 Montgomery County calls were resolved by the drone alone with no in-person response (~20% of drone-attended calls there); Philadelphia resolved 72% of drone-attended calls without a patrol response. Even calls the drone did not attend got faster inside the service area as workload fell. Drones typically cover a one-to-two-mile radius. Mourtgos called the research preliminary; use-of-force and full resolution-time analyses were still underway. Durham and Fayetteville have approved DFR; Raleigh is gathering information.
Why it matters
Rare measured DFR evidence agencies can cite—or caveat—when justifying docked drones, contrasting with proposals that lack outcome data.
Evidence and measured results
Opened and read the full WRAL article. The underlying RCT paper or dataset was not opened; figures are as stated by the researcher to WRAL and labeled preliminary.
Limitations and uncertainty
Secondary news interview; RCT details and peer-review status not verified from a paper; Philadelphia and Montgomery results may not transfer; use-of-force outcomes pending.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; 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 need measured proof DFR improves 911 response.
- Stakeholders
- Police chief
- City council
- Dispatchers
- Researchers
- Discovery questions
- What is our Priority 2 volume?
- How many docks for coverage?
- What will we measure?
- Value hypothesis
- Dense docks may cut arrival time and car responses if local metrics match the RCT.
- Potential engagement
- DFR evaluation design and dock-coverage plan.
- Unsupported claims
- Peer-reviewed final results
- Use-of-force reduction
- Universal transferability
Pre-sales engineering
Role takeaway
- Fit
- Relevant to agencies designing DFR dock networks.
- Architecture and integration
- Docks, CAD priority rules and RTCC video tied to dispatch.
- Prerequisites
- CAD integration
- Dock sites
- Measurement plan
- Constraints
- 1–2 mile radius
- Airspace
- Weather
- Security
- Control who views live feeds; log drone-only closures.
- Proof of value
- First-arrival delta
- Drone-only rate
- Spillover on non-drone calls
Delivery
Role takeaway
- Work
- Run a timed pilot and publish results.
- Dependencies
- Analytics partner
- Dispatch
- Vendor
- Ownership
- Operations deputy.
- Skills and adoption
- Dispatchers and pilots need shared closure rules.
- Governance checkpoints
- Baseline
- Mid-trial review
- Go/no-go
- Acceptance criteria
- Metrics published
- Rules written
- Coverage mapped
- Risks
- Sparse docks
- Overclaiming
- Policy gaps on drone-only
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?
Dock placement must cover enough one-to-two-mile radii to realize citywide benefits; sparse docks underdeliver.
Governance
Who approves, reviews and stays accountable for outcomes?
Agencies should demand RCT-style or at least pre/post metrics before scaling DFR budgets.
Security and privacy
What data, permissions and controls need testing?
High drone-only resolution rates increase reliance on aerial observation without an officer on scene.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
DFR is framed as a staffing workaround; benefits depend on covering enough geography.
Procurement
What should contracts, pricing and exit terms secure?
Buyers should size dock density to the one-to-two-mile limit rather than buying a token fleet.
Operating model
Which teams own the service once it runs?
Priority 2 triage and drone-only closures change dispatch workload; policies must define when a car is still required.
Publication history
- 2026-11-05Public Safety · Issue 605 resources
Stable resource ID: wral-mourtgos-dfr-randomized-trial-two-minute-faster-drone-resolved-calls-20261105