Skip to content
worldfires
US · United States · →

Fox Mountain Fire, October 2016 Dade, DeKalb

Out · last measured on 4 Oct 2016

The fire started on 4 October 2016 in Dade, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 410 hectares, spread across 2 counties.

It is the 13th largest in Georgia since 2016 (of 14 with a page). Number 472 in United States in 2016, of 475.

Burnt area
410ha
official perimeter (MTBS / NIFC)
Duration
1day
4 Oct 2016 – 4 Oct 2016
Municipalities hit
2
counties
Started on
4 Oct
2016
Heat detections
66
in a single hotspot: 36 MW
Danger at start
21
Moderate · FWI index

Where it burned

HOTSPOTS BY DAY 4 Oct4 Oct

The weather it burned in

27°high
39km/h · peak gust
36%lowest humidity

It had gone 7 days without rain (1 mm or more) when it started.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Dade where it started
    250 ha reached on 7 Oct
    0.6 %
  2. DeKalb
    156 ha reached on 7 Oct
    0.1 %

Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.

The weather day by day

ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.

Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

Day High Min. humidity Peak gust Rain Danger (FWI)
4 Oct 27.3 °C 36 % 39 km/h 0.0 mm Moderate 21
5 Oct after 27.5 °C 32 % 29 km/h 0.0 mm Moderate 21
6 Oct after 27.7 °C 32 % 27 km/h 0.0 mm Moderate 21
7 Oct after 28.4 °C 27 % 32 km/h 0.0 mm High 25
8 Oct after 24.9 °C 33 % 63 km/h 0.0 mm High 32
9 Oct after 23.2 °C 21 % 51 km/h 0.0 mm High 31
10 Oct after 23.7 °C 24 % 29 km/h 0.0 mm High 26
11 Oct after 23.6 °C 22 % 34 km/h 0.0 mm High 26
12 Oct after 23.6 °C 24 % 27 km/h 0.0 mm High 25
13 Oct after 26.2 °C 31 % 23 km/h 0.0 mm High 24
14 Oct after 24.4 °C 40 % 36 km/h 0.0 mm High 24

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 27 Sept 2016
After · 11 Oct 2016

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Detections table · 66Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Frequently asked questions

How long did the Fox Mountain Fire fire last?
It burned between 4 October 2016 and 4 October 2016: 1 day, according to the start date recorded by United States agencies (MTBS / NIFC) and the heat detections seen by satellite.
How much area did it burn?
The official perimeter published by United States agencies (MTBS / NIFC) is 410 hectares (4.1 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire entered 2 counties: Dade (250 ha, 0.6 %); DeKalb (156 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 27.3 °C, humidity dropped to 36 % and gusts hit 39 km/h. The fire danger index (FWI) reached 21, class Moderate.
Where does this data come from?
From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. It is not an official report.

Where to verify it

A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.

Emergency number: 911

Satellite cross-check

Does something look wrong on this page?

This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.

Report an error
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 911.

Where this data comes from

The perimeter is official and in the public domain. For past years it comes from MTBS (Monitoring Trends in Burn Severity), run by the U.S. Geological Survey and the USDA Forest Service, which map it on Landsat and Sentinel-2 imagery. For the current and last year it comes from WFIGS at the National Interagency Fire Center (NIFC): incident perimeters mapped by fire crews, aircraft and imagery. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. County boundaries come from geoBoundaries ADM2 (Public Domain). The area per county is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.