Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Minneola, Kansas

Jim Wright, 67, from Minneola, Kansas, on 9 March 2021

Victim Info

  • Jim Wright
  • White/European American
  • 67
  • Male

Details

Wright's family contacted police concerned about his welfare, but Wright drove away when police arrived. Officers pursued Wright and eventually disabled his vehicle with spike strips. Wright then exited his vehicle allegedly holding a firearm, and officers ordered he drop it. Several officers then fired at Wright, killing him.

Additional Evidence

  • Jim Wright
  • 67
  • Male
  • White
  • US-283 and Ash St.
  • Minneola
  • KS
  • 67865
  • Clark
  • Meade County Sheriff's Office, Clark County Sheriff's Office, Ford County Sheriff's Office, Kansas Department of Wildlife, Parks and Tourism
  • KS0600000, KS0130000, KS0290000, KS0760200
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • gun
  • other
  • car
  • no
  • 6689
  • Rural
  • https://fatalencounters.org/wp-content/uploads/2021/03/James-Jim-Crosby-Wright.jpg
  • Mental Illness/Welfare Check
  • welfare check

Source

Source ID: 8800 - Mapping Police Violence

Cross References

This report has possible entries from multiple sources

BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65426. Submitted in Mainchain Tx A3C3E8C8BE726A42B52ABC9836BA0C7E4349AF6B1D963EBECAD311ADB06ED5B0, at block height 140525

Transaction details

Tx A3C3E8C8BE726A42B52ABC9836BA0C7E4349AF6B1D963EBECAD311ADB06ED5B0
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: mKLgMc81Qov1gYpWSkWtCuv+3LbsdlnB/K5RnjyTuEwa7s7SDmyqiyh9AR54ClV01u6Uh1WgUvEzTRRfUgKmlA==
Raw Tx data:

Hash Comparison

Hash stored in database: 1169e6386e63bc153b163775f74e76bbf557f72042133b42f459bbbef47a50ea

Hash from Mainchain Tx: 1169e6386e63bc153b163775f74e76bbf557f72042133b42f459bbbef47a50ea

Dynamically generated hash: 1169e6386e63bc153b163775f74e76bbf557f72042133b42f459bbbef47a50ea

Hashes Match?
YES

How is the comparison calculated?

The hash stored in the database is used as the identifier for this report, and can be seen in the URL. The hash from the Mainchain Tx is the hash sent to and stored on Mainchain. Finally, the "generated hash" is generated each time this page is loaded, using the same data used for the hash submitted to Mainchain.

Raw data used to generate the hash, using the Node.js crypto.createHash('sha256') algorithm: