Senator John Cornyn of Texas introduced a bill on February 24 called the Need for Speed Act. The name is pure Capitol Hill showmanship. The substance is a request for the Federal Highway Administration to build a software tool and a unified dataset to track traffic bottlenecks across state lines.
That’s it. That’s the bill.
S.3906 would direct the USDOT to create what Cornyn’s office calls a “national infrastructure intelligence tool,” a platform designed to pull together fragmented highway performance data, commodity flow information, truck parking demand, and urban congestion reports into a single, actionable system. The goal is interstate coordination — letting federal, state, and local governments share information to target infrastructure investments and respond faster when something goes wrong.
Cornyn points to the March 2024 collapse of the Francis Scott Key Bridge in Baltimore as the kind of crisis that exposes how badly the current patchwork system fails. Maryland, his office says, didn’t have the data infrastructure to redirect freight traffic across state lines after the bridge went down. That gap rippled outward — delayed emergency response, disrupted trade, and chaos on alternate routes that weren’t designed to absorb the overflow.
“Incidents like the collapse of the Francis Scott Key Bridge have exposed critical vulnerabilities in our nation’s highway infrastructure, hampering the swift deployment of emergency responders and disrupting millions of dollars in trade and travel,” Cornyn said in a statement.
Fair enough. Nobody argues that fragmented data systems are a good thing. The question is whether another federal platform is the answer, or whether it becomes one more layer of bureaucracy sitting on top of the same crumbling roads.
The bill’s language is deliberately vague, which is typical of legislation that “empowers” an agency to figure out implementation details later. It doesn’t specify a budget. It doesn’t name a technology vendor or framework.
It doesn’t set a timeline for deployment. It tells USDOT to build something smart and useful, then waves it toward the Committee on Environment and Public Works, where it now sits.
The phrase “national intelligence tool” deserves scrutiny. In a trucking and freight context, centralizing commodity movement data and real-time highway performance monitoring raises legitimate questions about surveillance scope. Who gets access? What data gets collected on commercial drivers and private vehicles? The bill doesn’t say.
There’s also the uncomfortable math of priorities. American roads and bridges carry a maintenance backlog measured in the hundreds of billions of dollars. The American Society of Civil Engineers has been handing out near-failing grades for decades.
Spending federal resources on a data platform to better understand where traffic jams happen, while the physical infrastructure generating those jams continues to deteriorate, is a choice.
The Key Bridge collapse wasn’t caused by a data gap. It was caused by a container ship hitting a bridge support. Better cross-state traffic coordination wouldn’t have prevented it.
It might have improved the response afterward — a worthy goal, but a modest one dressed up in a blockbuster name.
Cornyn has a talent for branding. The Need for Speed Act will generate headlines and nods of approval from logistics industry groups who have long wanted better federal data sharing. Whether it generates an actual tool that changes how America manages its highways is another matter entirely.
The bill is in committee. It has no co-sponsors listed yet. In a Senate focused on tariffs, defense spending, and a dozen louder fights, a data-integration bill for highway planning faces the most American of bottlenecks — attention.
Share this Story