Crash Record AL0004689785

FMCSA crash record in HUNTSVILLE on Aug 27, 2024.

Tow-Away Federal Recordable

What happened

On August 27, 2024, FMCSA recorded a tow-away crash with no reported injuries in HUNTSVILLE, Alabama. The vehicle was operated by BNA TRANSPORT INC (USDOT 3514118). Recorded conditions: 1 / 1 / 1 pavement. Reported by BNA TRANSPORT INC, FMCSA reference AL0004689785.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

BNA TRANSPORT INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 5 tow-away

Crashes per 100 power units (24 mo)

14.3

10 crashes · 70 units

Days since prior carrier crash

Last on Aug 6, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,879 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

TATE SERVICES INC · 4 reports
UNKNOWN · 4 reports
AEC WASTE SOLUTIONS · 2 reports

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 #:: AL0004689785
Date:: Aug 27, 2024
Time:: 0811
State:: Alabama
City:: HUNTSVILLE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: BNA TRANSPORT INC (3514118)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	4V4NC9EJ3RN630862	3646375 (IN)	BNA TRANSPORT INC	3	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	Injuries
cr_5014468	Aug 12, 2025	TX	Tow-Away	0
cr_4939355	May 7, 2025	FL	Injury	1
cr_4923401	Apr 3, 2025	MO	Tow-Away	0
cr_4909980	Mar 6, 2025	TX	Tow-Away	0
cr_4890529	Feb 6, 2025	NC	Injury	1
cr_4881263	Jan 18, 2025	FL	Tow-Away	0
cr_4869256	Dec 16, 2024	FL	Tow-Away	0
cr_4860177	Dec 10, 2024	NC	Tow-Away	0
cr_4906663	Nov 22, 2024	WV	Tow-Away	0
cr_4832345	Oct 26, 2024	AL	Injury	1

Related records

Vehicle

2024 VOLVO TRUCK VNL

NHTSA recalls and complaints for this make/model/year.

Carrier

BNA TRANSPORT INC

USDOT 3514118 · 18 crashes · 0 inspections

Vehicle

VIN: 4V4NC9EJ3RN630862

Decode this VIN for make, model, year, and recall data.

State

Crashes in Alabama

Statewide crash records.

Agency

BNA TRANSPORT INC

Crashes reported by this law-enforcement agency.

City

Crashes in HUNTSVILLE, 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.