Skip to main content
TruckCodex
Hubs

Crash Record VA0231515128

FMCSA crash record in Virginia on May 30, 2023.

Injury Federal Recordable

What happened

On May 30, 2023, FMCSA recorded an injury crash with one person hurt in Virginia. The vehicle was operated by CROSBY TRUCKING SERVICE INC (USDOT 32052). Recorded conditions: 1 / 1 / 1 pavement. Reported by CROSBY TRUCKING SERVICE INC, FMCSA reference VA0231515128.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CROSBY TRUCKING SERVICE INC
USDOT 32052
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
14
1 fatal · 7 injury
Crashes per 100 power units (24 mo)
4.2
4 crashes · 96 units
Days since prior carrier crash
8
Last on May 22, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within Virginia, 7,325 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 #:
VA0231515128
Date:
May 30, 2023
Time:
1146
State:
Virginia
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CROSBY TRUCKING SERVICE INC (32052)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 98 3ALXA7CGXJDJV5701 28395PZ (VA) CROSBY TRUCKING SERVICE 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 Fatalities Injuries
cr_5044517 Oct 20, 2025 NC Tow-Away 0 0
cr_5035642 Sep 23, 2025 MO Tow-Away 0 0
cr_5008567 Jul 14, 2025 SC Tow-Away 0 0
cr_4921332 Mar 7, 2025 NJ Tow-Away 0 0
cr_4810650 Sep 9, 2024 NC Tow-Away 0 0
cr_4794512 Aug 16, 2024 VA Tow-Away 0 0
cr_4739280 Apr 28, 2024 TN Tow-Away 0 0
cr_4726421 Mar 7, 2024 IN Tow-Away 0 0
cr_4678560 Dec 22, 2023 VA Injury 0 1
cr_4684701 Dec 14, 2023 GA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
CROSBY TRUCKING SERVICE INC
USDOT 32052 · 208 crashes · 325 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3ALXA7CGXJDJV5701
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
CROSBY TRUCKING SERVICE INC
Crashes reported by this law-enforcement agency.
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.