ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · AUSTIN, TX · APRIL 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/april-2017-report
Monthly Traffic Safety Analysis
1,318 CRASHES IN
AUSTIN, TX
APRIL 2017
In April 2017, Austin recorded 1,318 total crashes, a 9.5% decrease from the 1,457 crashes reported in April 2016. Despite the overall reduction in collisions, the number of people killed increased significantly. The most notable year-over-year shift was the rise in total fatalities from 5 to 9, an 80% increase, even as total injuries fell from 928 to 865.
1,318
▼ -9.5%was 1,457
Total Crash Events
9
▲ 80.0%was 5
Persons Killed
865
▼ -6.8%was 928
Persons Injured
7
▲ 40.0%was 5
Fatal Crash Events
Note: "Persons Killed" (9) counts individual fatalities across all crash events. "Fatal" in the severity table below (7) 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-04-01 to 2017-04-30 · Aggregate counts from crash, person, and vehicle records
Trend Summary
The overall trend for traffic collisions in April 2017 shows a year-over-year decrease compared to April 2016. Total crashes fell by 9.5% from 1,457 to 1,318, and the number of people injured declined by 6.8% from 928 to 865. However, this downward trend did not extend to crash severity, as total fatalities rose from 5 to 9 during the same period.
Vulnerable Road User Casualties
2
Pedestrians Killed
5
Motorists Killed
0
Pedestrians Injured
0
Motorists Injured
Source: Austin Crash Reports · Socrata Open Data · 2017-04-01 to 2017-04-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 remained largely consistent between April 2016 and April 2017. Friday was the peak day for crashes in both periods, with 218 crashes in 2017 compared to 255 in 2016. Similarly, the 5 p.m. hour was the peak hour for collisions in both years, accounting for 108 crashes in 2017 and 114 in 2016. No significant shifts in the time or day of crash occurrences were observed year-over-year.
Source: Austin Crash Reports · Socrata Open Data · 2017-04-01 to 2017-04-30 · Crash date field aggregated by weekday
Source: Austin Crash Reports · Socrata Open Data · 2017-04-01 to 2017-04-30 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
While total crashes declined, the severity of collisions increased from April 2016 to April 2017. The number of fatal crashes rose from 5 to 7, and their proportion of all crashes increased from 0.3% to 0.5%. The share of crashes resulting in minor injuries also grew from 17.4% to 20.6%. Conversely, crashes resulting only in possible injury or no injury saw a decrease in their respective proportions of the monthly total.
Severity is per crash event (most severe injury). 7 fatal crash events resulted in 9 persons killed.
Outcome by Severity (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2017-04-01 to 2017-04-30 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2017-04-01 to 2017-04-30 · Most severe injury per crash record
Speed Limit Zones
A comparison of crash data by speed zone shows a general decrease in collisions in zones of 35 mph and higher, while crashes in zones of 30 mph or less increased from 151 to 160. In April 2017, fatal crashes were recorded across a wider range of speed limits, including zones of 55 mph, 65 mph, and 80 mph. This contrasts with April 2016, where all fatal crashes with a posted speed limit occurred in zones between 35 mph and 45 mph.
Fatal crashes by zone: 35 mph: 1 of 192 (0.521%) · 40 mph: 2 of 84 (2.381%) · 45 mph: 1 of 153 (0.654%) · 55 mph: 1 of 124 (0.806%) · 65 mph: 1 of 66 (1.515%) · 80 mph: 1 of 4 (25%)
Source: Austin Crash Reports · Socrata Open Data · 2017-04-01 to 2017-04-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-04-01 through 2017-04-30
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2017-04-01 through 2017-04-30 (30 days)
- Geographic scope: Austin, TX
- Total crash records analyzed: 1,318
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: April 2017." Published July 5, 2026. Reporting period: 2017-04-01 to 2017-04-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/april-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-04-01 – 2017-04-30
Generated: July 5, 2026 · All rights reserved