ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · BATON ROUGE, LA · FEBRUARY 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/february-2025-report
Monthly Traffic Safety Analysis
1,184 CRASHES IN
BATON ROUGE, LA
FEBRUARY 2025
In February 2025, Baton Rouge recorded 1,184 total crashes, a 3.9% decrease from the 1,232 crashes reported in February 2024. Despite the overall drop in collisions, the number of fatalities resulting from these crashes increased from two to three year-over-year.
1,184
▼ -3.9%was 1,232
Total Crash Events
3
▲ 50.0%was 2
Fatal Crashes
940
▼ -1.9%was 958
Injury Crashes
248
▼ -5.3%was 262
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-02-01 to 2025-02-28 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall traffic crash trends in Baton Rouge showed a slight decline in February 2025 compared to the same month in 2024. Total collisions fell by 3.9%, from 1,232 to 1,184, and total injuries decreased by 1.9% from 958 to 940. However, the number of fatalities rose from two to three.
248
Hit-and-Run Crashes — February 2025
▼ -5.3% vs prior (262)
The number of hit-and-run incidents in Baton Rouge saw a slight decrease in February 2025 compared to the prior year. The total count of hit-and-run crashes fell from 262 to 248. The hit-and-run rate, which measures the percentage of all crashes that were hit-and-runs, also declined modestly from 21.3% in February 2024 to 20.9% in February 2025.
When Crashes Happen
The temporal patterns of crashes showed some consistency year-over-year, with Thursday remaining the peak day for crashes in both February 2025 (207 crashes) and February 2024 (215 crashes). A notable shift occurred during the weekend, where crash counts decreased from the prior year. Collisions on Sundays fell from 153 to 117, and crashes on Saturdays dropped from 150 to 125.
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-02-01 to 2025-02-28 · Crash date field aggregated by weekday
Crash Severity Breakdown
The severity of crashes shifted year-over-year, with a notable increase in fatal outcomes. The number of fatal crashes rose from two to three, and the fatal crash rate increased from 0.16% to 0.25%. While the absolute number of injury-related crashes decreased slightly from 958 to 940, their share of all crashes grew from 77.8% to 79.4%.
Outcome by Severity (Crash Events)
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-02-01 to 2025-02-28 · 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-02-01 to 2025-02-28 · Most severe injury per crash record
Top Contributing Factors
The ranking of the top contributing factors remained consistent, led by 'Violations' in both periods. The count of crashes attributed to 'Violations' increased by 4.0%, from 910 to 946. In contrast, crashes related to the second-ranked factor, 'Movement prior to crash,' saw a 23.3% decrease in count, from 266 to 204. Crashes involving 'Driver condition' also fell by 50.0%, from 26 incidents to 13.
Officer-Reported Primary Contributing Cause
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-02-01 to 2025-02-28 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
Crashes in February 2025 occurred under slightly more adverse environmental conditions compared to the previous year. The proportion of crashes happening in the rain increased from 4.2% to 6.7% of all incidents. Correspondingly, the share of collisions on wet road surfaces rose from 5.6% in February 2024 to 10.2% in February 2025, while the share of crashes on dry roads decreased.
Weather
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-02-01 to 2025-02-28 · Weather condition at time of crash
Lighting
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-02-01 to 2025-02-28 · Lighting condition field
Road Surface
Source: Baton Rouge Crash Data · Socrata Open Data · 2025-02-01 to 2025-02-28 · 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-02-01 through 2025-02-28
- Report generated: June 19, 2026
Data Coverage
- Reporting period: 2025-02-01 through 2025-02-28 (28 days)
- Geographic scope: Baton Rouge, LA
- Total crash records analyzed: 1,184
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: February 2025." Published June 19, 2026. Reporting period: 2025-02-01 to 2025-02-28. Data source: Baton Rouge Crash Data, Socrata Open Data. Available at: https://thatcarhitme.com/crash-data/louisiana/baton-rouge/february-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-02-01 – 2025-02-28
Generated: June 19, 2026 · All rights reserved