Supreme Court OKs Deadly Force To Stop Dangerous Pursuit

Print Friendly, PDF & Email

A new Supreme Court decision has been added to the ongoing controversy in law enforcement circles about whether officers should be permitted by policy to shoot at moving vehicles.

Last week, the U.S. Supreme Court ruled that officers were justified in firing fatal rounds at a driver to end a dangerous high-speed chase. Further, the court declared, the officers were not guilty of excessive force for sending a fusillade at the offender’s vehicle–15 shots in all.

“The Supreme Court is making it clear that the Fourth amendment allows the use of deadly force to stop drivers in those exceptional cases when their actions pose a very serious threat to public safety,” says police attorney Bill Everett, a legal consultant to the Force Science Institute. “By limiting legal liability in these circumstances, the Court is allowing agencies to put more emphasis on keeping the public safe when developing their policies.”

A summary of this case (Plumhoff v. Rickard) and the decision in full can be read by clicking here

Here’s the essence of the matter:


The case began, the Court’s decision explains, near midnight on a hot July night in 2004 when a lieutenant with the West Memphis (AR) PD pulled over a white Honda Accord “because the car had only one operating headlight.” Closer contact revealed that the windshield bore an indentation “roughly the size of a head,” as if the vehicle had struck a pedestrian.

The nervous driver denied any recent drinking but failed to produce a driver’s license. When the lieutenant asked him to step out of the car, he sped away instead. Quickly, the lieutenant was joined in hot pursuit by a phalanx of five other squad cars as the suspect, with a front-seat passenger, headed on Interstate 40 for a bridge that spans the Mississippi River into Memphis, TN.

An attempt at a “rolling roadblock” proved unsuccessful. Undeterred, the driver swerved through traffic at speeds over 100 mph, passing more than two dozen vehicles.

Across the bridge, he exited onto a Memphis street and shortly made a sudden right turn, colliding with one of the chase squads closing in. The Honda “spun out into a parking lot” and there crashed into another cruiser. “Now in danger of being cornered,” the suspect slammed his car into reverse “in an attempt to escape.”

An officer and a sergeant exited their units and ran to the vehicle. “Gun in hand,” the sergeant “pounded on the passenger-side window.” Desperation mounting, the suspect steered into yet another police car. With his bumper “flush against a cruiser,” he tromped on the accelerator, spinning tires and rocking his car back and forth, trying to break free.

“At that point,” the Court recounts, the sergeant “fired three shots into [the suspect’s] car.” Undaunted, the driver “reversed in a 180-degree arc” and “maneuvered onto” another street, nearly striking another officer on foot in the process.

As the suspect continued “fleeing down” the street, two other officers now fired 12 shots toward the Honda, striking the driver and his passenger. The driver “lost control of the car and crashed into a building.” Both he and his passenger, in the Court’s words, “died from some combination of gunshot wounds and injuries suffered in the crash that ended the chase.”

The pursuit had lasted “more than five minutes.” All the shots were fired within a span of 10 seconds.


A 1983 action was brought in federal court on behalf of the dead driver’s minor daughter, alleging excessive force that violated the suspect’s constitutional rights. The six West Memphis officers involved in the chase (including the three who fired shots), their chief, and the town’s mayor were named as defendants.

Specifically, the civil suit contended that the 4th Amendment “did not allow [the officers] to use deadly force to terminate the chase,” and that, “even if they were permitted to fire their weapons, they went too far when they fired as many rounds as they did.”

The district court agreed with the plaintiff. It denied a defense motion for summary judgment based on qualified immunity, holding that “the officers’ conduct…was contrary to law that was clearly established” at the time of the shootings. An appellate panel affirmed this decision.

The Supreme Court Justices, however, unanimously struck down these findings.


First the Court’s decision notes that 4th Amendment claims must be analyzed in accordance with its landmark Graham v. Connor decision; i.e., with the “totality of the circumstances” considered from the perspective of “a reasonable officer on the scene.”

Then the Court points out that in a previous case in 2007 it held that a “police officer’s attempt to terminate a dangerous high-speed car chase that threatens the lives of innocent bystanders does not violate the Fourth Amendment, even when it places the fleeing motorist at risk of serious injury or death.” [That case, Scott v. Harris, can be accessed in full by clicking here]

