Dibat fire, February 2017 Dibat
The fire started on 8 February 2017 in Dibat, Ethiopia, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,852 hectares from heat detections, spread across a single municipality.
It is the 369th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 157 in Ethiopia in 2017, of 266.
- Burnt area
- 2,852ha
- GWIS perimeter (Copernicus)
- Duration
- 3days
- 8 Feb 2017 – 10 Feb 2017
- Municipalities hit
- 1
- districts
- Started on
- 8 Feb
- 2017
- Heat detections
- 100
- in a single hotspot: 41 MW
- Danger at start
- 35
- High · FWI index
- Energy released
- 515MW
- 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 more than two months without rain (1 mm or more) when it started.
This area had burned before
68% of the perimeter overlaps earlier fires recorded since 2016: 2,040 ha in 2016. Part of it burned more than once, so the yearly figures add up to more than the 1,939 ha that had burned before.
- 1,290 ha Dibat fire, February 2016 5,163 ha in total; the hectares shown are those it shares with this fire
- 658 ha Dibat fire, January 2016 3,313 ha in total; the hectares shown are those it shares with this fire
- 92 ha Dibat fire, March 2016 2,435 ha in total; the hectares shown are those it shares with this fire
What happened to each town
-
Dibat where it started2,870 ha reached on 7 Feb1.3 %
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) |
|---|---|---|---|---|---|
| 8 Feb | 33.9 °C | 23 % | 19 km/h | 0.0 mm | High 35 |
| 9 Feb | 32.7 °C | 24 % | 20 km/h | 0.0 mm | High 35 |
| 10 Feb | 34.4 °C | 17 % | 20 km/h | 0.0 mm | High 35 |
| 11 Feb after | 33.9 °C | 22 % | 25 km/h | 0.0 mm | Very high 40 |
| 12 Feb after | 34.2 °C | 20 % | 30 km/h | 0.0 mm | Very high 40 |
| 13 Feb after | 33.9 °C | 22 % | 20 km/h | 0.0 mm | Very high 43 |
| 14 Feb after | 28.2 °C | 35 % | 24 km/h | 0.0 mm | High 30 |
| 15 Feb after | 31.6 °C | 28 % | 27 km/h | 0.0 mm | High 30 |
| 16 Feb after | 31.6 °C | 25 % | 28 km/h | 0.0 mm | High 33 |
| 17 Feb after | 30.9 °C | 28 % | 25 km/h | 0.0 mm | High 32 |
| 18 Feb after | 28.5 °C | 32 % | 20 km/h | 0.0 mm | High 30 |
| 19 Feb after | 30.4 °C | 29 % | 26 km/h | 0.0 mm | High 30 |
| 20 Feb after | 31.6 °C | 25 % | 26 km/h | 0.0 mm | High 32 |
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 · 100Every 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 Dibat fire last?
- GWIS (Copernicus) dates it between 8 February 2017 and 10 February 2017: 3 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,852 hectares (28.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Dibat (2,870 ha, 1.3 %).
- What was the weather like?
- During the fire the temperature reached 34.4 °C, humidity dropped to 17 % and gusts hit 20 km/h. The fire danger index (FWI) reached 35, class 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
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.