Batha Est fire, 6 December 2016 Batha Est, Biltine
The fire started on 6 December 2016 in Batha Est, Chad, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,829 hectares from heat detections, spread across 2 municipalities.
It is the 81th largest in Batha since 2016 (of 135 with a page). Number 101 in Chad in 2016, of 220.
The power measured by the satellite is low (2.8 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 2,829ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 6 Dec 2016 – 7 Dec 2016
- Municipalities hit
- 2
- departments
- Started on
- 6 Dec
- 2016
- Heat detections
- 109
- in a single hotspot: 3 MW
- Danger at start
- 67
- Extreme · FWI index
- Average daily power
- 134MW
- detected power per day, on average
Where it burned
How it evolved, day by day
7 Dec 2016 · 134 MW · 109
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone more than two months 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.
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 town
-
Batha Est where it started2,179 ha reached on 7 Dec0.1 %
-
675 ha reached on 7 Dec0.0 %
Burnt area inside each municipality, from crossing the GWIS 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 2015Inside 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) |
|---|---|---|---|---|---|
| 6 Dec | 35.3 °C | 11 % | 39 km/h | 0.0 mm | Extreme 67 |
| 7 Dec | 36.6 °C | 10 % | 34 km/h | 0.0 mm | Extreme 64 |
| 8 Dec after | 35.6 °C | 9 % | 34 km/h | 0.0 mm | Extreme 66 |
| 9 Dec after | 33.4 °C | 9 % | 40 km/h | 0.0 mm | Extreme 69 |
| 10 Dec after | 31.7 °C | 12 % | 42 km/h | 0.0 mm | Extreme 69 |
| 11 Dec after | 32.4 °C | 9 % | 40 km/h | 0.0 mm | Extreme 68 |
| 12 Dec after | 32.3 °C | 8 % | 32 km/h | 0.0 mm | Extreme 64 |
| 13 Dec after | 32.9 °C | 6 % | 40 km/h | 0.0 mm | Very extreme 70 |
| 14 Dec after | 30.4 °C | 10 % | 52 km/h | 0.0 mm | Very extreme 81 |
| 15 Dec after | 31.1 °C | 11 % | 45 km/h | 0.0 mm | Very extreme 73 |
| 16 Dec after | 31.6 °C | 13 % | 34 km/h | 0.0 mm | Extreme 61 |
| 17 Dec after | 33.7 °C | 6 % | 35 km/h | 0.0 mm | Extreme 68 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · 109Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 9,220 haBatha Est24 April 2019 · 2 days · 11 km away
- 13,654 haBatha EstApril 2025 · 1 day · 22 km away
- 10,025 haBiltine8 November 2025 · 2 days · 26 km away
- 9,215 haBatha Est22 January 2026 · 2 days · 26 km away
- 6,850 haBatha Est31 December 2025 · 2 days · 26 km away
- 14,646 haBiltine8 November 2025 · 3 days · 33 km away
Frequently asked questions
- How long did the Batha Est fire last?
- GWIS (Copernicus) dates it between 6 December 2016 and 7 December 2016: 2 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 2,829 hectares (28.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Batha Est (2,179 ha, 0.1 %); Biltine (675 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 36.6 °C, humidity dropped to 10 % and gusts hit 39 km/h. The fire danger index (FWI) reached 67, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Chad (geoBoundaries). 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.
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.
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: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 109 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 comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.