CrashDNA

Crash data.
Real-world context.

Explore CrashDNA
Texas / City guides
PUBLIC DATA. LOCAL CONTEXT.

Abilene Crash Guide.

Jones and Taylor counties

Reported crash counts, locations and trends in Abilene.

Records through 2026-09-30 Source: TxDOT public records Prepared 2026-10-17

Choose a period, then select Update guide.

Guide figures: Oct 1, 2025 to Sep 30, 2026. Based on records available through Sep 30, 2026. The map uses a separate calendar year.

Reported crashes2,360 6.0% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes13 6 more13 vs. 7
Compared with Oct 1, 2024 to Sep 30, 2025
People killed13 6 more13 vs. 7
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured84 23.5% moreCompared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 6.0%.

Compared with Oct 1, 2024 to Sep 30, 2025. Counts alone do not tell us how risky a trip is.

Explore the data →
KNOW THE PLACE

Getting around Abilene

Abilene is a city in Jones and Taylor counties, Texas. Include the place and county when looking up local road notices, especially where another Texas community shares the same name. [1]

Location context, separate from the crash analysis below. Local road descriptions are added only after source review.

Local context sources
  1. U.S. Census Bureau · Texas place/county reference (2026)
  2. TxDOT · how to use DriveTexas for current conditions
THE LOCAL PICTURE

Abilene’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 2,360 reported crashes in Abilene. That is 150 fewer than the 2,510 recorded for the corresponding dates a year earlier—a 6.0% decrease in reported crashes.

South 1st Street appears repeatedly in the reports, with 92 crashes listed under that road name. The 4 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 199 of the 2,360 crashes in this guide.

Based on the public TxDOT records included in this guide. Counts describe reported crashes, not risk per trip or why a crash happened. Source, coverage and limitations →

WHERE IT HAPPENS

Explore Abilene’s reported crash locations.

Named areas with the most matching crashes. Choose an area to zoom in.

  1. The ranked areas appear when the map loads.
View the area data ↓

Approximate areas, not verified intersections. The list follows the map filters.

This map uses a calendar year, not the guide’s reporting period. The figures above cover Oct 1, 2025 to Sep 30, 2026 (2,360 crashes). The count below follows the selected map year and filters.

Loading crash map…

Loading the 2026 map. Records are available through 2026-09-30.

Background map: OpenStreetMap. Map tiles load automatically; your browser sends the provider your IP address and the requested map area.

Map area data & how locations are grouped

Numbers on markers are crash counts. Areas use a 0.002° grid (roughly 180–220 metres across in Texas), not verified intersections. Names use the most common recorded street or intersection-pair label in each area across the loaded history; they are not verified neighborhood boundaries. Several areas may share a road name. Missing-coordinate records remain in the totals.

THE LONGER VIEW

The same month, year over year

Compare seasonal patterns across 2022–2026. Each line is one year. Hollow points and dashed segments mark partial months; gaps are not treated as zero. Historical context stays visible when you change the guide’s reporting period.

