Product Liability Expert Witness Impeachment: 510(k), PMA, MAUDE & Bradford Hill Attacks

Product liability cases — especially pharmaceutical and medical device cases — live or die on expert testimony. Whether you're in a single-plaintiff state court case or a bellwether trial inside a federal MDL, the defense's strategy is almost always to weaponize FDA clearance, minimize adverse event data, and attack plaintiff causation experts under Daubert. Your job is to do the same — impeach the defense experts on regulatory sophistry, feasible alternative design, and Bradford Hill application.

This guide covers the three types of product defect, the regulatory vocabulary you need to master, and 25 specific impeachment questions keyed to the most common defense expert positions.

The three types of product defect

Under the Restatement (Third) of Torts: Products Liability § 2, a product can be defective in three ways. Your expert strategy depends on which type you're pursuing.

Design defect

The product's design itself is unreasonably dangerous, even when manufactured as intended. Most jurisdictions apply either a risk-utility test or a consumer expectations test — often both. The plaintiff must typically prove a feasible alternative design existed at the time of manufacture that would have reduced or eliminated the risk without impairing utility. This is where your design engineer or biomedical engineer expert lives. Classic examples: unstable SUVs, surgical mesh with inadequate fixation points, Essure nickel-containing implants.

Manufacturing defect

The product deviated from its intended design. This is the easiest defect to prove — you compare the exemplar (a properly manufactured unit) to the subject product and show the deviation. Examples: a weld that failed, a batch with excess contamination, a drug vial that contained the wrong dosage. Manufacturing defects usually require a metallurgist, polymer scientist, or analytical chemist.

Warning defect (failure to warn)

The product carried inadequate warnings about a known or knowable risk. This is where the learned intermediary doctrine becomes critical in pharmaceutical cases — most jurisdictions hold that the manufacturer's duty runs to the prescribing physician, not the patient. Warning defect cases turn on what the manufacturer knew, when they knew it, and whether the label, Dear Doctor letter, or REMS program adequately communicated the risk.

Bellwether and MDL dynamics

If your case is part of a multidistrict litigation (MDL) and selected for bellwether trial, the impeachment stakes are enormous. A strong bellwether verdict drives settlement values across the entire MDL. Defense experts in bellwether cases are heavily prepared — often deposed dozens of times previously — and their prior testimony is your most productive impeachment source.

Before any bellwether expert deposition, obtain:

• Every prior deposition transcript in the MDL (from other bellwether cases)
• The expert's reports in each prior MDL case
• Any Daubert rulings — granted or denied — on this expert in other jurisdictions
• The expert's CV, publication list, and prior testimony list (Rule 26(a)(2)(B)(v) list)
• The expert's grant funding history and any industry consulting payments (Open Payments database for physician experts)

Cross-jurisdictional inconsistency is gold. If the same defense expert said "the epidemiologic signal is weak" in one MDL case and "the data show no association" in another — that's an impeachment moment you need ready.

The regulatory vocabulary: 510(k), PMA, MDR, MAUDE

Defense experts routinely invoke FDA clearance as if it precludes liability. It doesn't, but you need to understand the distinctions to impeach them.

510(k) clearance

A 510(k) pre-market notification is a clearance pathway for Class II devices that are "substantially equivalent" to an already-marketed predicate device. It is not a finding of safety or efficacy. The Supreme Court explicitly said so in Medtronic, Inc. v. Lohr, 518 U.S. 470 (1996). When a defense expert treats 510(k) clearance as evidence of safety, you impeach with Lohr.

PMA (Pre-Market Approval)

PMA is the rigorous approval pathway for Class III devices. Under Riegel v. Medtronic, Inc., 552 U.S. 312 (2008), state tort claims are expressly preempted for PMA-approved devices to the extent they impose requirements different from or in addition to federal ones. Parallel claims — where the state law duty is identical to an FDA requirement — survive preemption. Your impeachment here is against the expert who overstates Riegel preemption.

MDR (Medical Device Reports) and MAUDE

Medical Device Reports are the mandatory adverse event reports manufacturers file with FDA. They populate the MAUDE database (Manufacturer and User Facility Device Experience). Plaintiffs frequently pull MAUDE data showing the manufacturer knew of recurring adverse events well before the subject plaintiff was injured. Defense experts will try to minimize MAUDE as "unverified" — but they cannot escape the fact that the manufacturer's own reports show a signal.

Open Payments / Sunshine Act

Every physician expert who accepts manufacturer payments is reported in the CMS Open Payments database. Before deposing any physician expert in a pharmaceutical or device case, pull their Open Payments record. Defense experts are often receiving substantial consulting or speaking fees from the defendant manufacturer — or from competitors with aligned interests.

25 impeachment questions for product liability experts

Regulatory and FDA positioning

