Elkhart County, IN —February 11, 2026, Mildred Weiser was killed and two other people were injured in a truck accident at about 5 p.m. on County Road 5/Elkhart Road.
Authorities said a work truck crossed into oncoming traffic and collided head-on with a Nissan sedan.
A passenger in the Nissan, 67-year-old Edwardsburg resident Mildred Weiser, died in the crash near Elkhart, while the driver and another passenger were hospitalized with unspecified injuries, according to authorities.
The truck driver suffered minor injuries, authorities said.
Authorities have not released any additional information about the Elkhart County crash at this time. The accident is still under investigation.
Commentary by Attorney Michael Grossman
When people read about a head-on crash like this, the first question that comes to mind is simple: how does a work truck end up in oncoming traffic in the middle of the afternoon? Vehicles don’t just drift across the center line for no reason. Something caused it. The real issue is figuring out what.
Right now, authorities say a work truck crossed into oncoming traffic and hit a Nissan sedan head-on. A passenger in the Nissan was killed, two others were hurt and the truck driver reportedly suffered minor injuries. But beyond that, we’re told very little. The crash is still under investigation.
That leaves several critical questions unanswered.
It’s not clear why the truck crossed the center line. Was the driver distracted? Fatigued? Dealing with a medical issue? Did something mechanical fail? Depending on what caused the truck to move into opposing traffic, responsibility could fall in very different places.
This is where evidence matters more than assumptions.
Most work trucks today contain an engine control module, its “black box.” That data can show speed, braking, throttle position and sometimes steering input in the moments before impact. If the truck never slowed, that raises one set of concerns. If there was hard braking or a sudden steering correction, that suggests something else entirely.
It’s also not clear whether the driver was using a cell phone at the time. That’s not something anyone can answer without reviewing call and data records. Many companies also install in-cab cameras, which can show whether a driver was looking at the road, distracted or reacting to something unexpected. If such systems were in place, they could provide objective answers.
Then there’s the company side of the equation. This was described as a “work truck,” which suggests the driver may have been operating in the course of employment. If so, the company’s role becomes relevant. What were the driver’s qualifications? Was the driver properly trained? Were there prior incidents? What kind of supervision was in place? These aren’t abstract legal questions; they go directly to whether this crash was an isolated mistake or the result of preventable decisions.
In my experience handling truck cases, crossing the center line is often treated as an open-and-shut case against the driver. Sometimes it is. But not always. I’ve seen cases where a deeper investigation revealed hiring shortcuts, ignored safety histories or mechanical issues that never should have been left unaddressed. The only way to know is to gather the evidence and follow it where it leads.
At this stage, we simply don’t yet know why this truck entered oncoming traffic. Until investigators review electronic data, vehicle condition, driver history and company policies, any conclusion about fault is incomplete.
When serious crashes happen, the public deserves more than a basic summary. They deserve answers grounded in verifiable facts.
Key Takeaways
- A vehicle crossing the center line is a result, not an explanation. The cause still needs to be identified.
- Black box data, cell phone records and in-cab video can provide objective answers about what happened.
- If the driver was working at the time, company hiring, training and oversight may also be relevant.
- The crash remains under investigation, and key facts about distraction, mechanical failure or medical issues are still unknown.
