Dangura fire, 11 January 2018 Dangura, Guba
The fire started on 11 January 2018 in Dangura, Ethiopia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,568 hectares from heat detections, spread across 2 municipalities.
It is the 444th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 54 in Ethiopia in 2018, of 96.
Compare with…
Suggestions: Guba · 2025Guba · 2019Guba · 2026Guba · 2017
- Burnt area
- 2,568ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 11 Jan 2018 – 14 Jan 2018
- Municipalities hit
- 2
- districts
- Started on
- 11 Jan
- 2018
- Heat detections
- 87
- in a single hotspot: 89 MW
- Danger at start
- 43
- Very high · FWI index
- Average daily power
- 157MW
- 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
24% of the perimeter overlaps earlier fires recorded since 2016: 526 ha in 2016, 86 ha in 2017.
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
-
Dangura where it started1,803 ha reached on 10 Jan0.4 %
-
783 ha reached on 10 Jan0.1 %
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 2020Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, 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.
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) |
|---|---|---|---|---|---|
| 11 Jan | 35.8 °C | 14 % | 26 km/h | 0.0 mm | Very high 43 |
| 12 Jan | 35.9 °C | 12 % | 30 km/h | 0.0 mm | Very high 48 |
| 13 Jan | 37.0 °C | 9 % | 34 km/h | 0.0 mm | Extreme 54 |
| 14 Jan | 36.3 °C | 8 % | 39 km/h | 0.0 mm | Extreme 60 |
| 15 Jan after | 34.3 °C | 11 % | 34 km/h | 0.0 mm | Extreme 56 |
| 16 Jan after | 34.5 °C | 14 % | 30 km/h | 0.0 mm | Extreme 51 |
| 17 Jan after | 34.4 °C | 14 % | 30 km/h | 0.0 mm | Extreme 52 |
| 18 Jan after | 34.4 °C | 13 % | 29 km/h | 0.0 mm | Extreme 50 |
| 19 Jan after | 34.0 °C | 15 % | 32 km/h | 0.0 mm | Extreme 53 |
| 20 Jan after | 34.7 °C | 15 % | 31 km/h | 0.0 mm | Extreme 51 |
| 21 Jan after | 35.5 °C | 16 % | 28 km/h | 0.0 mm | Very high 49 |
| 22 Jan after | 35.6 °C | 16 % | 36 km/h | 0.0 mm | Extreme 54 |
| 23 Jan after | 35.8 °C | 16 % | 34 km/h | 0.0 mm | Extreme 51 |
| 24 Jan after | 34.6 °C | 19 % | 30 km/h | 0.0 mm | Very high 49 |
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 · 87Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 12,439 haGuba29 December 2025 · 15 days · 19 km away
- 11,110 haGuba10 December 2019 · 15 days · 20 km away
- 12,870 haGuba21 January 2026 · 19 days · 22 km away
- 10,633 haGuba5 December 2017 · 9 days · 31 km away
- 28,159 haQuara22 November 2016 · 15 days · 33 km away
- 9,415 haDangura14 January 2020 · 9 days · 36 km away
Frequently asked questions
- How long did the Dangura fire last?
- GWIS (Copernicus) dates it between 11 January 2018 and 14 January 2018: 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,568 hectares (25.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Dangura (1,803 ha, 0.4 %); Guba (783 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 37.0 °C, humidity dropped to 8 % and gusts hit 39 km/h. The fire danger index (FWI) reached 60, 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
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. 87 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 2020, 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.