Crash Record MI0002522332
FMCSA crash record in FIFE LAKE TWP on Feb 24, 2022.
Tow-Away
Federal Recordable
What happened
On February 24, 2022, FMCSA recorded a tow-away crash with no reported injuries in FIFE LAKE TWP, Michigan. The vehicle was operated by BRENNER OIL COMPANY (USDOT 355912). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference MI0002522332.
Carrier pattern note
This is the carrier's 7 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.
Fatalities
0
Injuries
0
Vehicles
2
Carrier
BRENNER OIL COMPANY
Vehicle Type
Truck
Severity
Tow-Away
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
7
0 injury · 7 tow-away
Crashes per 100 power units (24 mo)
5.1
7 crashes · 136 units
Days since prior carrier crash
22
Last on Feb 2, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,687 carriers
Geographic context
How this crash sits in its setting.
Within FIFE LAKE TWP, Michigan, 5 other commercial vehicle crashes have been recorded in the past 24 months.
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 #:
- MI0002522332
- Date:
- Feb 24, 2022
- Time:
- 1551
- State:
- Michigan
- City:
- FIFE LAKE TWP
- Fatalities:
- 0
- Injuries:
- 0
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- BRENNER OIL COMPANY (355912)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 2 | 9 | 4 | 1XPBD49X2ED250472 | RC09762 (MI) | BRENNER OIL COMPANY | 3 | No |
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_5085622 | Jan 6, 2026 | MI | Tow-Away | 0 | 0 |
| cr_5020488 | May 18, 2025 | MI | Tow-Away | 0 | 0 |
| cr_4932573 | Apr 11, 2025 | FL | Injury | 0 | 3 |
| cr_4923001 | Mar 22, 2025 | FL | Tow-Away | 0 | 0 |
| cr_4909604 | Feb 18, 2025 | MI | Tow-Away | 0 | 0 |
| cr_4858411 | Nov 22, 2024 | MI | Injury | 0 | 1 |
| cr_4828136 | Oct 2, 2024 | MI | Tow-Away | 0 | 0 |
| cr_4712413 | Feb 26, 2024 | MI | Tow-Away | 0 | 0 |
| cr_4704787 | Feb 5, 2024 | MI | Tow-Away | 0 | 0 |
| cr_4681712 | Dec 23, 2023 | MI | Tow-Away | 0 | 0 |
Related records
Vehicle
2014 PETERBILT 579
NHTSA recalls and complaints for this make/model/year.
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
18V816000
EXTERIOR LIGHTING
Recall
17V471000
ELECTRICAL SYSTEM:WIRING:FUSES AND CIRCUIT BREAKERS
Carrier
BRENNER OIL COMPANY
USDOT 355912 · 124 crashes · 124 inspections
Vehicle
VIN: 1XPBD49X2ED250472
Decode this VIN for make, model, year, and recall data.
State
Crashes in Michigan
Statewide crash records.
City
Crashes in FIFE LAKE TWP, MI
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.