Update (February 25, 2026): Authorities have identified the woman killed in the accident as Zeeland resident Toni Laws. Her husband, David Laws, was injured in the crash.

Ottawa County, MI — February 17, 2026, one person was killed and another person was injured in a truck accident at about 5:15 a.m. on Port Sheldon Road east of Borculo.

Authorities said a semi-truck allegedly ran a stop sign while going north on 72nd Avenue and collided with an eastbound GMC Sierra, forcing both vehicles into the ditch.

A passenger in the pickup, a 59-year-old Zeeland woman, was pronounced dead at the scene of the Blendon Township crash, according to authorities. The driver, a 56-year-old man, was hospitalized with critical injuries after being removed from the wreckage.

The truck driver suffered non-life-threatening injuries in the crash, authorities said.

Authorities have not released any additional information about the Ottawa County crash at this time. The accident is still under investigation.

Commentary by Attorney Michael Grossman

When people read about a crash like this, the first questions that come to mind are simple: How does a semi-truck run a stop sign? Was the driver distracted? Or is there more to the story than what we’re being told?

According to early reports, authorities say the semi-truck was traveling north on 72nd Avenue and allegedly ran a stop sign before colliding with an eastbound pickup. That sounds straightforward. But in my experience, what sounds simple at first rarely is.

It’s not clear why the truck allegedly failed to stop. Was the driver distracted? Fatigued? Dealing with a mechanical issue? Or is there some dispute about visibility, road conditions or even whether the truck actually stopped but misjudged the pickup’s speed? We don’t yet know. And until investigators pull hard data, we’re left with assumptions.

In any serious truck crash investigation, the first place I look is the truck’s electronic control module, the “black box.” That data can show speed, braking, throttle position and other inputs in the seconds before impact. If the truck never slowed, that’s important. If the brakes were applied but too late, that tells a different story.

Next comes distraction. Was the driver on a cell phone? That won’t be answered without phone records. Many fleets now use inward- and outward-facing dash cameras. If this truck had them, that footage could confirm whether the driver was attentive, looking down or reacting too late.

Then there’s the company behind the wheel. What do we know about the driver’s training and history? Was this driver properly vetted before being hired? Were there prior safety violations? I’ve handled cases where a driver with a troubling record was put on the road after only a brief evaluation. When that happens, responsibility doesn’t stop with the person in the cab.

It’s also not clear whether any road design or visibility issues played a role. Was the stop sign clearly visible at 5:15 a.m.? Were there lighting issues? Depending on those answers, different questions arise about what the driver reasonably should have seen.

Authorities have said the crash remains under investigation. That’s appropriate. But a thorough investigation requires more than a crash report. It requires preserving electronic data, securing video, reviewing driver logs, examining hiring files and analyzing the physical evidence from the scene.

In cases like this, accountability isn’t about jumping to conclusions. It’s about following the evidence wherever it leads. Sometimes that confirms the obvious. Other times it uncovers failures that aren’t visible in a headline.

Key Takeaways

  • A report that a truck “ran a stop sign” raises questions that only black box data, video and phone records can answer.
  • It’s not yet clear why the truck allegedly failed to stop, and that gap matters.
  • Responsibility may extend beyond the driver, depending on hiring, training and supervision practices.
  • A complete investigation requires hard evidence, not assumptions, to determine what really happened.

Explore cases we take