Skip to main content
TruckCodex
Hubs

Crash Record CA8602110088

FMCSA crash record in GRAND TERRACE on May 24, 2021.

Injury Federal Recordable

What happened

On May 24, 2021, FMCSA recorded an injury crash with 2 people hurt in GRAND TERRACE, California. The vehicle was operated by PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC (USDOT 2387259). Recorded conditions: 1 / 1 / 1 pavement. Reported by PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC, FMCSA reference CA8602110088.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
2
Carrier
PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC
USDOT 2387259
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 injury · 4 tow-away
Crashes per 100 power units (24 mo)
5.3
3 crashes · 57 units
Days since prior carrier crash
183
Last on Nov 22, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,042 carriers

Geographic context

How this crash sits in its setting.

Within GRAND TERRACE, California, 5 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 #:
CA8602110088
Date:
May 24, 2021
Time:
0538
State:
California
City:
GRAND TERRACE
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC (2387259)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 4 1FVHCYBS4DHFE7032 39829W2 (CA) PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5027357 Aug 13, 2025 CA Injury 0 1
cr_4923555 Mar 7, 2025 CA Injury 0 1
cr_4845558 Oct 23, 2024 CA Injury 0 1
cr_4858698 Oct 5, 2024 CA Injury 0 1
cr_4825585 Sep 29, 2024 CA Tow-Away 0 0
cr_4709863 Dec 19, 2023 CA Tow-Away 0 0
cr_4597433 Jul 29, 2023 CA Tow-Away 0 0
cr_4509196 Jan 31, 2023 CA Tow-Away 0 0
cr_4427119 Sep 18, 2022 CA Tow-Away 0 0
cr_4243094 Oct 5, 2021 CA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2013 FREIGHTLINER M2
NHTSA recalls and complaints for this make/model/year.
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
18V094000
EQUIPMENT
Recall
17V739000
EQUIPMENT
Carrier
PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC
USDOT 2387259 · 21 crashes · 37 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FVHCYBS4DHFE7032
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
PETERSON CHASE GENERAL ENGINEERING CONSTRUCTION INC
Crashes reported by this law-enforcement agency.
City
Crashes in GRAND TERRACE, 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.