20222023202420252026
070141211281JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 241 reported crashesFeb 2022: 235 reported crashesMar 2022: 234 reported crashesApr 2022: 279 reported crashesMay 2022: 249 reported crashesJun 2022: 206 reported crashesJul 2022: 217 reported crashesAug 2022: 226 reported crashesSep 2022: 277 reported crashesOct 2022: 279 reported crashesNov 2022: 278 reported crashesDec 2022: 246 reported crashesJan 2023: 270 reported crashesFeb 2023: 233 reported crashesMar 2023: 258 reported crashesApr 2023: 260 reported crashesMay 2023: 256 reported crashesJun 2023: 249 reported crashesJul 2023: 220 reported crashesAug 2023: 250 reported crashesSep 2023: 245 reported crashesOct 2023: 259 reported crashesNov 2023: 245 reported crashesDec 2023: 260 reported crashesJan 2024: 256 reported crashesFeb 2024: 229 reported crashesMar 2024: 255 reported crashesApr 2024: 257 reported crashesMay 2024: 281 reported crashesJun 2024: 209 reported crashesJul 2024: 204 reported crashesAug 2024: 261 reported crashesSep 2024: 254 reported crashesOct 2024: 262 reported crashesNov 2024: 228 reported crashesDec 2024: 261 reported crashesJan 2025: 221 reported crashesFeb 2025: 185 reported crashesMar 2025: 278 reported crashesApr 2025: 201 reported crashesMay 2025: 193 reported crashesJun 2025: 180 reported crashesJul 2025: 144 reported crashesAug 2025: 177 reported crashesSep 2025: 180 reported crashesOct 2025: 213 reported crashesNov 2025: 240 reported crashesDec 2025: 232 reported crashesJan 2026: 183 reported crashesFeb 2026: 178 reported crashesMar 2026: 212 reported crashesApr 2026: 159 reported crashesMay 2026: 193 reported crashesJun 2026: 147 reported crashesJul 2026: 165 reported crashesAug 2026: 230 reported crashesSep 2026: 208 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan241270256221183
Feb235233229185178
Mar234258255278212
Apr279260257201159
May249256281193193
Jun206249209180147
Jul217220204144165
Aug226250261177230
Sep277245254180208
Oct279259262213—
Nov278245228240—
Dec246260261232—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Abilene recorded 1,675 crashes, compared with 1,759 over the matching dates a year earlier. That is 4.8% fewer reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 4 PM.

Oct 1, 2025 to Sep 30, 2026 · Known hours only.

Time of day

010019912 AM: 43 reported crashes12 AM1 AM: 43 reported crashes2 AM: 39 reported crashes3 AM: 25 reported crashes3 AM4 AM: 16 reported crashes5 AM: 42 reported crashes6 AM: 67 reported crashes6 AM7 AM: 143 reported crashes8 AM: 109 reported crashes9 AM: 86 reported crashes9 AM10 AM: 99 reported crashes11 AM: 134 reported crashes12 PM: 155 reported crashes12 PM1 PM: 154 reported crashes2 PM: 145 reported crashes3 PM: 185 reported crashes3 PM4 PM: 199 reported crashes5 PM: 194 reported crashes6 PM: 120 reported crashes6 PM7 PM: 102 reported crashes8 PM: 70 reported crashes9 PM: 77 reported crashes9 PM10 PM: 70 reported crashes11 PM: 43 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM43113
1 AM43000
2 AM39002
3 AM25000
4 AM16002
5 AM42000
6 AM67003
7 AM143001
8 AM109114
9 AM86003
10 AM99002
11 AM134003
12 PM155113
1 PM154112
2 PM145223
3 PM185118
4 PM199112
5 PM1940010
6 PM120119
7 PM102119
8 PM70112
9 PM77227
10 PM70004
11 PM43002

Day of the week

0197394Sun: 239 reported crashesSun239Mon: 394 reported crashesMon394Tue: 362 reported crashesTue362Wed: 376 reported crashesWed376Thu: 331 reported crashesThu331Fri: 388 reported crashesFri388Sat: 270 reported crashesSat270
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun2391113
Mon3943314
Tue3622213
Wed376229
Thu3313311
Fri3882212
Sat2700012

Month by month

01202402025-10: 213 reported crashes10/252025-11: 240 reported crashes2025-12: 232 reported crashes12/252026-01: 183 reported crashes2026-02: 178 reported crashes02/262026-03: 212 reported crashes2026-04: 159 reported crashes04/262026-05: 193 reported crashes2026-06: 147 reported crashes06/262026-07: 165 reported crashes2026-08: 230 reported crashes08/262026-09: 208 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10213226
2025-11240117
2025-12232118
2026-01183116
2026-021781113
2026-03212227
2026-04159009
2026-05193117
2026-06147225
2026-07165006
2026-08230115
2026-09208115

Selected period; * partial month. Outlined bars mean missing coverage, not zero crashes.

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved148
  • Commercial vehicle involved123
  • Motorcycle involved72
  • Pedestrian involved32
  • Bicycle involved13

Crash counts, not people. Categories overlap—a crash can appear in more than one group.

View involvement & severity details

People killed or injured are totals for the whole crash, not necessarily people in the named travel mode.

