Skip to content
worldfires
ET · Ethiopia · →

Kamashi fire, March 2016 Kamashi

Out · last detection 4 Mar 2016, 23:05 UTC

The fire started on 3 March 2016 in Kamashi, Ethiopia, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,723 hectares from heat detections, spread across a single municipality.

It is the 404th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 186 in Ethiopia in 2016, of 309.

Burnt area
2,723ha
GWIS perimeter (Copernicus)
Duration
2days
3 Mar 2016 – 4 Mar 2016
Municipalities hit
1
districts
Started on
3 Mar
2016
Heat detections
58
in a single hotspot: 241 MW
Danger at start
47
Very high · FWI index
Energy released
1.6GW
sum of detected power

Where it burned

4 Mar 2016
HOTSPOTS BY DAY 3 Mar4 Mar

How it evolved, day by day

34

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

The weather it burned in

37°high
39km/h · peak gust
12%lowest humidity

It had gone more than two months 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. Kamashi where it started
    2,741 ha reached on 3 Mar
    1.9 %

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 Mar 35.8 °C 12 % 39 km/h 0.0 mm Very high 47
4 Mar 36.7 °C 12 % 37 km/h 0.0 mm Very high 48
5 Mar after 36.3 °C 14 % 33 km/h 0.0 mm Very high 46
6 Mar after 36.1 °C 16 % 32 km/h 0.0 mm Very high 50
7 Mar after 34.5 °C 15 % 36 km/h 0.0 mm Very high 48
8 Mar after 35.4 °C 9 % 39 km/h 0.0 mm Extreme 52
9 Mar after 36.8 °C 7 % 38 km/h 0.0 mm Extreme 56
10 Mar after 35.0 °C 17 % 34 km/h 0.0 mm Very high 48
11 Mar after 35.9 °C 17 % 30 km/h 0.0 mm Very high 46
12 Mar after 36.2 °C 16 % 29 km/h 0.0 mm Very high 47
13 Mar after 36.2 °C 13 % 32 km/h 0.0 mm Very high 47
14 Mar after 34.0 °C 25 % 52 km/h 0.0 mm Very high 48

Before and after, from space

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

Before · 25 Feb 2016
After · 11 Mar 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 · 58Every 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 Kamashi fire last?
GWIS (Copernicus) dates it between 3 March 2016 and 4 March 2016: 2 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,723 hectares (27.2 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Kamashi (2,741 ha, 1.9 %).
What was the weather like?
During the fire the temperature reached 36.7 °C, humidity dropped to 12 % and gusts hit 39 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.