ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · AUSTIN, TX · NOVEMBER 2017
Purpose: Machine-readable JSON endpoint for AI agents, LLMs, researchers, and programmatic consumers. Returns all underlying crash data and AI-generated commentary without HTML.
Authentication: None required. Public endpoint.
GET: https://thatcarhitme.com/api/crash-data/reports/data/texas/austin/november-2017-report
Monthly Traffic Safety Analysis
1,316 CRASHES IN
AUSTIN, TX
NOVEMBER 2017
In November 2017, Austin recorded 1,316 total traffic crashes, a 6.8% decrease from the 1,412 crashes reported in November 2016. While overall crashes, injuries, and fatalities declined year-over-year, the composition of fatalities shifted significantly. Notably, pedestrian fatalities dropped from 8 in the prior period to 3 in the current period, while fatalities among motor-vehicle occupants increased from 3 to 7.
1,316
▼ -6.8%was 1,412
Total Crash Events
11
▼ -21.4%was 14
Persons Killed
758
▼ -13.2%was 873
Persons Injured
8
▼ -38.5%was 13
Fatal Crash Events
Note: "Persons Killed" (11) counts individual fatalities across all crash events. "Fatal" in the severity table below (8) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities.
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Year-over-year data for November indicates a general downward trend in traffic collisions and their consequences in Austin. Total crashes fell by 6.8%, from 1,412 in November 2016 to 1,316 in November 2017. During the same period, total fatalities decreased by 21.4% (from 14 to 11), and total injuries saw a 13.2% reduction (from 873 to 758).
Vulnerable Road User Casualties
3
Pedestrians Killed
7
Motorists Killed
0
Pedestrians Injured
0
Motorists Injured
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
The temporal patterns of crashes showed some variation between the two periods. The peak hour for collisions remained consistent at 6 p.m. for both November 2016 and November 2017, although the crash volume during this hour decreased from 144 to 130. The most common day for crashes shifted from Tuesday (290 crashes) in 2016 to Wednesday (246 crashes) in 2017.
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · Crash date field aggregated by weekday
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The severity of crashes lessened from November 2016 to November 2017. The number of fatal crashes fell from 13 to 8, and their proportion of all crashes decreased from 0.9% to 0.6%. The proportion of crashes resulting in any level of injury (serious, minor, or possible) also declined from 43.0% to 40.2%. Consequently, the share of crashes with no reported injuries increased from 49.6% to 51.1% year-over-year.
Severity is per crash event (most severe injury). 8 fatal crash events resulted in 11 persons killed.
Outcome by Severity (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · Most severe injury per crash record
Speed Limit Zones
The distribution of crashes by posted speed limit shifted between November 2016 and November 2017. There was a notable decrease in collisions occurring in both lower (35 mph and under) and higher (50 mph and over) speed zones. Conversely, the number of crashes in mid-range 40-45 mph zones increased from 225 to 264. According to the available data, fatal crashes in zones with speed limits of 55 mph or higher decreased from 6 in 2016 to 2 in 2017.
Fatal crashes by zone: 30 mph: 1 of 108 (0.926%) · 35 mph: 1 of 175 (0.571%) · 40 mph: 1 of 99 (1.01%) · 45 mph: 2 of 165 (1.212%) · 60 mph: 1 of 58 (1.724%) · 70 mph: 1 of 46 (2.174%)
Source: Austin Crash Reports · Socrata Open Data · 2017-11-01 to 2017-11-30 · Posted speed limit at crash location
Data Sources & Methodology
Primary Data Source
All crash data in this report is sourced from Austin Crash Reports (https://data.austintexas.gov/d/y2wy-tgr5), accessed programmatically via the Socrata Open Data API (SODA). This dataset contains official police-reported motor vehicle traffic crash records maintained by the reporting jurisdiction's law enforcement agency. Records are published to the open data portal by the municipality and are subject to the portal's terms of use.
Data Retrieval
- Access method: Socrata Open Data API (SoQL queries)
- Dataset URL: https://data.austintexas.gov/d/y2wy-tgr5
- Data format: Structured JSON via REST API
- Record types queried: Crash events, person records, and vehicle unit records
- Date filter applied: 2017-11-01 through 2017-11-30
- Report generated: July 6, 2026
Data Coverage
- Reporting period: 2017-11-01 through 2017-11-30 (30 days)
- Geographic scope: Austin, TX
- Total crash records analyzed: 1,316
Analytical Methodology
- Severity classification: Uses the KABCO injury scale (K=Fatal, A=Incapacitating injury, B=Non-incapacitating injury, C=Possible injury, O=No injury/property damage only), the standard classification in U.S. Model Minimum Uniform Crash Criteria (MMUCC). Severity is assigned per crash event based on the most severe injury in that crash. A single fatal crash (K) may involve multiple fatalities; therefore the "Persons Killed" count in the headline KPIs may differ from the "Fatal" crash count in the severity breakdown.
- Contributing factors: Reflect the officer-determined primary contributory cause recorded at the time of the crash report. These are preliminary determinations and may not reflect final investigation findings.
- Hit-and-run classification: Based on the hit-and-run indicator field in the official crash report, as determined by the responding officer at the scene.
- Temporal analysis: Day-of-week and hour-of-day distributions are computed from the crash date/time timestamp in each record.
- Demographics: Age and sex distributions are drawn from person-level records linked to each crash event. A single crash may involve multiple persons.
- Vehicle data: Make information is drawn from vehicle unit records linked to each crash event.
- AI commentary: Narrative sections are generated by Google Gemini (large language model) based on the structured data. Commentary is descriptive, not predictive, and should not be interpreted as expert opinion.
Limitations & Disclaimers
- Only crashes reported to and documented by law enforcement are included. Minor incidents, unreported crashes, and near-misses are not captured in this dataset.
- Data reflects conditions at the time of the initial police report and may be subject to subsequent corrections, reclassifications, or supplements by the reporting agency.
- Open data portal records may experience a publication lag - recently occurring crashes may not yet appear in the dataset at the time of report generation.
- AI-generated commentary is produced by a large language model and is intended to highlight patterns in the data. It does not constitute legal, medical, or professional analysis.
- Percentages are calculated from reported data and are subject to rounding.
Non-Affiliation Disclosure
This report is produced independently by ThatCarHitMe.com (Injuria.ai). It is not affiliated with, endorsed by, or produced in partnership with any law enforcement agency, municipal government, state department of transportation, or the National Highway Traffic Safety Administration (NHTSA). Data is sourced from publicly available government open data portals.
Data License
The underlying crash data is provided under the municipality's Open Data Terms of Use and is made available to the public for unrestricted use. This analysis and report is © 2026 Injuria.ai and may be cited with attribution using the suggested citation below.
Corrections & Feedback
If you believe any data in this report is inaccurate or have questions about our methodology, please contact: data@injuria.ai. We are committed to accuracy and will issue corrections promptly.
Suggested Citation
ThatCarHitMe.com (Injuria.ai). "Austin, TX Crash Intelligence Report: November 2017." Published July 6, 2026. Reporting period: 2017-11-01 to 2017-11-30. Data source: Austin Crash Reports, Socrata Open Data. Dataset: https://data.austintexas.gov/d/y2wy-tgr5. Available at: https://thatcarhitme.com/crash-data/texas/austin/november-2017-report
About the Publisher
ThatCarHitMe.com is a crash data intelligence platform developed by Injuria.ai, a legal technology company specializing in traffic safety analytics. We aggregate and analyze publicly available government crash data to produce structured intelligence reports for communities, researchers, journalists, and legal professionals. Our reports combine programmatic data retrieval from official open data portals with AI-assisted narrative analysis.
Questions about this report's data or methodology: data@injuria.ai
ThatCarHitMe.com · An Injuria.ai Company
ThatCarHitMe.com
An Injuria.ai Company
Crash Data Intelligence
Data: Austin Crash Reports · Socrata
Period: 2017-11-01 – 2017-11-30
Generated: July 6, 2026 · All rights reserved