Denver traffic crash report: Lincoln Park and Hale move

Photo: Bimmer Torres / CC BY — Indio Chichen Itza

Plan for different crash counts in a few neighborhoods this week, not a citywide change. The Denver traffic crash report for Friday, October 2, 2026 to Thursday, October 8, 2026 shows Lincoln Park at 12 crashes against 7 the week before, and Hale at 1 against 10, according to the City and County of Denver open data. Hampden went from 10 to 4, Globeville from 11 to 5 and Civic Center from 10 to 5. Each of these is a swing of a handful of crashes, so none reads as a surge.

Drivers met slightly lighter crash totals than the week before: 399 against 424, down 5.9%, and down 5.7% on the 423 of the same week last year, per the open data. The eight weekly totals shown in the figure range from 394 to 432.

Serious-injury crashes moved the other way, up 400% on the week before. The same week last year also had 10, so the week before was the unusual one. No crash with a death appears this week; last year's same week had 1.

Crashes involving a person on foot numbered 9, up 28.6% on the week before's 7 and down 35.7% on last year's 14. Those involving a person on a bicycle matched last year's 4. The dataset records that a person on foot or on a bicycle was involved; it does not say who was at fault.

Central Park logged 28 crashes, down from 30, at 5.8 crashes per square kilometre. Five Points logged 15, down from 18, and Gateway Green Valley Ranch logged 15, up from 12.

Cherry Creek went from 1 crash to 9. That is an 800% rise built on a handful of crashes, at 6.3 crashes per square kilometre.

Baker is the spotlight. It logged 21 crashes, down from 24 the week before, at 13.2 crashes per square kilometre. The Denver traffic accidents map shows the locations. A neighborhood count measures how much traffic passes through as much as risk, so it shows which area had the most reports and nothing more.

For the twelve months from Thursday, October 9, 2025 to Thursday, October 8, 2026, I25 Hwynb / W 6th Ave leads the address list with 222 crashes. I70 Hwyeb / N Peoria St follows with 108, and N Federal Blvd / W 6th Ave has 95.

I70 Hwyeb also appears at N Havana St (80) and N Pecos St (69), and I225 Hwysb / I70 Hwyeb has 80. A high count shows where much traffic passes; it does not rank danger, and an address with many crashes is a design question, not a driver's failing.

A 33-year-old man was killed Saturday evening after being struck by two vehicles while crossing Interstate 76 in Brighton, according to police, KDVR reported. Brighton Police Department said an eastbound vehicle hit the pedestrian, then a second vehicle in the same direction. The investigation is ongoing.

Colorado State Patrol seeks a Chevrolet driver who fled after hitting a motorcycle near South Rosemary Street, Hoodline reported. A passenger was seriously injured, according to the report.

Compare next week against 399 citywide crashes and 10 serious-injury crashes. Lincoln Park's 12 and Hale's 1 will show whether the moves hold. The Denver crime report covers the week's police-reported figures. Check Brighton Police Department and Colorado State Patrol updates for both incidents.

How many crashes did Denver have this week? Police logged 399 crashes, against 424 the week before.

Which Denver neighborhood had the most crashes this week? Central Park, with 28 crashes. Baker followed with 21. Counts are not rates.

Where does the Denver crash data come from? From the City and County of Denver open data portal, with a second copy on the Colorado data portal.

Which Denver addresses have the most recorded crashes? I25 Hwynb / W 6th Ave leads over twelve months, followed by I70 Hwyeb / N Peoria St and N Federal Blvd / W 6th Ave. The list counts crashes and does not rank danger.

The figures are crashes reported to Denver Police and published in the city's open data, in a rolling extract also on the Colorado data portal. The week covered runs Friday, October 2, 2026 to Thursday, October 8, 2026.

The comparison weeks are Friday, September 25, 2026 to Thursday, October 1, 2026, and Thursday, October 2, 2025 to Wednesday, October 8, 2025. A crash never reported, or not yet published by the city, is not counted.

Counts are not adjusted for traffic volume, so they cannot say which place is more dangerous. The dataset does not say who was at fault, and this report does not unless a cited police statement does.

Errors are corrected in public; send one to hello@303happenings.com.