Skip to main content
TruckCodex
Hubs

Crash Record TN0400255077

FMCSA crash record in ALCOA on May 4, 2025.

Injury Federal Recordable

What happened

On May 4, 2025, FMCSA recorded an injury crash with one person hurt in ALCOA, Tennessee. The vehicle was operated by DAVENPORT TRANSPORTATION INC (USDOT 283939). Recorded conditions: 3 / 9 / 1 pavement. Reported by DAVENPORT TRANSPORTATION, FMCSA reference TN0400255077.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
DAVENPORT TRANSPORTATION INC
USDOT 283939
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
51
2 fatal · 17 injury
Crashes per 100 power units (24 mo)
3.3
30 crashes · 910 units
Days since prior carrier crash
25
Last on Apr 9, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within ALCOA, Tennessee, 23 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
3
Weather
9
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 #:
TN0400255077
Date:
May 4, 2025
Time:
0330
State:
Tennessee
City:
ALCOA
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
DAVENPORT TRANSPORTATION INC (283939)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 — 98 5PVNJ8JV9H4S63118 EGY262 (GA) DAVENPORT TRANSPORTATION 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvj4mhg7001vo3kfe49e1af3 Oct 16, 2026 TN Tow-Away 0 0
cmreexwg10003p8r591c021d9 Jul 6, 2026 TN Tow-Away 0 0
cmq0fazbw001lpmw8zs2ztykj May 29, 2026 NC Tow-Away 0 0
cr_5109575 Feb 20, 2026 TN Tow-Away 0 0
cr_5104529 Feb 4, 2026 TN Tow-Away 0 0
cr_5071951 Dec 1, 2025 TN Tow-Away 0 0
cr_5066673 Nov 30, 2025 GA Tow-Away 0 0
cr_5071914 Nov 30, 2025 TN Injury 0 1
cr_5071361 Nov 24, 2025 SC Tow-Away 0 0
cr_5064691 Nov 18, 2025 GA Fatal 1 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2017 HINO Conventional Type Truck
NHTSA recalls and complaints for this make/model/year.
Carrier
DAVENPORT TRANSPORTATION INC
USDOT 283939 · 304 crashes · 466 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 5PVNJ8JV9H4S63118
Decode this VIN for make, model, year, and recall data.
State
Crashes in Tennessee
Statewide crash records.
Agency
DAVENPORT TRANSPORTATION
Crashes reported by this law-enforcement agency.
City
Crashes in ALCOA, TN
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.