Fillmore County, MN — May 22, 2025, John Peterson was injured in a truck accident at about 8 a.m. on State Highway 44 west of Mabel.

Authorities said an eastbound semi-truck collided with two vehicles that had been headed west, a pickup and an SUV.

John Peterson Injured in Truck Accident near Mabel, MN

Pickup driver John Deloy Peterson, 77, of Mabel was transported to a La Crosse hospital with non-life-threatening injuries after the crash, according to authorities. Truck driver Jeffrey Slowiak, 39, of Granton, WI, was injured as well, but he was not hospitalized.

The Mabel woman who was driving the SUV was not injured, authorities said.

Authorities have not released any additional information about the Fillmore County crash at this time.

Commentary by Attorney Michael Grossman

When people read about a crash like the one that happened just outside Mabel, the first thing they want to know is how did something like this happen? A semi-truck going east reportedly hit two vehicles coming the other way. That raises immediate questions about why a truck would end up in the westbound lane to begin with. Was it a steering error? Did something fail mechanically? Or was the driver distracted?

At this point, the public statements from authorities haven’t filled in those blanks. They’ve confirmed the crash happened around 8 a.m. on Highway 44 and that it involved a pickup, an SUV and an eastbound semi-truck. Two drivers were injured, and one person wasn’t hurt. But what we don’t yet know is why the semi ended up in the path of oncoming vehicles in the first place.

The idea that the semi-truck might have crossed the center line, if that’s indeed what happened, should immediately prompt a detailed investigation. In my experience, that investigation needs to look beyond the crash scene. For example:

  • Was the truck equipped with in-cab cameras or electronic logging devices? These tools often hold critical data about what the driver was doing seconds before the crash.
  • Does the truck’s ECM (engine control module) show any unusual steering, braking or speed changes? That could point to distraction, driver fatigue or even a sudden mechanical failure.
  • What do the driver’s phone records show? If the driver was texting, calling or using an app, that may explain a loss of lane control.
  • What do the trucking company’s hiring and training policies look like? Sometimes the problem isn’t just the driver; it’s how they were vetted and trained in the first place.

I’ve handled more than one case where a trucking company put someone behind the wheel who never should’ve been there. In one, the company’s so-called driver evaluation boiled down to a 20-minute drive around the block, hardly a real test of whether someone can safely handle 80,000 pounds of steel on a busy highway. If something similar happened here, that may turn out to be a key factor.

As of now, it’s not clear whether the semi-truck actually crossed into the westbound lane, or whether the westbound vehicles somehow ended up in the eastbound lane. Depending on how that detail shakes out, the legal analysis could change significantly. It’s also unclear whether weather or road conditions may have played a role.

Until we have access to ECM data, dash cam footage and a full police reconstruction, we’re still only seeing the tip of the iceberg. What matters most now is that someone makes sure all that evidence is secured and examined carefully, because that’s the only way to determine who, if anyone, failed to uphold their responsibilities.


Key Takeaways

  • The most critical unanswered question is what caused the semi-truck to collide with two westbound vehicles.
  • Investigating the truck’s onboard systems, driver conduct and company policies is essential to determine fault.
  • It’s too soon to say whether the truck driver is to blame; facts about lane positioning and driver behavior are still unclear.
  • A full investigation should include black box data, phone records, dash cams and driver hiring practices.
  • Accountability only follows when all the evidence is in and independently verified.

Explore cases we take