Dibat fire, 19 February 2025 Dibat
The fire started on 19 February 2025 in Dibat, Ethiopia, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,711 hectares from heat detections, spread across a single municipality.
It is the 210th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 35 in Ethiopia in 2025, of 127.
The power measured by the satellite is low (25.6 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
Suggestions: Dibat · 2016Dibat · 2021Dibat · 2022Dibat · 2024
- Burnt area
- 3,711ha
- GWIS perimeter (Copernicus)
- Duration
- 8days
- 19 Feb 2025 – 26 Feb 2025
- Municipalities hit
- 1
- districts
- Started on
- 19 Feb
- 2025
- Heat detections
- 184
- in a single hotspot: 26 MW
- Danger at start
- 38
- High · FWI index
- Average daily power
- 111MW
- 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
99% of the perimeter overlaps earlier fires recorded since 2016: 1,792 ha in 2016, 341 ha in 2017, 867 ha in 2019, 680 ha in 2020, 2,478 ha in 2021, 1,199 ha in 2022, 1,416 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 3,679 ha that had burned before.
- 1,792 ha Dibat fire, February 2016 8,143 ha in total; the hectares shown are those it shares with this fire
- 1,437 ha Dibat fire, February 2021 2,883 ha in total; the hectares shown are those it shares with this fire
- 1,199 ha Dibat fire, February 2022 2,078 ha in total; the hectares shown are those it shares with this fire
- 897 ha Dibat fire, February 2024 2,424 ha in total; the hectares shown are those it shares with this fire
- 148 ha Dibat fire, January 2019 3,299 ha in total; the hectares shown are those it shares with this fire
- 48 ha Dibat fire, March 2017 3,617 ha in total; the hectares shown are those it shares with this fire
- 31 ha Dibat fire, January 2019 2,135 ha in total; the hectares shown are those it shares with this fire
- 3 ha Dibat fire, January 2017 3,386 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
-
Dibat where it started3,732 ha reached on 18 Feb1.7 %
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) |
|---|---|---|---|---|---|
| 19 Feb | 35.4 °C | 19 % | 19 km/h | 0.0 mm | High 38 |
| 20 Feb | 33.7 °C | 17 % | 29 km/h | 0.0 mm | Very high 40 |
| 21 Feb | 35.3 °C | 13 % | 23 km/h | 0.0 mm | Very high 40 |
| 22 Feb | 35.8 °C | 12 % | 29 km/h | 0.0 mm | Very high 43 |
| 23 Feb | 37.1 °C | 11 % | 38 km/h | 0.0 mm | Very high 47 |
| 24 Feb | 36.5 °C | 11 % | 32 km/h | 0.0 mm | Very high 45 |
| 25 Feb | 36.5 °C | 11 % | 32 km/h | 0.0 mm | Very high 44 |
| 26 Feb | 37.3 °C | 15 % | 32 km/h | 0.0 mm | Very high 45 |
| 27 Feb after | 36.6 °C | 16 % | 27 km/h | 0.0 mm | Very high 45 |
| 28 Feb after | 37.3 °C | 18 % | 25 km/h | 0.0 mm | Very high 43 |
| 1 Mar after | 37.3 °C | 17 % | 30 km/h | 0.0 mm | Very high 46 |
| 2 Mar after | 36.7 °C | 14 % | 24 km/h | 0.0 mm | Very high 43 |
| 3 Mar after | 37.1 °C | 19 % | 22 km/h | 0.0 mm | Very high 43 |
| 4 Mar after | 35.8 °C | 14 % | 27 km/h | 0.0 mm | Very high 46 |
| 5 Mar after | 36.2 °C | 17 % | 27 km/h | 0.0 mm | Very high 43 |
| 6 Mar after | 36.9 °C | 15 % | 26 km/h | 0.0 mm | Very high 44 |
| 7 Mar after | 36.9 °C | 13 % | 32 km/h | 0.0 mm | Very high 48 |
| 8 Mar after | 36.9 °C | 13 % | 30 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 27 February 2025 the air beside the fire reached 97 µg/m³ of PM2.5. That day averaged 52: 3.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 · 184Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 8,143 haDibat29 February 2016 · 8 days · 6 km away
- 7,791 haDibat23 January 2020 · 15 days · 17 km away
- 7,826 haDibat28 February 2020 · 8 days · 22 km away
- 8,828 haYaso5 January 2016 · 16 days · 25 km away
- 11,905 haYaso7 January 2017 · 8 days · 29 km away
- 8,720 haBulen10 January 2019 · 14 days · 32 km away
Frequently asked questions
- How long did the Dibat fire last?
- GWIS (Copernicus) dates it between 19 February 2025 and 26 February 2025: 8 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,711 hectares (37.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Dibat (3,732 ha, 1.7 %).
- What was the weather like?
- During the fire the temperature reached 37.3 °C, humidity dropped to 11 % and gusts hit 38 km/h. The fire danger index (FWI) reached 47, 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 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. 184 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.