Burned area
satellite only507ha
Perimeter published by MTBS (USGS/USFS).
- Source
- MTBS (USGS/USFS)
- Date
- 28 Nov 2016 – 24 Dec 2016
+− cross-check
No official record is matched to this page to compare it with.
US · United States · –
Lake Chinnabee Fire, November 2016 Clay, Cleburne
Out · last measured on 24 Dec 2016
The fire started on 28 November 2016 in Cleburne, United States, and satellites saw it burning for 27 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 507 hectares, spread across 2 counties.
It is the 6th largest in Alabama since 2016 (of 14 with a page). Number 423 in United States in 2016, of 475.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only27days
28 Nov 2016 to 24 Dec 2016: first and last day with fire on the page.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- 28 Nov 2016 – 24 Dec 2016
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only28 Nov 2016
First day with fire seen by the satellites or the perimeter.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- 28 Nov 2016
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Danger at the start
model33.0FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 42.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 28 Nov 2016, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model21.7°C · 55% RH
High of 21.7 °C and minimum humidity of 55% on 24 December 2016; gusts of 77 km/h on 28 November 2016.
- Source
- weather model at the fire’s grid cell
- Date
- 28 Nov 2016 – 24 Dec 2016
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 507 ha
- Dates
- 28 Nov 2016 – 24 Dec 2016
- Name
- Lake Chinnabee
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/lake-chinnabee-fire-2016-11?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire lake-chinnabee-fire-2016-11.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2016-11-28 | 0 | 0 | 18.6 | 9.7 | 44 | 30.4 | 77.4 | 2.6 | 33 | alto | 1 |
| 2016-11-29 | 0 | 0 | 20.9 | 10.7 | 66 | 29.5 | 73.8 | 38.4 | 0.3 | muy_bajo | 1 |
| 2016-11-30 | 0 | 0 | 21 | 9.2 | 58 | 21 | 76 | 11.5 | 0 | muy_bajo | 1 |
| 2016-12-01 | 0 | 0 | 12.9 | 2.5 | 36 | 12.1 | 32.8 | 0 | 0.2 | muy_bajo | 1 |
| 2016-12-02 | 0 | 0 | 15 | 0.1 | 31 | 10.2 | 25.6 | 0 | 1.9 | muy_bajo | 1 |
| 2016-12-03 | 0 | 0 | 11.7 | 5.2 | 38 | 12.6 | 32 | 6.1 | 4.6 | muy_bajo | 1 |
| 2016-12-04 | 0 | 0 | 8.9 | 6.5 | 81 | 19 | 50 | 30.1 | 0 | muy_bajo | 1 |
| 2016-12-05 | 0 | 0 | 12.5 | 8.5 | 93 | 20 | 41 | 34 | 0 | muy_bajo | 1 |
| 2016-12-06 | 0 | 0 | 16.2 | 9.6 | 83 | 20.4 | 49 | 13.6 | 0 | muy_bajo | 1 |
| 2016-12-07 | 0 | 0 | 11.9 | 6.8 | 66 | 11.3 | 29.2 | 0 | 0.1 | muy_bajo | 1 |
| 2016-12-08 | 0 | 0 | 7.8 | 1.4 | 38 | 17.7 | 42.8 | 0 | 0.5 | muy_bajo | 1 |
| 2016-12-09 | 0 | 0 | 5.5 | -3.3 | 35 | 14.2 | 33.5 | 0 | 0.7 | muy_bajo | 1 |
| 2016-12-10 | 0 | 0 | 9.3 | -4.3 | 18 | 8.9 | 23 | 0 | 2 | muy_bajo | 1 |
| 2016-12-11 | 0 | 0 | 14.4 | -1.7 | 44 | 17.2 | 35.6 | 0 | 3.4 | muy_bajo | 1 |
| 2016-12-12 | 0 | 0 | 16.1 | 9.7 | 68 | 18.7 | 42.1 | 4.6 | 0.1 | muy_bajo | 1 |
| 2016-12-13 | 0 | 0 | 16.6 | 11.1 | 85 | 16.7 | 38.9 | 7.8 | 0.1 | muy_bajo | 1 |
| 2016-12-14 | 0 | 0 | 13.3 | 5.1 | 49 | 13 | 29.9 | 0.2 | 0.1 | muy_bajo | 1 |
| 2016-12-15 | 0 | 0 | 5.9 | -1.8 | 28 | 14.9 | 38.9 | 0 | 0.4 | muy_bajo | 1 |
| 2016-12-16 | 0 | 0 | 10.4 | -2.8 | 28 | 21.9 | 45.4 | 0 | 1.2 | muy_bajo | 1 |
| 2016-12-17 | 0 | 0 | 18.9 | 9.4 | 62 | 22.3 | 51.1 | 0.9 | 2.3 | muy_bajo | 1 |
| 2016-12-18 | 0 | 0 | 20.4 | -0.2 | 82 | 24.3 | 71.3 | 10.7 | 0 | muy_bajo | 1 |
| 2016-12-19 | 0 | 0 | 5.9 | -2 | 63 | 15.5 | 36 | 0 | 0 | muy_bajo | 1 |
| 2016-12-20 | 0 | 0 | 8.5 | 2.6 | 71 | 8.2 | 17.3 | 0 | 0 | muy_bajo | 1 |
| 2016-12-21 | 0 | 0 | 15.2 | 0 | 32 | 10.5 | 17.6 | 0 | 0.2 | muy_bajo | 1 |
| 2016-12-22 | 0 | 0 | 17.3 | 7.2 | 39 | 11.3 | 28.4 | 0 | 0.7 | muy_bajo | 1 |
| 2016-12-23 | 0 | 0 | 18 | 2.9 | 34 | 16 | 38.5 | 0 | 4.1 | muy_bajo | 1 |
| 2016-12-24 | 0 | 0 | 21.7 | 10.6 | 55 | 15.7 | 33.5 | 0 | 3.5 | muy_bajo | 1 |
| 2016-12-25 | 0 | 0 | 24.2 | 10.8 | 55 | 15.5 | 34.9 | 0 | 4.5 | muy_bajo | 0 |
| 2016-12-26 | 0 | 0 | 20.1 | 15.8 | 74 | 15.8 | 36.7 | 0.5 | 3.8 | muy_bajo | 0 |
| 2016-12-27 | 0 | 0 | 20.2 | 12.9 | 84 | 15.5 | 36 | 3.9 | 2.3 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: MTBS (USGS/USFS), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
We have the official perimeter (MTBS / NIFC) for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by county is there.
- Burnt area
- 507ha
- official perimeter (MTBS / NIFC)
- Duration
- 27days
- 28 Nov 2016 – 24 Dec 2016
- Counties hit
- 2
- counties
- Started on
- 28 Nov
- 2016
- Danger at start
- 33
- High · FWI index
Where it burned
The weather it burned in
22°high
77km/h · peak gust
18%lowest humidity
It had gone 42 days without rain (1 mm or more) when it started. Rain came after the fire: 3.9 mm on 27 Dec.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each county
-
258 ha0.2 %
-
Cleburne where it started250 ha0.2 %
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 2015Built-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)
Started with Strong wind: 27 % of the area in United States
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 28 Nov | 18.6 °C | 44 % | 77 km/h | 2.6 mm | High 33 |
| 29 Nov | 20.9 °C | 66 % | 74 km/h | 38.4 mm | Very low 0 |
| 30 Nov | 21.0 °C | 58 % | 76 km/h | 11.5 mm | Very low 0 |
| 1 Dec | 12.9 °C | 36 % | 33 km/h | 0.0 mm | Very low 0 |
| 2 Dec | 15.0 °C | 31 % | 26 km/h | 0.0 mm | Very low 2 |
| 3 Dec | 11.7 °C | 38 % | 32 km/h | 6.1 mm | Very low 5 |
| 4 Dec | 8.9 °C | 81 % | 50 km/h | 30.1 mm | Very low 0 |
| 5 Dec | 12.5 °C | 93 % | 41 km/h | 34.0 mm | Very low 0 |
| 6 Dec | 16.2 °C | 83 % | 49 km/h | 13.6 mm | Very low 0 |
| 7 Dec | 11.9 °C | 66 % | 29 km/h | 0.0 mm | Very low 0 |
| 8 Dec | 7.8 °C | 38 % | 43 km/h | 0.0 mm | Very low 0 |
| 9 Dec | 5.5 °C | 35 % | 34 km/h | 0.0 mm | Very low 1 |
| 10 Dec | 9.3 °C | 18 % | 23 km/h | 0.0 mm | Very low 2 |
| 11 Dec | 14.4 °C | 44 % | 36 km/h | 0.0 mm | Very low 3 |
| 12 Dec | 16.1 °C | 68 % | 42 km/h | 4.6 mm | Very low 0 |
| 13 Dec | 16.6 °C | 85 % | 39 km/h | 7.8 mm | Very low 0 |
| 14 Dec | 13.3 °C | 49 % | 30 km/h | 0.2 mm | Very low 0 |
| 15 Dec | 5.9 °C | 28 % | 39 km/h | 0.0 mm | Very low 0 |
| 16 Dec | 10.4 °C | 28 % | 45 km/h | 0.0 mm | Very low 1 |
| 17 Dec | 18.9 °C | 62 % | 51 km/h | 0.9 mm | Very low 2 |
| 18 Dec | 20.4 °C | 82 % | 71 km/h | 10.7 mm | Very low 0 |
| 19 Dec | 5.9 °C | 63 % | 36 km/h | 0.0 mm | Very low 0 |
| 20 Dec | 8.5 °C | 71 % | 17 km/h | 0.0 mm | Very low 0 |
| 21 Dec | 15.2 °C | 32 % | 18 km/h | 0.0 mm | Very low 0 |
| 22 Dec | 17.3 °C | 39 % | 28 km/h | 0.0 mm | Very low 1 |
| 23 Dec | 18.0 °C | 34 % | 38 km/h | 0.0 mm | Very low 4 |
| 24 Dec | 21.7 °C | 55 % | 34 km/h | 0.0 mm | Very low 4 |
| 25 Dec after | 24.2 °C | 55 % | 35 km/h | 0.0 mm | Very low 4 |
| 26 Dec after | 20.1 °C | 74 % | 37 km/h | 0.5 mm | Very low 4 |
| 27 Dec after | 20.2 °C | 84 % | 36 km/h | 3.9 mm | Very low 2 |
Its twins: fires that started in the same weather
It started with an FWI of 33.0, a minimum humidity of 44% and 42 days without rain. Fires in the area that started in weather like this since 2016: 1.
FWI at the start
33.0
Minimum humidity
44 %
Days without rain
42
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Lake Chinnabee Fire, November 2016
507 ha
27 days
FWI 33.0
Min. humidity 44 %
Half Way Fire, November 2016
421 ha
5 days
FWI 35.8
Min. humidity 33 %
40 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
Fires in the area that started in similar weather: 1. 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
3.9 mmfirst rain
27 Dec3 days after it ended
77km/h · max. gust
It was considered over on 24 Dec, and on 27 Dec 3.9 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.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 21 Nov 2016
After · 31 Dec 2016
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
Other fires nearby
Frequently asked questions
- How long did the Lake Chinnabee Fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 28 November 2016 to 24 December 2016 (27 days). The perimeter dates it from 28 November 2016 to 28 November 2016.
- How much area did it burn?
- The official perimeter published by United States agencies (MTBS / NIFC) is 507 hectares (5.1 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire entered 2 counties: Clay (258 ha, 0.2 %); Cleburne (250 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 21.7 °C, humidity dropped to 18 % and gusts hit 77 km/h. The fire danger index (FWI) reached 33, 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
- NIFC · National Interagency Fire Center ↗
- InciWeb · Incident Information System ↗
- MTBS · Monitoring Trends in Burn Severity ↗
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
RSS Changes to this page With cross-checks and a citable version
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
How we know this
- Perimeter: MTBS (US Geological Survey and US Forest Service), official.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 28 November 2016 to 28 November 2016. No 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.
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.