Attorney-built legal research

365 years of American case law. Essentially every published opinion.

$75 / month / seat

Search an essentially complete published record of federal and state courts, state codes, and regulations. Ask in plain English on the web, or plug the keys directly into Claude Code, Codex, and Antigravity.

Your seat includes unlimited research through your own API key and full portal access. Answers generated by our AI are billed per query, according to the AI resources actually used. Most queries run about a dollar. You see each query’s cost as you go, and can check your running spend anytime.

An Actual Query and Response
Scroll down for more ↓
Your research question

At 2:00am on a Friday morning, my client was driving along a narrow country road in Pocahontas County, West Virginia, when he blew a tire. Lacking a spare and feeling it was unsafe to change a tire on the pavement, he pulled over to the right as far as possible, but leaving his left wheels about 2 feet on the pavement. He set his 4-way flashers, called for a wrecker, and settled into the driver's seat to wait. Ten minutes later, another driver pulled up from behind and collided with his car, causing him serious injury, and severe damage to both vehicles. Later, police arrived and measured the other driver's BAL at 9.2 by breathalyzer. Neither driver was charged by the police. My client is suing for damages. Please research the applicable statutes and case law and advise me in preparing the suit.

Maverick research memo · grounded in retrieved statutes & cases

I'll research the West Virginia statutes and case law governing the key issues here: (1) the rules for stopping/parking a disabled vehicle on a roadway, (2) the drunk driver's liability and how his intoxication factors in, and (3) West Virginia's comparative fault regime, which will determine how any negligence by your client affects recovery.

Running additional targeted searches for West Virginia–specific case law, since the initial results are almost entirely out-of-state (persuasive only)…

I now have solid West Virginia authority on every issue. Here is my research memorandum.


Research Memorandum — Pocahontas County, WV Rear-End Collision (Disabled Vehicle / Intoxicated Following Driver)

A verification note before anything else: Everything below is grounded in the statutes and cases returned by my research library, with operative language quoted. But Maverick's library is a point-in-time snapshot and does not run a citator. Before you file or rely on any of this, please independently confirm each case is still good law (Shepardize/KeyCite) and check each statute against the current West Virginia Code, as several of these provisions have been amended over the years. You are responsible for verifying every quotation and holding against the source text, which I've linked.

One factual flag: you report the other driver's "BAL at 9.2 by breathalyzer." A 9.2% (0.092) reading is a plausible number that exceeds the 0.08 per se limit; "9.2" flat is not a possible BAC. I've assumed you mean roughly 0.092 (or that the true figure is in the record). Confirm the actual number, because—as the case law below shows—the degree of intoxication matters a great deal to the punitive-damages analysis.


I. Your client's stop: the parking statute and the "disabled vehicle" question

The controlling statute is W. Va. Code § 17C-13-1(a), which provides that "[u]pon any highway outside of a business or residence district no person shall stop, park, or leave standing any vehicle, whether attended or unattended, upon the paved or main-traveled part of the highway when it is practicable to stop, park, or so leave such vehicle off such part of said highway, but in every event an unobstructed width of the highway opposite a standing vehicle shall be left for the free passage" of other vehicles. W. Va. Code § 17C-13-1(a) (source: code.wvlegislature.gov/17C-13-1/).

Two features of this statute are favorable to your client:

  1. The prohibition is conditional, not absolute. It applies only "when it is practicable" to get the vehicle off the pavement. Your client blew a tire, had no spare, and (he says) it was unsafe to change it on the narrow pavement at 2:00 a.m. Whether it was "practicable" to move the car further off the road is the central factual issue.
  2. The narrow-road caveat matters. The statute's clear-width requirement, by its terms, protects "free passage" of oncoming traffic. On a narrow country road, whether the two feet of intrusion actually violated the statute at all is fact-dependent.