1. You testified that the device was FDA-cleared — is that through the 510(k) pathway or the PMA pathway?
2. Are you aware that under Medtronic v. Lohr, 510(k) clearance is not a finding of safety?
3. 510(k) clearance requires demonstration of substantial equivalence to a predicate device. What was the predicate in this case?
4. Has the predicate device itself been the subject of Class I or Class II recalls?
5. Are you aware of the FDA's 2011 Institute of Medicine report recommending reform of the 510(k) process?
6. In the MAUDE database, how many adverse event reports involving this device have been filed since market entry?
7. Did the manufacturer's internal complaint handling database show adverse events the manufacturer did not report to FDA?
8. Have you reviewed all MDRs filed for this device, or only those provided to you by defense counsel?

Design, alternative design, and state-of-the-art defense

9. You testified the product met the state of the art — which publications or engineering standards define "state of the art" in this context?
10. ISO or ASTM standards governing this device — are they mandatory or voluntary?
11. When was the last time those standards were updated, and has the manufacturer's design kept pace with them?
12. Was a feasible alternative design available at the time of manufacture that would have reduced the risk?
13. Are you aware of competitor products on the market at the time with different design features that addressed this risk?
14. Did the manufacturer's own internal R&D documents evaluate alternative designs and reject them?
15. On what basis were those alternatives rejected — cost, feasibility, or otherwise?

Warning adequacy and learned intermediary

16. You've testified the product warning was adequate — what is the FDA's standard for warning adequacy?
17. Does the warning disclose the risk at issue here specifically?
18. When the manufacturer became aware of this risk through post-market surveillance, how soon was the label updated?
19. Was a Dear Doctor letter or safety communication issued to prescribers at that time?
20. Does the REMS program address this specific risk?

Causation: Bradford Hill and differential etiology

21. You dispute general causation — did you apply the Bradford Hill criteria in your analysis?
22. Which Bradford Hill factors did you evaluate: strength of association, consistency, specificity, temporality, biological gradient, plausibility, coherence, experiment, analogy?
23. Temporality — the exposure preceded the injury. You don't dispute that, correct?
24. Dose-response — are you aware of peer-reviewed studies showing a dose-response relationship between this exposure and the outcome?
25. In your differential etiology, which alternative causes did you consider and rule in or rule out, and by what methodology?

The pharmaceutical Daubert angle

Pharmaceutical cases are where Daubert attacks on causation experts are most intense. Defense routinely moves to exclude plaintiff epidemiologists, toxicologists, and treating physicians on causation. Your counter-strategy:

• Ground causation in Bradford Hill. Courts have repeatedly held Bradford Hill is a scientifically accepted framework. Make your expert walk through each factor.
• Build general causation before specific. General = can this substance cause this disease? Specific = did it cause it in this plaintiff? These are separate analyses and must be treated as such in the expert report.
• Use FDA label changes as admissions. When the manufacturer adds a warning post-market, that's often admissible as notice and causation evidence.
• Attack defense experts on selective study inclusion. If the defense epidemiologist relied on three industry-funded studies and ignored seven independent studies, that's a Rule 702(b) "sufficient facts" attack.
• Pull Open Payments data for every physician defense expert. Consulting relationships with the defendant or with competitors matter for bias.

How Courtroom AI catches product liability impeachment moments live

Product liability depositions run long — often full-day or multi-day — and the defense expert has been coached to fluidly use regulatory terminology, study citations, and causal framings without explicit commitments. Our product_liability specialty keyword pack, rolled out this month, recognizes the domain vocabulary and flags:

• 510(k) vs PMA confusion. When an expert implies 510(k) equates to safety approval, the AI flags for impeachment with Lohr.
• MAUDE and MDR under-reporting inconsistencies. When the expert claims no safety signal but MAUDE data you've uploaded shows a cluster.
• Bradford Hill selective application. When the expert cites some Bradford Hill factors for absence of causation but ignores the ones that cut the other way.
• Feasible alternative design evasion. "There was no alternative" answered inconsistently with competitor product information already of record.
• Differential etiology gaps. When the expert fails to address a known alternative cause.
• Industry funding disclosure. Cross-checks against Open Payments data when the expert minimizes manufacturer relationships.

The goal is to ensure that sophisticated regulatory and causal language doesn't slip by unchallenged because the attorney was formulating the next line of questioning.

Common mistakes in product liability expert depositions

• Treating FDA clearance as if it ends the analysis. It doesn't — 510(k) especially is not a safety finding.
• Not pulling Open Payments data. Every physician expert in a drug or device case must have their disclosures checked.
• Letting the expert decline to opine on specific causation. A defense expert who won't commit to a causation opinion can't later defeat your general causation case without methodological reciprocity.
• Missing the internal company documents. Design history files, complaint handling records, and internal safety meeting minutes are usually the most devastating impeachment material.
• Not coordinating with MDL co-counsel. Cross-case impeachment only works if you share transcripts and findings across the plaintiff steering committee.

Related reading

• How to Daubert Challenge an Expert Witness in 2026
• Birth Injury OB/GYN Deposition Checklist
• Nursing Home Neglect Deposition Questions
• How AI Analyzes a Two-Hour Deposition in Real Time