CrashDNA

Crash data.
Real-world context.

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

Lufkin Crash Guide.

Angelina County

Reported crash counts, locations and trends in Lufkin.

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,222 1.7% moreCompared with Oct 1, 2024 to Sep 30, 2025
Fatal crashes5 3 more5 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People killed6 4 more6 vs. 2
Compared with Oct 1, 2024 to Sep 30, 2025
People seriously injured32 13 more32 vs. 19
Compared with Oct 1, 2024 to Sep 30, 2025

Reported crashes rose 1.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 Lufkin

Lufkin is a city in Angelina 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

Lufkin’s crash picture

From Oct 1, 2025 through Sep 30, 2026, the available records include 1,222 reported crashes in Lufkin. That is 21 more than the 1,201 recorded for the corresponding dates a year earlier—a 1.7% increase in reported crashes.

South Medford Drive appears repeatedly in the reports, with 125 crashes listed under that road name. The 2 p.m. hour had the highest reported count among crashes with a recorded time, accounting for 117 of the 1,222 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 Lufkin’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,222 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
03570105140JanFebMarAprMayJunJulAugSepOctNovDecJan 2022: 95 reported crashesFeb 2022: 95 reported crashesMar 2022: 90 reported crashesApr 2022: 109 reported crashesMay 2022: 96 reported crashesJun 2022: 105 reported crashesJul 2022: 66 reported crashesAug 2022: 104 reported crashesSep 2022: 103 reported crashesOct 2022: 108 reported crashesNov 2022: 99 reported crashesDec 2022: 90 reported crashesJan 2023: 98 reported crashesFeb 2023: 89 reported crashesMar 2023: 110 reported crashesApr 2023: 103 reported crashesMay 2023: 105 reported crashesJun 2023: 101 reported crashesJul 2023: 90 reported crashesAug 2023: 93 reported crashesSep 2023: 124 reported crashesOct 2023: 90 reported crashesNov 2023: 97 reported crashesDec 2023: 102 reported crashesJan 2024: 96 reported crashesFeb 2024: 83 reported crashesMar 2024: 102 reported crashesApr 2024: 99 reported crashesMay 2024: 92 reported crashesJun 2024: 88 reported crashesJul 2024: 106 reported crashesAug 2024: 100 reported crashesSep 2024: 98 reported crashesOct 2024: 108 reported crashesNov 2024: 116 reported crashesDec 2024: 114 reported crashesJan 2025: 91 reported crashesFeb 2025: 86 reported crashesMar 2025: 114 reported crashesApr 2025: 85 reported crashesMay 2025: 125 reported crashesJun 2025: 97 reported crashesJul 2025: 90 reported crashesAug 2025: 85 reported crashesSep 2025: 90 reported crashesOct 2025: 102 reported crashesNov 2025: 105 reported crashesDec 2025: 89 reported crashesJan 2026: 95 reported crashesFeb 2026: 94 reported crashesMar 2026: 110 reported crashesApr 2026: 110 reported crashesMay 2026: 117 reported crashesJun 2026: 140 reported crashesJul 2026: 75 reported crashesAug 2026: 82 reported crashesSep 2026: 103 reported crashes
View year-over-year monthly data
Reported crashes in the same calendar month across years. * Partial month; — no loaded value.
Month20222023202420252026
Jan9598969195
Feb9589838694
Mar90110102114110
Apr1091039985110
May9610592125117
Jun1051018897140
Jul66901069075
Aug104931008582
Sep1031249890103
Oct10890108102—
Nov9997116105—
Dec9010211489—
Same-period year-to-date comparison

From January 1 through 2026-09-30, Lufkin recorded 926 crashes, compared with 863 over the matching dates a year earlier. That is 7.3% more reported crashes.

WHEN IT HAPPENS

Reported crashes peak at 2 PM.

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

Time of day

05911712 AM: 16 reported crashes12 AM1 AM: 10 reported crashes2 AM: 7 reported crashes3 AM: 5 reported crashes3 AM4 AM: 9 reported crashes5 AM: 12 reported crashes6 AM: 27 reported crashes6 AM7 AM: 58 reported crashes8 AM: 50 reported crashes9 AM: 39 reported crashes9 AM10 AM: 54 reported crashes11 AM: 80 reported crashes12 PM: 104 reported crashes12 PM1 PM: 96 reported crashes2 PM: 117 reported crashes3 PM: 93 reported crashes3 PM4 PM: 102 reported crashes5 PM: 115 reported crashes6 PM: 67 reported crashes6 PM7 PM: 52 reported crashes8 PM: 48 reported crashes9 PM: 26 reported crashes9 PM10 PM: 21 reported crashes11 PM: 14 reported crashes
View the data table
Reported crashes by hour
GroupCrashesFatal crashesPeople killedPeople seriously injured
12 AM16001
1 AM10000
2 AM7000
3 AM5000
4 AM9001
5 AM12000
6 AM27000
7 AM58002
8 AM50116
9 AM39122
10 AM54112
11 AM80002
12 PM104000
1 PM96000
2 PM117002
3 PM93112
4 PM102005
5 PM115111
6 PM67000
7 PM52001
8 PM48002
9 PM26002
10 PM21000
11 PM14001