West Virginia treats a traffic-statute violation as prima facie evidence of negligence — not negligence per se — and leaves both the violation and causation to the jury. This is the single most important body of WV authority for you:

  • Spurlin v. Nardo, 145 W. Va. 408 (1960): "Violation of a statute … constitutes prima facie negligence, not negligence per se," and "[a] prima facie case of actionable negligence … must be submitted to a jury and not decided against the plaintiff as a matter of law." (source: app.mavericklegalresearch.com/case/1371718)
  • Anderson v. Moulder, 183 W. Va. 77 (1990): "Violation of a statute is prima facie evidence of negligence. In order to be actionable, such violation must be the proximate cause of the plaintiff's injury." (source: app.mavericklegalresearch.com/case/1218604)
  • Marcus v. Staubs, 229 W. Va. 305 (2012), reaffirming Simmons v. City of Bluefield, 159 W. Va. 451 (1975): "The determination as to whether there was in fact a statutory violation and whether the violation was the proximate cause of the injury is within the province of the jury." (source: app.mavericklegalresearch.com/case/8219325)

Practical consequence: Even if the defense argues your client technically violated § 17C-13-1, that is not automatically fault, and the jury decides (a) whether it was "practicable" to move the car and (b) whether any violation was a proximate cause. That framing is much better for a plaintiff than a negligence-per-se rule.

The "disabled vehicle" theme. West Virginia's § 17C-13-1 does not contain the express "disabled vehicle" exception that many other states' versions have, but the "practicable" language does similar work, and courts elsewhere construe "impossible/impracticable to move" to mean not reasonably practicable, treating it as a jury question. I did not find a West Virginia case squarely applying the disabled-vehicle concept to § 17C-13-1; the leading disabled-vehicle cases in the library are all from other states and are persuasive only (e.g., Schermer v. Muller (Iowa); Silvey v. Harm (Cal.); Rice v. Yellow Cab (Ohio)). Use these to illustrate the majority approach, but anchor your brief in the WV "practicable"/prima-facie-negligence line.

Warning-device / lighting statutes to check. Note two related provisions the defense may raise:

  • § 17C-15-40 requires certain large vehicles ("motor truck, passenger bus, truck tractor, trailer, semitrailer, or pole trailer") that are "disabled upon the traveled portion of any highway or the shoulder" to display warning devices. By its terms this does not apply to an ordinary passenger car, which helps your client. Confirm the vehicle type.
  • § 17C-15-15 governs lamps on parked/stopped vehicles. In Smith v. Penn Line Service, Inc., 145 W. Va. 1 (1960), the Court held that even where a parked vehicle violated a lighting statute, the violation "is not the proximate cause of a collision when the driver of the moving vehicle could have seen the parked vehicle in time to avoid the collision but failed to keep a proper lookout" — the following driver's negligence was "the sole proximate cause." (source: app.mavericklegalresearch.com/case/1331479) Your client's 4-way flashers cut strongly in his favor here.

II. The other driver's liability — the strongest part of your case

A. Ordinary negligence / following too closely

W. Va. Code § 17C-7-10(a): "The driver of a motor vehicle shall not follow another vehicle more closely than is reasonable and prudent having due regard for the speed of such vehicles and the traffic upon and the condition of the highway." (source: code.wvlegislature.gov/17C-7-10/) A driver who rear-ends a stopped, flasher-lit vehicle on an open road at 2:00 a.m. faces a strong negligence case, and the intoxication evidence makes it stronger.

B. Driving under the influence

W. Va. Code § 17C-5-2 makes it unlawful to drive with "an alcohol concentration in his or her blood of eight hundredths of one percent or more" (0.08). (source: code.wvlegislature.gov/17C-5-2/) A reading around 0.092 exceeds the per se threshold.

Admissibility of the BAC in the civil case is expressly authorized by statute. W. Va. Code § 17C-5-8(a) provides that "upon the trial of any civil or criminal action arising out of acts alleged to have been committed by any person driving a motor vehicle while under the influence of alcohol … evidence of the amount of alcohol in the person's blood at the time of the [arrest]" is admissible. (source: code.wvlegislature.gov/17C-5-8/) You will need to lay a proper foundation for the breathalyzer result.

The fact that neither driver was charged is largely irrelevant to civil liability. The civil standard is preponderance, and the DUI statute violation is prima facie evidence of negligence under the Spurlin/Anderson line above.

C. Joint and several liability is preserved for the drunk driver

This is important and favorable. West Virginia's modern several-liability statute generally abolishes joint liability, but expressly carves out drunk drivers. W. Va. Code § 55-7-13C provides that "the liability of each defendant for compensatory damages shall be several only and may not be joint," except that "a defendant whose conduct constitutes driving a vehicle under the influence of alcohol, a controlled substance, or any other drug … which is a proximate cause of the [injury]" shall be jointly and severally liable. (source: code.wvlegislature.gov/55-7-13C/) If there are ever other defendants, the intoxicated driver can be held fully liable.


