Skip to main content
TruckCodex
Hubs

Crash Record AL0003708014

FMCSA crash record in AUBURN on Oct 3, 2023.

Tow-Away Federal Recordable

What happened

On October 3, 2023, FMCSA recorded a tow-away crash with no reported injuries in AUBURN, Alabama. The vehicle was operated by FASTENAL COMPANY (USDOT 242294). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference AL0003708014.

Carrier pattern note

This is the carrier's 39 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.

Geographic note

This crash is part of an active corridor: 26 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
3
Carrier
FASTENAL COMPANY
USDOT 242294
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
39
8 injury · 38 tow-away
Crashes per 100 power units (24 mo)
3.6
25 crashes · 704 units
Days since prior carrier crash
33
Last on Aug 31, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,880 carriers

Geographic context

How this crash sits in its setting.

Within AUBURN, Alabama, 26 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
AL0003708014
Date:
Oct 3, 2023
Time:
1256
State:
Alabama
City:
AUBURN
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
FASTENAL COMPANY (242294)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 5 5 3C7WRSBJXLG273452 12A1MPB (AL) FASTENAL COMPANY 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5109697 Feb 24, 2026 MN Tow-Away 0 0
cr_5124543 Feb 20, 2026 PA Tow-Away 0 0
cr_5103987 Feb 1, 2026 MN Tow-Away 0 0
cr_5091190 Jan 16, 2026 AZ Injury 0 1
cr_5088247 Dec 15, 2025 IN Tow-Away 0 0
cr_5069150 Dec 3, 2025 MN Tow-Away 0 0
cr_5078567 Nov 27, 2025 OH Injury 0 1
cr_5099190 Nov 26, 2025 MS Tow-Away 0 0
cr_5071076 Nov 21, 2025 PA Tow-Away 0 0
cr_5065350 Nov 19, 2025 AL Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 242294 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle
2020 RAM 3500
NHTSA recalls and complaints for this make/model/year.
Recall
25V010000
AIR BAGS
Recall
22V904000
STRUCTURE:BODY:TAILGATE:HINGE AND ATTACHMENTS
Recall
22V835000
POWER TRAIN:AUTOMATIC TRANSMISSION
Carrier
FASTENAL COMPANY
USDOT 242294 · 451 crashes · 1,480 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3C7WRSBJXLG273452
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
City
Crashes in AUBURN, AL
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.