Cambridge committee sends police drone request back to full council after hours of debate

The Cambridge Public Safety Committee voted 4–0, with one member absent, to send the city manager's Surveillance Technology Impact Report (STIR) and the Cambridge Police Department's request to use remotely piloted aerial vehicles back to the full City Council after an hours‑long hearing filled with public comment and council questions.

The hearing featured a string of public speakers both for and against the department's request. Supporters including Lan Gilboa and Ori Perot said drones would aid search‑and‑rescue operations, crowd and traffic monitoring and officer safety. Opponents, including Alex Matthews of Digital Fourth and Kate Crawford of the ACLU of Massachusetts, urged caution and asked the council to withhold approval until a binding policy addressing privacy, retention and restrictions is available.

"If you approve the technology, then it is approved forever without any restrictions on its use," Alex Matthews said, arguing the STIR presents nonbinding suggestions rather than an enforceable policy.

Cambridge Police Commissioner Christine Elo said the department's goal is to "harness drone technology strictly as a safety and operational tool while maintaining rigorous safeguards to protect our privacy and civil liberties." Elo told the committee the drones would fly up to 400 feet, would not be weaponized, would not capture audio, and "do not record unless you press the record button." She said documented recordings would be linked to police reports and that the department would incorporate public feedback into a written policy.

Detective Kristy Casenza, a special response team member and licensed FAA drone pilot, described real‑world incidents in which aerial imagery or thermal sensors could have shortened searches or lowered risk to officers, including a barricaded subject and a missing person who was later found on a roof.

The ACLU's Kate Crawford countered that the surveillance ordinance and prior deliberations intended to give the council authority to "claw back" approvals if problems emerged. "It was, in fact, the explicit intention that the council would have the authority to claw back any surveillance technologies that were approved," she said, and urged that a final policy be in hand before any authorization is granted.

Councilors asked detailed operational and legal questions: who would decide when to hit the camera's record button (CPD said the pilot/operator would), whether federal agencies could compel access to footage (legal staff and ACLU representatives noted that court orders could require disclosure in specific cases), and how the council could later revoke or amend approval under the surveillance ordinance (the city solicitor said the ordinance does not explicitly provide for revocation of a STIR approval and that she'd need to provide further legal analysis).

Council members also pressed for empirical evaluation. Kate Crawford noted peer‑reviewed studies that show limited evidence that passive surveillance systems deter serious crime, and the committee discussed building in reporting and review requirements to assess whether drones deliver measurable public‑safety benefits.

The committee recorded equipment and cost estimates during the hearing: CPD staff gave a per‑unit range of roughly $10,000–$12,000 for outdoor drones and $1,000–$1,200 for smaller indoor models, and estimated a conservative equipment outlay in the neighborhood of $20,000 when cases, batteries and data storage are included.

After the exchange of questions and public testimony, Councilor Wilson moved to refer the STIR and the police department's RPA request back to the full City Council so the commissioner and the city solicitor can return with a policy (or a draft policy) and legal clarifications. The clerk recorded four yes votes and one absence on the referral. A subsequent motion to adjourn carried on the same roll‑call tally.

Next steps: the committee expects CPD and the city solicitor's office to work with community stakeholders, including the ACLU and civil‑liberties groups, to draft or finalize policy language and return the matter to full council for a vote. The committee did not adopt any operational approvals at the hearing.

(Reporting note: all quotes and attributions are drawn from the committee hearing transcript.)