Crash Record MN0232070096
FMCSA crash record in SAINT MARY on Jul 26, 2023.
Tow-Away
Federal Recordable
What happened
On July 26, 2023, FMCSA recorded a tow-away crash with no reported injuries in SAINT MARY, Minnesota. The vehicle was operated by CRYSTAL VALLEY COOPERATIVE (USDOT 840516). Recorded conditions: 1 / 1 / 1 pavement. Reported by CRYSTAL VALLEY COOPERATIVE, FMCSA reference MN0232070096.
Fatalities
0
Injuries
0
Vehicles
2
Carrier
CRYSTAL VALLEY COOPERATIVE
Vehicle Type
Truck
Severity
Tow-Away
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
2
0 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.8
1 crashes · 120 units
Days since prior carrier crash
392
Last on Jun 29, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers
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 #:
- MN0232070096
- Date:
- Jul 26, 2023
- Time:
- 1421
- State:
- Minnesota
- City:
- SAINT MARY
- Fatalities:
- 0
- Injuries:
- 0
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- CRYSTAL VALLEY COOPERATIVE (840516)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 6 | 4 | 2NP3LJ9X3LM705921 | YBZ3245 (MN) | CRYSTAL VALLEY COOPERATIVE | 3 | Yes |
Crash event
Event sequence description.
1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT
Other crashes by this carrier
10 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_4954602 | Jun 2, 2025 | MN | Injury | 0 | 1 |
| cr_4706390 | Feb 19, 2024 | MN | Injury | 0 | 2 |
| cr_4379753 | Jun 29, 2022 | MN | Tow-Away | 0 | 0 |
| cr_3789014 | May 10, 2019 | MN | Tow-Away | 0 | 0 |
| cr_3705618 | Dec 12, 2018 | MN | Tow-Away | 0 | 0 |
| cr_3480720 | Oct 19, 2017 | MN | Tow-Away | 0 | 0 |
| cr_3388003 | Apr 22, 2017 | MN | Injury | 0 | 1 |
| cr_3216981 | May 20, 2016 | MN | Injury | 0 | 1 |
| cr_3215063 | May 19, 2016 | MN | Tow-Away | 0 | 0 |
| cr_2938136 | Oct 28, 2014 | MN | Injury | 0 | 1 |
Related records
Carrier
CRYSTAL VALLEY COOPERATIVE
USDOT 840516 · 17 crashes · 21 inspections
Vehicle
VIN: 2NP3LJ9X3LM705921
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
CRYSTAL VALLEY COOPERATIVE
Crashes reported by this law-enforcement agency.
City
Crashes in SAINT MARY, MN
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.