CrashDNA

Crash data.
Real-world context.

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

League City Crash Guide.

Galveston and Harris counties

Reported crash counts, locations and trends in League City.

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,020 5.4% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes4 2 more4 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People killed4 2 more4 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured31 13.9% fewerCompared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 5.4%.

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 League City

League City is a city in Galveston and Harris 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

League City’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 2,020 reported crashes in League City. That is 103 more than the 1,917 recorded for the corresponding dates a year earlier—a 5.4% increase in reported crashes.

South Gulf Freeway appears repeatedly in the reports, with 227 crashes listed under that road name. The 5 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 181 of the 2,020 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 League City’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,020 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
056112167223JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 157 reported crashesFeb 2022: 156 reported crashesMar 2022: 212 reported crashesApr 2022: 210 reported crashesMay 2022: 179 reported crashesJun 2022: 194 reported crashesJul 2022: 177 reported crashesAug 2022: 169 reported crashesSep 2022: 176 reported crashesOct 2022: 202 reported crashesNov 2022: 223 reported crashesDec 2022: 208 reported crashesJan 2023: 178 reported crashesFeb 2023: 150 reported crashesMar 2023: 172 reported crashesApr 2023: 193 reported crashesMay 2023: 192 reported crashesJun 2023: 174 reported crashesJul 2023: 147 reported crashesAug 2023: 150 reported crashesSep 2023: 179 reported crashesOct 2023: 178 reported crashesNov 2023: 150 reported crashesDec 2023: 183 reported crashesJan 2024: 147 reported crashesFeb 2024: 153 reported crashesMar 2024: 156 reported crashesApr 2024: 153 reported crashesMay 2024: 184 reported crashesJun 2024: 186 reported crashesJul 2024: 150 reported crashesAug 2024: 179 reported crashesSep 2024: 161 reported crashesOct 2024: 172 reported crashesNov 2024: 158 reported crashesDec 2024: 194 reported crashesJan 2025: 143 reported crashesFeb 2025: 135 reported crashesMar 2025: 155 reported crashesApr 2025: 166 reported crashesMay 2025: 153 reported crashesJun 2025: 126 reported crashesJul 2025: 162 reported crashesAug 2025: 175 reported crashesSep 2025: 178 reported crashesOct 2025: 178 reported crashesNov 2025: 174 reported crashesDec 2025: 199 reported crashesJan 2026: 151 reported crashesFeb 2026: 181 reported crashesMar 2026: 186 reported crashesApr 2026: 155 reported crashesMay 2026: 174 reported crashesJun 2026: 149 reported crashesJul 2026: 147 reported crashesAug 2026: 164 reported crashesSep 2026: 162 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan157178147143151
Feb156150153135181
Mar212172156155186
Apr210193153166155
May179192184153174
Jun194174186126149
Jul177147150162147
Aug169150179175164
Sep176179161178162
Oct202178172178—
Nov223150158174—
Dec208183194199—
Same-period year-to-date comparison

From January 1 through 2026-09-30, League City recorded 1,469 crashes, compared with 1,393 over the matching dates a year earlier. That is 5.5% 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

09118112 AM: 19 reported crashes12 AM1 AM: 14 reported crashes2 AM: 22 reported crashes3 AM: 7 reported crashes3 AM4 AM: 14 reported crashes5 AM: 18 reported crashes6 AM: 47 reported crashes6 AM7 AM: 93 reported crashes8 AM: 94 reported crashes9 AM: 90 reported crashes9 AM10 AM: 81 reported crashes11 AM: 119 reported crashes12 PM: 145 reported crashes12 PM1 PM: 146 reported crashes2 PM: 130 reported crashes3 PM: 174 reported crashes3 PM4 PM: 170 reported crashes5 PM: 181 reported crashes6 PM: 166 reported crashes6 PM7 PM: 95 reported crashes8 PM: 69 reported crashes9 PM: 72 reported crashes9 PM10 PM: 29 reported crashes11 PM: 25 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM19001
1 AM14000
2 AM22001
3 AM7000
4 AM14000
5 AM18002
6 AM47000
7 AM93000
8 AM94000
9 AM90000
10 AM81000
11 AM119004
12 PM145002
1 PM146001
2 PM130221
3 PM174002
4 PM170003
5 PM181114
6 PM166002
7 PM95004
8 PM69003
9 PM72000
10 PM29000
11 PM25111

