Skip to content
worldfires
ET · Ethiopia · →

Guba fire, January 2017 Guba, Dangura

Out · last detection 13 Jan 2017, 22:57 UTC

The fire started on 10 January 2017 in Guba, Ethiopia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,032 hectares from heat detections, spread across 2 municipalities.

It is the 682th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 259 in Ethiopia in 2017, of 266.

Compare with…
Burnt area
2,032ha
GWIS perimeter (Copernicus)
Duration
4days
10 Jan 2017 – 13 Jan 2017
Municipalities hit
2
districts
Started on
10 Jan
2017
Heat detections
78
in a single hotspot: 115 MW
Average daily power
181MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 10 Jan13 Jan
13 Jan 2017

How it evolved, day by day

10 Jan 2017 · 22 MW · 4 11 Jan 2017 · 81 MW · 10 12 Jan 2017 · 270 MW · 22 13 Jan 2017 · 352 MW · 29
10 Jan 11 Jan 12 Jan 13 Jan

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

This area had burned before

25% of the perimeter overlaps earlier fires recorded since 2016: 501 ha in 2016.

How big is it?

10 km
It burned the equivalent of 1.3% of the area of London (20 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Guba where it started
    1,600 ha reached on 5 Jan
    0.2 %
  2. 446 ha reached on 6 Jan
    0.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 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 3 Jan 2017
After · 20 Jan 2017

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 · 78Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Ethiopia ›

Frequently asked questions

How long did the Guba fire last?
GWIS (Copernicus) dates it between 10 January 2017 and 13 January 2017: 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,032 hectares (20.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Guba (1,600 ha, 0.2 %); Dangura (446 ha, 0.1 %).
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.

RSS Changes to this page

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

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. 78 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2015, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

How we build fire pages: methodology ›

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.