Skip to content
worldfires
ET · Ethiopia · →

Dibat fire, 3 January 2019 Dibat

Out · last detection 7 Jan 2019, 23:23 UTC

The fire started on 3 January 2019 in Dibat, Ethiopia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,299 hectares from heat detections, spread across a single municipality.

It is the 272th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 89 in Ethiopia in 2019, of 220.

The power measured by the satellite is low (24.0 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
3,299ha
GWIS perimeter (Copernicus)
Duration
4days
3 Jan 2019 – 6 Jan 2019
Municipalities hit
1
districts
Started on
3 Jan
2019
Heat detections
102
in a single hotspot: 24 MW
Danger at start
37
High · FWI index
Energy released
652MW
sum of detected power

Where it burned

7 Jan 2019
HOTSPOTS BY DAY 3 Jan6 Jan

How it evolved, day by day

34567

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

The weather it burned in

35°high
37km/h · peak gust
4%lowest humidity

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

This area had burned before

69% of the perimeter overlaps earlier fires recorded since 2016: 357 ha in 2016, 1,135 ha in 2017, 1,679 ha in 2018. Part of it burned more than once, so the yearly figures add up to more than the 2,265 ha that had burned before.

What happened to each town

  1. Dibat where it started
    3,318 ha reached on 3 Jan
    1.5 %

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)
3 Jan 33.4 °C 21 % 33 km/h 0.0 mm High 37
4 Jan 35.4 °C 9 % 37 km/h 0.0 mm Very high 46
5 Jan 34.5 °C 4 % 30 km/h 0.0 mm Very high 48
6 Jan 33.3 °C 7 % 25 km/h 0.0 mm Very high 46
7 Jan after 33.5 °C 10 % 32 km/h 0.0 mm Very high 48
8 Jan after 35.5 °C 6 % 29 km/h 0.0 mm Very high 47
9 Jan after 34.8 °C 9 % 24 km/h 0.0 mm Very high 46
10 Jan after 34.1 °C 9 % 28 km/h 0.0 mm Very high 49
11 Jan after 34.6 °C 8 % 29 km/h 0.0 mm Very high 49
12 Jan after 33.7 °C 9 % 33 km/h 0.0 mm Extreme 51
13 Jan after 33.8 °C 8 % 26 km/h 0.0 mm Very high 47
14 Jan after 34.2 °C 7 % 23 km/h 0.0 mm Very high 47
15 Jan after 34.8 °C 12 % 31 km/h 0.0 mm Very high 49
16 Jan after 35.2 °C 12 % 29 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.

Before · 27 Dec 2018
After · 13 Jan 2019

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 · 102Every 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 Dibat fire last?
GWIS (Copernicus) dates it between 3 January 2019 and 6 January 2019: 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 3,299 hectares (33.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Dibat (3,318 ha, 1.5 %).
What was the weather like?
During the fire the temperature reached 35.4 °C, humidity dropped to 4 % and gusts hit 37 km/h. The fire danger index (FWI) reached 48, class Very 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.