Laserfiche WebLink
Exhibit 1 <br />Background: <br />Prior to January 2021, the only means to identify reasons for a car stop was to review a traffic citation and/or <br />read an arrest or crime report narrative. Now with the RIPA database, the department is able to analyze <br />reasons for the stop. It is important to recognize RIPA requirements continue to evolve and today's <br />requirements will likely differ beginning 2022. <br />Source: <br />Car stop data (reason for the stop and result of the stop) was collected from January 1, 2021 through June <br />30, 2021, which resulted in the identification of 9,785 car stops. <br />Information on car stops is found in several data sources: <br />* CAD is a dispatch system and provides incident types, dispositions, and unit types. <br />* RIPA data provides information on the reason a stop was initiated and the result of the stop. <br />* Crossroads e-citation provides information on when stops occurred and if a citation was issued. <br />* RMS data contains arrest, crime, Fl, citation, and impound inTormation. <br />Methodoloqy: <br />RIPA is the only data source that identifies the reason for the stop. In many cases, there may be several <br />reasons for a car stop (i.e., traffic violation, probation, suspicious behavior, etc.) and there may be several <br />outcomes (i.e., citation, warning, education, arrest, etc.) resulting from it. In the cases of CAD, RIPA, and <br />RMS data, there are multiple pieces of information that must be ranked in order to identify the most <br />significant reason or result of a stop. <br />* For stop reasons, subjects known to have wants/warrants are given the highest score followed by <br />persons on probation/parole, traffic violations, truants, suspicious behavior, and consensual <br />encounters. <br />* For stop results, arrests are given the highest position followed by citations, field interview <br />documentation, crime reports, warnings, etc. <br />Motor officers' stops are not consistently recorded in CAD due to it being a dispatch system. Motor officers <br />conduct proactive traffic enforcement and due to the volume of stops, the officer may not communicate their <br />stop. Therefore, citations were only tied to CAD incidents, when possible. If the citation included a case <br />number, the case number was used to link CAD and citation data. If not, links were established when the <br />citing officer was on the CAD call and the CAD call occurred within five (5) minutes of the violation time of <br />the citation. Citations that could not be associated to CAD incidents were included as additional stops and <br />tallied with a stop reason of Traffic Violation and a result of Cited. <br />Conclusion: <br />Of the 9,785 car stops, a traffic violation was the reason for the stop 73% of the time. Suspicious behavior, <br />parole, probation, and consensual encounters were also identified as reasons. The leading car stop result <br />was the issuance of a citation at 39% followed by a combined 37% of warnings and education/no action <br />taken. A physical arrest occurred 7% of the time while a police report and/or field interview documentation <br />was completed 1.6'!/o of the time. <br />August10, 2021