CrashDNA

Crash data.
Real-world context.

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

Pflugerville Crash Guide.

Travis and Williamson counties

Reported crash counts, locations and trends in Pflugerville.

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 crashes923 8.8% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes6 3 more6 vs. 3
Compared with Oct 1, 2024 to Sep 30, 2025
People killed6 3 more6 vs. 3
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured17 No change17 vs. 17
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 8.8%.

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 Pflugerville

Pflugerville is a city in Travis and Williamson 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

Pflugerville’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 923 reported crashes in Pflugerville. That is 75 more than the 848 recorded for the corresponding dates a year earlier—a 8.8% increase in reported crashes.

Farm-to-Market Road 685 appears repeatedly in the reports, with 111 crashes listed under that road name. The 6 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 94 of the 923 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 Pflugerville’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 (923 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
0265177102JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 63 reported crashesFeb 2022: 44 reported crashesMar 2022: 68 reported crashesApr 2022: 73 reported crashesMay 2022: 80 reported crashesJun 2022: 55 reported crashesJul 2022: 54 reported crashesAug 2022: 85 reported crashesSep 2022: 73 reported crashesOct 2022: 61 reported crashesNov 2022: 61 reported crashesDec 2022: 73 reported crashesJan 2023: 80 reported crashesFeb 2023: 46 reported crashesMar 2023: 77 reported crashesApr 2023: 75 reported crashesMay 2023: 76 reported crashesJun 2023: 65 reported crashesJul 2023: 74 reported crashesAug 2023: 78 reported crashesSep 2023: 70 reported crashesOct 2023: 90 reported crashesNov 2023: 67 reported crashesDec 2023: 77 reported crashesJan 2024: 64 reported crashesFeb 2024: 66 reported crashesMar 2024: 63 reported crashesApr 2024: 56 reported crashesMay 2024: 85 reported crashesJun 2024: 73 reported crashesJul 2024: 76 reported crashesAug 2024: 102 reported crashesSep 2024: 65 reported crashesOct 2024: 92 reported crashesNov 2024: 79 reported crashesDec 2024: 78 reported crashesJan 2025: 56 reported crashesFeb 2025: 60 reported crashesMar 2025: 79 reported crashesApr 2025: 75 reported crashesMay 2025: 66 reported crashesJun 2025: 58 reported crashesJul 2025: 67 reported crashesAug 2025: 72 reported crashesSep 2025: 66 reported crashesOct 2025: 78 reported crashesNov 2025: 82 reported crashesDec 2025: 89 reported crashesJan 2026: 85 reported crashesFeb 2026: 59 reported crashesMar 2026: 82 reported crashesApr 2026: 81 reported crashesMay 2026: 83 reported crashesJun 2026: 70 reported crashesJul 2026: 70 reported crashesAug 2026: 69 reported crashesSep 2026: 75 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan6380645685
Feb4446666059
Mar6877637982
Apr7375567581
May8076856683
Jun5565735870
Jul5474766770
Aug85781027269
Sep7370656675
Oct61909278—
Nov61677982—
Dec73777889—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Pflugerville recorded 674 crashes, compared with 599 over the matching dates a year earlier. That is 12.5% more reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 6 PM.

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

Time of day

0479412 AM: 11 reported crashes12 AM1 AM: 8 reported crashes2 AM: 14 reported crashes3 AM: 14 reported crashes3 AM4 AM: 13 reported crashes5 AM: 10 reported crashes6 AM: 25 reported crashes6 AM7 AM: 27 reported crashes8 AM: 37 reported crashes9 AM: 29 reported crashes9 AM10 AM: 29 reported crashes11 AM: 32 reported crashes12 PM: 42 reported crashes12 PM1 PM: 35 reported crashes2 PM: 49 reported crashes3 PM: 66 reported crashes3 PM4 PM: 84 reported crashes5 PM: 85 reported crashes6 PM: 94 reported crashes6 PM7 PM: 73 reported crashes8 PM: 40 reported crashes9 PM: 46 reported crashes9 PM10 PM: 36 reported crashes11 PM: 24 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM11000
1 AM8001
2 AM14000
3 AM14110
4 AM13000
5 AM10000
6 AM25000
7 AM27000
8 AM37000
9 AM29111
10 AM29001
11 AM32001
12 PM42000
1 PM35000
2 PM49001
3 PM66002
4 PM84110
5 PM85000
6 PM94004
7 PM73000
8 PM40001
9 PM46001
10 PM36110
11 PM24224

Day of the week

077154Sun: 97 reported crashesSun97Mon: 127 reported crashesMon127Tue: 138 reported crashesTue138Wed: 154 reported crashesWed154Thu: 135 reported crashesThu135Fri: 139 reported crashesFri139Sat: 133 reported crashesSat133
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun97114
Mon127224
Tue138111
Wed154001
Thu135221
Fri139003
Sat133003

Month by month

045892025-10: 78 reported crashes10/252025-11: 82 reported crashes2025-12: 89 reported crashes12/252026-01: 85 reported crashes2026-02: 59 reported crashes02/262026-03: 82 reported crashes2026-04: 81 reported crashes04/262026-05: 83 reported crashes2026-06: 70 reported crashes06/262026-07: 70 reported crashes2026-08: 69 reported crashes08/262026-09: 75 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-1078111
2025-1182006
2025-1289001
2026-0185223
2026-0259000
2026-0382003
2026-0481000
2026-0583111
2026-0670110
2026-0770111
2026-0869001
2026-0975000

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved78
  • Commercial vehicle involved33
  • Motorcycle involved12
  • Bicycle involved11
  • Pedestrian involved2

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 involved78112
Commercial vehicle involved33111
Motorcycle involved12114
Bicycle involved11000
Pedestrian involved2001
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. Farm-to-Market Road 685111 crashes
  2. North Heatherwilde Boulevard72 crashes
  3. East Pecan Street59 crashes
  4. West Pecan Street53 crashes
  5. East Pflugerville Parkway40 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
FM 685111333
N HEATHERWILDE BLVD72002
E PECAN ST59000
W PECAN ST53002
E PFLUGERVILLE PKWY40111
KELLY LN40000
W PFLUGERVILLE PKWY35000
SH 13028112
DESSAU RD27001
WEISS LN23001
N SH 13022000
S HEATHERWILDE BLVD18001
A W GRIMES BLVD15000
COLORADO SAND DR15000
E WELLS BRANCH PKWY15000
GRAND AVENUE PKWY15000
WILKE LN15001
SH 4511000
NEW MEISTER LN9000
FM 18258000
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
N HEATHERWILDE BLVD & WILKE LN17001
A W GRIMES BLVD & SCHULTZ LN10000
FM 685 & KELLY LN10000
GRAND AVENUE PKWY & W PFLUGERVILLE PKWY10000
E PFLUGERVILLE PKWY & FM 6858111
COPPER MINE DR & FM 6857000
E PFENNIG LN & FM 6857000
KELLY LN & WEISS LN7000
N HEATHERWILDE BLVD & W PECAN ST7001
N HEATHERWILDE BLVD & W PFLUGERVILLE PKWY7000
COLORADO SAND DR & LONE STAR RANCH BLVD6000
E PECAN ST & FM 6856000
E PECAN ST & SUN LIGHT NEAR WAY6000
N HEATHERWILDE BLVD & W BLACK LOCUST DR5000
S HEATHERWILDE BLVD & W OLYMPIC DR5000
AUTUMN SLATE DR & COLORADO SAND DR4000
DESSAU RD & E PECAN ST4000
E PFLUGERVILLE PKWY & PFLUGER FARM LN4000
FALCON POINTE BLVD & KELLY LN4000
FM 685 & OLD AUSTIN HUTTO RD4000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Pflugerville Crash Guide. Pflugerville — Travis County and Williamson 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/pflugerville/

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

Pflugerville city · Travis County and Williamson County. Reported city code 330; county codes 227, 246. Current Census place identifier 4857176 (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 PFLUGERVILLE, 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, 25 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; 10 lack a usable road label. 515 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:26:56.791Z. 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 →