CrashDNA

Crash data.
Real-world context.

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

San Juan Crash Guide.

Hidalgo County

Reported crash counts, locations and trends in San Juan.

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 crashes907 16.5% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes0 1 fewer0 vs. 1
Compared with Oct 1, 2024 to Sep 30, 2025
People killed0 2 fewer0 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured9 6 fewer9 vs. 15
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 16.5%.

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 San Juan

San Juan is a city in Hidalgo 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

San Juan’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 907 reported crashes in San Juan. That is 179 fewer than the 1,086 recorded for the corresponding dates a year earlier—a 16.5% decrease in reported crashes.

North Raul Longoria Road appears repeatedly in the reports, with 108 crashes listed under that road name. The 4 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 96 of the 907 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 San Juan’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 (907 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
04285127169JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 116 reported crashesFeb 2022: 143 reported crashesMar 2022: 123 reported crashesApr 2022: 148 reported crashesMay 2022: 154 reported crashesJun 2022: 122 reported crashesJul 2022: 85 reported crashesAug 2022: 127 reported crashesSep 2022: 133 reported crashesOct 2022: 169 reported crashesNov 2022: 150 reported crashesDec 2022: 148 reported crashesJan 2023: 138 reported crashesFeb 2023: 150 reported crashesMar 2023: 159 reported crashesApr 2023: 162 reported crashesMay 2023: 127 reported crashesJun 2023: 135 reported crashesJul 2023: 119 reported crashesAug 2023: 129 reported crashesSep 2023: 127 reported crashesOct 2023: 128 reported crashesNov 2023: 126 reported crashesDec 2023: 128 reported crashesJan 2024: 115 reported crashesFeb 2024: 122 reported crashesMar 2024: 126 reported crashesApr 2024: 123 reported crashesMay 2024: 99 reported crashesJun 2024: 125 reported crashesJul 2024: 91 reported crashesAug 2024: 108 reported crashesSep 2024: 106 reported crashesOct 2024: 129 reported crashesNov 2024: 125 reported crashesDec 2024: 95 reported crashesJan 2025: 76 reported crashesFeb 2025: 68 reported crashesMar 2025: 109 reported crashesApr 2025: 90 reported crashesMay 2025: 80 reported crashesJun 2025: 76 reported crashesJul 2025: 82 reported crashesAug 2025: 69 reported crashesSep 2025: 87 reported crashesOct 2025: 95 reported crashesNov 2025: 77 reported crashesDec 2025: 72 reported crashesJan 2026: 55 reported crashesFeb 2026: 78 reported crashesMar 2026: 89 reported crashesApr 2026: 71 reported crashesMay 2026: 71 reported crashesJun 2026: 85 reported crashesJul 2026: 63 reported crashesAug 2026: 62 reported crashesSep 2026: 89 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan1161381157655
Feb1431501226878
Mar12315912610989
Apr1481621239071
May154127998071
Jun1221351257685
Jul85119918263
Aug1271291086962
Sep1331271068789
Oct16912812995—
Nov15012612577—
Dec1481289572—
Same-period year-to-date comparison

From January 1 through 2026-09-30, San Juan recorded 663 crashes, compared with 737 over the matching dates a year earlier. That is 10.0% 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

0489612 AM: 8 reported crashes12 AM1 AM: 4 reported crashes2 AM: 7 reported crashes3 AM: 3 reported crashes3 AM4 AM: 4 reported crashes5 AM: 11 reported crashes6 AM: 7 reported crashes6 AM7 AM: 54 reported crashes8 AM: 63 reported crashes9 AM: 36 reported crashes9 AM10 AM: 42 reported crashes11 AM: 51 reported crashes12 PM: 55 reported crashes12 PM1 PM: 52 reported crashes2 PM: 57 reported crashes3 PM: 72 reported crashes3 PM4 PM: 96 reported crashes5 PM: 82 reported crashes6 PM: 59 reported crashes6 PM7 PM: 37 reported crashes8 PM: 36 reported crashes9 PM: 36 reported crashes9 PM10 PM: 14 reported crashes11 PM: 21 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM8000
1 AM4000
2 AM7000
3 AM3000
4 AM4000
5 AM11000
6 AM7000
7 AM54000
8 AM63001
9 AM36000
10 AM42000
11 AM51000
12 PM55001
1 PM52000
2 PM57002
3 PM72001
4 PM96000
5 PM82000
6 PM59001
7 PM37001
8 PM36000
9 PM36001
10 PM14001
11 PM21000

Day of the week

082164Sun: 83 reported crashesSun83Mon: 139 reported crashesMon139Tue: 137 reported crashesTue137Wed: 146 reported crashesWed146Thu: 148 reported crashesThu148Fri: 164 reported crashesFri164Sat: 90 reported crashesSat90
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun83000
Mon139002
Tue137004
Wed146000
Thu148002
Fri164000
Sat90001

Month by month

048952025-10: 95 reported crashes10/252025-11: 77 reported crashes2025-12: 72 reported crashes12/252026-01: 55 reported crashes2026-02: 78 reported crashes02/262026-03: 89 reported crashes2026-04: 71 reported crashes04/262026-05: 71 reported crashes2026-06: 85 reported crashes06/262026-07: 63 reported crashes2026-08: 62 reported crashes08/262026-09: 89 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-1095002
2025-1177000
2025-1272001
2026-0155000
2026-0278000
2026-0389000
2026-0471000
2026-0571000
2026-0685003
2026-0763001
2026-0862001
2026-0989001

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved79
  • Commercial vehicle involved36
  • Pedestrian involved7
  • Motorcycle involved5
  • Bicycle involved3

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 involved79000
Commercial vehicle involved36000
Pedestrian involved7002
Motorcycle involved5001
Bicycle involved3001
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. North Raul Longoria Road108 crashes
  2. North Veterans Boulevard71 crashes
  3. South Stewart Road49 crashes
  4. South Nebraska Avenue23 crashes
  5. South Veterans Boulevard20 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
N RAUL LONGORIA RD108000
N VETERANS BLVD71000
S STEWART RD49001
S NEBRASKA AVE23000
S VETERANS BLVD20001
E SIOUX RD19000
E EXPRESSWAY 8318000
W RIDGE RD18000
W EXPRESSWAY 8317000
N CESAR CHAVEZ RD16001
E INTERSTATE 2 HWY15000
N NEBRASKA AVE15000
E INTERSTATE 2 EXPY13000
W EXPRESSWAY 83 EXPY13000
E RIDGE RD12000
W FRONTAGE RD12001
W INTERSTATE 212000
E INTERSTATE 211000
N VETERANS RD11000
E FRONTAGE RD10001
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
E DICKER RD & S STEWART RD5000
E FRONTAGE RD & N CESAR CHAVEZ RD5001
E POLK AVE & N VETERANS BLVD5000
E FERGUSON AVE & N VETERANS BLVD4000
E MOORE RD & S STEWART RD4000
E RIDGE RD & S STEWART RD4000
E HALL ACRES RD & S STEWART RD3000
E KELLY AVE & S VETERANS BLVD3000
E RIDGE RD & S CESAR CHAVEZ RD3000
E SIOUX RD & N VETERANS BLVD3000
CESAR CHAVEZ RD & SIOUX RD2000
E 495 & N RAUL LONGORIA RD2000
E BUSINESS 83 & S STEWART RD2000
E CARROLL RD & S STEWART RD2000
E ELDORA RD & GRANDORA DR2000
E FRONTAGE RD & N NEBRASKA AVE2000
E MINNESOTA RD & N RAUL LONGORIA RD2000
E NOLANA LOOP & N RAUL LONGORIA RD2000
E POLK AVE & N VETERANS RD2000
E SAM HOUSTON BLVD & S CESAR CHAVEZ RD2000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. San Juan Crash Guide. San Juan — Hidalgo 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/san-juan/

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

San Juan city · Hidalgo County. Reported city code 382; county codes 108. Current Census place identifier 4865516 (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 SAN JUAN, 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, 179 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; 1 lack a usable road label. 731 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:30:58.280Z. 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 →