Mandura fire, 23 February 2017 Bulen, Mandura, Dibat
The fire started on 23 February 2017 in Mandura, Ethiopia, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 33,850 hectares from heat detections, spread across 3 municipalities.
It is the 10th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 2 in Ethiopia in 2017, of 266.
- Burnt area
- 33,850ha
- GWIS perimeter (Copernicus)
- Duration
- 7days
- 23 Feb 2017 – 1 Mar 2017
- Municipalities hit
- 3
- districts
- Started on
- 23 Feb
- 2017
- Heat detections
- 1,178
- in a single hotspot: 131 MW
- Danger at start
- 35
- High · FWI index
- Energy released
- 13.5GW
- sum of detected power
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 5 days without rain (1 mm or more) when it started.
This area had burned before
58% of the perimeter overlaps earlier fires recorded since 2016: 19,575 ha in 2016.
- 10,631 ha Dangura fire, February 2016 89,959 ha in total; the hectares shown are those it shares with this fire
- 8,788 ha Bulen fire, February 2016 11,694 ha in total; the hectares shown are those it shares with this fire
- 89 ha Bulen fire, January 2016 5,157 ha in total; the hectares shown are those it shares with this fire
- 18 ha Bulen fire, January 2016 4,299 ha in total; the hectares shown are those it shares with this fire
What happened to each town
-
29,350 ha reached on 24 Feb9.7 %
-
Mandura where it started2,532 ha reached on 22 Feb2.3 %
-
2,205 ha reached on 24 Feb1.0 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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) |
|---|---|---|---|---|---|
| 22 Feb | 33.3 °C | 20 % | 29 km/h | 0.1 mm | High 35 |
| 23 Feb | 33.7 °C | 19 % | 30 km/h | 0.0 mm | Very high 39 |
| 24 Feb | 34.3 °C | 14 % | 37 km/h | 0.0 mm | Very high 44 |
| 25 Feb | 34.1 °C | 16 % | 38 km/h | 0.0 mm | Very high 44 |
| 26 Feb | 34.3 °C | 15 % | 31 km/h | 0.0 mm | Very high 43 |
| 27 Feb | 36.6 °C | 8 % | 27 km/h | 0.0 mm | Very high 49 |
| 28 Feb | 35.9 °C | 5 % | 26 km/h | 0.0 mm | Very high 48 |
| 1 Mar | 35.4 °C | 14 % | 20 km/h | 0.0 mm | Very high 45 |
| 2 Mar after | 37.9 °C | 7 % | 32 km/h | 0.0 mm | Extreme 54 |
| 3 Mar after | 36.9 °C | 4 % | 33 km/h | 0.0 mm | Extreme 58 |
| 4 Mar after | 35.6 °C | 10 % | 29 km/h | 0.0 mm | Extreme 52 |
| 5 Mar after | 36.2 °C | 12 % | 31 km/h | 0.0 mm | Extreme 52 |
| 6 Mar after | 36.2 °C | 13 % | 32 km/h | 0.0 mm | Extreme 51 |
| 7 Mar after | 35.0 °C | 18 % | 23 km/h | 0.0 mm | Very high 43 |
| 8 Mar after | 36.6 °C | 16 % | 26 km/h | 0.0 mm | Very high 45 |
| 9 Mar after | 35.2 °C | 18 % | 27 km/h | 0.0 mm | Very high 44 |
| 10 Mar after | 36.9 °C | 16 % | 31 km/h | 0.0 mm | Very high 46 |
| 11 Mar after | 36.7 °C | 18 % | 28 km/h | 0.0 mm | Very high 45 |
| 12 Mar after | 37.9 °C | 14 % | 35 km/h | 0.0 mm | Very high 50 |
| 13 Mar after | 37.0 °C | 14 % | 20 km/h | 0.0 mm | Very high 45 |
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 · 1,178Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 39,575 haDangura24 February 2025 · 15 days · 12 km away
- 92,220 haDangura17 February 2026 · 26 days · 21 km away
- 42,975 haManduraMarch 2021 · 9 days · 24 km away
- 125,093 haDangura29 January 2020 · 52 days · 25 km away
- 55,315 haDanguraMarch 2018 · 6 days · 25 km away
- 39,054 haDangura21 February 2017 · 10 days · 26 km away
Frequently asked questions
- How long did the Mandura fire last?
- GWIS (Copernicus) dates it between 23 February 2017 and 1 March 2017: 7 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 33,850 hectares (338.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Bulen (29,350 ha, 9.7 %); Mandura (2,532 ha, 2.3 %); Dibat (2,205 ha, 1.0 %).
- What was the weather like?
- During the fire the temperature reached 37.9 °C, humidity dropped to 4 % and gusts hit 38 km/h. The fire danger index (FWI) reached 58, class Extreme.
- 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
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
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.