DRAFT REPORT OF THE CITY OF SPOKANE USE ... - Samuel Walker

DRAFT REPORT OF THE CITY OF SPOKANE USE ... - Samuel Walker DRAFT REPORT OF THE CITY OF SPOKANE USE ... - Samuel Walker

spokanepolice.org
from spokanepolice.org More from this publisher
21.07.2014 Views

City of Spokane Use of Force Commission December 20, 2012 was done notwithstanding that the officers arrived on the scene at different times during the encounter with the subject, from different directions, witnessed different behavior by the subject, and offered various specific justifications for their individual use of deadly force. Id. A far better result would be for the ARP to carry out an exacting force analysis of each officer’s actions and compare such to the department’s training and policy expectations and requirements. Id. at 7 & 16. A DFRB was also convened to review the November 2010 deadly force incident. Two issues that go directly to public and officer safety that were identified by Mr. Gennaco in connection with that review were the consideration of the twenty-four rounds fired by the officers (out of twenty-six total rounds) that failed to strike the subject and the existence of a cross-fire situation in the encounter. Exhibit D at 9-10. In regards to the expended rounds, Mr. Gennaco recommends that the DFRB examine each officer’s use of deadly force individually and arrive at an assessment of whether the officer was tactically sound and proficient when he discharged his weapon. Id. at 9 & 16. Similarly, Mr. Gennaco considered the DFRB’s review of the cross-fire issue to be incomplete due to its failure to sufficiently explore the question based upon the placement and actions of all of the officers involved in the incident. Id. at 10 & 16. Recognizing that a single instance does not necessarily represent a consistent pattern, the Commission nevertheless calls for the SPD to reflect upon Mr. Gennaco’s findings and to ensure that DFRBs always thoroughly explore deadly force encounters for lessons learned that will enhance public and officer safety. Recommendation #17 – Create and deploy a fully developed Early Intervention System. Operating under the premise that small issues will lead to big problems if left unattended, an Early Intervention System (EIS) is a valuable administrative tool that can enhance accountability and integrity in a law enforcement agency. An EIS is a databased management tool designed to identify officers whose behavior is problematic and to spur intervention to correct that performance before the situation escalates into a formal disciplinary action or worse. A department’s EIS must be part of its larger efforts to support and improve officer performance. Frontline supervisors are key actors in the use of an EIS, but the Chief of Police and his command staff must be committed to the full deployment of the system. The information collected as part of an EIS can be as expansive as a department desires. Of particular relevance to the issue of the use of force, an EIS should track all reported uses of force, searches and seizures, number of arrests, and any civilian or internal complaints, civil suits, or criminal charges regarding the use of force. Additionally, recognizing that aberrant behavior in a multitude of performance areas can be a precursor to a use of force problem, an EIS system should capture other information that could identify outliers in the department. This could include, for example, such things as unusual numbers of pedestrian stops, the failure to meet training obligations, disciplinary actions, negative performance evaluations, and any City of Spokane Use of Force Commission – Page 23

City of Spokane Use of Force Commission December 20, 2012 civilian or internal complaints, civil suits, or criminal charges against an officer for matters other than the use of force. It is important to make sure that EIS thresholds are set at an appropriate level so as to initiate relevant and effective intervention (i.e., not so high that intervention never occurs or occurs too late). For example, recognizing that the officers who are of particular concern are indeed the outliers on the force, thresholds for triggering intervention can be set to capture approximately 3-5% of the line officer population. Additionally, the criteria for the system should take into account the need to create single-event thresholds for occurrences that are so critical that they require immediate department intervention and should implement rolling thresholds, thereby ensuring that an officer who has received an intervention is not permitted to engage in the initial threshold number of additional events before again triggering the EIS. Finally, the structure of the system must ensure that interventions follow close in time to the actual triggering event. Once the EIS is triggered for an officer, it is critical that the supervisor conduct a thorough review, take appropriate action, and be diligent in tracking resolution. The supervisor should review any triggering event in its entirety and prescribe appropriate resolutions or training opportunities specifically targeted to the behavior that prompted the intervention. At a minimum, supervisors should be required to review the EIS files on each subordinate every two months and a response by a supervisor should be required within two weeks of detecting a red flag. Thereafter, the supervisor should check the EIS on that officer every month for twelve months to determine if the response has satisfactorily resolved the issue. In each instance of a red flag, the supervisor should document what action was taken and document the event in at least the subject officer’s next performance evaluation and the officer’s next promotion recommendation. Ideally, a regular audit of the system would be conducted to make sure that it is being optimally deployed. Recommendation #18 – Equip officers with body cameras. Providing officers with body cameras will preserve important evidence of the circumstances surrounding encounters between the SPD and citizens. Although no recording can be a perfect record of the totality of an event, body cameras will help SPD officers gather evidence, improve the quality of their reports, and protect them from false citizen complaints, and they will provide valuable evidence when the circumstances of an encounter are called into question by any source. Recommendation #19 – Explore standardizing the weapons carried by officers in the line of duty. The Commission is aware that there is variation in the types of weapons that SPD officers are allowed to carry. For example, officers are allowed, with permission, to carry non-standard firearms or batons. While some have expressed a concern about this practice, the Commission is not in a position to state that it should be continued or disbanded. Rather, the Commission recommends that the Chief of Police review the City of Spokane Use of Force Commission – Page 24

