Crash Record CA3652201229

FMCSA crash record in VALLEJO on Jul 20, 2022.

Injury Federal Recordable

What happened

On July 20, 2022, FMCSA recorded an injury crash with one person hurt in VALLEJO, California. The vehicle was operated by ATECH LOGISTICS INC (USDOT 1047145). Recorded conditions: 2 / 1 / 1 pavement. Reported by ATECH LOGISTICS INC, FMCSA reference CA3652201229.

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.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

ATECH LOGISTICS INC

USDOT 1047145

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

4 injury · 13 tow-away

Crashes per 100 power units (24 mo)

8.4

15 crashes · 178 units

Days since prior carrier crash

Last on May 14, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,134 carriers

Geographic context

How this crash sits in its setting.

Within VALLEJO, California, 32 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: 2
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 #:: CA3652201229
Date:: Jul 20, 2022
Time:: 0155
State:: California
City:: VALLEJO
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: ATECH LOGISTICS INC (1047145)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1HSDGAPN9EH781895	9E91394 (CA)	ATECH LOGISTICS INC	3	No

Crash event

Event sequence description.

2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cmtazy7kw0039pmlntvg5fp17	Aug 20, 2026	OR	Tow-Away	0
cmokyirl7004nnv1daavmfe0g	Apr 23, 2026	AZ	Tow-Away	0
cr_5108458	Feb 18, 2026	AZ	Tow-Away	0
cr_5084667	Dec 17, 2025	WA	Tow-Away	0
cr_5125566	Nov 20, 2025	NM	Tow-Away	0
cr_5045541	Oct 7, 2025	NV	Tow-Away	0
cr_5042359	Sep 19, 2025	AZ	Tow-Away	0
cr_5020238	Jul 25, 2025	CA	Injury	1
cr_4990291	Jun 20, 2025	CA	Injury	1
cr_4941065	Apr 29, 2025	CA	Tow-Away	0

Carrier booking & risk tools

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

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

Related records

Carrier

ATECH LOGISTICS INC

USDOT 1047145 · 106 crashes · 592 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1HSDGAPN9EH781895

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

State

Crashes in California

Statewide crash records.

Agency

ATECH LOGISTICS INC

Crashes reported by this law-enforcement agency.

City

Crashes in VALLEJO, CA

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.