Minneapolis Police ‘no-knock’ search warrant policy on city council agenda
[anvplayer video=”5087898″ station=”998122″]
After the Minneapolis Police Department fatally shot 22-year-old Amir Locke while serving a “no-knock” search warrant last week, a city council committee will have a hearing Monday afternoon to discuss MPD’s “no-knock” policy — and there will likely be some recommendations to fully ban such warrants.
University of St. Thomas law professor Rachel Moran told 5 EYEWITNESS NEWS she will address the city council committee to explain the current MPD “no-knock” policy and how it compares to other policies across the country. She expects to also offer her own recommendation.
“I think MPD should have a much more restrictive policy than they currently do,” Moran said. “I think most people, including me, would probably say there needs to be some exception, but much less exception than what we currently have because there is far too much discretion allowed with MPD’s current policies.”
RELATED: Minneapolis Mayor Frey announces moratorium on no-knock warrants
MPD’s current policy was updated in November 2020.
[anvplayer video=”5087844″ station=”998122″]
In an email, a city spokesperson said “MPD officers executing a ‘no-knock’ warrant have been required to announce their presence before crossing the threshold of a residence.”
A group called “Knock-First Minnesota” will also make recommendations Monday.
Sarah Murtada said her organization will push for a complete “no-knock” ban.
“We would like to see the MPD policy to require four things during a search warrant,” said Murtada. “First, we want them to knock on the door, then announce their presence, wait 30-seconds and if there is no reply then they could enter the residence and only if it is done during daylight hours.”
RELATED: Car caravan gathers to protest deadly police shooting of Amir Locke
Mayor Jacob Frey and civil rights attorneys Ben Crump and Jeff Storms are also expected to participate in Monday’s hearing, which begins at 1:30 p.m.
[anvplayer video=”5087814″ station=”998122″]