Crash Record VA0242535367

FMCSA crash record in HAMPTON CITY on Aug 28, 2024.

Injury Federal Recordable

What happened

On August 28, 2024, FMCSA recorded an injury crash with 2 people hurt in HAMPTON CITY, Virginia. The vehicle was operated by SPIVEY SERVICE CORP (USDOT 4142480). Recorded conditions: 3 / 1 / 1 pavement. FMCSA reference VA0242535367.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

SPIVEY SERVICE CORP

USDOT 4142480

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

4 injury · 7 tow-away

Crashes per 100 power units (24 mo)

25.0

5 crashes · 20 units

Days since prior carrier crash

Last on Jun 18, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 315,866 carriers

Geographic context

How this crash sits in its setting.

Within HAMPTON CITY, Virginia, 23 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

HAMPTON ROADS CONNECTOR PARTNERS · 3 reports
DJDLOGISTICS INC · 1 reports
ASCEND TRANSPORTATION LLC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 3
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 #:: VA0242535367
Date:: Aug 28, 2024
Time:: 0258
State:: Virginia
City:: HAMPTON CITY
Fatalities:: 0
Injuries:: 2
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: SPIVEY SERVICE CORP (4142480)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	5	98	1HTMMAAM07H334041	30331UA (VA)	SPIVEY SERVICE CORP	2	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;3:98:OTHER;4:18:COLLISION INVOLVING FIXED OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cmtv12eia000ppmdihxj9edd6	Sep 3, 2026	VA	Injury	0	2
cr_4944233	May 8, 2025	VA	Tow-Away	0	0
cr_4919310	Mar 29, 2025	VA	Tow-Away	0	0
cr_5013075	Feb 6, 2025	VA	Tow-Away	0	0
cr_4876344	Dec 16, 2024	VA	Fatal	1	0
cr_4807131	Sep 9, 2024	VA	Injury	0	2
cr_4768177	Jun 18, 2024	VA	Tow-Away	0	0
cr_4767366	Jun 18, 2024	VA	Tow-Away	0	0
cr_4752370	May 16, 2024	VA	Tow-Away	0	0
cr_4752369	May 15, 2024	VA	Injury	0	1

Carrier booking & risk tools

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

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

Related records

Vehicle

2007 INTERNATIONAL MA025

NHTSA recalls and complaints for this make/model/year.

Carrier

SPIVEY SERVICE CORP

USDOT 4142480 · 13 crashes · 1 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1HTMMAAM07H334041

Decode this VIN for make, model, year, and recall data.

State

Crashes in Virginia

Statewide crash records.

City

Crashes in HAMPTON 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.