Was Suspect’s Shooting A “Police Execution?”

Print Friendly, PDF & Email

Until the Force Science Research Center entered the case, no one knew precisely how Randall Carr ended up killed by a police bullet that tore into his body near his rectum and blew a hole in his heart.

His angry relatives, with Johnnie Cochran’s legal team behind them, insisted it had to be a deliberate police execution.

The officers involved vehemently denied that, of course. But they couldn’t reconstruct the fatal details of Carr’s final moments or explain the seemingly incriminating pattern of wounds documented at autopsy.

With a $5 million federal civil rights lawsuit and the officers’ reputations at stake, attorneys for the officers contacted Dr. Bill Lewinski, executive director of the nonprofit FSRC at Minnesota State University-Mankato, in hopes that a scientific analysis of the shooting could shed some light on its dark mysteries.

This much was known about the circumstances that began unfolding about 11 o’clock one autumn night in the Maxwell House Apartments in downtown Oklahoma City:

During an investigation of an assault on the landlord during a rent dispute, 2 officers were questioning the accused tenant, Randall Carr, 38. Carr was acting “very excited and aggressive,” and was later found to have evidence of cocaine use in his bloodstream. He declared, “I own this building, I own Oklahoma City and I don’t have to pay rent!” Then he punched one officer in the head, inflicting a cut over his right eye, and kneed the other in the groin, and fled on foot. Multiple units responded.

During a pursuit by foot and car, Carr at one point was whacked at the knee with an expandable baton and sprayed directly in the eyes and nose with OC, but he did not submit. Finally the cop who’d been kneed during the initial call, Ofcr. Jerry Bowen, and a responding sergeant, Randy Castle, cornered Carr in a small, dark churchyard a couple of blocks from his apartment.

With a jagged piece of concrete about twice the size of a softball clutched in his left hand, Carr (who was left handed) tried to scale a spiked fence at one edge of the yard, but he couldn’t make it. The officers were yelling at him to get down and to drop the concrete. He dropped off the fence, turned and with his left arm raised started to run directly at Castle, who was about 20 feet away.

Bowen was forward from Castle and to his right. In Bowen’s perception, Carr was charging Castle intent on bashing in the sergeant’s skull with the concrete chunk.

Both officers opened fire with their Glocks. Eleven rounds were discharged. Seven struck Carr. When the shooting stopped he was slumped against a wooden bench several feet to Castle’s left.

Castle had no clear recollection of the 5 shots he fired. He recalled Carr “throwing” the concrete at him at a point. A left-hander like the suspect, Castle instinctively turned away while raising his right hand to protect his head, and fired his rounds blindly back at his assailant with his left hand.

Bowen said he started shooting when Carr crossed his line of fire in the dead run toward Castle. There was about 5 feet between Bowen and the attacker at that moment. He fired a total of 6 rounds. Between the moment he started shooting and an awareness that Carr was “suddenly” no longer upright as a target, he had no relevant memories.

These days, white officers shooting and killing any black suspect guarantees controversy. But in this case, the situation was exacerbated by a disturbing medical examiner’s report.

The fatal round, which ballistics determined was fired by Bowen, has entered to the left of Carr’s rectum and had followed a path roughly paralleling his spinal column straight to his heart.

Through a local attorney, surviving relatives of Carr (who included a professional football player) contacted Johnnie Cochran’s law office and a federal civil suit inevitably materialized, alleging excessive force by the officers and failure to train and supervise by the city. The municipality got out of the case on a motion for summary judgment prior to trial, but the officers remained as defendants.

At the heart of the plaintiffs’ case was an inflammatory premise: Such a fatal bullet pathway could have occurred only if Carr was already down on his hands and knees, butt in the air and no longer a threat, when the killing shot was fired. Bowen must have advanced on the suspect and pulled the trigger from behind him to create the resulting wound channel. In effect, the fatal round was an unjustified execution.

Bill Lewinski says he approached this volatile situation with no preconceived notions. “Mentally I kept myself neutral to how it would come out, good or bad,” he says. “I was interested just in understanding what happened.”

Besides the fatal round, Carr had been shot in the left hip, the left waistline, the right calf, the left wrist, the left thigh and the inside right thigh. The autopsy report clearly established each wound channel, confirming the trajectory on which each slug had penetrated into the offender’s body. All but one had struck him from the rear. However, the sequencing of the shots, whose gun some of the rounds came from (those that were through and through), and what time span the shooting covered–all were among the case’s many unknowns.

As one of the nation’s foremost authorities on reaction times and shooting dynamics, Lewinski felt that documenting the missing elements would be critical to understanding how the shooting actually unfolded and determining whether the plaintiffs’ allegations of wrongdoing might, in fact, be true.

He started by taking Ofcr. Bowen and Sgt. Castle to Oklahoma City PD’s firearms range. They’d told him that in an effort to stop the onrushing Carr they had fired as fast as they could pull the trigger that fateful night. He asked them to do that again–repeatedly–while they were videotaped by Lewinski and one of FSRC’s National Advisory Board members, Parris Ward. Ward, who heads the firm Biodynamics Engineering, is a prominent computer animator whose vivid reconstructions of police shootings and other controversial events are frequently introduced as pivotal evidence in high-profile court cases.

The videotapes offered gross time stamps of the officers shooting. But back in his lab in Pacific Palisades, CA, Ward’s ultra-sophisticated equipment was able to break down the sample firings into hundredths of a second. That revealed that the officers had been able to shoot in a range of .233 to .268 of a second per round.

Now Lewinski, working with Ward and his precision equipment, set about the laborious task of calculating the sequence and timing of every round that had struck Carr.

