In 2023/24 the stop and search rate for Black or Black British people in England and Wales was 22 per one thousand people, compared with the overall stop and search rate for white people of six per one thousand people, and that of Asian

Stop and Search is an operational tool used to prevent, detect and investigate crime as well as to bring offenders to justice. Police officers have a legal power to stop and search members of the public in certain circumstances, from dealing with incidents of anti-social behaviour through to countering terrorism. PSNI Statistics Branch collate and report statistics on the number of persons stopped, searched, questioned and arrested under the main legislative powers.

The police in England and Wales performed 535,307 stop and searches in 2023/24, compared with 547,000 in the previous year. Between 2008/09 and 2017/18 the amount of stop and searches had been decreasing, but have increased in every subsequent year up until 2021/22.

Stop and Search is an operational tool used to prevent, detect and investigate crime as well as to bring offenders to justice. Police officers have a legal power to stop and search members of the public in certain circumstances, from dealing with incidents of anti-social behaviour through to countering terrorism. PSNI Statistics Branch collate and report statistics on the number of persons stopped, searched, questioned and arrested under the main legislative powers.

In 2023/24, 292,497stop and searches were performed by the police in England and Wales on white people, compared with ****** on Black people, and ****** on Asian people.

Stop and search data presented here are taken from the annual Home Office Statistics release ‘Police Powers and Procedures, England and Wales 2012/13’, and cover stops and searches conducted by police under:

• Section 1 of PACE and associated legislation (collectively referred to as section 1 of PACE). The associated legislation includes stop and search powers under section 47 of the Firearms Act 1968, section 23 of the Misuse of Drugs Act 1971, section 43 of the Terrorism Act 2000 as well as other legislation.
• Section 60 of the Criminal Justice and Public Order Act 1994 in anticipation of violence.
• Section 47A (as amended by the Protection of Freedoms Act 2012) of the Terrorism Act 2000 in order to prevent acts of terrorism). For each of the above powers, data on resultant arrests as well as breakdowns by police force area and self-defined ethnicity of search recipient are included in the tables.

Please refer to the ‘Index’ tab within the tables to navigate to the appropriate data. Please also ensure you review the ‘notes’ tab before using the data.

Merseyside Police, responsible for policing the city of Liverpool and surrounding areas, performed 34.6 stop and searches per 1,000 population in 2023/24, the highest rate among police forces in England and Wales.

Stop and Search is an operational tool used to prevent, detect and investigate crime as well as to bring offenders to justice. Police officers have a legal power to stop and search members of the public in certain circumstances, from dealing with incidents of anti-social behaviour through to countering terrorism. PSNI Statistics Branch collate and report statistics on the number of persons stopped, searched, questioned and arrested under the main legislative powers.

🇬🇧 United Kingdom English Stop and search data presented here are taken from the annual Home Office Statistics release ‘Police Powers and Procedures, England and Wales 2012/13’, and cover stops and searches conducted by police under: * Section 1 of PACE and associated legislation (collectively referred to as section 1 of PACE). The associated legislation includes stop and search powers under section 47 of the Firearms Act 1968, section 23 of the Misuse of Drugs Act 1971, section 43 of the Terrorism Act 2000 as well as other legislation. * Section 60 of the Criminal Justice and Public Order Act 1994 in anticipation of violence. * Section 47A (as amended by the Protection of Freedoms Act 2012) of the Terrorism Act 2000 in order to prevent acts of terrorism). For each of the above powers, data on resultant arrests as well as breakdowns by police force area and self-defined ethnicity of search recipient are included in the tables. Please refer to the ‘Index’ tab within the tables to navigate to the appropriate data. Please also ensure you review the ‘notes’ tab before using the data.

