Crash Record CA5752301480
FMCSA crash record in GLENDALE on Apr 27, 2023.
Injury
Federal Recordable
What happened
On April 27, 2023, FMCSA recorded an injury crash with one person hurt in GLENDALE, California. The vehicle was operated by EVERSOFT INC (USDOT 2612072). Recorded conditions: 1 / 1 / 1 pavement. Reported by EVERSOFT INC, FMCSA reference CA5752301480.
Geographic note
This crash is part of an active corridor: 40 crashes occurred in the same city in the past 24 months.
Fatalities
0
Injuries
1
Vehicles
2
Carrier
EVERSOFT INC
Vehicle Type
Truck
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
2
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
4.2
1 crashes · 24 units
Days since prior carrier crash
162
Last on Nov 16, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,670 carriers
Geographic context
How this crash sits in its setting.
Within GLENDALE, California, 40 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- CITY OF GLENDALE · 4 reports
- LOS ANGELES COUNTY METROPOLITAN TRANSPORTATION AUTHORITY · 2 reports
- ALDO CLAUDIO JR · 1 reports
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 #:
- CA5752301480
- Date:
- Apr 27, 2023
- Time:
- 1405
- State:
- California
- City:
- GLENDALE
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- No
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- EVERSOFT INC (2612072)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 5 | 5 | 2NP2HM6X4LM676979 | 03947L2 (CA) | EVERSOFT INC | 2 | No |
Crash event
Event sequence description.
1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT
Other crashes by this carrier
6 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_5024443 | Aug 29, 2025 | CA | Tow-Away | 0 | 0 |
| cr_4726696 | Mar 18, 2024 | CA | Tow-Away | 0 | 0 |
| cr_4468109 | Nov 16, 2022 | CA | Tow-Away | 0 | 0 |
| cr_3569713 | Mar 10, 2018 | CA | Tow-Away | 0 | 0 |
| cr_3536946 | Jan 9, 2018 | CA | Injury | 0 | 1 |
| cr_3089771 | Jul 14, 2015 | CA | Injury | 0 | 2 |
Related records
Vehicle
2020 PETERBILT 337
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V391000
FUEL SYSTEM, DIESEL:FUEL INJECTION SYSTEM:FUEL RAIL
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Carrier
EVERSOFT INC
USDOT 2612072 · 7 crashes · 103 inspections
Vehicle
VIN: 2NP2HM6X4LM676979
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
EVERSOFT INC
Crashes reported by this law-enforcement agency.
City
Crashes in GLENDALE, 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.