/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

NTSB: the Uber self-driving test car that killed a pedestrian in Tempe, Arizona last year wasn't programmed to recognize and react to jaywalkers

- U.S. safety board releases documents on fatal 2018 accident  — Pedestrian hit, killed by experimental self-driving Uber car

Bloomberg

Context & Ripple Effects

This release closes the loop on an arc the coverage has tracked since March 2018, when Uber paused all self-driving testing after the Tempe fatality and police footage showed the safety driver glancing off-camera before impact. The first NTSB report already established that the car failed to identify the pedestrian or brake in time; today's documents go one layer deeper into why, showing the perception-and-planning software simply had no programmed path for someone crossing outside a designated area.

First-order effects

  • Uber's autonomous unit, already shelved after the crash, now has its core engineering decision on record: the system was designed around expected pedestrian behaviors, so a jaywalker fell outside what the vehicle would classify or respond to.

Second-order effects

  • Liability splits across layers rather than concentrating anywhere: the NTSB later named the safety driver the primary cause and faulted Uber's safety culture rather than the jaywalking gap itself, and by 2020 prosecutors charged the driver with negligent homicide — leaving software design exposed in civil and regulatory terms while criminal accountability landed on the human in the seat.

Third-order effects

  • Regulators now have a template for interrogating not just what a self-driving system did but what it was never built to do — pushing the industry toward explicit operational design boundaries where every scenario an autonomous car won't handle must be declared, tested for handoff, and justified before road testing.

The trend: Autonomous-vehicle oversight is shifting from reconstructing crashes after they happen to demanding upfront disclosure of each system's designed-in blind spots.

Discussion

  • @alexhern Hern on x
    There has never been a self-driving collision even close to a trolley problem. There's only one philosophical conundrum the field faces: “If you test safely, your competitors might beat you to the market. Pull this lever to feed human lives into your system, and maybe win.” https…
  • @brenttoderian Brent Toderian on x
    In other words, it wasn't programmed to recognize & react to completely predictable human behavior. #SelfDrivingCars #AutonomousVehicles https://twitter.com/...
  • @karlbode Karl Bode on x
    I think that's more than a “software bug in Uber's self-driving car technology,” which was the May 2019 explanation. https://twitter.com/...
  • @sustainable2050 Kees van der Leun on x
    Self-Driving Uber in Lethal Crash Wasn't Programmed to Spot Pedestrians Crossing the Road anywhere but on Crossroads. https://www.bloomberg.com/...
  • @kmac Kate Mackenzie on x
    It wasn't programmed to spot *humans* crossing the road. https://twitter.com/...
  • @ketanj0 Ketan Joshi on x
    These are chilling paragraphs for everyone who likes to walk, drive or cycle on public streets (aka the testing grounds for private companies and their lethal machines). https://www.bloomberg.com/... https://twitter.com/...
  • @tonyromm Tony Romm on x
    that would be like programming a plane not to identify clouds https://twitter.com/...
  • @mistydemeo Misty on x
    This Bloomberg article the Uber self-driving car accident that killed someone is incredibly damning, even outside the “car wasn't programmed for the concept of jaywalkers” angle. https://www.bloomberg.com/... https://twitter.com/...
  • @dannypage Untitled Danny Page on x
    First off, a bunch of people from Uber need to go to jail. Secondly, why did Arizona allow them on the road in the first place if it wouldn't pass a simple safety test? https://www.bloomberg.com/...
  • @robaeprice Rob Price on x
    At what point do you start holding engineers and executives directly liable for a failure of this magnitude? https://twitter.com/...