Crash involvement categories; do not sum these rows
GroupCrashesFatal crashesPeople killedPeople seriously injured
Truck / truck-tractor involved148114
Commercial vehicle involved123114
Motorcycle involved728819
Pedestrian involved32227
Bicycle involved13003
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. South 1st Street92 crashes
  2. Buffalo Gap Road90 crashes
  3. South Clack Street80 crashes
  4. South Danville Drive66 crashes
  5. South 14th Street62 crashes

Oct 1, 2025 to Sep 30, 2026. Counts, not the chance of a crash on a trip. Street-name variants may split the same corridor. Short road labels are expanded for readability; the tables and CSV preserve recorded labels.

View all road rankings
Top 20 reported road labels by crash count
GroupCrashesFatal crashesPeople killedPeople seriously injured
S 1ST ST92004
BUFFALO GAP RD90112
S CLACK ST80001
S DANVILLE DR66000
S 14TH ST62002
AMBLER AVE57001
SOUTHWEST DR54002
SAYLES BLVD45110
S TREADAWAY BLVD43110
N JUDGE ELY BLVD42000
BARROW ST40111
PINE ST37110
US 8336002
S 7TH ST33006
N 10TH ST32000
IH 2030002
N MOCKINGBIRD LN30002
ANTILLEY RD29001
GRAPE ST29000
N TREADAWAY BLVD29001
Reported intersection pairs

Only records flagged as intersections with both street names. These are reported labels—not verified geographic intersections.

Top 20 reported street pairs by crash count
GroupCrashesFatal crashesPeople killedPeople seriously injured
INDUSTRIAL BLVD & S DANVILLE DR16000
S 1ST ST & SAYLES BLVD15001
S DANVILLE DR & SOUTHWEST DR13000
AMBLER AVE & N TREADAWAY BLVD11000
BUFFALO GAP RD & S CLACK ST11000
E AMBLER AVE & N JUDGE ELY BLVD9000
S 14TH ST & S DANVILLE DR9000
S 11TH ST & SAYLES BLVD8000
E HWY 80 & N JUDGE ELY BLVD7000
S 1ST ST & S WILLIS ST7001
AMBLER AVE & OLD ANSON RD6000
BARROW ST & S 14TH ST6001
CAMPUS CT & E AMBLER AVE6001
GRAPE ST & N 10TH ST6000
INDUSTRIAL BLVD & SAYLES BLVD6000
N 10TH ST & N WILLIS ST6000
RIDGEMONT DR & TURNER DR6000
ANTILLEY RD & BUFFALO GAP RD5000
BARROW ST & S 11TH ST5000
BUFFALO GAP RD & S 27TH ST5000
SOURCE & ATTRIBUTION

Cite this guide.

Using these figures? Keep the reporting period and source with them.

CrashDNA. Abilene Crash Guide. Abilene — Jones County and Taylor County, Texas. All reported crashes; selected reporting period 2025-10-01–2026-09-30. Analysis of available public Texas Department of Transportation (TxDOT) crash records. Snapshot prepared 2026-10-17. https://crashdna.com/texas/abilene/

Download selected-period CSVMethods & definitions

You can also select and copy the citation text above. Figures describe available records, not traffic-adjusted risk or independently verified complete reporting.

Methods, definitions and limitations

Abilene city · Jones County and Taylor County. Reported city code 2; county codes 127, 221. Current Census place identifier 4801000 (2026 reference). These identifiers reconcile the reported source labels, not independently geocoded historical boundaries.

Source: public Texas Department of Transportation (TxDOT) crash records loaded for this publication. Guide focus: All reported crashes. All displayed totals, historical comparisons, maps, rankings and CSV rows use this cohort. Selected reporting period: exact recorded city label ABILENE, Oct 1, 2025 to Sep 30, 2026. Each crash is counted once using its selected current record revision. This is not a metropolitan-area or police-agency-only filter.

Fatal crashes count events; deaths and serious injuries count people. Fatal and serious-injury crash groups use recorded severity codes 4 and 1. A crash can involve multiple vehicle or road-user types. Counts do not control for traffic or pedestrian activity, do not establish fault, and are not crash rates.

In the selected reporting period, 72 records lack usable Texas-range coordinates for Oct 1, 2025 to Sep 30, 2026 (the guide period, not the separate map year); 0 lack a usable hour; 61 lack a usable road label. 1,462 records are not assigned a usable intersection pair (including non-intersection crashes). Unknown categories remain in totals but not narrative rankings. Coordinates are not independently verified.

