Skip to main content
TruckCodex
Hubs

Crash Record VA0231765235

FMCSA crash record in VIRGINIA BEACH CITY on Jun 23, 2023.

Injury Federal Recordable

What happened

On June 23, 2023, FMCSA recorded an injury crash with one person hurt in VIRGINIA BEACH CITY, Virginia. The vehicle was operated by SALMONS CONCRETE HAULING INC (USDOT 3222697). Recorded conditions: 1 / 2 / 2 pavement. Reported by SALMONS CONCRETE HAULING INC, FMCSA reference VA0231765235.

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
SALMONS CONCRETE HAULING INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
2 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 32 units
Days since prior carrier crash
385
Last on Jun 3, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,547 carriers

Geographic context

How this crash sits in its setting.

Within VIRGINIA BEACH CITY, Virginia, 61 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
2
Road surface
2

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 #:
VA0231765235
Date:
Jun 23, 2023
Time:
0934
State:
Virginia
City:
VIRGINIA BEACH CITY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
SALMONS CONCRETE HAULING INC (3222697)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 7 1NKWXUTX74J397176 20734TB (VA) SALMONS CONCRETE HAULING INC 3 No

Crash event

Event sequence description.

3:18:COLLISION INVOLVING FIXED OBJECT;1:8:NONCOLLISION:CROSS MEDIAN/CENTERLINE;4:17:COLLISION INVOLVING ANIMAL;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

6 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4806018 Sep 3, 2024 VA Injury 0 1
cr_4718267 Mar 14, 2024 VA Tow-Away 0 0
cr_4721895 Feb 28, 2024 VA Tow-Away 0 0
cr_4681030 Sep 11, 2023 VA Injury 0 1
cr_4375148 Jun 3, 2022 VA Injury 0 1
cr_4110012 Feb 9, 2021 NC Injury 0 1

Related records

Vehicle
2004 KENWORTH W900
NHTSA recalls and complaints for this make/model/year.
Recall
09V239000
SERVICE BRAKES, AIR
Recall
08V485000
SUSPENSION
Recall
07V107000
POWER TRAIN:AUTOMATIC TRANSMISSION
Carrier
SALMONS CONCRETE HAULING INC
USDOT 3222697 · 7 crashes · 10 inspections
Vehicle
VIN: 1NKWXUTX74J397176
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
SALMONS CONCRETE HAULING INC
Crashes reported by this law-enforcement agency.
City
Crashes in VIRGINIA BEACH CITY, VA
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.