Critical Points To Ponder About A “Don’t Shoot At Vehicles” Policy

Print Friendly, PDF & Email

A growing number of agencies are specifying in policy that moving motor vehicles per se should no longer be considered deadly threats and that officers should not use deadly force to protect themselves or others from vehicular attack.

Firing is permitted only when someone inside a vehicle is posing an immediate lethal threat with some means other than the vehicle itself. To defend themselves, officers are encouraged to move to cover out of a vehicle’s path rather than shoot.

The unforeseen problem with such an ultra-restrictive mandate, according to Dr. Bill Lewinski, executive director of the Force Science Institute, is this:

Given the realities both of vehicular assaults on cops and of human performance under stress, violations of these policies may be inevitable, resulting in a rash of unfair disciplinary actions while failing to achieve the goal of reducing officer-involved shootings.

“Most often,” says Lewinski, “these policies seem to be driven by political pressure and are based more on speculation than on solid behavioral science.

“In my opinion, prohibiting a police officer from shooting to disable a driver or persuade him to stop using a vehicle as a weapon is likely to increase the risk of injury and death to officers and possibly to innocent civilians as well.”

Before a department adopts a blanket no-shoot policy, Lewinski suggests that the following questions be candidly considered:

Will officers really be able to comply with the policy?

“Behavioral science tells us that in many cases the honest answer to that question is ‘No,'” Lewinski says. He explains:

“Regardless of how a written policy may view them, moving motor vehicles in and of themselves can be deadly weapons, and some offenders do use them to target cops. Officers are well aware of this serious danger.

“In training, officers are taught that when their lives are at grave and immediate risk and there is no other feasible option to protect them against serious bodily harm or death, they are to draw their sidearm and shoot–or, if they already have it in hand, to fire it at the threatening suspect. In other words, you meet imminent deadly force with deadly force.

“This is instilled to the depth that a shooting response to a life threat is virtually automatic and reflexive, similar to throwing out your hands when you trip and are about to fall.

“Automatic decision-making dominates when there is too little time–seconds or less–to analyze a threat and determine a reasoned response. Vehicle assaults commonly occur under such time-pressured conditions.

“In a best-case scenario, a no-shoot policy will underscore the potential dangers of vehicles, motivate officers to plan ahead and strategically avoid making themselves vulnerable. But vehicular assaults often unfold dramatically, rapidly, and unexpectedly–beyond an officer’s control. And that’s when the policy falls apart.

“Chances are that an officer facing an on-coming vehicle will not even remember a no-shoot policy amidst his or her desperate, instinctive reaction. If it does flit to mind, it’s likely to cause confusion, hesitation, and/or inappropriate action. Anything that causes you to think about options when there’s no time to think will impair your performance.

“All this is to say that however well-intentioned they may be, rigid no-shoot policies hold officers accountable to an unrealistic standard of behavior. That’s why agencies that have adopted stringent policies tend to still have officers who shoot at cars. They aren’t necessarily being defiant. They just can’t overcome a compelling trained reaction.”

• What retraining realistically will be required to achieve compliance?
“First,” Lewinski says, “we need to know a lot more about the nature of vehicular attacks and the circumstances under which they occur than we do now. We can’t design and train good tactical responses without a thorough knowledge of the problems we’re addressing. And at the moment, there is no reliable, comprehensive research on vehicular assaults.

“Also we don’t know how much or what kind of training is necessary to change behavioral instincts. Certainly it takes more than just announcing a policy change and expecting automatic conformity.

“One major Canadian agency that adopted a rigid no-shoot policy ‘retrained’ its officers by exposing them to one simulator scenario involving a vehicle coming toward them. That department later reversed its new policy as a failure, after shootings at moving vehicles continued to occur.

“For a department to override an officer’s instinctive response and instill its preferred decision-making to an effective level, it must reinforce the new value repeatedly and far before any real-world incident occurs. This includes providing officers with the experience necessary to read and correctly respond to the kinds of situations they are likely to encounter on the street.

“In effect, the training must create a new automaticity as a default reaction that officers will resort to without conscious thought under the massive stress of a mortal threat.

“Training to this level will be very intensive and very expensive. I’ve assessed training in three different countries, and I have never seen a police training program capable of doing this. Without it, it will be very difficult to build anything more than an initial awareness of the policy change.”

