ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Family Autopsy Appears to Conflict with Witness Account in Michael Brown Shooting

Updated on August 19, 2014
We need answers for Michael Brown, we need answers for everyone involved.  We need them to be honest answers, based in fact and supported with evidence, not with emotion, opinion and hyperbole.
We need answers for Michael Brown, we need answers for everyone involved. We need them to be honest answers, based in fact and supported with evidence, not with emotion, opinion and hyperbole. | Source

Dorian Johnson was quickly seen on CNN with his account where he stated there was an altercation between the officer and his friend, Mike Brown. He stated the physical confrontation was initiated by the officer who reached out of the vehicle through the window, grabbed Mr. Brown by the neck and tried to drag him into the window as Mr. Brown tried to pull away. Mr. Johnson states during this interaction the officer was threatening to shoot Mr. Brown and had drawn his weapon.

The theme of the story in the media however has focused on this moment a little differently -- on the claim that the officer said Mr. Brown was attempting to take his gun and the family and witnesses -- who do, by the way, to a person, state there was an altercation of some kind at the vehicle between the two men -- say this simply is not true. That Mike Brown would never have attempted to take the officer's gun and the officer is lying in order to give cause for his later actions.

Mr. Johnson then goes on in his publicized TV interview to state that Mr. Brown, shot during the vehicle altercation, ran away from the vehicle. They both ran. As they were running away, key point here, away, Mr. Brown was again shot. This is according to another witness as well that was further down the street. It was only at that point that Mike Brown, according to Dorian Johnson, turned around, faced the officer, raised his hands, said "don't shoot", and was shot several more times.

During all this, there has been a video floating around mostly right wing sites which has been overlooked. I've seen no media either give credence to or debunk the veracity of this video, but you can hear a conversation ongoing in the background that appears to be from a witness to the incident that appears to be indicating Brown was advancing on the officer and failing to stop, not holding his hands up, standing still and saying, "please don't shoot."

With much ado, the family came forward yesterday to announce their private autopsy was complete and as they disclosed the results, several things were in disturbing contrast to witness statements.

First, they stated that there was no evidence of any physical altercation between the officer and Mike Brown. There was no bruising or injury around the neck. They're painting this as an indication that an altercation did not happen. This is even more a problem for them because it's being reported that the officer did have "swelling of the face" and was seen at the hospital after the incident. They have not released any more information on the officer's injuries.

So the altercation happened, it appears that Brown was not grabbed and manhandled by the neck as initially claimed, however, current information still indicates the officer did sustain injuries to the face, we can assume at this point, as if he was punched during an altercation.

The second glaring contrast was the claim by witnesses, all of which have been reported as friends of Mr. Brown, is that there was not a single entry wound indicating that Mr. Brown had been shot from behind. Not one. The wounds were all clearly sustained from the front as he was either standing or moving towards the officer (depending on the account) or as he was falling to the ground.

There is still a lot of evidence that we are waiting to see.

Witnesses all state there was a single shot fired in the vehicle. It may be important to see the trajectory of that bullet, it could help determine if the gun was in or near the holster as the officer appears to be claiming, or if the gun was drawn as Mr. Johnson has been claiming.

We are waiting to hear exactly what the injuries sustained by the officer and what the evidence says about how they were sustained.

We have 2 other autopsies we have yet to see the results of; do they concur or are there deviations in what each pathologist sees? We have toxicology results that we're waiting on -- the officer thought that Mr. Brown might be "on something" given his responses and behaviors. Is this true or simply a perception or maybe even an excuse?

Right now, the media needs to stop with the moving data. When information conflicts, on either side of the story, it needs to be pointed out. If we're going to insist on trying this in the court of public opinion, the media owes the public responsible fact finding and not compassionate moderation.


    0 of 8192 characters used
    Post Comment

    • Pragmatic Politic profile imageAUTHOR

      Pragmatic Politic 

      4 years ago from United States

      Natemims, I see them as conflicting because the autopsy indicated no damage, injury, bruising or other markings from being grabbed around the neck and pulled forward while trying to pull away. To be fair, it's possible a contact like that would leave no indication. Without seeing what happened and only hearing the description from Dorian Johnson, it's hard to tell.

      Also the claim by Dorian and other witnesses that Mike Brown was shot in the back at least once, THEN turned around and put his hands up. Now there is no proof at this point that the officer didn't shoot while Brown's back was turned, but clearly he was not shot while in that position. Again, depending on witness accounts can be difficult, particularly if there are conflicting reports as there increasingly seem to be.

      The hard part of this is -- did they or did they not attempt to take the officers gun in a confrontation in the vehicle? If they did, the law states that it doesn't matter if Brown was running away, if the did not, it does matter and puts far more blame on the officer.

      I'm interested in knowing the scene forensics at this point, specifically where the alleged fired bullet went in the vehicle and what it's trajectory was -- that may or may not give us a little bit clearer picture.

    • natemims profile image

      Nate Mims 

      4 years ago from Iowa City Iowa

      I didn't see the results as contradicting. I also didn't see them as fully supportive either. They just were. A shot through the very top of the head. The fact that there was no swelling or signs of struggle to does that coincide with him attacking the officer and causing swelling to his head? The pathologist said the shot to his arm could have come from either front or seems everyone is doing their fair share of selective interpretation.

    • Pragmatic Politic profile imageAUTHOR

      Pragmatic Politic 

      4 years ago from United States

      We have a lot of information, so little of it vetted at this point. It feels like the media continues to move the goal posts based on unvetted, unproven information while ignoring that nearly the entire story from the other side has yet to be released and that the incident is still under investigation to see what evidence exists that would support either side of the story.

    • mdscoggins profile image

      Michelle Scoggins 

      4 years ago from Fresno, CA

      Thank you it seems that this situation is completely out of control. There is always a problem when people are quick to react without the facts and in this case a lot has been destroyed on the assumption of police brutality and racial profiling. Sad!!


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)