Skip to content
worldfires
US · United States · –

Anderson fire, November 2016 Anderson

Out · last detection 23 Nov 2016, 18:13 UTC

The fire started on 3 November 2016 in Anderson, United States, and satellites saw it burning for 21 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 901 hectares, spread across a single county.

It is the 7th largest in Tennessee since 2016 (of 15 with a page). Number 291 in United States in 2016, of 475.

Burnt area
901ha
official perimeter (MTBS / NIFC)
Duration
≈ 21days
3 Nov 2016 – 23 Nov 2016
Counties hit
1
counties
Started on
3 Nov
2016
Heat detections
40
in a single hotspot: 37 MW
Danger at start
21
Moderate · FWI index
Average daily power
42MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 3 Nov23 Nov
23 Nov 2016

How it evolved, day by day

4 Nov 2016 · 7 MW · 2 5 Nov 2016 · 109 MW · 14 6 Nov 2016 · 28 MW · 6 7 Nov 2016 · 60 MW · 11 10 Nov 2016 · 2 MW · 1 12 Nov 2016 · 9 MW · 1 22 Nov 2016 · 43 MW · 3 23 Nov 2016 · 75 MW · 2
5 Nov 10 Nov 22 Nov

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

23°high
60km/h · peak gust
16%lowest humidity

It had gone 6 days without rain (1 mm or more) when it started. Rain came after the fire: 1.1 mm on 24 Nov.

This area had burned before

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

How big is it?

10 km
It burned the equivalent of 0.6% of the area of London (9 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each county

  1. Anderson where it started
    901 ha reached on 4 Nov
    1.0 %

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

People and buildings inside the perimeter

GHSL 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

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)
3 Nov 22.8 °C 38 % 37 km/h 1.8 mm Moderate 21
4 Nov 17.8 °C 29 % 37 km/h 0.4 mm Low 9
5 Nov 17.3 °C 28 % 20 km/h 0.0 mm Low 10
6 Nov 18.1 °C 22 % 19 km/h 0.0 mm Moderate 16
7 Nov 19.3 °C 21 % 26 km/h 0.0 mm High 22
8 Nov 17.0 °C 29 % 24 km/h 0.0 mm High 22
9 Nov 11.1 °C 46 % 42 km/h 0.5 mm High 22
10 Nov 15.2 °C 21 % 20 km/h 0.0 mm Moderate 16
11 Nov 15.1 °C 35 % 34 km/h 0.0 mm Moderate 18
12 Nov 12.2 °C 29 % 34 km/h 0.0 mm Moderate 19
13 Nov 13.8 °C 26 % 16 km/h 0.0 mm Moderate 15
14 Nov 14.4 °C 32 % 21 km/h 0.0 mm Moderate 15
15 Nov 15.0 °C 35 % 22 km/h 0.0 mm Moderate 15
16 Nov 17.1 °C 27 % 26 km/h 0.0 mm Moderate 20
17 Nov 21.5 °C 26 % 22 km/h 0.0 mm Moderate 20
18 Nov 22.0 °C 20 % 36 km/h 0.0 mm High 27
19 Nov 11.8 °C 33 % 60 km/h 2.8 mm Low 8
20 Nov 4.9 °C 23 % 40 km/h 0.0 mm Low 9
21 Nov 7.1 °C 18 % 26 km/h 0.0 mm Moderate 12
22 Nov 10.9 °C 19 % 21 km/h 0.0 mm Moderate 14
23 Nov 16.1 °C 16 % 48 km/h 0.5 mm High 29
24 Nov after 14.8 °C 60 % 38 km/h 1.1 mm Low 6

Its twins: fires that started in the same weather

It started with an FWI of 21.1, a minimum humidity of 38% and 6 days without rain. Fires in the area that started in weather like this since 2016: 11.

FWI at the start 21.1
Minimum humidity 38 %
Days without rain 6
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Jefferson Rd Fire, September 2016
531 ha 2 days FWI 21.9 Min. humidity 37 % 248 km away, in 2016

First rain (1 mm or more) after it ended: 1.2 mm on 26 Sept.

What happened to them

Fires in the area that started in similar weather: 11. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

1.1 mmfirst rain
24 Novthe day after it ended
60km/h · max. gust

It was considered over on 23 Nov, and on 24 Nov 1.1 mm fell. We do not know whether the rain or the firefighters put it out.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 27 Oct 2016
After · 30 Nov 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 · 40Every 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

Other fires nearby

All fires in United States

Frequently asked questions

How long did the Anderson fire last?
The official perimeter only gives the start date (3 November 2016). The end comes from the heat detections inside the perimeter: it burned until 23 November 2016 (21 days from 3 November 2016), the last day with detections before more than 10 days in a row without any, so it is approximate.
How much area did it burn?
The official perimeter published by United States agencies (MTBS / NIFC) is 901 hectares (9.0 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Anderson (901 ha, 1.0 %).
What was the weather like?
During the fire the temperature reached 22.8 °C, humidity dropped to 16 % and gusts hit 60 km/h. The fire danger index (FWI) reached 29, class High.
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 · Emergency number and official warnings

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

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.

How we know this
  • Perimeter: MTBS (US Geological Survey and US Forest Service), official.
  • The official perimeter has no end date: the end is the last day with VIIRS detections inside the perimeter before a gap of more than 10 days (150 days at most), so it is approximate. 40 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2015, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

How we build fire pages: methodology

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.