Mandura fire, 16 February 2026 Mandura
The fire started on 16 February 2026 in Mandura, Ethiopia, and satellites saw it burning for 22 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,235 hectares from heat detections, spread across a single municipality.
It is the 166th largest in Beneshangul Gumu since 2016 (of 701 with a page). Number 42 in Ethiopia in 2026, of 194.
Compare with…
- Burnt area
- 4,235ha
- GWIS perimeter (Copernicus)
- Duration
- 22days
- 16 Feb 2026 – 9 Mar 2026
- Municipalities hit
- 1
- districts
- Started on
- 16 Feb
- 2026
- Heat detections
- 160
- in a single hotspot: 46 MW
- Danger at start
- 39
- Very high · FWI index
- Average daily power
- 80MW
- 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
96% of the perimeter overlaps earlier fires recorded since 2016: 1,998 ha in 2016, 579 ha in 2017, 1,489 ha in 2018, 1,651 ha in 2019, 2,616 ha in 2020, 251 ha in 2021, 1,071 ha in 2022, 459 ha in 2023, 557 ha in 2024, 895 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 4,058 ha that had burned before.
- 1,998 ha Dangura fire, February 2016 89,959 ha in total; the hectares shown are those it shares with this fire
- 1,558 ha Mandura fire, February 2020 4,836 ha in total; the hectares shown are those it shares with this fire
- 1,285 ha Mandura fire, March 2019 6,098 ha in total; the hectares shown are those it shares with this fire
- 1,124 ha Mandura fire, March 2018 4,042 ha in total; the hectares shown are those it shares with this fire
- 1,019 ha Mandura fire, January 2022 2,363 ha in total; the hectares shown are those it shares with this fire
- 549 ha Mandura fire, February 2025 2,372 ha in total; the hectares shown are those it shares with this fire
- 463 ha Mandura fire, February 2024 2,054 ha in total; the hectares shown are those it shares with this fire
- 383 ha Mandura fire, February 2023 9,046 ha in total; the hectares shown are those it shares with this fire
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
-
Mandura where it started4,262 ha reached on 17 Feb3.9 %
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 were about 0.96 hectares of built-up land and about 1,500 residents (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) |
|---|---|---|---|---|---|
| 16 Feb | 32.9 °C | 21 % | 26 km/h | 0.0 mm | Very high 39 |
| 17 Feb | 35.1 °C | 22 % | 27 km/h | 0.0 mm | Very high 40 |
| 18 Feb | 36.4 °C | 16 % | 25 km/h | 0.0 mm | Very high 41 |
| 19 Feb | 34.7 °C | 20 % | 26 km/h | 0.0 mm | Very high 42 |
| 20 Feb | 34.1 °C | 22 % | 24 km/h | 0.0 mm | Very high 40 |
| 21 Feb | 32.9 °C | 21 % | 26 km/h | 0.0 mm | Very high 42 |
| 22 Feb | 34.1 °C | 23 % | 28 km/h | 0.0 mm | Very high 41 |
| 23 Feb | 34.2 °C | 17 % | 28 km/h | 0.0 mm | Very high 41 |
| 24 Feb | 30.8 °C | 20 % | 28 km/h | 0.0 mm | Very high 42 |
| 25 Feb | 31.7 °C | 23 % | 24 km/h | 0.0 mm | Very high 40 |
| 26 Feb | 31.6 °C | 28 % | 24 km/h | 0.0 mm | High 35 |
| 27 Feb | 31.9 °C | 26 % | 27 km/h | 0.0 mm | High 35 |
| 28 Feb | 31.6 °C | 23 % | 29 km/h | 0.0 mm | High 37 |
| 1 Mar | 31.5 °C | 22 % | 25 km/h | 0.0 mm | High 38 |
| 2 Mar | 31.2 °C | 20 % | 28 km/h | 0.0 mm | Very high 39 |
| 3 Mar | 30.4 °C | 18 % | 28 km/h | 0.0 mm | Very high 39 |
| 4 Mar | 31.5 °C | 16 % | 32 km/h | 0.0 mm | Very high 42 |
| 5 Mar | 31.5 °C | 16 % | 30 km/h | 0.0 mm | Very high 41 |
| 6 Mar | 31.5 °C | 17 % | 29 km/h | 0.0 mm | Very high 40 |
| 7 Mar | 32.8 °C | 17 % | 26 km/h | 0.0 mm | Very high 40 |
| 8 Mar | 33.2 °C | 16 % | 27 km/h | 0.0 mm | Very high 41 |
| 9 Mar | 33.6 °C | 16 % | 29 km/h | 0.0 mm | Very high 42 |
| 10 Mar after | 33.6 °C | 16 % | 28 km/h | 0.0 mm | Very high 44 |
| 11 Mar after | 33.3 °C | 16 % | 27 km/h | 0.0 mm | Very high 42 |
| 12 Mar after | 33.9 °C | 16 % | 27 km/h | 0.0 mm | Very high 42 |
| 13 Mar after | 36.4 °C | 17 % | 25 km/h | 0.0 mm | Very high 41 |
| 14 Mar after | 36.7 °C | 14 % | 22 km/h | 0.0 mm | Very high 42 |
| 15 Mar after | 35.4 °C | 13 % | 30 km/h | 0.0 mm | Very high 44 |
| 16 Mar after | 37.1 °C | 18 % | 39 km/h | 0.0 mm | Extreme 51 |
| 17 Mar after | 35.5 °C | 24 % | 34 km/h | 0.0 mm | Very high 44 |
| 18 Mar after | 33.5 °C | 27 % | 32 km/h | 0.5 mm | Very high 45 |
| 19 Mar after | 30.5 °C | 37 % | 34 km/h | 0.6 mm | High 33 |
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 25 February 2026 the air beside the fire reached 57 µg/m³ of PM2.5. That day averaged 37: 2.5 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 · 160Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Mandura fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 16 February 2026 to 9 March 2026 (22 days). The perimeter dates it from 21 February 2026 to 7 March 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 4,235 hectares (42.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mandura (4,262 ha, 3.9 %).
- What was the weather like?
- During the fire the temperature reached 36.4 °C, humidity dropped to 16 % and gusts hit 32 km/h. The fire danger index (FWI) reached 42, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Ethiopia (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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 7 March 2026 → 9 March 2026.
- Start date: 21 February 2026 → 16 February 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 adjusted with the VIIRS detections inside the perimeter, which said 21 February 2026 to 7 March 2026. 160 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 ADM3 (Open Data Commons Open Database License 1.0). 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.