Page:Investigation of the Ferguson Police Department.djvu/25

From Wikisource
Jump to navigation Jump to search
This page has been validated.

person for Failure to Comply. The officer thus acknowledged that he regularly exceeds his authority under the Fourth Amendment by arresting passengers who refuse, as is their right, to provide identification. See Hiibel, 542 U.S. at 188 ("[A]n officer may not arrest a suspect for failure to identify himself if the request for identification is not reasonably related to the circumstances justifying the stop."); Stufflebeam v. Harris, 521 F.3d 884, 887–88 (8th Cir. 2008) (holding that the arrest of a passenger for failure to identify himself during a traffic stop violated the Fourth Amendment where the passenger was not suspected of other criminal activity and his identification was not needed for officer safety). Further, the officer told us that he was trained to arrest for this violation.

Good supervision would correct improper arrests by an officer before they became routine. But in Ferguson, the same dynamics that lead officers to make unlawful stops and arrests cause supervisors to conduct only perfunctory review of officers' actions—when they conduct any review at all. FPD supervisors are more concerned with the number of citations and arrests officers produce than whether those citations and arrests are lawful or promote public safety. Internal communications among command staff reveal that FPD for years has failed to ensure even that officers write their reports and first-line supervisors approve them. In 2010, a senior police official complained to supervisors that every week reports go unwritten, and hundreds of reports remain unapproved. "It is time for you to hold your officers accountable," he urged them. In 2014, the official had the same complaint, remarking on 600 reports that had not been approved over a six-month period. Another supervisor remarked that coding errors in the new records management system is set up "to hide, do away with, or just forget reports," creating a heavy administrative burden for supervisors who discover incomplete reports months after they are created. In practice, not all arrests are given incident numbers, meaning supervisors may never know to review them. These systemic deficiencies in oversight are consistent with an approach to law enforcement in which productivity and revenue generation, rather than lawful policing, are the priority. Thus, even as commanders exhort line supervisors to more closely supervise officer activity, they perpetuate the dynamics that discourage meaningful supervision.

      1. FPD's Use of a Police-run "Wanted" System Circumvents Judicial Review and Poses the Risk of Abuse

FPD and other law enforcement agencies in St. Louis County use a system of "wanteds" or "stop orders" as a substitute for seeking judicial approval for an arrest warrant. When officers believe a person has committed a crime but are not able to immediately locate that person, they can enter a "wanted" into the statewide law enforcement database, indicating to all other law enforcement agencies that the person should be arrested if located. While wanteds are supposed to be based on probable cause, see FPD General Order 424.01, they operate as an end-run around the judicial system. Instead of swearing out a warrant and seeking judicial authorization from a neutral and detached magistrate, officers make the probable cause determination themselves and circumvent the courts. Officers use wanteds for serious state-level crimes and minor code violations alike, including traffic offenses.

FPD command staff express support for the wanted system, extolling the benefits of being able to immediately designate a person for detention. But this expedience carries constitutional risks. If officers enter wanteds into the system on less than probable cause, then

22