Does the proposed policy reflect the true complexity of vehicular assaults?

“Strict no-shoot policies offer a simplistic solution to a complex problem,” Lewinski says. “Like most simplistic solutions, they often fail to take important factors into consideration.

“These policies try to impose what might be called the ‘El Toro’ model of reaction–officers are expected to perfectly escape the path of an oncoming vehicle much as a matador sidesteps a charging bull, thus avoiding the need to shoot. But that may not be possible.

“An officer may have fallen or be injured and physically unable to leap out of harm’s way. Or an on-looking officer may need to save an injured fellow officer or a child who’s immobilized by fear.

“Or there may not be time to escape if the vehicle is rapidly accelerating and the officer is only a car length or two away. Research has shown that for the average person to sprint even two strides and cover four feet takes about three quarters of a second, not allowing for the time required for a threat to be perceived and processed. An officer will be even slower because of the weight of his or her duty gear. The officer’s response time will often be significantly greater than the acceleration and travel time of the vehicle.

“Because of a trick of the mind called ‘looming,’ a more distant vehicle moving forward may appear to be closer and speeding faster than it actually is, and an officer experiencing that terrifying phenomenon may feel an enhanced urgency to shoot in hopes of stopping the driver.

“In reality, you don’t have to be directly in front of or in rear of a car to be in jeopardy. With a slight turn, a moving vehicle can easily compress against or hit an officer standing to the side. The closer you are, even to the side of a vehicle, the faster it will seem to be going. Mere proximity can appear to more than double the actual speed.

“When you’re in range of a vehicle coming in your direction, it’s difficult to predict exactly where it may go and how it may threaten you. The potential path of danger–the area a moving vehicle could cover–can change in a fraction of a second and be far wider than an officer can flee from.

“To expect a safe escape 100% of the time can be quite illusory. This is especially true when the incident occurs unexpectedly, unfolds rapidly, and creates an almost immediate threat to life.

“One fear that seems to drive no-shoot policies is the ‘uncontrolled projectile’ concern. That is, if the driver is shot and incapacitated, the vehicle would then become an ‘unguided missile’ that may cause significant damage or injury before it finally stops.

“Again, this seems to be a theoretical assertion that’s made without documented research; as yet, there is no scientific basis for it. It seemed logical when I first started to investigate the human factors in officer-involved shootings, but having closely analyzed dozens of incidents in which officers shot and either killed or seriously wounded a driver attempting to assault them with a vehicle, I have found that the vehicle invariably has rolled forward two to eight car lengths and then stopped.”

Have outliers been considered?

“People who write policy generally have some specific concepts in their head of the kind of situations they are addressing,” Lewinski says. “With no-shoot restrictions, they may envision a vehicular confrontation where an officer can feasibly sidestep the threat, or they may imagine a suspect car fleeing away from a scene where shooting would be clearly inappropriate.

“But they may not consider the kinds of outlier possibilities in the crazy world of policing in which the policy makes no sense.

“Some years ago an offender in San Diego stole a National Guard armored tank and proceeded to drive down a street squashing parked cars and endangering motor traffic and pedestrians. In Toronto, a barefoot EDP in the dead of winter hijacked a snowplow and went on a two-hour rampage during which he struck and killed a police sergeant.

“Does a policy that prohibits the use of deadly force against the driver of a moving vehicle really serve the public good in such circumstances?

“Sometimes on traffic stops, officers reach inside a vehicle for the keys or open a driver’s door for an extraction and get trapped or pinned in the vehicle when the driver suddenly accelerates and speeds off. Sometimes officers are crushed or pinned against another vehicle or some other object. Deadly force in these situations may be the only choice that can save them.

“When formulating policy, administrators need to be aware that there are many unanticipated variables that may arise, not just the ones they are intending to prohibit.”

What’s better?

“Of course,” Lewinski says, “there are circumstances in which shooting at moving vehicles is illegal or at least undesirable, and the proper parameters of use of force need frequent reinforcement. So does tactical training that lessens the risk of officers unwittingly placing themselves where they are vulnerable to vehicular attack.

“But by the same token, it is hardly defensible to impose restraints on self-defense that are unrealistic, unscientific, and likely to prove unenforceable. A number of departments that have adopted stringent no-shoot policies have, in fact, reversed themselves because these measures proved not to be feasible.

