About the data

What this dataset is, how each case is found and coded, what it cannot tell you, and how to use and cite it.

We're iteratively improving this site and dataset. Please email corrections or suggestions to consortium@crimrxiv.com.

What it is

A case is one incident in which a vehicle's automated-driving feature is claimed, questioned or confirmed to be involved: a crash, a near miss, a police stop, a person found asleep at the wheel, or a court case about any of these. Incidents with no collision are included. The dataset covers Tesla (Autopilot, Full Self-Driving, Summon and its robotaxi service) for now, and is built so other makers can be added.

It is meant for research and teaching in criminology and related fields: who is said to have done what, how police, prosecutors, regulators and courts respond, and how responsibility is attributed when a machine shares the driving.

How cases are found

Once a day, a program searches Google News and Bing News for reports that name an automated-driving feature and describe something that happened. Reports about the same event are grouped into one case, and later reports (an arrest, a lawsuit, a verdict) are attached to the case they belong to. Round-ups of several incidents, statistics, product news and opinion pieces are set aside and listed, with the reason, in screened_out.csv.

How cases are coded

A language model reads the reports attached to a case (the article text where the publisher allows it, otherwise the headline and summary) and drafts the coded variables, a short neutral narrative, and a list of who said what. Three rules limit what it can assert:

  • It may use only the reports attached to the case.
  • Every coded value must come with a quotation, and the program keeps the value only if that quotation is found word for word in the report. Values that fail are removed and counted on the case page.
  • A mention of a feature is never treated as evidence that it was in use. The variable engagement_status separates what an official source or the maker's own data states from what a driver, lawyer or witness claims.

Every record is marked “machine-coded, not yet reviewed” until a person has checked it. Summaries shown on the homepage are each publisher's own words, not ours.

What it cannot tell you

  • It is not a count of all incidents. It holds only incidents that reached published news in English and that our searches found. Many incidents are never reported.
  • Counts are not rates. Nothing here says how often these features are used without incident, so the data cannot show whether they are safer or less safe than a human driver.
  • It does not establish fault or cause. It records what coverage reports and who says so.
  • Machine coding makes mistakes. Dates, places and counts can be wrong, and two cases may turn out to be the same event. Check the linked sources before relying on a record.
  • Coverage changes. Early reports are often revised. A case reflects the reports attached to it on the date shown.

Privacy

Coded fields, narratives and claims describe people by role (“the driver”, “a passenger”) and do not name private individuals. Names may still appear in publishers' headlines and in the linked reports. We store links and short quotations, not copies of articles. To ask for a change, email consortium@crimrxiv.com.

Download, licence and citation

Download everything as one .zip, or take single files: cases.csv, evidence.csv, claims.csv, sources.csv, screened_out.csv, cases.json, codebook.json.

The data are free to reuse under CC BY 4.0. The code that builds them is on GitHub, where every change to the data is recorded.

Cite as: CrimConsortium. Self-Driving Incidents Explorer [dataset]. https://selfdriving.crimconsortium.com/ (data as of November 22, 2026; codebook version 0.1).

Codebook, version 0.1

26 coded variables. Select one to see its definition and allowed values. A blank value means the reports read did not state it.

Incident

Incident dateincident_date

Date the incident happened, as stated in coverage: YYYY-MM-DD, or YYYY-MM or YYYY when only that much is given. Work out relative dates ("Thursday night") from the report's publication date. (date)

Type of incidentincident_type

What kind of event the coverage describes. (one value)

collision
The vehicle struck, or was struck by, something or someone.
near_miss_or_erratic_driving
No collision reported: a near miss, swerving, running a signal, wrong-way travel or similar.
traffic_stop_or_violation
No collision reported: the coverage centres on a police stop, citation or arrest.
driver_asleep_or_absent
No collision reported: the person in the car was seen asleep, out of the driver's seat, or absent.
low_speed_or_parking_manoeuvre
Something that happened while parking, summoning or creeping at walking pace.
other
An identifiable incident that fits none of the above.
Collided withcollision_with

What the vehicle collided with, if there was a collision. (one or more values)

passenger_vehicle
Car, SUV, pickup or van.
truck_or_bus
Heavy truck, tractor-trailer or bus.
motorcycle
Motorcycle or scooter.
bicycle
Bicycle or e-bike.
pedestrian
Person on foot.
emergency_or_police_vehicle
Police, fire, ambulance or tow vehicle.
train
Train or tram.
fixed_object
Pole, tree, barrier, wall, building and the like.
construction_zone_or_equipment
Work-zone equipment, barrels or vehicles.
animal
Animal.
other
Anything else.
Vehicle makevehicle_make

Make of the vehicle whose automated-driving feature is in question (for example Tesla). (short text)

Vehicle modelvehicle_model

Model, as named in coverage (for example Model Y, Cybertruck, Cybercab). (short text)

Model yearvehicle_model_year

Model year of that vehicle, when coverage gives it. (whole number)

Place and time

City or localitylocation_city

City, town or county where the incident happened. (short text)

State or regionlocation_state_region

State, province or region, written in full. (short text)

Countrylocation_country

Country, written in full (for example United States). (short text)

Road settingroad_type

Where on the road network the incident happened. (one value)

highway_or_freeway
Interstate, freeway, motorway or other limited-access road.
urban_or_suburban_street
City or suburban street.
rural_road
Rural or country road.
intersection
At a junction or signal.
parking_lot_or_driveway
Car park, garage or driveway.
rail_crossing
Railway or tram crossing.
other
Any other setting.
Time of daytime_of_day

