Home› New York› Nesconset
2025 Annual Fire Report

Fires in Nesconset, New York

In 2025, fire departments serving Nesconset responded to 32 fire and hazmat incidents . Here's the full picture.

Updated Sep 27, 2026 Grade A+ Peak yr 2025 Suffolk County 13,549 residents 1 reporting departments 79 5-yr
Total incidents
32
Not comparable with 2024 (incomplete reporting)
Building fires
6
Residential 67% Other 33%
Property loss
$0
$0 structure · $0 contents
Deaths & injuries
0 / 0
0 civilian deaths · 0 civ injuries · 0 firefighter injuries
01 The mix

What kinds of fires happen here?

Cooking fire, confined to container lead by count. Building fires lead by dollars. Together the top five categories make up about 84% of all calls.

32
Total Incidents
Cooking fire, confined to container 11 34.4%
Building fires 6 18.8%
Gas leak (natural gas or LPG) 5 15.6%
Power line down 3 9.4%
Fire, other 2 6.2%
All other categories 5 15.6%
02 Seasonality

When do fires happen?

Feb peaks. Oct dips. Watch for the typical fall climb starting in October.

Jan 1
Feb 5
Mar 4
Apr 1
May 2
Jun 3
Jul 5
Aug 3
Sep 2
Oct 0
Nov 3
Dec 3
Fewer
More
2b Five-year trend

Year over year in Nesconset

79 incidents 2021–2025. Peak year was 2025.

YearIncidentsYoY 
2021* 9 —
2022* 8 —
2023 28 —
2024* 2 —
2025 32 —

* Well below Nesconset's usual volume. That almost always means one or more departments didn't submit a full year to NFIRS, not that fires dropped, so no year-over-year change is shown for it.

03 Cause of ignition

What sparks building fires?

For the 6 building fires Nesconset departments responded to in 2025, here's how they were classified once investigators were finished.

05 How Nesconset compares

Nesconset vs New York vs the nation

Per-capita rates let us compare apples to apples. Nesconset sits below the national average for incidents per resident.

2.36
Incidents per 1,000 residents
Nesconset
2.36
NY avg
3.48
US avg
7.48
0.44
Building fires per 1,000 residents
Nesconset
0.44
NY avg
0.2
US avg
0.85
0
Civilian fire deaths per million
Nesconset
0
NY avg
1
US avg
5.9
5c Wildfires nearby

Wildfires within 50 mi of Nesconset

Top 25 wildfires (1992+) in the FPA-FOD ignitions database, scaled by acres. 9,730 acres burned in this 50-mile radius. Each dot is a fire — bigger dots burned more land.

50 mi radius
YearCauseAcresDistance 
1995 Arson/incendiarism 5,050 24.1 mi
1995 Equipment and vehicle use 1,000 10.5 mi
2012 Arson/incendiarism 992 16.6 mi
2013 Recreation and ceremony 363 43.5 mi
1992 Arson/incendiarism 250 10.5 mi
2012 Missing data/not specified/undetermined 190 47.7 mi
1999 Arson/incendiarism 175 44.5 mi
1995 Arson/incendiarism 152 24.1 mi
2002 Arson/incendiarism 125 7.7 mi
2000 Arson/incendiarism 125 44.5 mi
1995 Missing data/not specified/undetermined 100 38.4 mi
1998 Arson/incendiarism 100 10.5 mi
5d Top ZIPs

Where in Nesconset do fires concentrate?

Top 5 ZIP codes by NFIRS incident count across 2021–2025. Each ZIP has its own fire profile — dive in for neighborhood-level context.

#ZIP5-yr incidents 
1 11767 63
2 11779 9
3 11720 4
4 11738 2
5 11722 1
5e Peer cities

Cities similar to Nesconset

Six New York cities with population within ±25% of Nesconset. Useful comparison targets — same state, similar size, different fire profile.

06 First responders

Who responds in Nesconset?

1 departments report to NFIRS for incidents in Nesconset.

NESCONSET FIRE DEPARTMENT
25 GIBBS POND RD
FDID 52073
07 Stay prepared

Before the next Red Flag day.

A 30-minute weekend can cut your home's exposure substantially. These four checklists are a good starting point.

About this data

Numbers reflect incidents reported by participating fire departments to the National Fire Incident Reporting System (NFIRS) Public Data Release for calendar year 2025. NFIRS is voluntary — about 23,000 of roughly 30,000 US fire departments report — so totals are a strong indicator, not a complete census. Per-capita comparisons use 2023 ACS population estimates. Wildland fire data complements NFIRS with NIFC and USFS perimeters. Active-fire counts come from a dated NIFC snapshot, not a live feed.