Dibat fire, 9 February 2024 Dibat, Guangua
The fire started on 9 February 2024 in Dibat, Ethiopia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,600 hectares from heat detections, spread across 2 municipalities.
It is the 222th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 22 in Ethiopia in 2024, of 87.
- Burnt area
- 3,600ha
- GWIS perimeter (Copernicus)
- Duration
- 5days
- 9 Feb 2024 – 13 Feb 2024
- Municipalities hit
- 2
- districts
- Started on
- 9 Feb
- 2024
- Heat detections
- 127
- in a single hotspot: 42 MW
- Danger at start
- 40
- Very high · FWI index
- Energy released
- 1.1GW
- 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
84% of the perimeter overlaps earlier fires recorded since 2016: 1,823 ha in 2016, 2,013 ha in 2017, 809 ha in 2018, 573 ha in 2019, 1,619 ha in 2020, 951 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 3,036 ha that had burned before.
- 2,013 ha Dibat fire, March 2017 4,986 ha in total; the hectares shown are those it shares with this fire
- 1,619 ha Dibat fire, March 2020 4,902 ha in total; the hectares shown are those it shares with this fire
- 686 ha Dibat fire, March 2016 6,018 ha in total; the hectares shown are those it shares with this fire
- 5 ha Dibat fire, March 2019 4,965 ha in total; the hectares shown are those it shares with this fire
What happened to each town
-
Dibat where it started2,583 ha reached on 9 Feb1.2 %
-
1,041 ha reached on 9 Feb0.4 %
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) |
|---|---|---|---|---|---|
| 9 Feb | 31.9 °C | 19 % | 30 km/h | 0.0 mm | Very high 40 |
| 10 Feb | 32.4 °C | 16 % | 31 km/h | 0.0 mm | Very high 40 |
| 11 Feb | 33.0 °C | 14 % | 29 km/h | 0.0 mm | Very high 43 |
| 12 Feb | 33.3 °C | 12 % | 31 km/h | 0.0 mm | Very high 45 |
| 13 Feb | 32.8 °C | 12 % | 31 km/h | 0.0 mm | Very high 45 |
| 14 Feb after | 33.2 °C | 10 % | 25 km/h | 0.0 mm | Very high 43 |
| 15 Feb after | 33.4 °C | 9 % | 24 km/h | 0.0 mm | Very high 42 |
| 16 Feb after | 32.9 °C | 9 % | 30 km/h | 0.0 mm | Very high 48 |
| 17 Feb after | 33.1 °C | 11 % | 34 km/h | 0.0 mm | Very high 50 |
| 18 Feb after | 32.2 °C | 15 % | 33 km/h | 0.0 mm | Very high 48 |
| 19 Feb after | 33.3 °C | 17 % | 29 km/h | 0.0 mm | Very high 46 |
| 20 Feb after | 33.2 °C | 16 % | 24 km/h | 0.0 mm | Very high 43 |
| 21 Feb after | 33.0 °C | 17 % | 26 km/h | 0.0 mm | Very high 44 |
| 22 Feb after | 34.8 °C | 11 % | 38 km/h | 0.0 mm | Extreme 50 |
| 23 Feb after | 34.5 °C | 10 % | 35 km/h | 0.0 mm | Very high 50 |
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 12 February 2024 the air beside the fire reached 25 µg/m³ of PM2.5. That day averaged 18: 1.2 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 · 127Every 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 9 February 2024 and 13 February 2024: 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 3,600 hectares (36.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Dibat (2,583 ha, 1.2 %); Guangua (1,041 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 33.3 °C, humidity dropped to 12 % and gusts hit 31 km/h. The fire danger index (FWI) reached 45, 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
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.