III. Punitive damages — plausible, but the degree of intoxication controls

A. The statutory standard

W. Va. Code § 55-7-29(a): punitive damages require proof "by clear and convincing evidence that the damages suffered were the result of the conduct that was carried out by the defendant with actual malice toward the plaintiff or a conscious, reckless and outrageous indifference to the health, safety and welfare of others." (source: code.wvlegislature.gov/55-7-29/) This is a demanding, clear-and-convincing standard, and there are statutory caps/ratios in § 55-7-29 you should read in full.

B. West Virginia case law on punitive damages in drunk-driving cases

The on-point WV authority is Smith v. Perry, 178 W. Va. 395 (1987), an automobile-accident case where "the trial court … set aside the jury's award of punitive damages" and the appeal turned on "sufficient[]" evidence. (source: app.mavericklegalresearch.com/case/1257484) Pull and read this case carefully — it is your closest WV factual analog on whether intoxication supports punitive damages. For the punitive-damages framework generally, see Vandevender v. Sheetz, Inc., 200 W. Va. 591 (1997) (source: app.mavericklegalresearch.com/case/1330468), and Stevenson v. Independence Coal Co., 227 W. Va. 388 (2011) (source: app.mavericklegalresearch.com/case/2502946).

C. The out-of-state split (persuasive only) — why the BAC number matters

The cases divide on whether intoxication alone supports punitives, and they show why you should nail down the exact BAC and any aggravating conduct (speeding, erratic driving, prior DUIs):

  • Intoxication may suffice / sliding scale: Nast v. Lockett (Md.) — "a high degree of impairment (intoxication) may alone be sufficient … a lower degree … requires more extraordinary or outrageous conduct" (source: app.mavericklegalresearch.com/case/2381849); Taylor v. Superior Court (Cal.); Ingram v. Pettit (Fla.).
  • Intoxication alone is NOT enough — need aggravating conduct: Wohlwend v. Edwards (Ind.) — "[d]riving while intoxicated is not per se willful and wanton misconduct" (source: app.mavericklegalresearch.com/case/2150718); Komornik v. Sparks (Md.).

These are not binding in West Virginia. Given § 55-7-29's "clear and convincing / conscious, reckless and outrageous indifference" language, plead punitive damages, but marshal aggravating facts beyond the bare BAC (speed, no braking/skid marks, lane position, prior offenses, post-crash conduct) to meet the WV standard.


IV. The comparative-fault defense — the pivotal battleground for your client

Expect the defense to argue your client's stop was itself negligent. Two regimes to be aware of, and you must determine which applies based on the date of your accident:

  1. Statutory modified comparative fault (current law). W. Va. Code § 55-7-13A et seq. establishes "modified comparative fault," and § 55-7-13C(c) and § 55-7-13D govern allocation. Recovery is barred only if the plaintiff's fault exceeds a statutory threshold; read § 55-7-13D(b) for the exact bar. These provisions were enacted in 2015 — confirm the accident post-dates the effective date.
  2. The prior common-law rule from Bradley v. Appalachian Power Co., 163 W. Va. 332 (1979): "A party is not barred from recovering damages in a tort action so long as his negligence or fault does not equal or exceed the combined negligence or fault of the other parties involved in the accident." (source: app.mavericklegalresearch.com/case/1397438) If the accident predates the statute, Bradley controls.

Either way, your client can be less than 50% at fault and still recover (reduced by his percentage). Given a stopped car with flashers vs. a drunk driver who never braked, keeping the client's share low is very achievable.

Two doctrines that help defeat or minimize the comparative-fault defense:

  • Sudden emergency (as a comparative-fault factor). Moran v. Atha Trucking, Inc., 208 W. Va. 379 (2001): "The sudden emergency doctrine remains viable under West Virginia's comparative negligence scheme," operating as "one factor in the total comparative fault analysis." (source: app.mavericklegalresearch.com/case/1315846) The blowout was arguably a sudden emergency not of your client's making.
  • Intervening cause / sole proximate cause. Your best causation theme: the drunk driver's failure to keep a lookout and stop was the superseding cause. Smith v. Penn Line Service (above) is directly supportive. But note Evans v. Farmer, 148 W. Va. 142 (1963): where original negligence "sets in motion a chain of events … the intervening act does not become the sole proximate cause as a matter of law" — meaning proximate cause is generally a jury question (source: app.mavericklegalresearch.com/case/1339059). That cuts both ways but keeps your case out of summary judgment.
  • Last clear chance is abolished under comparative negligence — do not plead it. Ratlief v. Yokum, 167 W. Va. 779 (1981) (source: app.mavericklegalresearch.com/case/1314807).

