One killed, two injured in Fayette Street shooting in Martinsville
Martinsville police identified the man who died as D'Sean Jones after officers responded to a report of shots fired early on Aug. 1, 2026.
2 reports on this incident · first at Aug 7, 2026, 9:21 a.m. ET
Earlier reports
Aug 7, 2026, 9:21 a.m. ETFirst report
One killed, two injured in early-morning Martinsville shooting
One person was killed and two others were injured in a shooting in Martinsville, Virginia, early on Aug. 1, 2026, according to a Martinsville Police Department news release reported by the Martinsville Bulletin.
Martinsville police identified the man who died as D'Sean Jones. Officers received a report of shots fired at 4:16 a.m. and found Jones dead when they arrived, according to the department's news release. Emergency dispatch information indicated that a first report came in at approximately 4:12 a.m., initially describing three people shot, prompting a significant response from police and emergency personnel. Police have not released the identities of the two people reported injured.
Police said Fayette Street was expected to remain closed to through traffic between High and Peters streets while investigators processed the scene. The Martinsville Police Department is the only responding agency named in the release.
The investigation remains open. No cause or circumstances have been determined, and police have not said whether anyone has been taken into custody.
Was this report accurate and useful?
Sources
- Martinsville shooting: Danville man killed, 2 women woundedmartinsvillebulletin.com
Revision history
- Version 47 Aug 2026, 13:21current
No new facts; headline and standfirst added, body unchanged.
- Version 47 Aug 2026, 13:21current
No new facts; added headline and standfirst and moved the responding-agency line ahead of the note that police have released no further details.
- Version 34 Aug 2026, 23:23
Added headline and standfirst summarizing the identification and the police-stated toll; body unchanged.
- Version 34 Aug 2026, 23:28
Removed the crisis-resource line, which was not supported by facts on the record, and added a headline and standfirst.
- Version 24 Aug 2026, 20:33
No new information released by police; headline and standfirst added and wording on the open investigation tightened.
- Version 24 Aug 2026, 22:51
Restructured for clarity, added Martinsville as the city and named the responding agency; casualty figures and attribution unchanged.
- Version 14 Aug 2026, 20:09
First published.
- Version 14 Aug 2026, 22:48
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.