Home› North Carolina› Carolina Shores
2025 Annual Fire Report

Fires in Carolina Shores, North Carolina

In 2025, fire departments serving Carolina Shores responded to 11 fire and hazmat incidents . Here's the full picture.

Updated Sep 27, 2026 Grade A+ Peak yr 2025 Brunswick County 4,643 residents 0 reporting departments 13 5-yr
Total incidents
11
Not comparable with 2024 (incomplete reporting)
Building fires
2
Residential 50% Other 50%
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?

Gas leak (natural gas or LPG) lead by count. Building fires lead by dollars. Together the top five categories make up about 91% of all calls.

11
Total Incidents
Gas leak (natural gas or LPG) 3 27.3%
Building fires 2 18.2%
Arcing, shorted electrical equipment 2 18.2%
Authorized controlled burning 2 18.2%
Brush, or brush and grass mixture fire 1 9.1%
All other categories 1 9.1%
02 Seasonality

When do fires happen?

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

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

Year over year in Carolina Shores

13 incidents 2021–2025. Peak year was 2025.

YearIncidentsYoY 
2021* 1 —
2022* 0 —
2023* 1 —
2024* 0 —
2025 11 —

* Well below Carolina Shores'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 2 building fires Carolina Shores departments responded to in 2025, here's how they were classified once investigators were finished.

05 How Carolina Shores compares

Carolina Shores vs North Carolina vs the nation

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

2.37
Incidents per 1,000 residents
Carolina Shores
2.37
NC avg
9.36
US avg
7.48
0.43
Building fires per 1,000 residents
Carolina Shores
0.43
NC avg
1.35
US avg
0.85
0
Civilian fire deaths per million
Carolina Shores
0
NC avg
8.6
US avg
5.9
5c Wildfires nearby

Wildfires within 50 mi of Carolina Shores

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

50 mi radius
YearCauseAcresDistance 
2009 Debris and open burning 19,130 20.8 mi
1997 Missing data/not specified/undetermined 3,150 43.9 mi
2001 Arson/incendiarism 1,911 12.7 mi
2002 Debris and open burning 1,648 26.4 mi
2016 Debris and open burning 1,577 22.8 mi
2011 Fireworks 1,155 21.9 mi
2009 Debris and open burning 1,089 40.4 mi
1993 Debris and open burning 970 25.0 mi
1996 Missing data/not specified/undetermined 844 27.7 mi
2008 Missing data/not specified/undetermined 830 48.9 mi
2007 Arson/incendiarism 765 32.2 mi
1998 Debris and open burning 750 13.9 mi
5d Top ZIPs

Where in Carolina Shores do fires concentrate?

Top 1 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 28467 13
5e Peer cities

Cities similar to Carolina Shores

Six North Carolina cities with population within ±25% of Carolina Shores. Useful comparison targets — same state, similar size, different fire profile.

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.