Rossville, MD — June 4, 2025, a pedestrian was killed in a a bus accident at about 1:55 p.m. at the intersection of Philadelphia and Ridge roads.
Authorities said a school bus hit a pedestrian near the intersection.
The pedestrian, a woman whose name has not been made public yet, was pronounced dead at the scene of the crash, according to authorities.
The bus, which was contracted to Baltimore City Public Schools, was reportedly on its way to pick up students at the time of the crash.
Authorities have not released any additional information about the Baltimore County crash at this time.
Commentary by Attorney Michael Grossman
When people hear that a school bus hit and killed someone in the middle of the day, their first questions aren’t legal; they’re practical. How did this happen? Was the bus driver distracted? Did the pedestrian step out unexpectedly? Was anyone watching the road? The short answer is, we don’t know yet. And that’s precisely why a thorough investigation matters.
At the time of the crash, reports say the school bus was on its way to pick up students. That gives us one possible context: this wasn’t a case of a bus sitting still or parked. It was moving. But what else was going on? Was the driver using a phone? Was there an issue with visibility at that intersection? Did the bus have dash cams or any in-cab monitoring equipment that might show what the driver was doing at the moment of impact?
Those questions aren’t just idle curiosity; they’re the starting point for determining accountability. In my experience, one of the first things investigators should look for is whether the bus had an event data recorder or engine control module (ECM). These systems can tell you things like the bus’s speed, whether the brakes were applied and how the driver responded (or didn’t) in the seconds before impact.
And while there’s a tendency to assume that a crash involving a pedestrian must be the pedestrian’s fault, or the driver’s, the reality is far more complicated. Intersections are dynamic environments. Visibility can be limited. Traffic signals may malfunction. And most importantly, even when the facts are unclear, technology and records can help fill in the blanks.
Another layer here is the fact that the bus was contracted to Baltimore City Public Schools. That raises yet another round of questions: What training did the driver receive? Who hired the driver? What vetting process was in place? In other cases I’ve handled, I’ve seen situations where school contractors failed to perform meaningful background checks or provided drivers with minimal training. If something like that happened here, then it’s not just the driver under scrutiny; it’s the company that put them behind the wheel.
Right now, authorities haven’t released enough information to draw any conclusions. But if the goal is to get to the truth, and to prevent this kind of incident from happening again, then investigators will need to go beyond the scene itself. That means digging into cell phone records, camera footage, driver logs and anything else that can provide clarity.
Key Takeaways
- We don’t yet know what caused the bus to hit the pedestrian, and that’s the key question that needs answering.
- Critical evidence could include dash cam footage, ECM data and cell phone records to assess driver behavior.
- The bus was under contract with a school district, which raises questions about driver vetting and training.
- Accountability in cases like this depends on a full investigation, not assumptions based on limited information.
- Technology and records are often the only reliable way to understand what really happened and who may be responsible.
call us 
Email Us 
Text us