CrashDNA

Crash data.
Real-world context.

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

Lake Jackson Crash Guide.

Brazoria County

Reported crash counts, locations and trends in Lake Jackson.

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 crashes805 7.6% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes0 No change0 vs. 0
Compared with Oct 1, 2024 to Sep 30, 2025
People killed0 No change0 vs. 0
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured9 10 fewer9 vs. 19
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 7.6%.

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 Lake Jackson

Lake Jackson is a city in Brazoria County, 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

Lake Jackson’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 805 reported crashes in Lake Jackson. That is 57 more than the 748 recorded for the corresponding dates a year earlier—a 7.6% increase in reported crashes.

West 332 Highway appears repeatedly in the reports, with 103 crashes listed under that road name. The 5 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 84 of the 805 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 Lake Jackson’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 (805 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
021426384JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 61 reported crashesFeb 2022: 51 reported crashesMar 2022: 50 reported crashesApr 2022: 63 reported crashesMay 2022: 71 reported crashesJun 2022: 58 reported crashesJul 2022: 65 reported crashesAug 2022: 71 reported crashesSep 2022: 73 reported crashesOct 2022: 83 reported crashesNov 2022: 66 reported crashesDec 2022: 81 reported crashesJan 2023: 69 reported crashesFeb 2023: 51 reported crashesMar 2023: 70 reported crashesApr 2023: 60 reported crashesMay 2023: 77 reported crashesJun 2023: 57 reported crashesJul 2023: 59 reported crashesAug 2023: 52 reported crashesSep 2023: 46 reported crashesOct 2023: 50 reported crashesNov 2023: 55 reported crashesDec 2023: 73 reported crashesJan 2024: 41 reported crashesFeb 2024: 55 reported crashesMar 2024: 65 reported crashesApr 2024: 42 reported crashesMay 2024: 61 reported crashesJun 2024: 52 reported crashesJul 2024: 44 reported crashesAug 2024: 58 reported crashesSep 2024: 68 reported crashesOct 2024: 80 reported crashesNov 2024: 76 reported crashesDec 2024: 58 reported crashesJan 2025: 35 reported crashesFeb 2025: 64 reported crashesMar 2025: 64 reported crashesApr 2025: 67 reported crashesMay 2025: 54 reported crashesJun 2025: 65 reported crashesJul 2025: 62 reported crashesAug 2025: 61 reported crashesSep 2025: 62 reported crashesOct 2025: 68 reported crashesNov 2025: 55 reported crashesDec 2025: 73 reported crashesJan 2026: 54 reported crashesFeb 2026: 60 reported crashesMar 2026: 69 reported crashesApr 2026: 84 reported crashesMay 2026: 69 reported crashesJun 2026: 67 reported crashesJul 2026: 73 reported crashesAug 2026: 75 reported crashesSep 2026: 58 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan6169413554
Feb5151556460
Mar5070656469
Apr6360426784
May7177615469
Jun5857526567
Jul6559446273
Aug7152586175
Sep7346686258
Oct83508068—
Nov66557655—
Dec81735873—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Lake Jackson recorded 609 crashes, compared with 534 over the matching dates a year earlier. That is 14.0% more reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 5 PM.

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

Time of day

0428412 AM: 13 reported crashes12 AM1 AM: 5 reported crashes2 AM: 2 reported crashes3 AM: 5 reported crashes3 AM4 AM: 3 reported crashes5 AM: 15 reported crashes6 AM: 13 reported crashes6 AM7 AM: 22 reported crashes8 AM: 23 reported crashes9 AM: 30 reported crashes9 AM10 AM: 31 reported crashes11 AM: 45 reported crashes12 PM: 74 reported crashes12 PM1 PM: 58 reported crashes2 PM: 74 reported crashes3 PM: 68 reported crashes3 PM4 PM: 82 reported crashes5 PM: 84 reported crashes6 PM: 48 reported crashes6 PM7 PM: 31 reported crashes8 PM: 32 reported crashes9 PM: 23 reported crashes9 PM10 PM: 14 reported crashes11 PM: 10 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM13002
1 AM5001
2 AM2000
3 AM5000
4 AM3000
5 AM15000
6 AM13000
7 AM22000
8 AM23000
9 AM30000
10 AM31000
11 AM45000
12 PM74000
1 PM58000
2 PM74001
3 PM68000
4 PM82001
5 PM84001
6 PM48002
7 PM31000
8 PM32000
9 PM23001
10 PM14000
11 PM10000

Day of the week

067134Sun: 76 reported crashesSun76Mon: 104 reported crashesMon104Tue: 117 reported crashesTue117Wed: 125 reported crashesWed125Thu: 124 reported crashesThu124Fri: 134 reported crashesFri134Sat: 125 reported crashesSat125
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun76003
Mon104001
Tue117000
Wed125001
Thu124000
Fri134003
Sat125001

Month by month

042842025-10: 68 reported crashes10/252025-11: 55 reported crashes2025-12: 73 reported crashes12/252026-01: 54 reported crashes2026-02: 60 reported crashes02/262026-03: 69 reported crashes2026-04: 84 reported crashes04/262026-05: 69 reported crashes2026-06: 67 reported crashes06/262026-07: 73 reported crashes2026-08: 75 reported crashes08/262026-09: 58 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-1068001
2025-1155001
2025-1273000
2026-0154000
2026-0260003
2026-0369001
2026-0484001
2026-0569000
2026-0667001
2026-0773000
2026-0875001
2026-0958000

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved33
  • Commercial vehicle involved11
  • Motorcycle involved10
  • Pedestrian involved8
  • Bicycle involved6

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 involved33000
Commercial vehicle involved11000
Motorcycle involved10002
Pedestrian involved8000
Bicycle involved6002
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. West 332 Highway103 crashes
  2. Oyster Creek Drive92 crashes
  3. East 332 Highway61 crashes
  4. Farm-to-Market Road 200442 crashes
  5. 288 Highway34 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
W 332 HWY103001
OYSTER CREEK DR92001
E 332 HWY61001
FM 200442000
288 HWY34001
LAKE RD22000
W SH 33220000
SH 28819001
OAK DR17000
N DIXIE DR10000
S OAK DR10000
E SH 3329000
HWY 332 W9000
THIS WAY9000
W PLANTATION DR9000
332 HWY8000
GARLAND DR8000
SH 332 W8000
ABNER JACKSON PKWY7000
CIRCLE WAY7000
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
FM 2004 & LAKE RD7000
288 HWY & W 332 HWY6000
ANY WAY ST & OYSTER CREEK DR4000
E 332 HWY & W PLANTATION DR4000
LAKE RD & W 332 HWY4000
N SH 288 & OYSTER CREEK DR4000
W 332 HWY & W 332 HWY4001
288 HWY & FM 20043000
E 332 HWY & OYSTER CREEK DR3000
E 332 HWY & W 332 HWY3000
FM 2004 & N YAUPON ST3000
2004 & 288 HWY2000
288 HWY & OYSTER CREEK DR2000
332 HWY & OYSTER CREEK DR2000
CENTER WAY & CIRCLE WAY2000
CIRCLE WAY & THAT WAY2000
CR 400 & FM 20042000
DIXIE DR & OYSTER CREEK DR2000
E 332 HWY & OAK DR2000
E 332 HWY & THIS WAY2000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Lake Jackson Crash Guide. Lake Jackson — Brazoria 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/lake-jackson/

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

Lake Jackson city · Brazoria County. Reported city code 248; county codes 20. Current Census place identifier 4840588 (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 LAKE JACKSON, 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, 239 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; 19 lack a usable road label. 598 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:19:18.617Z. 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 →