The Court concludes there’s no reason to depart from that precedent. In the case at hand, the suspect’s “outrageously reckless driving posed a grave public safety risk,” says the decision, written by Justice Samuel Alito Jr.

Collision with police vehicles may have brought the pursuit “temporarily to a near standstill, [but] that did not end the chase…. [A]t the moment when the shots were fired, all that a reasonable police officer could have concluded was that [the driver] was intent on resuming his flight and that, if he was allowed to do so, he would once again pose a deadly threat for others on the road…. [T]he police acted reasonably in using deadly force to end that risk.”

As for the lawsuit’s claim that 15 shots were too many, the Court says: “We reject that argument. It stands to reason that, if police officers are justified in firing at a suspect in order to end a severe threat to public safety, the officers need not stop shooting until the threat has ended.”

During the brief span when all the shots were fired, the suspect “never abandoned his attempt to flee. Indeed, even after all the shots had been fired, he managed…to continue driving until he crashed.

“This would be a different case if [officers] had initiated a second round of shots after an initial round had clearly incapacitated [the suspect] and had ended any threat of continued flight, or if [he] had clearly given himself up. But that is not what happened.”

Given the circumstances and the absence of any compelling prior cases that proscribe firing at a vehicle to terminate a dangerous car chase, the Court ruled that the accused parties were fully entitled to qualified immunity in the shooting “because they violated no clearly established law.”

Atty. Everett told Force Science News: “One of the startling–and welcome–aspects of this opinion doesn’t have so much to do with pursuits as it does with deadly force in general.

“The Court flatly rejected the plaintiffs’ tactic of using the number of rounds fired to make a good decision look bad. The opinion doesn’t mince words: Officers are justified, the Court says, in continuing to use deadly force until the threat has been stopped.

“This should give officers more confidence that their training will hold up in court, and should also give a lot of would-be plaintiffs serious pause when considering certain lawsuits.”


“In this case,” notes FSI’s executive director Dr. Bill Lewinski, “the circumstances were relatively straightforward. The Supreme Court determined that the suspect vehicle and its driver posed a clear threat and shooting to end that threat was both practical and appropriate.

“However, in a broader context, including situations in which vehicles are used as assault weapons against officers, shooting at a moving vehicle can become a more complex issue. Then a myriad of behavioral science factors may come into play, including speed and distance calculations, changing trajectories, unconsciously altered perceptions of threat, psychophysiological and perceptual phenomena like “looming,” and so on.

“Confronted with contradictory forensic evidence, officers may find themselves challenged to articulate why they believed a high level of threat existed when, in fact, the actual threat seems to have been much lower. They may be puzzled as to why rounds they insist were fired directly at a car bearing down on them ended up suspiciously impacting in a remote part of the vehicle.

“The dynamics involved in shooting at moving vehicles affect policy makers, trainers, street officers, investigators, force reviewers, and legal representatives alike. All need to understand the sometimes surprising nuances of human behavior under stress in these high-intensity circumstances.”

A near-term goal of Force Science, Lewinski says, is to thoroughly explore this area for law enforcement. Currently in discussion are groundbreaking research projects and instructional courses that will “help to unravel the perplexities of this issue and will equip all those involved to make better decisions.”

FSN will report more details as these future plans take shape.

EDITOR’S NOTE: Three days after the Supreme Court decision, a grand jury in Cuyahoga County, OH, indicted six Cleveland PD officers on criminal charges for their roles in a controversial pursuit-related shooting in which two unarmed subjects were killed. A patrol officer, who had fired nearly 50 rounds in the incident, was charged with voluntary manslaughter and five supervisors with dereliction of duty.

In news reports, the county prosecutor contrasted this case with the one ruled on by the Supreme Court. In the Cleveland incident, the suspect vehicle “was fully stopped,” prosecutor Timothy McGinty explained. “Escape was no longer even a remote possibility. The flight was over. The public was no longer in danger because the car was surrounded by police cars and 23 police officers in a schoolyard safely removed from pedestrians and traffic.”

An attorney for the police union, however, lambasted the prosecutor and the indictment, charging that McGinty “had the benefit of hindsight,” spending about 18 months dissecting decisions and actions made in seconds.

Click here for more details from a local news account.

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.