City of Spokane Use of Force Commission December 20, 2012<br />

was done notwithstanding that the officers arrived on the scene at different times during<br />

the encounter with the subject, from different directions, witnessed different behavior by<br />

the subject, and offered various specific justifications for their individual use of deadly<br />

force. Id. A far better result would be for the ARP to carry out an exacting force analysis<br />

of each officer’s actions and compare such to the department’s training and policy<br />

expectations and requirements. Id. at 7 & 16.<br />

A DFRB was also convened to review the November 2010 deadly force incident. Two<br />

issues that go directly to public and officer safety that were identified by Mr. Gennaco in<br />

connection with that review were the consideration of the twenty-four rounds fired by the<br />

officers (out of twenty-six total rounds) that failed to strike the subject and the existence<br />

of a cross-fire situation in the encounter. Exhibit D at 9-10. In regards to the expended<br />

rounds, Mr. Gennaco recommends that the DFRB examine each officer’s use of deadly<br />

force individually and arrive at an assessment of whether the officer was tactically<br />

sound and proficient when he discharged his weapon. Id. at 9 & 16. Similarly, Mr.<br />

Gennaco considered the DFRB’s review of the cross-fire issue to be incomplete due to<br />

its failure to sufficiently explore the question based upon the placement and actions of<br />

all of the officers involved in the incident. Id. at 10 & 16. Recognizing that a single<br />

instance does not necessarily represent a consistent pattern, the Commission<br />

nevertheless calls for the SPD to reflect upon Mr. Gennaco’s findings and to ensure that<br />

DFRBs always thoroughly explore deadly force encounters for lessons learned that will<br />

enhance public and officer safety.<br />

Recommendation #17 – Create and deploy a fully developed Early Intervention<br />

System.<br />

Operating under the premise that small issues will lead to big problems if left<br />

unattended, an Early Intervention System (EIS) is a valuable administrative tool that can<br />

enhance accountability and integrity in a law enforcement agency. An EIS is a databased<br />

management tool designed to identify officers whose behavior is problematic and<br />

to spur intervention to correct that performance before the situation escalates into a<br />

formal disciplinary action or worse. A department’s EIS must be part of its larger efforts<br />

to support and improve officer performance. Frontline supervisors are key actors in the<br />

use of an EIS, but the Chief of Police and his command staff must be committed to the<br />

full deployment of the system.<br />

The information collected as part of an EIS can be as expansive as a department<br />

desires. Of particular relevance to the issue of the use of force, an EIS should track all<br />

reported uses of force, searches and seizures, number of arrests, and any civilian or<br />

internal complaints, civil suits, or criminal charges regarding the use of force.<br />

Additionally, recognizing that aberrant behavior in a multitude of performance areas can<br />

be a precursor to a use of force problem, an EIS system should capture other<br />

information that could identify outliers in the department. This could include, for<br />

example, such things as unusual numbers of pedestrian stops, the failure to meet<br />

training obligations, disciplinary actions, negative performance evaluations, and any<br />

City of Spokane Use of Force Commission – Page 23

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!