WeVote
Log In

Bill

JS

Bill

HR 8640

To direct the Administrator of the Federal Motor Carrier Safety Administration to establish and maintain a database for commercial driver's license data, and for other purposes.

119th Congress Introduced by Jefferson Shreve

The bill would require FMCSA to establish and maintain a centralized database of commercial driver’s license data to improve safety, enforcement, and data access.

Introduced in House
0
WeVote Research Nonpartisan
Bill Summary · HR 8640

Summary of HR 8640 (118th or 119th Congress? — As Provided)

Note: This summary is based on the bill title and provided action history. If there are additional text sections in the official bill, those should be consulted for precise statutory language.

Basic Information

  • Bill (Official): HR 8640
  • Session: 119
  • Jurisdiction: United States
  • Short Title / Purpose (per provided title): To direct the Administrator of the Federal Motor Carrier Safety Administration to establish and maintain a database for commercial driver's license data, and for other purposes.
  • Introduced: April 30, 2026 (House)
  • Referral: Referred to the House Committee on Transportation and Infrastructure (T&I) on April 30, 2026
  • Sponsors: Primary sponsor not listed in the provided snippet; co-sponsor identified as Jefferson Shreve

Objective and Intent

  • The bill aims to direct the Administrator of the Federal Motor Carrier Safety Administration (FMCSA) to establish and maintain a database for commercial driver’s license (CDL) data.
  • The overarching goal appears to be improving the collection, storage, and accessibility of CDL-related information to support safety, compliance, and enforcement related to commercial motor vehicles.

Key Provisions (Inferred from Title)

Since the text of the bill isn’t provided here, the following provisions are typical for a bill with this title. Readers should verify the final statutory language for exact scope and definitions.

  1. Establishment of a CDL Data Database

    • FMCSA would create a centralized database to house CDL-related data.
    • Data categories may include, but are not limited to, CDL issuance, endorsements, disqualifications, suspensions/revocations, medical certificates, driving history, and enforcement actions.

  2. Data Management and Maintenance

    • Standards for data quality, privacy protections, access controls, and data retention timelines.
    • Procedures for regular updating from state Departments of Motor Vehicles (DMVs) or state licensing authorities and FMCSA enforcement records.

  3. Interoperability and Access

    • Mechanisms for sharing data with authorized federal and possibly state agencies (e.g., FMCSA, state DMVs, law enforcement, and safety regulators).
    • Potential provisions to support interstate and intrastate commerce while safeguarding personal information.

  4. Uses and Purposes

    • Enhance safety enforcement and compliance monitoring for commercial drivers.
    • Support for investigations of CDL-related violations and safety audits.
    • Potentially support risk-based licensing decisions or enforcement prioritization.

  5. Privacy and Civil Liberties Considerations

    • Provisions to protect personally identifiable information (PII) and ensure lawful use of data.
    • Compliance with applicable privacy laws and data security standards.

  6. Funding and Implementation Timeline

    • Authorization of appropriations or use of existing FMCSA funding to establish and operate the database.
    • Timeline milestones for development, pilot testing, and full deployment.

  7. Reporting and Oversight

    • Administrative reporting requirements to Congress on progress, expenditures, and data governance.
    • Possible sunset or review provisions to assess effectiveness.

Affected Parties

  • Federal Level: FMCSA and the U.S. Department of Transportation (DOT) would implement and administer the database.
  • State Level: State DMVs/licensing authorities would likely contribute data and participate in data sharing; may have reporting and data exchange responsibilities.
  • Authorized Users: Federal and state enforcement agencies, safety inspectors, and other approved entities with legitimate needs to access CDL data.
  • Commercial Drivers: CDL holders would be affected through enhanced recordkeeping; privacy protections would govern what data is accessible and by whom.

Procedural and Timeline Considerations

  • Status: Introduced and referred to the Committee on Transportation and Infrastructure on April 30, 2026.
  • Next Steps: Committee hearings, markup, and potential floor consideration. If enacted, rulemaking, procurement, and system development activities would follow, with implementation phased per bill specifics.

Notes for Readers

  • The above summary focuses on the bill’s stated purpose to create a CDL data database and typical accompanying provisions. For precise definitions (e.g., “CDL data” scope, data-sharing limits, enforcement mechanisms, penalties for noncompliance) and exact timelines, consult the full bill text and any committee reports or amendments.
  • As always, watch for subsequent action history (committee reports, amendments, or floor amendments) that can modify scope and impact.

Compiled from official sources — confirm details with the bill’s official record.

Sign in to ask a question.