Article 5 of 7 in CodeBlu Use-of-Force Research

Traffic Stops: Statistical Patterns and De-Escalation Opportunities

Published:
May 25, 2026
Last updated:
May 25, 2026
  • traffic-stops
  • de-escalation
  • use-of-force-data
On this page
  1. The scale of the traffic stop
  2. Where in the stop escalation happens
  3. The disparity data, presented carefully
  4. The officer-safety dimension
  5. What this means for your agency's training

The traffic stop is the most common reason Americans interact with police. This article examines what the data shows about where stops escalate, and where the training opportunities sit.

No single police activity touches more members of the public than the traffic stop. It is, by a wide margin, the most common form of police-initiated contact, and for most people in most years it is the only direct contact they will have with an officer at all. That combination, enormous volume and low individual frequency, makes the traffic stop a distinctive training problem. This article works through the statistical patterns and identifies where the de-escalation opportunities actually are.

The scale of the traffic stop

The Bureau of Justice Statistics measures police-public contact through the Police-Public Contact Survey (PPCS), a periodic supplement to the National Crime Victimization Survey that asks U.S. residents about their contacts with police over the prior twelve months.1 The PPCS finding is consistent across survey waves: being a driver in a traffic stop is the single most common reason for contact with police, and it holds that position across all racial groups.2 In 2022, about one in five U.S. residents experienced some contact with police.2

The volume estimates from independent analysis are large. The Stanford Open Policing Project, which has assembled and standardized more than 200 million traffic-stop records from state and municipal agencies, estimates that more than 20 million Americans are stopped for traffic violations each year.3 That is on the order of tens of thousands of stops every day.

Set against that volume, two facts define the traffic stop as a training subject.

First, the overwhelming majority of stops are uneventful. Most end with a warning, a citation, or no enforcement action at all, and force of any kind is statistically rare relative to the number of stops conducted.2 Second, despite that rarity, the traffic stop remains a meaningful serious-incident category. In the FBI's National Use-of-Force Data Collection, traffic stops accounted for roughly 12.9 percent of reported serious-force incidents over the 2021 to 2025 period, the second-largest contact category after responses to suspicious or unlawful activity.4

That is the paradox a training program must hold in mind. For the officer, the traffic stop is routine to the point of being automatic. For the rare stop that goes wrong, the consequences are among the most serious in policing. Officers cannot rely on field experience to stay sharp for the exception, because thousands of uneventful stops train the opposite reflex: that nothing will happen. This is the central argument for deliberate, scenario-based traffic-stop training rather than reliance on accumulated road time.

Where in the stop escalation happens

A traffic stop is not a single moment. It is a sequence, and escalation, when it occurs, tends to occur at identifiable transitions in that sequence. Mapping the timeline is the most useful thing a training analysis can do.

The approach. The walk from the patrol vehicle to the stopped car is an information-poor, exposure-high moment. The officer does not yet know who is in the vehicle or what the encounter is. Officer-safety doctrine has long concentrated on this phase, and the LEOKA data, discussed below, shows why. The training question here is positioning and observation, not communication.

The opening and the explanation. The first words exchanged set the tone of the entire encounter. Research and practitioner consensus in the procedural-justice literature emphasize that a clear explanation of the reason for the stop, delivered early, is associated with smoother encounters and greater perceived legitimacy. This is a communication phase, and it is one of the few moments in the stop the officer fully controls.

The document exchange and the wait. While the officer runs documents, the driver waits, often anxious, sometimes without a clear sense of how long the stop will take or what will happen next. Uncertainty drives anxiety, and anxiety drives unpredictable behavior. A simple practice, telling the driver what is happening and roughly how long it will take, addresses a real escalation driver at almost no cost.

The decision points: exit, search, custody. The transitions that most often precede force are the requests that change the encounter's nature: asking a driver to step out of the vehicle, initiating a search, or moving to an arrest. These are the moments where a compliant encounter can become a resistant one. They are also the moments most amenable to deliberate sequencing, clear communication of what is being asked and why, and rehearsal.

The practical takeaway: the traffic stop has a clear verbal phase and a clear set of physical-transition decision points, and they are separable. Officer-safety skill governs the approach. Communication skill governs the opening and the wait. Both together govern the decision points. A training program that treats the traffic stop as a single undifferentiated event misses the structure that makes it teachable.

The disparity data, presented carefully

The Stanford Open Policing Project's large-scale analysis of nearly 100 million stops found statistical evidence of racial disparities at several points in the stop process.3 Among its findings: officers appeared to require less suspicion to search Black and Hispanic drivers than white drivers, a pattern the researchers identified using the rate at which searches actually turned up contraband; and a "veil of darkness" analysis found Black drivers were relatively less likely to be stopped after dark, when an officer is less able to perceive a driver's race before the stop.3

