Reference Source

Vehicle Lemon Law Eligibility Thresholds by State

State lemon law eligibility thresholds for new motor vehicles in each US state and DC: the time window, mileage limit, number of repair attempts required, and cumulative out-of-service days that trigger the presumption, with the controlling statute cited.

Records37
Sources37
Verified
Review by
Licencepublic-domain-facts

The data

statetime limitmileage limitrepair attemptsout of service daysstatute citation
Arizonatwo yearstwenty-four thousand milesfour or more timesthirty or more calendar daysAriz. Rev. Stat. § 44-1264
California18 months18,000 milesfour or more timesmore than 30 calendar daysCal. Civ. Code § 1793.22
Coloradoone yearfour or more timesthirty or more business daysColo. Rev. Stat. § 42-10-103
Connecticuttwo yearstwenty-four thousand milesfour or more timesthirty or more calendar daysConn. Gen. Stat. § 42-179
Delaware1 year4 or more timesmore than 30 calendar days6 Del. C. § 5004
District of Columbia2 years18,000 miles4 or more times30 days or moreD.C. Code § 50-502
Floridaat least three times30 or more daysFla. Stat. § 681.104
Hawaiiat least three timesthirty or more business daysHaw. Rev. Stat. § 481I-3
Idahotwo (2) yearstwenty-four thousand (24,000) milesfour (4) or more timesthirty (30) or more business daysIdaho Code § 48-903
Illinoisone year12,000 miles4 or more times30 or more business days815 ILCS 380/2(f), 380/3(b)
Iowatwo yearstwenty-four thousand milesIowa Code § 322G.2
Kansasone yearfour or more times30 or more calendar daysKan. Stat. Ann. § 50-645
Maine3 years18,000 miles3 or more times15 or more business daysMe. Rev. Stat. tit. 10, § 1163
Maryland4 or more times30 or more daysMd. Code, Com. Law § 14-1502
Massachusettsone yearfifteen thousand milesthree or more timesfifteen or more business daysMass. Gen. Laws ch. 90, § 7N1/2
Michigan4 or more times30 or more daysMich. Comp. Laws § 257.1403
Minnesotatwo yearsfour or more times30 or more business daysMinn. Stat. § 325F.665
Missourione yearfour or more timesthirty or more working daysMo. Rev. Stat. § 407.571
Nebraskaone yearfour or more timesforty or more daysNeb. Rev. Stat. § 60-2704
Nevada1 yearfour or more times30 or more calendar daysNev. Rev. Stat. § 597.630
New Hampshireat least 3 times30 or more business daysN.H. Rev. Stat. Ann. § 357-D:3
New Yorktwo yearseighteen thousand milesfour or more timesthirty or more calendar daysN.Y. Gen. Bus. Law § 198-a
North Carolinafour or more times20 or more business daysN.C. Gen. Stat. § 20-351.5
North Dakotaone yearmore than three timesat least thirty business daysN.D. Cent. Code § 51-07-19
Ohioone yeareighteen thousand milesthree or more timesthirty or more calendar daysOhio Rev. Code § 1345.73
Oklahomaone (1) yearfour or more timesthirty (30) business daysOkla. Stat. tit. 15, § 901
Oregontwo-year period24,000 milesthree or more times30 or more calendar daysOr. Rev. Stat. § 646A.406
Pennsylvaniathree times30 or more calendar days73 P.S. § 1958
Rhode Islandfour (4) or more timesthirty (30) or more calendar daysR.I. Gen. Laws § 31-5.2-5
South Carolinathree or more timesthirty or more calendar daysS.C. Code Ann. § 56-28-50
Texas24 months24,000 milesfour or more times30 or more daysTex. Occ. Code § 2301.605(a)
Utahone-year periodfour or more times30 or more business daysUtah Code § 13-20-5
Vermontat least three times30 or more calendar days9 V.S.A. § 4172
Virginiathree or more times30 calendar daysVa. Code § 59.1-207.13
Washingtontwo yearstwenty-four thousand milesWash. Rev. Code § 19.118.021
West Virginiaone yearthree or more timesthirty or more calendar daysW. Va. Code § 46A-6A-5
Wisconsinone yearat least 4 timesat least 30 daysWis. Stat. § 218.0171(1)(h)

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 37 sources this dataset was assembled from.

Machine-readable

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 vehicle-lemon-law-thresholds-by-state state=Arizona

npx -y refsource lookup vehicle-lemon-law-thresholds-by-state state=Arizona

Set 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 "Vehicle Lemon Law Eligibility Thresholds by State", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `vehicle-lemon-law-thresholds-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.

37 records. last verified against source . due for re-check by .

Licence. public-domain-facts