V. Recommendations for the complaint

  1. Plead ordinary negligence against the other driver (breach of § 17C-7-10 following-too-closely; § 17C-5-2 DUI; general duty of due care), framing each statutory violation as prima facie negligence under Spurlin/Anderson.
  2. Plead punitive damages under § 55-7-29, but plead specific aggravating facts (BAC level, absence of braking, speed, any prior DUIs) — read Smith v. Perry first to calibrate.
  3. Anticipate and neutralize the comparative-fault defense with (a) the "practicable" conditional language of § 17C-13-1, (b) the sudden-emergency factor (Moran), (c) the flashers/lookout/sole-proximate-cause theme (Smith v. Penn Line), and (d) the fact that § 17C-15-40's warning-device duty targets large commercial vehicles, not a passenger car.
  4. Nail down the facts early: exact BAC and the breath-test foundation (§ 17C-5-8); the road's actual traveled width and whether "free passage" was in fact obstructed; the vehicle type; skid/lookout evidence; the other driver's speed and history.
  5. Confirm the currency of everything. Verify § 55-7-13A–13D's effective date against your accident date; confirm § 17C-13-1, § 17C-5-2, § 17C-5-8, § 17C-15-40, and § 55-7-29 against the current Code; and run every case (Spurlin, Anderson, Marcus v. Staubs, Smith v. Penn Line, Moran, Evans v. Farmer, Smith v. Perry, Bradley) through a citator to confirm each remains good law.

I'm a research assistant, not a substitute for your own judgment, and this is not legal advice to a client — it's a research memo for you to review and verify. I was unable to find a West Virginia case applying the "disabled vehicle" concept directly to § 17C-13-1; if that becomes central, the disabled-vehicle authority you'll be relying on is out-of-state and persuasive only, so you may want to run additional targeted research. Want me to dig deeper on any single issue — for example, pull the full text of Smith v. Perry on punitive damages, or search specifically for WV decisions on the § 17C-13-1 "practicable" standard?

Generated by Maverick Legal Research · AI-assisted research — review and verify every citation against the cited source text before filing or relying on it.

Work sample only — not for legal use. Verify all authority independently.
9.9M+ opinions across federal and state courts
50 states state statutory coverage and jurisdiction filters
USC + CFR federal statutes and regulations
API-first built for agents, workbenches, and firm tools

The problem

A made-up citation is not a harmless bug.

A general model can produce a clean-looking citation that does not exist or misstated authority that would never survive a filing. Maverick sits between the agent and the draft, so research starts with verified sources instead of confidence.

Agent alone

Confident text, thin source trail.

Smith v. ABC Bank, 2021 WL 000000. Looks useful. May not exist.

Agent + Maverick

Real authority the lawyer can inspect.

Statutes, cases, jurisdiction, source text, and citation metadata returned together.

We don’t blame the models. A general AI will confidently invent a citation — because guessing is the only thing it can do without the actual law in front of it. So we put the law in the path. Every Maverick answer runs through the real corpus — cases, statutes, regulations, source text — not a model’s memory. The research sees what a lawyer sees: the holding, the statute, the jurisdiction, the citation trail — and answers from it, with links back to the source. The result: a first-pass research memo, grounded in authority you can open and read, in the time it takes to get a cup of coffee.

Research coverage

Cases, statutes, and source text for litigation work.

Maverick is not limited to one side of the bar or one practice area. The early corpus is broad, with deeper tuning where active litigation work demands state-specific answers.

Cases

Federal and state opinions through a CourtListener/Free Law Project based corpus, ranked for issue fit, jurisdiction, and litigation relevance.

  • Criminal defense, DUI, sentencing, and post-conviction
  • Family and domestic — divorce, custody, support, protective orders
  • Personal injury, auto and other torts, negligence, premises liability
  • Real property, landlord-tenant, title, and boundary disputes
  • Contracts, collections, consumer protection, and small-business disputes
  • Estates and probate, bankruptcy, employment, and civil appeals

