The Database Is the Problem, Not Just Transdev

In April 2025, a Boston kindergartner named Lens Joseph was run over by his own school bus. The bus was operated by Transdev, one of the largest private operators of public transit in the United States. When WBUR and ProPublica went to check Transdev's federal safety record, they found no sign the company was involved in the crash at all.

That is not a filing error. That is a system telling you something about itself.

The investigation, published in June, identified at least 42 fatal crashes connected to Transdev over the past decade that were absent from its federal record. Sens. Maria Cantwell (D-WA) and Ed Markey (D-MA) — the ranking Democrats on the Senate Commerce, Science, and Transportation Committee — subsequently sent a formal letter to the Federal Motor Carrier Safety Administration demanding documentation: proof that FMCSA can detect troubled operators, an explanation of why enforcement actions have dropped dramatically under the current administration, and all inspection and crash records related to Transdev. The deadline is August 12.

The Department of Transportation responded that it "shares the Senators' commitment to the safe transportation of America's children" and is "currently investigating the matter." Transdev said it "complies with all applicable laws and regulatory requirements" and has "always followed federal regulations, as prescribed."

Both responses are, in their own way, informative.

---

FMCSA's safety database is only as accurate as the reporting pipelines feeding it. Law enforcement agencies, state DMVs, and carriers themselves all have roles in that pipeline. When a crash occurs, the record connecting a specific operating company to that incident depends on someone — often a local police officer filling out a crash report — accurately identifying and recording the carrier. When enforcement atrophies, the gaps in that pipeline compound quietly. The official record does not degrade with a warning label. It just stops describing what actually happened.

The senators' letter asks FMCSA to explain why enforcement actions have dropped "dramatically" under the current administration. That is the structural question underneath the Transdev story. One company with 42 missing fatal crashes is alarming on its own terms. A regulator whose enforcement capacity has visibly contracted — and whose reduced presence therefore allows exactly this kind of gap to persist — is a different order of problem.

---

The best innocent explanation is worth taking seriously. The reporting pipeline for commercial vehicle crashes is genuinely complicated. Local law enforcement agencies do not always correctly identify which company operated a given vehicle. A bus under a municipal contract may be recorded as a city fleet vehicle rather than a Transdev vehicle. Some of those 42 missing crashes may reflect local reporting failures rather than federal enforcement failures, and untangling the two requires the document-by-document review the senators are now demanding.

Transdev's statement — that it has always followed federal regulations "as prescribed" — is doing real work here. If the prescribed process puts the burden of accurate carrier identification on local law enforcement, Transdev can comply with its own reporting obligations and still be invisible in the record whenever a local officer mis-codes the carrier. That is a genuine design flaw in the system, not necessarily evidence of deliberate concealment.

But this is precisely why the senators' second question matters more than their first. If the answer to "why are 42 crashes missing?" turns out to be "local law enforcement didn't identify the carrier correctly," then FMCSA's enforcement mechanism should have been catching that through its own inspections and cross-referencing. The senators asked what guidance FMCSA provides to law enforcement on how to report carrier involvement. That question goes directly to whether the agency is managing the pipeline or merely receiving whatever the pipeline delivers.

A regulator that passively accepts the data it receives is not really a safety regulator. It is a filing cabinet.

---

Three facts from the investigation are worth sitting with together. At least two crashes beyond Lens Joseph's resulted in criminal charges against Transdev bus drivers — a guilty plea in a 2017 Massachusetts death, a guilty plea in a 2023 Las Vegas death, and an ongoing felony involuntary manslaughter case in Boston. None appear to have triggered a visible enforcement response in the federal record. And the investigation began because a five-year-old's death left no trace in the database of the company that operated the bus that killed him.

Courts convicted or are prosecuting Transdev drivers in multiple states. The federal safety record reflected none of it.

At some point, the gap between what the courts know and what the regulator knows is not a data pipeline problem. It is an enforcement presence problem.

---

The senators are Democrats asking questions of a Republican administration, and the political framing will be applied accordingly. It is worth noting that the WBUR/ProPublica investigation spans a decade of crashes across multiple administrations. Enforcement atrophy at FMCSA is not a single-administration story. The senators' letter is sharper than its press statement framing suggests — it asks for documentation of what the agency's enforcement processes actually are, which is the right question regardless of who currently runs the building.

The question is not whether Transdev is the villain or the victim of a broken reporting system.

The question is what it means when the federal safety record for a company with documented fatal crashes, criminal convictions, and ongoing prosecutions shows no sign of any of it.

The data is incomplete. That is not a minor administrative observation.

It is the whole problem.