CrashDNA

Crash data.
Real-world context.

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

Port Arthur Crash Guide.

Jefferson County

Reported crash counts, locations and trends in Port Arthur.

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,462 10.9% fewerCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes10 2 more10 vs. 8
Compared with Oct 1, 2024 to Sep 30, 2025
People killed10 2 more10 vs. 8
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured31 58.1% fewerCompared with Oct 1, 2024 to Sep 30, 2025

Reported crashes fell 10.9%.

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 Port Arthur

Port Arthur is a city in Jefferson 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

Port Arthur’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 1,462 reported crashes in Port Arthur. That is 178 fewer than the 1,640 recorded for the corresponding dates a year earlier—a 10.9% decrease in reported crashes.

Memorial 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 146 of the 1,462 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 Port Arthur’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,462 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
04487131174JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 133 reported crashesFeb 2022: 120 reported crashesMar 2022: 146 reported crashesApr 2022: 162 reported crashesMay 2022: 137 reported crashesJun 2022: 120 reported crashesJul 2022: 120 reported crashesAug 2022: 155 reported crashesSep 2022: 144 reported crashesOct 2022: 124 reported crashesNov 2022: 150 reported crashesDec 2022: 131 reported crashesJan 2023: 121 reported crashesFeb 2023: 132 reported crashesMar 2023: 159 reported crashesApr 2023: 141 reported crashesMay 2023: 165 reported crashesJun 2023: 143 reported crashesJul 2023: 107 reported crashesAug 2023: 145 reported crashesSep 2023: 139 reported crashesOct 2023: 151 reported crashesNov 2023: 141 reported crashesDec 2023: 150 reported crashesJan 2024: 138 reported crashesFeb 2024: 143 reported crashesMar 2024: 150 reported crashesApr 2024: 174 reported crashesMay 2024: 144 reported crashesJun 2024: 120 reported crashesJul 2024: 128 reported crashesAug 2024: 144 reported crashesSep 2024: 129 reported crashesOct 2024: 139 reported crashesNov 2024: 159 reported crashesDec 2024: 151 reported crashesJan 2025: 106 reported crashesFeb 2025: 125 reported crashesMar 2025: 125 reported crashesApr 2025: 145 reported crashesMay 2025: 160 reported crashesJun 2025: 148 reported crashesJul 2025: 99 reported crashesAug 2025: 144 reported crashesSep 2025: 139 reported crashesOct 2025: 163 reported crashesNov 2025: 129 reported crashesDec 2025: 139 reported crashesJan 2026: 118 reported crashesFeb 2026: 105 reported crashesMar 2026: 108 reported crashesApr 2026: 121 reported crashesMay 2026: 111 reported crashesJun 2026: 124 reported crashesJul 2026: 129 reported crashesAug 2026: 100 reported crashesSep 2026: 115 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan133121138106118
Feb120132143125105
Mar146159150125108
Apr162141174145121
May137165144160111
Jun120143120148124
Jul12010712899129
Aug155145144144100
Sep144139129139115
Oct124151139163—
Nov150141159129—
Dec131150151139—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Port Arthur recorded 1,031 crashes, compared with 1,191 over the matching dates a year earlier. That is 13.4% fewer reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 5 PM.

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

Time of day

07314612 AM: 26 reported crashes12 AM1 AM: 17 reported crashes2 AM: 21 reported crashes3 AM: 23 reported crashes3 AM4 AM: 34 reported crashes5 AM: 50 reported crashes6 AM: 46 reported crashes6 AM7 AM: 53 reported crashes8 AM: 58 reported crashes9 AM: 52 reported crashes9 AM10 AM: 53 reported crashes11 AM: 60 reported crashes12 PM: 90 reported crashes12 PM1 PM: 88 reported crashes2 PM: 87 reported crashes3 PM: 113 reported crashes3 PM4 PM: 139 reported crashes5 PM: 146 reported crashes6 PM: 93 reported crashes6 PM7 PM: 63 reported crashes8 PM: 53 reported crashes9 PM: 43 reported crashes9 PM10 PM: 32 reported crashes11 PM: 22 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM26110
1 AM17001
2 AM21004
3 AM23111
4 AM34112
5 AM50110
6 AM46001
7 AM53000
8 AM58110
9 AM52000
10 AM53000
11 AM60001
12 PM90113
1 PM88001
2 PM87001
3 PM113111
4 PM139004
5 PM146111
6 PM93001
7 PM63002
8 PM53001
9 PM43224
10 PM32001
11 PM22001

