FirstAlerts

Knoxville crime scene technician wounded while processing shooting scene

Police say Forensics Unit technician Cody Lawson has undergone surgery and remains hospitalized after a man fired at officers working a South Knoxville scene just after midnight; a 35-year-old suspect is in custody.

By AI ReporterFirst reported Jul 13, 2026, 4:25 a.m. ETWritten Aug 15, 2026, 5:27 p.m. ET

More on this incident

A crime scene technician was shot and wounded while working an earlier shooting scene in South , the department said. KPD identified the wounded staff member as Crime Scene Technician Cody Lawson, and said as of 11:50 a.m. on July 13, 2026 that she had undergone surgery and remained hospitalized. According to the , officers responded at around 11 p.m. on Sunday, July 12, 2026 to a report that shots had been fired into an occupied home at 2300 Jones Street. No injuries were reported in that shooting. KPD officers and Forensics Unit staff were processing the scene and canvassing for evidence when, just after midnight, a man fired multiple shots at a KPD Officer and Crime Scene Technician from an adjacent wood line, the department said. KPD said the man has since been identified as . Officers converged on the area after the gunfire and located Rudd hiding in the woods, where he surrendered, according to the department. He is . The stated that Rudd fired multiple rounds and said it booked him on four counts of employing a firearm during the commission of a felony. Nothing in the department's account addresses a motive. "This incident demonstrates the substantial risk our officers and staff take every day and every shift," Chief Paul Noel said in the department's statement. "It is only by the grace of God that Cody or one of our officers was not killed today, and I am profoundly grateful for that. Nonetheless, Cody has a long road of recovery ahead. We will support her, her family and her colleagues in the Forensics Unit however we can along the way, and we ask that the community uplift Cody in the days, weeks and months ahead."

Was this report accurate and useful?

Sources

Revision history

  1. Version 115 Aug 2026, 21:27current

    First published.

  2. Version 115 Aug 2026, 21:37current

    First published.

  3. Version 115 Aug 2026, 21:34current

    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.