When in the day the incident happened. (one value)

daytime
In daylight.
night
After dark.
dawn_or_dusk
Around sunrise or sunset.

Automation

Automated-driving feature namedsystem_named

Which automated-driving feature(s) the coverage names. Naming a feature is not evidence it was in use. (one or more values)

autopilot
Tesla Autopilot or Autosteer.
full_self_driving
Tesla Full Self-Driving (FSD), supervised or otherwise.
robotaxi_or_driverless_service
A robotaxi or other vehicle operating with no driver.
summon_or_autopark
Summon, Smart Summon or Autopark.
unspecified
"Self-driving mode", "driver assistance" and similar, with no product named.
Was the feature in use?engagement_status

The strongest statement the coverage supports about whether the feature was in use at the time. This records what coverage reports; it is not a finding by this dataset. (one value)

confirmed_by_official_source
A police or regulator finding, a court finding, or the manufacturer's own data report states the feature was in use.
claimed
Someone says it was in use (for example the driver, or police relaying the driver's account) and coverage reports no official confirmation.
alleged_in_legal_filing
The claim that it was in use is made in a lawsuit or criminal case.
under_investigation
Coverage says whether it was in use is unknown or being investigated.
disputed
Sources in the coverage contradict each other about whether it was in use.
reported_not_engaged
An official source or the manufacturer says it was not in use.
mentioned_only
The feature is mentioned as background; nobody in the coverage says it was in use.
Who says it was in useengagement_claimed_by

Everyone the coverage reports as saying the feature was in use. (one or more values)

driver
Driver.
passenger
Passenger.
police
Police.
prosecutor
Prosecutor.
manufacturer
Manufacturer.
regulator
Regulator.
ntsb
NTSB.
plaintiff_or_plaintiff_lawyer
Plaintiff or plaintiff lawyer.
defense_lawyer
Defense lawyer.
court_or_jury
Court or jury.
witness
Witness.
news_outlet
News outlet.
other
Other.
Someone in the driver's seatdriver_seat_occupied

Whether coverage says a person was in the driver's seat. (one value)

yes
A person was in the driver's seat.
no
The driver's seat was empty.
Driver condition mentioneddriver_condition_mentioned

Conditions of the person responsible for the vehicle that coverage mentions. Mentions, not findings. (one or more values)

alcohol_or_drugs
Alcohol or drug impairment is alleged or reported.
asleep_or_drowsy
The driver is said to have been asleep or drowsy.
distracted
Phone use or another distraction is reported.
medical_event
A medical emergency is reported.
not_supervising
Hands off the wheel, eyes off the road, or otherwise not monitoring.

Harm

Deaths reportedfatalities

Number of people coverage reports as killed. 0 only when coverage says nobody died. (whole number)

Injuries reportedinjuries

Number of people coverage reports as injured but not killed. 0 only when coverage says nobody was hurt. (whole number)

Who was harmedpersons_harmed

Roles of the people reported killed or injured. (one or more values)

subject_vehicle_driver
The driver of the vehicle in question.
subject_vehicle_passenger
A passenger in that vehicle.
other_vehicle_occupant
Someone in another vehicle.
motorcyclist
A motorcyclist.
cyclist
A cyclist.
pedestrian
A pedestrian.
emergency_or_road_worker
A police officer, firefighter, medic, tow operator or road worker.

Official response

Police actionpolice_action

The furthest police action that coverage reports. (one value)

investigating
Police are investigating.
citation_issued
A citation or ticket was issued.
arrest_made
Someone was arrested.
Criminal chargescriminal_charges

Charges reported, in a few words (for example "DUI; reckless driving"). No names. (short text)

Criminal case stagecriminal_case_stage

The furthest stage of any criminal case that coverage reports. (one value)

charged
Charges filed or announced.
plea
A plea was entered.
trial
At trial.
convicted
Found guilty.
acquitted
Found not guilty.
sentenced
Sentenced.
dismissed
Charges dropped or dismissed.
Civil litigationcivil_litigation

The furthest stage of any lawsuit about the incident that coverage reports. (one value)

lawsuit_filed
A lawsuit has been filed.
trial
At trial.
verdict_for_plaintiff
Verdict for the person suing.
verdict_for_defendant
Verdict for the party sued.
settled
Settled.
dismissed
Dismissed.
Regulator or safety boardregulator_involved

Regulators or safety boards that coverage says are involved in this incident. (one or more values)

nhtsa
U.S. National Highway Traffic Safety Administration.
ntsb
U.S. National Transportation Safety Board.
state_regulator
A U.S. state agency such as a DMV or utilities commission.
non_us_regulator
A regulator outside the United States.
Responsibility attributed toresponsibility_attributed_to

Where anyone quoted or cited in coverage places responsibility. This records attributions made by others; the dataset never judges fault. (one or more values)

driver
The person responsible for the vehicle.
automation_or_manufacturer
The automated-driving feature or its maker.
other_road_user
Another driver, rider or pedestrian.
road_or_weather_conditions
Road design, work zones, weather or lighting.

Coverage

Stage of coveragecoverage_stage

What the most recent coverage is mainly about. (one value)

initial_report
First reports of the incident.
follow_up_investigation
Later reporting on an investigation or new findings.
legal_proceeding
Reporting on charges, a lawsuit, a trial or a verdict.
retrospective
A look back at an older incident.