Dibat fire, January 2026 Dibat
The fire started on 14 January 2026 in Dibat, Ethiopia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,131 hectares from heat detections, spread across a single municipality.
It is the 624th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 161 in Ethiopia in 2026, of 190.
- Burnt area
- 2,131ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 14 Jan 2026 – 17 Jan 2026
- Municipalities hit
- 1
- districts
- Started on
- 14 Jan
- 2026
- Heat detections
- 74
- in a single hotspot: 40 MW
- Energy released
- 242MW
- 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.
This area had burned before
23% of the perimeter overlaps earlier fires recorded since 2016: 4 ha in 2016, 59 ha in 2020, 63 ha in 2021, 64 ha in 2022, 398 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 492 ha that had burned before.
What happened to each town
-
Dibat where it started2,142 ha reached on 10 Jan1.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.
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 18 January 2026 the air beside the fire reached 40 µg/m³ of PM2.5. That day averaged 27: 1.8 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 · 74Every 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 14 January 2026 and 17 January 2026: 4 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,131 hectares (21.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Dibat (2,142 ha, 1.0 %).
- 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.