Legal Structure

Attorney-built data layers organize sources around how litigators reason: claims, defenses, exceptions, remedies, analogs, and controlling authority.

  • ABA Model Rules plus 50 states and DC professional-conduct rules
  • Cross-jurisdictional analog mapping
  • Freshness and source checks for statutory updates

Web Research Portal

An affordable AI search portal. Built for lawyers.

For quick lookups or lawyers who prefer a visual interface, Maverick includes a complete browser-based web portal. Ask questions in plain English, browse statutory codes, and click through to read full cases and statutes.

Search & Click-Through Reader

Ask legal questions in plain English. Get highly relevant, ranked results, and click through to read the full text of cases, federal statutes, or state codes in a clean, distraction-free browser view.

Read the Primary Source

Open the full text of any case or statute in a clean reader and verify the law yourself. Maverick is a research tool, not a citator — always confirm a case is still good law with a standard citator before you rely on it.

API access

Add legal authority to the tools your firm already uses.

Maverick is designed as infrastructure. A firm can use it through a web interface later, but the core product is API-based: one research layer for agent workflows, workbench features, and internal tools.

REST research endpoint

GET /v1/research?q=RESPA+QWR+response+duties&jurisdiction=NC
Authorization: Bearer MAVERICK_API_KEY

Claude Code

Add Maverick as an MCP server — sign in once from your dashboard’s Connect page.

claude mcp add --transport http maverick \
  https://api.mavericklegalresearch.com/mcp

Codex

Project-level MCP access for research-backed code and drafting workflows.

codex mcp add maverick \
  --url https://api.mavericklegalresearch.com/mcp

Antigravity

External API tool configuration for agentic legal workflows.

Name: Maverick Legal Research
Auth: Bearer MAVERICK_API_KEY
Tools: research, resolve, fetch

Example setup only. We email you a secure sign-in link when you start a trial or subscribe; reveal your API key from your dashboard (shown once).

The alternative

Built to break the lock-in.

The research giants trap solo and small firms in multi-year contracts, bloated suites, and pricing you can’t predict. Maverick is the opposite.

Legacy research giants

  • Multi-year, lock-in contracts
  • Bloated, confusing suites
  • Hidden, per-search pricing
  • Their platform, their walls

Maverick

  • Month-to-month — $75/seat, cancel anytime
  • Lean and fast — ask in plain English
  • One transparent price; AI metered and billed on actual usage
  • API-first — plug into the tools you already use

Pricing

One unified plan. Full research access.

Access the entire Maverick research library — cases, statutes, regulations, and inspectable source text. Work however you prefer: use our browser-based web portal, plug the API keys into your own AI agents, or do both.

Maverick Research Plan

$75 / seat / month

or $825 / seat / year — one month free

  • Comprehensive Library: 9.9M+ opinions, USC + CFR, and all 50 states' statutory codes.
  • Web Research Portal: Ask in plain English — pay only for the AI you use (see below).
  • API Access: Connect Claude Code, Codex, Antigravity, and custom agents over MCP or REST.
  • Inspectable Source Text: Read the full opinion or statute yourself, then verify current validity with your citator.

About the AI in the Web Portal. Research through your own API key is fully included — you bring, and pay for, your own AI provider. Answers generated in the hosted Web Portal are billed as you use them: each query’s cost depends on its complexity and the AI tokens it takes, you see each query’s cost as you go, and can check your running spend at any time — so you decide exactly how much, or how little, to spend. In our experience the average query runs about a dollar, but your mileage may vary; use the free trial to gauge your own usage.

Not a citator. Maverick’s library is a point-in-time snapshot. It does not confirm that a case is still good law or that a statute is current. Always verify current validity with a standard citator, and check statutes against the current code, before relying on any result.

Free Trial

Try it on a real research question.

Five days, 50 queries, full research access, no credit card required. You get access to the web portal, and an API key and a two-minute setup guide for the tools you already use — if Maverick doesn't change how your next brief comes together, walk away and we never bill you.

Skip the trial and sign up now

Five days, 50 queries, no card. Both the web portal and API keys are included in the single $75 plan — you can switch how you work anytime from your account.