Kamashi fire, 5 March 2017 Kamashi
The fire started on 5 March 2017 in Kamashi, Ethiopia, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,540 hectares from heat detections, spread across a single municipality.
It is the 455th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 188 in Ethiopia in 2017, of 266.
Compare with…
- Burnt area
- 2,540ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 5 Mar 2017 – 5 Mar 2017
- Municipalities hit
- 1
- districts
- Started on
- 5 Mar
- 2017
- Heat detections
- 23
- in a single hotspot: 54 MW
- Danger at start
- 42
- Very high · FWI index
- Average daily power
- 433MW
- detected power per day, on average
Where it burned
How it evolved, day by day
5 Mar 2017 · 433 MW · 23
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 10 days without rain (1 mm or more) when it started.
This area had burned before
14% of the perimeter overlaps earlier fires recorded since 2016: 353 ha in 2016.
- 94 ha Kamashi fire, March 2016 2,723 ha in total; the hectares shown are those it shares with this fire
- 65 ha Kamashi fire, January 2016 4,486 ha in total; the hectares shown are those it shares with this fire
- 1 ha Agalometi fire, February 2016 10,558 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Kamashi where it started2,557 ha reached on 5 Mar1.8 %
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 2015Inside the perimeter there were about 0.32 hectares of built-up land and about 200 residents (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
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) |
|---|---|---|---|---|---|
| 5 Mar | 35.4 °C | 14 % | 23 km/h | 0.0 mm | Very high 42 |
| 6 Mar after | 36.1 °C | 13 % | 30 km/h | 0.0 mm | Very high 45 |
| 7 Mar after | 35.2 °C | 18 % | 28 km/h | 0.0 mm | Very high 44 |
| 8 Mar after | 36.1 °C | 18 % | 30 km/h | 0.0 mm | Very high 42 |
| 9 Mar after | 35.4 °C | 18 % | 26 km/h | 0.1 mm | Very high 41 |
| 10 Mar after | 36.6 °C | 17 % | 32 km/h | 0.0 mm | Very high 44 |
| 11 Mar after | 35.8 °C | 18 % | 25 km/h | 0.0 mm | Very high 42 |
| 12 Mar after | 36.6 °C | 14 % | 28 km/h | 0.0 mm | Very high 45 |
| 13 Mar after | 37.0 °C | 14 % | 30 km/h | 0.0 mm | Very high 48 |
| 14 Mar after | 37.7 °C | 20 % | 23 km/h | 0.0 mm | Very high 44 |
| 15 Mar after | 36.5 °C | 19 % | 27 km/h | 0.3 mm | Very high 46 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · 23Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 28,239 haKamashiJanuary 2021 · 16 days · 4 km away
- 15,873 haKamashi24 January 2017 · 12 days · 7 km away
- 10,580 haAgalometi25 January 2022 · 8 days · 10 km away
- 9,791 haAgalometi30 January 2017 · 6 days · 15 km away
- 13,880 haAgalometi27 January 2016 · 11 days · 16 km away
- 10,558 haAgalometi21 February 2016 · 7 days · 17 km away
Frequently asked questions
- How long did the Kamashi fire last?
- GWIS (Copernicus) dates it between 5 March 2017 and 5 March 2017: 1 day 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,540 hectares (25.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Kamashi (2,557 ha, 1.8 %).
- What was the weather like?
- During the fire the temperature reached 35.4 °C, humidity dropped to 14 % and gusts hit 23 km/h. The fire danger index (FWI) reached 42, 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
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.
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
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. 23 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
- 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.
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.