ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · AUSTIN, TX · NOVEMBER 2016
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-2016-report
Monthly Traffic Safety Analysis
1,412 CRASHES IN
AUSTIN, TX
NOVEMBER 2016
In November 2016, Austin recorded 1,412 vehicle crashes, an increase of 10.9% from the 1,273 crashes reported in November 2015. The most significant year-over-year change was a 75% increase in total fatalities, which rose from 8 in the prior period to 14 in the current period. Total injuries also increased by 7.1%, from 815 to 873.
1,412
▲ 10.9%was 1,273
Total Crash Events
14
▲ 75.0%was 8
Persons Killed
873
▲ 7.1%was 815
Persons Injured
13
▲ 44.4%was 9
Fatal Crash Events
Note: "Persons Killed" (14) counts individual fatalities across all crash events. "Fatal" in the severity table below (13) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities.
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-11-30 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Crash data for November 2016 indicates a rising trend in traffic incidents compared to the same month in the previous year. Total crashes increased by 139 incidents, from 1,273 to 1,412. This was accompanied by a rise in both fatalities, from 8 to 14, and injuries, from 815 to 873.
Vulnerable Road User Casualties
8
Pedestrians Killed
1
Cyclists Killed
3
Motorists Killed
0
Pedestrians Injured
0
Cyclists Injured
0
Motorists Injured
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-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 a shift in the peak day of the week between the two periods. In November 2016, Tuesday was the busiest day with 290 crashes, whereas Monday was the peak day in November 2015 with 213 crashes. However, the peak hour for collisions remained consistent year-over-year, with the 6 p.m. hour seeing the highest frequency in both November 2016 (144 crashes) and November 2015 (107 crashes).
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-11-30 · Crash date field aggregated by weekday
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-11-30 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The proportion of fatal crashes increased slightly, accounting for 0.9% of all incidents in November 2016 (13 crashes) compared to 0.7% in November 2015 (9 crashes). Conversely, the share of serious injury crashes decreased from 3.5% (44 incidents) in the prior period to 2.6% (37 incidents) in the current period. Crashes resulting in minor injuries saw a proportional increase, rising from 16.7% to 18.9% of total incidents year-over-year.
Severity is per crash event (most severe injury). 13 fatal crash events resulted in 14 persons killed.
Outcome by Severity (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-11-30 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-11-30 · Most severe injury per crash record
Speed Limit Zones
A comparison of crashes by speed limit reveals a shift toward higher speed zones. In November 2016, there were 436 crashes in zones posted at 50 mph or higher, up from 403 in the prior year. Conversely, incidents in zones posted at 45 mph or lower decreased from 604 to 582. The number of fatal crashes in higher speed zones (50+ mph) increased from 4 to 6 year-over-year, while fatalities in lower speed zones (below 50 mph) decreased from 5 to 3.
Fatal crashes by zone: 25 mph: 1 of 30 (3.333%) · 35 mph: 1 of 189 (0.529%) · 40 mph: 1 of 74 (1.351%) · 55 mph: 2 of 153 (1.307%) · 60 mph: 2 of 64 (3.125%) · 70 mph: 2 of 45 (4.444%)
Source: Austin Crash Reports · Socrata Open Data · 2016-11-01 to 2016-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: 2016-11-01 through 2016-11-30
- Report generated: July 6, 2026
Data Coverage
- Reporting period: 2016-11-01 through 2016-11-30 (30 days)
- Geographic scope: Austin, TX
- Total crash records analyzed: 1,412
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 2016." Published July 6, 2026. Reporting period: 2016-11-01 to 2016-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-2016-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: 2016-11-01 – 2016-11-30
Generated: July 6, 2026 · All rights reserved