“While this issue continues to be researched, any policy specifically addressing deadly force and motor vehicles should permit officers to protect themselves and others from what is reasonably perceived to be a threat of death or serious injury or, under the guidelines established by the Supreme Court, to prevent the escape of a violent felon.

“An alternative is not to single out vehicles for special mention but to implicitly include them in a broad policy that permits deadly force at an officer’s reasonable discretion when an imminent threat is perceived.”

Leave a Reply


  • Privacy Policy

Privacy Policy

Effective date: January 06, 2019

Force Science Institute, Ltd. (“us”, “we”, or “our”) operates the https://www.forcescience.org/ website (hereinafter referred to as the “Service”).

This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our Service and the choices you have associated with that data. Our Privacy Policy for Force Science Institute, Ltd. is based on the Privacy Policy Template from Privacy Policies.

We use your data to provide and improve the Service. By using the Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, accessible from https://www.forcescience.org/

Information Collection And Use

We collect several different types of information for various purposes to provide and improve our Service to you.

Types of Data Collected

Personal Data

While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you (“Personal Data”). Personally identifiable information may include, but is not limited to:

  • Email address
  • First name and last name
  • Phone number
  • Address, State, Province, ZIP/Postal code, City
  • Cookies and Usage Data

Usage Data

We may also collect information on how the Service is accessed and used (“Usage Data”). This Usage Data may include information such as your computer’s Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

Tracking & Cookies Data

We use cookies and similar tracking technologies to track the activity on our Service and hold certain information.

Cookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Service.

You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service. You can learn more how to manage cookies in the Browser Cookies Guide.

Examples of Cookies we use:

  • Session Cookies. We use Session Cookies to operate our Service.
  • Preference Cookies. We use Preference Cookies to remember your preferences and various settings.
  • Security Cookies. We use Security Cookies for security purposes.

Use of Data

Force Science Institute, Ltd. uses the collected data for various purposes:

  • To provide and maintain the Service
  • To notify you about changes to our Service
  • To allow you to participate in interactive features of our Service when you choose to do so
  • To provide customer care and support
  • To provide analysis or valuable information so that we can improve the Service
  • To monitor the usage of the Service
  • To detect, prevent and address technical issues

Transfer Of Data

Your information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.

If you are located outside United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to United States and process it there.

Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.

Force Science Institute, Ltd. will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.

Disclosure Of Data

Legal Requirements

Force Science Institute, Ltd. may disclose your Personal Data in the good faith belief that such action is necessary to:

  • To comply with a legal obligation
  • To protect and defend the rights or property of Force Science Institute, Ltd.
  • To prevent or investigate possible wrongdoing in connection with the Service
  • To protect the personal safety of users of the Service or the public
  • To protect against legal liability

Security Of Data

The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

Service Providers

We may employ third party companies and individuals to facilitate our Service (“Service Providers”), to provide the Service on our behalf, to perform Service-related services or to assist us in analyzing how our Service is used.

These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.


We may use third-party Service Providers to monitor and analyze the use of our Service.

  • Google AnalyticsGoogle Analytics is a web analytics service offered by Google that tracks and reports website traffic. Google uses the data collected to track and monitor the use of our Service. This data is shared with other Google services. Google may use the collected data to contextualize and personalize the ads of its own advertising network.You can opt-out of having made your activity on the Service available to Google Analytics by installing the Google Analytics opt-out browser add-on. The add-on prevents the Google Analytics JavaScript (ga.js, analytics.js, and dc.js) from sharing information with Google Analytics about visits activity.For more information on the privacy practices of Google, please visit the Google Privacy & Terms web page: https://policies.google.com/privacy?hl=en

Links To Other Sites

Our Service may contain links to other sites that are not operated by us. If you click on a third party link, you will be directed to that third party’s site. We strongly advise you to review the Privacy Policy of every site you visit.

We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.

Children’s Privacy

Our Service does not address anyone under the age of 18 (“Children”).

We do not knowingly collect personally identifiable information from anyone under the age of 18. If you are a parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from children without verification of parental consent, we take steps to remove that information from our servers.

Changes To This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update the “effective date” at the top of this Privacy Policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

Contact Us

If you have any questions about this Privacy Policy, please contact us:

  • By email: support@forcescience.org
  • By visiting this page on our website: https://www.forcescience.org/contact
  • By phone number: 866-683-1944
  • By mail: Force Science Institute, Ltd.