Day of the week

0126252Sun: 167 reported crashesSun167Mon: 198 reported crashesMon198Tue: 224 reported crashesTue224Wed: 221 reported crashesWed221Thu: 252 reported crashesThu252Fri: 226 reported crashesFri226Sat: 174 reported crashesSat174
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun167113
Mon198114
Tue224112
Wed221115
Thu252228
Fri226442
Sat174007

Month by month

0821632025-10: 163 reported crashes10/252025-11: 129 reported crashes2025-12: 139 reported crashes12/252026-01: 118 reported crashes2026-02: 105 reported crashes02/262026-03: 108 reported crashes2026-04: 121 reported crashes04/262026-05: 111 reported crashes2026-06: 124 reported crashes06/262026-07: 129 reported crashes2026-08: 100 reported crashes08/262026-09: 115 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10163222
2025-11129001
2025-12139112
2026-01118222
2026-02105002
2026-03108003
2026-04121111
2026-05111114
2026-06124004
2026-07129114
2026-08100112
2026-09115114

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved111
  • Commercial vehicle involved71
  • Pedestrian involved21
  • Motorcycle involved18
  • Bicycle involved8

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 involved111111
Commercial vehicle involved71110
Pedestrian involved21446
Motorcycle involved18004
Bicycle involved8110
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. Memorial Boulevard225 crashes
  2. Gulfway Drive99 crashes
  3. 9th Avenue86 crashes
  4. 365 Highway68 crashes
  5. Twin City Highway57 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
MEMORIAL BLVD225113
GULFWAY DR99111
9TH AVE86003
365 HWY68002
TWIN CITY HWY57001
JIMMY JOHNSON BLVD44002
73 HWY35111
W PORT ARTHUR RD29001
WOODWORTH BLVD22001
CENTRAL MALL DR21001
W NOT REPORTED21001
SAVANNAH AVE20110
W 73 HWY18001
S GULFWAY DR16110
JEFFERSON DR14000
US 6913000
FM 36512000
FM 365 HWY12001
MLK DR12000
39TH ST11001
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
JIMMY JOHNSON BLVD & MEMORIAL BLVD20000
CENTRAL MALL DR & REGIONAL DR10001
365 HWY & MEMORIAL BLVD9000
39TH ST & MEMORIAL BLVD8000
MEMORIAL BLVD & NEDERLAND AVE8001
ANCHOR DR & CENTRAL MALL DR7000
7TH AVE & GULFWAY DR5000
ANCHOR DR & JIMMY JOHNSON BLVD5001
32ND ST & TWIN CITY HWY4000
AERO DR & MEMORIAL BLVD4000
ANCHOR DR & TURTLE CREEK DR4000
GULFWAY DR & LAKEVIEW AVE4000
25TH ST & SAVANNAH AVE3000
39TH ST & DREXEL AVE3000
3RD AVE & 7TH ST3000
DEQUEEN BLVD & GULFWAY DR3000
15TH ST & 2ND AVE2000
19TH ST & SAVANNAH AVE2000
25TH ST & 9TH AVE2000
25TH ST & MEMORIAL BLVD2000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Port Arthur Crash Guide. Port Arthur — Jefferson 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/port-arthur/

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

Port Arthur city · Jefferson County. Reported city code 339; county codes 123. Current Census place identifier 4858820 (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 PORT ARTHUR, 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, 64 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; 100 lack a usable road label. 1,065 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:54.690Z. 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 →