Day of the week

0184367Sun: 194 reported crashesSun194Mon: 248 reported crashesMon248Tue: 367 reported crashesTue367Wed: 322 reported crashesWed322Thu: 261 reported crashesThu261Fri: 350 reported crashesFri350Sat: 278 reported crashesSat278
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun194005
Mon248227
Tue367112
Wed322004
Thu261003
Fri350006
Sat278114

Month by month

01001992025-10: 178 reported crashes10/252025-11: 174 reported crashes2025-12: 199 reported crashes12/252026-01: 151 reported crashes2026-02: 181 reported crashes02/262026-03: 186 reported crashes2026-04: 155 reported crashes04/262026-05: 174 reported crashes2026-06: 149 reported crashes06/262026-07: 147 reported crashes2026-08: 164 reported crashes08/262026-09: 162 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10178003
2025-11174113
2025-12199007
2026-01151001
2026-02181000
2026-03186112
2026-04155004
2026-05174115
2026-06149003
2026-07147002
2026-08164000
2026-09162111

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved76
  • Commercial vehicle involved47
  • Motorcycle involved31
  • Bicycle involved26
  • Pedestrian involved18

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 involved76000
Commercial vehicle involved47001
Motorcycle involved31119
Bicycle involved26002
Pedestrian involved18112
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. South Gulf Freeway227 crashes
  2. West Main Street164 crashes
  3. East League City Parkway155 crashes
  4. West League City Parkway126 crashes
  5. West Farm-to-Market Road 646109 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 GULF FWY227003
W MAIN ST164110
E LEAGUE CITY PKWY155004
W LEAGUE CITY PKWY126112
W FM 646109000
E MAIN ST88002
E FM 64674003
S IH 45 FWY51002
MARINA BAY DR46001
W WALKER ST46000
SOUTH SHORE BLVD42000
E FM 51839000
S EGRET BAY BLVD35001
N EGRET BAY BLVD34001
S SHORE BLVD32000
W FM 51831000
N GULF FWY30000
HOBBS RD23001
S IH 4523000
FM 64616000
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
S GULF FWY & W LEAGUE CITY PKWY14000
S GULF FWY & W FM 64612000
ACCESS RD & N EGRET BAY BLVD6001
E LEAGUE CITY PKWY & LAWRENCE RD6000
HOBBS RD & W LEAGUE CITY PKWY6000
LANDING BLVD & W LEAGUE CITY PKWY6000
E FM 646 & S SH 35000
E LEAGUE CITY PKWY & S EGRET BAY BLVD5000
E LEAGUE CITY PKWY & SOUTH SHORE BLVD5000
E LEAGUE CITY PKWY & TUSCAN LAKES BLVD5002
N GULF FWY & W MAIN ST5000
W FM 646 & W WALKER ST5000
BALLPARK WAY & BROOKPORT DR4000
CROSS COLONY DR & W FM 6464000
E FM 646 & OHIO AVE4001
E MAIN ST & PARK AVE4000
E MAIN ST & PERKINS AVE4000
TOWN CENTER DR & W WALKER ST4000
ALDERWOOD ST & N BAY AREA BLVD3000
CALDER DR & W LEAGUE CITY PKWY3000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. League City Crash Guide. League City — Galveston County and Harris 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/league-city/

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

League City city · Galveston County and Harris County. Reported city code 255; county codes 84, 101. Current Census place identifier 4841980 (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 LEAGUE CITY, 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, 323 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; 2 lack a usable road label. 1,592 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:20:09.606Z. 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 →