Two honest caveats belong with these findings. First, the Stanford analysis covers a defined historical window, roughly 2011 to 2015 for the core multi-state analysis, and patterns may have shifted since.3 Second, aggregate statistical disparity is a measure of pattern, not of any individual officer's intent or conduct in any individual stop.

The training relevance is specific and bounded. Disparities of this kind, whatever their causes, tend to concentrate at exactly the discretionary decision points identified above, the search decision in particular. Training that makes officers more deliberate and more articulable at those decision points, requiring a clear, statable basis before escalating an encounter, addresses the moment where discretion is exercised. That is a training observation, not a policy recommendation, and this article makes no policy recommendation.

The officer-safety dimension

The traffic stop also carries genuine officer-safety weight, and the de-escalation case must not be made in a way that ignores it. The FBI's LEOKA data shows that traffic stops have long been a context in which officers are feloniously killed. Encouragingly, within that category the trend has been downward: of officers feloniously killed during traffic stops, roughly 40 percent of such deaths occurred in the 1990s, 32 percent in the 2000s, and 24 percent in the 2010s.5

The point for training is that officer-safety skill and de-escalation skill are not competing claims on the traffic stop. The approach phase is governed by officer-safety practice. The verbal phase and the decision points are governed by communication and de-escalation practice. A complete traffic-stop curriculum trains both, in their proper places in the timeline, rather than treating the stop as a single posture an officer must choose.

What this means for your agency's training

The traffic-stop data supports a clear set of training conclusions.

The defining feature of the traffic stop is volume without frequency: every officer conducts thousands, almost all uneventful, and the rare serious stop cannot be prepared for through routine experience. Scenario-based rehearsal exists precisely to manufacture the reps that the road will not provide for the exceptional case.

The traffic stop has a teachable structure. It is a sequence, the approach, the opening, the wait, the decision points, and escalation concentrates at the transitions. Training that maps to that structure, rather than treating the stop as one event, gives officers a usable mental model.

The discretionary decision points, exit, search, custody, are where both escalation and statistical disparity concentrate. Training that builds the habit of a clear, articulable basis before each escalation addresses that moment directly, and it does so as a matter of professional decision-making rather than policy advocacy.

And officer safety belongs in the same curriculum, not in opposition to it. The approach is an officer-safety phase; the verbal phases are de-escalation phases. A program that trains both, in sequence, prepares officers for the stop as it actually unfolds.

CodeBlu's scenario-based model is well suited to the traffic stop because the traffic stop is, structurally, a sequence of decision points, and decision points are what scenarios rehearse. The honest claim is bounded: scenario training builds proficiency at the timeline transitions the data identifies as escalation-prone. It does not, by itself, change the population-level patterns that broader policy and supervision also bear on.

Recommended CodeBlu scenarios this article supports

  1. Traffic stop approach and positioning: the officer-safety phase, rehearsing observation and positioning before the verbal encounter begins.
  2. The opening explanation: practicing a clear, early statement of the reason for the stop and setting expectations for its duration.
  3. The exit-the-vehicle decision: rehearsing the request to step out as a deliberate, communicated transition rather than an abrupt command.
  4. The search decision point: building the habit of articulating a clear basis before initiating a search, the discretionary moment where escalation concentrates.
  5. The non-compliant driver: a decision-point scenario for the stop that turns resistant, rehearsing the choice to slow down and create options.

Footnotes

  1. Bureau of Justice Statistics, "Police-Public Contact Survey (PPCS)." https://bjs.ojp.gov/data-collection/police-public-contact-survey-ppcs

  2. Bureau of Justice Statistics, "Contacts Between Police and the Public, 2022." https://bjs.ojp.gov/document/cbpp22.pdf 2 3

  3. Stanford Open Policing Project. https://openpolicing.stanford.edu/ and "Findings." https://openpolicing.stanford.edu/findings/ ; underlying analysis: E. Pierson et al., "A large-scale analysis of racial disparities in police stops across the United States." https://5harad.com/papers/100M-stops.pdf 2 3 4

  4. USAFacts, "What FBI data says about law enforcement use-of-force," 2025, summarizing FBI National Use-of-Force Data Collection figures. https://usafacts.org/articles/what-the-data-says-about-law-enforcement-use-of-force/

  5. "Education, (re)training, and traffic stops: Felonious law enforcement officer deaths in the United States," ScienceDirect, 2023. https://www.sciencedirect.com/science/article/pii/S1756061623000447

More from this series

This article is educational content prepared by CodeBlu for law enforcement training purposes. It is not legal advice. Officers should consult their agency's legal counsel for guidance specific to their jurisdiction and situation.

Questions? Email hello@codeblu.co.