TruckCodex
Hubs

Crash Record CA5252200070

FMCSA crash record in AZUSA on Jan 6, 2022.

Injury Federal Recordable

What happened

On January 6, 2022, FMCSA recorded an injury crash with one person hurt in AZUSA, California. The vehicle was operated by BLACK HORSE CARRIERS LLC (USDOT 807505). Recorded conditions: 1 / 1 / 1 pavement. Reported by BLACK HORSE CARRIERS LLC, FMCSA reference CA5252200070.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
4
Carrier
BLACK HORSE CARRIERS LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
145
5 fatal · 56 injury
Crashes per 100 power units (24 mo)
100.0
1 crashes · 1 units
Days since prior carrier crash
6
Last on Dec 31, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,552,303 carriers

Geographic context

How this crash sits in its setting.

Within AZUSA, California, 29 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 #:
CA5252200070
Date:
Jan 6, 2022
Time:
0755
State:
California
City:
AZUSA
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
4
Carrier (USDOT):
BLACK HORSE CARRIERS LLC (807505)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKBHSDV5LSLS3107 3122053 (IN) BLACK HORSE CARRIERS 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 Fatalities Injuries
cr_5125635 Dec 19, 2025 CT Injury 0 1
cr_4797708 Jul 30, 2024 GA Tow-Away 0 0
cr_4649865 Oct 30, 2023 IA Injury 0 1
cr_4503715 Jan 5, 2023 MD Tow-Away 0 0
cr_4453059 Oct 29, 2022 NY Injury 0 1
cr_4439102 Oct 20, 2022 IA Tow-Away 0 0
cr_4438718 Oct 7, 2022 AL Tow-Away 0 0
cr_4445984 Oct 1, 2022 MD Tow-Away 0 0
cr_4445953 Aug 5, 2022 MD Injury 0 1
cr_4386440 Jul 16, 2022 AR Tow-Away 0 0

Related records

Vehicle
2020 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V299000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V208000
EXTERIOR LIGHTING
Recall
23V105000
STEERING:LINKAGES:DRAG:LINK:CONNECTION
Carrier
BLACK HORSE CARRIERS LLC
USDOT 807505 · 866 crashes · 0 inspections
Vehicle
VIN: 3AKBHSDV5LSLS3107
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
BLACK HORSE CARRIERS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in AZUSA, CA
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.