Aliases Expose Major Gaps In Driver Licensing

Border inspection station with heavy vehicle traffic — Photo: Arthur Greenberg / Shutterstock

When licensing systems fail to catch identity fraud, people die; that is the hard lesson at the center of the Ohio crash that killed a family of three and triggered Senator Bernie Moreno’s demand that Connecticut explain how a driver using aliases could carry a state-issued credential at all.

The Short Version

Ohio authorities say the truck driver in the fatal crash used multiple names and birthdates to obtain identification documents, including an Ohio CDL.
Sen. Bernie Moreno has asked federal agencies to investigate how state and federal vetting broke down, citing Connecticut’s role in issuing a license linked to a false identity.
Connecticut law voids any state-issued license obtained through misrepresentation and bars applicants who committed identity fraud at the DMV.
States that license undocumented drivers run parallel systems with additional document checks; those systems improve lawful driving access but raise verification and fraud-control challenges.

What is known about the Ohio case

According to Ohio investigators cited by Senator Bernie Moreno and local reporting, the semitruck driver tied to a deadly interstate crash had operated under multiple identities for years, securing an Ohio driver’s license in 2003 and later a commercial driver’s license in 2007 under an alternate identity. Moreno has asked the Departments of Transportation and Homeland Security to determine how the driver accumulated credentials across jurisdictions and whether any steps toward naturalization also relied on the alias. The senator’s letter frames the core failure plainly: if identity proofing breaks, every downstream control — from licensing class eligibility to background checks — is compromised. A brief procedural caveat applies: charges are allegations until adjudicated. But on the question of alias-driven credentials, the record Ohio officials summarized is the point of departure.

Moreno’s inquiry specifically flags Connecticut, asking why and how a license tied to a false identity existed given that state’s statutory posture on fraud. That is not a jurisdictional swipe so much as an accountability map: modern identity ecosystems are interstate by design. A fraudulent identity that penetrates one DMV can bootstrap credibility in another, especially when digital record checks lean on prior issuances as trust anchors.

How Connecticut’s licensing regimes work — and where they can break

Connecticut runs two relevant licensing tracks. First, the standard credentialing system for citizens and permanent residents, which supports REAL ID–verified cards and relies on federal documents for lawful presence. Second, the “drive-only” license program created by Public Act 13-89, which permits residents who cannot show lawful U.S. presence or a Social Security number to obtain a license for driving purposes only; it is explicitly not valid for federal identification and carries distinct markings. Both tracks require proof of identity and state residence, and both are bounded by the same anti-fraud law: any license or certificate issued on the basis of a material false identity statement is void ab initio — invalid from the moment of issuance — and such fraud is chargeable.

The drive-only program is not a loophole; it is an access channel premised on alternative documentation and tighter authentication of residence. The DMV’s Document Integrity Unit publishes guidance for applicants who previously used fake or fraudulent cards and bars eligibility for anyone who committed identity fraud at the Connecticut DMV. Yet the operational challenge is real. In 2019, an NBC Connecticut investigation reported that DMV had revoked drive-only licenses from 87 holders over falsified proof-of-address documents and that the integrity unit had identified numerous suspect submissions. Those revocations demonstrate the system’s corrective muscle. They also illustrate a basic truth: verification is a process, not a binary, and adversaries adapt.

Identity fraud in DMV systems is a known, manageable risk — not an abstraction

State licensing agencies are identity brokers as much as they are testers of driving competence. Audits of DMV populations by outside data-forensics teams routinely uncover deceased identities, duplicates, and synthetic personas seeded through weak points in document workflows. One multi-million-record review by a special investigations unit identified tens of thousands of deceased or otherwise invalid identities in a single state’s files — not because DMV staff are indifferent, but because matching across legacy systems, court records, and federal feeds is an adversarial-data problem. Robust controls reduce the error surface; they do not reduce it to zero.

Connecticut’s legal scaffolding is comparatively strict: void-from-issuance statutes, explicit ineligibility for known identity fraud, and a separate credential class that limits federal reuse. Those elements help contain damage when fraud is caught. The allegation now before federal and state officials is that a false identity evaded those controls long enough to enable interstate credentialing and, years later, a catastrophic outcome in Ohio. The technical question is not whether a drive-only license “caused” a crash; licensing does not drive. The question is whether any Connecticut credential or record lent unwarranted legitimacy to an alias that later qualified for a commercial license elsewhere, and whether identity-proofing safeguards worked as designed.

The policy context: inclusion, safety, and fraud controls can coexist — if engineered well

States have diverged on whether to allow undocumented residents to drive lawfully. Where they do, academic and policy literature shows mixed but instructive effects. Studies in large markets like California have found that opening legal channels to licensing and insurance did not increase total accidents or fatal crashes, and did reduce hit-and-run collisions — the predictable outcome when drivers no longer flee to avoid cascading penalties for unlicensed operation. Other work has estimated small increases in fatal crashes associated with licensing expansions in specific contexts, reminding policymakers that design and enforcement details matter. Meanwhile, economic analyses point to improved access to jobs and services as more residents can lawfully commute.

The throughline for administrators is consistent across the research and practice: if you choose an inclusive licensing policy, you must pair it with serious document authentication. That means curated lists of acceptable foreign IDs; verification workflows informed by consulates and community intermediaries; and purpose-built integrity units with data-matching tools to detect duplicates and synthetic identities before issuance, not after. Connecticut’s statutes and guidance largely reflect that playbook; Moreno’s challenge is whether execution matched intent in the case at hand.

What accountability and reform look like

The right investigative sequence is straightforward. First, reconstruct the identity chain: source documents presented, databases queried, external verifications attempted, and any exceptions granted. Second, trace interstate propagation: where a Connecticut record, if present, was used as a trust anchor for subsequent issuances or vetting in other states. Third, apply the consequence architecture already on the books: if any Connecticut license was fraudulently obtained, it is void by statute, and the applicant should be ineligible for drive-only consideration going forward; if personnel or procedural lapses surfaced, remediate with training, system controls, or both.

For the public, the stakes are not abstract. Commercial drivers operate heavy vehicles on shared roads; the credential that places them behind the wheel must be linked to a real, verified person with a clean safety history under that same identity. When aliasing defeats the linkage, safety regulators cannot see risk clearly, insurers cannot price it honestly, and law enforcement cannot attribute violations accurately. Identity-proofing is therefore not a bureaucratic nicety. It is a core safety function.