TruckCodex
Hubs

Crash Record CT2100012977

FMCSA crash record in MILFORD on Jan 10, 2021.

Tow-Away Federal Recordable

What happened

On January 10, 2021, FMCSA recorded a tow-away crash with no reported injuries in MILFORD, Connecticut. The vehicle was operated by BLUE DIAMOND TRANSPORTATION LLC (USDOT 2533963). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference CT2100012977.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
BLUE DIAMOND TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
32
13 injury · 31 tow-away
Crashes per 100 power units (24 mo)
12.1
21 crashes · 174 units
Days since prior carrier crash
72
Last on Oct 30, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,684 carriers

Geographic context

How this crash sits in its setting.

Within MILFORD, Connecticut, 71 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 #:
CT2100012977
Date:
Jan 10, 2021
Time:
1220
State:
Connecticut
City:
MILFORD
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BLUE DIAMOND TRANSPORTATION LLC (2533963)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHHDR7LSKV8410 68242A (CT) BLUE DIAMOND TRANSPORTATION LLC 3 Yes

Crash event

Event sequence description.

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

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmtazy7kx003bpmlnybmepy9r Aug 20, 2026 OH Injury 0 1
cr_5112085 Feb 25, 2026 MA Tow-Away 0 0
cr_5104009 Jan 25, 2026 ME Tow-Away 0 0
cr_5090084 Jan 4, 2026 PA Tow-Away 0 0
cr_5078495 Nov 19, 2025 MA Tow-Away 0 0
cr_5058965 Nov 8, 2025 MO Injury 0 1
cr_5054371 Nov 1, 2025 ME Tow-Away 0 0
cr_5056594 Oct 30, 2025 NY Injury 0 2
cr_5044788 Oct 9, 2025 CT Tow-Away 0 0
cr_5028279 Aug 29, 2025 OH Tow-Away 0 0

Related records

Carrier
BLUE DIAMOND TRANSPORTATION LLC
USDOT 2533963 · 150 crashes · 866 inspections
Vehicle
VIN: 3AKJHHDR7LSKV8410
Decode this VIN for make, model, year, and recall data.
State
Crashes in Connecticut
Statewide crash records.
City
Crashes in MILFORD, CT
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.