A Boston police drone fell out of the sky and onto a parked Mazda 3 at 11 Hatherly Road in Brighton around 1:30 p.m. on Thursday, September 3, smashing the rear windshield and trunk and leaving the aircraft in pieces in a private driveway. The car’s owner, a 42-year-old Brighton man, was not home. He came back to a wrecked car and a note from a Boston police officer on the windshield.

The crash came six days after the Boston Police Department announced its Drone as First Responder pilot with Motorola Solutions and BRINC, and less than a week after the first launch sites went live. BPD had sold the program on speed and safety. The Boston Herald broke the story on September 9, and the city’s largest police union used it to attack the entire program.

I have covered police drone crashes in New York and Kent since May 2025. This one has a detail the others didn’t: the department that flew the drone had, days earlier, promised to publish the program’s statistics. The first statistic that matters is now a crashed aircraft on a stranger’s car, and BPD has said nothing about it in public.

The Crash Report Says the Drone Was in Pieces on Arrival

The BPD incident report, quoted by the Boston Herald, says the responding officer found the drone in pieces in the driveway and that it appeared to have crashed onto a vehicle. BRINC, which builds the aircraft, collected the wreckage afterward. Neither BPD nor BRINC has said what brought it down.

The Herald’s account, which Hoodline and the Boston Institute for Nonprofit Journalism both relayed, is the only public record of the crash so far. The car was damaged at the rear windshield and trunk. The owner was not there. No injuries were reported. The Herald put the word “destroyed” in quotation marks in its own headline, and the Boston Police Patrolmen’s Association repeated it, so treat the extent of the damage as the union’s framing until a repair estimate surfaces.

The aircraft is a BRINC Responder. BRINC’s own spec sheet puts it at 7.7 pounds (3.5 kilograms) with 42 minutes of flight time, a 44 mph (71 km/h) top speed, a 40x zoom camera and a 640-pixel thermal imager. The sheet lists forward obstacle avoidance among the safety features. It does not list a parachute. Greg Reverdiau raised the parachute question in this week’s news update for DroneXL partner Pilot Institute, and it is still open: BRINC has not said whether the Boston aircraft carried one.

BPD Announced the Program on August 28 and Promised Statistics

The Boston Police Department announced the pilot on August 28 and said the rollout would begin that weekend. FAA-certified BPD pilots fly the drones. A drone launches within seconds of a 911 call or a ShotSpotter activation, and BPD said key statistics would be posted on BPDnews.com.

Commissioner Michael Cox framed the pitch around getting eyes on a scene faster than a cruiser can drive there. “By putting eyes on a scene in as little as a minute,” he said, dispatchers can send the right resources and officers can approach a dangerous call more safely. The release described privacy guardrails: cameras face the horizon in transit and tilt down only on arrival at the emergency location.

BPD’s news site has kept posting about its drones since. Its Drone Unit page leads with a September 18 release on a motorcycle enforcement sweep in Roxbury that the unit supported. As of September 19, sixteen days after the crash, the site carries nothing about Hatherly Road and none of the promised statistics.

The pilot had a good first few days. Hoodline reported on August 30 that a drone helped BPD find an armed suspect hiding in bushes during a foot chase in Roslindale. Four days later the Responder was in a Brighton driveway.

The Police Union Says It Wants Officers, Not Robots

The Boston Police Patrolmen’s Association turned the crash into a case against the program itself. Union president Larry Calderone told the Herald the drones are invasive surveillance, built in secret instead of hiring officers. The union’s X account headlined the story “BPD Drone Crashes and Burns in Brighton.”

Calderone’s quotes run in two directions at once. “We have a problem with Big Brother,” he told the Herald, before getting to the point the union actually cares about: the BPPA wants more bodies on the street and will not accept a drone in place of a community-policing officer. BINJ’s Chris Faraone, who has covered Boston police surveillance since the license-plate-reader fights of the early 2010s, read the same quotes and concluded the union’s objection is about headcount, not privacy.

