Tesla driver in fatal Texas crash pressed accelerator 100%, NTSB confirms ⁠27%

By Sean O'Kane⁠28%

7/15/2026, 8:22:52 PM

BS Summary: This article contains 23 faulty reasoning types, including Availability Heuristic, Ambiguity (Equivocation), and Hasty Generalization, with Appeal to Authority as the most egregious example at 23% saturation with 79 hits. Analysis detected 612 faulty-reasoning hits from 344 analyzed words, generating a BS Score of 38.4% and a BS Rank of ⁠27% (15,512 of 21,172 articles). This article is better (less manipulative) than 73.30% of the article peer group.

The National Transportation Safety Board (NTSB) said Wednesday that the driver of a Tesla who crashed into a house in June had pressed the accelerator pedal to 100%, overriding the company’s Full Self-Driving (Supervised) software. 
Data recovered from the Tesla showed that the vehicle was traveling more than 70 miles per hour when it struck a house in Katy, Texas, killing 76-year-old resident Martha Avila, according to the NTSB. 
The family of the victim has since sued the alleged driver, 44-year-old Michael Butler, and Tesla, claiming negligence. 
Butler has also been charged with manslaughter. 
The safety board shared the information as part of a preliminary report on the progress of its investigation into the crash. 
The National Highway Traffic Safety Administration is also probing the incident. 
The data confirms Tesla's account of the crash, which the company shared in the days after it happened in order to show that its advanced driver assistance system wasn’t to blame. 
“[T]his [allegation] makes no sense. 
FSD drives slowly through neighborhood streets and this was a high speed crash! 
” Tesla CEO Elon Musk wrote on X shortly after the crash. 
The NTSB said Wednesday that the 44-year-old driver was using Full Self-Driving (Supervised) on Rose Hollow Lane, a residential two-lane road with a speed limit of 30 miles per hour, prior to the crash. 
Security camera footage obtained by the safety board showed the car accelerating through an intersection, leaving the road, and hitting the house. 
The “weather was clear, the roadway was dry, and daylight conditions were present,” according to the NTSB. 
Tesla requires that drivers using Full Self-Driving (Supervised) pay attention to the road and be ready to take control at any moment. 
Butler allegedly told authorities that he had “passed out” and that he was using Tesla's driver assistance system. 
Police reportedly discovered that his Google searches included the terms “Tesla FSD not aggressive enough 2026,” “Tesla not aggressive enough,” and “Tesla FSD too timid,” according to local ABC news affiliate station KTRK TV. 
Article reasoning-pattern comparisonThis article: 12.2%Sean O'Kane: 3.5%TechCrunch: 3.0%Confirmation Bias12.2%This article: 0.0%Sean O'Kane: 1.9%TechCrunch: 1.4%Anchoring Bias0.0%This article: 14.5%Sean O'Kane: 2.9%TechCrunch: 3.5%Availability Heuristic14.5%This article: 3.8%Sean O'Kane: 0.4%TechCrunch: 1.1%Representativeness Heuristic3.8%This article: 0.0%Sean O'Kane: 1.1%TechCrunch: 0.6%Hindsight Bias0.0%This article: 0.0%Sean O'Kane: 0.6%TechCrunch: 2.5%Overconfidence Bias0.0%This article: 6.4%Sean O'Kane: 2.0%TechCrunch: 4.8%Framing Effect6.4%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.6%Loss Aversion0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.6%Status Quo Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.2%Sunk Cost Effect0.0%This article: 0.0%Sean O'Kane: 5.4%TechCrunch: 5.0%Optimism Bias0.0%This article: 1.5%Sean O'Kane: 1.1%TechCrunch: 1.2%Pessimism Bias1.5%This article: 11.9%Sean O'Kane: 9.3%TechCrunch: 5.0%Negativity Bias11.9%This article: 9.0%Sean O'Kane: 2.7%TechCrunch: 2.1%Self-Serving Bias9.0%This article: 5.2%Sean O'Kane: 1.2%TechCrunch: 0.5%Fundamental Attribution Error5.2%This article: 0.0%Sean O'Kane: 0.6%TechCrunch: 0.1%Actor-Observer Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.6%In-Group Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.3%Out-Group Homogeneity Bias0.0%This article: 0.0%Sean O'Kane: 1.8%TechCrunch: 3.3%Halo Effect0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.1%Horn Effect0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.0%Dunning-Kruger Effect0.0%This article: 0.0%Sean O'Kane: 3.3%TechCrunch: 2.3%Recency Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.3%Primacy Effect0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.1%Blind-Spot Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.3%Ad Hominem0.0%This article: 0.0%Sean O'Kane: 0.4%TechCrunch: 0.6%Straw Man0.0%This article: 23.0%Sean O'Kane: 4.1%TechCrunch: 4.3%Appeal to Authority23.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 1.7%False Dilemma0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.6%Slippery Slope0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.2%Circular Reasoning0.0%This article: 13.7%Sean O'Kane: 2.8%TechCrunch: 6.0%Hasty Generalization13.7%This article: 9.9%Sean O'Kane: 1.2%TechCrunch: 0.2%Red Herring9.9%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 1.2%Bandwagon0.0%This article: 2.0%Sean O'Kane: 0.2%TechCrunch: 2.2%Appeal to Emotion2.0%This article: 1.5%Sean O'Kane: 1.1%TechCrunch: 0.6%Begging the Question1.5%This article: 9.0%Sean O'Kane: 1.5%TechCrunch: 2.9%Post Hoc (False Cause)9.0%This article: 5.2%Sean O'Kane: 0.6%TechCrunch: 0.1%Tu Quoque5.2%This article: 5.2%Sean O'Kane: 0.6%TechCrunch: 0.5%Burden of Proof5.2%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.2%Appeal to Nature0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.3%Composition/Division0.0%This article: 6.4%Sean O'Kane: 0.8%TechCrunch: 2.4%Anecdotal6.4%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.1%No True Scotsman0.0%This article: 14.0%Sean O'Kane: 1.8%TechCrunch: 2.0%Ambiguity (Equivocation)14.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.2%Middle Ground0.0%This article: 1.5%Sean O'Kane: 0.2%TechCrunch: 0.0%Personal Incredulity1.5%This article: 6.4%Sean O'Kane: 0.8%TechCrunch: 0.1%Special Pleading6.4%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.1%Genetic Fallacy0.0%This article: 1.5%Sean O'Kane: 0.8%TechCrunch: 2.0%Unattributed Quote1.5%This article: 1.5%Sean O'Kane: 1.3%TechCrunch: 0.7%Quote-first Misdirection1.5%This article: 12.8%Sean O'Kane: 2.7%TechCrunch: 4.6%Biased Writer Voice12.8%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.8%Indoctrination0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.1%Politically Left Leaning Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 0.1%Politically Right Leaning Bias0.0%This article: 0.0%Sean O'Kane: 0.0%TechCrunch: 4.6%Attempt to Sell a Product or S…0.0%

344 words analyzed.

Speakers

5speakers72%attributed speech97writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 11 words • 0.0% coverageNational Transportation Safety Board (NTSB) • 35 words • 0.0% coverageNational Transportation Safety Board (NTSB) • 34 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageWriter's voice • 7 words • 0.0% coverageWriter's voice • 21 words • 0.0% coverageNational Highway Traffic Safety Administration • 11 words • 0.0% coverageTesla • 31 words • 100.0% coverageElon Musk • 5 words • 100.0% coverageElon Musk • 13 words • 100.0% coverageElon Musk • 12 words • 0.0% coverageNational Transportation Safety Board (NTSB) • 34 words • 0.0% coverageWriter's voice • 22 words • 0.0% coverageNational Transportation Safety Board (NTSB) • 16 words • 0.0% coverageTesla • 22 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageKTRK TV • 34 words • 0.0% coverage
Selected voice

KTRK TV

100%flagged-word coverage
34 attributed words14% of attributed speech78% writer coverage

No manipulation-pattern hits were found in this speaker's attributed words or the writer's voice.

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.