Skip to content
worldfires
ET · Ethiopia · →

Guba fire, 29 December 2017 Dangura, Guba

Out · last detection 31 Dec 2017, 22:57 UTC

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

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

Burnt area
2,752ha
GWIS perimeter (Copernicus)
Duration
3days
29 Dec 2017 – 31 Dec 2017
Municipalities hit
2
districts
Started on
29 Dec
2017
Heat detections
64
in a single hotspot: 31 MW
Danger at start
52
Extreme · FWI index
Average daily power
118MW
detected power per day, on average

Where it burned

31 Dec 2017
HOTSPOTS BY DAY 29 Dec31 Dec

How it evolved, day by day

29 Dec 2017 · 82 MW · 12 30 Dec 2017 · 198 MW · 30 31 Dec 2017 · 73 MW · 18
29 Dec 30 Dec 31 Dec

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

The weather it burned in

33°high
35km/h · peak gust
11%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

75% of the perimeter overlaps earlier fires recorded since 2016: 2,128 ha in 2016.

What happened to each town

  1. 1,677 ha reached on 30 Dec
    0.3 %
  2. Guba where it started
    1,095 ha reached on 24 Dec
    0.2 %

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)
29 Dec 32.6 °C 11 % 35 km/h 0.0 mm Extreme 52
30 Dec 32.2 °C 12 % 34 km/h 0.0 mm Extreme 51
31 Dec 31.3 °C 16 % 33 km/h 0.0 mm Very high 48
1 Jan after 30.4 °C 19 % 32 km/h 0.0 mm Very high 46
2 Jan after 29.3 °C 24 % 32 km/h 0.0 mm Very high 42
3 Jan after 30.4 °C 24 % 31 km/h 0.0 mm Very high 41
4 Jan after 29.4 °C 21 % 36 km/h 0.0 mm Very high 43
5 Jan after 30.2 °C 20 % 32 km/h 0.0 mm Very high 42
6 Jan after 29.5 °C 21 % 36 km/h 0.0 mm Very high 44
7 Jan after 30.3 °C 16 % 36 km/h 0.0 mm Very high 44
8 Jan after 31.1 °C 15 % 34 km/h 0.0 mm Very high 44
9 Jan after 30.7 °C 16 % 34 km/h 0.0 mm Very high 44
10 Jan after 31.6 °C 15 % 33 km/h 0.0 mm Very high 44

Before and after, from space

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

Before · 22 Dec 2017
After · 7 Jan 2018

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 · 64Every 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 29 December 2017 and 31 December 2017: 3 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,752 hectares (27.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Dangura (1,677 ha, 0.3 %); Guba (1,095 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 32.6 °C, humidity dropped to 11 % and gusts hit 35 km/h. The fire danger index (FWI) reached 52, 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

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.

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.