Lewinski figured that the round which entered Carr’s left side at waist level had to have been the initial round fired by Bowen and the first of the fusillade to hit the running suspect. “This would could only have come from one officer at one point in the action,” Lewinski says.

Almost simultaneous to that round, according to investigators’ reports, Carr had stumbled and had “thrown” the concrete at Castle, who was then less than 5 feet away. The chunk hit Castle’s left shoulder.

At about the point Carr had reached in his line of travel when all this happened there was a depression in the ground that accommodated a drain grate. In the dark and malevolently focused on rushing Castle, Carr would not likely have seen this hole. If his left foot had gone down in it he would certainly have stumbled, his raised left hand would likely have involuntarily released the concrete and–most important, Lewinski knew from his extensive study of physical dynamics–his body would have thrust sharply forward and then twisted to the right as he tried unsuccessfully to regain his balance and his right leg collapsed from the sudden, unexpected shift of his body weight. Bowen’s shots coming from the left would have contributed to this motion.

Turning right and then falling face down toward the ground would have positioned him so that most of Bowen’s 5 shots that connected–including the troublesome fatal round–would have hit him from the rear, without Bowen advancing significantly toward him.

Painstakingly, Lewinski and Ward gradually reconstructed this probable timing and sequence:

0.000 second: Bowen’s first shot to Carr’s left hip (timing baseline).

0.233 second: Bowen’s second round, to the left waistline, slightly to the rear

0.500 second: Bowen’s third round, to the left buttock (the fatal shot)

0.600 second: Castle’s first round, a miss

0.733 second: Bowen’s fourth round, to the right rear calf

0.867 second: Castle’s second round, to the left wrist

0.967 second: Bowen’s fifth round, to the left rear thigh

1.133 seconds: Castle’s third round, to the inner right thigh

1.200 seconds: Bowen’s sixth (last) round, a miss to the suspect’s right

1.400 seconds: Castle’s fourth round, a miss

1.600 seconds: Castle’s fifth round, a miss (last round fired).

“This sequence of rounds, matched to bullet trajectories and times, when put all together makes a sensible scenario of what occurred,” Lewinski says. “Things can only happen in a certain way, and based on the science of the situation, we are confident this is the way.”

In confirming the incredible speed in which police shootings can go down, incidentally, this is a classic case: 11 rounds fired by these 2 officers in just 1.6 seconds, start to finish.

*** NOTE: To see Parris Ward’s 4 dramatic animation clips recreating this shooting, go to:


Versions for all 4 clips are available in both high- and low-resolution versions and can be played in both QuickTime and Windows Media Player.

When the lawsuit went to trial in U.S. District Court last November, Ward’s elegant and gripping color animation of the shooting and Lewinski’s detailed explanation of the science behind it were highlights of the officers’ defense presented by attorneys Robert Manchester (brother of the famed historian William Manchester) and Susan Knight (wife of an Oklahoma peace officer). The jury was shown the conflict recreated in time-coded slow motion, in freeze-frames and in actual time, from a variety of angles.

The key element was the placement of Bowen’s fatal round early in the sequence. Without that being plausibly positioned and explained, the plaintiff’s spectre of a final, fatal “execution” shot might have seem much more credible.

Johnnie Cochran, who had been expected to head the plaintiff’s case, failed to show, reportedly because of health problems. An associate from Hawaii replaced him.

This attorney tried to convince the jury that Ward’s animation was unrealistic. During cross examination, he had Lewinski get down on the courtroom floor, with his butt thrust toward the jury, and try to assume the position that he claimed Carr had been in when he took the fatal round. Lewinski could not do so–because, as he patiently explained, this was a dynamic posture that occurred ever so briefly while the suspect was falling.

The plaintiffs presented their own animated version of the shooting. But it was built backward from the alleged “execution shot,” which the plaintiffs claimed was fired after Carr had come to rest against the bench. In critiquing this scenario, Lewinski explained in detail why it was illogical and inaccurate and not based on sound principles. “They ignored science for the purpose of constructing a story that fit their conception of the shooting,” he says.

Among other things, Lewinski also testified about FSRC research that documents why the officers could not have instantly stopped shooting once Carr started to fall and was no longer an imminent threat. (This research is detailed in an article for The Police Marksman magazine titled “Time to Start Shooting, Time to Stop Shooting” and can be accessed through the FSRC website: www.forcescience.org. Click here to go directly to the article: http://forcescience.org/articles/tempestudy.pdf

A member of FSRC’s Technical Advisory Board, Dr. Paul Michel, an optometrist from Littleton, CO, also testified for the defense. He explained the ambient light levels that would have existed in the courtyard and how the darkened conditions would have affected the officers’ ability to immediately perceive details of the action.

Two other defense experts have recently been added to FSRC’s Technical Board. They are Greg Karim, a retired Oklahoma City cop now heading a regional ballistics lab in Austin, TX, who testified about shell-casing ejection patterns and other firearms-related technical material, and Joe Callanan, a former Los Angeles County (CA) Sheriff’s officer now with Specialized Training Consultants in Morro Bay, CA, who reviewed the police tactics used in trying to deal with Carr.

On Nov. 22, after days of testimony and arguments, the jury returned its verdict. Four long years after the shooting occurred, the officers were finally exonerated. The plaintiffs were granted nothing, and there was no reimbursement for the substantial funds the plaintiffs’ attorneys had put forth to prepare for trial.

This case, incidentally, is the third in which Lewinski has helped to successfully defend officers against Johnnie Cochran’s legal armada.

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.