Day of the week

0107213Sun: 109 reported crashesSun109Mon: 165 reported crashesMon165Tue: 182 reported crashesTue182Wed: 205 reported crashesWed205Thu: 191 reported crashesThu191Fri: 213 reported crashesFri213Sat: 157 reported crashesSat157
View the data table
Reported crashes by weekday
GroupCrashesFatal crashesPeople killedPeople seriously injured
Sun109003
Mon165238
Tue182006
Wed205003
Thu191003
Fri213004
Sat157335

Month by month

0701402025-10: 102 reported crashes10/252025-11: 105 reported crashes2025-12: 89 reported crashes12/252026-01: 95 reported crashes2026-02: 94 reported crashes02/262026-03: 110 reported crashes2026-04: 110 reported crashes04/262026-05: 117 reported crashes2026-06: 140 reported crashes06/262026-07: 75 reported crashes2026-08: 82 reported crashes08/262026-09: 103 reported crashes
View the data table
Reported crashes by month
GroupCrashesFatal crashesPeople killedPeople seriously injured
2025-10102006
2025-11105000
2025-1289110
2026-0195114
2026-0294001
2026-03110007
2026-04110002
2026-05117234
2026-06140003
2026-0775002
2026-0882112
2026-09103001

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

WHO’S INVOLVED

Crashes by road-user involvement.

  • Truck / truck-tractor involved141
  • Commercial vehicle involved110
  • Pedestrian involved16
  • Motorcycle involved7
  • Bicycle involved5

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 involved141114
Commercial vehicle involved110114
Pedestrian involved16007
Motorcycle involved7002
Bicycle involved5001
WHERE REPORTS CONCENTRATE

Roads with the most reports.

  1. South Medford Drive125 crashes
  2. South John Redditt Drive115 crashes
  3. South First Street107 crashes
  4. West Frank Avenue76 crashes
  5. East Denman Avenue64 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 MEDFORD DR125003
S JOHN REDDITT DR115000
S FIRST ST107347
W FRANK AVE76003
E DENMAN AVE64001
N TIMBERLAND DR60002
S TIMBERLAND DR53000
N JOHN REDDITT DR43001
ELLEN TROUT DR38113
N MEDFORD DR38002
S CHESTNUT ST33000
E LUFKIN AVE25000
SOUTHWOOD DR25000
ATKINSON DR23000
TULANE DR20001
N BRENTWOOD DR18000
N RAGUET ST15001
ABNEY AVE13000
WHITEHOUSE DR13000
E FRANK AVE9000
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
N JOHN REDDITT DR & W FRANK AVE13000
E DENMAN AVE & S MEDFORD DR12000
ATKINSON DR & N TIMBERLAND DR10001
ELLEN TROUT DR & SAYERS ST9001
S JOHN REDDITT DR & W FRANK AVE9000
ABNEY AVE & CULVERHOUSE ST6000
ATKINSON DR & N MEDFORD DR6000
E LUFKIN AVE & N CHESTNUT ST5000
ELLEN TROUT DR & KURTH DR5000
S CHESTNUT ST & S MEDFORD DR5000
S JOHN REDDITT DR & SOUTHWOOD DR5000
S MEDFORD DR & TULANE DR5000
DANIEL MCCALL DR & SOUTHWOOD DR4000
E DENMAN AVE & S TIMBERLAND DR4000
N MEDFORD DR & N TIMBERLAND DR4000
S CHESTNUT ST & S TIMBERLAND DR4000
S FIRST ST & S MEDFORD DR4000
S JOHN REDDITT DR & WESTGATE LN4000
COLLEGE DR & S FIRST ST3000
COLLEGE DR & S JOHN REDDITT DR3000
SOURCE & ATTRIBUTION

Cite this guide.

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

CrashDNA. Lufkin Crash Guide. Lufkin — Angelina 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/lufkin/

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

Lufkin city · Angelina County. Reported city code 272; county codes 3. Current Census place identifier 4845072 (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 LUFKIN, 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, 82 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; 9 lack a usable road label. 866 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:21:47.611Z. 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 →