Skip to main content
TruckCodex
Hubs

Crash Record VA0232815274

FMCSA crash record in Virginia on Oct 5, 2023.

Injury Federal Recordable

What happened

On October 5, 2023, FMCSA recorded an injury crash with 3 people hurt in Virginia. The vehicle was operated by PYRAMID MOVING LLC (USDOT 2210417). Recorded conditions: 1 / 1 / 1 pavement. Reported by PYRAMID MOVING LLC, FMCSA reference VA0232815274.

Carrier pattern note

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

Fatalities
0
Injuries
3
Vehicles
5
Carrier
PYRAMID MOVING LLC
USDOT 2210417
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
52
3 fatal · 15 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 279 units
Days since prior carrier crash
8
Last on Sep 27, 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,264 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 #:
VA0232815274
Date:
Oct 5, 2023
Time:
1520
State:
Virginia
Fatalities:
0
Injuries:
3
Tow-Away:
Yes
HazMat:
No
Vehicles:
5
Carrier (USDOT):
PYRAMID MOVING LLC (2210417)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDR6KSHU6121 P1160488 (IL) PYRAMID MOVING 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_4681317 Dec 30, 2023 FL Injury 0 1
cr_4692004 Dec 23, 2023 KS Tow-Away 0 0
cr_4666745 Dec 10, 2023 VA Tow-Away 0 0
cr_4666398 Dec 4, 2023 OH Tow-Away 0 0
cr_4728250 Dec 1, 2023 CO Tow-Away 0 0
cr_4660726 Nov 21, 2023 NV Injury 0 1
cr_4650672 Nov 13, 2023 NE Tow-Away 0 0
cr_4716921 Oct 26, 2023 IL Tow-Away 0 0
cr_4650840 Oct 24, 2023 PA Tow-Away 0 0
cr_4668066 Oct 11, 2023 MD Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
PYRAMID MOVING LLC
USDOT 2210417 · 91 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR6KSHU6121
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
PYRAMID MOVING LLC
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.