ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · BATON ROUGE, LA · JANUARY 2025
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/louisiana/baton-rouge/january-2025-report
Monthly Traffic Safety Analysis
1,010 CRASHES IN
BATON ROUGE, LA
JANUARY 2025
In January 2025, Baton Rouge recorded 1,010 total traffic crashes, an 8.3% decrease from the 1,101 crashes documented in January 2024. While total collisions and related injuries saw a decline, one of the most notable year-over-year shifts was a significant drop in crashes occurring during rainy conditions. The peak day for crashes also shifted from Tuesday in the prior year to Friday in the current period.
1,010
▼ -8.3%was 1,101
Total Crash Events
1
Fatal Crashes
811
▼ -6.6%was 868
Injury Crashes
229
▼ -1.7%was 233
Hit-and-Run Crashes
Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons.
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall traffic safety trends in Baton Rouge showed improvement in January 2025 compared to the same month in 2024. The total number of crashes fell by 8.3%, from 1,101 to 1,010. Similarly, the number of people injured in these incidents decreased by 6.6%, from 868 to 811, while fatalities remained constant at one for both periods.
229
Hit-and-Run Crashes — January 2025
▼ -1.7% vs prior (233)
The number of hit-and-run incidents remained relatively stable, decreasing slightly from 233 in January 2024 to 229 in January 2025. However, because the total number of crashes declined, the hit-and-run rate trended upward. Hit-and-runs constituted 22.7% of all crashes in the current period, an increase from the 21.2% rate recorded in the prior year.
When Crashes Happen
The timing of crashes in Baton Rouge shifted between January 2024 and January 2025. The peak day for collisions moved from Tuesday (201 crashes) in the prior year to Friday (202 crashes) in the current period. Crashes on Thursday also increased from 171 to 193, while Tuesday crashes saw a substantial drop from 201 to 111. Analysis of crash distribution by the hour of the day was not possible as this data was not provided for either period.
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Crash date field aggregated by weekday
Crash Severity Breakdown
Crash severity patterns saw a slight shift in January 2025 compared to the previous year. While the number of fatal crashes remained stable at one, the fatal crash rate increased marginally from 0.09% to 0.1% due to the lower total number of crashes. The proportion of crashes resulting in an injury rose from 78.8% (868 incidents) to 80.3% (811 incidents), even as the absolute number of injury crashes declined.
Outcome by Severity (Crash Events)
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Severity derived from reported fatal/injury indicators (no KABCO A/B/C codes)
Severity Distribution (Crash Events)
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Most severe injury per crash record
Top Contributing Factors
The leading contributing factors for crashes in January 2025 were consistent with the prior year, with 'Violations' being the most cited factor in both periods. The count for 'Violations' decreased slightly from 803 to 790, but its share of all contributing factors rose from 72.9% to 78.2%. Crashes attributed to 'Movement prior to crash' saw a notable drop in count from 233 to 177, a 24% decrease. Similarly, crashes linked to 'Driver condition' fell by 44.4%, from 27 incidents in January 2024 to 15 in January 2025.
Officer-Reported Primary Contributing Cause
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
Comparing environmental conditions, there was a significant decrease in crashes occurring during adverse weather in January 2025. Crashes in rainy conditions dropped from 135 to 48 year-over-year, and collisions on wet road surfaces fell from 219 to 83. Consequently, the proportion of crashes on dry roads increased, with the count rising from 847 to 878 despite an overall reduction in total crashes. Regarding lighting, the distribution remained largely consistent, with daylight crashes accounting for 63.8% of incidents in January 2025, slightly up from 62.4% in January 2024.
Weather
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Weather condition at time of crash
Lighting
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Lighting condition field
Road Surface
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-01-01 to 2025-01-31 · Road surface condition field
Data Sources & Methodology
Primary Data Source
All crash data in this report is sourced from Baton Rouge Crash Data, 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)
- Data format: Structured JSON via REST API
- Record types queried: Crash events, person records, and vehicle unit records
- Date filter applied: 2025-01-01 through 2025-01-31
- Report generated: June 19, 2026
Data Coverage
- Reporting period: 2025-01-01 through 2025-01-31 (31 days)
- Geographic scope: Baton Rouge, LA
- Total crash records analyzed: 1,010
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). "Baton Rouge, LA Crash Intelligence Report: January 2025." Published June 19, 2026. Reporting period: 2025-01-01 to 2025-01-31. Data source: Baton Rouge Crash Data, Socrata Open Data. Available at: https://thatcarhitme.com/crash-data/louisiana/baton-rouge/january-2025-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: Baton Rouge Crash Data · Socrata
Period: 2025-01-01 – 2025-01-31
Generated: June 19, 2026 · All rights reserved