Wenbera fire, 31 March 2016 Wenbera
The fire started on 31 March 2016 in Wenbera, Ethiopia, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 2,971 hectares from heat detections, spread across a single municipality.
It is the 334th largest in Beneshangul Gumu since 2016 (of 699 with a page). Number 156 in Ethiopia in 2016, of 322.
The power measured by the satellite is low (16.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
Suggestions: Wenbera · 2022Bulen · 2016
- Burnt area
- 2,971ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 31 Mar 2016 – 8 Apr 2016
- Municipalities hit
- 1
- districts
- Started on
- 31 Mar
- 2016
- Heat detections
- 68
- in a single hotspot: 16 MW
- Danger at start
- 32
- High · FWI index
- Average daily power
- 55MW
- detected power per day, on average
Where it burned
How it evolved, day by day
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 8 days without rain (1 mm or more) when it started. Rain came after the fire: 3.5 mm on 13 Apr.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
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
-
Wenbera where it started2,991 ha reached on 3 Apr0.4 %
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.
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 Apr | 31.3 °C | 26 % | 33 km/h | 0.0 mm | High 32 |
| 4 Apr | 35.1 °C | 6 % | 38 km/h | 0.0 mm | Very high 44 |
| 5 Apr | 34.7 °C | 17 % | 35 km/h | 0.0 mm | Very high 40 |
| 6 Apr | 36.3 °C | 7 % | 34 km/h | 0.0 mm | Very high 44 |
| 7 Apr | 35.8 °C | 3 % | 36 km/h | 0.0 mm | Very high 49 |
| 8 Apr | 35.0 °C | 7 % | 41 km/h | 0.0 mm | Extreme 52 |
| 9 Apr after | 35.4 °C | 15 % | 37 km/h | 0.0 mm | Very high 47 |
| 10 Apr after | 34.8 °C | 19 % | 37 km/h | 0.1 mm | Very high 45 |
| 11 Apr after | 35.1 °C | 16 % | 39 km/h | 0.0 mm | Very high 44 |
| 12 Apr after | 35.1 °C | 19 % | 51 km/h | 0.1 mm | Extreme 54 |
| 13 Apr after | 32.1 °C | 28 % | 40 km/h | 3.5 mm | Moderate 16 |
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 · 68Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Wenbera fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 31 March 2016 to 8 April 2016 (9 days). The perimeter dates it from 3 April 2016 to 8 April 2016.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 2,971 hectares (29.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Wenbera (2,991 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 36.3 °C, humidity dropped to 3 % and gusts hit 41 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
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 adjusted with the VIIRS detections inside the perimeter, which said 3 April 2016 to 8 April 2016. 68 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.
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.