ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · AUSTIN, TX · FEBRUARY 2019
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/february-2019-report
Monthly Traffic Safety Analysis
1,341 CRASHES IN
AUSTIN, TX
FEBRUARY 2019
In February 2019, Austin recorded 1,341 total crashes, a 5.3% increase from the 1,273 crashes documented in February 2018. During this same period, the number of traffic fatalities rose by 50%, from 4 to 6 deaths. The most notable year-over-year shift was this increase in fatalities, even as the total number of injuries saw a minor decrease.
1,341
▲ 5.3%was 1,273
Total Crash Events
6
▲ 50.0%was 4
Persons Killed
764
▼ -2.8%was 786
Persons Injured
6
▲ 50.0%was 4
Fatal Crash Events
Note: "Persons Killed" (6) counts individual fatalities across all crash events. "Fatal" in the severity table below (6) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities.
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Year-over-year data for February shows a rising trend in the total number of crashes and fatalities. Total crashes increased by 5.3%, from 1,273 in February 2018 to 1,341 in February 2019, and fatalities increased by 50% from 4 to 6. Conversely, the total number of injuries reported saw a slight decrease of 2.8%, from 786 to 764.
Vulnerable Road User Casualties
2
Pedestrians Killed
2
Motorists Killed
0
Pedestrians Injured
0
Motorists Injured
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · 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 shifts between the two periods. The peak day for crashes moved from Friday (215 crashes) in February 2018 to Tuesday (218 crashes) in February 2019. However, the peak hour for collisions remained consistent at 5 p.m. in both years, with a slight increase in incidents from 91 to 96.
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · Crash date field aggregated by weekday
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The severity of crashes shifted between the two periods, with the fatal crash rate increasing from 0.31 in February 2018 to 0.45 in February 2019. Fatal crashes accounted for 0.4% of all incidents in the current period, up from 0.3% in the prior year. While fatal crashes increased, the proportion of injury-related crashes declined, with serious injury crashes falling from 2.6% to 2.4% and minor injury crashes dropping from 20.7% to 17.4% of the total.
Outcome by Severity (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · Most severe injury per crash record
Speed Limit Zones
The overall distribution of crashes by posted speed limit remained consistent year-over-year, with the 35 mph, 45 mph, and 55 mph zones recording the highest number of incidents in both February 2018 and February 2019. However, the profile of fatal crashes changed; in February 2019, two fatal crashes occurred in 40 mph zones, where none were recorded in the prior year's period. The 35 mph zone also saw its fatal crash count increase from one to two year-over-year, while the 50 mph zone recorded one fatal crash in 2018 but none in 2019.
Fatal crashes by zone: 35 mph: 2 of 179 (1.117%) · 40 mph: 2 of 74 (2.703%) · 45 mph: 1 of 156 (0.641%)
Source: Austin Crash Reports · Socrata Open Data · 2019-02-01 to 2019-02-28 · 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: 2019-02-01 through 2019-02-28
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2019-02-01 through 2019-02-28 (28 days)
- Geographic scope: Austin, TX
- Total crash records analyzed: 1,341
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: February 2019." Published July 5, 2026. Reporting period: 2019-02-01 to 2019-02-28. 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/february-2019-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: 2019-02-01 – 2019-02-28
Generated: July 5, 2026 · All rights reserved