FANALOwn the Record.crash explorer
School-zone camera report
The record · neutral crash data

Every reported crash in Fairfield, on one page

Fairfield Police have reported 22,295 crashes between 2017 and today. This page lays out the patterns and nothing more: how many, how serious, when they happen, and where. No arguments, just the record. If you want to know whether the new speed cameras actually target these crashes, the camera report picks that up below.

Data source
22,295
crashes reported, 2017–2026 YTD
2,350
per year, on average
20.4%
involved an injury, and 14 were fatal
Fri
busiest day · peaks around 3 PM

How many, and how serious

Most reported crashes are property damage only. From 2017 through 2026 the department counts 4,541 people injured, roughly 20.4 for every 100 crashes, and 14 killed. On the yearly chart below, gold marks the injury share.

Damage only, ~79.6% Injury, 20.4% · 14 fatal
Crashes by year
2,595
2017
2,629
2018
2,596
2019
1,646
2020
2,160
2021
2,521
2022
2,446
2023
2,271
2024
2,290
2025
1,141
2026
YearCrashesInjuryFatalInjury %vs prior year
20172,595524120.2%
20182,629521119.8%+1%
20192,596558321.5%-1%
20201,646354221.5%-37%
20212,160430219.9%+31%
20222,521486119.3%+17%
20232,446544222.2%-3%
20242,271453019.9%-7%
20252,290472120.6%+1%
2026 (YTD)1,141199117.4%

The honest way to read this is year over year. The full years from 2017 to 2025 have stayed close to 2,350 crashes, drifting down a little. 2026 is only year-to-date, so its bar and row are partial and we leave it out of the year-over-year column. The injury figures count people injured, which is why the injury bar can sit higher than the crash-only rate.

Month over month

Crashes stay fairly flat across the year, with a mild autumn bump that usually puts October among the busiest months. This is the real monthly shape, built from each incident's own date rather than one timestamp per location. Hover a bar to see its month and count.

Crashes by month, 2017–2026 YTD
223
’17
177
195
181
223
254
186
218
197
269
230
242
207
’18
172
212
185
241
245
206
194
205
279
241
242
187
’19
179
208
219
217
221
239
189
226
226
236
249
172
’20
164
106
49
71
138
151
151
158
177
142
167
112
’21
155
147
166
199
159
202
182
225
224
190
199
191
’22
152
186
213
236
226
204
197
208
243
227
238
179
’23
179
186
177
244
187
192
178
224
244
231
225
200
’24
174
154
173
206
214
179
173
191
203
215
189
235
’25
156
195
167
176
183
205
157
207
222
183
204
198
’26
187
162
168
215
193
18

The final bar is the current, partial month. Tick labels mark each January.

When crashes happen

Taken across all years, crashes bunch up on Friday and in the late afternoon, peaking around 3 PM. That is the evening commute, not the small hours of the night. Use the year filter to see how any single year looks, and hover a bar for its exact count.

In 2017–2026, crashes cluster on Friday and peak around 3 PM (22,295 crashes with a timestamp). Switch the year to see the shape change.

Crashes by day of week · 2017–2026
2,093
Sun
3,169
Mon
3,396
Tue
3,476
Wed
3,367
Thu
3,884
Fri
2,910
Sat
Crashes by hour of day · 2017–2026
193
12a
176
138
79
3a
60
113
411
6a
738
1,036
1,103
9a
1,280
1,504
1,738
12p
1,829
1,963
1,964
3p
1,791
1,821
1,442
6p
955
725
518
9p
414
304

Where crashes happen

Warmer colors are denser crash clusters. Crashes concentrate on the major arterials and their intersections.

Crash density (2017–present)

The map uses the 21,882crashes that carry coordinates. The counts above use the department's full totals, so the difference between them is the crashes reported without a mappable location.

Highest-crash locations
#LocationCrashes
1BLACK ROCK200
2I95 NB 18 TO 19174
3EASTON150
4ARROWHEAD145
5BLACK ROCK136
6BLACK ROCK126
7GRASMERE117
8BLACK ROCK114
9KINGS HWY CUTOFF109
10MERRITT SB 44 TO 42108
11VILLA101
12BLACK ROCK100
Crashes by street
StreetCrashesShare
BLACK ROCK3,67116.8%
POST3,62716.6%
KINGS9504.3%
KINGS HWY CUTOFF7303.3%
BENSON7073.2%
PARK6733.1%
VILLA5682.6%
MILL PLAIN3711.7%
UNQUOWA3481.6%
REEF3481.6%
STRATFIELD3421.6%
TUNXIS HILL3151.4%

Street and location labels are the representative value reported per coordinate; treat as approximate.

Follow the data

Fanal keeps an open, reproducible record of Fairfield crashes and enforcement. Subscribe for the next refresh and new jurisdictions.

About this data

Source: the Fairfield Police Department Interactive Crime & Statistical Dashboard, incident years 2017–2026. We pull it straight from the dashboard's query API at the incident level, so each crash arrives with its own timestamp, street, call type, and coordinates. The counts, the month, hour, and day breakdowns, and severity all use the full incident set. The spatial views (the heatmap, the highest-crash locations, and the by-street table) use the 21,882 crashes with coordinates across 6,422 distinct locations, which is why they read a little below the department totals. Injuries and fatalities are people counts. Everything here is counts rather than rates, with no adjustment for traffic volume. The department may shift coordinates slightly for privacy.