Batha Est fire, 17 February 2026 Batha Est
The fire started on 17 February 2026 in Batha Est, Chad, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,153 hectares from heat detections, spread across a single municipality.
It is the 20th largest in Batha since 2016 (of 135 with a page). Number 21 in Chad in 2026, of 201.
Compare with…
- Burnt area
- 7,153ha
- GWIS perimeter (Copernicus)
- Duration
- 5days
- 17 Feb 2026 – 21 Feb 2026
- Municipalities hit
- 1
- departments
- Started on
- 17 Feb
- 2026
- Heat detections
- 170
- in a single hotspot: 65 MW
- Danger at start
- 71
- Very extreme · FWI index
- Average daily power
- 208MW
- detected power per day, on average
Where it burned
How it evolved, day by day
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
52% of the perimeter overlaps earlier fires recorded since 2016: 1,671 ha in 2016, 378 ha in 2018, 2,546 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 3,702 ha that had burned before.
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 started7,187 ha reached on 17 Feb0.2 %
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 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
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) |
|---|---|---|---|---|---|
| 17 Feb | 36.1 °C | 10 % | 40 km/h | 0.0 mm | Very extreme 71 |
| 18 Feb | 36.1 °C | 10 % | 40 km/h | 0.0 mm | Extreme 70 |
| 19 Feb | 36.0 °C | 8 % | 36 km/h | 0.0 mm | Extreme 68 |
| 20 Feb | 37.6 °C | 8 % | 30 km/h | 0.0 mm | Extreme 65 |
| 21 Feb | 37.7 °C | 8 % | 29 km/h | 0.0 mm | Extreme 65 |
| 22 Feb after | 35.9 °C | 6 % | 39 km/h | 0.0 mm | Very extreme 73 |
| 23 Feb after | 33.0 °C | 6 % | 44 km/h | 0.0 mm | Very extreme 74 |
| 24 Feb after | 31.7 °C | 10 % | 41 km/h | 0.0 mm | Extreme 70 |
| 25 Feb after | 32.7 °C | 7 % | 34 km/h | 0.0 mm | Extreme 66 |
| 26 Feb after | 31.6 °C | 7 % | 33 km/h | 0.0 mm | Extreme 64 |
| 27 Feb after | 30.7 °C | 8 % | 31 km/h | 0.0 mm | Extreme 61 |
| 28 Feb after | 32.1 °C | 8 % | 40 km/h | 0.0 mm | Extreme 69 |
| 1 Mar after | 32.0 °C | 11 % | 37 km/h | 0.0 mm | Extreme 63 |
| 2 Mar after | 32.8 °C | 6 % | 34 km/h | 0.0 mm | Extreme 65 |
| 3 Mar after | 33.1 °C | 7 % | 39 km/h | 0.0 mm | Extreme 70 |
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.
The smoke
CAMS · CopernicusOn 17 February 2026 the air beside the fire reached 176 µg/m³ of PM2.5. That day averaged 105: 7.0 times the WHO daily guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 170Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 3,909 haBatha EstFebruary 2021 · 2 days · 7 km away
- 4,040 haBatha Est17 February 2026 · 7 days · 9 km away
- 3,125 haBatha EstOctober 2016 · 1 day · 11 km away
- 10,566 haBatha EstMarch 2021 · 3 days · 12 km away
- 2,621 haBatha EstJanuary 2021 · 1 day · 19 km away
- 6,186 haBatha Est23 October 2020 · 1 day · 37 km away
Frequently asked questions
- How long did the Batha Est fire last?
- GWIS (Copernicus) dates it between 17 February 2026 and 21 February 2026: 5 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 7,153 hectares (71.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Batha Est (7,187 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 37.7 °C, humidity dropped to 8 % and gusts hit 40 km/h. The fire danger index (FWI) reached 71, class Very 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. 170 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 2025, 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.