In July 2019, the Metropolitan Police Department (MPD) implemented new data collection methods that enabled officers to collect more comprehensive information about each police stop in an aggregated manner. More specifically, these changes have allowed for more detailed data collection on stops, protective pat down (PPDs), searches, and arrests. (For a complete list of terms, see the glossary on page 2.) These changes support data collection requirements in the Neighborhood Engagement Achieves Results Amendment Act of 2016 (NEAR Act).The accompanying data cover all MPD stops including vehicle, pedestrian, bicycle, and harbor stops for the period from July 22, 2019 to December 31, 2022. A stop may involve a ticket (actual or warning), investigatory stop, protective pat down, search, or arrest.If the final outcome of a stop results in an actual or warning ticket, the ticket serves as the official documentation for the stop. The information provided in the ticket include the subject’s name, race, gender, reason for the stop, and duration. All stops resulting in additional law enforcement actions (e.g., pat down, search, or arrest) are documented in MPD’s Record Management System (RMS). This dataset includes records pulled from both the ticket (District of Columbia Department of Motor Vehicles [DMV]) and RMS sources. Data variables not applicable to a particular stop are indicated as “NULL.” For example, if the stop type (“stop_type” field) is a “ticket stop,” then the fields: “stop_reason_nonticket” and “stop_reason_harbor” will be “NULL.” Each row in the data represents an individual stop of a single person, and that row reveals any and all recorded outcomes of that stop (including information about any actual or warning tickets issued, searches conducted, arrests made, etc.). A single traffic stop may generate multiple tickets, including actual, warning, and/or voided tickets. Additionally, an individual who is stopped and receives a traffic ticket may also be stopped for investigatory purposes, patted down, searched, and/or arrested. If any of these situations occur, the “stop_type” field would be labeled “Ticket and Non-Ticket Stop.” If an individual is searched, MPD differentiates between person and property searches. The “stop_location_block” field represents the block-level location of the stop and/or a street name. The age of the person being stopped is calculated based on the time between the person’s date ofbirth and the date of the stop.There are certain locations that have a high prevalence of non-ticket stops. These can be attributed to some centralized processing locations. Additionally, there is a time lag for data on some ticket stops as roughly 20 percent of tickets are handwritten. In these instances, the handwritten traffic tickets are delivered by MPD to the DMV, and then entered into data systems by DMV contractors. On August 1, 2021, MPD transitioned to a new version of its current records management system, Mark43 RMS.Due to this transition, the data collection and structures for the period between August 1, 2021 – December 31, 2021 were changed. The list below provides explanatory notes to consider when using this dataset.New fields for data collection resulted in an increase of outliers in stop duration (affecting 0.98% of stops). In order to mitigate the disruption of outliers on any analysis, these values have been set to null as consistent with past practices.Due to changes to the data structure that occurred after August 1, 2021, six attributes pertaining to reasons for searches of property and person are only available for the first seven months of 2021. These attributes are: Individual’s Actions, Information Obtained from Law Enforcement Sources, Information Obtained from Witnesses or Informants, Characteristics of an Armed Individual, Nature of the Alleged Crime, Prior Knowledge. These data structure changes have been updated to include these attributes going forward (as of April 23, 2022).Out of the four attributes for types of property search, warrant property search is only available for the first seven months of 2021. Data structure changes were made to include this type of property search in future datasets.The following chart shows how certain property search fields were aligned prior to and after August 1, 2021. A glossary is also provided following the chart. As of August 2, 2022, these fields have reverted to the original alignment.https://mpdc.dc.gov/sites/default/files/dc/sites/mpdc/publication/attachments/Explanatory%20Notes%202021%20Data.pdfIn October 2022 several fields were added to the dataset to provide additional clarity differentiating NOIs issued to bicycles (including Personal Mobility Devices, aka stand-on scooters), pedestrians, and vehicles as well as stops related specifically to MPD’s Harbor Patrol Unit and stops of an investigative nature where a police report was written. Please refer to the Data Dictionary for field definitions.In March 2023 an indicator was added to the data which reflects stops related to traffic enforcement and/or traffic violations. This indicator will be 1 if a stop originated as a traffic stop (including both stops where only a ticket was issued as well as stops that ultimately resulted in police action such as a search or arrest), involved an arrest for a traffic violation, and/or if the reason for the stop was Response to Crash, Observed Moving Violation, Observed Equipment Violation, or Traffic Violation.Between November 2021 and February 2022 several fields pertaining to items seized during searches of a person were not available for officers to use, leading to the data showing that no objects were seized pursuant to person searches during this time period. Finally, MPD is conducting on-going data audits on all data for thorough and complete information. For more information regarding police stops, please see: https://mpdc.dc.gov/stopdataFigures are subject to change due to delayed reporting, on-going data quality audits, and data improvement processes.

Per the requirements in the settlement to Federal Case 17-CV-234-JPS the Milwaukee Fire and Police Commission (FPC) is required to publish particular stop and search encounter data in compliance with Sec. IV(A)(10-13).

(MPD stands for Milwaukee Police Department)

A subset of data collected when individuals are interviewed by NOPD Officers (including individuals stopped for questioning and complainants).Disclaimer: The New Orleans Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information. The New Orleans Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The New Orleans Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of New Orleans or New Orleans Police Department web page. The user specifically acknowledges that the New Orleans Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. Any use of the information for commercial purposes is strictly prohibited. The unauthorized use of the words "New Orleans Police Department," "NOPD," or any colorable imitation of these words or the unauthorized use of the New Orleans Police Department logo is unlawful. This web page does not, in any way, authorize such use.

Stop and Search is an operational tool used to prevent, detect and investigate crime as well as to bring offenders to justice. Police officers have a legal power to stop and search members of the public in certain circumstances, from dealing with incidents of anti-social behaviour through to countering terrorism. PSNI Statistics Branch collate and report statistics on the number of persons stopped, searched, questioned and arrested under the main legislative powers.