Latest 12 months means the latest available calendar month plus the preceding 11 months, clipped to loaded coverage; an unfinished final month is partial. Year to date means January 1 through the latest loaded date in that year, not through today. Historical charts and the map use the wider loaded history (Jan 1, 2022 to Sep 30, 2026); the monthly year-over-year chart shows up to five recent years. Map year, crash-type and outcome filters apply only to the map and its linked area table. Every matching record with coordinates contributes; there is no top-100 cap. Map locations are approximate grid centres, not exact crash sites. Area names use reported road labels, not verified neighborhoods. CSV contains aggregate tables, not individual crash records.

Loaded extraction intervals span the selected period. Source intervals do not guarantee complete reporting. New reports and amendments can change earlier months. Prepared 2026-10-17T22:01:25.118Z. Approved snapshots change only after an editor publishes an update.

Source extraction intervals
  • 2022-01-01 – 2022-03-01 · extracted 20260910100040
  • 2022-03-02 – 2022-04-26 · extracted 20260910100040
  • 2022-04-27 – 2022-06-22 · extracted 20260910100040
  • 2022-06-23 – 2022-08-22 · extracted 20260910100040
  • 2022-08-23 – 2022-10-16 · extracted 20260910100040
  • 2022-10-17 – 2022-12-08 · extracted 20260910100040
  • 2022-12-09 – 2022-12-31 · extracted 20260910100040
  • 2023-01-01 – 2023-02-27 · extracted 20260910100112
  • 2023-02-28 – 2023-04-24 · extracted 20260910100112
  • 2023-04-01 – 2023-04-24 · extracted 20260910100112
  • 2023-04-25 – 2023-06-19 · extracted 20260910100112
  • 2023-06-20 – 2023-08-17 · extracted 20260910100112
  • 2023-08-18 – 2023-10-12 · extracted 20260910100112
  • 2023-10-13 – 2023-12-05 · extracted 20260910100112
  • 2023-12-06 – 2023-12-31 · extracted 20260910100112
  • 2024-01-01 – 2024-02-29 · extracted 20260828124847
  • 2024-03-01 – 2024-04-26 · extracted 20260828124847
  • 2024-04-27 – 2024-06-22 · extracted 20260828124847
  • 2024-06-23 – 2024-08-22 · extracted 20260828124847
  • 2024-08-23 – 2024-10-16 · extracted 20260828124847
  • 2024-10-17 – 2024-12-09 · extracted 20260828124847
  • 2024-12-10 – 2024-12-31 · extracted 20260828124847
  • 2025-01-01 – 2025-03-05 · extracted 20260910100224
  • 2025-03-06 – 2025-05-01 · extracted 20260910100224
  • 2025-05-02 – 2025-06-29 · extracted 20260910100224
  • 2025-06-30 – 2025-08-29 · extracted 20260910100224
  • 2025-08-30 – 2025-10-23 · extracted 20260910100224
  • 2025-10-24 – 2025-12-16 · extracted 20260910100224
  • 2025-12-17 – 2025-12-31 · extracted 20260910100224
  • 2026-01-01 – 2026-03-03 · extracted 20260910100333
  • 2026-03-04 – 2026-04-30 · extracted 20260910100333
  • 2026-05-01 – 2026-06-27 · extracted 20260910100333
  • 2026-06-28 – 2026-08-29 · extracted 20260910100333
  • 2026-08-30 – 2026-08-31 · extracted 20260910100333
  • 2026-09-01 – 2026-09-30 · extracted 20261010194744

Download selected-period CSV · Download all-history CSV

CSV download
A table file you can open in a spreadsheet. Downloads contain grouped counts, not individual crash reports.
Crash count versus risk
A count tells you how many crashes were reported. Without knowing how much people drove, walked or cycled, it cannot tell you how likely a crash was on a trip.
Location identifiers and severity codes
These are source-system labels used to match places and classify recorded outcomes. They are not independent proof of a city boundary or the cause of a crash.
Back to top ↑

Public records. A clearer local picture.

Explore the patterns in another Texas community.

Explore another city →