Crash Record KY0073159279

FMCSA crash record in LEXINGTON on Mar 9, 2025.

Tow-Away Federal Recordable

What happened

On March 9, 2025, FMCSA recorded a tow-away crash with no reported injuries in LEXINGTON, Kentucky. The vehicle was operated by BROTHERS TRANSPORT LLC (USDOT 2123265). Recorded conditions: 3 / 1 / 1 pavement. Reported by BROTHERS TRANSPORT LLC, FMCSA reference KY0073159279.

Carrier pattern note

This is the carrier's 12 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: 325 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

BROTHERS TRANSPORT LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

5 injury · 12 tow-away

Crashes per 100 power units (24 mo)

16.7

15 crashes · 90 units

Days since prior carrier crash

Last on Feb 19, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within LEXINGTON, Kentucky, 325 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

LEXTRAN · 5 reports
HAYNES TRUCKING LLC · 4 reports
RYDER · 4 reports

Contributing factors

What the responding officer recorded.

Light: 3
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 #:: KY0073159279
Date:: Mar 9, 2025
Time:: 2129
State:: Kentucky
City:: LEXINGTON
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: BROTHERS TRANSPORT LLC (2123265)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	5	4V4NC9TH3RN660895	A99709 (KY)	BROTHERS TRANSPORT LLC	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
cmpqehz48002tqiysjnlz7siy	May 22, 2026	KY	Tow-Away	0
cmokyiris000tnv1d7dd8sei2	Apr 24, 2026	NC	Tow-Away	0
cmny3ygre00sck38viv5lsn12	Apr 2, 2026	KY	Tow-Away	0
cr_5114940	Feb 27, 2026	KY	Injury	1
cr_5114925	Feb 17, 2026	GA	Injury	1
cr_5064015	Nov 17, 2025	LA	Tow-Away	0
cr_5017902	Aug 4, 2025	IN	Tow-Away	0
cr_4952515	Jun 4, 2025	KY	Tow-Away	0
cr_4951065	May 23, 2025	VA	Injury	1
cr_4935080	Apr 17, 2025	NC	Tow-Away	0

Related records

Carrier

BROTHERS TRANSPORT LLC

USDOT 2123265 · 32 crashes · 219 inspections

Vehicle

VIN: 4V4NC9TH3RN660895

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

State

Crashes in Kentucky

Statewide crash records.

Agency

BROTHERS TRANSPORT LLC

Crashes reported by this law-enforcement agency.

City

Crashes in LEXINGTON, KY

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.