Whatever the union’s motive, it does not explain the crash. A staffing dispute does not put a drone on a car. Something in the aircraft, the link, or the pilot’s decisions did, and that is the part nobody has addressed.

The FAA Reporting Clock Ran Out on September 13

Under 14 CFR 107.9, a remote pilot must report to the FAA within 10 calendar days a flight that damages property other than the drone, unless repair cost or value is $500 or less. A smashed Mazda 3 rear windshield clears that bar. That window closed on September 13.

The rule sits in Part 107, and BPD’s own release describes its pilots as FAA-certified, which points to Part 107 operations. Whether the department filed, and what it told the FAA about the cause, is not public. BPD has not said. Hoodline raised the same question on September 10 and had no answer either.

Boston has argued about drones over its streets before, with other people’s aircraft. In October 2024 a CNN-operated drone hit a light pole and fell into the crowd at a Celtics watch party on City Hall Plaza, injuring three people. Draganfly secured a rare FAA waiver in February 2025 to fly over people and moving traffic in the city for a Mass General Brigham delivery pilot. A police DFR fleet flying from fixed launch sites over residential streets is a different scale of exposure than either.

Police Drone Crashes Are Not New, But the Silence Is

New York’s police department has crashed two Skydio X10 drones in 13 months. The contrast with Boston is what happened next. When an NYPD X10 caught fire on the roof of the 71st Precinct in May 2025, Skydio CEO Adam Bry published the cause, a battery connector failure, within days.

When a second X10 fell and burned in DUMBO steps from the World Cup Fan Zone on June 23, the crash was public within days, down to photographs of the wreck from the Mayor’s Office photographer.

BRINC is not a small vendor that can plead inexperience. The company raised $125 million in July in a round led by Motorola Solutions, with the stated goal of a 911 drone on the roof of every one of the roughly 80,000 police and fire stations in the country. Boston is one of its highest-profile deployments. BRINC also sells the Responder on the claim that agencies clear roughly one call in four with the drone alone, a manufacturer figure DroneXL flagged as unaudited when Victorville bought its fleet in April.

DroneXL’s Take

I want Drone as First Responder programs to work. One that reaches a shooting scene in 70 seconds and tells responding officers what they are walking into is one of the best uses of this technology. DroneXL has followed BRINC rollouts in Plano and Reno. Boston should have one.

The union’s argument has a real foundation. BRINC’s own sales pitch is that a quarter of calls get cleared without sending an officer, and Commissioner Cox’s release says the drones will “outpace ground units.” A patrolmen’s union hearing that is not paranoid to conclude the drone is a headcount tool. But the union’s remedy, no drones, would have Boston’s officers arriving at unknown scenes blind, and the crash does not support it either way. A staffing fight is not a safety finding.

The safety finding is what is missing. My read is that BPD and BRINC know what happened to that Responder. BRINC collected the wreckage on September 3, its LiveOps software keeps flight logs, and the company has had 16 days. The NYPD-Skydio precedent shows the alternative: name the failure and say what changed. Skydio did that in May 2025 and came out of it with more credibility. BPD told Boston it would publish the pilot’s statistics. A crash onto a resident’s car in week one is the first one due.

The FAA filing is the simplest question. If BPD flew under Part 107, a report was due by September 13, and a department that launched a program on the word “safety” should be willing to say it filed. Watch two things: whether BPDnews.com ever posts the promised numbers, and what BPD puts in the next Annual Surveillance Report under Boston’s surveillance ordinance, which the Mayor’s office sends to the City Council every year with an account of how each surveillance tool was used, complaints included. A DFR program that cannot survive publishing its first crash was never going to survive a City Council hearing.

The Brighton man got a note on his windshield. Boston deserves a fuller one.

Sources: Boston Herald, Boston Police Department, Hoodline, Boston Institute for Nonprofit Journalism, BRINC, Legal Information Institute (14 CFR 107.9)

DroneXL uses automated tools to support research and source retrieval. All reporting and editorial perspectives are by Haye Kesteloo. Read our editorial standards.