Intrastate truck driver hours-of-service rules by state — where they differ from federal
The hours-of-service rules for commercial drivers operating solely within one state, per state: maximum driving hours per shift, the on-duty window, the weekly/cycle cap, the short-haul air-mile radius, and whether the state simply adopts the federal rules unchanged (which is itself an answer worth stating). Federal 49 CFR 395 does not apply intrastate; states set their own, and they genuinely differ — Florida allows 12 driving hours in a 16-hour window against the federal 11-in-14 (Fla. Stat. 316.302), California allows 12 hours and an 80-in-8 cycle (13 CCR 1212). Answers 'how many hours can I drive if I never leave Texas', 'does the 14-hour rule apply intrastate in Florida', and the questions small intrastate carriers and their drivers ask without a compliance department to ask instead. No neutral cross-state compilation exists; the search results and page-one content contradict each other about Texas.
The data
| State | Max driving hours | On-duty window | Weekly/cycle limit | Statute or rule | Adopts federal rules |
|---|---|---|---|---|---|
| Federal | a total of 11 hours | after a period of 14 consecutive hours after coming on-duty following 10 consecutive hours off-duty | 60 hours in any period of 7 consecutive days if the employing motor carrier does not operate commercial motor vehicles every day of the week; or (2) Having been on duty 70 hours in any period of 8 consecutive days | 49 CFR 395.3 | |
| Florida | 12 hours following 10 consecutive hours off duty | after the end of the 16th hour after coming on duty following 10 consecutive hours off duty | 70 hours in any period of 7 consecutive days or more than 80 hours in any period of 8 consecutive days | F.S. 316.302 | no — intrastate drivers need not comply with 49 C.F.R. ss. 391.11(b)(1) and 395.3; Florida sets its own limits |
| Virginia | 19VAC30-20-80 | yes — incorporates the Federal Motor Carrier Safety Regulations (49 CFR Parts 390 through 397, including hours of service) by reference for both interstate and intrastate commerce, with certain exceptions |
Where this came from
Every record above links the page it was taken from and quotes the sentence that states it. These are the 3 sources this dataset was assembled from.
- ecfr.govhttps://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-A/section-395.3
- leg.state.fl.ushttp://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&URL=0300-0399/0316/Sections/0316.302.html
- law.lis.virginia.govhttps://law.lis.virginia.gov/admincode/title19/agency30/chapter20/section80/
Machine-readable
- data.jsonThe whole dataset — every record with its source URL and source quote.
- Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
- data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
- How this is made and checkedWhat "verified against source" does and does not mean.
From your own code
Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.
pip install refsource
refsource lookup intrastate-driver-hours-by-state state=Federal
npx -y refsource lookup intrastate-driver-hours-by-state state=FederalSet your AI assistant up to use this
Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.
{
"mcpServers": {
"referencesource": {
"type": "http",
"url": "https://referencesource.org/mcp"
}
}
}Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project
Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:
When a question needs "Intrastate truck driver hours-of-service rules by state — where they differ from federal", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `intrastate-driver-hours-by-state`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.What each tool does, and the servers built over single registers: Connect your AI assistant.