James "Jim" Crosby Wright, 67, from Minneola, Kansas, on 9 March 2021
Victim Info
- James "Jim" Crosby Wright
- White/European American
- 67
- Male
Details
Around 7 p.m., Jim Wright's family member reported to the Meade County Sheriff's Office that they were concerned about his welfare. Deputies found him near the Clark County and Meade County line. Wright fled in his SUV, and deputies pursued. Deputies deployed spike strips, and Wright's SUV slowed and came to a stop. Wright got out of his vehicle holding a firearm. Deputies and officers gave commands for him to drop the gun. Around 9:40 p.m., officers from various agencies shot and killed him.Primary Evidence & Links
Additional Evidence
- James "Jim" Crosby Wright
- 67
- Male
- European-American/White
- European-American/White
- Not imputed
- US-283 and Ash St.
- Minneola
- KS
- 67865
- Clark
- 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
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/03/James-Jim-Crosby-Wright.jpg
Source
Source ID: 29772 - Fatal Encounters
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65429. Submitted in Mainchain Tx 51DBAC733483D3CDE929B28486D357FDF1701DDF58213A8B54233CB9DE5719E5, at block height 140528
Transaction details
Tx 51DBAC733483D3CDE929B28486D357FDF1701DDF58213A8B54233CB9DE5719E5
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: /f1KRqdiXjIRcTU06FWh2XMPbHBsNcO/5pZwq3buzZBKmLQ+FhTncsIZufiaBNDMy4uggjjW/1D8CeOSYnK85w==
Raw Tx data:
Hash Comparison
Hash stored in database: 41af181d7a3b6e66844c9c22187c37cbd80241c96282941c78e2c77654587fa6
Hash from Mainchain Tx: 1655513510
Dynamically generated hash: b981d4332fed4ff67a44034d0bc1fdf8b1e7e38c3259c66f796147b55eed89bf
Hashes Match?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: