Skip to content
worldfires
ET · Ethiopia · →

Dima fire, 23 January 2016 Dima, Gog

Out · last detection 26 Jan 2016, 23:19 UTC

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

It is the 144th largest in Gambela since 2016 (of 611 with a page). Number 67 in Ethiopia in 2016, of 309.

Burnt area
4,702ha
GWIS perimeter (Copernicus)
Duration
4days
23 Jan 2016 – 26 Jan 2016
Municipalities hit
2
districts
Started on
23 Jan
2016
Heat detections
128
in a single hotspot: 234 MW
Danger at start
32
High · FWI index
Energy released
1.3GW
sum of detected power

Where it burned

26 Jan 2016
HOTSPOTS BY DAY 23 Jan26 Jan

How it evolved, day by day

23242526

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

The weather it burned in

38°high
22km/h · peak gust
22%lowest humidity

It had gone 43 days without rain (1 mm or more) when it started.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Dima where it started
    4,645 ha reached on 22 Jan
    0.6 %
  2. Gog
    92 ha reached on 23 Jan
    0.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.

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)
23 Jan 37.9 °C 22 % 18 km/h 0.0 mm High 32
24 Jan 36.4 °C 25 % 22 km/h 0.0 mm High 34
25 Jan 37.0 °C 22 % 17 km/h 0.0 mm High 33
26 Jan 36.4 °C 22 % 18 km/h 0.0 mm High 31
27 Jan after 35.7 °C 20 % 26 km/h 0.0 mm High 36
28 Jan after 34.6 °C 18 % 27 km/h 0.0 mm High 35
29 Jan after 34.9 °C 16 % 22 km/h 0.0 mm High 36
30 Jan after 36.1 °C 17 % 25 km/h 0.0 mm High 36
31 Jan after 35.9 °C 25 % 16 km/h 0.0 mm High 36
1 Feb after 36.8 °C 25 % 25 km/h 0.0 mm High 36
2 Feb after 34.9 °C 30 % 26 km/h 0.2 mm High 35
3 Feb after 35.5 °C 29 % 20 km/h 0.0 mm High 35
4 Feb after 37.5 °C 23 % 21 km/h 0.0 mm High 35
5 Feb after 37.5 °C 21 % 22 km/h 0.0 mm Very high 39

Before and after, from space

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

Before · 16 Jan 2016
After · 2 Feb 2016

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 · 128Every 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 Dima fire last?
GWIS (Copernicus) dates it between 23 January 2016 and 26 January 2016: 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 4,702 hectares (47.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Dima (4,645 ha, 0.6 %); Gog (92 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 37.9 °C, humidity dropped to 22 % and gusts hit 22 km/h. The fire danger index (FWI) reached 34, class 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

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.