Common Logical Flaws & Fallacies
1. What You Need to Know
Logical flaws (aka fallacies) are predictable ways arguments go wrong. On the LSAT, you’ll see them most in Logical Reasoning (Flaw, Weaken, Strengthen, Necessary Assumption, Sufficient Assumption, Parallel Flaw), and sometimes in Reading Comp when evaluating an author’s reasoning.
Core idea
An argument is flawed when its premises don’t justify the conclusion. Your job is to spot the gap and describe it in a way that matches an answer choice.
Why this matters
- Flaw/Parallel Flaw questions directly test your ability to name the error.
- Weaken/Strengthen questions are easier if you can predict the exact vulnerability.
- Assumption questions often hinge on a hidden but necessary link (many flaws are “missing assumption” patterns).
Two big LSAT realities
- Don’t obsess over formal names. Knowing names helps, but the LSAT rewards recognizing the pattern.
- Most wrong answers are “nearby.” They describe a different (but tempting) flaw, or they’re too extreme/too mild.
Critical reminder: Most LSAT flaw answers are descriptions, not diagnoses with fancy labels. Translate the argument into: “They conclude because , but that assumes .”
2. Step-by-Step Breakdown
Use this whenever you’re asked to find a flaw, parallel flaw, weaken/strengthen, or assumption.
Step-by-step method (the “Gap Hunt”)
Identify the conclusion
- Look for indicator words: therefore, thus, hence, so, clearly.
- Or ask: “What is the author trying to prove?”
List the premises (support)
- Evidence, facts, statistics, studies, examples.
Pre-phrase the gap
- Ask: “What would have to be true for the premises to guarantee this conclusion?”
- Common gaps: causation, representativeness, comparison standard, necessary vs sufficient, alternative explanations.
Classify the flaw pattern (fast sorting)
- Causal? Conditional? Sampling? Comparison? Definition shift? Attack/appeal?
Match to answer choices by specificity
- The right answer describes the flaw at the right level:
- Not too abstract (“it’s flawed”) and not too specific (“it ignores that the mayor is left-handed”).
- The right answer describes the flaw at the right level:
For Weaken/Strengthen: target the vulnerability
- If causal: weaken with alternative cause, reverse causation, or cause without effect / effect without cause.
- If sampling: weaken with bias or small sample; strengthen with random/large/representative.
Micro-examples (quickly)
- Causal gap: “After , happened; therefore caused .”
- Gap: assumes no other cause, not coincidence, not reverse.
- Conditional gap: “Only if then ; , so .”
- Gap: affirms the consequent (mixing up necessary/sufficient).
3. Key Formulas, Rules & Facts
A high-yield fallacy table (what it is | how it shows up | what to attack)
| Flaw / Fallacy Pattern | What it means (LSAT-usable wording) | Common LSAT tells | Best weaken/strengthen moves |
|---|---|---|---|
| Correlation causation | Treats a correlation as proof one thing caused the other | “associated with,” “linked to,” “goes with” | Weaken: alternative cause, reverse causation, coincidence; Strengthen: mechanism, controlled comparison |
| Post hoc (after this, therefore because of this) | Because followed , caused | “after,” “since then,” “following” | Same as causal + show occurs without |
| Necessary vs sufficient confusion | Treats a necessary condition as sufficient or vice versa | “only if,” “requires,” “guarantees,” “unless” | Translate to conditionals; test contrapositive; find invalid inference |
| Affirming the consequent | If ; ; therefore | “must have,” “therefore it was ” | Weaken: show another cause of ; Strengthen: eliminate alternatives |
| Denying the antecedent | If ; not ; therefore not | “since not , not ” | Weaken: show can happen without |
| Equivocation (shifting meaning) | Uses a key term in two different senses | same word appears, meaning subtly changes | Define terms; show ambiguity; clarify which meaning matters |
| Scope shift | Conclusion is broader/narrower than support | Premise: “some/many”; conclusion: “all/none” | Match quantifiers; weaken with counterexample; strengthen with broader evidence |
| Sampling bias / unrepresentative sample | Generalizes from a biased or tiny sample | “surveyed our website visitors,” “in one town” | Weaken: show sample not representative; Strengthen: random, large, diverse |
| Hasty generalization | Generalizes too much from too few cases | “in the few cases,” “one study,” “a handful” | Weaken: add contrary cases; Strengthen: replication, size |
| Composition | What’s true of parts is assumed true of the whole | “each player is great, so the team is great” | Show interactions/coordination matter |
| Division | What’s true of whole is assumed true of each part | “the company is profitable, so each division is profitable” | Show uneven distribution |
| False dilemma | Treats only two options as exhaustive | “either…or…,” “the only way” | Introduce third option/middle ground |
| Straw man | Misrepresents an opponent’s view then attacks that weaker version | “they want to ban all…,” “so they think…” | Point out distortion; restate original claim |
| Ad hominem | Attacks the person instead of the argument | “she’s biased,” “he’s immoral” | Show claim can be true regardless of person |
| Appeal to authority (weak authority) | Treats a non-expert/irrelevant authority as decisive | celebrity endorsement; unrelated expertise | Ask: is the authority qualified? is there consensus? |
| Circular reasoning | Conclusion is assumed in the premises | “ is true because ” | Identify restatement; no independent support |
| Confuses absence of evidence with evidence of absence | No proof of ⇒ is false (or vice versa) | “no one has shown,” “there’s no evidence” | Show lack of study/testing; hidden info possible |
| Percent vs number (base rate neglect) | Uses percentages without totals, or totals without population | “increased ” without base | Provide base rates/denominators |
| Bad comparison / apples-to-oranges | Compares things that differ in relevant ways | “better than,” “more effective,” no baseline | Demand common standard; control variables |
| Relative vs absolute confusion | “More” is treated like “enough” or “safe” | “reduced risk” ⇒ “safe” | Ask: compared to what? still too high? |
| Temporal shift | Uses past trend to predict future despite changed conditions | “has always,” “historically” | Show conditions changed; trend reversal |
| Policy flaw: ignores feasibility / side effects | Recommends a policy without showing it will work or is best | “we should,” “must implement” | Ask: will it achieve goal? costs? alternatives? unintended effects? |
Conditional language quick rules (high yield)
- “Only if” introduces a necessary condition: “ only if ” means .
- “If” introduces a sufficient condition: “If , then ” means .
- “Unless” often sets up: “ unless ” ≈ “If not , then ” (and also ).
Warning: Many “flaw” questions are just invalid conditional inferences dressed up in English.
4. Examples & Applications
Example 1: Causation (classic)
Stimulus (simplified): In cities that added more bike lanes, traffic accidents decreased. Therefore, adding bike lanes reduces traffic accidents.
Key insight: The evidence is a correlation. The argument assumes no alternative explanation.
- Weaken: Maybe those cities also increased traffic enforcement at the same time.
- Strengthen: Accident rates decreased more in cities with bike lanes than in otherwise similar cities without them (controlled comparison).
Example 2: Necessary vs sufficient (conditional trap)
Stimulus: To get certified, a mechanic must complete training. Alex completed training, so Alex is certified.
Key insight: “Must” signals necessary: certified trained. The argument does: trained certified (invalid).
- Flaw description: treats a necessary condition as sufficient / affirms the consequent structure.
- Weaken: Some trainees fail the certification exam.
Example 3: Sampling / survey
Stimulus: A poll of readers of a fitness magazine found support the new city gym tax. Therefore, most city residents support the tax.
Key insight: Sample is likely biased (fitness-mag readers aren’t representative).
- Weaken: Fitness magazine readers are more likely to use gyms than the average resident.
- Strengthen: The poll used a random sample of city residents with a large sample size.
Example 4: Equivocation / shifting definition
Stimulus: A “natural” product is better for you. This supplement is natural. So it’s better for you.
Key insight: “Natural” is vague; it can mean “found in nature,” “minimally processed,” or just marketing. Even if “natural,” it doesn’t follow it’s “better for you.”
- Flaw description: uses an ambiguous term without fixing a consistent meaning.
5. Common Mistakes & Traps
Mistake: Hunting for a fancy fallacy name
- What goes wrong: You spend time labeling (“is this ad populum or bandwagon?”) instead of matching the described gap.
- Why it’s wrong: LSAT answers rarely require the name; they require the functional description.
- Fix: Phrase it as: “assumes ” / “fails to rule out ” / “confuses with .”
Mistake: Missing the conclusion, then mis-describing the flaw
- What goes wrong: You think a premise is the conclusion.
- Why it’s wrong: Flaws are defined by the premise-to-conclusion leap.
- Fix: Always point to the “therefore” claim first; if no indicator, ask what the author is trying to prove.
Mistake: Treating “causal” as one single flaw
- What goes wrong: You pick any causal-sounding answer.
- Why it’s wrong: Causal flaws split into alternative cause, reverse causation, third variable, mere timing, selection effects, etc.
- Fix: Identify which causal assumption is doing the work in that stimulus.
Mistake: Conditional translation errors (“only if” and “unless”)
- What goes wrong: You flip necessary/sufficient and then think the argument is valid/invalid for the wrong reason.
- Why it’s wrong: Many “flaws” are just mistranslated conditionals.
- Fix: Translate carefully; then check whether the argument uses a valid form (modus ponens / modus tollens) or an invalid one.
Mistake: Confusing a missing premise with a flaw that’s not actually present
- What goes wrong: You assume the argument “generalizes,” but it’s actually making a narrow claim; or you assume “sampling” when there’s no sample.
- Why it’s wrong: Wrong answers often describe a plausible flaw not in the stimulus.
- Fix: Tie your flaw to specific language in the argument (quantifiers, comparisons, timing, definitions).
Mistake: Falling for extreme wording in answer choices
- What goes wrong: You pick an answer saying the argument “proves nothing” or “completely ignores all possibilities.”
- Why it’s wrong: LSAT flaws are often limited, not absolute.
- Fix: Prefer answers that match the stimulus’s level: “fails to consider the possibility…” beats “fails to consider any possibility…” unless truly warranted.
Mistake: Mixing up “attack the person” vs “source bias matters”
- What goes wrong: You label any mention of bias as ad hominem.
- Why it’s wrong: Sometimes the source’s incentives legitimately weaken evidence (e.g., self-reported data, conflict of interest).
- Fix: Ask: Is the argument rejecting a claim solely because of the person (ad hominem), or questioning reliability of evidence (sometimes legitimate)?
6. Memory Aids & Quick Tricks
| Trick / Mnemonic | What it helps you remember | When to use it |
|---|---|---|
| Causal TRIAD: Alt / Rev / Coinc | Causation attacks: Alternative cause, Reverse causation, Coincidence/third factor | Any causal conclusion from correlation or timing |
| “ONLY IF = NECESSARY” | “Only if” introduces the required condition | Translating conditionals quickly |
| Quantifier ladder: some < many < most < all | Scope shifts often hide in quantifiers | Any argument moving from a sample/example to a broad claim |
| “Compared to WHAT?” | Forces you to identify a missing baseline/standard | Any comparative claim: better, worse, safer, more efficient |
| Parts/Whole check: “team vs players” | Composition/division are easiest to spot with this mental image | Claims about groups and members |
| Policy checklist: Goal → Means → Feasible → Net good | Policy arguments often skip feasibility/side effects | “We should…” recommendations |
7. Quick Review Checklist
- Identify conclusion first, then premises.
- Pre-phrase the gap: “This assumes…” / “This fails to rule out…”
- For causation, check: alternative causes, reverse causation, coincidence/third variable, selection effects.
- For conditionals, translate carefully: only if = necessary, watch invalid reversals.
- Watch for scope shifts (some→all, local→national, short-term→long-term).
- Test for bad comparisons (different groups, different baselines, different time periods).
- Flag sampling problems (biased source, small sample, self-selection).
- Watch definition shifts and ambiguous terms (equivocation).
- In answers, avoid too extreme descriptions unless the stimulus really warrants them.
You don’t need to memorize every label—if you can consistently articulate the assumption the argument needs, you’ll crush these.