The Database Is the Problem, Not Just Transdev
A Boston kindergarten death was filed in federal records under the City of Boston, not the company that operated the bus. The Transdev gap is real — but the deeper question the senators are asking is whether FMCSA is managing its own database or just receiving it.
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 the crash listed under "CITY OF BOSTON MVMB," the city's Motor Vehicle Management Bureau, with no sign the company was involved.
That is a filing problem. It is also a system telling you something about itself.
The investigation, published in June, identified at least 60 fatal crashes involving Transdev-operated buses from 2016 through 2025; 42 were not listed under Transdev's name — 40 filed under other names, two not in the database at all. Sen. Maria Cantwell (D-WA), the ranking member of the Senate Commerce, Science, and Transportation Committee, and Sen. Ed Markey (D-MA) subsequently sent a formal letter to the Federal Motor Carrier Safety Administration demanding documentation: how FMCSA monitors the safety of carriers that transport students, why its closed enforcement cases declined in fiscal 2025, and all inspection and crash records involving Transdev. The deadline was August 12, 2026, and it has passed.
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 its closed enforcement cases fell from nearly 4,000 in fiscal 2024 to about 1,400 in fiscal 2025, a 65 percent decrease. 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 caseload has fallen that sharply, while its data misses a carrier's fatal crashes, 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. Many of those 42 crashes reflect how local officers recorded the carrier 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.
FMCSA has seen this before. A 2016 agency review of Transdev found "numerous crashes" missing from its record and told the company that "this self reporting is required for accurate evaluation by FMCSA and the accurate safety record of the carrier." The planned "conditional" rating was dropped after Transdev appealed. According to FMCSA's own figures cited in the senators' letter, Transdev had been involved in 187 crashes in the 24 months before the July 29 letter, seven fatal, with no enforcement actions and a "Satisfactory" rating.
The criminal cases are worth sitting with together. Lens Joseph's death and at least two others resulted in criminal charges against Transdev bus drivers: a guilty plea to misdemeanor negligent operation in a 2017 Taunton, Massachusetts death; a guilty plea to misdemeanor vehicular manslaughter in a 2023 Las Vegas death; and an ongoing felony involuntary manslaughter case in Boston, where the driver has pleaded not guilty. The 2017 and 2023 crashes are listed in the federal database under the transit agencies that hired Transdev, not under Transdev.
Courts convicted or are prosecuting Transdev drivers in multiple states. Transdev's own federal safety record reflects none of those crashes.
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. The data gap predates the current administration; the 65 percent enforcement drop the senators cite is from fiscal 2024 to fiscal 2025. The letter 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 an ongoing prosecution does not show most of them.
The data is incomplete. That is not a minor administrative observation.
It is the whole problem.
Sources
- https://www.propublica.org/article/boston-school-bus-crash-record-lens-joseph-transdev
- https://www.wbur.org/news/2026/06/08/massachusetts-bus-crashes-transdev-lens-joseph
- https://www.wbur.org/news/2026/07/29/senate-markey-cantwell-dot-regulators-school-bus-data
- https://www.commerce.senate.gov/press/dem/release/cantwell-and-markey-call-out-critical-gaps-in-fatal-accident-data-involving-large-trucks-and-buses/
Don't take my word for it. The sources are above — do the research yourself.
The Daily Edition
Get the next investigation in your inbox.
The day's reporting, ranked and sourced, in your inbox each morning. No spin, no paywall.
Reader-supported
Support the work
Independent, reader-supported media intelligence — every article free to read, every claim traced to a primary document, no paywall. If this was useful, a donation keeps it going.
Choose an amount
More ways to give on the donate page. Cory Rove is not a registered charity — donations are gifts and not tax-deductible.