CrashDNA

Crash data.
Real-world context.

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

Pharr Crash Guide.

Hidalgo County

Reported crash counts, locations and trends in Pharr.

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 crashes1,935 2.7% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes1 5 fewer1 vs. 6
Compared with Oct 1, 2024 to Sep 30, 2025
People killed1 5 fewer1 vs. 6
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured26 6 more26 vs. 20
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 2.7%.

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 Pharr

Pharr 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

Pharr’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 1,935 reported crashes in Pharr. That is 54 fewer than the 1,989 recorded for the corresponding dates a year earlier—a 2.7% decrease in reported crashes.

North Cage Boulevard appears repeatedly in the reports, with 225 crashes listed under that road name. The 5 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 210 of the 1,935 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 Pharr’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 (1,935 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
065131196261JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 246 reported crashesFeb 2022: 207 reported crashesMar 2022: 235 reported crashesApr 2022: 240 reported crashesMay 2022: 232 reported crashesJun 2022: 214 reported crashesJul 2022: 214 reported crashesAug 2022: 257 reported crashesSep 2022: 251 reported crashesOct 2022: 243 reported crashesNov 2022: 235 reported crashesDec 2022: 261 reported crashesJan 2023: 241 reported crashesFeb 2023: 227 reported crashesMar 2023: 238 reported crashesApr 2023: 232 reported crashesMay 2023: 259 reported crashesJun 2023: 232 reported crashesJul 2023: 207 reported crashesAug 2023: 239 reported crashesSep 2023: 244 reported crashesOct 2023: 237 reported crashesNov 2023: 224 reported crashesDec 2023: 232 reported crashesJan 2024: 193 reported crashesFeb 2024: 199 reported crashesMar 2024: 205 reported crashesApr 2024: 201 reported crashesMay 2024: 211 reported crashesJun 2024: 169 reported crashesJul 2024: 189 reported crashesAug 2024: 199 reported crashesSep 2024: 178 reported crashesOct 2024: 209 reported crashesNov 2024: 193 reported crashesDec 2024: 164 reported crashesJan 2025: 162 reported crashesFeb 2025: 169 reported crashesMar 2025: 169 reported crashesApr 2025: 172 reported crashesMay 2025: 165 reported crashesJun 2025: 173 reported crashesJul 2025: 139 reported crashesAug 2025: 141 reported crashesSep 2025: 133 reported crashesOct 2025: 172 reported crashesNov 2025: 172 reported crashesDec 2025: 159 reported crashesJan 2026: 135 reported crashesFeb 2026: 187 reported crashesMar 2026: 167 reported crashesApr 2026: 185 reported crashesMay 2026: 166 reported crashesJun 2026: 122 reported crashesJul 2026: 183 reported crashesAug 2026: 128 reported crashesSep 2026: 159 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan246241193162135
Feb207227199169187
Mar235238205169167
Apr240232201172185
May232259211165166
Jun214232169173122
Jul214207189139183
Aug257239199141128
Sep251244178133159
Oct243237209172—
Nov235224193172—
Dec261232164159—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Pharr recorded 1,432 crashes, compared with 1,423 over the matching dates a year earlier. That is 0.6% 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

010521012 AM: 12 reported crashes12 AM1 AM: 14 reported crashes2 AM: 25 reported crashes3 AM: 12 reported crashes3 AM4 AM: 6 reported crashes5 AM: 14 reported crashes6 AM: 28 reported crashes6 AM7 AM: 107 reported crashes8 AM: 109 reported crashes9 AM: 87 reported crashes9 AM10 AM: 84 reported crashes11 AM: 98 reported crashes12 PM: 140 reported crashes12 PM1 PM: 108 reported crashes2 PM: 129 reported crashes3 PM: 137 reported crashes3 PM4 PM: 190 reported crashes5 PM: 210 reported crashes6 PM: 141 reported crashes6 PM7 PM: 94 reported crashes8 PM: 63 reported crashes9 PM: 60 reported crashes9 PM10 PM: 40 reported crashes11 PM: 27 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM12000
1 AM14111
2 AM25003
3 AM12000
4 AM6000
5 AM14002
6 AM28001
7 AM107000
8 AM109002
9 AM87000
10 AM84002
11 AM98001
12 PM140000
1 PM108001
2 PM129001
3 PM137000
4 PM190001
5 PM210005
6 PM141003
7 PM94000
8 PM63000
9 PM60000
10 PM40001
11 PM27002

Day of the week

0169338Sun: 180 reported crashesSun180Mon: 298 reported crashesMon298Tue: 302 reported crashesTue302Wed: 287 reported crashesWed287Thu: 287 reported crashesThu287Fri: 338 reported crashesFri338Sat: 243 reported crashesSat243
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun180006
Mon298001
Tue302001
Wed287004
Thu287003
Fri338004
Sat243117

Month by month

0941872025-10: 172 reported crashes10/252025-11: 172 reported crashes2025-12: 159 reported crashes12/252026-01: 135 reported crashes2026-02: 187 reported crashes02/262026-03: 167 reported crashes2026-04: 185 reported crashes04/262026-05: 166 reported crashes2026-06: 122 reported crashes06/262026-07: 183 reported crashes2026-08: 128 reported crashes08/262026-09: 159 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10172002
2025-11172114
2025-12159001
2026-01135002
2026-02187003
2026-03167003
2026-04185003
2026-05166000
2026-06122000
2026-07183002
2026-08128003
2026-09159003

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved206
  • Commercial vehicle involved114
  • Motorcycle involved15
  • Pedestrian involved13
  • Bicycle involved9

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 involved206002
Commercial vehicle involved114001
Motorcycle involved15005
Pedestrian involved13115
Bicycle involved9002
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. North Cage Boulevard225 crashes
  2. South Cage Boulevard198 crashes
  3. North Jackson Road85 crashes
  4. West Nolana Loop83 crashes
  5. South Jackson Road76 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 CAGE BLVD225003
S CAGE BLVD198001
N JACKSON RD85001
W NOLANA LOOP83001
S JACKSON RD76000
W INTERSTATE 2 HWY62001
N SUGAR RD43000
E INTERSTATE 2 HWY35000
N INTERSTATE 69C HWY33000
E NOLANA LOOP28000
W FERGUSON AVE28000
W KELLY AVE28000
W DICKER RD24000
W OWASSA RD24000
E DICKER RD23000
W BUSINESS 83 HWY22001
W RIDGE RD22000
E OWASSA RD21000
N VETERANS BLVD17000
W MINNESOTA RD17000
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 NOLANA LOOP & N CAGE BLVD9000
N CAGE BLVD & W NOLANA LOOP9000
S CAGE BLVD & W RIDGE RD6001
E DICKER RD & N JACKSON RD5000
N CAGE BLVD & W FERGUSON AVE5000
N CAGE BLVD & W POLK AVE5000
E DICKER RD & S CAGE BLVD4000
E MOORE RD & S CAGE BLVD4000
E OWASSA RD & N CAGE BLVD4000
N SUGAR RD & W MINNESOTA RD4000
N SUGAR RD & W POLK AVE4000
S BLUEBONNET ST & W KELLY AVE4000
S JACKSON RD & W DICKER RD4000
S JACKSON RD & W RIDGE RD4000
E EL RANCHO RD & S MCCOLL RD3000
E JAVELINA DR & S CAGE BLVD3000
E KELLY AVE & S DOGWOOD ST3000
E OWASSA RD & S 25TH AVE3000
N CAGE BLVD & W MINNESOTA RD3000
N CAGE BLVD & W OWASSA RD3000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Pharr Crash Guide. Pharr — 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/pharr/

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

Pharr city · Hidalgo County. Reported city code 331; county codes 108. Current Census place identifier 4857200 (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 PHARR, 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, 136 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; 4 lack a usable road label. 1,564 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:27:06.278Z. 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 →