The accompanying data cover all MPD stops including vehicle, pedestrian, bicycle, and harbor stops for the period from January 1, 2023 – December 31, 2024. A stop may involve a ticket (actual or warning), investigatory stop, protective pat down, search, or arrest. If the final outcome of a stop results in an actual or warning ticket, the ticket serves as the official documentation for the stop. The information provided in the ticket include the subject’s name, race, gender, reason for the stop, and duration. All stops resulting in additional law enforcement actions (e.g., pat down, search, or arrest) are documented in MPD’s Record Management System (RMS). This dataset includes records pulled from both the ticket (District of Columbia Department of Motor Vehicles [DMV]) and RMS sources. Data variables not applicable to a particular stop are indicated as “NULL.” For example, if the stop type (“stop_type” field) is a “ticket stop,” then the fields: “stop_reason_nonticket” and “stop_reason_harbor” will be “NULL.” Each row in the data represents an individual stop of a single person, and that row reveals any and all recorded outcomes of that stop (including information about any actual or warning tickets issued, searches conducted, arrests made, etc.). A single traffic stop may generate multiple tickets, including actual, warning, and/or voided tickets. Additionally, an individual who is stopped and receives a traffic ticket may also be stopped for investigatory purposes, patted down, searched, and/or arrested. If any of these situations occur, the “stop_type” field would be labeled “Ticket and Non-Ticket Stop.” If an individual is searched, MPD differentiates between person and property searches. Please note that the term property in this context refers to a person’s belongings and not a physical building. The “stop_location_block” field represents the block-level location of the stop and/or a street name. The age of the person being stopped is calculated based on the time between the person’s date of birth and the date of the stop. There are certain locations that have a high prevalence of non-ticket stops. These can be attributed to some centralized processing locations. Additionally, there is a time lag for data on some ticket stops as roughly 20 percent of tickets are handwritten. In these instances, the handwritten traffic tickets are delivered by MPD to the DMV, and then entered into data systems by DMV contractors. On August 1, 2021, MPD transitioned to a new version of its current records management system, Mark43 RMS. Beginning January 1, 2023, fields pertaining to the bureau, division, unit, and PSA (if applicable) of the officers involved in events where a stop was conducted were added to the dataset. MPD’s Records Management System (RMS) captures all members associated with the event but cannot isolate which officer (if multiple) conducted the stop itself. Assignments are captured by cross-referencing officers’ CAD ID with MPD’s Timesheet Manager Application. These fields reflect the assignment of the officer issuing the Notice of Infraction (NOIs) and/or the responding officer(s), assisting officer(s), and/or arresting officer(s) (if an investigative stop) as of the end of the two-week pay period for January 1 – June 30, 2023 and as of the date of the stop for July 1, 2023 and forward. The values are comma-separated if multiple officers were listed in the report. For Stop Type = Harbor and Stop Type = Ticket Only, the officer assignment information will be in the NOI_Officer fields. For Stop Type = Ticket and Non-Ticket the officer assignments will be in both NOI Officer (for the officer that issued the NOI) and RMS_Officer fields (for any other officer involved in the event, which may also be the officer who issued the NOI). For Stop Type = Non-Ticket, the officer assignment information will be in the RMS_Officer fields. Null values in officer assignment fields reflect either Reserve Corps members, who’s assignments are not captured in the Timesheet Manager Application, or members who separated from MPD between the time of the stop and the time of the data extraction. Finally, MPD is conducting on-going data audits on all data for thorough and complete information. Figures are subject to change due to delayed reporting, on-going data quality audits, and data improvement processes.

Per the requirements in the settlement to Federal Case 17-CV-234-JPS the Milwaukee Fire and Police Commission (FPC) is required to publish particular stop and search encounter data in compliance with Sec. IV(A)(10-13).

MPD stands for Milwaukee Police Department

To download XML and JSON files, click the CSV option below and click the down arrow next to the Download button in the upper right on its page.

The data used in the MPS Stop and Search Dashboard is available here Stop and Search Dashboard | Metropolitan Police, along with the related data definitions. Please note that, this dataset is updated monthly at the beginning of the month. Data runs until the end of the month prior. Definitions / Counting Rules Stop and Search (S&S) - When an officer stops a member of the public and searches them. The police can only detain members of the public in order to carry out a search when certain conditions have been met. Search powers fall under different areas of legislation which include searching for - Stolen property - Prohibited articles namely offensive weapons or anything used for burglary, theft, deception or criminal damage - Drugs - Guns Historically searches of unattended vehicles and vessels have made up a very low proportion of search activity.

Per the requirements in the settlement to Federal Case 17-CV-234-JPS the Milwaukee Fire and Police Commission (FPC) is required to publish particular stop and search encounter data in compliance with Sec. IV(A)(10-13).

MPD stands for Milwaukee Police Department

Home Office statisticians are committed to regularly reviewing the usefulness, clarity and accessibility of the statistics that we publish under the Code of Practice for Statistics.

We are therefore seeking your feedback as we look to improve the presentation and dissemination of our statistics and data in order to support all types of users.

If you have any comments about this release please contact us at crimeandpolicestats@homeoffice.gov.uk.